Hi,

I have recently had a crash with my Phantom and was looking at the flight logs and wanted to see if anyone can help interpret what some of the codes may be. To hopefully identify a cause. (As its a workplace incident I have to do up a report on the incident.

This code came up multiple times on the day of the crash.  
[L-FMU/MOTOR]failed to set motor force flag

Looking through my DAT file. the Motor ESC temps. my Front Left motor was running 12units higher than the other 3 motors.

---

-66.418 : {root}INFO:lib_route_init ok
-66.418 : {root}INFO:link_host_init ok.||
-66.418 : {root}INFO:link_init <0> link_host, ret(0x0)||
-66.418 : {root}INFO:link_init <1> link_pc, ret(0x0)||
-66.418 : {root}INFO:link_init <2> link_vo, ret(0x0)||
-66.418 : {root}INFO:link_init <3> link_ap, ret(0x0)||
-66.418 : {root}INFO:link_init <4> link_sdk, ret(0x0)||
-66.418 : {root}INFO:link_init <5> link_ofdm, ret(0x0)||
-66.418 : {root}INFO:link_init <6> link_auto_cali, ret(0x0)||
-66.418 : {root}INFO:link_init <7> link_manual_cali, ret(0x0)||
-66.417 : {root}INFO:link_init <8> link_cali_led, ret(0x0)||
-66.417 :       0 [L-SENSOR][ASR]sync host lead offset 0x11a||
-66.417 : {root}INFO:[panic]:******************check fault info and trace(0) ************||
-66.417 : {root}INFO:[panic]:-----fault info is null: addr(0x2045e800),flag(0x1a840708)-----||
-66.417 : {root}INFO:[panic]:-----fault info is null: addr(0x2045e938),flag(0x8cf29939)-----||
-66.417 : {root}INFO:[panic]:-----all task info  is null: addr(0x2045ea70),flag(0xa9db5633)-----||
-66.417 : {root}INFO:[panic]:-----trace info  is null: addr(0x2045f260),flag(0x8f62662c)-----||
-66.417 : {root}INFO:[panic]:******************check last trace ******************||
-66.417 : {root}INFO:[panic]:-----trace info  is null: addr(0x2045eca0),flag(0xa0e33529)-----||
-66.417 :       0 [L-SENSOR][ASR]asr host sync start
-66.417 : {root}INFO:[panic]:-----wdg_time_info is null: addr(0x2045f820),flag(0x51f10521)-----||
-65.237 :       0 [L-SENSOR] hw_ver voltage: 0
-64.318 :       0 [L-SIM]read parameter successfully!
-64.304 :       0 [L-FMU/MOTOR]read motor force disable flag successfully!
-64.304 :       0 [L-FMU/DM]success reg dev type  3(A3), id:2, total num:2
-64.274 :       0 [L-SENSOR][ASR]need re sync host load_offset, freq=0x190||
-64.274 :       0 [L-SENSOR][ASR]need re sync host load_offset, freq=0x190||
-64.274 :       0 [L-SENSOR][ASR]need re sync host load_offset, freq=0x190||
-4.663 :    2971 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
-4.663 :    2971 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02
-4.663 :    2971 [L-FMU/MOTOR]failed to set motor force flag
-4.595 :    2975 [L-EMBEDDED]Eeprom write offset:9f0||
-.018 :    3204 [L-RC]rc cmd:STD_ASSI_TAKEOFF
.000 :    3205 [L-FMU/MOTOR]Start. reason:REQ_RC_NORMAL
.000 :    3205 [L-PWM]set actuator mode:CTRL
.001 :    3205 [L-FMU/FSM]state changed. cur: on ground
.002 :    3205 [L-FLYMODE][Ctrl<2>] REQ_RC_COMMAND ENGINE_START ctrl_engine_start
.002 :    3205 [L-FDI]tilt when motor on = 0.015409, static flag = 1
.017 :    3206 [L-IMU]set imu switch level = 8
.020 :    3206 [L-IOC]Set CL. -103.2 Degree
.020 :    3206 [L-TAKEOFF]alti: 344.791473 tors: -103.197357
1.542 :    3282 [L-FLYMODE][Ctrl<2>] REQ_RC_COMMAND ASST_TAKEOFF ctrl_asst_takeoff
3.231 :    3366 [L-FMU/FSM]state changed. cur: in air
3.240 :    3367 [L-HOME]Update. lati:-23.9219281 longti:148.0425330 alti:364.79
3.242 :    3367 [L-FLYMODE]CTRL reset all by assisted takeoff finish
3.242 :    3367 [L-FDI][FDI CTRL] event: impact turn on
3.243 :    3367 [L-FDI][FDI CTRL] event: height turn on
3.243 :    3367 [L-FDI][FDI CTRL] event: tilt turn on
3.243 :    3367 [L-FDI][FDI CTRL] event: head turn on
3.243 :    3367 [L-FDI][FDI CTRL] event: random fly turn on
3.245 :    3367 [L-FDI][FDI CTRL] event: fly away turn on
3.245 :    3367 [L-FDI][FDI CTRL] event: horiz turn on
3.262 :    3368 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
3.622 :    3386 [L-FMU/LED]action changed. set home0)
3.882 :    3399 [L-RC]Emergency break. rc vib!
4.359 :    3423 [L-NS][AHRS]height max obv num [3/16]
5.484 :    3479 [L-NS][AHRS] yaw aligned 1
5.722 :    3491 [L-FMU/LED]action changed. Normal Flash(0)
5.722 :    3491 [L-FMU/LED]type:0, normal flash action:
5.722 :    3491 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
6.686 :    3539 [L-FMU/FSM]not near ground
6.702 :    3540 [L-FMU/MOTOR]safe_near_grd:false
8.037 :    3606 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
8.037 :    3606 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02
8.037 :    3606 [L-FMU/MOTOR]failed to set motor force flag
8.057 :    3607 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
8.057 :    3607 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02
8.057 :    3607 [L-FMU/MOTOR]failed to set motor force flag
8.057 :    3607 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
8.057 :    3607 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02
8.077 :    3608 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
8.077 :    3608 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02
8.077 :    3608 [L-FMU/MOTOR]failed to set motor force flag
8.077 :    3608 [L-FMU/MOTOR]failed to set motor force flag
8.097 :    3609 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
8.097 :    3609 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02
8.097 :    3609 [L-FMU/MOTOR]failed to set motor force flag
10.237 :    3716 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
10.237 :    3716 [L-CFG]write g_config.device.is_locked(0.000000) by hash sender:0x02

