Copter: Throw mode's NextMode and Drop feature #4592
Closed
Conversation
This file contains 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
This makes it easier to add more state which is required for the follow throw_nextmode change
vehicle switches to mode specified in THROW_NEXTMODE parameter after the throw is completed.
No functional change
No functional change
rmackay9
changed the title
|
Merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR adds two new features to Throw mode:
This PR also removes the use of the interlock and instead uses the motor spool logic. This resolves a problem with being unable to arm if the THROW_MOT_SPIN was set to "1" (the arming checks complained that the motor interlock was on) and it generally simplifies (I think) how the motors are turned on/off without interfering with the interlock.
This PR includes the changes from these two (now closed) PRs:
#4410
#4585