Copter instantly released itself from 30m

I am using Copter 4.0.3 and Pixhawk 2.4.8. I have flown 10+ times with same setup just having land detection issues. But this time, copter started falling from 30 meter altitude and I observed no reaction at all. I saw these messages,
-EKF primary changed:1
-EKF primary changed:0
-EKF variance
-GPS Glitch
-Potential Thrust Loss (3)

I am having hard times to figure out what caused the suicide. I am attaching flashlogs if any of you curious to help out!
Thanks in advance.

Potential Thrust Loss means that one or more motors stoped working. Check your hardware.

It looks like a faulty/glitching BARO which thrown an EKF switch then a EKF failsafe.

It looks like this error > Barometer glitch inducing EKF primary change

OK, but copter did not perform any failsafe behaviour which was LAND. It just crashed nose down. Something else must be broken?

Indeed, after EKF failsafe copter tried to stay in the air, but event a full throttle to all motors, it kept sinking. And 10 sec before ekf failsafe the vibrations started in increasing causing clipping (saturation) on sensors. It could be a mechanical failure. (Motors were running because the battery voltage slag is consistent with the increased throttle)

1 Like

OK, after failsafe situation was thrown, I observe altitude drop in the logs. Then Throttle maxed out. But there is a subsystem err with no 25.
I found this:

  • Does autopilot shutsdown after this error? Or It just stops recording logs? Because there is no more of logs after error. Can someone light the way?

After Throttle maxed out I see voltage dip which is expected I guess? So motors were running as @Eosbandi confirmes.

I want to ask, is it the reason that copter could not recover from falling because its orientation was too bad even if throttle was maxed? And there was bad output coming from EKF originally resulting false attitude estimation. So that wrong motor outputs may be the reason to flip the copter? I guess I am coming back to vibration errors… :thinking:

I gotta find the main problem in order to fix things, otherwise I will be doing shit and these things will come up again. I hope someone will give me the details that I am missing.

Thanks in advance.

The potential thrust loss error logged almost at the same time when copter impacted the ground,(coincidence) this likely caused power disconnect and this is why the logging stopped. (check IMU, AccX, AccY and AccZ you can see the impact caused about 9G deceleration on the Z axis… )

There is a conflict I guess. Because logging stop when the vehicle was still on the air at 20m. There is no copter impacting the ground in the logs. Confusing colors, sorry for inconvenience.

The last log of Vbattery is 10.3 Volts

According to GPS alt, it was less than 2 meters relative to the takeoff alt. Based on the accelerometer data is does looks like an impact for me.


You are right. In terms of altitude, while Baro and GPS giving good output, EKF’s Alt is wrong
This is the picture from tlog:

EKF status is severe. I feel like vibrations was the main problem so that pos/vel estimates giving wrong results then causing a fall down somehow.

@rmackay9 Do you think the same? I will appreciate if you show me the direction.

Hi. It is definitely the level of z-vibration, leading to wrong altitude-estimation of EKF.
That is also the reason, why you get GPS-Glitch. I had this with several copters in the past too. The problem will be defintely solved in improved dumping of the FC.



Thank you for your reply. I am dumping the FC tho.
Here I can see Vib in 3 dims are fine during flight but suddenly Vib-Z starts increasing but I think it is not caused by windy conditions or anything affecting the copter that will end up giving more output to the motors. Because I don’t see any increase in CTUN.Tho. I guess there might be a mech failure causing that vib? And maybe that failure throw that Baro Glitch? Is it possible?

This my other setup, not the one that crashed. They are almost the same. I used tapes between surfaces of frame, isolation platform and pixhawk. Pi is located at top. Do you see any issue that would lead to vibration problems?

When I having issues with vibration and cannot tame them with prop balancing, I add 25-50g of lead below the flight controller, on the damped plate.

Plus, forget the hot glue, it get brittle in couple of months and fell off, plus as I see you covered only the solder part of the cable. The issue is that when you tin the cable, the thin goes up, under the insulation, and if you not fixing the flexible not tinned part of the cable, it will break where the tinning ends, under the insulation…

You mean this area or the middle? So Having extra weight will make the plates more steady?

Thank you for advices, I will take those into account!

Nope, you have to make the flight controller more heavy. So put weight directly on the bottom of the flight controller plate.

1 Like