All-in-One firmware Version: v1.6.80

I believe you are correct Stuart unless I'm bad mistaken .
Everything I have seen done was through the App .
You didn't save anything to the card .

It is via the App, but the app downloads the .bin TO the SD card so it can update, that is where the "downloaded" update goes so it can update the bird. So yes, it MUST be present on the SD card, but it only does so after being downloaded from the app first.
 
Last edited:
  • Like
Reactions: dirkclod
Ok , so it just writes it to the card then upgrades.
I always format my card every time I come in and change
Cards a lot so I just assumed the card had nothing to do with it.
That's what I get for assuming :)
 
Ok , so it just writes it to the card then upgrades.
I always format my card every time I come in and change
Cards a lot so I just assumed the card had nothing to do with it.
That's what I get for assuming :)

Yeah, downloads via WiFi, then once downloaded, it first transfers from tablet to the bird, THEN commences upgrade. :) Leaving that .bin file on the card will also update your batteries when plugged in. This is part of the reason people think the upgrade didn't take the first time, because a new battery without the required firmware will again prompt you to install the same firmware version, but it's not the whole bird being updated, ONLY the battery this time.
 
  • Like
Reactions: EddieM and dirkclod
Yeah, downloads via WiFi, then once downloaded, it first transfers from tablet to the bird, THEN commences upgrade. :) Leaving that .bin file on the card will also update your batteries when plugged in. This is part of the reason people think the upgrade didn't take the first time, because a new battery without the required firmware will again prompt you to install the same firmware version, but it's not the whole bird being updated, ONLY the battery this time.
So if I was to update and I have 4 battery's I should not format my card till I have put all the battery's through it .Correct ?
 
  • Like
Reactions: arcaine25
So if I was to update and I have 4 battery's I should not format my card till I have put all the battery's through it .Correct ?

That is indeed correct. Just remember it will pop up and it will appear just the same / similar as it did when you needed to update the bird, only this time, being for a battery only it will go pretty quick!
 
  • Like
Reactions: dirkclod
That is indeed correct. Just remember it will pop up and it will appear just the same / similar as it did when you needed to update the bird, only this time, being for a battery only it will go pretty quick!
Thank-you :)
monker thumbup.gif
 
  • Like
Reactions: arcaine25
  • Like
Reactions: Nickster and RodPad
I thought this message would be better here.

So (MTR-Aerial)
Posted This,

I am on the DJI Forum as well and I had noticed a lot of talk over there about the new FW causing issues with the standard model, even some making them worthless. I had updated mine straight out of the box to 1.6.8 and it had no issues but upon reading so many posts that 1.5.7 was so much better I thought I'd give it a try. So last night I had downgraded it to 1.5.7 and took it out the next morning and I couldn't break 600ft distance. I went back in and re-upgraded it to 1.6.8 and I had no problems hitting 2500ft in a congested area. I don't know if this is truly an issue with the drones because I was only on the one forum. But my conclusion of the FW with my P3S is 1.6.8 works great and allows my drone to fly just as it should!

Here is his actually Post.
Introduction/ 3D Parts/ Input needed!

So, I had to know more,

RodPad (Me)
Posted This,

Questions,
#1 What firmware was in it you purchased it?, 1.6.8 came out May 9th, Less than 3 weeks ago.
#2 So out of the box, you updated to 1.5.7?
#3 How did you downgrade, through the app, or putting an older bin file on the SD card?
#4 If you downgraded with the app, is there or was there an option to load older than 1.5.7?
#5 What are you using for your mobile device?
#6 Couldn't break 600ft, was there an error message / warning?

Should posted that part here,
All-in-One firmware Version: v1.6.80
Let us know, the downgrade option has only been out about 6 weeks, I had it until I went to 1.5.7.
Its there but none to pick from anymore, On a crApple or an Antroid. Ants eat Apples.
:D


So (MTR-Aerial)
Posted This,


