px4io: servorail_status -> px4io_status and log all flags #15356
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This expands the px4io published
servorail_status
message into a more generalpx4io_status
and adds most of the useful status, alarm, input, output fields as self descriptive fields (ie booleans for bits).Storing just the flags would obviously be more efficient, but we were already paying for the flash to decode and print them in
px4io status
and there's no real mechanism to properly define bits in uORB messages, so they end up poorly defined or ignored in tools or review. This makes it accessible, self describing, and as useful as px4io status, but in all regular logs.The message is published at 1 Hz or immediately on any status or alarm change.