mirror of https://github.com/ArduPilot/ardupilot
8a2f1fdb3d
this fixes an issue where an airspeed sensor that becomes unhealthy can have an undue effect after the sensor becomes healthy again. In a recent flight log the MS4525 airspeed sensor went unhealthy for a few seconds, and at the same time gave a reading of 12m/s. The plane was flying at 24m/s. While the sensor was unhealthy the code correctly switched to the airspeed estimate, which was fine. When the airspeed sensor become healthy again the IIR filter in AP_Airspeed meant that the speed read at 12m/s initially, then came up to 24m/s over a couple of seconds. This caused the VTOL motors to come on for a few seconds. |
||
---|---|---|
.. | ||
examples/Airspeed | ||
models | ||
AP_Airspeed.cpp | ||
AP_Airspeed.h | ||
AP_Airspeed_Backend.cpp | ||
AP_Airspeed_Backend.h | ||
AP_Airspeed_MS4525.cpp | ||
AP_Airspeed_MS4525.h | ||
AP_Airspeed_MS5525.cpp | ||
AP_Airspeed_MS5525.h | ||
AP_Airspeed_SDP3X.cpp | ||
AP_Airspeed_SDP3X.h | ||
AP_Airspeed_analog.cpp | ||
AP_Airspeed_analog.h | ||
Airspeed_Calibration.cpp |