Ok... Ill do my best to answer these.
1. It came with 1.5.7 on it and I upgraded it to 1.6.8. (didn't fly it with 1.5.7... the way they have the app blink red... I took no chance and updated it)
2. Yes
3. I downgraded by getting the FW from phantomhelp, formatting a sd card, putting said FW onto sd card (no folder), turned on controller and connected to APP and then turned on drone. Once you turn on the drone the downgrade process begins. (I had to hit the home button on the app, once it kicked back to the first screen it would say "uploading --%")
4. Phantom help has all the older FW's. You could downgrade to anything, I would imagine.
5. When I did the downgrade I was using an Amazon Fire 7". (The super cheap one, I got it for 28 dollars on back friday.) I am currently using an iPad Pro 12.9" though.
6. Couldn't break 600ft as in it would drop video feed and say "weak signal" and "lost signal"


I hope that helps and any other questions... FIRE AWAY! Ill do my best to answer them!

The process I used to downgrade... I don't see that really being written in to a FW? If you can go back to 1.5.7 and you say its 6 weeks old(process to downgrade)? Isn't 1.5.7 older than that? Therefore making the downgrade process always being there?



Now, RodPad (Me)
I am posting this reply,

MTR-Aerial, Thanks for your info.
I have not loaded 1.6.8, I know of nobody that has able to downgrade from 1.5.7 or 1.6.8, except for you.
Here is some things that many of us have tried to downgrade.

No signal after update
www.phantompilots.com/threads/p3s-service-bin.77660

This is just a few,
:rolleyes:
 
Last edited:
  • Like
Reactions: arcaine25
Lol, just glad I could help!
R we sure the phantom does a complete format (wipes everything) and not just media n temps? I finally understand battery formatting now,thanks! Could swear I found a hidden file 1 time after formatting from the bird
 
R we sure the phantom does a complete format (wipes everything) and not just media n temps? I finally understand battery formatting now,thanks! Could swear I found a hidden file 1 time after formatting from the bird

Once booted, even on a clean SD card, it writes files to the card, some hidden (most hidden?) that are UDX, LOG, etc. That may be what you are referring to?
 
Hi!

Yesterday weather allowed for a longer flight in Sweden (CE) and this time the purpose was to examine if the 1.6.80 f/w changed the range in some way (compared to 1.3.50+)

Screenshot as proof below ;)

At 700m+ - started to get weak videosignal but no loss of 5.8G RC signal, returned home manually.
This is in CE-mode and no modifications whatsoever, going to try the limit this weekend if it only could stop snowing :)


/Per
 
HI, weird thing happened to my P3S when I tried to update... First it stucked at 16%, and I got message, update failed. After that, I did start phantom again, but there was red light on controller, and I somehow managed to get the green light, and start update again, and it got to 40% when I lost controller and percentage again. I left phantom to update... and to tell you the truth, I don't know if it was updated completely, I just had a hunch it was, because of the sound that I got. I turned it off, took it to another room, without PC in it, turned it on, turned RC on, and it connected, fw is 1.6.80, everything works. Should I be worried, because I don't know if update was done completely, but my logic is telling me that it was, because it's working fine.. What should I do, take it to dealer to send it to a service, or trust it was updated successfully and fly?

UPDATE:

This is the log:


[00296240]========== 2016.05.20 22:53:08. boot(15) ============
[00296287]Packet [C:\P3C_FW_V99.99.9999.bin] detected, card sn [0x43efe6c0].
[00296327]Packet upgrade start...

[00296373]Packet checking...
[00296413]Packet vlink 01.06.0080 <-> 01.05.0070.
[00296452]Record vlink 01.05.0070 <-> 01.04.0060 (flow = 0).
[00296501]Done.

[00296540]Version checking[1]...
[00296579][01 00][00] v1.14.4920 -> v1.14.4920
[00296618][01 01][00] v1.14.4920 -> v1.14.4920
[00296665][04 00][00] v1.44.0.0 -> v1.44.0.0
[00296772][03 05][00] v34.2.0.9 -> v34.2.0.9
[00296850][03 06][00] v2.4.14.5 -> v2.4.15.5 need upgrade.
[00297034][09 00][00] v0.1.1.0 -> v0.1.1.0
[00297165][12 00][00] v5.9.0.0 -> v5.9.0.0
[00297277][12 01][00] v5.9.0.0 -> v5.9.0.0
[00297356][12 02][00] v5.9.0.0 -> v5.9.0.0
[00297471][12 03][00] v5.9.0.0 -> v5.9.0.0
[00297591][11 00][00] v1.8.0.0 -> v1.8.0.0
[00297710][11 01][00] v1.8.0.0 -> v2.0.0.32, firmware v1.8.0.0 not support.
[00297748][11 01][00] v1.8.0.0 -> v2.0.0.32
[00297796]Done.

