Firmware 1.3.20-DJI Go 2.0.0 App Discussion Thread

kriskhalil@hotm

rayrokni Posted at 2015-8-7 13:27
go to the settings and see what fw versions are installed please

I have my iPad with me, drone is locked away for safety as I am in a very remote location. Can't find the FW version on just the iPad/ DJI app. I had updated to 1.2.6 a few months ago with no issues.

rayrokni

kriskhalil@hotm Posted at 2015-8-7 13:35
I have my iPad with me, drone is locked away for safety as I am in a very remote location. Can't ...

wll when u get it , turn everything on and open the app go to the settings and see what fw vwesion ur p3 has,

kriskhalil@hotm

rayrokni Posted at 2015-8-7 13:38
wll when u get it , turn everything on and open the app go to the settings and see what fw vwesion ...

OK - will do. I assume its 1.2.6. I tried to revert back but no update was taking.

rayrokni

kriskhalil@hotm Posted at 2015-8-7 13:49
OK - will do. I assume its 1.2.6. I tried to revert back but no update was taking.

well, if your orig. fw was 126 and the new update132 did not work, the old fw will still be on the p3 and if u try to as u said downgrade to 126. its not going to do anything as it sees the 126fw same or older than the 126 already on it.
the original problem of loosing video could be because of a few other factors. i suggest leaving the update be til u get back, meanwhile take it out and see if you have good gps signal, chk your mod values in sensor settings, manually chk the compass bearing if u can, use ur smartphone and find north, mark a line and put the nose of p3 on that line and see if that corresponds correctly on the map view. make sure u have enabled multi flights in the settings( in case u need to go to atti mode). arm the motors and let it sit there for a few minutes. if you dont hear any odd noises or speed changes in the motor, take off manually and hover at six feet for a few minutes, again listen for any odd noises. then fly it at that altitude using all the different movements u can. basically use a whole battery for all the tests you can do, make sure you are videoing all the time. if all goes well then you gotta take it higher and further with the second battery. if u feel its doing everything ok then depends how brave u r in taking it out fully to video!!

good luck

jafarini

krasnoperovrw Posted at 2015-8-7 12:41
I do not work the remote control dji pilot, when you connect your smartphone or tablet to control pa ...

After firmware upgrade on my Drone and RC my P3A behaved similar. Then I tried reconnecting and I was requested by the Software DJI Pilot to allow RC connection. I marked always trust and since then everything works just fine.

Try to disable and enable again debugging on your device.

I am using Nexus 5 (Android 4.4.4)

jafarini

This is my experience on updating firmware to Firmware 1.3.20 on my DJI PHANTOM 3 ADVANCED

Drone was updated without any issues and process was smooth.

Following new Update instruction I tried to Update RC using my mobile device Nexus 5 (Android 4.4.4) but DJI Pilot doesn't allow me to do so.
There was kinda error message saying "It is not possible to update RC firmware from Mobile Device"

Then I switched back to old method and used Gimbal Card Reader for RC firmware update.
It took several minutes. I looked text logs and all good - Success.

Later did the update for the battery and success.

I went on the field for testing the drone after update and everything seems good!
I also noticed my Nexus 5 is not getting very hot anymore and also have not noticed any video lag.

Today my friend bought new battery for me and I have updated the firmware for this one as well.

I checked the logs and its says: Success
but dates are wrong. It shows 01.01.2014

Log records for previous updates are OK 06.08.2015 but for this new battery it is wrong.
Probably it will not affect anything.

Hope my experience will be useful for any member.

Thanks!

Booradley

dirk.liesenfeld Posted at 2015-8-5 18:06
Hi guys,
I was one of those, who couldn't use the drone anymore, because of a lot of issues: Unstabi ...

Hey Dirk,

I am also using the Samsung Galaxy Tab S and was wondering how you updated the remote control. I noticed in the pdf instructions it states to update through the DJI Go App, which is not available. Did you update via USB?

Btw, have you downgraded your google play services? I just reinstalled all of the updates believing the choppy, crashing, and laggy video was fixed with this update. Is that not the case?

Thanks!

jsfarms69@gmail

Booradley Posted at 2015-8-8 00:39
Hey Dirk,

I am also using the Samsung Galaxy Tab S and was wondering how you updated the remote c ...

What worked for me is connect the RC to the tab, turn on RC, then the Tab. (do not turn on the Phantom) Click the status icon (top Middle) and where you see "Update Required" click it and mine downloaded the new update for the RC. Then it asked if I want to install. Yes and the RC appeared to update. It will still say "Update Required".

I ran a test last night. I had Google services updates uninstalled and there was no lagging. So on the second flight I updated Google and 10 minutes into the flight I started to get bad lagging. On the third flight I uninstalled Google updates and everything was back to working good. Did have to reboot the Tab to get the maps to show.

Nemmo

Try to downgrade to 1.2.6. If it is not start the process then try to 1.1.9.
If result will be Sucess- repeat to update to 1.3.2
Allways use SD-Card witch was in box with the P3P/. So and format the card with windows to FAT32
Hope there will be successed

astrostar

