According to the data, the motors were on until 92 Seconds. That does not mean however that they were spinning. Would need the .dat file from the AC to see that.
Crash while using Litchi
- Thread starter Phantomndmore
- Start date
- Joined
- Jun 14, 2016
- Messages
- 1,744
- Reaction score
- 791
- Age
- 65
RodPad
Premium Pilot
Phantom was still powered on?
BTW, .dat file to large to upload here, you will need to uploaded it to a Dropbox, Googledrive, Onedrve, etc.
Rod
Last edited:
The Phantom has produces 2x .dat files both with the same time, one 111mb one 6.43mb. which one is it?
That's not going to work. I need the original DAT. DJIlogs will not do a comprehensive decode.
RodPad
Premium Pilot
The log file reads like a really bad nightmare. I cannot untangle the series of events but, if you consider the entire power up, which was more than one motor start and takeoff, things started to go bad very early on. At 18 s (during the first flight) the GPS stops reporting with an update rate error. The GPS time and location never changes after that, even though the IMU apparently continues to try to update position. At 273 s, during the second flight, the IMU stops reporting position and at 275 s all IMU reporting seems to end.
Looking at the end of the data stream shows the motor behavior. The motors simply spool down when the IMU quits, resulting in an uncontrolled descent with the motors idling.
I've never seen anything quite like that - the IMU operating system looks like it simply froze. The final log status entries make sad reading. The final line is particularly potent.
251.058 : 21556 [Ctrl<3>] REQ_NAVI_MISSION NAVI_WP_MISSION ctrl_navi_waypoint_mission
251.120 : 21559 WP Mission: received idle vel cmd 5.600000 from app
251.120 : 21559 WP Mission: ack idle vel 0 to app
252.258 : 21616 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
252.680 : 21637 WP Mission: received idle vel cmd 5.600000 from app
252.680 : 21637 WP Mission: ack idle vel 234 to app
258.233 : 21914 gps update rate err
258.258 : 21916 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
260.258 : 22016 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
261.258 : 22066 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
265.258 : 22266 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
266.258 : 22316 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
267.258 : 22366 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
268.233 : 22414 gps update rate err
270.258 : 22516 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
271.258 : 22566 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
273.958 : 22701 [Ctrl<12>] REQ_AIRPORT_LIMIT AUTO_LANDING_HOLD ctrl_auto_landing
274.138 : 22710 [LED] changed: fly limit,eg:airport
274.258 : 22716 [Ctrl<12>] REQ_AIRPORT_LIMIT AUTO_LANDING ctrl_auto_landing
277.158 : 22861 [LED] changed: no atti
278.233 : 22914 gps update rate err
279.138 : 22960 [M. Stop]ACT.landing
279.138 : 22960 Motor Start 2 Total 125.90
279.138 : 22960 CTRL reset all by motor stopped
279.138 : 22960 [ACT.msg] ACT_AUTO_LANDING can't exec auto-landing while motor off
Looking at the end of the data stream shows the motor behavior. The motors simply spool down when the IMU quits, resulting in an uncontrolled descent with the motors idling.
I've never seen anything quite like that - the IMU operating system looks like it simply froze. The final log status entries make sad reading. The final line is particularly potent.
251.058 : 21556 [Ctrl<3>] REQ_NAVI_MISSION NAVI_WP_MISSION ctrl_navi_waypoint_mission
251.120 : 21559 WP Mission: received idle vel cmd 5.600000 from app
251.120 : 21559 WP Mission: ack idle vel 0 to app
252.258 : 21616 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
252.680 : 21637 WP Mission: received idle vel cmd 5.600000 from app
252.680 : 21637 WP Mission: ack idle vel 234 to app
258.233 : 21914 gps update rate err
258.258 : 21916 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
260.258 : 22016 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
261.258 : 22066 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
265.258 : 22266 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
266.258 : 22316 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
267.258 : 22366 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
268.233 : 22414 gps update rate err
270.258 : 22516 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
271.258 : 22566 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing
273.958 : 22701 [Ctrl<12>] REQ_AIRPORT_LIMIT AUTO_LANDING_HOLD ctrl_auto_landing
274.138 : 22710 [LED] changed: fly limit,eg:airport
274.258 : 22716 [Ctrl<12>] REQ_AIRPORT_LIMIT AUTO_LANDING ctrl_auto_landing
277.158 : 22861 [LED] changed: no atti
278.233 : 22914 gps update rate err
279.138 : 22960 [M. Stop]ACT.landing
279.138 : 22960 Motor Start 2 Total 125.90
279.138 : 22960 CTRL reset all by motor stopped
279.138 : 22960 [ACT.msg] ACT_AUTO_LANDING can't exec auto-landing while motor off
So much went wrong it's difficult to be sure what caused it. The IMU looks like it failed, but so did the GPS, and those are separate components.
Yeah, this is a strange one. I can add some more but it doesn't get us any closer to knowing what happened. At 275 secs the smoothed barometer data stopped being computed but the raw barometer data continued being logged (as was the accelZ data). It's like the FC decided to quit computing the smooth barometer values but nothing was said about this in the eventLog stream.
Notice the high negative accelZ about 10 secs later. Probably due to the impact when it hit those brambles.
Notice the high negative accelZ about 10 secs later. Probably due to the impact when it hit those brambles.
RodPad
Premium Pilot
@Phantomndmore, I thinking you should do some test flights low to the ground with DJI-GO, (If want to have a claim with DJI). Post a few more logs. Another thought, you still older flights on the Phantom, there maybe some information in those?
Rod
Rod
I think that’s the way to go now. Will carry out a few low to ground test flights once the rain/snow stops! Meanwhile I’ll post the .dat files from successful flights in days before crash.
Similar threads
