Today we have two options; to use or not to use AS.
If airspeed is disabled, it is not displayed in Mission Planner, or can be
displayed on OSD.
In order to enable better, more reliable AS tuning, testing, or just use it for
OSD I wish one of two methods were in place:
IF AIRSPEED_SENSOR=Enabled (use airspeed for AP (just as today))
IF AIRSPEED_SENSOR=Disabled (don't use airspeed for AP, but get it and provide
over MAVlink)
or: If the above method have a drawback:
IF AIRSPEED_SENSOR=0 (don't use airspeed for AP, no AD)
IF AIRSPEED_SENSOR=1 (get and use airspeed for AP (just as today))
IF AIRSPEED_SENSOR=2 (don't use airspeed for AP, but get it and provide over
MAVlink)
of course, to save variable space, we could have two bool values:
AIRSPEED_SENSOR (enabled/disabled) (when enabled - the values are in MAVlink)
AIRSPEED_USE (enabled/disabled) (AP would use it if enabled)
Original issue reported on code.google.com by andre.kj...@gmail.com on 29 Mar 2012 at 7:12
Original issue reported on code.google.com by
andre.kj...@gmail.com
on 29 Mar 2012 at 7:12