PartsGuy Posted at 2016-4-8 18:41
Donnie, I updated my P3P and RC today. I did not have the RC on during the aircraft update. It took  ...

Parts Guy ,the damage occurs when the Aircarft is updating and the Transmitter is ON.   I just  try to keep a good policy of not having both on at the same time when updating.  You did not damage it, I would not do that in the future.  I always promote powering one up at a time and updating  so no one get's confused on which way causes damage (  Keep this between us )  .......

I am so glad the point is getting out there not to leave transmitter on while updating, usually  a couple of days after the updates pilots are asking ,"Why they cant see Video after update"  and the conclusion is usually , " I did have my Transmitter on during aircraft update,,,,,,was this bad ".  And this will cause the Dreaded "Device not detected " on line 8 and 15 of the hidden log on the SD card.  This means the Vido Tranmission module was corrupted and must go in for repair.  

Donnie Posted at 2016-4-8 09:59
Falexander 115,  glad you had success.  The most common cause of failure is about 7 primary causes. ...

I'll add that I'm a Mac user and agree that formatting an SD card can be a bit problematic.  BUT once it is formatted, I've had zero issues using my Mac for updating the firmware.   I've used my Mac for the last 3 or 4 updates with no issues...

eddycheah Posted at 2016-4-8 20:05
I have some suggestion for updating,For aircraft update use sd card(Download from DJI ），For remote ...

   Eddychea  You should always update using the GO APP for the RC transmitter.  The ONLY timne the SD card Thumb Drive Method is used is if you are having trouble.  For example the Wi-Fi connection was broke during the update and the RC transmitter is stuck with a Blue light , THAT is when the method of a thumb drive is used on the RC.  

Thank you for Reminding everyone one of the proper method,  thanks for the input.

Donnie

QuadBart Posted at 2016-4-9 07:23
I'll add that I'm a Mac user and agree that formatting an SD card can be a bit problematic.  BUT o ...

QuadBart, I understand that MAC users can do updates HOWEVER I have found that many pilots  have trouble using the MAC to do updates and format the SD card .  From my perspective I want to inform members that there can be trouble with the MAC's.  I always leave a Caveat that the MAC can be used but only by knowledgeable MAC users.

Please provide your e-mail so I can send the MAC users to you who are having trouble with the FW  issues  and MAC's   (kidding ).......

cheers- donnie

Can some let me know how to turn off Auto Firmware Update on a P3A?  Thank you.  

Avellas Posted at 2016-4-9 07:40
Can some let me know how to turn off Auto Firmware Update on a P3A?  Thank you.

What do you mean?  after you have completed the update to aircraft and RC  is it saying that you need to update again? Be sure that you do a complete Re boot of the System.  Make sure for example on the device ( I-pad or whatever ) that you power off 100%.  If after doing this and it still is requesting update , make sure you  power up in this sequence
1- Transmitter
2-Aircraft
3- Go app  ( the device can be on , just don't open the go app till last )

Or do you not want Auto updates  to occur on your Go app?   The only way you can do this is to change the settings on your device ,( I -pad or whatever), not to auto update.  

Hope this helps- donnie

Hi, I bought  my P3A on May 2015. My bird and RC had 1.4FW until yesterday. Today, I tried to update, but can't update my bird. My RC was updated successfully via DJI Go app(iOS/2.7.1), so the RC has 1.6.0FW. When I check the status with Go App, it shows 1.4.10+ in my bird, 1.6.0 in RC. I can control the bird/cam(no props, in my room/night).

What should I do to update my bird?  

The log is below :

Hidden LOG (the last session)

[00012296]========== 2016.04.09 19:23:25. boot(15) ============
[00012484]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x00002b0c].
[00012562]Packet upgrade start...

[00012653]Packet checking...
[00012733]Packet vlink 01.08.0080 <-> 01.07.0060.
[00012820]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00012898]Done.

[00012984]Version checking[1]...
[00013098][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013238][03 06][00] v2.4.14.5 -> v2.4.14.5
[00013345][04 00][00] v1.44.0.0 -> v1.44.0.0
[00013498][11 00][00] v1.7.15.1 -> v1.7.15.1
[00013626][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013751][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013891][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014026][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014107][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014241][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014421][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014521][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014600][01 00][00] v1.21.3647 -> v1.23.4920 need upgrade
[00014687][01 01][00] v1.23.4920 -> v1.23.4920
[00014801][09 00][00] v3.0.0.10 -> v3.0.0.10
[00014880]Done.