jsfarms69@gmail Posted at 2015-8-8 01:56
What worked for me is connect the RC to the tab, turn on RC, then the Tab. (do not turn on the Pha ...

Just updated my P3P to the latest firmware and all went well

========== 2014.01.01 00:00:13 unsynchronized ======
Packet: P3X_FW_V01.03.0020.bin
Upgrading ...
Result: Success.

I then updated the RC (GL-300A) and the .TXT file read as follows...

P3_FW_GS_LOG.txt
[1438879181.341271] RC upgrade log:
[1438879189.430614] start upgrade 13
[1438879209.613434] success
[1438879212.630061] start upgrade 14
[1438879235.674370] success

P3_FW_RESULT_GS.txt
==========2015.08.06 16:39:41==========
Packet: /mnt/usb/P3X_FW_V01.03.0020.bin,
Upgrading ...
Result: Success

but having checked the DJ Pilot APP (Android) it still shows FW version as 1.2.0

The RC was updated using a USB stick directly in the USB port on the controller.

Is this correct or have I missed something ?

L8again

Your pilot app is 1.2.0 until they get the GO app out for android. FW is 1.3.2

astrostar

L8again Posted at 2015-8-8 04:01
Your pilot app is 1.2.0 until they get the GO app out for android. FW is 1.3.2

Hi L8again,
Thanks for the info. I thought I had to upgrade the RC with the new FW even though it's the Android app that I'm running, but I guess I shall have to wait for the Android version of the GO app to appear.

Just realised I'm confusing the RC firmware version with the Pilot app version - DOH !

Many Thanks.

Booradley

jsfarms69@gmail Posted at 2015-8-8 01:56
What worked for me is connect the RC to the tab, turn on RC, then the Tab. (do not turn on the Pha ...

Thank you, I'll give it a go in a few hours when I get out of work.

thisisafish

I guess I turned mine off before it was finished (yes yes - but was at party eager to fly) and the result was what looked liked a bricked battery and the P3 craft was beeping VERY loud and intense in a scary way.. The P3 craft did finally get into "normal beep" mode (after 15 minutes?) but then went into a long hissing noise for an hour - couldn't turn it off, so pulled the battery out.. Then I doinked in my spare battery, and it finally finished. The other battery was non-responsive pressing the button and in the charger, but when I inserted it into the craft it immediately started - so prepared the flash card again and thing is back to normal again now.. So:

1) Don't drink and firmware!
2) The upgrade takes a long time - especially if you do wrong
3) If it fails - the P3 is actaully very good at self-resetting etc. (very hard to brick?) - nice
4) The DJI engineers has invented a lot of flashing and beeping modes - including really loud ones

hundleton1

Guys with the firmware its this easy,

Craft, Look at the led on the front of the gimbal

Flashing Green/Red Update in Progress
Solid Green Update complete
Solid Red Update failed

Controller

Solid Blue in Progress
Solid Green When Complete

Follow this and you should not be able to go wrong.

fred

hundleton1 Posted at 2015-8-8 07:25
Guys with the firmware its this easy,

Craft, Look at the led on the front of the gimbal

ok, so the update is failing.....looks like some component has failed and has not been detected. But, it should not cause the update to fail...but it has. Wish I knew what failed.

[00015212]Version checking[1]...
[00015320][03 05][00] v34.2.0.9 -> v34.2.0.9
[00015425][03 06][00] v2.2.6.19 -> v2.2.6.19
[00015487][04 00][00] v1.40.0.0 -> v1.40.0.0
[00015576][09 00][00] v1.7.0.3 -> v1.7.0.3
[00015719][11 00][00] v1.7.0.0 -> v1.7.0.0
[00015833][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015929][12 01][00] v1.8.0.0 -> v1.8.0.0
[00016032][12 02][00] v1.8.0.0 -> v1.8.0.0
[00016159][12 03][00] v1.8.0.0 -> v1.8.0.0
[00028717][15 00][00] device not detected.
[00028824][17 00][00] v1.1.1.7 -> v1.1.1.7
[00028969][17 01][00] v1.0.2.7 -> v1.0.2.7
[00029043][19 00][00] v1.0.8.96 -> v1.0.8.96
[00029101][01 00][00] v1.23.3419 -> v1.23.3419
[00029159][01 01][00] v1.23.3419 -> v1.23.3419
[00041714][08 00][00] device not detected.
[00041771]Packet upgrade failed at version checking.

mpdigiman

Took out my Phantom 3 pro tiday after doing the update followed by IMU & Gimbal. Calibration.

kriskhalil@hotm

rayrokni Posted at 2015-8-7 14:07
well, if your orig. fw was 126 and the new update132 did not work, the old fw will still be on the ...

But I can't video! the gimbal droops. The APP doesn't even recognize that I have an SD card in there!

kriskhalil@hotm

I've tried all of these suggestions guys. Im starting to get worried I will not be able to fly on my trip in paradise! :-(

mpdigiman

Took up my Phantom 3 pro today after doing the update followed by IMU & Gimbal Calibration. All went well but on two occasions i got lost rc signal. This was for a split second each time i was surprised to see that the video recorded shows horizontal flikering lines in two places on the clip. I put this down to the lost signal. Can someone confirm if the split second loss of signal caused this? I would have thought the video would not habe been affected since the recording started at take-off...and finished before landing..... Confused?.

kriskhalil@hotm

The Gimbal LEDs do not work anymore...

ScottyT

fred Posted at 2015-8-8 08:55
ok, so the update is failing.....looks like some component has failed and has not been detected. ...

That doesn't look good. I've not been following the firmware upgrade issues but that looks like you'll have to contact DJI for help.

coastodian

1.3.20 update

P3A

the craft has updated (according to the lights and the txt file

unable to update the RC, either via the app (version 2.0.0), or via the USB card reader.
model is GL 300A

app says i cannot update via app, use card reader.

when I plug in card reader, boot rc, the status light never goes to blue, always stays red.
after a about 5 minutes, the RC starts beeping loudly
tried it 3 times, same result with app or card reader

P3P

I am unable to update the craft.

The lights alternate from red to green for as long as up to an hour. Sometimes for a moment it stays solid green, then goes off, then alternates again. Always with the D-D-D-D sound

Nothing has ever been written to a txt file on the card.

have reformatted card twice (exFat), same result.

controller will not update either (GL 300A)

So, out of 2 craft, 2 RC, I am only able to update the P3A to the latest FW. Ap on ipad is at 2.0.0

Any tips?

The P3P is going back to the dealer.

-----
-----

more data

used entirely different CF card from my DSLR, formatted it to exFat, copied P3A FW to it and was able to update P3A remote.

deleted P3A FW, replaced it with P3P FW and was able to update P3P RC.

formatted the 16 GB lexar card that came with P3P, copied FW for P3P to it and insterted in P3P, started up.

very loud BEEP BEEP for about 5 minutes, then it went to normal low level D-D-D-D sound of update for about 3 min, then did D-DD sound and light on gimbal went solid green.
txt files said success, yet, when I connect RC to it, the app says the upgrade failed and to do it again.

So I am inserted same card from above. Craft is silent, ginmbal light is solid green.

txt file said:

========== 2015.08.07 21:30:07 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Corrupted.
Firmware bin file is corrupted, download it again from the DJI offical website.

========== 2015.08.07 21:35:40 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft..

So I download again

Craft is silent and light is solid green.

Now txt files says:

========== 2015.08.07 21:51:11 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

DJI should be paying me to debug their product

any tips from the experts are appreciated.

thank you

hundleton1

fred Posted at 2015-8-8 08:55
ok, so the update is failing.....looks like some component has failed and has not been detected. ...

it looks like there may be an issue with the firmware update, a few reports are coming of the same error, hold off a few days its been passed back by Ed,

sorry not the ideal answer but hopefully its something they can fix in fw quickly

sploodge

just an option coastodian, can you format the SD card using the DJI App, put the firmware BIN on it and try updating again.

Also, after whatever happens or not, can you look for a hidden folder on the SD card called /MISC/LOG and post the contents of any TXT file in there also. Its a long shot but has resolved this issue for some.

Like hundleton says, two VERY similar cases has been identified and passed to DJI and there might be a few not classified as the same issue too. The TXT file in the /MISC/LOG gives much more detail.

Sorry you are having this issue, its been a fairly smooth one for most..

coastodian

Thanks for your time and ideas guys.

here is contents of the file you ask for:

[00012230][01 00] Firmware upgrade finished successfully.
[00012361]Done.

[00012389]Packet [C:\P3X_FW_V01.02.0006.bin] resumed, card sn [0x90ce4ad2].
[00012422]Version checking[2]...
[00012484][03 05][00] v34.2.0.8 -> v34.2.0.9 need upgrade.
[00012540][03 06][00] v2.1.6.18 -> v2.2.6.8 need upgrade.
[00012577][04 00][00] v1.36.0.0 -> v1.38.0.0 need upgrade.
[00012623][09 00][00] v1.7.0.3 -> v1.7.0.3
[00012740][11 00][00] v1.6.0.0 -> v1.6.0.0
[00012807][12 00][00] v1.8.0.0 -> v1.8.0.0
[00012892][12 01][00] v1.8.0.0 -> v1.8.0.0
[00012973][12 02][00] v1.8.0.0 -> v1.8.0.0
[00013047][12 03][00] v1.8.0.0 -> v1.8.0.0
[00013171][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013247][17 00][00] v1.1.1.2 -> v1.1.1.6 need upgrade.
[00013367][17 01][00] v1.0.2.4 -> v1.0.2.5 need upgrade.
[00013422][19 00][00] v1.0.8.59 -> v1.0.8.96 need upgrade.
[00013450][01 00][05] v1.15.3056 -> v1.15.3056
[00013487][01 01][00] v1.6.2736 -> v1.15.3056 need upgrade
[00013529][08 00][00] v0.11.0.4 -> v0.11.0.4
[00013558]Done.

[00013585]Firmware upgrading[2]...
[00013732][01 01] Firmware upgrade start...
[00043987][01 01] Firmware upgrade finished successfully.
[00044043][17 00] Firmware upgrade start...
[00134368][17 00] Firmware upgrade finished successfully.
[00134411][17 01] Firmware upgrade start...
[00197212][17 01] Firmware upgrade finished successfully.
[00197260][03 05] Firmware upgrade start...
[00269990][03 05] Firmware upgrade finished successfully.
[00270205][03 06] Firmware upgrade start...
[00560321][03 06] Firmware upgrade finished successfully.
[00563127][19 00] Firmware upgrade start...
[00729502][19 00] Firmware upgrade finished successfully.
[00729566][04 00] Firmware upgrade start...
[00787131][04 00] Firmware upgrade finished successfully.
[00787160]Done.

[00787191]Version checking[3]...
[00787295][03 05][05] v34.2.0.9 -> v34.2.0.9
[00787370][03 06][05] v2.2.6.8 -> v2.2.6.8
[00787406][04 00][05] v1.38.0.0 -> v1.38.0.0
[00787471][09 00][00] v1.7.0.3 -> v1.7.0.3
[00787670][11 00][00] v1.6.0.0 -> v1.6.0.0
[00787765][12 00][00] v1.8.0.0 -> v1.8.0.0
[00787844][12 01][00] v1.8.0.0 -> v1.8.0.0
[00787919][12 02][00] v1.8.0.0 -> v1.8.0.0
[00788004][12 03][00] v1.8.0.0 -> v1.8.0.0
[00788144][15 00][00] v1.1.2.0 -> v1.1.2.0
[00788219][17 00][05] v1.1.1.6 -> v1.1.1.6
[00788340][17 01][05] v1.0.2.5 -> v1.0.2.5
[00788391][19 00][05] v1.0.8.96 -> v1.0.8.96
[00788428][01 00][05] v1.15.3056 -> v1.15.3056
[00788458][01 01][05] v1.15.3056 -> v1.15.3056
[00788498][08 00][00] v0.11.0.4 -> v0.11.0.4
[00788525]Packet upgrade finish successfully.

[00013407]========== 2015.07.04 17:27:18. boot(15) ============
[00013518]Packet [C:\P3X_FW_V01.02.0006.bin] detected, card sn [0x90ce4ad2].
[00013626]Packet upgrade start...

[00013769]Packet checking...
[00013879]Done.

[00013935]Version checking[1]...
[00014077][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014238][03 06][00] v2.2.6.8 -> v2.2.6.8
[00014379][04 00][00] v1.38.0.0 -> v1.38.0.0
[00014556][09 00][00] v1.7.0.3 -> v1.7.0.3
[00014744][11 00][00] v1.6.0.0 -> v1.6.0.0
[00014910][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015067][12 01][00] v1.8.0.0 -> v1.8.0.0
[00015190][12 02][00] v1.8.0.0 -> v1.8.0.0
[00015267][12 03][00] v1.8.0.0 -> v1.8.0.0
[00015414][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015507][17 00][00] v1.1.1.6 -> v1.1.1.6
[00015627][17 01][00] v1.0.2.5 -> v1.0.2.5
[00015674][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015708][01 00][00] v1.15.3056 -> v1.15.3056
[00015745][01 01][00] v1.15.3056 -> v1.15.3056
[00015799][08 00][00] v0.11.0.4 -> v0.11.0.4
[00015833]Packet upgrade cancelled at version checking.

[00013403]========== 2015.07.04 17:40:36. boot(15) ============
[00013504]Packet [C:\P3X_FW_V01.02.0006.bin] detected, card sn [0x90ce4ad2].
[00013552]Packet upgrade start...

[00013695]Packet checking...
[00013800]Done.

[00013913]Version checking[1]...
[00014045][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014206][03 06][00] v2.2.6.8 -> v2.2.6.8
[00014455][04 00][00] v1.38.0.0 -> v1.38.0.0
[00014559][09 00][00] v1.7.0.3 -> v1.7.0.3
[00014742][11 00][00] v1.6.0.0 -> v1.6.0.0
[00014915][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015071][12 01][00] v1.8.0.0 -> v1.8.0.0
[00015238][12 02][00] v1.8.0.0 -> v1.8.0.0
[00015400][12 03][00] v1.8.0.0 -> v1.8.0.0
[00015618][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015774][17 00][00] v1.1.1.6 -> v1.1.1.6
[00015926][17 01][00] v1.0.2.5 -> v1.0.2.5
[00015980][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016017][01 00][00] v1.15.3056 -> v1.15.3056
[00016054][01 01][00] v1.15.3056 -> v1.15.3056
[00016094][08 00][00] v0.11.0.4 -> v0.11.0.4
[00016131]Packet upgrade cancelled at version checking.

[00013040]========== 2015.07.04 17:42:20. boot(15) ============
[00013075]Packet [C:\P3X_FW_V01.02.0006.bin] detected, card sn [0x90ce4ad2].
[00013112]Packet upgrade start...

[00013161]Packet checking...
[00013203]Done.

[00013240]Version checking[1]...
[00013308][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013393][03 06][00] v2.2.6.8 -> v2.2.6.8
[00013437][04 00][00] v1.38.0.0 -> v1.38.0.0
[00013487][09 00][00] v1.7.0.3 -> v1.7.0.3
[00013613][11 00][00] v1.6.0.0 -> v1.6.0.0
[00013704][12 00][00] v1.8.0.0 -> v1.8.0.0
[00013803][12 01][00] v1.8.0.0 -> v1.8.0.0
[00013903][12 02][00] v1.8.0.0 -> v1.8.0.0
[00014003][12 03][00] v1.8.0.0 -> v1.8.0.0
[00014143][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014238][17 00][00] v1.1.1.6 -> v1.1.1.6
[00014357][17 01][00] v1.0.2.5 -> v1.0.2.5
[00014407][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014441][01 00][00] v1.15.3056 -> v1.15.3056
[00014476][01 01][00] v1.15.3056 -> v1.15.3056
[00014527][08 00][00] v0.11.0.4 -> v0.11.0.4
[00014561]Packet upgrade cancelled at version checking.

[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000830][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000833][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000833][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000833][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000833][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00000831][01 00] Firmware upgrade finished failed (step = 3, err = 0xffffffff).
[00012428]========== remo-con disconnect. boot(15) ============
[00012469]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x28a78402].
[00012506]Packet upgrade start...

[00012557]Packet checking...
[00012592]Packet vlink 01.03.0020 <-> 01.01.0009.
[00012664]Done.

[00012700]Version checking[1]...
[00012765][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012841][03 06][00] v2.2.6.8 -> v2.2.6.19 need upgrade.
[00012883][04 00][00] v1.38.0.0 -> v1.40.0.0 need upgrade.
[00012944][09 00][00] v1.7.0.3 -> v1.7.0.3
[00013064][11 00][00] v1.6.1.0 -> v1.7.0.0 need upgrade.
[00013154][12 00][00] v1.8.0.0 -> v1.8.0.0
[00013230][12 01][00] v1.8.0.0 -> v1.8.0.0
[00013320][12 02][00] v1.8.0.0 -> v1.8.0.0
[00013394][12 03][00] v1.8.0.0 -> v1.8.0.0
[00013531][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013612][17 00][00] v1.1.1.6 -> v1.1.1.7 need upgrade.
[00013730][17 01][00] v1.0.2.5 -> v1.0.2.7 need upgrade.
[00013784][19 00][00] v1.0.8.96 -> v1.0.8.96
[00013834][01 00][00] v1.23.3419 -> v1.23.3419
[00013869][01 01][00] v1.15.3056 -> v1.23.3419 need upgrade
[00013919][08 00][00] v0.11.0.4 -> v0.12.0.4 need upgrade.
[00013959]Done.

