marty
lvl.2
United States
Offline
|
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.
|
|