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.

Sign up for GitHub

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

Jump to bottom

AP_Airspeed: Refuse to calibrate sensors if a device was not initialized #28471

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

AP_Airspeed: Refuse to calibrate sensors if a device was not initialized #28471

wants to merge 1 commit into from
+2 −1

Commits on Oct 25, 2024

  1. AP_Airspeed: Tag a uninit airspeed sensor as a failure when calibrating 

    This helps catch the case where a GCS commands a calibration, and the
command is reported as MAV_RESULT_ACCEPTED, even though the actual state
is that at least one sensor backend failed. We are still letting the
other sensors be calibrated in this situation as a GCS may not be paying
proper attention to what happens with the MAV_RESULT and a user could
miss the status text, so it's safer to calibrate everything we can, and
then report a failure afterwards.
    @WickedShell
    WickedShell committed Oct 25, 2024
    Configuration menu
    Copy the full SHA
    32a87ce View commit details
    Browse the repository at this point in the history