Firmware upgrade, now P3P just beeps
1076 11 2016-6-18
Uploading and Loding Picture ...(0/1)
o(^-^)o
Capt. Wild Bill
lvl.4
Flight distance : 1319180 ft
  • >>>
United States
Offline

Did the fw upgrade, checked the sd card and showed a "success". So I powered up and now then P3P just beeps continually. I had flown the P3P a half and hour before the ugrade w/o any issues..

Anyone else having an issue?
2016-6-18
Use props
todd
lvl.2
Flight distance : 1063389 ft
  • >>>
United States
Offline

Did you delete the bin file from the SD card after you were done with the upgrade?
2016-6-18
Use props
Capt. Wild Bill
lvl.4
Flight distance : 1319180 ft
  • >>>
Offline

todd@copelandho Posted at 2016-6-19 06:16
Did you delete the bin file from the SD card after you were done with the upgrade?

Yes why?
It showed success..
2016-6-18
Use props
Capt. Wild Bill
lvl.4
Flight distance : 1319180 ft
  • >>>
United States
Offline

todd@copelandho Posted at 2016-6-19 06:16
Did you delete the bin file from the SD card after you were done with the upgrade?

Yes why?
It showed success..
2016-6-18
Use props
Capt. Wild Bill
lvl.4
Flight distance : 1319180 ft
  • >>>
Offline

todd@copelandho Posted at 2016-6-19 06:16
Did you delete the bin file from the SD card after you were done with the upgrade?

Yes why?
It showed success..
2016-6-18
Use props
larryallison
New

Nigeria
Offline

I have similar issue , the aircraft light is off and continuous bleeding. Help
2016-6-18
Use props
Steelman
lvl.1

United States
Offline

Hi guys,  I too had problems with Upgrade/Update.  My problem was that the RC and the Aircraft would not link even though it showed green light on both.
Here is what I did to fix it.

Remove SD card,  Hard format (not quick format)
Put ver. 1.8 on the card
Plug it in and start the aircraft only
after done,  check .txt file for success
then hard format again, put ver. 1.9 on the card and plug it in and start the aircraft again.
this time when I got done I had success again and it connected and worked fine.
BTW I kept the ver. 1.9 in the aircraft so that each battery I plugged in updated properly.
You don't need to remove the .bin file, it just ignores the file if it is same version as on the aircraft now.
OK, gotta go fly!  Hope it works for you guys.
Steelman
2016-6-19
Use props
dansteidl
lvl.1
Offline

same issue, double beep constantly when i turn it on and the green yellow and red under lights cycle over and over as it's beeping after a completed update.  The light on the front of the gimbal is solid green.  I got the success message from the update.  It appears all updated correctly but something just isn't right now.  I have updated the firmware in the past with no issues, now this update seems to be causing a lot of people issues.

========== 2016.06.19 03:43:22 =====================
Packet: P3X_FW_V01.09.0060.bin
Upgrading ...
Result: Success.

The only thing the controller does is tilts the camera, I have no other controller functions other than that.  If I put the card back in with the firmware, it tells me it already is up to date.

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

It was working fine right before I updated.  I also updated the remote through the app, and now I can't even get the remote to recognize that the iPad is even plugged in, anything that I plug in to the usb on the controller doesn't even light up.  It's as if the remote update broke the USB port, and I am seeing 100s of other people on the forums saying the same thing.  I am on the newest version of the Go app and the newest version of iOS.
2016-6-19
Use props
pgrover516
Banned

United States
Offline

Tip: the author has been banned or deleted automatically shield
2016-6-19
Use props
dansteidl
lvl.1
Offline

I am able to switch upgrades fine, went back to 1.8 and the text log said success.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.08.0080.bin
Upgrading ...
Result: Success.

It is still beeping though and unresponsive minus the gimbal.  formatted again and installed back to 1.9 and it again said success but the same result, nothing is working.  I still can't even get the remote to detect anything plugged into the USB slot and the phantom just keeps double beeping while flashing the 3 colors lights underneath but the gimabl light remains solid green.

========== 2016.06.19 03:43:22 =====================
Packet: P3X_FW_V01.09.0060.bin
Upgrading ...
Result: Success.
2016-6-19
Use props
DJI-Paladin
Administrator
Flight distance : 2408 ft
Hong Kong
Offline

Hello Bill, usually the this kind of beeping is related to an unsuccessful upgrade process. Format the SD card and extract the bin file to the card then run the upgrading again.Keep your eyes on the camera indicator. Feel free to post the log here and you can find the upgrade log by these steps:
1. Enable the option of viewing hidden files in your OS. Below are the websites where you can check how to show the hidden files in your PC.
For The Windows System:
http://windows.microsoft.com/en-us/windows/show-hidden-files#show-hidden-files=windows-7
For The Mac System:
http://ianlunn.co.uk/articles/quickly-showhide-hidden-files-mac-os-x-mavericks/
2.Enter the root directory of the SD card, then find the hidden folder MISC and enter it. There is LOG folder in it.
3.The LOG txt file is under the LOG folder. 升级指示灯.JPG
2016-6-19
Use props
dansteidl
lvl.1
Offline

