Firmware version weirdness (updated to 1.6.0040 but version shown as 1.3.20+)

Joined
May 12, 2015
Messages
18
Reaction score
0
Age
52
Hi All,

Just wondering if anyone can help me.
I've not flown my Phantom 3 Pro for about 4 months, so I figured that I should check for updates.
The last update I did was to bring the controller firmware up to v1.3.20 in order to enable updates from the DJI Go app.

Given the issues with batteries that I've been reading about, I thought it wise to go with the 1.6.0040 update.
My first step was to copy the file to the micro SD card, insert it, and then power on the Phantom.
The upgrade process took about 25 minutes, and I got a 'good' status at the end of it.

I then went into the DJI Go app, and it reports App v2.6.0, Aircraft 1.3.20+ and RC v1.3.20.
This doesn't seem correct to me. If I check the firmware log, then I see the following:

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...
Result: Success.


My assumption is that the 2nd and 3rd sucess entries refer to the battery updates, as I've got 3 batteries in total.

If we look at the more advanced log from MISC/LOG on the SD card, then I see the following:

[00013905]========== remo-con disconnect. boot(15) ============
[00013963]Packet [C:\P3X_FW_V01.06.0040.bin] detected, card sn [0x70dee2b9].
[00014013]Packet upgrade start...

[00014066]Packet checking...
[00014123]Packet vlink 01.06.0040 <-> 01.05.0030.
[00014178]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00014229]Done.

[00014282]Version checking[1]...
[00014365][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014446][03 06][00] v2.3.0.13 -> v2.4.10.7 need upgrade.
[00014499][04 00][00] v1.41.0.0 -> v1.41.0.0
[00014646][11 00][00] v1.7.0.0 -> v1.7.15.1 need upgrade.
[00014744][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014865][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014979][12 02][00] v1.10.0.0 -> v1.10.0.0
[00015079][12 03][00] v1.10.0.0 -> v1.10.0.0
[00015307][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015414][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015557][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015630][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015683][01 00][00] v1.23.3419 -> v1.26.4315 need upgrade
[00015739][01 01][00] v1.23.3419 -> v1.26.4315 need upgrade
[00015801][08 00][00] v0.12.0.4 -> v0.13.0.7 need upgrade.
[00015870][09 00][00] v1.7.0.3 -> v2.13.0.0 need upgrade.
[00015928]Done.

[00017978]Waiting for user confirm...
[00028037]Timeout, start upgrade automatically.

[00028140]Firmware upgrading[1]...
[00040267][01 00] Firmware upgrade start...
[00012229][01 00] Firmware upgrade finished successfully.
[00012377]Done.

[00012433]Packet [C:\P3X_FW_V01.06.0040.bin] resumed, card sn [0x70dee2b9].
[00012485]Packet vlink 01.06.0040 <-> 01.05.0030.
[00012554]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00012603]Version checking[2]...
[00012716][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012810][03 06][00] v2.3.0.13 -> v2.4.10.7 need upgrade.
[00012956][04 00][00] v1.41.0.0 -> v1.41.0.0
[00013177][11 00][00] v1.7.0.0 -> v1.7.15.1 need upgrade.
[00013305][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013415][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013523][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013627][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013785][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013883][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014022][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014093][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014231][01 00][05] v1.26.4315 -> v1.26.4315
[00014366][01 01][00] v1.23.3419 -> v1.26.4315 need upgrade
[00014427][08 00][00] v0.12.0.4 -> v0.13.0.7 need upgrade.
[00014493][09 00][00] v1.7.0.3 -> v2.13.0.0 need upgrade.
[00014546]Done.

[00014601]Firmware upgrading[2]...
[00014769][01 01] Firmware upgrade start...
[00045050][01 01] Firmware upgrade finished successfully.
[00045953][08 00] Firmware upgrade start...
[00562509][08 00] Firmware upgrade finished successfully.
[00562660][11 00] Firmware upgrade start...
[00610359][11 00] Firmware upgrade finished successfully.
[00610616][03 06] Firmware upgrade start...
[00959760][03 06] Firmware upgrade finished successfully.
[00959841][09 00] Firmware upgrade start...
[01013305][09 00] Firmware upgrade finished successfully.
[01013359]Done.

[01013412]Version checking[3]...
[01013509][03 05][00] v34.2.0.9 -> v34.2.0.9
[01013583][03 06][05] v2.4.10.7 -> v2.4.10.7
[01013653][04 00][00] v1.41.0.0 -> v1.41.0.0
[01013785][11 00][05] v1.7.15.1 -> v1.7.15.1
[01013883][12 00][00] v1.10.0.0 -> v1.10.0.0
[01013983][12 01][00] v1.10.0.0 -> v1.10.0.0
[01014083][12 02][00] v1.10.0.0 -> v1.10.0.0
[01014192][12 03][00] v1.10.0.0 -> v1.10.0.0
[01014380][15 00][00] v1.1.2.0 -> v1.1.2.0
[01014493][17 00][00] v1.1.1.7 -> v1.1.1.7
[01014633][17 01][00] v1.0.2.7 -> v1.0.2.7
[01014698][19 00][00] v1.0.8.96 -> v1.0.8.96
[01014757][01 00][05] v1.26.4315 -> v1.26.4315
[01014809][01 01][05] v1.26.4315 -> v1.26.4315
[01014884][08 00][05] v0.13.0.7 -> v0.13.0.7
[01014958][09 00][05] v2.13.0.0 -> v2.13.0.0
[01015010]Packet upgrade finish successfully.



[00013111]========== remo-con disconnect. boot(15) ============
[00013171]Packet [C:\P3X_FW_V01.06.0040.bin] detected, card sn [0x70dee2b9].
[00013224]Packet upgrade start...

[00013280]Packet checking...
[00013339]Packet vlink 01.06.0040 <-> 01.05.0030.
[00013394]Record vlink 01.06.0040 <-> 01.05.0030 (flow = 0).
[00013447]Done.

[00013500]Version checking[1]...
[00013597][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013698][03 06][00] v2.4.10.7 -> v2.4.10.7
[00013756][04 00][00] v1.41.0.0 -> v1.41.0.0
[00013898][11 00][00] v1.7.0.0 -> v1.7.15.1 need upgrade.
[00014012][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014138][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014247][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014342][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014506][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014602][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014842][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014918][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014972][01 00][00] v1.26.4315 -> v1.26.4315
[00015027][01 01][00] v1.26.4315 -> v1.26.4315
[00015098][08 00][00] v0.13.0.7 -> v0.13.0.7
[00015172][09 00][00] v2.13.0.0 -> v2.13.0.0
[00015227]Done.

[00017286]Waiting for user confirm...
[00027342]Timeout, start upgrade automatically.

[00027456]Firmware upgrading[1]...
[00027521][11 00] Firmware upgrade start...
[00076711][11 00] Firmware upgrade finished successfully.
[00076772]Done.

[00076827]Version checking[2]...
[00076922][03 05][00] v34.2.0.9 -> v34.2.0.9
[00077023][03 06][00] v2.4.10.7 -> v2.4.10.7
[00077083][04 00][00] v1.41.0.0 -> v1.41.0.0
[00077241][11 00][05] v1.7.15.1 -> v1.7.15.1
[00077344][12 00][00] v1.10.0.0 -> v1.10.0.0
[00077444][12 01][00] v1.10.0.0 -> v1.10.0.0
[00077569][12 02][00] v1.10.0.0 -> v1.10.0.0
[00077694][12 03][00] v1.10.0.0 -> v1.10.0.0
[00077838][15 00][00] v1.1.2.0 -> v1.1.2.0
[00077944][17 00][00] v1.1.1.7 -> v1.1.1.7
[00078119][17 01][00] v1.0.2.7 -> v1.0.2.7
[00078196][19 00][00] v1.0.8.96 -> v1.0.8.96
[00078252][01 00][00] v1.26.4315 -> v1.26.4315
[00078310][01 01][00] v1.26.4315 -> v1.26.4315
[00078373][08 00][00] v0.13.0.7 -> v0.13.0.7
[00078456][09 00][00] v2.13.0.0 -> v2.13.0.0
[00078508]Packet upgrade finish successfully.



[00013223]========== remo-con disconnect. boot(15) ============
[00013281]Packet [C:\P3X_FW_V01.06.0040.bin] detected, card sn [0x70dee2b9].
[00013339]Packet upgrade start...

[00013399]Packet checking...
[00013460]Packet vlink 01.06.0040 <-> 01.05.0030.
[00013513]Record vlink 01.06.0040 <-> 01.05.0030 (flow = 0).
[00013566]Done.

[00013625]Version checking[1]...
[00013717][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013798][03 06][00] v2.4.10.7 -> v2.4.10.7
[00013863][04 00][00] v1.41.0.0 -> v1.41.0.0
[00013998][11 00][00] v1.7.0.0 -> v1.7.15.1 need upgrade.
[00014091][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014191][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014402][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014501][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014648][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014741][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014882][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014947][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015003][01 00][00] v1.26.4315 -> v1.26.4315
[00015064][01 01][00] v1.26.4315 -> v1.26.4315
[00015135][08 00][00] v0.13.0.7 -> v0.13.0.7
[00015206][09 00][00] v2.13.0.0 -> v2.13.0.0
[00015261]Done.

[00017320]Waiting for user confirm...
[00027374]Timeout, start upgrade automatically.

[00027485]Firmware upgrading[1]...
[00027553][11 00] Firmware upgrade start...
[00077134][11 00] Firmware upgrade finished successfully.
[00077189]Done.