[00015996]Waiting for user confirm...
[00026032]Timeout, start upgrade automatically.

[00026099]Firmware upgrading[1]...
[00026248][01 01] Firmware upgrade start...
[00056475][01 01] Firmware upgrade finished successfully.
[00064432][08 00] Firmware upgrade start...
[00573646][08 00] Firmware upgrade finished successfully.
[00582292][17 00] Firmware upgrade start...
[00708609][17 00] Firmware upgrade finished successfully.
[00717229][17 01] Firmware upgrade start...
[00797071][17 01] Firmware upgrade finished successfully.
[00805679][11 00] Firmware upgrade start...
[00863965][11 00] Firmware upgrade finished successfully.
[00872742][03 06] Firmware upgrade start...
[00012633]========== remo-con disconnect. boot(15) ============
[00012673]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x90ce4ad2].
[00012718]Packet upgrade start...

[00012766]Packet checking...
[00012805]Packet vlink 01.03.0020 <-> 01.01.0009.
[00012878]Done.

[00012924]Version checking[1]...
[00012998][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013058][03 06][00] v0.0.0.0 -> v2.2.6.19 need upgrade.
[00013106][04 00][00] v1.38.0.0 -> v1.40.0.0 need upgrade.
[00013168][09 00][00] v1.7.0.3 -> v1.7.0.3
[00025711][11 00][00] device not detected.
[00038253][12 00][00] device not detected.
[00050790][12 01][00] device not detected.
[00063345][12 02][00] device not detected.
[00075882][12 03][00] device not detected.
[00076037][15 00][00] v1.1.2.0 -> v1.1.2.0
[00088579][17 00][00] device not detected.
[00101116][17 01][00] device not detected.
[00101193][19 00][00] v1.0.8.96 -> v1.0.8.96
[00101233][01 00][00] v1.23.3419 -> v1.23.3419
[00101280][01 01][00] v1.23.3419 -> v1.23.3419
[00101340][08 00][00] v0.12.0.4 -> v0.12.0.4
[00101380]Done.

[00103418]Waiting for user confirm...
[00113458]Timeout, start upgrade automatically.

[00113533]Firmware upgrading[1]...
[00113741][03 06] Firmware upgrade start...
[00410059][03 06] Firmware upgrade finished successfully.
[00410128][04 00] Firmware upgrade start...
[00467927][04 00] Firmware upgrade finished successfully.
[00467970]Done.

[00468010]Version checking[2]...
[00468092][03 05][00] v34.2.0.9 -> v34.2.0.9
[00468172][03 06][05] v2.2.6.19 -> v2.2.6.19
[00468216][04 00][05] v1.40.0.0 -> v1.40.0.0
[00468273][09 00][00] v1.7.0.3 -> v1.7.0.3
[00468397][11 00][00] v1.6.0.0 -> v1.7.0.0 need upgrade.
[00468482][12 00][00] v1.8.0.0 -> v1.8.0.0
[00468563][12 01][00] v1.8.0.0 -> v1.8.0.0
[00468673][12 02][00] v1.8.0.0 -> v1.8.0.0
[00468762][12 03][00] v1.8.0.0 -> v1.8.0.0
[00468899][15 00][00] v1.1.2.0 -> v1.1.2.0
[00468997][17 00][00] v1.1.1.7 -> v1.1.1.7
[00469122][17 01][00] v1.0.2.7 -> v1.0.2.7
[00469274][19 00][00] v1.0.8.96 -> v1.0.8.96
[00469315][01 00][00] v1.23.3419 -> v1.23.3419
[00469356][01 01][00] v1.23.3419 -> v1.23.3419
[00469405][08 00][00] v0.12.0.4 -> v0.12.0.4
[00469448]Done.

[00469488]Firmware upgrading[2]...
[00469543][11 00] Firmware upgrade start...
[00517670][11 00] Firmware upgrade finished successfully.
[00517710]Done.

[00517751]Version checking[3]...
[00517835][03 05][00] v34.2.0.9 -> v34.2.0.9
[00517915][03 06][05] v2.2.6.19 -> v2.2.6.19
[00517967][04 00][05] v1.40.0.0 -> v1.40.0.0
[00518034][09 00][00] v1.7.0.3 -> v1.7.0.3
[00518157][11 00][05] v1.7.0.0 -> v1.7.0.0
[00518244][12 00][00] v1.8.0.0 -> v1.8.0.0
[00518324][12 01][00] v1.8.0.0 -> v1.8.0.0
[00518470][12 02][00] v1.8.0.0 -> v1.8.0.0
[00518570][12 03][00] v1.8.0.0 -> v1.8.0.0
[00518697][15 00][00] v1.1.2.0 -> v1.1.2.0
[00518786][17 00][00] v1.1.1.7 -> v1.1.1.7
[00518925][17 01][00] v1.0.2.7 -> v1.0.2.7
[00518996][19 00][00] v1.0.8.96 -> v1.0.8.96
[00519035][01 00][00] v1.23.3419 -> v1.23.3419
[00519077][01 01][00] v1.23.3419 -> v1.23.3419
[00519131][08 00][00] v0.12.0.4 -> v0.12.0.4
[00519176]Packet upgrade finish successfully.

[00088455]========== 2015.08.07 21:30:24. boot(15) ============
[00088492]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x28a78402].
[00088529]Packet upgrade start...

[00088568]Packet upgrade failed at packet checking.

