I am trying out the (latest) ArduPilot and noticed that I have to#define AIRSPEED_SENSOR 1in order to NOT get a "disabled" reading using "test" "airspeed" functionHowever I also noticed that with the sensor disconnected (or perhaps broken), with that #define set, test/airspeed gives readings that vary from 0.0 m/s to 30 m/s, how it varies depends on when you kick off the test.What if one launched with a disconnected or broken airspeed sensor, but with AIRSPEED_SENSOR 1 set in the code? does that play havoc with the autopilot?How about a detection (if AIRSPEED_SENSOR is defined) that samples the airspeed port, and if the values are changing a great deal over a second or two, conclude that the sensor is not connected or is not functioning?
You need to be a member of diydrones to add comments!
You don't need to touch the code! Are you going through the normal setup process in the Mission Planner? You just enable the airspeed sensor on the hardware setup page. Just check the box.
Replies