-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Land detector edge case in descend mode #13231
Comments
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
@MaEtUgR Can you think of a simple solution? |
This has been reworked since, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The land detector seems to detect ground contact in Descend mode (RC land failsafe without GPS).
vertical_movement
to befalse
: https://github.com/PX4/Firmware/blob/95dc522b99688a08402ac6462ad28f5dfd338eda/src/modules/land_detector/MulticopterLandDetector.cpp#L154hit_ground
to betrue
: https://github.com/PX4/Firmware/blob/95dc522b99688a08402ac6462ad28f5dfd338eda/src/modules/land_detector/MulticopterLandDetector.cpp#L165This happens because the z controller only reacts slowly to the new setpoint so the z velocity down is much less than the z velocity setpoint here:
https://github.com/PX4/Firmware/blob/95dc522b99688a08402ac6462ad28f5dfd338eda/src/modules/land_detector/MulticopterLandDetector.cpp#L151-L154
One observation of the descend case is that the velocity setpoint jumps to the land speed instead of gradually reaching it like in Land (with GPS) mode.
To Reproduce
This is hard to reproduce in SITL because the drone seems to follow the setpoint quicker.
Expected behavior
It should not detect ground contact until actually landed.
Log Files and Screenshots
This happened in a failsafe descend test:
https://review.px4.io/plot_app?log=3104d449-dd29-473f-9055-354984ff8afa
This does not happen in normal landing:
https://review.px4.io/plot_app?log=2ea6423f-b232-45c9-8c40-32e775118359
More info in #13143 (comment).
FYI @bresch @MaEtUgR
The text was updated successfully, but these errors were encountered: