This update doesn't engage for my Phantom 3 Pro.
This is the First time my updates have failed to start. Formatted the card, downloaded the new firmware.
Inserted the card into the gimbal. It did the initial B-BB one time, but that's it.
The gimbal light stays solid green, back arm LED's blink fast yellow. Front arms, are solid red.
But nothing else transpires.
Formatted the card, even tried my other micro SD card, same result? The update doesn't start.
Any clues or ideas, would be appreciated?

RedHotPoker

No help is necessary for me now. But thanks for the effort. 0

I've just been informed, there was a problem at DJI HQ, & not with my system.
I was told from a tech, to try again after 6:00pm MST.
Apparently, the latest bin file I tried is empty. So no wonder nothing happened. ;-)
You can't upgrade from an empty file.

Just a Couple of more hours and it should have been corrected. Hopefully.

RedHotPoker

I am a little scared to update.

Once they @DJI update the firmware on their download page right, I will be on it like white on rice. Hehehe
Don't fear updating, fear not updating, and missing out on some cool new features.
Um, Like the Phantom 3 Pro camera getting 2.7K like the Phantom 3 Advanced was given, last round.
But This time, it was only made available for Phantom 3 Pro Android app. ;-)
For the rest of us, Our Phantom 3 Pro iOS Go app, camera update, will happen, some time in the near future.

RedHotPoker

Thanks for a really great post on the firmware update process Sploodge. Well Done.

I posted a newbie thread just a few days ago because I thought, erroneously, I had done something wrong upgrading FW. After several very kind forum members walked me through the process I realized all was good.

Fast forward to today and a new firmware is released so I went through the process again and had a "successful" upgrade. However, I now have a few questions as I did some things contrary to the instructions in the OP. Even though I have the "success" indicator in the .txt file could there be any issues because...

1. I left the gimble lock clamp in place?
2. I left the Controller on?
If leaving those two on could cause me issues later on then I assume I would need to downgade back to 1.4 and then upgade back to 1.5 since it wont reinstall the same FW over itself.

Also, all the instructions indicate the FW updates both the P3 and the battery (depending on the FW). Does this mean I need to run the process over again for each additional battery or will the battery get updated automatically whenever I insert it and turn on the bird as long as I leave the .bin file on the SD card? In other words will it know its just a battery update and be quick or will ot go through the whole 25 min process again. I want to avoid that when in the field if possible.

Sorry again for the newbie questions. I just want to make sure I do this properly.

Craig

cobbler Posted at 2015-11-26 05:12
Thanks for a really great post on the firmware update process Spoilage. Well Done.

I posted a newbi ...

Hi Craig..

There is NO battery update in this firmware version 1.5.0030. What versions have you come from?
Controller being ON is OK.. Done it myself and has no impact ( although again advised to be off during aircraft updates ).

Leaving the gimbal clamp on is not ideal at all. make sure you test it to make sure its functioning OK. I'm *think DJI added a feature where the gimbal stops trying to move if it detects restriction but I am not 10% sure.. can't remember where I saw this info.. Check it in the sky..

sploodge Posted at 2015-11-25 23:47
Hi Craig..

There is NO battery update in this firmware version 1.5.0030. What versions have you c ...

Hi Sploodge and again thanks for taking the time to post the guide. I knew I made the mistake as soon as the update finished when I saw the gimble lock on even prior to reading your post. I am a total newbie here. Just got the P3P a few days ago. Hopefully the gimble isn't messed up. It seems to do the normal power up moves correctly. I guess we shall see.

So I have only updated to 1.4 when I received the bird and now to 1.5. I understand that this particular FW update didn't have a battery update so I guess my question relates to what if it did? So let's assume the next update does have a battery update.  I have 3 batteries. So I would update with battery 1 in the bird no problem. I assume I need to leave the .bin file on the SD card so the other two batteries can be updated.
So, do the other two batteries have to go through the whole 25 min update process? I'm not sure how to convey what I am trying to ask. In other words does the update process know the FW on the bird has been updated and only do a smaller battery update on the remaining two batteries when i put them in and power up? If so then I would want to do that prior to being out in the field.

I'll do a search on updating multiple batteries and see if anything comes up. I really hate wasting others time if this has already been talked about.

Thanks,

Craig

Do I have to calibrate the IMU, gimbal and compass after update to this FW?

cobbler Posted at 2015-11-26 09:24
Hi Sploodge and again thanks for taking the time to post the guide. I knew I made the mistake as so ...

Hi Craig..

On the SD card there is a hidden folder called MISC/LOG that contains a txt file with som info about the upgrade.. at the bottom of the file it will look something like the below.

[00386109][03 05][00] v34.2.0.9 -> v34.2.0.9
[00386210][03 06][05] v2.4.0.5 -> v2.4.0.5
[00386293][04 00][00] v1.41.0.0 -> v1.41.0.0
[00386471][11 00][00] v1.7.0.0 -> v1.7.0.0
[00386599][12 00][00] v1.10.0.0 -> v1.10.0.0
[00386721][12 01][00] v1.10.0.0 -> v1.10.0.0
[00386844][12 02][00] v1.10.0.0 -> v1.10.0.0
[00386979][12 03][00] v1.10.0.0 -> v1.10.0.0
[00387149][15 00][00] v1.1.2.0 -> v1.1.2.0
[00387254][17 00][00] v1.1.1.7 -> v1.1.1.7
[00387513][17 01][00] v1.0.2.7 -> v1.0.2.7
[00387619][19 00][00] v1.0.8.96 -> v1.0.8.96
[00387693][01 00][05] v1.26.4315 -> v1.26.4315
[00387764][01 01][05] v1.26.4315 -> v1.26.4315
[00387865][08 00][00] v0.13.0.7 -> v0.13.0.7
[00387959][09 00][00] v2.13.0.0 -> v2.13.0.0

The part hilighted in RED is the battery ( module [11 00] ). If it shows v1.7.0.0 then the battery is already at the latest version, you can power on the P3 with each battery and it will amend the log each time to show the battery version.. have a look to see. below is a video showing how to see hidden folders in Windows..

voyager4000 Posted at 2015-11-26 10:17
Do I have to calibrate the IMU, gimbal and compass after update to this FW?

It is recommended to do so..

Checked all 3 batteries and they are all up to date. All is good.

Last question as I probably confused you with my long post above. If for example one of my 3 batteries was on an older version when I put it in the bird and turned it on I assume it would notice i have an outdated battery version on the initial check and update the battery. The question is does it go through the whole FW update process ie. 25 minutes or is it a quicker subset of instructions that lets say takes 5 minutes or so?

I am no doubt overthinking all this but I am an IT guy so we do those things. Are battery firmware upgrades rare or do they happen on a regular basis?

Again, thank you  sploodge for your patience and time answering these questions. I am sure they get old hearing them over and over from us new goobers. Flying this thing will be a breeze compared to all the initial prep. DJI really needs to put together a little app or include the functionality in the Go App that handles the FW upgrade process and making sure all components are up to date and compatible with each other.

You rock sploodge,

Craig

thanks for your help.

I hoped this update would fix my ultrasonic error land now but it did not!

I hoped this update would fix my ultrasonic error land now but it did not!

aggiornamento

I may just wait until the 2.7K for pro feature hits IOS before upgrading,
Doesn't seem a lot in this one for me yet

RedHotPoker Posted at 2015-11-25 19:36
Once they @DJI update the firmware on their download page right, I will be on it like white on rice. ...

Mine is doing the same as yours! Not updating at all... Any luck on your end?

Jason

truckiejp Posted at 2015-11-27 06:38
Mine is doing the same as yours! Not updating at all... Any luck on your end?

Jason

Just a thought, but it comes in the form of a zipped up file, you are extracting it before you put it on the card? It should be a BIN file.

Geebax Posted at 2015-11-26 17:17
Just a thought, but it comes in the form of a zipped up file, you are extracting it before you put ...

Yes, def a "bin" file..... Yours update ok?

truckiejp Posted at 2015-11-27 10:51
Yes, def a "bin" file..... Yours update ok?

Yes, it did, no problem at all. But others are reporting similar problems to you.

Geebax Posted at 2015-11-26 19:18
Yes, it did, no problem at all. But others are reporting similar problems to you.

Compared to the last update, this one didn't have a folder, was just the zipped file... Something is missing.... thanks for the look out...

truckiejp Posted at 2015-11-26 12:38
Mine is doing the same as yours! Not updating at all... Any luck on your end?

Jason

Yes
I have already updated the firmware of my radio controller, the drone and camera.
I feel kind of stupid after my antics here last night., or was it the night before, actually?
Anyway, the correct bin file was always there, in the root, 64mb.
But I had forgot to delete the other portion, and so no wonder it couldn't find and load the firmware.

When you download the zipped files, open the zipped file, and extract, only the bin file, and nothing else.
Or do delete anything that is not the actual bin file. Once I understood the error of my ways, I was home free. The update ran clean and smooth, & with that pretty tune it sings, D-DD D-DD. . .  ;-)

Place "only the bare naked bin file" on the micro sd card.

RedHotPoker

RedHotPoker Posted at 2015-11-26 19:42
Yes
I gave updated the radio controller, the drone and camera.
I feel kind of stupid after my ant ...

Yes I did that... There's only 1 bin file.....

RedHotPoker Posted at 2015-11-26 19:42
Yes
I gave updated the radio controller, the drone and camera.
I feel kind of stupid after my ant ...

P3S_FW_V01.05.0030.bin   that file correct?

Yes, that's for the Phantom 3 Advanced, only, that's correct.
P3X_FW_V01.05.0030.bin is for the Phantom 3 Professional.

RedHotPoker

I formatted sd card using Go app.
Inserted it in my iMac and it is protected, I cannot copy anything.
SD info:
Created: Dic 31, 1969
Modified: Jan 1, 1980
Format: ExFat
Capacity: 64,2 Gb
You can only read

So I guess I have to use a writable sd card, copy .bin file and go on.
Crazy.PS: it remembers me the gopro 3+

DJI-Patrick Posted at 2015-11-23 19:39
Hi ,sploodge
The new firmware is going to be released in a few hours . Everything is fine !

Trust in sploodge!

Great info. I just successfully upgraded both P3A and RC with your instruction. Cheers!

Hi all. Having an unusual problem with the new f/w upgrade. At least I haven't come across anyone having the same issue here or on PhantomPilots forum after checking all the update threads.
I have a P3A which was on the latest f/w version before 1.5. Downloaded the update from DJI site, extracted the .bin file. Reformatted the sd card while it was in the quad, shut down the P3A, then transferred the .bin file to the root directory on the sd card, making sure it was the only file on the card. Plugged it back into the P3, and turned it on. Update started fine and continued for about 15 minutes, at which point the gimbal light turned solid red, with a continuous tone. Tried all the usual work-arounds - re-format card, use a different card, re-download update, make sure I have the correct update for adanced (P3S, not P3X), make sure bin is rooted, glare menacingly at P3 while it's updating - all to no avail.
The log files show that the update failed and the LOG_AB.txt file shows a specific item that needed an upgrade that wouldn't do so. (see attached text file)
Now here's the unusual part. I decided to update the GO app (using Ipad mini2) and controller, which happened with no problems, and connect up to my P3 to see what would happen. Everything connected fine, and everything works as it should - all camera control functions work, motors stop and start as they should, etc. But now, the Go app is saying I need an update for my camera. (see screenshot) Also, under "about", I'm showing latest version numbers for GO and TX, but the quad update is showing 1.4+, not 1.5. (see screenshot). Haven't had a chance to fly since updating so I can't be sure if everything is working properly. I didn't think there was any changes for P3A camera, so why do I need a camera update? Any suggestions would be welcome. Thanks in advance.


P3S_FW_LOG_AB.txt (for the sake of brevity I edited the file to only show my last failed update)




[00012276]========== remo-con disconnect. boot(15) ============
[00012348]Packet [C:\P3S_FW_V01.05.0030.bin] detected, card sn [0x4e50f542].
[00012421]Packet upgrade start...

[00012495]Packet checking...
[00012570]Packet vlink 01.05.0030 <-> 01.04.0010.
[00012642]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00012714]Done.

[00012788]Version checking[1]...
[00012892][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013012][03 06][00] v2.4.0.5 -> v2.4.0.5
[00013090][04 00][00] v1.41.0.0 -> v1.41.0.0
[00013236][11 00][00] v1.7.0.0 -> v1.7.0.0
[00013342][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013465][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013585][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013711][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013787][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013900][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014055][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014160][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014234][01 00][00] v1.21.3647 -> v1.22.4095 need upgrade
[00014306][01 01][00] v1.22.4095 -> v1.22.4095
[00014401][09 00][00] v2.13.0.0 -> v2.13.0.0
[00014472]Done.

[00016543]Waiting for user confirm...
[00026612]Timeout, start upgrade automatically.

[00026755]Firmware upgrading[1]...
[00041913][01 00] Firmware upgrade start...
[00011730][01 00] Firmware upgrade finished successfully.
[00011803]Done.

[00011875]Packet [C:\P3S_FW_V01.05.0030.bin] resumed, card sn [0x4e50f542].
[00012111]Packet vlink 01.05.0030 <-> 01.04.0010.
[00012184]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00012255]Version checking[2]...
[00012378][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012478][03 06][00] v2.4.0.5 -> v2.4.0.5
[00012562][04 00][00] v1.41.0.0 -> v1.41.0.0
[00012698][11 00][00] v1.7.0.0 -> v1.7.0.0
[00012838][12 00][00] v1.10.0.0 -> v1.10.0.0
[00012947][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013071][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013271][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013346][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013461][17 00][00] v1.1.1.7 -> v1.1.1.7
[00013622][17 01][00] v1.0.2.7 -> v1.0.2.7
[00013702][19 00][00] v1.0.8.96 -> v1.0.8.96
[00013776][01 00][02] v1.21.3647 -> v1.22.4095 need upgrade
[00013848][01 01][00] v1.22.4095 -> v1.22.4095
[00013943][09 00][00] v2.13.0.0 -> v2.13.0.0
[00014014]Done.

[00014084]Firmware upgrading[2]...
[00014157]Done.

[00014228]Version checking[3]...
[00014338][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014438][03 06][00] v2.4.0.5 -> v2.4.0.5
[00014516][04 00][00] v1.41.0.0 -> v1.41.0.0
[00014678][11 00][00] v1.7.0.0 -> v1.7.0.0
[00014811][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014922][12 01][00] v1.10.0.0 -> v1.10.0.0
[00015046][12 02][00] v1.10.0.0 -> v1.10.0.0
[00015171][12 03][00] v1.10.0.0 -> v1.10.0.0
[00015246][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015364][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015531][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015622][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015693][01 00][02] v1.21.3647 -> v1.22.4095 need upgrade
[00015766][01 01][00] v1.22.4095 -> v1.22.4095
[00015861][09 00][00] v2.13.0.0 -> v2.13.0.0
[00015935]Done.

[00016004]Firmware upgrading[3]...
[00016075]Done.

[00016148]Version checking[4]...
[00016258][03 05][00] v34.2.0.9 -> v34.2.0.9
[00016538][03 06][00] v2.4.0.5 -> v2.4.0.5
[00016615][04 00][00] v1.41.0.0 -> v1.41.0.0
[00016758][11 00][00] v1.7.0.0 -> v1.7.0.0
[00016872][12 00][00] v1.10.0.0 -> v1.10.0.0
[00016991][12 01][00] v1.10.0.0 -> v1.10.0.0
[00017118][12 02][00] v1.10.0.0 -> v1.10.0.0
[00017251][12 03][00] v1.10.0.0 -> v1.10.0.0
[00017326][15 00][00] v1.1.2.0 -> v1.1.2.0
[00017446][17 00][00] v1.1.1.7 -> v1.1.1.7
[00017601][17 01][00] v1.0.2.7 -> v1.0.2.7
[00017681][19 00][00] v1.0.8.96 -> v1.0.8.96
[00017755][01 00][02] v1.21.3647 -> v1.22.4095 need upgrade
[00017826][01 01][00] v1.22.4095 -> v1.22.4095
[00017923][09 00][00] v2.13.0.0 -> v2.13.0.0
[00018105]Done.

[00018179]Firmware upgrading[4]...
[00018251]Done.

[00018322]Version checking[5]...
[00018438][03 05][00] v34.2.0.9 -> v34.2.0.9
[00018538][03 06][00] v2.4.0.5 -> v2.4.0.5
[00018613][04 00][00] v1.41.0.0 -> v1.41.0.0
[00018759][11 00][00] v1.7.0.0 -> v1.7.0.0
[00018872][12 00][00] v1.10.0.0 -> v1.10.0.0
[00018992][12 01][00] v1.10.0.0 -> v1.10.0.0
[00019102][12 02][00] v1.10.0.0 -> v1.10.0.0
[00019226][12 03][00] v1.10.0.0 -> v1.10.0.0
[00019300][15 00][00] v1.1.2.0 -> v1.1.2.0
[00019422][17 00][00] v1.1.1.7 -> v1.1.1.7
[00019561][17 01][00] v1.0.2.7 -> v1.0.2.7
[00019661][19 00][00] v1.0.8.96 -> v1.0.8.96
[00019735][01 00][02] v1.21.3647 -> v1.22.4095 need upgrade
[00019805][01 01][00] v1.22.4095 -> v1.22.4095
[00019902][09 00][00] v2.13.0.0 -> v2.13.0.0
[00019973]Done.

[00020043]Firmware upgrading[5]...
[00020114]Done.

[00020186]Version checking[6]...
[00020298][03 05][00] v34.2.0.9 -> v34.2.0.9
[00020418][03 06][00] v2.4.0.5 -> v2.4.0.5
[00020496][04 00][00] v1.41.0.0 -> v1.41.0.0
[00020659][11 00][00] v1.7.0.0 -> v1.7.0.0
[00020812][12 00][00] v1.10.0.0 -> v1.10.0.0
[00020923][12 01][00] v1.10.0.0 -> v1.10.0.0
[00021206][12 02][00] v1.10.0.0 -> v1.10.0.0
[00021332][12 03][00] v1.10.0.0 -> v1.10.0.0
[00021406][15 00][00] v1.1.2.0 -> v1.1.2.0
[00021523][17 00][00] v1.1.1.7 -> v1.1.1.7
[00021664][17 01][00] v1.0.2.7 -> v1.0.2.7
[00021783][19 00][00] v1.0.8.96 -> v1.0.8.96
[00021856][01 00][02] v1.21.3647 -> v1.22.4095 need upgrade
[00021927][01 01][00] v1.22.4095 -> v1.22.4095
[00022022][09 00][00] v2.13.0.0 -> v2.13.0.0
[00022092]Packet upgrade failed at firmware upgrade.

I had an unusual problem upgrading - the lights would do their thing but eventually ending up with a continuous tone and solid red gimbal light - log would show aborted update.   Happened on two P3 Pro's.

Tried re downloading, formatting differently, different cards etc.  same ending.

