ESC status error

Thanks for "DatCon 2.3.2", so my log is:


new esc board:
Code: 
                41 ESC0 link up
3.740 : 3017 :      42 ESC1 link up
3.752 : 3024 :      42 ESC2 link up
3.763 : 3031 :      43 ESC3 link up
3.763 : 3031 :      43 esc alive info = 0xf
4.728 : 3610 :      91 ESC0 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.728 : 3610 :      91 Loader   = [V00.00.01.01]
4.728 : 3610 :      91 Firmware = [V01.08.00.00]
4.737 : 3615 :      91 ESC1 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.737 : 3615 :      91 Loader   = [V00.00.01.01]
4.737 : 3615 :      91 Firmware = [V01.08.00.00]
4.745 : 3620 :      92 ESC2 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.745 : 3620 :      92 Loader   = [V00.00.01.01]
4.745 : 3620 :      92 Firmware = [V01.08.00.00]
4.753 : 3625 :      92 ESC3 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.753 : 3625 :      92 Loader   = [V00.00.01.01]
4.753 : 3625 :      92 Firmware = [V01.08.00.00]
...
4334 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
89.977 : 54759 :    4354 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
94.937 : 57735 :    4602 [M.Start]REQ_RC_NORMAL FAIL, esc error!
100.717 : 61203 :    4891 [M.Start]REQ_RC_NORMAL FAIL, esc error!
101.997 : 61971 :    4955 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
...

old esc board
Code: 
                59 ESC1 link up
6.595 : 4719 :      60 ESC2 link up
6.607 : 4726 :      61 ESC3 link up
6.607 : 4726 :      61 esc alive info = 0xe
6.638 : 4745 :      62 ESC1 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
6.638 : 4745 :      62 Loader   = [V00.00.01.01]
6.638 : 4745 :      62 Firmware = [V01.10.00.00]
6.647 : 4750 :      63 ESC2 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
6.647 : 4750 :      63 Loader   = [V00.00.01.01]
6.647 : 4750 :      63 Firmware = [V01.10.00.00]
6.655 : 4755 :      63 ESC3 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
6.655 : 4755 :      63 Loader   = [V00.00.01.01]
6.655 : 4755 :      63 Firmware = [V01.10.00.00]
...
   5775 [LED] changed: normal led
152.403 : 92204 :    7351 [M.Start]REQ_RC_NORMAL FAIL, esc error!
160.343 : 96968 :    7748 [M.Start]REQ_RC_NORMAL FAIL, esc error!
...

I have changed for a new esc board and same error !!!, someone can help me with this error ????
 
Its maybe motor or motor conection issue

Comedoo said:
Thanks for "DatCon 2.3.2", so my log is:


new esc board:
Code: 
                41 ESC0 link up
