Commander: always allow to switch to LAND mode, also if requirements are not met #23580
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.
Solved Problem
The manual trigger of "Land" mode is often done in emergencies, when you want the vehicle to stop the current operation and land ("come down") at the current spot. As it is though an auto flight mode, the Land mode gets rejected when e.g. local position is invalid. In these scenarios the only option for the pilot is to land the vehicle manually, which is a more complex action than clicking on a single button. And for VTOL there comes additional complexity should the pilot have to land it manually, as in that case he/she has to also trigger the transition manually. If in Land/Descend mode the transition to Hover is automatically done.
Solution
For now hard-coded that the switching into Land does never get rejected. We maybe want to hide it behind a param or an extra field in the mavlink messages (see #Alternatives).
Changelog Entry
For release notes:
Alternatives
Context
Screenrecording of simulation of targeted use case:
Note: requires this fix: #23578
QGC_VTOL_Land_GPS_denied.mp4