Strange behaviour from phantom 3 std RC

I have a thought about your P3S that you may not want to hear, unfortunately. I had a similar problem following a crash (I thought it was a moderate crash, with nothing broken except 1 prop). My main control board had been damaged and was replaced. Expensive fix, but effective.

Good luck.
 
Thanks guys, do you think the camera can just pack in like that, I mean it wasn't hit in the crash (I think!) because drone was moving very slow and when watching the footage, you still see the video from drone when it's lying on the ground (after crash).
My theory is this, after repairing damage, when I interrupted the firmware upgrade and ended up with the VERY loud beeping stage, then waiting through this until loud beeping stopped, the firmware upgrade continued for around 15 mins then stopped with the dreaded continuous beep, I think the drone has updated and the RC hasn't, meaning we now have different versions of firmware, is this possible or am I now clutching at straws here!
Greig
Interrupt a firware upgrade is guaranteed FW failure. Redoing the upgrade using Solentlife's technique may work if fw failure is the problem. Otherwise, and highly likely, the gimble is toast assuming the firmware upgrade and re-linking if necessary go successfully.
 
My first P3S had a catastrophic crash. Hit a side of a tower and fell 60ft. The camera case had a dent in it and it wouldn't connect to the android tablet. As cost for a new camera and base plate cost more than half the cost of a new P3S and I didn't know if there was more internal damage so I bit the bullet and purchased a new replacement.

The original still flies with it's r/c and returns to home when the r/c is switched off but I cannot set parameters so it is there for spares.

Since the crash I don't fly now without prop guards fitted. The mounts for the guards provide extra strength at the point where others have reported cracks.
 
This may be a long shot but in the app have you tried the imu calibration and the camera calibration? It may spring it back into life.

Failing that I had a crash where the camera snapped off, shell was damaged and it wasn't under warranty. So I sent it to DJI. The cost of the repair..... £90. Bargain. Might be worth sending it off mate esp as mine was cheap and seems to have more damage then yours
 
It was in the Netherlands if I remember correctly. Took about 3 weeks for them to repair it and send it back
 
Hi guys
Sorry for lack of posts but here is the lasted info from the hidden fields on SD card after another failed update.

[00107303]========== remo-con disconnect. boot(15) ============
[00107387]Packet [C:\P3C_FW_V01.09.0200.bin] detected, card sn [0xd1cc105a].
[00107462]Packet upgrade start...

[00107551]Packet checking...
[00107627]Packet vlink 01.09.0200 <-> 00.00.0000.
[00107705]Record vlink 01.08.0100 <-> 00.00.0000 (flow = 0).
[00107786]Done.

[00107870]Version checking[1]...
[00107967][04 00][00] v1.51.0.0 -> v1.51.0.0
[00108139][11 00][00] v2.0.0.33 -> v1.8.0.0, firmware v2.0.0.33 not support.
[00108219][11 00][00] v2.0.0.33 -> v1.8.0.0
[00108372][11 01][00] v2.0.0.33 -> v2.0.0.33
[00108448][01 00][00] v1.14.4920 -> v1.14.4920
[00108535][01 01][00] v1.14.4920 -> v1.14.4920
[00108659][03 05][00] v34.2.0.9 -> v34.2.0.9
[00108818][03 06][00] v2.4.20.50 -> v2.4.20.50
[00121413][07 00][00] device not detected.
[00121518][09 00][00] v0.1.1.1 -> v0.1.1.1
[00121685][12 00][00] v5.9.0.0 -> v5.9.0.0
[00121839][12 01][00] v5.9.0.0 -> v5.9.0.0
[00121981][12 02][00] v5.9.0.0 -> v5.9.0.0
[00122139][12 03][00] v5.9.0.0 -> v5.9.0.0
[00122217]Packet upgrade failed at version checking.

This means absolutely nothing to me, sorry, any advice would be greatly appreciated
Thanks guys
Greig
 
What is the date time on this file, so you know it is current.
Some know what all of this means, i don't.

Rod
 

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,094
Messages
1,467,600
Members
104,980
Latest member
ozmtl