Hi,

I've updated today to the latest firmware P3X_FW_V01.01.0006 but during the update didn't hear the camera making any sounds (that the update started or finished)
Can somebody confirm that the update is correct? (the start date is 2014? little bit strange?)

Second,not so important but just wondering -The instructions also said that the installation files must remain on the SD card. This means that every time you start your Phantom the aircraft will try to update the firmware and write this line again and again:-Result: Abort. The firmware on the SD card is identical to or older than the current firmware on the aircraft.

...and last but not least-copying only the .bin file is enough for the firmware update, right?

Thanks in advance!

These are my log files:


========== 2014.01.01 00:00:12 unsynchronized ======
Packet: P3X_FW_V01.01.0006.bin
Upgrading ...
Result: Success.

========== 2015.05.05 02:07:37 =====================
Packet: P3X_FW_V01.01.0006.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.


And this one:

[00012291]========== 2014.01.01 00:00:12 unsynchronized ======
[00012307]Packet [C:\P3X_FW_V01.01.0006.bin] detected.
[00012321]Packet upgrade start...

[00012333]Packet checking...
[00012338]Done.

[00012345]Version checking[1]...
[00012384][03 05] v34.2.0.8 -> v34.2.0.8
[00012424][03 06] v2.1.6.7 -> v2.1.6.7
[00012437][04 00] v1.36.0.0 -> v1.36.0.0
[00012458][09 00] v1.6.0.4 -> v1.7.0.1 need upgrade.
[00012546][11 00] v1.6.0.0 -> v1.6.0.0
[00012594][12 00] v1.7.0.0 -> v1.7.0.0
[00012664][12 01] v1.7.0.0 -> v1.7.0.0
[00012713][12 02] v1.7.0.0 -> v1.7.0.0
[00012784][12 03] v1.7.0.0 -> v1.7.0.0
[00012893][15 00] v1.1.2.0 -> v1.1.2.0
[00012948][17 00] v1.1.1.2 -> v1.1.1.2
[00013048][17 01] v1.0.2.4 -> v1.0.2.4
[00013079][19 00] v1.0.8.59 -> v1.0.8.59
[00013084][01 00] v1.4.2674 -> v1.6.2736 need upgrade
[00013089][01 01] v1.4.2674 -> v1.5.2735 need upgrade
[00013110][08 00] v0.10.0.4 -> v0.11.0.4 need upgrade.
[00013116]Done.

[00015121]Waiting for user confirm...
[00025126]Timeout, start upgrade automatically.

[00025136]Firmware upgrading[1]...
[00037396][01 00] Firmware upgrading start...
[00012128][01 00] Firmware upgrade finished successfully.
[00012149]Done.

[00012158]Version checking[2]...
[00017198][03 05] v34.2.0.8 -> v34.2.0.8
[00017232][03 06] v2.1.6.7 -> v2.1.6.7
[00017243][04 00] v1.36.0.0 -> v1.36.0.0
[00017267][09 00] v1.6.0.4 -> v1.7.0.1 need upgrade.
[00017333][11 00] v1.6.0.0 -> v1.6.0.0
[00017382][12 00] v1.7.0.0 -> v1.7.0.0
[00017422][12 01] v1.7.0.0 -> v1.7.0.0
[00017468][12 02] v1.7.0.0 -> v1.7.0.0
[00017532][12 03] v1.7.0.0 -> v1.7.0.0
[00017629][15 00] v1.1.2.0 -> v1.1.2.0
[00017657][17 00] v1.1.1.2 -> v1.1.1.2
[00017737][17 01] v1.0.2.4 -> v1.0.2.4
[00017767][19 00] v1.0.8.59 -> v1.0.8.59
[00017771][01 00] v1.6.2736 -> v1.6.2736
[00017776][01 01] v1.4.2674 -> v1.5.2735 need upgrade
[00017798][08 00] v0.10.0.4 -> v0.11.0.4 need upgrade.
[00017802]Done.

[00017807]Firmware upgrading[2]...
[00017922][01 01] Firmware upgrading start...
[00048150][01 01] Firmware upgrade finished successfully.
[00048976][08 00] Firmware upgrading start...
[00563366][08 00] Firmware upgrade finished successfully.
[00563395][09 00] Firmware upgrading start...
[00613775][09 00] Firmware upgrade finished successfully.
[00613781]Done.

[00613786]Version checking[3]...
[00613832][03 05] v34.2.0.8 -> v34.2.0.8
[00613868][03 06] v2.1.6.7 -> v2.1.6.7
[00613878][04 00] v1.36.0.0 -> v1.36.0.0
[00613898][09 00] v1.7.0.1 -> v1.7.0.1
[00613973][11 00] v1.6.0.0 -> v1.6.0.0
[00614018][12 00] v1.7.0.0 -> v1.7.0.0
[00614063][12 01] v1.7.0.0 -> v1.7.0.0
[00614113][12 02] v1.7.0.0 -> v1.7.0.0
[00614162][12 03] v1.7.0.0 -> v1.7.0.0
[00614270][15 00] v1.1.2.0 -> v1.1.2.0
[00614323][17 00] v1.1.1.2 -> v1.1.1.2
[00614417][17 01] v1.0.2.4 -> v1.0.2.4
[00614438][19 00] v1.0.8.59 -> v1.0.8.59
[00614443][01 00] v1.6.2736 -> v1.6.2736
[00614448][01 01] v1.5.2735 -> v1.5.2735
[00614466][08 00] v0.11.0.4 -> v0.11.0.4
[00614470]Packet upgrade finish successfully.



[00012258]========== 2015.05.05 02:07:37 =====================
[00012268]Packet [C:\P3X_FW_V01.01.0006.bin] detected.
[00012277]Packet upgrade start...

[00012290]Packet checking...
[00012301]Done.

[00012312]Version checking[1]...
[00012353][03 05] v34.2.0.8 -> v34.2.0.8
[00012397][03 06] v2.1.6.7 -> v2.1.6.7
[00012410][04 00] v1.36.0.0 -> v1.36.0.0
[00012421][09 00] v1.7.0.1 -> v1.7.0.1
[00014997][11 00] v1.6.0.0 -> v1.6.0.0
[00015042][12 00] v1.7.0.0 -> v1.7.0.0
[00015087][12 01] v1.7.0.0 -> v1.7.0.0
[00015136][12 02] v1.7.0.0 -> v1.7.0.0
[00015182][12 03] v1.7.0.0 -> v1.7.0.0
[00015312][15 00] v1.1.2.0 -> v1.1.2.0
[00015362][17 00] v1.1.1.2 -> v1.1.1.2
[00015443][17 01] v1.0.2.4 -> v1.0.2.4
[00015462][19 00] v1.0.8.59 -> v1.0.8.59
[00015466][01 00] v1.6.2736 -> v1.6.2736
[00015479][01 01] v1.5.2735 -> v1.5.2735
[00015495][08 00] v0.11.0.4 -> v0.11.0.4
[00015500]Packet upgrade cancelled at version checking.

Mine made the strange noises and took about 5 min. I also think you want to delete the file after update. I sure hope this fixes issues with the drone suddenly stop working in flight as some has reported.

I am confused by this.  I cannot tell if the firmware update worked.  Wear does this "txt" file appear?

SJS94 Posted at 2015-5-5 07:38
I am confused by this.  I cannot tell if the firmware update worked.  Wear does this "txt" file appe ...

After you've updated the firmware on the P3 and radio you put the SD card back into your computer and the .txt file will be on the card telling you if it was a success or failed.

Here what I posted on another tread.
P3A
I didn't have much  text on mine.


"========== 2014.01.01 00:00:12 unsynchronized ======
Packet: P3S_FW_V01.01.0006.bin
Upgrading ...
Result: Success.

Updated the P3A bird, took 2 - 5 minutes not 25

