-
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
Pr move land detector mavlink to airspeed validated #13710
Pr move land detector mavlink to airspeed validated #13710
Conversation
This e.g. changes the way QGC displays the airspeed in case of an airspeed failure (0 instead of the last valid airspeed). It will always display the airspeed that's used currently in the control modules. Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
…airspeed topic - the land detector checks further if the airspeed is NAN, in which case it sets the airspeed to 0 (min groundspeed, vz and accel checks still have to pass. Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
In another PR we should also add something to commander to require that the airspeed selector is alive and well for arming as FW or VTOL. |
@PX4/testflights could you give this a try the next time you fly FW or VTOL? |
Tested on Pixhawk 1 fixed-wing Take off: no issues log: |
…ents - replaced ternary by conditional - set airspeed to 0 if airspeed_validated stops publishing Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
@dagar is this now good to be merged from your side? |
* Mavlink: subscribe to airspeed_validated instead of airspeed topic This e.g. changes the way QGC displays the airspeed in case of an airspeed failure (0 instead of the last valid airspeed). It will always display the airspeed that's used currently in the control modules. * FW land detector: move to subscribe to airspeed_validated instead of airspeed topic - the land detector checks further if the airspeed is NAN, in which case it sets the airspeed to 0 (min groundspeed, vz and accel checks still have to pass. * Fixed-wing land detector use airspeed_vaidated: addressed review comments - replaced ternary by conditional - set airspeed to 0 if airspeed_validated stops publishing Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
* Mavlink: subscribe to airspeed_validated instead of airspeed topic This e.g. changes the way QGC displays the airspeed in case of an airspeed failure (0 instead of the last valid airspeed). It will always display the airspeed that's used currently in the control modules. * FW land detector: move to subscribe to airspeed_validated instead of airspeed topic - the land detector checks further if the airspeed is NAN, in which case it sets the airspeed to 0 (min groundspeed, vz and accel checks still have to pass. * Fixed-wing land detector use airspeed_vaidated: addressed review comments - replaced ternary by conditional - set airspeed to 0 if airspeed_validated stops publishing Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
Alternative to #13706, this time with moving the subscription of the FW land detector and mavlink to airspeed_validated.
SITL tested, eg FW mission where in mid-flight the ASPD_STALL is set to 100 to trigger an "airspeed invalid" declaration. The plane then keeps on flying in non-airspeed mode, and after landing the land detector correctly detects the landing. https://review.px4.io/plot_app?log=48c0f65a-35bc-4241-b3ea-5e4a0aef78db