Add more stage separation options for deployable payloads and a deployable payload example #2529
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…fter the condition is met the delay is added
…, apogee, and specific altitude during descent to support payloads with separate descent
Member
|
Very nice! |
JoePfeiffer
changed the title
JoePfeiffer
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds three new stage separation options: separate at a given altitude (ascending), separate at apogee, and separate at a given altitude (descending). All three can have a delay following the trigger event.
Separate at apogee and separate at altitude (descending) are to support deployable payloads, which descend on their own recovery system separate from the rest of the rocket. Separate at altitude (ascending) is to support a conventional booster/sustainer; I noticed recently that at least one flight computer (Altus Metrum EasyMega/TeleMega) can be programmed to fire an event in this circumstance.
Created an example rocket consisting of the existing Simple Model Rocket example with an added deployable payload.
One last thing while I was in there I reordered the fields for recovery device deployment to make the decision flow more obvious; the delay after the triggering event is now the last thing in that dialog.
Fixes #852 and fixes #2519