we are starting to get huge downloads for autotest failures. High
logging rates rarely help to diagnose an issue, so lower the default
rate when in autotest
SITL: vehicle_test_suite.py parameters removal from whitelist
SITL: Add known unit amp hour
SITL: Add known unit Ah
Co-authored-by: Peter Barker <pb-gh@barker.dropbear.id.au>
autotest: tidy WheelEncoders test
autotest: rover: tidy PolyFenceObjectAvoidance code
autotest: add load_fence_using_mavwp
Also corrects the mission item types being returned by the mission-item-to-misison-item-int converter
autotest: fix Rover PolyFenceAvoidanceBendyRulerEasier test
these tests weren't being run becausethey were disabled based on support for loading fence items from QGC files.
autotest: fix Rover PolyFenceAvoidanceBendyRuler test
Autotests for takeoffs have been added for Plane, covering AUTO and
TAKEOFF mode takeoffs.
An auxiliary `set_servo` method has been added to `vehicle_test_suite.py`.
clean-up fence manipulation functions and add test for auto-enablement on copter
update tests to have some FENCE_ENABLE tests
add avoidance minimum and maximum altitude fence
add fence switch test while flying
add FenceAutoEnableDisableSwitch for auto mode 2
add more scenarios for plane fence auto-enable
validate fence rc switch behaviour
check fence autoenable by taking off in guided mode
more FENCE_AUTOENABLE tests
add FenceEnableDisableAux and FenceMinAltAutoEnableAbort
this makes the assumption that any reboot done within a SITL was because some parameter changes only take effect after a reboot.
... so after we have reverted the parameters, reboot again to make the reverted parameter values take effect
we're running at large speedups; 5 simulated seconds might not be enough time for MAVProxy to accumulate statistics. So get MAVProxy to emit the rate each second instead
allows state to be encapsulated within the object rather than simply in the same scope / closure of the method being called.
Will allow easier re-use of these blocks