Then I used the service bin file (sorry, check my posts for a link), then installed 1.4 and then 1.5.   That worked fine the first try on both!

Help! I may have screwed up here by updating the RC first because I didn't realise there was an update for the camera. I am wondering if there is a way of resetting the RC to factory defaults and then begin the whole process again. As things stand, it will not allow me to format the SD card in the camera, it says it times out every time I try and I use different cards. Also, lots of strange messages. First, on the initial screen, it shows an Inspire 1, not my P3P. I get message like "landing gear retracting".

marciano Posted at 2015-11-27 16:11
I formatted sd card using Go app.
Inserted it in my iMac and it is protected, I cannot copy anything ...

The Phantom 3 is only compatible with 32GB micro SD cards. It looks like you're attempting with a 64GB.

thebiomed.yahoo Posted at 2015-11-28 13:40
The Phantom 3 is only compatible with 32GB micro SD cards. It looks like you're attempting with a  ...

Not correct. The P3 supports cards up to 64GB.. I suggest he tries to format it in another computer then try again..

headkumquat Posted at 2015-11-28 08:12
Hi all. Having an unusual problem with the new f/w upgrade. At least I haven't come across anyone ha ...

Strange on.. The camera ( module [01 00] ) looks to be failing to update..

What do the logs show if you format the card and try again?

sploodge Posted at 2015-11-28 05:54
Strange on.. The camera ( module [01 00] ) looks to be failing to update..

What do the logs show  ...

Hi Sploodge;
tried several re-formats with two different cards, one of which was the original sd card provided by DJI. All results were exactly the same as the one I posted, aside from the sd card sn. All failed at the same point, module 01 00 (thanks for the info that that's the camera module. I had my suspicions, but wasn't sure) Do you know if there were any modifications done to the P3A camera with this firmware? We already had the 2.7k capability from a prior fw update.  As I said in my post, everything seems to work as far as the camera and quad are concerned, with just the "camera needs update" message coming up in the status display, and the f/w being reported as 1.4.10+. Hopefully I can do my calibrations today and take it up for a test flight. Will post back here on the results.

Thank you splodge. Clear, concise and informative. Thank you. Upgraded both Phantom and RC, no issues during updates. Flew 3 batteries and Phantom performed flawlessly.  

sploodge Posted at 2015-11-28 08:47
Not correct. The P3 supports cards up to 64GB.. I suggest he tries to format it in another computer ...

Interesting...Thanks for the correction. The guy who presented the DJI new pilot workshop told our class it was limited to 32GB.

64GB it is...even better!

headkumquat Posted at 2015-11-28 14:48
Hi Sploodge;
tried several re-formats with two different cards, one of which was the original sd c ...

Hi, not sure exactly what changed in the P3A in terms of the camera.. Strange that it only failing on that module.

Hopefully DHI-Amy or one of the other will chime in and maybe pass your problem on to R&D or suggest a fix..

All I could suggest is the method of forcing them P3 to "reinstall" the same firmware. Up to you to give it a go but since you say its working then maybe wait and see what DJI say

sploodge Posted at 2015-11-28 11:47
Not correct. The P3 supports cards up to 64GB.. I suggest he tries to format it in another computer ...

In Ubuntu gparted 'Format to exfat' is disbled

Edit: I formatted it in a friend's laptop (it has a sysOp called Windows)
After taking a test photo and video I could open them in MacOs but couldn't send them to trash


So I have entered into a loop: I have again a Read Only card.
I repeat, it reminds me Gopro 3+ where you have to format the card each time you have to delete files.

Finally, after reformatting it from DJI Go again but after performed upgrades I got "Read and Write" permission.
Thanks for your help.

Hi guys quick question. Just got my phantom p3 pro. Current firmware is 1.3.20. Should I update to 1.4 first before going for 1.5.3? Or just skip it and move immediately to 1.5.3? Thanks!