How to identify which motor cause the ESC error?

Joined
Jul 25, 2017
Messages
2
Reaction score
0
Age
42
I got two 2 phantom adv. Both got same "ESC error"
I managed to fixed one by replaced all 4 motors and problem solved.
The cause of the problem was the long screw (from motor base Reinforcement" )damage the motor wire inside.

However for the 2nd drone instead of replacing the whole motor I want to fix specific motor.
I did an investigation through the log file (FLYXXX.DAT) on the mainboard using the CsvView/DatCon

and here is the result of log message
1.745 : 1047 : 0 IST8303[2:0x18]:Init...
1.750 : 1050 : 0 IST8303[2:0x18]:set mode failed
1.750 : 1050 : 0 ist83xx:0 ret:-14
1.750 : 1050 : 0 IST8303[2:0x1e]:Init...
1.755 : 1053 : 0 IST8303[2:0x1e]:set mode failed
1.755 : 1053 : 0 ist83xx:1 ret:-14
2.265 : 1359 : 0 ms5607:0 ret:0 spi_id:0 init ok
2.662 : 1597 : 0 [BAT]read barcode data success num:1
2.662 : 1597 : 0 [BAT]read begin:12211232.end:12345678
2.662 : 1597 : 0 [BAT]barcode[0]:6171152308289
2.710 : 1626 : 0 eeprom load 0 0 22 32
2.745 : 1647 : 0 eeprom load 1 32 28 32
2.782 : 1669 : 0 eeprom load 2 64 34 40
2.835 : 1701 : 0 eeprom load 3 104 20 24
2.870 : 1722 : 0 eeprom load 4 128 132 136
2.978 : 1787 : 0 eeprom load 5 264 128 136
3.085 : 1851 : 0 eeprom load 6 400 12 16
3.120 : 1872 : 0 eeprom load 7 416 40 48
3.173 : 1904 : 0 eeprom load 8 464 11 16
3.208 : 1925 : 0 eeprom load 9 480 1 8
3.243 : 1946 : 0 eeprom load 10 488 6 16
3.280 : 1968 : 0 eeprom load 11 504 4 8
3.315 : 1989 : 0 eeprom load 12 512 52 56
3.368 : 2021 : 0 eeprom load 13 568 8 16
3.403 : 2042 : 0 eeprom load 14 584 7 16
3.438 : 2063 : 0 eeprom load 15 600 12 16
3.492 : 2095 : 0 eeprom load 16 616 38 48
3.545 : 2127 : 0 eeprom load 17 664 12 16
3.598 : 2159 : 0 eeprom load 18 680 56 64
3.652 : 2191 : 0 eeprom load 19 744 32 40
3.705 : 2223 : 0 eeprom load 20 784 1 8
3.740 : 2244 : 0 eeprom load 21 792 16 24
3.793 : 2276 : 0 eeprom load 22 816 16 24
3.828 : 2297 : 0 eeprom load 23 840 1 8
3.863 : 2318 : 0 eeprom load 24 848 1 8
3.898 : 2339 : 0 eeprom load 25 856 10 16
3.952 : 2371 : 0 eeprom load 26 872 36 40
4.005 : 2403 : 0 eeprom load 27 912 52 56
4.077 : 2446 : 0 eeprom load 28 968 44 48
4.130 : 2478 : 0 eeprom load 29 1016 28 32
4.183 : 2510 : 0 eeprom load 30 1048 18 24
4.237 : 2542 : 0 eeprom load 31 1072 16 24
4.272 : 2563 : 0 eeprom load 32 1096 72 80
4.342 : 2605 : 0 eeprom load 33 1176 24 32
4.395 : 2637 : 0 eeprom load 34 1208 64 72
4.467 : 2680 : 0 eeprom load 35 1280 24 32
4.503 : 2702 : 0 eeprom load 36 1312 96 104
4.685 : 2811 : 0 mis cali 55 55 883e fff0 cnt:0
4.685 : 2811 : 0 imu status:0
4.685 : 2811 : 0 [hardfault]:******************check fault info and trace ************
4.685 : 2811 : 0 [hardfault]:-----fault is null: addr(0x40024000),flag(0x89dd0a51)-----
4.685 : 2811 : 0 [hardfault]:-----fault is null: addr(0x400241a0),flag(0x11548af3)-----
4.685 : 2811 : 0 [hardfault]:-----task info is null: addr(0x40024340),flag(0x43829cff)-----
4.685 : 2811 : 0 [hardfault]:-----trace info is null: addr(0x400244d0),flag(0xa5ed89fb)-----
4.685 : 2811 : 0 [hardfault]:******************check last trace ******************
4.685 : 2811 : 0 [hardfault]:-----trace info is null: addr(0x40024790),flag(0xbc0e61cc)-----
4.685 : 2811 : 0 [hardfault]:-----wdg_time_info is null: addr(0x40024a50),flag(0x49d57182)-----
4.685 : 2811 : 0 startup:4.582611||
4.685 : 2811 : 0 Board:"wm320v2"
4.705 : 2823 : 1 airport limit inited[1]
4.705 : 2823 : 1 compass calibration init!
4.705 : 2823 : 1 [LED] changed: test led when startup
4.705 : 2823 : 1 app connect changed:last(255) != current(0)
4.705 : 2823 : 1 assistant connect changed:last(255) != current(0)
4.705 : 2823 : 1 [FDI MAGN[1]] event:turn on
4.705 : 2823 : 1 [FDI GYRO[1]] event:turn on
4.705 : 2823 : 1 [FDI ACC[1]] event:turn on
4.707 : 2824 : 1 [FDI BARO[1]] event:turn on
4.707 : 2824 : 1 [FDI AHRS[1]]:turn on
4.707 : 2824 : 1 [FDI CTRL] event: turn on
4.708 : 2825 : 1 temp cali (0.000000,0.000000) 0 fw:4 4||
4.708 : 2825 : 1 temp cali 0 bw:0.000000 0.000000 0.000000 ba:0.000000 0.000000 0.000000||
4.708 : 2825 : 1 app temp cali (52.000000,65.000000) aa fw:6 6||
4.708 : 2825 : 1 app temp cali aa bw:0.000294 -0.000458 0.000216 ba:0.000283 -0.000006 0.000006||
4.708 : 2825 : 1 read gps date:20170725
4.767 : 2860 : 4 [esc_is_stall] status changed: last(0xffffffff) != current(0x00000000)
4.767 : 2860 : 4 [esc_is_empty] status changed: last(0xffffffff) != current(0x00000000)
4.885 : 2931 : 10 [FDI GPS[1]] event:turn on
5.017 : 3010 : 16 ESC0 link up||
5.028 : 3017 : 17 ESC1 link up||
5.040 : 3024 : 17 ESC2 link up||
5.052 : 3031 : 18 ESC3 link up||
5.052 : 3031 : 18 esc alive info = 0xf||
6.017 : 3610 : 66 ESC0 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
6.017 : 3610 : 66 Loader = [V01.00.02.02]
6.017 : 3610 : 66 Firmware = [V01.12.00.00] ||
6.025 : 3615 : 66 ESC1 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
6.025 : 3615 : 66 Loader = [V01.00.02.02]
6.025 : 3615 : 66 Firmware = [V01.12.00.00] ||
6.027 : 3616 : 67 [Err] OFDM_TX State:0x00000008
6.033 : 3620 : 67 ESC2 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
6.033 : 3620 : 67 Loader = [V01.00.02.02]
6.033 : 3620 : 67 Firmware = [V01.12.00.00] ||
6.042 : 3625 : 67 ESC3 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
6.042 : 3625 : 67 Loader = [V01.00.02.02]
6.042 : 3625 : 67 Firmware = [V01.12.00.00] ||
6.268 : 3761 : 79 Eeprom write offset:0||
6.385 : 3831 : 85 Battery barcode:6171160335728
6.405 : 3843 : 86 Battery barcode:6171160335728
6.425 : 3855 : 87 Battery barcode:6171160335728
6.710 : 4026 : 101 [FDI AHRS[1]]:ahrs_init begin
6.725 : 4035 : 102 [FDI AHRS[1]]:bias fdi turn on
6.725 : 4035 : 102 [FDI AHRS[1]]:init fdi turn on
6.725 : 4035 : 102 [FDI AHRS[1]]:wait for sensor check
6.905 : 4143 : 111 [LED] changed: temperature not ready when startup
7.085 : 4251 : 120 Battery name :ATL NVT DJ005.||
7.085 : 4251 : 120 manufacture Date:2016/2/11||
7.085 : 4251 : 120 Serial number :1193||
7.785 : 4671 : 155 old.IOC reset intelligence_orientation_enabled
7.785 : 4671 : 155 [BATTERY]:reset default smart cfg - L1:1 L2:2
7.785 : 4671 : 155 [smart_battery]this fireware calc gohme speed:7.800000 - land speed:2.500000||
7.785 : 4671 : 155 CTRL reset all by rc mode switch
7.785 : 4671 : 155 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
7.907 : 4744 : 161 Eeprom write offset:1d0||
8.345 : 5007 : 183 [LED] changed: no atti
10.645 : 6387 : 297 [FDI AHRS[1]]:ahrs_init pass
10.645 : 6387 : 298 [FDI AHRS[1]]:evaluation fdi turn on
10.745 : 6447 : 303 [LED] changed: temperature not ready when startup
39.298 : 23579 : 1730 Eeprom write offset:0||
58.303 : 34982 : 2680 Eeprom write offset:0||
86.105 : 51663 : 4071 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
86.485 : 51891 : 4090 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
88.805 : 53283 : 4206 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
101.465 : 60879 : 4839 [LED] changed: rc completely lost
225.278 : 135167 : 11029 Eeprom write offset:0||
287.025 : 172215 : 14117 [Err] OFDM_TX State:0x00000408
288.607 : 173164 : 14196 [Err] OFDM_TX State:0x00000008
288.662 : 173197 : 14198 Eeprom write offset:0||
289.665 : 173799 : 14249 [LED] changed: compass out of range
293.045 : 175827 : 14418 app connect changed:last(0) != current(1)


Which part of the log message can tell me which motor caused the ESC error?
Is there anyway to indentify the which motor case the problem?
I don't want to replace the whole set of motor without any pin point Identification.

THank you
 
Are you able to turn on the motors? If yes, then you will be able to identify which one is not rotating correctly.
 
Are you able to turn on the motors? If yes, then you will be able to identify which one is not rotating correctly.
Wow Ok I'm just going to elaborate because I HAVE THE PRECISELY EXACT PROBLEM AS HIM but no I'm not able to turn my motors so is there any way of identifying which motor it is needs repairing ?
 
No motor spin at all. Again
Is there any way of identifying which motor it is needs repairing ?
 
It's not that easy Togo d out which motor has burned out as there are chances that even ESC also got burned.

If you know which prop broke, then you can probably figure out which motor esc combo is giving error.
 
Assuming the ESCs are numbered the same as the arms, ESC1 should be controlling the front left motor.

Have you had a look at the ESCs? it might be written on the PCB somewhere...
 
If you have the lid off the AC grab a multimeter and measure DCR between gate and drain on the ESC mosfets- this is a very common failure mode (they short).

More likely to be a cooked mainboard than a motor problem (absent the driving a screw into the stator field windings).
 

Members online

No members online now.

Forum statistics

Threads
143,054
Messages
1,467,297
Members
104,919
Latest member
BobDan