Motors cut off mid flight

Hi everyone,

I’ve recently done a new build running arducopter on a speedybee f405 v4 and the motors cut mid flight. I cannot for the life of me find out how. I’ve analyzed the logs a lot of times and still cannot come up with a reason.

Context: I took off in loiter mode (and stayed in it for all of the flight), and reached some altitude, then descended. It stabilized at my desired altitude (and even fought against very strong wind) and then, as I was descending to land (still in loiter) it just cut off all motors. There was a beep just before this happened (unfortenatly do not have video).

If anyone can help me sort this out, I would really appreciate it.

Link to the log file: https://drive.google.com/file/d/1L8QPsA_J-EQ4jynDWGIxuBLJbLKAYHIm/view?usp=drive_link

Thanks!

Remove the access requirement from the link for help.

Sorry, forgot about that. I’ve removed it now. Thanks!

Perhaps the ESC’s overheated from the output oscillation due to many default parameters. Rate PID’s and the Vertical Acceleration Controller gains specifically. Current dropped out, outputs went to max. You are not configured for ESC Telemetry which may have exposed that. The Motor Ranges are at default also.

A couple of ugly looking graphs:


1 Like

I noticed during flight that the gains seemed a bit too high. Given all these oscilations, would you turn them down?

Yes, as part of a systemic tune process.
Go here:
Tuning Process Instructions
Or here:
Methodic Configurator

Thank you so much! Just one last question: one of my theories in the beginning is that the FC thought it had crashed because of the oscilations but I couldn’t find any messages or errors. So, am I right in assuming that the “Crash Detector” did not go off? Thanks!

It did not. After the failure the craft rolled over ~125 deg and at ~5M altitude logging stopped before it hit the ground. Not sure why that is.