Skip to content
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

common.xml: add note about enable parachute before release #253

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

peterbarker
Copy link

No description provided.

@peterbarker
Copy link
Author

@hamishwillee AFAICS QGC and PX4Firmware don't use these.

@@ -1090,7 +1090,7 @@
<param index="7">Empty</param>
</entry>
<entry value="208" name="MAV_CMD_DO_PARACHUTE" hasLocation="false" isDestination="false">
<description>Mission item/command to release a parachute or enable/disable auto release.</description>
<description>Mission item/command to release a parachute or enable/disable auto release. Note that to release a parachute it must first be enabled, so a PARACHUTE_RELEASE must be preceeded by a PARACHUTE_ENABLE</description>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peterbarker This is not correct/consistent, based on definition of PARACHUTE_ACTION:

0 PARACHUTE_DISABLE Disable auto-release of parachute (i.e. release triggered by crash detectors).
1 PARACHUTE_ENABLE Enable auto-release of parachute.
2 PARACHUTE_RELEASE Release parachute and kill motors.

So PARACHUTE_ENABLE does not enable release as a precondition to PARACHUTE_RELEASE "commanded release". What it does currently is is enable./disable auto release as a safety mechanism.

Note I'm not opposed to this change, but you'd also need to update PARACHUTE_ENABLE/PARACHUTE_DISABLE to say something like "Disable auto-release of parachute, both manual and automatic (i.e. release triggered by crash detectors)."

Lastly, do all parachutes support enabling, and is the default that they are enabled or disabled? My assumption is that this depends on the flight stack. Might be worth adding that to the mix

Suggested change
<description>Mission item/command to release a parachute or enable/disable auto release. Note that to release a parachute it must first be enabled, so a PARACHUTE_RELEASE must be preceeded by a PARACHUTE_ENABLE</description>
<description>Mission item/command to release a parachute or enable/disable auto release. Note parachute release may be disabled by default: a PARACHUTE_RELEASE should be preceded by PARACHUTE_ENABLE.</description>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants