P3 Pro - Beep from Hell !!!

[alokbhargava]

Nope. No such luck yet! I do however have a set of replacement connection wires (part 42, I think) on the way. Hopefully it could be just a bad "grey" wire...(?). When I got this Phantom, it did have some crash damage, including broken yaw arm and the front grey wire's leads were pulled out of its connector. I was able to press the leads back into their respective spots in the connector, and I thought all was well. But I did order the replacement set though..


Sent from my iPhone using PhantomPilots mobile app

I doubted Gimbal gray cables and told you to check in my very first post. Hope new cables work for you.

Per log, you had 1.5 FW on your AC and you are unable to upgrade to 1.8. It will not accept 1.7 anytime. You said you tried 1.7 FW too but it doesn't show any records of it, surprising.

RC 1.6 will not work with any AC FW until you upgrade AC to 1.8.

 

[Anthony Radford]

Hey Alok, although a visual inspection of the visible portion of the grey cables all look good, I opened up my shell today, being I have the new set of cables on the way - on the inside portion of the cable, near the connector on the board, I found that 3 of the 8 wires were severed!


Sent from my iPhone using PhantomPilots mobile app

 

[Anthony Radford]

If THATS not my problem, I don't know what is!


Sent from my iPhone using PhantomPilots mobile app

 

[droneshop]

Force install firmware :

 

[RocketBrew]

Force install firmware :

Is there suppose to be audio on this video?

 

[alokbhargava]

Is there suppose to be audio on this video?

Yes it does have.

 

[alokbhargava]

Force install firmware :

Has any one tried this process? Or should I verify it on my drone?

 

[MikeyOnline]

It looks like this forces the update when you get an "abort" in the log telling you the firmware version on the AC is already the same or later version. My guess is it won't bypass situations where the AC is just failing to do an update (regardless of version).

Mike

 

[RocketBrew]

Has any one tried this process? Or should I verify it on my drone?

I did it recently when I had problems with my controller bricking during the last upgrade. Of course, it didn't help the controller but I figured I would give it a try during the height of my frustration at the time.

 

[alokbhargava]

Has any one tried this process? Or should I verify it on my drone?

I tried it and I was able to RE-INSTALL 1.8.80 on previously installed 1.8.80 FW.

It works, I certify. Not sure about other situations.

 

[Phantom George]

I'm wondering this: it originally had v1.5.xx or v1.6.xx FW, and I was trying to upgrade straight to v1.8.80. Is that correct, or would I have to increment up? Meaning, install v1.7 and then v1.8?


Sent from my iPhone using PhantomPilots mobile app

Yes, I believe you have to increment up if your bird version is to far away from v1.8.
I've always uograded the Fw as it become available and never had any trouble that way.
Hope you get it going alright. These things can be very very frustrating.

 

[Anthony Radford]

Thanks guys. And thanks for that video - very informational!

I believe I have found my problem. The grey cable that goes into the aircraft. I opened the shell, and found 3 of the 8 mini-wires on the bundle are severed near the internal connector. Therefore, the information isn't being transferred on those channels, obviously causing a problem... I have a new set of cables (part 42) on the way now, hopefully will be here on Monday. Aircraft is still disassembled and ready for wire replacement. Will let you all know if that helped.

I want to thank EVERYONE for their help thus far...


Sent from my iPhone using PhantomPilots mobile app

 

[Anthony Radford]

Ok guys - I have replaced ALL the connection wires- grey, black, white and otherwise...

I am STILL having the same update and beeping issues. I have also tried the link button force install idea as well, but no luck. And yes, I have been formatting the card & redownloading the .bin file from the site... Nothing is working!


I'm hoping I don't have a $1000 paperweight!

Sent from my iPhone using PhantomPilots mobile app

 

[Anthony Radford]

.

 

[sdharris]

Apologies as I have only skimmed read the posts so far but the continuous beep is a problem I have had in the past during power on and when trying to apply firmware. Have you checked the detailed logged file in the hidden directory/folder on the SD card. It reveals a lot more information including crucially the current version of each component of the Phantom 3.

