Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FlightTasks: do not adjust tilt limit of the position control #14702

Merged
merged 1 commit into from Apr 21, 2020

Conversation

MaEtUgR
Copy link
Member

@MaEtUgR MaEtUgR commented Apr 19, 2020

Describe problem solved by this pull request
Adjusting the tilt limit can lead to diverging position control and should only be used by setting a sanity limit for the controller and not to adjust during the descent phase of a Land or RTL. Otherwise it leads to flyaways in important failsafe modes when there's stronger disturbance e.g. wind.

Describe your solution
I removed all occurances where flight tasks sets a tilt limit. All of them except for the one in AutoMapper's _prepareLandSetpoints() were setting the maximum redundantly. The auto land point one was causing the position control divergence on RTL and Land descend.

Describe possible alternatives
As discussed with @RomanBapst the goal landing strategy is to relax xy position control and ramp down the thrust gradually on ground contact as a next step of improvement.

Test data / coverage
I did quite some tests in SITL using different wind strengths made possible by @Jaeyoung-Lim 's efforts like PX4/PX4-SITL_gazebo-classic#461

It has to be said that before #12324 this tilt limit was already missing for a long time and hence we already know it's not breaking the user experience.

Additional context
fixes #13956

Adjusting the tilt limit can lead to diverging position control
and should only be used by setting a sanity limit for the controller
and not to adjust during the descent phase of a Land or RTL.
Otherwise it leads to flyaways in important failsafe modes when
there's stronger disturbance e.g. wind.
@MaEtUgR MaEtUgR requested a review from bresch April 19, 2020 11:13
@MaEtUgR MaEtUgR self-assigned this Apr 19, 2020
@bresch bresch added this to In progress in Multicopter via automation Apr 20, 2020
Multicopter automation moved this from In progress to Reviewer approved Apr 20, 2020
@LorenzMeier
Copy link
Member

When it does get approved, why are we not merging it?

@LorenzMeier LorenzMeier merged commit 809b45e into master Apr 21, 2020
Multicopter automation moved this from Reviewer approved to Done Apr 21, 2020
@LorenzMeier LorenzMeier deleted the flight-task-no-tilt-limit branch April 21, 2020 07:35
@MaEtUgR
Copy link
Member Author

MaEtUgR commented Apr 21, 2020

I assumed we'd need some real-world tests but everything I read from the problematic logs so far speaks for removing the limit. Making it part of the acceptance test for the release is probably more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Multicopter
  
Done
Development

Successfully merging this pull request may close these issues.

Issue with landing PixRacer FMUV4_K66, FMUv5
3 participants