-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
[WIP] Telemetry status: report type and ID of remote system #9473
Conversation
Quick question: If the link is connected to multiple external/remote systems, what happens? Do we maybe need to report 0 then for ALL / broadcast? I want to avoid having the remote ID toggling randomly. |
Good point. We can detect if the ID changes more than once (ex 0 - > 1 - > 255) and report 0. |
This is causing a failsafe activation in CI leading to a mode switch failure. Failsafe repeatedly cycles between enabled and disabled. Unfortunately, I don't have more info than that. ex:
#9440 does the same thing. |
@jlecoeur Could you please look into the CI failure? This PR is breaking something. Thanks! |
cd38ac1
to
4a41e5b
Compare
This reverts commit a1426dd.
Revisiting this idea - #10933 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. |
This PR adds infos about remote MAVLink systems into the topic telemetry_status:
mavlink status
prints these infos, useful to identify which instance is connected to whatPlease review carefully the changes in Commander, I do not want to break the detection of loss of GCS telemetry.