-
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
commander: ensure health report is always sent out before failsafe notificaation #23973
Conversation
…tificaation As the failsafe message can reference the health report, the health report needs to be sent out first. This is generally the case, except there is a rate limiter set to 2 seconds. So if the report changes quickly, it is sent out delayed (potentially after the failsafe report).
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.
Thanks for looking itno it! A classic C callback setup to allow triggering a healt_and_arming_checks action based on a consition in the completely separate failsafe state machine.
It works and crosses the nice architectural separation to have the nice behavior to only update in the necessary case.
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.
One CI failure is real: https://github.com/PX4/PX4-Autopilot/actions/runs/11934542772/job/33263873602?pr=23973
d7189a3
to
921cd8a
Compare
FLASH Analysispx4_fmu-v5x
px4_fmu-v6x
|
As the failsafe message can reference the health report, the health report needs to be sent out first. This is generally the case, except there is a rate limiter set to 2 seconds. So if the report changes quickly, it is sent out delayed (potentially after the failsafe report).