-
Notifications
You must be signed in to change notification settings - Fork 14.6k
[crsf] Add support for link statistics message #25693
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
base: main
Are you sure you want to change the base?
Conversation
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 920 byte (0.05 %)]
px4_fmu-v6x [Total VM Diff: 920 byte (0.05 %)]
Updated: 2025-10-08T05:20:21 |
a7e0589
to
66ed0e3
Compare
Do people really need both uncalibrated (input_rc) and calibrated (manual_control_setpoint, etc) data exposed? I'd send everything if we could afford it... I'd also try to avoid making msgs versioned by default and only do it once strictly needed. We don't want to force unnecessary data migration work on people if it doesn't actually matter. |
I want to drop a bit of a bomb here: I think message versioning inside the PX4 firmware was a bad idea from the start. The MCU is the wrong place to be solving this. Adding versioning at the firmware level complicates things unnecessarily and forces migrations that don’t actually bring value for most users. If we really want some safety guard, a lightweight hash/checksum is enough. With that in place, a ROS 2 node can take care of everything else if needed including handling conversions or bridging between formats just using optional hashes for integrators that suffer from this problem. This keeps PX4 clean and avoids burdening the firmware with problems that belong on the integration side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@niklaut Can you also update https://docs.px4.io/main/en/telemetry/crsf_telemetry.html#telemetry-messages - and add a note in https://docs.px4.io/main/en/releases/main.html
66ed0e3
to
f5a0664
Compare
I think those are different messages relating to something with OpenTX. The table is copied from the PDF, I don't think I should add anything to it. |
Fair enough. I guess my point is "if this is a message that users can get and might find useful, we should document it". If not, ignore. |
f5a0664
to
97de489
Compare
No flaws found |
Solved Problem
Changelog Entry
For release notes:
Alternatives
We could also split the input_rc message into just the control values and then a input_rc_link message with all the link quality metrics. But that involves probably quite a lot of refactoring.
Test coverage