You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INAV 8.0 added support for Mavlink protocol, when i setup my ELRS RX to talk to INAV over mavlink (and not CRSF), things changes on how INAV send his readiness/arm status
when using mavlink, FC sensor reported back to EdgeTX is now different, it will always state the mode, and arm/not armed is stated by * at the end
so, other words:
ACRO = not armed but in acro mode
ACRO* = acro + armed
MANU = not armed but in manual mode
MANU* = manual mode+ armed
i did dig a bit to the lua code, i saw it using bit32.band modes which i totally did not understood, but i know the solution will be there.
To reproduce
use INAV 8.0
use ELRS radio setup
on INAV > Ports, disable serial and enable mavlink protocol for the RX UART
on INAV > Receiver, enable back serial and choose mavlink
on INAV > CLI > set mavlink_radio_type=ELRS > save
on ELRS RX change protocol mavlink
on ELRX TX change mode from regular to mavlink
at this point we should have back RC control and telemetry
however now the LUA telemetry is not working well, when armed it think it is not armed, and when not armed it think it is armed
Expected behavior
it should read FC sensor / bit32.band mode E correct and state armed when armed and state not armed when not armed
The text was updated successfully, but these errors were encountered:
This is not a bug. This is an INAV LUA. Not a MAVLink LUA. This LUA works with standard receiver telemetry. Not MAVLink.
Some MAVLink support was added to INAV to support ArduPilot GCS software. INAV is still an MSP based system. Which means using an MSP GCS would be a better choice, such as MWPTools.
Hi Darren, I see your point :)
i simply think that many people will go for this setup of mavlink elrs in the near future (those who really like the ease and convenience INAV offers but would really like using some ground station software + still have INAV telemetry to the RC (using the INAV LUA))
Describe the bug
INAV 8.0 added support for Mavlink protocol, when i setup my ELRS RX to talk to INAV over mavlink (and not CRSF), things changes on how INAV send his readiness/arm status
when using mavlink, FC sensor reported back to EdgeTX is now different, it will always state the mode, and arm/not armed is stated by * at the end
so, other words:
ACRO = not armed but in acro mode
ACRO* = acro + armed
MANU = not armed but in manual mode
MANU* = manual mode+ armed
i did dig a bit to the lua code, i saw it using bit32.band modes which i totally did not understood, but i know the solution will be there.
To reproduce
at this point we should have back RC control and telemetry
however now the LUA telemetry is not working well, when armed it think it is not armed, and when not armed it think it is armed
Expected behavior
it should read FC sensor / bit32.band mode E correct and state armed when armed and state not armed when not armed
The text was updated successfully, but these errors were encountered: