p3 motor esc status error and firmware update problem

[mikey939426]

Hello,
I have about 10 hours on my p3a. It came up with the motor esc status error when i tried to upgrade to the newest version of firmware 1.9.6. The unit shows it has 1.6 on the controller and 1.9.6 on the drone but the files that are supposed to show up on the memory card arent there and the text file says it failed update. I have tried everything to reload the firmware but it won't take it. Everything looks normal except the motors will not start. I have had this phantom for about 6 months. I have done a dual battery mod to it so it isn't under warranty, any more. I just changed the control board to a brand new one and it didn't fix the firmware update or the motor esc status error problem. What do you suggest I do next? I don't want to keep spending money on this and not fixing it. Thanks. Michael

 

[msinger]

the text file says it failed update

Please post that file here.

 

[mikey939426]

Please post that file here.

This is alI get when I try to update, now. I aborted it after about five or ten minutes of it just going crazy. I had earlier tried letting it run for thirty minutes while going crazy to see if it ever settled down but it did not so, I aborted it. I have changed the main board with a brand new one, tried updating firmware, and done multiple imu calibrations, to no avail. Still the motor esc status error when i try to start it. Really dismayed with p3 at this point. My old p2 seemed indestructible compared to this one. It had been crashed and had multiple motor and esc replacements without any lasting affects. Is there a way to troubleshoot individual motors correctly on this p3? Thank you. Michael

Delete history success.

Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:00:48 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:02:41 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:29:34 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:31:01 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 04:34:56 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 15:58:05 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 16:00:23 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 16:08:20 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 16:10:44 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.09 01:55:42 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.13 20:06:12 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.14 22:44:25 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.14 22:46:56 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.14 23:08:59 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2016.08.15 14:48:23 =====================
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

 

[mikey939426]

That file was the result of trying to update with the newest version for the p3. The memory card was first formatted, then the new file was downloaded to the card and the card inserted into the p3. The file was labeled p3s fw v01.09.0060.bin

Michael

 

[alokbhargava]

I don't see the labeling of the file in the right format.


Sent from my iPhone using PhantomPilots

 

[mikey939426]

I don't see the labeling of the file in the right format.


Sent from my iPhone using PhantomPilots

Hello,

I just tried it, again. I downloaded the correct file from dji, put it on the newly formatted card and put it in the p3 and let it run for thirty minutes. I got the exact same text file when I aborted the process. I don't know what to do. Very odd that it did this on a new board. Isn't that where the program is stored? I don't know what to do next.

Exactly what is this text file telling me? Michael


Delete history success.

Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:00:48 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:02:41 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:29:34 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 03:31:01 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 04:34:56 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 15:58:05 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 16:00:23 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 16:08:20 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.08 16:10:44 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.09 01:55:42 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.13 20:06:12 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.14 22:44:25 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.14 22:46:56 =====================
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2016.08.14 23:08:59 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2016.08.15 14:48:23 =====================
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.


Michael

 

[Dronason]

Hello,
I have about 10 hours on my p3a. It came up with the motor esc status error when i tried to upgrade to the newest version of firmware 1.9.6. The unit shows it has 1.6 on the controller and 1.9.6 on the drone but the files that are supposed to show up on the memory card arent there and the text file says it failed update. I have tried everything to reload the firmware but it won't take it. Everything looks normal except the motors will not start. I have had this phantom for about 6 months. I have done a dual battery mod to it so it isn't under warranty, any more. I just changed the control board to a brand new one and it didn't fix the firmware update or the motor esc status error problem. What do you suggest I do next? I don't want to keep spending money on this and not fixing it. Thanks. Michael

Firmware version 1.9.60 for the P3 is the last one and version 1.6 for the remote control is also the latest one.

There are some more log files with full details about the upgrade process. See thread Increase in the number of crash threads recently? at post #15, I just learned it yesterday from there. That could help others to see if you have really a firmware issue. This is hidden folders, I cannot see them on my PC put if I put the uSD card on my Android tablet, I can see them.

I assume you checked that all motors are fully free to rotate.

 

[MPPilot]

Please excuse what may be a stupid question, but isn't the P3A more in line with the P3P than the P3S? Just wondering why the A is getting an S update. And what does the P34k use? I didn't even see firmware listed for it in the downloads section.

 

[Dronason]

Please excuse what may be a stupid question, but isn't the P3A more in line with the P3P than the P3S? Just wondering why the A is getting an S update. And what does the P34k use? I didn't even see firmware listed for it in the downloads section.

Yes, P3A and P3P are similar where P3S is really different.
The firmware names what they are, the professional firmware (Phantom 3 Professional - Specs, FAQ, Tutorials, Downloads and DJI GO | DJI) and for the P3A is here Phantom 3 Advanced - Specs, FAQ, Tutorials, Downloads and DJI GO | DJI as zip files. The strange name is in the zip file.
DJI programmers defined the P3P firmware as P3S_FW_V01.09.0060.bin and P3P as P3X_FW_V01.09.0060.bin and yes they used S for the advance and X for the Pro, but that was much before the standard exist (no idea what standard or 4k name have as I don't own them).
So that's more related to the history of development by DJI.

 

[Dusty lens]

Getting the same issue. New centre board, updated firmware, now all i get are esc error messages if i try to arm the motors. Everything else says its right to go.

 

[mikey939426]

Hello,
I have about 10 hours on my p3a. It came up with the motor esc status error when i tried to upgrade to the newest version of firmware 1.9.6. The unit shows it has 1.6 on the controller and 1.9.6 on the drone but the files that are supposed to show up on the memory card arent there and the text file says it failed update. I have tried everything to reload the firmware but it won't take it. Everything looks normal except the motors will not start. I have had this phantom for about 6 months. I have done a dual battery mod to it so it isn't under warranty, any more. I just changed the control board to a brand new one and it didn't fix the firmware update or the motor esc status error problem. What do you suggest I do next? I don't want to keep spending money on this and not fixing it. Thanks. Michael

I can't remember if I posted the problem or, cure to this post? Anyway, the entire problem was caused by me when I did the dual battery mod. During the mod, I put one screw back in each motor, part of the way in, just to hold the motor so the wire connections wouldn't be compromised while the motors dangled during the mod work. I did not screw them all the way in so as not to damage the motors. Or, so I thought! I was SURE I had not screwed them in so far as to cause damage. After all the help from people on here, along with some incorrect advice on log files and the such and, after changing out everything EXCEPT the motors, I bought new motors. Hooked everything back up and, it took off right away with no other errors, no hiccups, nothing wrong. I got my faith back in DJI and, am trying to decide between a new p4 pro and the mavic pro to add to my small collection. My p3 advanced is back to its bullet proof self even with the fairly wasted trouble of time and money putting the dual mod on. If I had to do it again, I would not do the dual battery mod. The extra 4-5 minutes of flight time it gave me are not worth the time or, money of the installation. Not to mention the aggravation of messing it up (my fault) and all the time of troubleshooting and money I spent trying to fix the problem. I am leaning towards a mavic pro just because of their portability. I am a little concerned with reports of the lesser degree of quality the camera affords but am wondering if that difference is something only "experts" can see with their trained eyes? Anyone on here with experience with both of them have any thoughts?

 

[Dusty lens]

Thanks for the reply. I replaced #1motor because the bell had a small dent in it (I'm rebuilding a crashed P3A I bought cheap). I ordered a spare CW and CCW motor just in case I would need them. Looks like I will have to order some more and replace the lot, even though they feel ok.