-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
FW LandDetector: disregard horizontal velocity if local_position.v_xy_valid is false #24133
Conversation
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 248 byte (0.01 %)]
px4_fmu-v6x [Total VM Diff: 200 byte (0.01 %)]
Updated: 2025-01-08T16:07:29 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With that change we stay on the conservative side: It makes triggering a false-positive "landing detected* in air very unlikely, with the cost of more false positive "takeoff detected" while still on the ground due to the very tight rotational movement threshold. Given the much higher severity of a false-positive in air I'm okay with that.
A slightly less drastic change would be to only consider the rotational movement check if the velocity (airspeed and groundspeed) are invalid, or work with different thresholds depending on velocity validity. But that in turn introduces more logic complexity, the system gets much harder to tune and debug.
As a next step we could give the FW land detector a bigger overhaul. I want to link it more directly with the FW launch detection and
d116b80
to
03c5958
Compare
In case the local position speed estimate is not valid, it is assumed to be 0m/s and thus check always passes.
…: LNDFW_ROT_MAX). Checks that the filtered norm of the angular velocity is below LNDFW_ROT_MAX.
03c5958
to
d9cad62
Compare
Solved Problem
Horizontal velocity considered in land detector for fixed wings even when invalid.
Solution
Changelog Entry
For release notes:
Test coverage