[00077246]Version checking[2]...
[00077341][03 05][00] v34.2.0.9 -> v34.2.0.9
[00077421][03 06][00] v2.4.10.7 -> v2.4.10.7
[00077486][04 00][00] v1.41.0.0 -> v1.41.0.0
[00077602][11 00][05] v1.7.15.1 -> v1.7.15.1
[00077705][12 00][00] v1.10.0.0 -> v1.10.0.0
[00077804][12 01][00] v1.10.0.0 -> v1.10.0.0
[00077904][12 02][00] v1.10.0.0 -> v1.10.0.0
[00078004][12 03][00] v1.10.0.0 -> v1.10.0.0
[00078168][15 00][00] v1.1.2.0 -> v1.1.2.0
[00078290][17 00][00] v1.1.1.7 -> v1.1.1.7
[00078430][17 01][00] v1.0.2.7 -> v1.0.2.7
[00078509][19 00][00] v1.0.8.96 -> v1.0.8.96
[00078570][01 00][00] v1.26.4315 -> v1.26.4315
[00078623][01 01][00] v1.26.4315 -> v1.26.4315
[00078690][08 00][00] v0.13.0.7 -> v0.13.0.7
[00078770][09 00][00] v2.13.0.0 -> v2.13.0.0
[00078826]Packet upgrade finish successfully.


From what I can see, this indicates that all of the firmware on the aircraft and batteries is up to date.
However, this isn't reflected in the firmware version shown in the DJI Go app.
I did find another thread on here which talks about this mismatch (http://www.phantompilots.com/threads/1-3-20-what-does-this-mean.53835/).
The suggestion in this thread is that dragging and dropping the firmware file to the SD card was the cause, and that copying and pasting fixes the issue. I'm at a loss to explain why, and certainly this fix does not address the issue for me.

Can anyone suggest why my firmware version is not displaying correctly?
What should the app being showing?
I've also not got any notifications of firmware updates for the controller. Is 1.3.20 the latest version for the RC?

Any help would be much appreciated.

Regards,

Andy.
 

Attachments

  • P3X_FW_LOG_AB.txt
    47.6 KB · Views: 374
Controller should be 1.5.7....you're way behind.

The question then becomes why isn't this fact being detected?
The DJI Go app is not offering me any updates, and the iPad is connected to WiFi and could check.

Also, why does the correct Aircraft version version not display, when it would appear that the various modules in the firmware have been updated successfully (based on the log file)?
 
If your RC is on firmware 1.3.20 -(which yours is)- when you turn on the RC and have it linked to your iPad, and then enter camera view, it should tell you an update is required. This is then downloaded via wi-fi and you are prompted to install.

If yours isn't doing this, I have no answer and suggest you contact DJI support....Sorry I can't be more helpful.
 
A quick afterthought....it may be worth deleting and re-installing the DJI GO app on your iPad to see if that makes any difference.
 
  • Like
Reactions: dirtybum
A quick afterthought....it may be worth deleting and re-installing the DJI GO app on your iPad to see if that makes any difference.
Thanks for that thought. I've uninstalled the app and re-installed. The Aircraft and RC firmware versions now say 'Unknown'. Not good.

I've raised a support ticket with DJI to try and find out what's going on. No response as yet.
 
Thanks for that thought. I've uninstalled the app and re-installed. The Aircraft and RC firmware versions now say 'Unknown'. Not good.

I've raised a support ticket with DJI to try and find out what's going on. No response as yet.
Sorry to hear the bad news.....hope you get it sorted soon.
 
It would appear that this issue is unique to the iPad Mini.
I plugged in my iPad Air 2, and my iPhone 6 Plus and both show the firmware versions correctly.
I've just successfully updated my RC to 1.5.70 using my iPhone.

It seems that DJI are aware of this issue, as it has been reported before. I can't seem to find any resolution, though. I really need to find a solution, as the Air 2 is simply too big and doesn't fit in the bracket properly when I use the screen hood.

What a pain in the a**e!!!
 
Nice to hear you're up and running!....Presumably the problem is with the original iPad Mini -(which is known to be too slow to fly with)- , but it seems strange it won't update the RC. I bought a second hand Mini 2 which is great, and used by many on the site.
Happy flying :)
 
Nice to hear you're up and running!....Presumably the problem is with the original iPad Mini -(which is known to be too slow to fly with)- , but it seems strange it won't update the RC. I bought a second hand Mini 2 which is great, and used by many on the site.
Happy flying :)
I'm using a Mini 2, so it should work.
Just chatting with DJI support about it now. They don't appear to believe me, and have asked me to send screenshots of the iPad Mini 2 and the iPhone showing the difference.

What iOS version are you using on your Mini 2?
 
Got it working now.
It seems that DJI Go 2.4 does something which breaks the ability for the Mini 2 to read this information.
Uninstalling, and then re-installing 2.6, followed by a reboot of the Mini 2 has fixed this for me. :)
 
I'm on 2.6.0 as well.....only got the Mini 2 recently, so I never had 2.4 on it -(luckily!)- ,before that I was using my iPad Air but found it a bit large on the RC.
 

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,091
Messages
1,467,576
Members
104,974
Latest member
shimuafeni fredrik