Updating Firmware issue, Beeping

[Jonathan M Halley]

I am updating my BRAND NEW out of box copter.

I followed the steps given by DJI for updating. However, I may have stopped it before it was completely done.

I am now getting a constant loud beep from the time I turn it on in addition to the beeping for the upgrade...

It will begin the update (changing red and green)... I've let it sit for 20min and it finishes with a solid green light... the LOUD beeping continues on....

I've tried reformatting the card on the copter and doing a fresh install of the firmware but the same thing continues.

Any thoughts???

PS, when I run the app and connect the RC, I get a Camera Needs Upgrade and Gimbal Cannot receive MC data

 

[msinger]

Try following these instructions exactly:
http://www.phantompilots.com/threads/how-to-install-phantom-3-firmware.45178

 

[bobmyers]

I am updating my BRAND NEW out of box copter.

I followed the steps given by DJI for updating. However, I may have stopped it before it was completely done.

I am now getting a constant loud beep from the time I turn it on in addition to the beeping for the upgrade...

It will begin the update (changing red and green)... I've let it sit for 20min and it finishes with a solid green light... the LOUD beeping continues on....

I've tried reformatting the card on the copter and doing a fresh install of the firmware but the same thing continues.

Any thoughts???

PS, when I run the app and connect the RC, I get a Camera Needs Upgrade and Gimbal Cannot receive MC data

Have you check the text file on the SD card.. If the upgrade was successful, it should read Successful.
If not, do the upgrade again, and put the Phantom behind closed door and check on it in 30 minutes-- then check the text file on the SD Card and get back on the forum with the results if the upgrade was not successful as reported the text file.
That reading will confirm whether the P3 is ready to fly.

There have been numerous upgrade problems with reports of upgrading from 1.1.9 to 1.2.6 or 1.2.8. There also have been successful upgrades to this version and also reports of problems following the upgrades. DJI has promised a fix-- several weeks ago.
Check it out and report back.

 

[Jonathan M Halley]

Have you check the text file on the SD card.. If the upgrade was successful, it should read Successful.
If not, do the upgrade again, and put the Phantom behind closed door and check on it in 30 minutes-- then check the text file on the SD Card and get back on the forum with the results if the upgrade was not successful as reported the text file.
That reading will confirm whether the P3 is ready to fly.

There have been numerous upgrade problems with reports of upgrading from 1.1.9 to 1.2.6 or 1.2.8. There also have been successful upgrades to this version and also reports of problems following the upgrades. DJI has promised a fix-- several weeks ago.
Check it out and report back.

OK, I started that 20min ago.. I'm gonna give it 40, just in case.... I'll post the txt file info in just a bit. Stand by!

 

[Jonathan M Halley]

HERE IS THE STRAIGHT COPY AND PASTE AFTER 40 MIN of updating. When I powered off, the gimbal light was solid green... The REALLY LOUD beeping was still going as well as the update beeping... I couldn't tell what the rythm of the second beeping was.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 18:30:45 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 18:33:17 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 19:20:10 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 19:52:02 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2015.07.29 20:35:16 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 20:36:14 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

 

[jryser]

I would get another MICRO SD card and try again. I wonder if you have a bad card.


Sent from my PT beating heart

 

[Jonathan M Halley]

Would that explain the gimbal MC data issue as well?

 

[bobmyers]

HERE IS THE STRAIGHT COPY AND PASTE AFTER 40 MIN of updating. When I powered off, the gimbal light was solid green... The REALLY LOUD beeping was still going as well as the update beeping... I couldn't tell what the rythm of the second beeping was.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 18:30:45 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 18:33:17 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 19:20:10 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 19:52:02 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Upgrading ...

========== 2015.07.29 20:35:16 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2015.07.29 20:36:14 =====================
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin

 

[bobmyers]

Would that explain the gimbal MC data issue as well?

I agree-- yes it could-- there have been reports of bad SD cards -- If you have a camera card or other mini laying around -- try that out -- check Phantomhelp.com for compatable SD cards.

 

[Jonathan M Halley]

Ok. I ran out and got another card and have started the update. I noticed that the green and red flashing started (on the gimbal) Then I am now getting a solid red light...

 

[bobmyers]

Ok. I ran out and got another card and have started the update. I noticed that the green and red flashing started (on the gimbal) Then I am now getting a solid red light...

Give it plenty of time and check the text file again.

 

[jryser]

Listen for the beep tone rhythm to be what it says in the update manual


Sent from my PT beating heart

 

[Albert R.]

My experience was similar to yours.
http://www.phantompilots.com/index....mware-update-"bug-ridden"?.45742/#post-424502

 

[Jonathan M Halley]

Thanks for the posts guys. I talked with DJI support, they were actually pretty helpful... Surprising considering their reputation.

They suggested I give it one more go at the install then contact the LA office. So, I tried it once more and it worked!!! I can't believe it! Thanks for the help guys!