[00016960]Waiting for user confirm...
[00027040]Timeout, start upgrade automatically.

[00027206]Firmware upgrading[1]...
[00044409][01 00] Firmware upgrade start...
[00011740][01 00] Firmware upgrade finished successfully.
[00011826]Done.

[00011908]Packet [C:\P3S_FW_V01.08.0080.bin] resumed, card sn [0x00002b0c].
[00011994]Packet vlink 01.08.0080 <-> 01.07.0060.
[00012077]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00012162]Version checking[2]...
[00012279][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012393][03 06][00] v2.4.14.5 -> v2.4.14.5
[00012487][04 00][00] v1.44.0.0 -> v1.44.0.0
[00012658][11 00][00] v1.7.15.1 -> v1.7.15.1
[00012807][12 00][00] v1.10.0.0 -> v1.10.0.0
[00012934][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013068][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013202][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013283][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013418][17 00][00] v1.1.1.7 -> v1.1.1.7
[00013582][17 01][00] v1.0.2.7 -> v1.0.2.7
[00013780][19 00][00] v1.0.8.96 -> v1.0.8.96
[00013862][01 00][02] v1.21.3647 -> v1.23.4920 need upgrade
[00013948][01 01][00] v1.23.4920 -> v1.23.4920
[00014057][09 00][00] v3.0.0.10 -> v3.0.0.10
[00014146]Done.

[00014226]Firmware upgrading[2]...
[00014314]Done.

[00014393]Version checking[3]...
[00014513][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014634][03 06][00] v2.4.14.5 -> v2.4.14.5
[00014717][04 00][00] v1.44.0.0 -> v1.44.0.0
[00014914][11 00][00] v1.7.15.1 -> v1.7.15.1
[00015062][12 00][00] v1.10.0.0 -> v1.10.0.0
[00015214][12 01][00] v1.10.0.0 -> v1.10.0.0
[00015347][12 02][00] v1.10.0.0 -> v1.10.0.0
[00015482][12 03][00] v1.10.0.0 -> v1.10.0.0
[00015564][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015702][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015882][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015997][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016079][01 00][02] v1.21.3647 -> v1.23.4920 need upgrade
[00016165][01 01][00] v1.23.4920 -> v1.23.4920
[00016257][09 00][00] v3.0.0.10 -> v3.0.0.10
[00016346]Done.

[00016424]Firmware upgrading[3]...
[00016512]Done.

[00016591]Version checking[4]...
[00016714][03 05][00] v34.2.0.9 -> v34.2.0.9
[00016861][03 06][00] v2.4.14.5 -> v2.4.14.5
[00016962][04 00][00] v1.44.0.0 -> v1.44.0.0
[00017117][11 00][00] v1.7.15.1 -> v1.7.15.1
[00017247][12 00][00] v1.10.0.0 -> v1.10.0.0
[00017382][12 01][00] v1.10.0.0 -> v1.10.0.0
[00017502][12 02][00] v1.10.0.0 -> v1.10.0.0
[00017746][12 03][00] v1.10.0.0 -> v1.10.0.0
[00017834][15 00][00] v1.1.2.0 -> v1.1.2.0
[00017962][17 00][00] v1.1.1.7 -> v1.1.1.7
[00018128][17 01][00] v1.0.2.7 -> v1.0.2.7
[00018217][19 00][00] v1.0.8.96 -> v1.0.8.96
[00018302][01 00][02] v1.21.3647 -> v1.23.4920 need upgrade
[00018383][01 01][00] v1.23.4920 -> v1.23.4920
[00018480][09 00][00] v3.0.0.10 -> v3.0.0.10
[00018560]Done.

[00018648]Firmware upgrading[4]...
[00018727]Done.

