feat(commander): extend COM_PARACHUTE to configure parachute failsafe#26918
feat(commander): extend COM_PARACHUTE to configure parachute failsafe#26918
Conversation
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 192 byte (0.01 %)]px4_fmu-v6x [Total VM Diff: 184 byte (0.01 %)]Updated: 2026-03-31T16:04:18 |
a98093f to
ced41d1
Compare
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 176 byte (0.01 %)]px4_fmu-v6x [Total VM Diff: 128 byte (0.01 %)]Updated: 2026-04-23T15:49:42 |
ced41d1 to
25b24c8
Compare
hamishwillee
left a comment
There was a problem hiding this comment.
This needs docs - the main page for failsafes is here https://docs.px4.io/main/en/config/safety
You should add a badge like <Badge type="tip" text="PX4 v1.18" /> to the new section.
This may also need update to https://docs.px4.io/main/en/peripherals/parachute and https://docs.px4.io/main/en/advanced_config/flight_termination
Also a release note here https://docs.px4.io/main/en/releases/main
Non-blocking, but is there a planned QGC safety panel update. Makes things easier for users.
@gguidone If you need help, ping me.
💡 Commit messages could be improvedNot blocking, but these commit messages could use some cleanup.
See the commit message convention for details. This comment will be automatically removed once the issues are resolved. |
|
No broken links found in changed files. |
c719bd3 to
b2f6cc6
Compare
226c1f7 to
e254c0b
Compare
hamishwillee
left a comment
There was a problem hiding this comment.
Approved for the docs part - thanks for the work, and advice on the enabled bit.
Note, there are some merge conflicts
…ilsafe Previously the parachute unhealthy failsafe was hardcoded to RTL.
Update safety.md, peripherals/parachute.md, and releases/main.md to document the extended COM_PARACHUTE parameter and the new configurable in-flight failsafe behaviour.
5ac205b to
a7c79ef
Compare
Solved Problem
Previously, the parachute health failsafe was hardcoded to RTL and enabling/configuring the check required two separate parameters. This is too restrictive for mission profiles where a simple warning or landing is preferred.
Solution
Unified
COM_PARACHUTEinto a single enum that controls both whether the check is active and what action is taken:Values ≥ 2 block arming.
Test coverage
COM_PARACHUTEvalues behave correctly upon failure injection.