[00012529]========== 2015.08.07 21:35:41. boot(15) ============
[00012568]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x90ce4ad2].
[00012613]Packet upgrade start...

[00012661]Packet checking...
[00012700]Packet vlink 01.03.0020 <-> 01.01.0009.
[00012740]Record vlink 01.03.0020 <-> 01.01.0009 (flow = 0).
[00012785]Done.

[00012825]Version checking[1]...
[00012912][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012993][03 06][00] v2.2.6.19 -> v2.2.6.19
[00013043][04 00][00] v1.40.0.0 -> v1.40.0.0
[00013112][09 00][00] v1.7.0.3 -> v1.7.0.3
[00013232][11 00][00] v1.7.0.0 -> v1.7.0.0
[00013412][12 00][00] v1.8.0.0 -> v1.8.0.0
[00013512][12 01][00] v1.8.0.0 -> v1.8.0.0
[00013601][12 02][00] v1.8.0.0 -> v1.8.0.0
[00013711][12 03][00] v1.8.0.0 -> v1.8.0.0
[00013875][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013976][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014117][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014175][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014218][01 00][00] v1.23.3419 -> v1.23.3419
[00014285][01 01][00] v1.23.3419 -> v1.23.3419
[00014333][08 00][00] v0.12.0.4 -> v0.12.0.4
[00014377]Packet upgrade cancelled at version checking.

[00012527]========== 2015.08.07 21:51:12. boot(15) ============
[00012568]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x90ce4ad2].
[00012613]Packet upgrade start...

[00012662]Packet checking...
[00012701]Packet vlink 01.03.0020 <-> 01.01.0009.
[00012743]Record vlink 01.03.0020 <-> 01.01.0009 (flow = 0).
[00012788]Done.

[00012828]Version checking[1]...
[00012915][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012996][03 06][00] v2.2.6.19 -> v2.2.6.19
[00013048][04 00][00] v1.40.0.0 -> v1.40.0.0
[00013115][09 00][00] v1.7.0.3 -> v1.7.0.3
[00013241][11 00][00] v1.7.0.0 -> v1.7.0.0
[00013335][12 00][00] v1.8.0.0 -> v1.8.0.0
[00013436][12 01][00] v1.8.0.0 -> v1.8.0.0
[00013536][12 02][00] v1.8.0.0 -> v1.8.0.0
[00013630][12 03][00] v1.8.0.0 -> v1.8.0.0
[00013783][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013884][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014030][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014094][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014144][01 00][00] v1.23.3419 -> v1.23.3419
[00014185][01 01][00] v1.23.3419 -> v1.23.3419
[00014280][08 00][00] v0.12.0.4 -> v0.12.0.4
[00014318]Packet upgrade cancelled at version checking.

fred

coastodian Posted at 2015-8-8 23:51
Thanks for your time and ideas guys.

here is contents of the file you ask for:

Mine is similar but a little different. I always have the .bin on my sd card so I can see all my boot ups.  I see that everything was happy with 1.2.6 but then, out of the blue, it gives this message:
[00014473]========== remo-con disconnect. boot(15) ============
now there are two device not detected messages in the list:
[00027975][15 00][00] device not detected.
[00040967][08 00][00] device not detected.
I must have power cycled the craft because while the next boot says:
[00012486]========== remo-con disconnect. boot(15) ============
it does not have the device not detected, instead it shows those two devices as being on the current version.
And things are happy for a while, until 1.3.2 when I get the remo-con message and then the following.  I don't know if the subcomponent has a failed bit of the firm ware or what but I do know one thing:
I can't downgrade because the package bails on the version checking before it even sees to downgrade.  here is the rest of the log, there is more but it is just the same thing with device not detected on the two items.
[00014480]========== remo-con disconnect. boot(15) ============
[00014519]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x88f02ae8].
[00014560]Packet upgrade start...

[00014607]Packet checking...
[00014646]Done.

[00014686]Version checking[1]...
[00014762][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014842][03 06][00] v2.2.6.8 -> v2.2.6.19 need upgrade.
[00014887][04 00][00] v1.38.0.0 -> v1.40.0.0 need upgrade.
[00014936][09 00][00] v1.7.0.3 -> v1.7.0.3
[00015060][11 00][00] v1.6.0.0 -> v1.7.0.0 need upgrade.
[00015150][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015250][12 01][00] v1.8.0.0 -> v1.8.0.0
[00015433][12 02][00] v1.8.0.0 -> v1.8.0.0
[00015530][12 03][00] v1.8.0.0 -> v1.8.0.0
[00028070][15 00][00] device not detected.
[00028166][17 00][00] v1.1.1.6 -> v1.1.1.7 need upgrade.
[00028306][17 01][00] v1.0.2.5 -> v1.0.2.7 need upgrade.
[00028377][19 00][00] v1.0.8.96 -> v1.0.8.96
[00028420][01 00][00] v1.15.3056 -> v1.23.3419 need upgrade
[00028464][01 01][00] v1.15.3056 -> v1.23.3419 need upgrade
[00041009][08 00][00] device not detected.
[00041051]Done.

[00043094]Waiting for user confirm...
[00053136]Timeout, start upgrade automatically.

[00053228]Firmware upgrading[1]...
[00064805][01 00] Firmware upgrade start...
[00014238][01 00] Firmware upgrade finished successfully.
[00014280]Done.

