Fatal crash during takeoff when mode switched to Pos Hold (log supplied)

I used a Mavlink command over telemetry to command my drone to takeoff. During takeoff I accidentally switched from Loiter mode to Position Hold mode using my transmitter (I touched a switch by mistake). The throttle was at minimum and the drone was about 3m up by my own judgement. Immediately the drone plummeted to the ground in a seemingly uncontrolled manner (it was tilted heavily to one side). The descent rate seemed much faster than normal Position Hold descent.

Does anyone have any ideas what happened? I looked at the log myself and it doesn’t show the change to Position Hold which I find strange…

Link to log:


Password is my username.

Thanks!

Loiter or position hold is quite the same. Your RC3 (throttle) is not at minimum in the log.

RC7 is switched at 19:52:47.9

Capture d’écran 2021-05-13 à 13.20.06

And a motor emergency stop occurred according to RC7 settings

Capture d’écran 2021-05-13 à 13.23.08

Capture d’écran 2021-05-13 à 13.22.53

1 Like

Hello! Taking a quick look to your log, I can see that there are some problems, but first of all, you were always on loiter, so you didn’t change to posHold:

It seems that you tried to perform three flights, in the first two the motors were at maximum trying to take off but the current altitude didn’t change, so that indicates that there is a problem with inverted propeller (or directly none) or you have an overweight/underpower drone.

And in the last flight, your motors and the roll/desRoll were crazy, so you have a big problem with the attitude of the drone

So have you followed the tuning instructions and configured the basic tuning parameters pressing ALT+A on Mission Planner?

1 Like

Yes, I applied motor emergency stop as soon as the drone hit the ground to prevent an ESC fire.

I have tuned each axis separately using autotune but I have not modified any of the tuning values manually. Do you recommend I do that? I avoided it because it seemed dangerous.

I should reiterate that the command to takeoff was done while the drone was in guided mode. I think the loiter mode is the original mode before I commanded guided mode using Mavlink. Does this make sense?

Thanks.

If you performed an autotune, then it seems that the new PID values are bad and the drone is very unstable, so I suggest you to perform a flight with the default PIDs and upload that log to see the differences.

The drone wasn’t in guided mode, the drone was all time in Loiter, you can see it in the logs and in the pictures above.

Thank you for your reply. I will be off to retune my drone. Many thanks again.