Copter disarmed in air (4.1.2)


while testing today after updating the FW to 4.1.2 and updating settings, the quad disarmed while hovering approx. 15m in the air.
After inspecting the log, it seems like the FW thought that the quad was landed and then deactivated the motors. Sadly, I don’t know my way around the logs enough to find out exactly what happened and it might be interesting for the devs too. I’ll attach the .bin file and the settings file.

FC: Matek H743 Slim
ESC: T-Motor Velox, using dshot
GPS: Matek M8Q-CAN
RC: Crossfire Nano
Props are 7"
Using a Li-Ion battery with 1450 mAh and 30C
The copter was connected to a RPi running OpenHD 2.0.7 and getting commands from a custom GCS software.

Thanks in advance! (709.9 KB)
lipo_init.param (20.4 KB)

1 Like

Do you have two rangefinders?
One of them was working but the other was not.

Actually yes, one Benewake TFmini-S and one inside the Matek 3901-L0X flow sensor.
Are both used for the height estimation? Could that have caused it?

The 3901-L0X should have a max usable height of 2m, so at 15m it is not expected to work.

Well, it seems to have been user error…

Here we can see that RCIN.C7 (red), which is my switch for disarming, was toggled to high and then low again. Afterwards Arduplilot deactivated the motors (green line) and the drone fell (height in blue).
Why the switch was toggled to high (thus taking over control from the GCS) is unclear, but lesson learned: When the GCS arms the drone, set the arm switch on the transmitter to high too.