Servers by jDrones

Hexacopter fall down in flight, log analisys

Hi, Hallo everyone. I hope some experience user of pixhawk and ardupilot software in generell can help me, because I try to analyze logs from my last flight, but its for me first time - I try to analyze logs - and I’m a litlle bit lost. I was flying my hexacopter with pixhawk 3.5.4 few minuts. It was maybe one of 100 prevoius succesfull flights. But this time copter fall down imediatelly right before landing, when it was 5 meters above landing point. It was looking like it was in stabilize mode with throttle puiling fast full down, mators are stops and copter fall into ground. But I was in POSHOLD mode. Damages are not big (broken landing gear and camera gimbal), but I can’t find out was what the reason for that. After bringing copter back home I armed motors withouts problems and raised throttle as well a little bit. So after repairing I will be possible to fly again, but I will not do that before find out whats was the reason for above problem. I flying mostly BVLOS with expensiv FLIR cameras and in full dark night, above homes, forest and wather , with heavy 22000mAh lipo, so I “happy” that copter fall down right before landing, and not 1km away from me above homes or wather, or deep forest. So can experience ardupilot user have please look on my logs to find out whats I can’t see ? To maybe find reason of this fall down.
Many thanks in a dvance for help !

here link for logs
https://drive.google.com/file/d/1e9FPadsTofzeeEUzku2MoeDIfBnooXb8/view?usp=sharing

The log ends abruptly with the barometer showing ~65m. No indication of why. Your Z-vibration levels are high and you are running a very old version of Arducopter.

Hi, many thanx for answer. Yes I flu at about 65 m, then I go back home, it takes maybe 40 sec, then go down to about 5m , stay a while and suddenly copter fall down as throttle was cut down. I will update to new version but Im still wandering how it was possible and whatscexactly happend.

With the log truncating at 65m hard to say.

The usual cause of this type of truncation of the log would be a power disruption of some sort.

When was the last time you did a service overhaul during your 100 flights ?
I would be checking ALL power connections.
The other possibility is a Flight Controller firmware crash due to bad sensor connections.

But as @Dave points out, we can only give you educated guesses.

Hi, many thanks for answer. Yes You are right, after 100 flights (it was reayl something about 100 flights, each about 20 min) I should perform some big check. I checked main connection before every flight, but to check every connection I have to disassembly drone. And exactly that I’m starting to do. I starting disassembly completely everything , to have empty frame only. And then I will assembly everything back and check all connection and as well soldering , and I will test whole frame (after uploading new firmware) without any additionall expensive equipment as VTX, FLIR cameras, gimbals a.s.o. I will inform if I will found some connection problems or similar, or any others things which can cause fall down.
many thanks for help and logs analysis !!!

Hi. I disassembled already now hexacopter to single parts. Realy silgle parts. And I found that there was problem with power module. Power module simply don’t outputs 5V. I can’t see on power module any problem, no poor soldering a.s.o. Even under magnifier glass. I have second , the same power module, so its simply to compare - one (from my drone) don’t output 5V, Completely NULL on both pins. Of course I had backup power (5VBEC) connected as well to servo rail + Zener Diode. And because of that after falling down, pixhawk was workink. But Im wondering why - when power module failed - pixhawk restart (I assume) instated of taking power from BEC. And why all logs ends on 65m ? when after crash everything looks as working normaly ?

Servers by jDrones