Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telemtry (arming state) not working with INAV 8.0 when using Mavlink Portocol (over ELRS) #167

Open
Itay-Sharoni opened this issue Jan 28, 2025 · 2 comments

Comments

@Itay-Sharoni
Copy link

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

  1. use INAV 8.0
  2. use ELRS radio setup
  3. on INAV > Ports, disable serial and enable mavlink protocol for the RX UART
  4. on INAV > Receiver, enable back serial and choose mavlink
  5. on INAV > CLI > set mavlink_radio_type=ELRS > save
  6. on ELRS RX change protocol mavlink
  7. 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

@MrD-RC
Copy link
Collaborator

MrD-RC commented Jan 28, 2025

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.

@Itay-Sharoni
Copy link
Author

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))

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants