Silvan Fuhrer 1a5d0f4347 AirspeedValidator: add new check (variance after boot) and disable data stuck check by default ...

This new check is inteded to trigger if there is no data variation published by
the airspeed driver for the first 10s after the first data is published.
This is to capture malfunctioning sensors/drivers that do publish a value, this
value though does not come from real sensor measurements.
Previously this was captured by the data stuck check, but it has shown that
some drivers can publish a stuck value without being actually malfunctioning
(e.g. when the airspeed is outside of their measurement range). Checking for
any data variation is the more conservative check that still catches the above
described failure case.

Signed-off-by: Silvan Fuhrer <silvan@auterion.com>

2022-09-19 17:44:44 +02:00

..

airspeed_selector_main.cpp

AirspeedValidator: add new check (variance after boot) and disable data stuck check by default

2022-09-19 17:44:44 +02:00

airspeed_selector_params.c

AirspeedValidator: add new check (variance after boot) and disable data stuck check by default

2022-09-19 17:44:44 +02:00

AirspeedValidator.cpp

AirspeedValidator: add new check (variance after boot) and disable data stuck check by default

2022-09-19 17:44:44 +02:00

AirspeedValidator.hpp

AirspeedValidator: add new check (variance after boot) and disable data stuck check by default

2022-09-19 17:44:44 +02:00

CMakeLists.txt

wind_estimator: move from ecl and consolidate airspeed selector

2021-07-15 10:38:24 -04:00

Kconfig

Add support for protected build in drivers, systemcmds and modules Kconfig

2022-02-18 07:58:58 +01:00