---

For me, I'm under the impression this was a hardware failure mid-flight which caused it to crash.

Try uploading your log here http://phantomhelp.com/logviewer/

Those entries in the eventLog stream are common and probably unrelated to the incident cause. If you could DropBox the .DAT I'll take a look.

BudWalker Posted at 12-22 08:32
Those entries in the eventLog stream are common and probably unrelated to the incident cause. If you could DropBox the .DAT I'll take a look.

Thanks, I have uploaded the DAT file to the following location.
https://www.dropbox.com/s/r734dlyq732wkba/2020-12-18_12-18-16_FLY036.DAT?dl=0

TheSamus Posted at 12-22 12:24
Thanks, I have uploaded the DAT file to the following location.
https://www.dropbox.com/s/r734dlyq732wkba/2020-12-18_12-18-16_FLY036.DAT?dl=0

The mobile device .DAT ends at 370 secs with negative throttle in effect and having been applied for about 6 secs. Is there another .DAT ending in  FLY036.DAT? If not then we'll need the .DAT from the P4P. Look here to see how to do that http://datfile.net/DatCon/retrieveV3Dat.html

BudWalker Posted at 12-22 14:15
The mobile device .DAT ends at 370 secs with negative throttle in effect and having been applied for about 6 secs. Is there another .DAT ending in  FLY036.DAT? If not then we'll need the .DAT from the P4P. Look here to see how to do that http://datfile.net/DatCon/retrieveV3Dat.html

Thanks for having a look. There aren't any other DAT files ending in 036. and as the AC fell from a decent height onto a Rocky surface it's unable to power up. I can't even access the USB port its that damaged.

TheSamus Posted at 12-22 14:26
Thanks for having a look. There aren't any other DAT files ending in 036. and as the AC fell from a decent height onto a Rocky surface it's unable to power up. I can't even access the USB port its that damaged.

