Firmware Version 01.09.0060

[hot11119]

is there a hacked fw that will let you fly anywhere you want? i find it hard to believe Yuneec has a fw with no restrictions while dji dont.
i live 4 miles from the nearest airport and never even fly over 100ft. i do go higher elsewhere off course.

 

[DPD]

I updated my P3P yesterday along with both batteries. Plan to take it up later. I'll report back after flying on the new FW.

Edit: as a point of reference, the initial install on the P3P took 8 minutes for me, coming from 1.8. The second install (second battery) took less, maybe 4 minutes just to update the battery.

Mike

Hey Mike. Does yours show up as 1.8+, or 1.9 in the GOApp??


Sent from my iPad using PhantomPilots mobile app

 

[walko]

Mine (P3Adv) shows 1.8+ too...

 

[RedHotPoker]

Either way, you guys are good to go. It has been noted, that sometimes an update will actually show a + sign and a lower number, but are essentially the same updated firmware.
If you have Success in the text file. There you go.
Go out and enjoy your drone, and stop worrying about nothing.
As stated you had Success. You are up to date. Enjoy. . .

Go Fly, fly away. . . ;-)

RedHotPoker

 

[UKFlyer]

Hey Mike. Does yours show up as 1.8+, or 1.9 in the GOApp??


Sent from my iPad using PhantomPilots mobile app

Mine (P3Adv) shows 1.8+ too...

My P3P is showing the correct firmware in the Go app. (android)

.

 

[Yiannis.B]

Hello,

my first post in the forum,

I have also upgraded successfully, but in DJI Go it shows firmware 1.8.80+ (android).

Then checked the P3X_FW_LOG_AB.txt file on the SD card ( MISC/LOG) :

Before the update (but with the new firmware downloaded to sd card):

-------------------------------------------------------------------------------------------------------------------

[00018589]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x854510a4].
[00018619]Packet upgrade start...

[00018661]Packet checking...
[00018695]Packet vlink 01.09.0060 <-> 01.08.0080.
[00018763]Done.

[00018796]Version checking[1]...
[00018873][03 05][00] v34.2.0.9 -> v34.2.0.9
[00018934][03 06][00] v2.4.10.7 -> v2.4.20.18 need upgrade.
[00018975][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00019054][11 00][00] v2.0.0.32 -> v1.8.0.0, firmware v2.0.0.32 not support.
[00019089][11 00][00] v2.0.0.32 -> v1.8.0.0
[00019173][11 01][00] v2.0.0.32 -> v2.0.0.33 need upgrade.
[00019273][12 00][00] v1.10.0.0 -> v1.10.0.0
[00019342][12 01][00] v1.10.0.0 -> v1.10.0.0
[00019422][12 02][00] v1.10.0.0 -> v1.10.0.0
[00019498][12 03][00] v1.10.0.0 -> v1.10.0.0
[00019632][15 00][00] v1.1.2.0 -> v1.1.2.0
[00019709][17 00][00] v1.1.1.7 -> v1.1.1.7
[00019823][17 01][00] v1.0.2.7 -> v1.0.2.7
[00019879][19 00][00] v255.255.255.254 -> v1.0.8.96
[00019913][01 00][00] v1.29.4920 -> v1.30.5036 need upgrade
[00019945][01 01][00] v1.29.4920 -> v1.30.5036 need upgrade
[00019997][08 00][00] v0.13.0.7 -> v0.13.0.7
[00020058][09 00][00] v2.13.0.0 -> v3.0.0.10 need upgrade.
[00020091]Done.
------------------------------------------------------------------------------------------------
And after the upgrade:
------------------------------------------------------------------------------------------------
[00545934]Version checking[3]...
[00546006][03 05][00] v34.2.0.9 -> v34.2.0.9
[00546085][03 06][05] v2.4.20.18 -> v2.4.20.18
[00546163][04 00][05] v1.44.0.0 -> v1.44.0.0
[00546284][11 00][00] v2.0.0.33 -> v1.8.0.0, firmware v2.0.0.33 not support.
[00546322][11 00][00] v2.0.0.33 -> v1.8.0.0
[00546426][11 01][05] v2.0.0.33 -> v2.0.0.33
[00546519][12 00][00] v1.10.0.0 -> v1.10.0.0
[00546599][12 01][00] v1.10.0.0 -> v1.10.0.0
[00546699][12 02][00] v1.10.0.0 -> v1.10.0.0
[00546799][12 03][00] v1.10.0.0 -> v1.10.0.0
[00546922][15 00][00] v1.1.2.0 -> v1.1.2.0
[00547014][17 00][00] v1.1.1.7 -> v1.1.1.7
[00547149][17 01][00] v1.0.2.7 -> v1.0.2.7
[00547205][19 00][00] v255.255.255.254 -> v1.0.8.96
[00547241][01 00][05] v1.30.5036 -> v1.30.5036
[00547276][01 01][05] v1.30.5036 -> v1.30.5036
[00547446][08 00][00] v0.13.0.7 -> v0.13.0.7
[00547505][09 00][05] v3.0.0.10 -> v3.0.0.10
[00547543]Packet upgrade finish successfully.
-----------------------------------------------------------------------------------