I have done all of this as well, I even get the successful update but the thing just keeps double beeping with the lights blinking.  the light on the gimbal is solid green but the phantom does a double beep with a pause between over and over.

[00013460]========== remo-con disconnect. boot(15) ============
[00013499]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x0d0e2e98].
[00013540]Packet upgrade start...

[00013583]Packet checking...
[00013633]Packet vlink 01.09.0060 <-> 01.08.0080.
[00013673]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00013714]Done.

[00013754]Version checking[1]...
[00013827][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013905][03 06][00] v2.4.14.5 -> v2.4.20.18 need upgrade.
[00013956][04 00][00] v1.44.0.0 -> v1.44.0.0
[00014065][11 00][00] v1.8.0.0 -> v1.8.0.0
[00014185][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014228][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014325][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014414][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014514][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014621][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014752][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014834][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014953][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015003][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015050][01 00][00] v1.30.5036 -> v1.30.5036
[00015091][01 01][00] v1.30.5036 -> v1.30.5036
[00015144][08 00][00] v0.13.0.7 -> v0.13.0.7
[00015204][09 00][00] v3.0.0.10 -> v3.0.0.10
[00015250]Done.

[00017292]Waiting for user confirm...
[00027332]Timeout, start upgrade automatically.

[00027414]Firmware upgrading[1]...
[00027702][03 06] Firmware upgrade start...
[00386389][03 06] Firmware upgrade finished successfully.
[00386431]Done.

[00386468]Version checking[2]...
[00386554][03 05][00] v34.2.0.9 -> v34.2.0.9
[00386649][03 06][05] v2.4.20.18 -> v2.4.20.18
[00386705][04 00][00] v1.44.0.0 -> v1.44.0.0
[00386853][11 00][00] v1.8.0.0 -> v1.8.0.0
[00386969][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00387110][11 01][00] v1.8.0.0 -> v2.0.0.33
[00387230][12 00][00] v1.10.0.0 -> v1.10.0.0
[00387320][12 01][00] v1.10.0.0 -> v1.10.0.0
[00387415][12 02][00] v1.10.0.0 -> v1.10.0.0
[00387527][12 03][00] v1.10.0.0 -> v1.10.0.0
[00387683][15 00][00] v1.1.2.0 -> v1.1.2.0
[00387798][17 00][00] v1.1.1.7 -> v1.1.1.7
[00388478][17 01][00] v0.0.0.0 -> v1.0.2.7 need upgrade.
[00388544][19 00][00] v1.0.8.96 -> v1.0.8.96
[00388589][01 00][00] v1.30.5036 -> v1.30.5036
[00388634][01 01][00] v1.30.5036 -> v1.30.5036
[00388684][08 00][00] v0.13.0.7 -> v0.13.0.7
[00388744][09 00][00] v3.0.0.10 -> v3.0.0.10
[00388789]Done.

[00388838]Firmware upgrading[2]...
[00388897][17 01] Firmware upgrade start...
[00446536][17 01] Firmware upgrade finished successfully.
[00446581]Done.

[00446626]Version checking[3]...
[00446693][03 05][00] v34.2.0.9 -> v34.2.0.9
[00446773][03 06][05] v2.4.20.18 -> v2.4.20.18
[00446823][04 00][00] v1.44.0.0 -> v1.44.0.0
[00447073][11 00][00] v1.8.0.0 -> v1.8.0.0
[00447193][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00447237][11 01][00] v1.8.0.0 -> v2.0.0.33
[00447353][12 00][00] v1.10.0.0 -> v1.10.0.0
[00447442][12 01][00] v1.10.0.0 -> v1.10.0.0
[00447538][12 02][00] v1.10.0.0 -> v1.10.0.0
[00447647][12 03][00] v1.10.0.0 -> v1.10.0.0
[00447782][15 00][00] v1.1.2.0 -> v1.1.2.0
[00447881][17 00][00] v1.1.1.7 -> v1.1.1.7
[00448001][17 01][05] v1.0.2.7 -> v1.0.2.7
[00448067][19 00][00] v1.0.8.96 -> v1.0.8.96
[00448109][01 00][00] v1.30.5036 -> v1.30.5036
[00448151][01 01][00] v1.30.5036 -> v1.30.5036
[00448206][08 00][00] v0.13.0.7 -> v0.13.0.7
[00448287][09 00][00] v3.0.0.10 -> v3.0.0.10
[00448329]Packet upgrade finish successfully.
2016-6-19
Use props
Advanced
You need to log in before you can reply Login | Register now

Credit Rules