TAKEOFF - clarify behaviour on VTOL #1377
Merged
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 clarifies that if a vehicle supports multiple modes (e.g. like a VTOL quadplane) then the takeoff command should do so in the current mode. The alternative is that it should switch to the VTOL/multicopter mode everyt time before takeoff. This behaviour is I believe the "standard" for both ArduPilot and PX4.
We should similarly define how vehicles should behave for MAV_CMD_NAV_VTOL_TAKEOFF. We could define as:
Note, the specific behaviour we choose not as important as consistent experience for GCS users.
Thoughts? @auturgy @julianoes ?