[00018814]Version checking[5]...
[00018936][03 05][00] v34.2.0.9 -> v34.2.0.9
[00019056][03 06][00] v2.4.14.5 -> v2.4.14.5
[00019259][04 00][00] v1.44.0.0 -> v1.44.0.0
[00019436][11 00][00] v1.7.15.1 -> v1.7.15.1
[00019585][12 00][00] v1.10.0.0 -> v1.10.0.0
[00019728][12 01][00] v1.10.0.0 -> v1.10.0.0
[00019868][12 02][00] v1.10.0.0 -> v1.10.0.0
[00020004][12 03][00] v1.10.0.0 -> v1.10.0.0
[00020087][15 00][00] v1.1.2.0 -> v1.1.2.0
[00020225][17 00][00] v1.1.1.7 -> v1.1.1.7
[00020385][17 01][00] v1.0.2.7 -> v1.0.2.7
[00020482][19 00][00] v1.0.8.96 -> v1.0.8.96
[00020561][01 00][02] v1.21.3647 -> v1.23.4920 need upgrade
[00020652][01 01][00] v1.23.4920 -> v1.23.4920
[00020787][09 00][00] v3.0.0.10 -> v3.0.0.10
[00020867]Done.

[00020957]Firmware upgrading[5]...
[00021036]Done.

[00021122]Version checking[6]...
[00021237][03 05][00] v34.2.0.9 -> v34.2.0.9
[00021357][03 06][00] v2.4.14.5 -> v2.4.14.5
[00021445][04 00][00] v1.44.0.0 -> v1.44.0.0
[00021621][11 00][00] v1.7.15.1 -> v1.7.15.1
[00021750][12 00][00] v1.10.0.0 -> v1.10.0.0
[00021884][12 01][00] v1.10.0.0 -> v1.10.0.0
[00022036][12 02][00] v1.10.0.0 -> v1.10.0.0
[00022169][12 03][00] v1.10.0.0 -> v1.10.0.0
[00022254][15 00][00] v1.1.2.0 -> v1.1.2.0
[00022384][17 00][00] v1.1.1.7 -> v1.1.1.7
[00022542][17 01][00] v1.0.2.7 -> v1.0.2.7
[00022650][19 00][00] v1.0.8.96 -> v1.0.8.96
[00022846][01 00][02] v1.21.3647 -> v1.23.4920 need upgrade
[00022926][01 01][00] v1.23.4920 -> v1.23.4920
[00023030][09 00][00] v3.0.0.10 -> v3.0.0.10
[00023111]Packet upgrade failed at firmware upgrade.

Normal LOG (from 1.0.2)

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.02.0008.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.02.0008.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.04.0010.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

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

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Upgrading ...

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.03.0020.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.06.0040.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.05.0030.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.04.0010.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.04.0010.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.05.0030.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2016.04.09 18:24:37 =====================
Packet: P3S_FW_V01.05.0030.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2016.04.09 18:44:09 =====================
Packet: P3S_FW_V01.06.0040.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2016.04.09 19:03:57 =====================
Packet: P3S_FW_V01.07.0060.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2016.04.09 19:23:24 =====================
Packet: P3S_FW_V01.08.0080.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

doctor_hs@yahoo Posted at 2016-4-9 07:57
Hi, I bought  my P3A on May 2015. My bird and RC had 1.4FW until yesterday. Today, I tried to update ...

Doc, you have 2 different logs here,  I usually look at the bottom one first. You are up to date.  Try and turn off your  device with the Go App and Re- Boot .  Also do a Re- boot of the aircraft and Take it outside and get a GPS lock.

This should update to 1.8  .  You also Have the + sign after the FW  ( 1.4 +)  version, when I first looked I thought it was in Japanese.  

I think you are in business, just do these  steps, : Go app device, turn off device and back on , make sure you have a wireless internet signal to device  ,  restart the aircraft and RC take it ouside for a GPS lock.  The" About " page you listed should roll from 1.4+  to 1.8 .What threw me off was the two seperate files, the top one is success and the very bootm ones are failure.  

donnie

Donnie, thanks!!

I can update my bird to v1.8!

When I finished my bird to V1.7, and I thought V1.8 failed... but  I opened the Go app, it shows V1.8!

Thank you!

*The below is OLD text.
------------------------------
I can update my bird to v1.7! ... but can't to v1.8.

First, I changed the SD card. I used the "TEAM" card before, and changed to the "Transcend" card. I wrote the 1.7FW in it, then I finished updating!
Both cards are the same specification, but the result is different.

The log said : The firmware on the SD card is identical to or older than the current firmware on the aircraft.

How should I do next?

The log is below :

========== 2016.04.09 19:23:24 =====================
Packet: P3S_FW_V01.08.0080.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

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

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

The hidden log is :

[00012936]========== remo-con disconnect. boot(15) ============
[00013015]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x04f00776].
[00013102]Packet upgrade start...

[00013187]Packet checking...
[00013277]Packet vlink 01.07.0060 <-> 01.06.0040.
[00013362]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00013462]Done.

[00013548]Version checking[1]...
[00013663][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013784][03 06][00] v2.4.14.5 -> v2.4.13.0
[00013882][04 00][00] v1.44.0.0 -> v1.41.0.0
[00014149][11 00][00] v1.7.15.1 -> v1.7.15.1
[00014277][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014423][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014562][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014697][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014791][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014936][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015097][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015192][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015285][01 00][00] v1.21.3647 -> v1.23.4920 need upgrade
[00015369][01 01][00] v1.23.4920 -> v1.23.4920
[00015493][09 00][00] v3.0.0.10 -> v2.13.0.0
[00015575]Done.

[00017666]Waiting for user confirm...
[00027757]Timeout, start upgrade automatically.

[00027937]Firmware upgrading[1]...
[00042884][01 00] Firmware upgrade start...
[00011739][01 00] Firmware upgrade finished successfully.
[00011829]Done.

[00011911]Packet [C:\P3S_FW_V01.07.0060.bin] resumed, card sn [0x04f00776].
[00012010]Packet vlink 01.07.0060 <-> 01.06.0040.
[00012094]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00012186]Version checking[2]...
[00012298][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012418][03 06][00] v2.4.14.5 -> v2.4.13.0
[00012513][04 00][00] v1.44.0.0 -> v1.41.0.0
[00012678][11 00][00] v1.7.15.1 -> v1.7.15.1
[00012826][12 00][00] v1.10.0.0 -> v1.10.0.0
[00012951][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013087][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013241][12 03][00] v1.10.0.0 -> v1.10.0.0
[00017832][15 00][00] v1.1.2.0 -> v1.1.2.0
[00017962][17 00][00] v1.1.1.7 -> v1.1.1.7
[00018127][17 01][00] v1.0.2.7 -> v1.0.2.7
[00018222][19 00][00] v1.0.8.96 -> v1.0.8.96
[00018313][01 00][05] v1.23.4920 -> v1.23.4920
[00018397][01 01][00] v1.23.4920 -> v1.23.4920
[00018502][09 00][00] v3.0.0.10 -> v2.13.0.0
[00018586]Packet upgrade finish successfully.



[00013022]========== remo-con disconnect. boot(15) ============
[00013105]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x04f00776].
[00013197]Packet upgrade start...

[00013291]Packet checking...
[00013474]Packet vlink 01.08.0080 <-> 01.07.0060.
[00013576]Record vlink 01.07.0060 <-> 01.06.0040 (flow = 0).
[00013666]Done.

[00013758]Version checking[1]...
[00013879][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013999][03 06][00] v2.4.14.5 -> v2.4.14.5
[00014091][04 00][00] v1.44.0.0 -> v1.44.0.0
[00014263][11 00][00] v1.7.15.1 -> v1.7.15.1
[00014407][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014552][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014692][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014827][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014913][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015047][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015227][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015327][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015411][01 00][00] v1.23.4920 -> v1.23.4920
[00015502][01 01][00] v1.23.4920 -> v1.23.4920
[00015623][09 00][00] v3.0.0.10 -> v3.0.0.10
[00015710]Packet upgrade cancelled at version checking.
  

doctor_hs@yahoo Posted at 2016-4-9 09:34
Donnie, thanks!!

I can update my bird to v1.8!

I knew there was a bad SD card there some where !   At first I read the bottom of the first log, that is where I normally look first  because that would be the most recent.  BUT when I looked more closely  I saw there were 2  logs .  

I am very pleased it is working,  Now go out and FLY  Tomorrow !  Right Now you need Sleep !

Cheers -donnie

I just updated my P3A with iPad Air 2 with no issues, seeing video and started the motors. I will test fly later today once I know I can still feel my fingers after a few minutes of flight...it's way to cold right now. .

xhip Posted at 2016-4-7 07:28
Same... My P3 Pro has been able to upgrade, but the RC hasn't upgraded.
I tried:
- sd card on RC

Normally the RC can be upgraded during wifi connection..it will auto upgrade when u click the apps and going to firmware. That is what happened to me.

ops Posted at 2016-4-7 07:22
My P3 Pro has been able to upgrade, but the RC hasn't upgraded.
Now I am in the same situation as  ...

Normally the RC can be upgraded during wifi connection..it will auto upgrade when u click the apps and going to firmware. That is what happened to me.

rriber Posted at 2016-4-7 07:09
I have the same problem with my p3 adv

Normally the RC can be upgraded during wifi connection..it will auto upgrade when u click the apps and going to firmware. That is what happened to me.

pmb.sergeymalko Posted at 2016-4-7 19:09
Upgrading is a mistake. Me and my friends have updated their Phantom 3 Pro and Adv, and faced with t ...

Hi,

I have the same problem have you been able to fix yours as I have had no luck.

Cheers

John

Donnie Posted at 2016-4-9 06:20
Parts Guy ,the damage occurs when the Aircarft is updating and the Transmitter is ON.   I just  tr ...

Thanks Donnie! Had me worried. Now I just need to figure out the noise issue. Still flies fine but has been producing a squeal? whine? noise in flight. Going to use a infrared gun on the bench today. See if one of the motors runs hotter than the others. Doesn't make the noise on the bench with the props off and outside with the props on at idle. At take off the noise starts I can hear it up to 100' and about 100' away. I've tried turning off the vps and replacing the gimbal cushions. Have blown out the motors with canned air (gently) and inspected the gimbal and the motor housings and cannot see anything amiss except the noise. This started before the update. Any ideas? I tried to upload a short video taken with my phone but it says the file is to big to upload.

rreindl Posted at 2016-4-9 22:53
I just updated my P3A with iPad Air 2 with no issues, seeing video and started the motors. I will te ...

The flight test went very well. I did have to format the SD card just like last time to prevent the random video from stopping.

PartsGuy Posted at 2016-4-10 02:02
Thanks Donnie! Had me worried. Now I just need to figure out the noise issue. Still flies fine but ...

My P3A was doing a whistle like sound for the first few hours of flight then recently has gone away. I think I remember DJI-KEN (??) say this was normal on new drones. Also I do notice I get slightly different sounds in different environment conditions. For example when it is windy compared to when not. Also warmer vs colder.

Hey Guys,

I was flying my drone over a farm house and got to around 200ft, by that time my drone was already over a cliff. Then the worst thing happened! RC signal lost and my P3S was set on hover mode whenever the signal is lost from the controller (Stupid me ). Should be on RTH mode, but oh well..

So now, my drone is happily hovering over a cliff at ~200ft. and i cannot control my drone as there is no signal from the RC! F*ck F*ck F*ck!!!!! I could somehow manage to steer the drone toward me as the signal was coming and going and fnally somehow i could tame my P3S (after running for 2-3 kms around the farm house like a mad person) and could safely land it in front of eyes

Now....

DJI Support - WHAT THE **** GUYS!!!!! :

Latest firmware altered the drone to the bits, I just cannot fly my drone over 150ft as it keeps losing signal. Why why why???? Earlier i have flown this bird to upto 2000ft. but now the performance has gone to the dogs. I need an expanation of what i am doing wrong. I have re-linked the RC, Caliberated it, intalled latest app version 2.7.2 and  done everything by the book.  I dont think i have missed anything.

If there is nothing wrong then i would like you guys to exchange it ASAP!

Appreciate a response withn 24Hrs. I am ready to share my flight logs if you need proofs.

Thanks,
A disgruntled customer

QuadBart Posted at 2016-4-9 08:23
I'll add that I'm a Mac user and agree that formatting an SD card can be a bit problematic.  BUT o ...

why not just format the sd card on  the aircraft  via go app

Posted this info elsewhere, but I think it is connected to the f/w upgrade.

Yesterday I received my brand new P3P, I uploaded GoApp 2.7.2 to my Samsung tablet, upgraded aircraft & battery to 1.8.8, calibrated IMU, then I upgraded the R/C to v. 1.6 via the GoApp. The upgrade finished, and the led turned green on the R/C. I re-booted tablet and RC, calibrated the R/C and did a short test flight for 1 min or so. Everything was OK.

A couple of hours later, I powered up again the RC and the GoApp prompt me again to upgrade the RC!!! I started to upgrade again, and the app message was "Upgarding from v 1.6 to v1.6" or something like that !

The second RC upgrade went as far as 45% and got stuck for more than 30' at that level... finally I had to shut down the RC. Since then, everytime I boot the RC I get the message "No signal" in the app, and a few seconds later the RC buzzer sounds and the RC red led blinks fast. I can not downgrade, because there is no f/w available.  The about section in the gen settings has no serial no. or f/w version info for the RC.

I contacted DJI, but all ideas/suggestions are welcomed!

iOS 9.3.1 on my iPad mini 2 = DJI GO app not connecting

I've updated firmware on both ac and rc, no probs. Updated dji go app and having couple of issues. 1- all settings screens pushed over to the right of tablet screen, 2- no graph showing in video channel screen, 3- red arrow in radar is 90degs off (if ac facing north, arrow pointing west etc) . Anyone have any ideas?

bobhyslop Posted at 2016-4-9 17:12
I've updated firmware on both ac and rc, no probs. Updated dji go app and having couple of issues. 1 ...

Just wondering , do you own a Android device ?  There  is an update for that 2.72.  If you own the apple product  you would be at 2.71.. If you are correct on the proper Go app for your device I would just delete it and re install.  

Donnie

Cheers Downie, yeah on android, deleted and reinstalled a few times but no change. All good on previous app.

Sorry, meant Donnie, I hate predictive text lol

my phantom just make a loud beep and the motors get hot. what happened?

My phontom just make a loud beep and the motors get hot. what happened?

Anyone else having issues with devices on iOS 9.3.1? If so is there a fix for this? Basically all my devices running this iOS will not connect to DJI GO

  
Notes：

l  The firmware can be downgraded to v1.7.0060.
  
l  Both the aircraft and the remote controller must be upgraded or else they will not link.

I'm using iPad air 2 iOS 9.3.1. Guys, I don't know if this will help anyone, but my RC would not link with the aircraft, and I couldn't figure it out. It was because the bird did not update like I thought it did on the first try. The only way I found out was I did an old fashioned update by downloading from the DJI website to my computer (mac), transferred to the SD card on the aircraft and the update ran. After10 minutes the update finished and I fired up the RC, ran the update on it, and voila!

I'm spending more time jacking with the firmware than flying , buy a battery update it , no problems with bird or remote they link up but that dji go app is trying to get me to buy a new phone its not happening went back to 2.6.1 and have live feed, I've only had it for a month , if it was not for this forum I'd be in the dark !

After I update phantom advanced to firmware 1.8.8,Dji Go 2.7.2,My RTH Point is Out Of The Setting Point,whan aircraft return(about 5- 10 Meter) between Setting point,Before I update my Firmware New

Hi! I updated RC,Aircraft,Gimbal and the Android app. Now I'm getting signal loss at 10meters or at 200meters. Whats with this? Can I downgrade the rc firmware or is it in the aircraft firmware?

*edit

And also weird problem when landing, it touched the ground but jumped into the air again. Happened today and yesterday.

*edit2

Flashed back to 1.7.0060, had 5 flight all back to normal now. Not a single signal drop or even a weak signal. Oh and its Phanton 3 Professional.

I think my RC or Bird is stuffed.
Ive been at this for days now looking at nearly every post on here ( thanks for all the help! cheers everyone)
Latest info.
Dji Phantom 3 Advanced purchased in Feb 2016.
I have a iPad Air 2 running 9.3.1 just the Dji Go app ( wifi on, Bluetooth off)
The bird finally gave me a successful update of 1.8.8
Deleted and reinstalled the Go app multiple times.
App on Ipad wont connect to the RC. It comes up with the (page how to connect)
with the RC , Bird and Go app on the c1 button does nothing ( remote wont talk to the bird)

I then shut everything off
Turned on the RC and the bird
Plugged in my Android Sony phone (its on the list also)
started the Go app on it and it came up with the camera button option.
I pressed the camera option and I have the black/dark grey screen with all the menu options.
At this point before the update of the RC I could hit the c1 button and control the camera gimbal straight down and forward etc  (full control of the Bird just no camera view on the screen)
At the same time it said I need a firmware update (whoo hoo. Finally)
Updated the RC through the Go app to version 1.6.0 successfully.
Shut every thing down and restarted the RC then the Bird and then launched the app.
Everything works except the live camera feed on screen which has been intermittent from day one.
When on the menu (about) option It displays:
app version 2.7.2
Version (aircraft) 1.8.80
RC 1.6.0
The funny thing is I just started it on the sony to triple check the firmware versions on screen and stuff me the camera feed is working again!!!! WTF
Shut it all down
Turn on the RC, Bird and launch the Go app on the Ipad
Comes up with the white screen connect your Aircraft ( and yes the lead is good ;) )
I think I have a very wierd problem , possibly an Intermittent video module, but that dosent explain why it half works on a sony.
I am so friggin over this.
Anyway to those that can Happy Flying I will stay tuned.
I reset my Ipad and deleted the app and then installed it through Itunes on my computer instead of through the Ipad and it made no difference.

