Plane supports being armed, in takeoff logic and not spinning the motor
until the moment the safety button has been pressed. Unfortunately
because the safety button is required to be pressed for soft arming this
results in the plane updating home position while the user moves the
vehicle or is holding it to throw the vehicle which will can result in
several meters of altitude error from where the user expected home to
be.
Because the normal approach to plane is to have activated the safety
button before arming the aircraft this is not expected to be a behaviour
change for most users, but an improvement for people who use the button
to initiate a takeoff.
this is most often implemented as dual-motor differential thrust, and
we don't want to do surface speed scaling for that.
In the future we'll move this scaling so it can be done on rudders for
3D planes
Navio2 exports its leds via /sys/class/leds interface. We reuse it in
order not to conflict with GPIO_Sysfs. Otherwise we'd get a Device Busy
error in GPIO_Sysfs::_export_pin().
This addresses the enhancement requested in: https://github.com/ArduPilot/ardupilot/issues/2424
It checks various PID values to check if they are zero, if they are and the corresponding rate forward feed is zero then it flags it as PreArm failure.
It has been added to the parameter check, so can be overridden if required.
Based on work done by khancir
(https://github.com/ArduPilot/ardupilot/pull/6360)
Tools: arduplane.py change print to progress function
Tools: quadplane.py change print to progress function
Tools: ardusub.py change print to progress function
Guy Tzoler
Michael du Breuil
Patrick José Pereira
Samuel Tabor
Andrew Tridgell
Georgii Staroselskii
Randy Mackay
Peter Barker
murata
Leonard Hall
ChrisBird
khancyr
Jacob Walser
DOMINATOR\Eugene
Pierre Kancir