Airspeed sensor calibration fails. But why?

ArduPlane
, ,
1

I’ve got a (EasyStar 3) fixed wing, in which I now built a (Holybro) digital airspeed sensor. When I blow on it I see increased airspeed reading in Mission Planner, so it does seem to work. When I go into QGroundContol and try to do a Baro/Airspeed pressure calibration it fails though. The only thing it displays is

Requesting pressure calibration…
Failed

Does anybody know what could be wrong here? How can I debug this?

2

Does the same error message appear when you trigger a preflight calibration with Missionplanner ?

3

In MissionPlanner I indeed also get an error:

The Command failed to execute PREFLIGHT_CALIBRATION

Are the preflight calibration in MP and the Baro/Airspeed pressure calibration in QGC the same thing?

These error messages are so vague that I don’t have a clue what to do. Do you know what a next step could be?

4

Is ARSPD_SKIP_CAL perhaps disabled ?
Or do you have an sdp33 sensor, the only one with ARSPD_SKIP_CAL has to be disabled.

Rolf

5

ARSPD_SKIP_CAL was indeed set to false. I set it to true and tried the calibration in both QGC and MP again, but they both fail in exactly the same way.

Btw, I’ve got this Holybro digital airspeed sensor.

Do you know if those checks in MP and QGC are actually doing the same thing?

6

Sorry, I don’t know, since I mainly use MP.

If Airspeed is displayed when you blow into it, but the error message comes up when you recalibrate, that’s strange.
Could it not be that the error message means that the calibration could not be triggered by the GCS ?

Rolf

7

Yes I assumed something similar, but I’m unsure why that could be. At this point I’m completely in the dark though. Do you know if I can get some kind of logging from the hardware, to get more details on the error?

8

I sometimes have similar error messages (that commands from the GCS cannot be executed) when the MAvlink connection is wireless. Does the error occurs with USB connection ?

9

It took me some time to test this, but I finally managed to. Unfortunately the error is the same as before, both in Mission Planner and QGroundControl.

Any more ideas on how to debug this? Can I get more detailed logs from the hardware?

10

The best thing to do is to post a link to a log file with the problem ( Enable logging while disarmed: LOG_DISARMED 1) .