bobhyslop Posted at 2016-4-9 17:12
I've updated firmware on both ac and rc, no probs. Updated dji go app and having couple of issues. 1 ...

What model do you own specific, Pro or advanced ?  Did you upload the correct go app for the Android 2.7.2 ?  Can you try another device just to test with ? The go app is simple to install and delete.  When you are updating the Go app to the Device make sure you are using a fixed WI-Fi to help eliminate any data  that may be missed on a cell  internet system .  I find it very strange that  you are missing the  graph for the Image transmission settings.  

Let me know .  I thought for sure you  uploaded the wrong go app for sure ( You loaded the standard go  app 2.7.1 on your android which should be 2.7.2

Keep me posted- donnie

SFGiants24 Posted at 2016-4-9 22:24
Notes：

l  The firmware can be downgraded to v1.7.0060.

In the future always check the SD card for Success after updating.  Even-if I hear the proper tones and Light on gimbal goes solid green, check the SD card ALWAYS.  Also the old fashioned way you mention to update the aircraft IS the correct way, how else were you doing it? just curious as to what you meant.

Cheers - donnie

eddycheah Posted at 2016-4-10 00:14
After I update phantom advanced to firmware 1.8.8,Dji Go 2.7.2,My RTH Point is Out Of The Setting Po ...

Make sure  you do an IMU and camera calibration after and update to FW.  Also dont forget a proper compass calibration as well.  This should Improve the RTH   landing point.  

donnie

sandmark Posted at 2016-4-10 06:20
I think my RC or Bird is stuffed.
Ive been at this for days now looking at nearly every post on here ...

     Sandmark You said that you have 2.7.2 Go App loaded on the I pad .  It should be version 2.7.1 .  I wonder if this is the cause of the trouble. How did you load 2.7.2 on the Apple device ? when I go to the app store on my I -pad it is not even  an option.( 2.7.2)

Pleasde keep me posted on this, I hope this helps- donnie

Donnie Posted at 2016-4-10 16:05
Sandmark You said that you have 2.7.2 Go App loaded on the I pad .  It should be version 2.7.1 ...

Hi, I really appreciate the help from here..because I see that more pilots have problems with it. Yesterday I bought a Ph3 advanced (had a Standard for a week and loved it so much that I wanted to make a small step up and saw the advanced  for  a nice price)
Yesterday I flew a little with it and it was great, at the evening I would do a little flight simulation with my son but it did't work because it needed an upgrade!
02.00 in the night I went to bed with a headache and frustrated. Four ours I was trying and no succes.
By accident or I don't know how that went the RC updated first and then I tried and tried to upgrade the 'Bird'
I downloaded the zip file to my macbook downloads and as I see it was already unpack't in a bin file: P3S_FW_V01.08.0080-02.bin
I place this in the root  on the formatted sd card  wich was formatted in the Drone with DJI GO app.
I put it in the Drone and did it on, nothing happend..I tried it many times after formatting card off course .
Than I tried the 1.7.0060 and that worked! After that I tried again with the 1.8.80..and again and again..nothing the drone
was finished after a minut and still no update. During this I did not put on my DC

Situate now is that: the overall status is * Firmware requires upgrade
The app is v 2.7.1
The aircraft is v 1.7.60
The RC is 1.6.0

I hope someone can help?
Thanks
Siep

siep Posted at 2016-4-10 09:30
Hi, I really appreciate the help from here..because I see that more pilots have problems with it.  ...

Are you sure you have the right file? , the Pro and advanced look the Same.  format again from the aircraft and try again.  try a different computer or SD card.  If it took 1.7 it will take 1.8 we are just missing something.  We will get this.    ***Below is just a sasmple, you cant pull the FW here but make sure you get it from the ADVANCED PAGE not pro.  

Donnie