3.740 : 3017 :      42 ESC1 link up
3.752 : 3024 :      42 ESC2 link up
3.763 : 3031 :      43 ESC3 link up
3.763 : 3031 :      43 esc alive info = 0xf
4.728 : 3610 :      91 ESC0 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.728 : 3610 :      91 Loader   = [V00.00.01.01]
4.728 : 3610 :      91 Firmware = [V01.08.00.00]
4.737 : 3615 :      91 ESC1 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.737 : 3615 :      91 Loader   = [V00.00.01.01]
4.737 : 3615 :      91 Firmware = [V01.08.00.00]
4.745 : 3620 :      92 ESC2 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.745 : 3620 :      92 Loader   = [V00.00.01.01]
4.745 : 3620 :      92 Firmware = [V01.08.00.00]
4.753 : 3625 :      92 ESC3 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
4.753 : 3625 :      92 Loader   = [V00.00.01.01]
4.753 : 3625 :      92 Firmware = [V01.08.00.00]
...
4334 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
89.977 : 54759 :    4354 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
94.937 : 57735 :    4602 [M.Start]REQ_RC_NORMAL FAIL, esc error!
100.717 : 61203 :    4891 [M.Start]REQ_RC_NORMAL FAIL, esc error!
101.997 : 61971 :    4955 [Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
...

old esc board
Code: 
                59 ESC1 link up
6.595 : 4719 :      60 ESC2 link up
6.607 : 4726 :      61 ESC3 link up
6.607 : 4726 :      61 esc alive info = 0xe
6.638 : 4745 :      62 ESC1 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
6.638 : 4745 :      62 Loader   = [V00.00.01.01]
6.638 : 4745 :      62 Firmware = [V01.10.00.00]
6.647 : 4750 :      63 ESC2 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
6.647 : 4750 :      63 Loader   = [V00.00.01.01]
6.647 : 4750 :      63 Firmware = [V01.10.00.00]
6.655 : 4755 :      63 ESC3 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
6.655 : 4755 :      63 Loader   = [V00.00.01.01]
6.655 : 4755 :      63 Firmware = [V01.10.00.00]
...
   5775 [LED] changed: normal led
152.403 : 92204 :    7351 [M.Start]REQ_RC_NORMAL FAIL, esc error!
160.343 : 96968 :    7748 [M.Start]REQ_RC_NORMAL FAIL, esc error!
...

I have changed for a new esc board and same error !!!, someone can help me with this error ????
Click to expand...
 
Comedoo said:
I have changed for a new esc board and same error !!!
Click to expand...

Since you can replace the ESC board, I assume you're working with Phantom 4. It's a pity this isn't so easy in Phantom 3.

lukman said:
Its maybe motor or motor conection issue
Click to expand...

Yup, if after changing ESC board the problem still persists - it is most likely motor issue.
The log (both of them) seem to confirm that - it gets into error state during "motor start".
 
quaddamage said:
Since you can replace the ESC board, I assume you're working with Phantom 4. It's a pity this isn't so easy in Phantom 3.



Yup, if after changing ESC board the problem still persists - it is most likely motor issue.
The log (both of them) seem to confirm that - it gets into error state during "motor start".
Click to expand...

I'm working with phantom 3 pro, esc board spare part no 33.
I removed the wires red and black of the motors one by one, to check what motor is burned, in case of motor burned i believe the message should be changed to Motor obstructed, but the motors didn't start and the message still esc status error ...
 
Comedoo said:
I'm working with phantom 3 pro, esc board spare part no 33.
Click to expand...
Oh, I see; so you've replaced all 4 ESCs and a flight controller.

Comedoo said:
I removed the wires red and black of the motors one by one, to check what motor is burned, in case of motor burned i believe the message should be changed to Motor obstructed, but the motors didn't start and the message still esc status error ...
Click to expand...
I don't know anything about the "Motor obstructed" message, I can't confirm nor deny whether it should show.

If you replaced all ESCs and a flight controller, and the issue still persists, then (assuming that the new components don't have the same problem as old ones), the reason must be within motors. That's just the only thing left.
 
droneforumaccount said:
any way of telling which motor may be faulting?
Click to expand...

1. Go through startup and observer all the motors, try to pinpoint the one which behaves differently.
2. Read the flight log. Search for the ESC related messages. Find number of the ESC which has different messages than others (ie. lacks some of the messages, or simply reports error).

If you've pinpoint the ESC number, you can easily locate corresponding motor: ESC0 -> M1 ... ESC3 -> M4.
 
quaddamage said:
1. Go through startup and observer all the motors, try to pinpoint the one which behaves differently.
2. Read the flight log. Search for the ESC related messages. Find number of the ESC which has different messages than others (ie. lacks some of the messages, or simply reports error).

If you've pinpoint the ESC number, you can easily locate corresponding motor: ESC0 -> M1 ... ESC3 -> M4.
Click to expand...


unfortunately the log just spits out a generic esc error and doesn't tell me which is faulting:

2.910 : 2508 : 0 [hardfault]:******************check fault info and trace ************
2.910 : 2508 : 0 [hardfault]:-----fault is null: addr(0x40024000),flag(0x842ed686)-----
2.910 : 2508 : 0 [hardfault]:-----fault is null: addr(0x400241a0),flag(0x87ba5e73)-----
2.910 : 2508 : 0 [hardfault]:-----task info is null: addr(0x40024340),flag(0x63e944c5)-----
2.910 : 2508 : 0 [hardfault]:-----trace info is null: addr(0x400244d0),flag(0x626ad5c3)-----
2.910 : 2508 : 0 [hardfault]:******************check last trace ******************
2.910 : 2508 : 0 [hardfault]:-----trace info is null: addr(0x40024790),flag(0xa1094ab2)-----
2.910 : 2508 : 0 [hardfault]:-----wdg_time_info is null: addr(0x40024a50),flag(0x99c96dac)-----
3.762 : 3019 : 42 ESC0 link up
3.773 : 3026 : 43 ESC1 link up
3.785 : 3033 : 43 ESC2 link up
3.797 : 3040 : 44 ESC3 link up
3.797 : 3040 : 44 esc alive info = 0xf
4.760 : 3618 : 92 ESC0 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.760 : 3618 : 92 Loader = [V01.00.02.02]
4.760 : 3618 : 92 Firmware = [V01.11.00.00]
4.768 : 3623 : 92 ESC1 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.768 : 3623 : 92 Loader = [V01.00.02.02]
4.768 : 3623 : 92 Firmware = [V01.11.00.00]
4.777 : 3628 : 93 ESC2 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.777 : 3628 : 93 Loader = [V01.00.02.02]
4.777 : 3628 : 93 Firmware = [V01.11.00.00]
4.785 : 3633 : 93 ESC3 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.785 : 3633 : 93 Loader = [V01.00.02.02]
4.785 : 3633 : 93 Firmware = [V01.11.00.00]
49.210 : 30288 : 2315 [M.Start]REQ_RC_NORMAL FAIL, esc error!
58.810 : 36048 : 2795 [Ctrl<6>] REQ_APP_WM610 ENGINE_START ctrl_engine_start
58.830 : 36060 : 2796 [M.Start]ACT.Takeoff FAIL, esc error!
58.850 : 36072 : 2797 [M.Start]ACT.Takeoff FAIL, esc error!
58.870 : 36084 : 2798 [M.Start]ACT.Takeoff FAIL, esc error!
58.890 : 36096 : 2799 [M.Start]ACT.Takeoff FAIL, esc error!
58.910 : 36108 : 2800 [M.Start]ACT.Takeoff FAIL, esc error!
58.930 : 36120 : 2801 [M.Start]ACT.Takeoff FAIL, esc error!
58.950 : 36132 : 2802 [M.Start]ACT.Takeoff FAIL, esc error!
58.970 : 36144 : 2803 [M.Start]ACT.Takeoff FAIL, esc error!
58.990 : 36156 : 2804 [M.Start]ACT.Takeoff FAIL, esc error!
59.010 : 36168 : 2805 [M.Start]ACT.Takeoff FAIL, esc error!
59.010 : 36168 : 2805 CTRL reset all by auto takeoff start fail
59.010 : 36168 : 2805 try auto takeoff, but start motor fail!
59.030 : 36180 : 2806 [M.Start]ACT.Takeoff FAIL, esc error!
59.030 : 36180 : 2806 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
 
droneforumaccount said:
unfortunately the log just spits out a generic esc error and doesn't tell me which is faulting:

2.910 : 2508 : 0 [hardfault]:******************check fault info and trace ************
2.910 : 2508 : 0 [hardfault]:-----fault is null: addr(0x40024000),flag(0x842ed686)-----
2.910 : 2508 : 0 [hardfault]:-----fault is null: addr(0x400241a0),flag(0x87ba5e73)-----
2.910 : 2508 : 0 [hardfault]:-----task info is null: addr(0x40024340),flag(0x63e944c5)-----
2.910 : 2508 : 0 [hardfault]:-----trace info is null: addr(0x400244d0),flag(0x626ad5c3)-----
2.910 : 2508 : 0 [hardfault]:******************check last trace ******************
2.910 : 2508 : 0 [hardfault]:-----trace info is null: addr(0x40024790),flag(0xa1094ab2)-----
2.910 : 2508 : 0 [hardfault]:-----wdg_time_info is null: addr(0x40024a50),flag(0x99c96dac)-----
3.762 : 3019 : 42 ESC0 link up
3.773 : 3026 : 43 ESC1 link up
3.785 : 3033 : 43 ESC2 link up
3.797 : 3040 : 44 ESC3 link up
3.797 : 3040 : 44 esc alive info = 0xf
4.760 : 3618 : 92 ESC0 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.760 : 3618 : 92 Loader = [V01.00.02.02]
4.760 : 3618 : 92 Firmware = [V01.11.00.00]
4.768 : 3623 : 92 ESC1 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.768 : 3623 : 92 Loader = [V01.00.02.02]
4.768 : 3623 : 92 Firmware = [V01.11.00.00]
4.777 : 3628 : 93 ESC2 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.777 : 3628 : 93 Loader = [V01.00.02.02]
4.777 : 3628 : 93 Firmware = [V01.11.00.00]
4.785 : 3633 : 93 ESC3 version: Protocol = [V1.0] Hardware = "WM320_ESC_V9"
4.785 : 3633 : 93 Loader = [V01.00.02.02]
4.785 : 3633 : 93 Firmware = [V01.11.00.00]
49.210 : 30288 : 2315 [M.Start]REQ_RC_NORMAL FAIL, esc error!
58.810 : 36048 : 2795 [Ctrl<6>] REQ_APP_WM610 ENGINE_START ctrl_engine_start
58.830 : 36060 : 2796 [M.Start]ACT.Takeoff FAIL, esc error!
58.850 : 36072 : 2797 [M.Start]ACT.Takeoff FAIL, esc error!
58.870 : 36084 : 2798 [M.Start]ACT.Takeoff FAIL, esc error!
58.890 : 36096 : 2799 [M.Start]ACT.Takeoff FAIL, esc error!
58.910 : 36108 : 2800 [M.Start]ACT.Takeoff FAIL, esc error!
58.930 : 36120 : 2801 [M.Start]ACT.Takeoff FAIL, esc error!
58.950 : 36132 : 2802 [M.Start]ACT.Takeoff FAIL, esc error!
58.970 : 36144 : 2803 [M.Start]ACT.Takeoff FAIL, esc error!
58.990 : 36156 : 2804 [M.Start]ACT.Takeoff FAIL, esc error!
59.010 : 36168 : 2805 [M.Start]ACT.Takeoff FAIL, esc error!
59.010 : 36168 : 2805 CTRL reset all by auto takeoff start fail
59.010 : 36168 : 2805 try auto takeoff, but start motor fail!
59.030 : 36180 : 2806 [M.Start]ACT.Takeoff FAIL, esc error!
59.030 : 36180 : 2806 [Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
Click to expand...
You could take a look at the motor speed, commanded and load for each of the motors at startup. One of the motors might be different. To do this use CsvView which you can obtain from here. You could also Dropbox the .DAT and post a link and I or someone else could take a look.
 
BudWalker said:
You could take a look at the motor speed, commanded and load for each of the motors at startup. One of the motors might be different. To do this use CsvView which you can obtain from here. You could also Dropbox the .DAT and post a link and I or someone else could take a look.
Click to expand...

so, i'm getting an esc error which prevents all of the motors from spinning. given that, would you think there would be any useful data. I'll poke through that file now.
 
droneforumaccount said:
so, i'm getting an esc error which prevents all of the motors from spinning. given that, would you think there would be any useful data. I'll poke through that file now.
Click to expand...
Might be. Maybe the errant motor/esc is showing less load than the others.
 
BudWalker said:
Might be. Maybe the errant motor/esc is showing less load than the others.
Click to expand...

Here's a snip from a test where I turned on the bird, tried to fire up motors with CSC, and received ESC error.

upload_2017-3-12_21-16-49.png
 
droneforumaccount said:
Here's a snip from a test where I turned on the bird, tried to fire up motors with CSC, and received ESC error.

View attachment 78309
Click to expand...
Sorry, I don't do .csv printouts. You'll have to provide either the .DAT or the .csv that DatCon generates if you want me to take a look. You might want to consider specifying 200 mHz sampling rate for this.
 
I have one more idea about detecting motor numbers.

The flight controller will ignore the error if "g_real.status.motor_status_0" option is set to "1". This would allow you to check which motor does not spin correctly.

This parameter can be set from a mobile device, but I don't know of any currently existing tool which has that option. Maybe someone from the hacking team at Github will be able to help you with this.
 
quaddamage said:
I have one more idea about detecting motor numbers.

The flight controller will ignore the error if "g_real.status.motor_status_0" option is set to "1". This would allow you to check which motor does not spin correctly.

This parameter can be set from a mobile device, but I don't know of any currently existing tool which has that option. Maybe someone from the hacking team at Github will be able to help you with this.
Click to expand...


that's helpful. I'll need to spend some time flashing my firmware down a few versions and then I may try some tampering like:
Hacking the DJI Phantom 3 - VoidSec
 
BudWalker said:
Sorry, I don't do .csv printouts. You'll have to provide either the .DAT or the .csv that DatCon generates if you want me to take a look. You might want to consider specifying 200 mHz sampling rate for this.
Click to expand...


would you be able to explain the difference between CMND, Speed, and Load and what the units are.

Here's a csv from a recent test where the motors were all whirling. let me know if you can pinpoint which one(s) aren't functioning as commanded. thanks!

note, had to add .txt to the file to allow the csv to upload
 

Attachments

  • FLY160.csv.txt
    2 MB · Views: 240
droneforumaccount said:
would you be able to explain the difference between CMND, Speed, and Load and what the units are.

Here's a csv from a recent test where the motors were all whirling. let me know if you can pinpoint which one(s) aren't functioning as commanded. thanks!

note, had to add .txt to the file to allow the csv to upload
Click to expand...
Info on the .csv columns can be found here. Commanded and speed are pretty obvious. Load is a little different in that I don't actually know what exactly it is. But, it does increase if the motor is restricted and it does decrease if the prop is lost.

Looking at the .csv you supplied the commanded and actual speeds don't seem to be unusual.
upload_2017-3-13_6-30-13.png

upload_2017-3-13_6-30-21.png


Motor load is a bit odd though. Don't know that I've ever seen something like this, but I don't usually have a reason for looking at motorLoads at motorStart.
upload_2017-3-13_6-56-2.png


I think we want to look at data where the ESC is failing. Can you provide the .DAT that produced the screenshot in post #53? The .csv is OK but the .DAT would be better.
 
BudWalker said:
Info on the .csv columns can be found here. Commanded and speed are pretty obvious. Load is a little different in that I don't actually know what exactly it is. But, it does increase if the motor is restricted and it does decrease if the prop is lost.

Looking at the .csv you supplied the commanded and actual speeds don't seem to be unusual.
View attachment 78331
View attachment 78332

Motor load is a bit odd though. Don't know that I've ever seen something like this, but I don't usually have a reason for looking at motorLoads at motorStart.
View attachment 78334

I think we want to look at data where the ESC is failing. Can you provide the .DAT that produced the screenshot in post #53? The .csv is OK but the .DAT would be better.
Click to expand...


thanks for taking a look. I'll upload the esc fail .dat in a bit. I actually noticed that one of the motors seemed to be slightly louder than the others. front left if your perspective is the center of the copter looking out (front right if looking straight on at the front of the copter).

going to replace this motor today and see if that changes anything. Load isn't a percentage of total capacity is it?
 
droneforumaccount said:
thanks for taking a look. I'll upload the esc fail .dat in a bit. I actually noticed that one of the motors seemed to be slightly louder than the others. front left if your perspective is the center of the copter looking out (front right if looking straight on at the front of the copter).

going to replace this motor today and see if that changes anything. Load isn't a percentage of total capacity is it?
Click to expand...
Load is a measure of the amount of effort required to turn the motor. Like in your car. If you're going up hill there is more load on the engine.
 

Similar threads

efrancanojr
ESC Status Error!
Replies
1
Views
1K
Phantom 3 Pro/Adv
brigerdrones
brigerdrones
C
Tried repairing after crash, works until I put the case back together.
Replies
11
Views
1K
Phantom 4 Help
Rnc3.1
R
M
Phantom 3 Advanced ESC Status Error and firmware update shows old version with a + instead of new
Replies
17
Views
2K
Phantom 3 Pro/Adv
albo752004
A
L
new board connection problem
Replies
6
Views
1K
FPV (First Person View)
Rnc3.1
R
R
Gimble Motor Overloaded
Replies
7
Views
919
Phantom 4 Help
Droneted
Droneted

Recent Posts

Members online

Total: 555 (members: 1, guests: 554)

Forum statistics

Threads
143,092
Messages
1,467,578
Members
104,976
Latest member
cgarner1