MPC: LAND: Split Landing out of FlightTaskAuto into FlightTaskLand #23678
+577
−14
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 #23546 did not consider the case when we trigger land from Altitude or Manual FlightTask, where the commanded velocity can greatly exceed the velocity possible in FlightTaskAuto.
Solution
With this PR, we are splitting the Landing Logic into a separate FlighTask called FlightTaskLand, and handle the landing logic in there.
Test on Hardware
Changelog Entry
For release notes:
Dependent PR's
Test coverage