[00014322]Packet [C:\P3X_FW_V01.03.0020.bin] resumed, card sn [0x88f02ae8].
[00014366]Packet vlink 01.03.0020 <-> 01.01.0009.
[00014440]Version checking[2]...
[00014524][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014604][03 06][00] v2.2.6.8 -> v2.2.6.19 need upgrade.
[00014657][04 00][00] v1.38.0.0 -> v1.40.0.0 need upgrade.
[00014719][09 00][00] v1.7.0.3 -> v1.7.0.3
[00014844][11 00][00] v1.6.0.0 -> v1.7.0.0 need upgrade.
[00014933][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015033][12 01][00] v1.8.0.0 -> v1.8.0.0
[00015133][12 02][00] v1.8.0.0 -> v1.8.0.0
[00015233][12 03][00] v1.8.0.0 -> v1.8.0.0
[00027777][15 00][00] device not detected.
[00027874][17 00][00] v1.1.1.6 -> v1.1.1.7 need upgrade.
[00028015][17 01][00] v1.0.2.5 -> v1.0.2.7 need upgrade.
[00028080][19 00][00] v1.0.8.96 -> v1.0.8.96
[00028125][01 00][05] v1.23.3419 -> v1.23.3419
[00028167][01 01][00] v1.15.3056 -> v1.23.3419 need upgrade
[00040709][08 00][00] device not detected.
[00040750]Done.

[00040794]Firmware upgrading[2]...
[00040937][01 01] Firmware upgrade start...
[00071186][01 01] Firmware upgrade finished successfully.
[00071253][17 00] Firmware upgrade start...
[00161781][17 00] Firmware upgrade finished successfully.
[00161837][17 01] Firmware upgrade start...
[00228320][17 01] Firmware upgrade finished successfully.
[00228369][11 00] Firmware upgrade start...
[00277595][11 00] Firmware upgrade finished successfully.
[00277810][03 06] Firmware upgrade start...
[00573141][03 06] Firmware upgrade finished successfully.
[00573208][04 00] Firmware upgrade start...
[00630756][04 00] Firmware upgrade finished successfully.
[00630796]Done.

[00630838]Version checking[3]...
[00630922][03 05][00] v34.2.0.9 -> v34.2.0.9
[00631002][03 06][05] v2.2.6.19 -> v2.2.6.19
[00631060][04 00][05] v1.40.0.0 -> v1.40.0.0
[00631116][09 00][00] v1.7.0.3 -> v1.7.0.3
[00631245][11 00][05] v1.7.0.0 -> v1.7.0.0
[00631345][12 00][00] v1.8.0.0 -> v1.8.0.0
[00631431][12 01][00] v1.8.0.0 -> v1.8.0.0
[00631515][12 02][00] v1.8.0.0 -> v1.8.0.0
[00631616][12 03][00] v1.8.0.0 -> v1.8.0.0
[00644159][15 00][00] device not detected.
[00644251][17 00][05] v1.1.1.7 -> v1.1.1.7
[00644391][17 01][05] v1.0.2.7 -> v1.0.2.7
[00644457][19 00][00] v1.0.8.96 -> v1.0.8.96
[00644499][01 00][05] v1.23.3419 -> v1.23.3419
[00644541][01 01][05] v1.23.3419 -> v1.23.3419
[00657084][08 00][00] device not detected.
[00657125]Packet upgrade failed at version checking.

[00014528]========== remo-con disconnect. boot(15) ============
[00014571]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x88f02ae8].
[00014616]Packet upgrade start...

[00014662]Packet checking...
[00014703]Packet vlink 01.03.0020 <-> 01.01.0009.
[00014777]Done.

[00014818]Version checking[1]...
[00014895][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014974][03 06][00] v2.2.6.19 -> v2.2.6.19
[00015023][04 00][00] v1.40.0.0 -> v1.40.0.0
[00015080][09 00][00] v1.7.0.3 -> v1.7.0.3
[00015195][11 00][00] v1.7.0.0 -> v1.7.0.0
[00015310][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015409][12 01][00] v1.8.0.0 -> v1.8.0.0
[00015509][12 02][00] v1.8.0.0 -> v1.8.0.0
[00015609][12 03][00] v1.8.0.0 -> v1.8.0.0
[00028153][15 00][00] device not detected.
[00028241][17 00][00] v1.1.1.7 -> v1.1.1.7
[00028463][17 01][00] v1.0.2.7 -> v1.0.2.7
[00028520][19 00][00] v1.0.8.96 -> v1.0.8.96
[00028565][01 00][00] v1.23.3419 -> v1.23.3419
[00028609][01 01][00] v1.23.3419 -> v1.23.3419
[00041151][08 00][00] device not detected.
[00041193]Packet upgrade failed at version checking.

[00014481]========== remo-con disconnect. boot(15) ============
[00014523]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0x88f02ae8].
[00014566]Packet upgrade start...

[00014610]Packet checking...
[00014650]Packet vlink 01.03.0020 <-> 01.01.0009.
[00014727]Done.

[00014769]Version checking[1]...
[00014851][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014933][03 06][00] v2.2.6.19 -> v2.2.6.19
[00014981][04 00][00] v1.40.0.0 -> v1.40.0.0
[00015056][09 00][00] v1.7.0.3 -> v1.7.0.3
[00015171][11 00][00] v1.7.0.0 -> v1.7.0.0
[00015260][12 00][00] v1.8.0.0 -> v1.8.0.0
[00015340][12 01][00] v1.8.0.0 -> v1.8.0.0
[00015425][12 02][00] v1.8.0.0 -> v1.8.0.0
[00015525][12 03][00] v1.8.0.0 -> v1.8.0.0
[00028069][15 00][00] device not detected.
[00028161][17 00][00] v1.1.1.7 -> v1.1.1.7
[00028282][17 01][00] v1.0.2.7 -> v1.0.2.7
[00028336][19 00][00] v1.0.8.96 -> v1.0.8.96
[00028380][01 00][00] v1.23.3419 -> v1.23.3419
[00028423][01 01][00] v1.23.3419 -> v1.23.3419
[00040963][08 00][00] device not detected.
[00041004]Packet upgrade failed at version checking.

