Crashed spark after this message: Warning! Not Enough Force/ESC Error

[RobUSA]

If you upload the Flight Data from the Spark, will this data let you know the exact ESC that is giving this ESC Error? And if this data tells you which ESC gave the error, will DJI let you know what ESC has failed?

Is there any other way to get the Flight Data interpreted or is DJI the only option?

I do have the flight record, and here is the part that shows what happened after I decided to do a return home. (there was No emergency when I did a RTH, just returned to home to make it easy for me to get back)

L 04m 04s 655.8 ft 1,943 ft Mode Mode changed to Go_Home

N 04m 15s 636.8 ft 1,631 ft Warning Not Enough Force/ESC Error (repeated 8 times)

04m 17s 632.5 ft 1,592 ft 70% Battery

O 04m 22s 614.2 ft 1,437 ft Warning Speed Error (repeated 2 times)

P 04m 26s 584.6 ft 1,339 ft Warning Compass Error (repeated 50 times)


thank you, Robert.

 

[RobUSA]

Where are error or warning messages stored?

I was told they could be found in the DJI Go App. but was never told how to see them using this APP.

can somebody please help.

 

[Dronason]

Hi and welcome

Error message are in the flight log from the Go4 app.
See DJI Flight Log Viewer

There is also some more detailled flight record stored in the Spark than can be retrieved using DJI assistant 2, but they self deleted as you fly more. So it is usually needed to retrieve them directly after an issue.

You can see also DJI Spark Accessories & Tips - Spark Help
This is the bible of info about DJI drones.

 

[RobUSA]

Hi and welcome

Error message are in the flight log from the Go4 app.
See DJI Flight Log Viewer

There is also some more detailled flight record stored in the Spark than can be retrieved using DJI assistant 2, but they self deleted as you fly more. So it is usually needed to retrieve them directly after an issue.

You can see also DJI Spark Accessories & Tips - Spark Help
This is the bible of info about DJI drones.

can you tell me what part needs to be replaced based on this test flight I made in my back yard. Never went above 20 feet high and it crashed within 2 minutes.

64.382 : 13388 [L-FMU/MOTOR]safe_near_grd:true

65.531 : 13445 [L-FMU/FSM]near ground

65.680 : 13452 [L-API]call cmd_handler_get_device_pos_info pos:1 [0,0] time:1[1530378240] net:0

67.891 : 13563 [L-FMU/FSM]not near ground

69.782 : 13658 [L-FMU/MOTOR]safe_near_grd:false

75.680 : 13952 [L-API]call cmd_handler_get_device_pos_info pos:1 [0,0] time:1[1530378250] net:0

78.999 : 14118 [L-ESC]ESC3 link down||

79.001 : 14119 [L-FMU/MOTOR]esc err, status:0

79.001 : 14119 [L-FMU/MOTOR]fault on , esc(4) is disconnect

79.051 : 14121 [L-ESC]ESC0 link down||

79.060 : 14122 [L-FMU/MOTOR]fault on , esc(1) is disconnect

79.063 : 14122 [L-FDI][CTRL]: fault on , tilt_ctrl_fail

79.064 : 14122 [L-ESC]ESC1 link down||

79.080 : 14123 [L-FMU/MOTOR]fault on , esc(2) is disconnect

79.082 : 14123 [L-RC]craft ctrl failed!!!

79.117 : 14124 [L-ESC]ESC2 link down||

79.120 : 14125 [L-FMU/MOTOR]fault on , esc(3) is disconnect

79.143 : 14126 [L-FMU/LED]action changed. sys error:esc error!(18)

79.259 : 14131 [L-NS] [AHRS] gyro mag inconsist on

79.343 : 14136 [L-FDI][CTRL]: fault off, tilt_ctrl_fail

79.485 : 14143 [L-FDI][CTRL]: fault on , tilt_ctrl_fail

79.544 : 14146 [L-ESC]ESC0 link up||

79.561 : 14147 [L-FMU/MOTOR]fault off, esc(1) is disconnect

79.701 : 14154 [L-FMU/FSM]near ground

79.703 : 14154 [L-FDI][CTRL]: fault on , impact_in_air

79.723 : 14155 [L-FDI][CTRL]: fault off, impact_in_air

79.759 : 14156 [L-FDI]NS(0) GYRO(0): fault on , stuck

79.761 : 14157 [L-FDI][IMU] gyro acc 0 err status 2080

79.781 : 14158 [L-FDI]ns req:fdi,0to0,reason:gyr.stuck,result:fail for same index

79.803 : 14159 [L-FDI][CTRL]: fault off, tilt_ctrl_fail

79.943 : 14166 [L-FMU/LED]action changed. imu error:gyro_acc_error(1)

80.191 : 14178 [L-ESC]ESC3 link up||

80.194 : 14178 [L-FDI]NS(0) GYRO(0): fault off, stuck

80.196 : 14178 [L-FDI][IMU] gyro acc 0 err status 2000

80.200 : 14179 [L-FMU/MOTOR]fault off, esc(4) is disconnect

80.223 : 14180 [L-FDI][CTRL]: fault on , tilt_ctrl_fail

80.283 : 14183 [L-FDI][CTRL]: fault off, tilt_ctrl_fail

80.343 : 14186 [L-FMU/LED]action changed. sys error:esc error!(18)

80.443 : 14191 [L-FMU/MOTOR]safe_near_grd:true

80.503 : 14194 [L-FDI][CTRL]: fault on , tilt_ctrl_fail

80.522 : 14195 [L-FMU/MOTOR] Stop. reason:roll over or atti fail

 

[Dronason]

can you tell me what part needs to be replaced based on this test flight I made in my back yard. Never went above 20 feet high and it crashed within 2 minutes.

64.382 : 13388 [L-FMU/MOTOR]safe_near_grd:true
...
80.522 : 14195 [L-FMU/MOTOR] Stop. reason:roll over or atti fail

Impossible to say for me. Can you post the flight log file as described in DJI Flight Log Viewer and post the link to it? That would help to have some background info.

It is also not sure it is sufficient info to give any diagnostic. Maybe it could require to retrieve the flight record from inside the Spark, which need to use the DJI assistant 2 software..

 

[RobUSA]

Impossible to say for me. Can you post the flight log file as described in DJI Flight Log Viewer and post the link to it? That would help to have some background info.

It is also not sure it is sufficient info to give any diagnostic. Maybe it could require to retrieve the flight record from inside the Spark, which need to use the DJI assistant 2 software..

i did a Firmware Refresh and that fixed it. So it was a corrupted firmware.

 

[Dronason]

i did a Firmware Refresh and that fixed it. So it was a corrupted firmware.

Good news, thanks for sharing.

 

[Texas Gonzo]

Was that 600+ ft your altitude btw?!