From memory about 20 of them and it will go through each determining whether the component needs an upgrade.

When this occurred on mine it go to hardware item 15 and then failed to detect hardware. It clearly said Hardware not found.

To fix it went back to DJI.

 

[Anthony Radford]

Harris- yes, I have checked the log. In fact, I have the text posted in one of my posts if you read up about halfway


Sent from my iPhone using PhantomPilots mobile app

 

[Anthony Radford]

Being I bought this second hand, I don't think warranty/sending it in would be an option?


Sent from my iPhone using PhantomPilots mobile app

 

[sdharris]

Harris- yes, I have checked the log. In fact, I have the text posted in one of my posts if you read up about halfway


Sent from my iPhone using PhantomPilots mobile app

Still not seeing the log file I am refering to. The file is in a hidden folder not visible unless you explicitily ask Windows or OSX to show hidden files and folders. The contents of the file is detailed and will show something like the below...

[00027520]Firmware upgrading[1]...
[00027754][03 06] Firmware upgrade start...
[00355344][03 06] Firmware upgrade finished successfully.
[00355418]Done.

[00355487]Version checking[2]...
[00355608][03 05][00] v34.2.0.9 -> v34.2.0.9
[00355728][03 06][05] v2.3.0.13 -> v2.3.0.13
[00355808][04 00][00] v1.41.0.0 -> v1.41.0.0
[00355908][09 00][00] v1.7.0.3 -> v1.7.0.3
[00356072][11 00][00] v1.7.0.0 -> v1.7.0.0
[00356197][12 00][00] v1.10.0.0 -> v1.10.0.0
[00356329][12 01][00] v1.10.0.0 -> v1.10.0.0
[00356457][12 02][00] v1.10.0.0 -> v1.10.0.0
[00356602][12 03][00] v1.10.0.0 -> v1.10.0.0
[00356766][15 00][00] v1.1.2.0 -> v1.1.2.0
[00356897][17 00][00] v1.1.1.7 -> v1.1.1.7
[00357056][17 01][00] v1.0.2.7 -> v1.0.2.7
[00357168][19 00][00] v1.0.8.96 -> v1.0.8.96
[00357240][01 00][00] v1.23.3419 -> v1.23.3419
[00357387][01 01][00] v1.23.3419 -> v1.23.3419
[00357469][08 00][00] v0.12.0.4 -> v0.12.0.4
[00357541]Packet upgrade finish successfully.​

If a piece of hardware within the P3 is not functioning the beep occurs when it trys to check its firmware level.

Again, sorry if I am being daft here but I could only find the generic high level log that is in the root of the SD Card.

 

[Anthony Radford]

Here's the hidden log:

[00017223]Delete history success.

[00017459]========== remo-con disconnect. boot(5) ============
[00017539]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00017618]Packet upgrade start...

[00017700]Packet checking...
[00017781]Packet vlink 01.08.0080 <-> 01.07.0060.
[00017861]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00017942]Done.

[00018022]Version checking[1]...
[00018131][03 05][00] v34.2.0.9 -> v34.2.0.9
[00018236][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00018332][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00018859]========== remo-con disconnect. boot(5) ============
[00018939]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00019018]Packet upgrade start...

[00019099]Packet checking...
[00019181]Packet vlink 01.08.0080 <-> 01.07.0060.
[00019261]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00019341]Done.

[00019420]Version checking[1]...
[00019538][03 05][00] v34.2.0.9 -> v34.2.0.9
[00019657][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00019751][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00018860]========== remo-con disconnect. boot(5) ============
[00018941]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00019021]Packet upgrade start...

[00019102]Packet checking...
[00019183]Packet vlink 01.08.0080 <-> 01.07.0060.
[00019263]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00019343]Done.