[00299835]Waiting for user confirm...
[00309881]Timeout, start upgrade automatically.

[00309960]Firmware upgrading[1]...
[00310220][03 06] Firmware upgrade start...
[00659347][03 06] Firmware upgrade finished successfully.
[00659390]Done.

[00659434]Version checking[2]...
[00659473][01 00][00] v1.14.4920 -> v1.14.4920
[00659512][01 01][00] v1.14.4920 -> v1.14.4920
[00659566][04 00][00] v1.44.0.0 -> v1.44.0.0
[00659651][03 05][00] v34.2.0.9 -> v34.2.0.9
[00659749][03 06][05] v2.4.15.5 -> v2.4.15.5
[00659808][09 00][00] v0.1.1.0 -> v0.1.1.0
[00659891][12 00][00] v5.9.0.0 -> v5.9.0.0
[00659990][12 01][00] v5.9.0.0 -> v5.9.0.0
[00660073][12 02][00] v5.9.0.0 -> v5.9.0.0
[00660171][12 03][00] v5.9.0.0 -> v5.9.0.0
[00660287][11 00][00] v1.8.0.0 -> v1.8.0.0
[00660407][11 01][00] v1.8.0.0 -> v2.0.0.32, firmware v1.8.0.0 not support.
[00660450][11 01][00] v1.8.0.0 -> v2.0.0.32
[00660493]Packet upgrade finish successfully.
 
Last edited:
Hello, rob 1984. My update experience was similar to yours. After the update, I re-calibrated the IMU. I took my p3s outside without the props installed and calibrated the compass and everything seemed good. Attached the props and flew a couple of short flights, all was good. It is operating fine now, I was sweating the first post-update flight though. Good luck.
Cheers,
Shawn
 
Hi!

Yesterday weather allowed for a longer flight in Sweden (CE) and this time the purpose was to examine if the 1.6.80 f/w changed the range in some way (compared to 1.3.50+)

Screenshot as proof below ;)

At 700m+ - started to get weak videosignal but no loss of 5.8G RC signal, returned home manually.
This is in CE-mode and no modifications whatsoever, going to try the limit this weekend if it only could stop snowing :)


/Per
You still have snow?
 
Hello, rob 1984. My update experience was similar to yours. After the update, I re-calibrated the IMU. I took my p3s outside without the props installed and calibrated the compass and everything seemed good. Attached the props and flew a couple of short flights, all was good. It is operating fine now, I was sweating the first post-update flight though. Good luck.
Cheers,
Shawn


Thank you Shawn, it's a bit of a relief to hear someone had same experience and in the end everything is working fine. I will try to fly today in one open field. Cheers.
 
Hi guys, just to confirm, I finally flew my bird after the 1.6.80 update (finally some good weather :)), and I noticed its handling wind much better (it's not as jerky as before).

I am in CE mode, so I only flew it to 250ish meters distance (72m height) because of location constraints, and so far I did not had any weak RC or Video signal. Mine seems to be in top shape :)

Hope all is good with yours guys ;)
 
Hi guys, just to confirm, I finally flew my bird after the 1.6.80 update (finally some good weather :)), and I noticed its handling wind much better (it's not as jerky as before).

I am in CE mode, so I only flew it to 250ish meters distance (72m height) because of location constraints, and so far I did not had any weak RC or Video signal. Mine seems to be in top shape :)

Hope all is good with yours guys ;)
Thanks for let us know!,
Not really you should send yours in anyway, we should all share the same grief.
:eek:
 
Just thought I'd throw this out there. My update failures occured when the controller lost the connection with the p3s during the upgrade. I spoke to a pilot earlier today who had similar issues. He stated that the fix was to move the controller away from the drone, not right next to it as I had done. Around a meter or so instead. Thought I would relate that for anyone still having similar issues.
Cheers,
Shawn
 
  • Like
Reactions: arcaine25

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,086
Messages
1,467,528
Members
104,965
Latest member
Fimaj