Step 3- Update the Aircraft
1. Ensure the remote controller is powered off and then power on the aircraft. Upgrade will begin automatically after aircraft is powered on.
2. It will take approximately 25 minutes to complete the firmware update. The camera will sound a short pluse of "D-D-D-D" beeping sound to indicate the upgarde is in progress and sound a “D---DD” beeping sound to indicate the update is complete with success.
3. Check the upgrade status by opening the “.txt” file that is automatically generated after the update. The update is successful if the text “result: successful” is in the document. Try upgrading the firmware again if the text “result: failed” is found or the gimbal sound a long beep sound.
Around 2 minutes to update the controller.
text files after updating

==========2015.05.04 22:58:31==========
Packet: /mnt/usb/P3S_FW_V01.01.0006.bin,
Upgrading ...
Result: Success


RC upgrade log:
start upgrade 13
success
start upgrade 14
success"

same problem, the fw says it is already present or that is older than what I am setting up, and me from your own log. Throughout emits sounds at the beginning and then just d-ddd

Your upgrade is successful. Usually after upgrade success you can del the bin file. But if you have more than one battery and the battery's firmware need to be upgraded, you need to remain the bin file in SD card and upgrade each one.

rbarbour@pacbel Posted at 2015-5-5 09:13
Here what I posted on another tread.
P3A
I didn't have much  text on mine.

You can set the hidden file visible in computer, then you can find other txt files indicate the upgrade process.
If you r not sure whether the upgrade is successful or not, refer to those hidden txt log files.

DJI-Autumn Posted at 2015-5-5 16:02
Your upgrade is successful. Usually after upgrade success you can del the bin file. But if you have  ...

Thank you for the clarification!

BrewserB Posted at 2015-5-5 07:26
Mine made the strange noises and took about 5 min. I also think you want to delete the file after up ...

According to the text below, we should just keep the latest bin files in the SD card. probably in case our new battery comes and it hasn't been updated yet.

"The Intelligent Flight Battery is upgraded during the aircraft firmware upgrade process. It is recommended to keep the upgrade package files in your SD card. The upgrade will start automatically after power cycling the aircraft."

nurimanizam Posted at 2015-5-6 00:48
According to the text below, we should just keep the latest bin files in the SD card. probably in  ...

I haven't tried firing up the drone since the update but if you leave the file on the SD card wouldn't it go through the upgrade process every time you start the P3? If this update is for the battery I'm wondering if this is why the batteries have been delayed? They all need to be updated. Makes sense.

DJI-Autumn Posted at 2015-5-5 16:02
Your upgrade is successful. Usually after upgrade success you can del the bin file. But if you have  ...

I just tried again to load update because I couldn't find the .txt file to tell me if it was success or failed. This time it's just continues to beep DDDD over and over. Is this what it's supposed to do?
Update: Success with all updates. The P3 just kept beeping DDDD until finished then the D...DD. Time 21 minutes. The controler 5 minutes.

BrewserB Posted at 2015-5-6 02:38
I haven't tried firing up the drone since the update but if you leave the file on the SD card would ...

This new firmware is not include the battery update. Only add iOS support. But battery's firmware can be upgraded, just not for this time.

BrewserB Posted at 2015-5-6 02:38
I haven't tried firing up the drone since the update but if you leave the file on the SD card would ...

Every time you start the phantom. It will append the txt file with a message like "Firmware on SD is the same as installed" and then skips the upgrade process. The txt file is only 1KB so I doubt it will grow big anytime soon.

So far I've had no issues leaving it in the card after flying a few times with the new firmware

I am  having the same issue it keeps saying I need update the firmware on my aircraft but the log files show it is already updated, I tried on both my Ipad and Iphone and rebooted both devices too, I have been flying without issue but am a little worried about the message.  I have gone about 500 meters before I get a signal transmission loss or weak and I return but then again I'm flying in an area with alot of wifi interference (town house area) anyone have this issue where it doesn't go away?