:

sploodge

coastodian Posted at 2015-8-8 23:51
Thanks for your time and ideas guys.

here is contents of the file you ask for:

The last section at the bottom of this log shows it updated OK..

fred

sploodge Posted at 2015-8-9 00:34
The last section at the bottom of this log shows it updated OK..

his is ok, mine just continually gets the device not detected...while everything works except video from the camera.

sploodge

fred Posted at 2015-8-9 00:48
his is ok, mine just continually gets the device not detected...while everything works except vide ...

Hi Fred..

can you format the SD card when its in the Phantom using the DJI App. Then put the firmware back on it and try again..

sploodge

Actually Fred.. I see Ed had got back to another user about this issue here - http://www.rcgroups.com/forums/s ... 969&postcount=30879 - I would wait and see what comes of this.. By all means give the option above a go though..

fred

sploodge Posted at 2015-8-9 01:03
Actually Fred.. I see Ed had got back to another user about this issue here - http://www.rcgroups.co ...

hmm, can't wait. thanks for the heads up. Oh, and I have formatter the card using the app, with the sdcard in the craft, everything, result is the same, result file says
========== 2015.08.08 13:30:50 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

log file says:
[00014815]========== 2015.08.08 13:30:51. boot(15) ============
[00014902]Packet [C:\P3X_FW_V01.03.0020.bin] detected, card sn [0xb0ce0ac2].
[00014959]Packet upgrade start...

[00015018]Packet checking...
[00015089]Packet vlink 01.03.0020 <-> 01.01.0009.
[00015184]Done.

[00015254]Version checking[1]...
[00015358][03 05][00] v34.2.0.9 -> v34.2.0.9
[00015477][03 06][00] v2.2.6.19 -> v2.2.6.19
[00015553][04 00][00] v1.40.0.0 -> v1.40.0.0
[00015633][09 00][00] v1.7.0.3 -> v1.7.0.3
[00015858][11 00][00] v1.7.0.0 -> v1.7.0.0
[00015992][12 00][00] v1.8.0.0 -> v1.8.0.0
[00016127][12 01][00] v1.8.0.0 -> v1.8.0.0
[00016253][12 02][00] v1.8.0.0 -> v1.8.0.0
[00016372][12 03][00] v1.8.0.0 -> v1.8.0.0
[00028942][15 00][00] device not detected.
[00029066][17 00][00] v1.1.1.7 -> v1.1.1.7
[00029227][17 01][00] v1.0.2.7 -> v1.0.2.7
[00029317][19 00][00] v1.0.8.96 -> v1.0.8.96
[00029382][01 00][00] v1.23.3419 -> v1.23.3419
[00029447][01 01][00] v1.23.3419 -> v1.23.3419
[00042011][08 00][00] device not detected.
[00042072]Packet upgrade failed at version checking.

Booradley

jsfarms69@gmail Posted at 2015-8-8 01:56
What worked for me is connect the RC to the tab, turn on RC, then the Tab. (do not turn on the Pha ...

Do you have the Samsung Galaxy Tab S (mine 8.4)?

I can confirm that you cannot update the RC through the application with the Samsung Galaxy Tab S 8.4.

Nemmo

sploodge Posted at 2015-8-4 18:50
Here is an entire FW Upgrade video ( its long and boring but shows the phases the P3 goes through ). ...

Hello everybody.  About upgrade the batteries. So, when You upgrade firmware you don't see anything according to battery upgrade. Any add. lights or some special DDD..
But if You put in the new batt(not  current FW one) You will monitor the upgrade process.
After24 sec since Power On P3. DDD...DDD will appear and LED on camera starts blink red/green.
On the battery  some seconds later the second LED starts to blink and third will light stadly.
All will be finished in a 1:30min approx.. Camera LED becomes solid green and D..DD.. will be hear.
So, there is entire video.

warrenkevin18@g

Has anyone experienced any differences in relation to the no fly zones?

sploodge

warrenkevin18@g Posted at 2015-8-9 02:46
Has anyone experienced any differences in relation to the no fly zones?

Not me.. But I do live where there is only ONE NFZ and its an RAF base so don't do too near to it

warrenkevin18@g

sploodge Posted at 2015-8-9 02:54
Not me.. But I do live where there is only ONE NFZ and its an RAF base so don't do too near to it ...

I was in a restricted zone today where my Alt is usually limited to 36m but today I wasn't promoted in the DJI go app and it continued above the limit, strange.

cellulit@gmail.

This damn upgrade takes so long, that in a moment the battery will go to zero. Camera led is solid green, but P3P is still making its old printer sound and blinking. I'll let it die and then see the results. Whatever it is, someone broke it. None of previous upgrades was that complicated and misleading.

Edit: my wife went nuts and I had to manually turn it off. Log says success. We'll see that in field tomorrow.

suaveaerial

Just curious - I don't even see the DJI Pilot app available for download anymore from the DJI website, just the Android version coming soon for DJI GO. Is it advisable to still update the firmware on the aircraft and the RC? Or wait until the Android version? Took the aircraft out today and noticed there was a firmware update required and I was unable to calibrate the compass while this message was displayed. I'm pretty OCD about calibrating the compass before each flight so was a little nervous.

cellulit@gmail.

suaveaerial Posted at 2015-8-9 07:30
Just curious - I don't even see the DJI Pilot app available for download anymore from the DJI websit ...

I had same situation today and I WAS ABLE to calibrate before safely flying (and before upgrading). The firmware message isn't a show-stopper.