I did not delete the .bin file in the sd card and rebooted aircraft. :
-----------------------------------------------------------------------------------------------------
[00012311]========== 2016.06.14 00:37:23. boot(15) ============
[00012348]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x854510a4].
[00012382]Packet upgrade start...

[00012422]Packet checking...
[00012458]Packet vlink 01.09.0060 <-> 01.08.0080.
[00012494]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00012532]Done.

[00012574]Version checking[1]...
[00012646][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012727][03 06][00] v2.4.20.18 -> v2.4.20.18
[00012766][04 00][00] v1.44.0.0 -> v1.44.0.0
[00012872][11 00][00] v2.0.0.33 -> v1.8.0.0, firmware v2.0.0.33 not support.
[00012907][11 00][00] v2.0.0.33 -> v1.8.0.0
[00013006][11 01][00] v2.0.0.33 -> v2.0.0.33
[00013100][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013200][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013300][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013401][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013540][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013616][17 00][00] v1.1.1.7 -> v1.1.1.7
[00013735][17 01][00] v1.0.2.7 -> v1.0.2.7
[00013788][19 00][00] v255.255.255.254 -> v1.0.8.96
[00013823][01 00][00] v1.30.5036 -> v1.30.5036
[00013873][01 01][00] v1.30.5036 -> v1.30.5036
[00013922][08 00][00] v0.13.0.7 -> v0.13.0.7
[00013992][09 00][00] v3.0.0.10 -> v3.0.0.10
[00014028]Packet upgrade cancelled at version checking.

---------------------------------------------------------------------------------------

So it seems that one hardware component cannot be upgraded. It seems like that to be the reason DJI Go shows 1.8.80+.

Any thoughts?

Which component was not upgraded?

(Sorry for my grammar, English is not my native language. )

 

[2nd2non]

@autoflightlogic confirms this FW version corrects the issue that prevented the aircraft from executing Return-to-Home (RTH) on RC signal loss for P3A/P3P. So this is the major FW version we have been awaiting. Time will tell what else has changed in it

 

[jonebk12]

@autoflightlogic confirms this FW version corrects the issue that prevented the aircraft from executing Return-to-Home (RTH) on RC signal loss for P3A/P3P. So this is the major FW version we have been awaiting. Time will tell what else has changed in it

Jeez I wasn't even aware of that problem.

 

[NRJ]

I think the problem for us enthusiasts is that every other week there is another update to the firmware, or app. Because DJI is making firmware changes for just about every bird they sell, they are rolling these all-in-one upgrades out pretty fast. This effects us because we are having to ugprade just about as often too. Personally, I like to test fly each new version of the app or fw before I take it out for a special mission. We know only to well that some versions have caused some of us big issues. Since the introduction of the P4, this has been the case. I hope DJI will get the message to make an All-in-one version for All-the-time.

 

[jonebk12]

I flew today on the latest firmware. No issues to report.

 

[UKFlyer]

To get the correct firmware to show try re-connecting to the internet with the Go app when upgrade is complete.

 

[nollzr]

I also flew mine today. Everything works good

 

[Purnong]

Hi all
First post here so be gentle
I also updated to 1.9 today and no problems with a ten minute test flight
I have only had my P3A a few days and just updated to 1.8 a couple of days ago and had no idea you had to do both batteries but I have this time
Thanks for the info, Steep learning curve with these things, lol

 

[FantomFlier]

Hi all
First post here so be gentle
I also updated to 1.9 today and no problems with a ten minute test flight
I have only had my P3A a few days and just updated to 1.8 a couple of days ago and had no idea you had to do both batteries but I have this time
Thanks for the info, Steep learning curve with these things, lol

Please will you check which firmware version the app shows for your aircraft, and also let us know whether you are on Android or iOS.

 

[Purnong]

Please will you check which firmware version the app shows for your aircraft, and also let us know whether you are on Android or iOS.

Hi FantomFlier
The app shows the same as the txt file

"
========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Success."

I'm on Android and the update was pretty quick, The second battery was only five minutes or so

 

[FantomFlier]

Hi FantomFlier
The app shows the same as the txt file

"
========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Success."

I'm on Android and the update was pretty quick, The second battery was only five minutes or so

Thanks.

 

[MikeyOnline]

Hey Mike. Does yours show up as 1.8+, or 1.9 in the GOApp??


Sent from my iPad using PhantomPilots mobile app

I'll try to fly later today. Ended up taking a 6 hour trip to help a friend buy a new car yesterday so didn't have time. Is it possible that if you were already on 1.8.80 and then updated, it just shows the +. But if you were on a firmware prior to 1.8.80, it shows 1.9? Just a thought.

Mike

 

[UKFlyer]

I'll try to fly later today. Ended up taking a 6 hour trip to help a friend buy a new car yesterday so didn't have time. Is it possible that if you were already on 1.8.80 and then updated, it just shows the +. But if you were on a firmware prior to 1.8.80, it shows 1.9? Just a thought.

Mike

I was on the previous firmware 1.8.80 before i updated to the current.

 

[Trackman1]

Just a thought guys. But there are different main boards within the same models. We know this as they made revisions during production.
So you want to make sure you compare apples with apples.

It would be nice if everyone would list their hardware and firmware in their signatures.

 

[UKFlyer]

In my opinion all you need to do is turn everything off, turn back on and reconnect to the internet then it should say the current firmware properly.