ArduPilot / ArduPilot/MissionPlanner
Parachute release through tab Actions
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
Hello,
I'm opening this issue because I'm experiencing difficulties triggering the parachute release using the Actions tab in Mission Planner.

My colleagues and I followed the setup instructions in the official documentation: https://ardupilot.org/plane/docs/common-parachute.html
We were able to successfully trigger the parachute release through the Aux Functions tab:

Clicking the "High" button with the "Parachute Release" function selected activates the release as expected.
However, when trying to trigger the release via the Actions tab, nothing happens.
Worse, it seems to prevent the parachute from being triggered at all even through the Aux tab, which worked before. The only way to restore the release function is to restart the system.
After reviewing the code (FlightData.cs), I noticed that at line 1733, param1 is set to 0.
According to the parachute documentation, param1 = 0 corresponds to “Disable parachute release”.
Line 1812, there’s the relevant code snippet of the execution of the mavlink command :
`if (MainV2.comPort.doCommand(cmd, param1, param2, param3, 0, 0, 0, 0))`
In this flow, param1 remains unchanged, which seems to result in the parachute not being released. So, from what I understand, the DO_PARACHUTE command being sent via the Actions tab is effectively disabling the release rather than triggering it.
Could someone please confirm if this is a bug or if I'm missing something in the configuration?
Contributor guide
No contributing guide indexed for this repository
Research direction
Read FlightData.cs around lines 1733 and 1812, then trace how the Actions tab constructs and sends the DO_PARACHUTE command. Compare its behavior with the working Aux Functions tab and the documented param1 values. Done means the Actions tab triggers parachute release without disabling the function or requiring a system restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100