How about the .txt from the mobile device then? Probably won't help much, but you never know for sure.

BudWalker Posted at 12-22 15:21
How about the .txt from the mobile device then? Probably won't help much, but you never know for sure.

The only text file that actually looks like something is this one which is the same as what I copied in the OP.
There is a bunch of other text files that are full of symbols and doesn't look readable.

https://www.dropbox.com/s/0ucysi7wzwm5uaf/2020-12-18_12-18-16_FLY036.log.txt?dl=0

TheSamus Posted at 12-22 16:14
The only text file that actually looks like something is this one which is the same as what I copied in the OP.
There is a bunch of other text files that are full of symbols and doesn't look readable.

That .txt was created by DatCon. The .txt I'm looking for is on the mobile device and is created by the Go App. You're right it's not an actual text file. Take a look at
https://www.phantomhelp.com/logviewer/upload/
to see how to retrieve the .txt log file.

BudWalker Posted at 12-22 17:20
That .txt was created by DatCon. The .txt I'm looking for is on the mobile device and is created by the Go App. You're right it's not an actual text file. Take a look at
https://www.phantomhelp.com/logviewer/upload/
to see how to retrieve the .txt log file.

So I have retrieved the file from that day. When I go to uploaded on Phantomhelp.com it times out every time.
I have saved the text file here.
https://www.dropbox.com/s/oaz6fwtvsr673bb/DJIFlightRecord_2020-12-18_%5B12-18-25%5D.txt?dl=0

TheSamus Posted at 12-22 17:51
So I have retrieved the file from that day. When I go to uploaded on Phantomhelp.com it times out every time.
I have saved the text file here.
https://www.dropbox.com/s/oaz6fwtvsr673bb/DJIFlightRecord_2020-12-18_%5B12-18-25%5D.txt?dl=0

That's the right one. I've heard that the phantomhelp site is having some problems today.

Looks to me like you're using a non-standard control stick mode? Throttle and pitch are swapped and roll and aileron are swapped. As I mentioned above the P4P was recieving a negative throttle at the end. Maybe you were meaning to give it positive pitch to back it towards you but instead negative throttle was being given.

Is there a FLY037.DAT?

BudWalker Posted at 12-22 18:10
That's the right one. I've heard that the phantomhelp site is having some problems today.

Looks to me like you're using a non-standard control stick mode? Throttle and pitch are swapped and roll and aileron are swapped. As I mentioned above the P4P was recieving a negative throttle at the end. Maybe you were meaning to give it positive pitch to back it towards you but instead negative throttle was being given.

Yeah, I'm a bit backwards and actually like mode 1 haha. Its the layout I started on 4 years ago and just stuck with it ever since. Was a slow sweeping corner along a flight path I do every single day each week.
Just this time it was flying along like normal and disconnected and never reconnected. Assumed it should have activated its RTH, but it never did an just fell.

There aren't any Fly037.DAT files.

TheSamus Posted at 12-22 18:30
Yeah, I'm a bit backwards and actually like mode 1 haha. Its the layout I started on 4 years ago and just stuck with it ever since. Was a slow sweeping corner along a flight path I do every single day each week.
Just this time it was flying along like normal and disconnected and never reconnected. Assumed it should have activated its RTH, but it never did an just fell.

Actually I was supposing that you normally flew mode 2 and that mode 1 was unfamiliar to you. If that were the case then you may have pulling back on the right stick ithinking the AC would be flying backwards towards you. Instead, since mode 1 was in effect, it was the throttle being pulled back. The throttle was negative during the last 8 secs of the recorded .DAT and that could have continued if the uplink was intact.

Hello there TheSamus. I am sorry for the trouble this has caused and thank you for reaching out. Since your Phantom 4 Pro had crashed before. It would be best to contact our DJI support team at https://www.dji.com/support?site=brandsite&from=nav for further assistance. We have a team that will do there best to check what happened to the said drone and will give out the best resolution for this issue. Again, I am sorry for the trouble and thank you for your understanding.

Hi Guys, I cant find a A3 / A3P help thread but i need VERY URGENT help for interprating a datfile from a crashed X8 Copter. is anyone willing to help?
br philipp