3.4.4 does not trigger failsafe on low battery ?!?!

two flight this morning with 3.4.4 /Pixracer
battery fs voltage was set at 11.3v, first flight quad disarmed on rtl at about 2m agl and crashed, second flight with a new fully charged 3s started at 12.5v when it hit 11.2v for more than 1 min on GS, failsafe was not triggered. Only FS for battery is voltage , current set to 0. As per user manual it is supposed to fail safe
The log from second flight, first one with the crash log was not saved …


The voltage was at no time for more than 10 seconds lower than 11.3 volts



Re the crash at 2m. That sounds like a false positive on the landing detector (i.e. it thought it was landed when it wasn’t). That’s very rare but it’s possible. If you manage to find the log, or it happens again and you can get the log, I’d like to have a look at it.

The way it can happen is if the motors are at their minimum levels for a second or two but the vehicle doesn’t descend. This makes the software think it’s landed. It’s very rare for that to happen on a vehicle that isn’t landed but it’s possible especially if the lower end of the motor ranges are set too high. So what might help is to check if the MOT_SPIN_MIN parameter value can be reduced. In your logs it’s set to the default of 0.15. I suspect that can be reduced to 0.12 or even lower. It should never be set lower than MOT_SPIN_ARM though so reduce MOT_SPIN_ARM as well maybe. You can test when the motors start spinning on the mission planner’s motor test page (documented on the wiki page below).

1 Like

Mot spin arm was set to 0 trying to execute a condition delay takeoff. Thanks Randy!