[00019422]Version checking[1]...
[00019531][03 05][00] v34.2.0.9 -> v34.2.0.9
[00019631][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00019716][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00032296][11 00][00] device not detected.
[00018864]========== remo-con disconnect. boot(5) ============
[00018944]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00019024]Packet upgrade start...

[00019105]Packet checking...
[00019187]Packet vlink 01.08.0080 <-> 01.07.0060.
[00019267]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00019468]Done.

[00019548]Version checking[1]...
[00019657][03 05][00] v34.2.0.9 -> v34.2.0.9
[00019782][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00019870][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00032460][11 00][00] device not detected.
[00045055][12 00][00] device not detected.
[00020866]========== remo-con disconnect. boot(5) ============
[00020947]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00021027]Packet upgrade start...

[00021108]Packet checking...
[00021189]Packet vlink 01.08.0080 <-> 01.07.0060.
[00021269]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00021349]Done.

[00021429]Version checking[1]...
[00021526][03 05][00] v34.2.0.9 -> v34.2.0.9
[00021626][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00021711][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00034290][11 00][00] device not detected.
[00046870][12 00][00] device not detected.
[00059451][12 01][00] device not detected.
[00016902]========== remo-con disconnect. boot(5) ============
[00016986]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00017066]Packet upgrade start...

[00017150]Packet checking...
[00017233]Packet vlink 01.08.0080 <-> 01.07.0060.
[00017321]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00017403]Done.

[00017484]Version checking[1]...
[00030066][03 05][00] device not detected.
[00042648][03 06][00] device not detected.
[00042748][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00055330][11 00][00] device not detected.
[00016882]========== remo-con disconnect. boot(5) ============
[00016964]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00017045]Packet upgrade start...

[00017129]Packet checking...
[00017210]Packet vlink 01.08.0080 <-> 01.07.0060.
[00017291]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
.4.0.5 need upgrade. [00016878]========== remo-con disconnect. boot(5) ============
[00016960]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00017165]Packet upgrade start...

[00017249]Packet checking...
[00017332]Packet vlink 01.08.0080 <-> 01.07.0060.
[00017412]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00017492]Done.

[00017583]Version checking[1]...
[00030163][03 05][00] device not detected.
[00042743][03 06][00] device not detected.
[00042839][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00016878]========== remo-con disconnect. boot(5) ============
[00016961]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00017042]Packet upgrade start...

[00017128]Packet checking...
[00017210]Packet vlink 01.08.0080 <-> 01.07.0060.
[00017291]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00017373]Done.

[00017453]Version checking[1]...
[00018886]========== remo-con disconnect. boot(2) ============
[00018969]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00019049]Packet upgrade start...

[00019133]Packet checking...
[00019214]Packet vlink 01.08.0080 <-> 01.07.0060.
[00019295]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00019377]Done.

[00019457]Version checking[1]...
[00018905]========== remo-con disconnect. boot(5) ============
[00018987]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00019067]Packet upgrade start...

[00019151]Packet checking...
[00019233]Packet vlink 01.08.0080 <-> 01.07.0060.
[00019313]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00019395]Done.

[00019476]Version checking[1]...
[00032058][03 05][00] device not detected.
[00044640][03 06][00] device not detected.
[00044741][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00020891]========== remo-con disconnect. boot(5) ============
[00020973]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x2877ba71].
[00021053]Packet upgrade start...

[00021137]Packet checking...
[00021218]Packet vlink 01.08.0080 <-> 01.07.0060.
[00021299]Record vlink 01.05.0030 <-> 01.04.0010 (flow = 0).
[00021464]Done.

[00021546]Version checking[1]...
[00034127][03 05][00] device not detected.
[00046707][03 06][00] device not detected.
[00046807][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00059388][11 00][00] device not detected.
[00071969][12 00][00] device not detected.



Sent from my iPhone using PhantomPilots mobile app

 

[Anthony Radford]

That was after letting it run for 1 1/2 hours, and I utilized the Link Button trick that time as well...


Sent from my iPhone using PhantomPilots mobile app