If changing mode to LOITER fails, fallback to ALT_HOLD #298
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
Contributor
|
Are you doing a new release? Or should we look at integrating this in the community? |
Author
|
This is a candidate for a change to Site Scan behaviour. |
Contributor
|
Ok, cool |
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.
We've seen a case where the drone entered
failsafe.GPS_GLITCHstate and remained in GUIDED mode. They tried to take manual control by changing mode to LOITER. The system refused to enter the LOITER mode, because of the GPS_GLITCH failsafe state.This PR introduces a fallback mechanism where it attempts to enter ALT_HOLD mode after a failed attempt to enter LOITER mode.