-
Notifications
You must be signed in to change notification settings - Fork 4
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
Arming Module #61
Arming Module #61
Conversation
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.
Please, fix the dronecan and cyphal modes. When the node is engaged, it shouldn't be in initialization mode as shown in your video. Since you have extended Module::Mode and it doesn't correspond to cyphal and dronecan modes anymore, you should manually convert from Module::Mode to cyphal and dronecan modes.
…to one with ArmingStatus
c429303
to
ee82489
Compare
Quality Gate passedIssues Measures |
stats.engaged_time
parameter. It checks mode of the node and setup the number of seconds the node was ENGAGED.STANDBY, ENGAGED, INITIALIZATION, MAINTENANCE
, mode assign for active components was updated relatively with theENGAGED
mode logic.Firmware image size difference
Test coverage
Screencast.from.09-02-2024.04.02.44.PM.webm