Having just received my P3P the other day, I cautiously investigated firmware.

With all of the erratic reports of 1.2.6, my first objective was to check the version shipped with my chopper. To my relief, it was 1.1.5. Wonderful. I had already downloaded 1.1.9 and had reviewed all of the steps for updating. What could possibly go wrong?

Cutting to the chase, after two attempts of updating the chopper.... each time the text file reported "abort" because the update version was identical or older than the installed version. After a bit of searching for similar scenarios on the boards here, come to find out that there is an issue with the installation misidentifying the installed firmware.

Whether it truly is 1.1.5, or 1.1.9... who knows, but the upshot of it all is now the chopper won't connect with the controller (which it was able to do prior to my attempt to update). If the update attempt was aborted, what has changed?

Are successful updates only achieved on 1.1.5 with 1.2.6?

I'm a media producer with solid suite of gear and have done my share of delicate and finnicky firmware updates on much more expensive gear in much smaller production runs than the Phantom.... but never has a faulty update been unackowledged if not corrected in less than a few days, and never has there been an issue of an update being confused by version numbers. That's the equivilent of a typo and doesn't instill confidence.

If this were a car, the recall notices would have been out some time ago.

I'm Android with a Nexus 7 II tablet. If anyone has suggestions as to how to address this problem, I'm all ears. I know the P3P is going to be incredible and fun, but mine is grounded for now.

Post the hidden txt file in the misc log folder of the SD card..

sploodge Posted at 2015-7-30 21:03
Post the hidden txt file in the misc log folder of the SD card..

Hey sploodge... thanks for checking in on this. Here's the text file:

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

[00012281]========== 2014.01.01 00:00:12 unsynchronized ======
[00012298]Packet [C:\P3X_FW_V01.01.0009.bin] detected.
[00012314]Packet upgrade start...

[00012327]Packet checking...
[00012332]Done.

[00012337]Version checking[1]...
[00012385][03 05] v34.2.0.9 -> v34.2.0.8
[00012426][03 06] v2.1.6.18 -> v2.1.6.18
[00012440][04 00] v1.38.0.0 -> v1.36.0.0
[00012461][09 00] v1.7.0.3 -> v1.7.0.3
[00012545][11 00] v1.6.1.0 -> v1.6.0.0
[00012595][12 00] v1.8.0.0 -> v1.8.0.0
[00012661][12 01] v1.8.0.0 -> v1.8.0.0
[00012715][12 02] v1.8.0.0 -> v1.8.0.0
[00012780][12 03] v1.8.0.0 -> v1.8.0.0
[00012877][15 00] v1.1.2.0 -> v1.1.2.0
[00012935][17 00] v1.1.1.2 -> v1.1.1.2
[00013035][17 01] v1.0.2.4 -> v1.0.2.4
[00013060][19 00] v1.0.8.96 -> v1.0.8.59
[00013065][01 00] v1.6.2736 -> v1.6.2736
[00013070][01 01] v1.6.2736 -> v1.5.2735
[00013088][08 00] v0.11.0.4 -> v0.11.0.4
[00013093]Packet upgrade cancelled at version checking.

That log shows you are already on 1.1.9

You say you cannot connect the controller to the P3 any more.. Have you ran the update process on the controller too? If not give that a go ( remove the TXT files from the sd card but keep a copy on your computer ).

if yuo have done the controller, what light is on the controller when P3 and it are powered on? Green ore Red?

sploodge Posted at 2015-7-30 21:44
You say you cannot connect the controller to the P3 any more.. Have you ran the update process on th ...

The controller shows red, and the Pilot App shows Disconnected.

I contemplated running the update on the controller, but at the risk of making bad situation worse I have held off. I suppose at this point, it's worth a shot.

An essential fact that would be nice to know is, where is the misidentification happening. If 1.1.5 is truly the current version on my chopper, why is 1.1.9 confused? Certainly, users were able to update from 1.1.5 to 1.1.9 when it was first released??

I can't recall if, or how many firmware versions there are between 1.1.9 and 1.2.6, but perhaps attempting an update of something newer than 1.1.9 (but not 1.2.6) would bypass the version conflict.

Later today, I will go with the attempt to update the controller and report back. Thanks for your input... I assume the hidden log file didn't reveal anything pertinent.

Log just seems to say its already 1.1.9.. Some before did report that if you start up the RC/App/P3 in the incorrect order that it displayed the wrong firmware version but never experienced this..

Order I use to start up is:
1/ switch on RC
2/ switch on P3
3/ start your Pilot app


If the controller shows red light it could just need re-associating to the Phantom.. Page 29 of the manual. I would not recommend having the two on different firmwares though even if the RC linking works

sploodge Posted at 2015-7-30 21:58
Log just seems to say its already 1.1.9.. Some before did report that if you start up the RC/App/P3  ...

Thanks sploodge.... I think I've been careful, but time to go back to step one and be sure. Your references from the manual are appreciated.

sploodge Posted at 2015-7-30 21:58
Log just seems to say its already 1.1.9.. Some before did report that if you start up the RC/App/P3  ...

LED is green on both the controller and the chopper to indicate they are linked, but the Pilot App shows as Disconnected.

In the RC Control Settings, I select Linking Remote Controllers, a pop up appears to confirm the frequency settings.... click on Agree, still Disconnected.

This has to be a result of my attempt to update the firmware (to 1.1.9)... but I am at a dead end on that effort. The controller wouldn't take the update either.

Even though the devices indicate they are linked, the Controller has no effect with the sticks.

What am I missing?

marty Posted at 2015-7-31 07:12
LED is green on both the controller and the chopper to indicate they are linked, but the Pilot App ...

In desperation, I went ahead with a 1.2.6 update... txt file said "success"

Version displayed in Pilot App, 1.1.5, and won't connect (probably why the version report is "stuck") even though the connection LEDs on the chopper and the controller are green.

If Pilot App is the problem, can I control the chopper without the tablet and simply disconnect it?

Sure is fun being a part of DJI's R&D failures. If it were only the Phantom 3, I would be patient... but QC seem to be dogging several of their product line.

I think I could get a license and fly a real helicopter at the pace input, let alone, solutions are forthcoming from DJI.

Unfortunately, this bird's next flight is likely to be back to its retailer... not ready for prime time.

So Long Marty... Or are you just exchanging this one, for another Phantom 3 model. Trade in and up.
I hope that you get your current problem resolved and eventually get to enjoy and appreciate your
Phantom 3.  Much like most of us are. I see different issues that others have dealt with, but my
Phantom 3 has been trouble free. And I never experienced any of the concerns that appear in the forums, described by other Phantom 3 pilots..
So I know that you can get an Awesome unit too. Wishing you great luck, in your next Phantom, Or what ever you fly. Just get back in the air soon.

RedHotPoker

RedHotPoker Posted at 2015-7-31 12:52
So Long Marty... Or are you just exchanging this one, for another Phantom 3 model. Trade in and up.
...

Thanks RedHotPoker... the allure of a properly functioning Phantom 3 is too much to resist. My plan is to exchange and hope that the replacement unit has better karma.

My break from here will be temporary and hopefully brief!

I hope that you get it traded in soon, and have a trouble free model when you do.
It's an actual blast, when everything is working correctly. I Really appreciate mine...

Thankfully, I got lucky, on my shoulder... ;-)

RedHotPoker