Hi all,
I have a P3 professional purchased in november 2015 here in Italy. I flew it only 5 times without ank kind of problem. Last flight was in june. two days ago I recharged both the controller and the battery but when I powered on the drone I discovered the camera doesn't send anymore the video signal. I tried to use different tablets but nothing changed. After this, since the fw was very old I tried to upgrade bot the controller now is at the latest release but the drone sistematically fails the upbrade. I tested using all the releases available on the DJI site. I tried alsto to reformat the sdcard... i tried also a different sdcard. nothing! the camera doesn't send the video. Now the djgo declares all the platform is upgraded but the upgrade process still finishes with a indefinite DDDDDDD sound and the text log reports only upgrade FAILS and the video is absent...

Any suggestion ?

Hi Lastorri, have you tried to format SD card, then put the bin file into the root of SD card and try again?
Then please check the upgrading log for the details as the instructions:
1. Enable 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- ... den-files=windows-7 For The Mac System: http://ianlunn.co.uk/articles/qu ... 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.

Ok I did it. These are  the last messages:
[00013490]========== remo-con disconnect. boot(15) ============
[00013545]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x2850ca52].
[00013598]Packet upgrade start...

[00013663]Packet checking...
[00013718]Packet vlink 01.09.0060 <-> 01.08.0080.
[00013773]Record vlink 01.04.0010 <-> 01.03.0020 (flow = 0).
[00013834]Done.

[00013888]Version checking[1]...
[00014086][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014184][03 06][00] v2.4.20.18 -> v2.4.20.18
[00014252][04 00][00] v1.44.0.0 -> v1.44.0.0
[00014387][11 00][00] v1.8.0.0 -> v1.8.0.0
[00014544][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014600][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014718][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014833][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014933][12 02][00] v1.10.0.0 -> v1.10.0.0
[00015039][12 03][00] v1.10.0.0 -> v1.10.0.0
[00027603][15 00][00] device not detected.
[00027714][17 00][00] v1.1.1.7 -> v1.1.1.7
[00027864][17 01][00] v1.0.2.7 -> v1.0.2.7
[00027946][19 00][00] v1.0.8.96 -> v1.0.8.96
[00028001][01 00][00] v1.30.5036 -> v1.30.5036
[00028077][01 01][00] v1.30.5036 -> v1.30.5036
[00040634][08 00][00] device not detected.
[00040726][09 00][00] v3.0.0.10 -> v3.0.0.10
[00040780]Packet upgrade failed at version checking.

lastorri Posted at 2016-10-17 18:24
Ok I did it. These are  the last messages:
[00013490]========== remo-con disconnect. boot(15) ====== ...

According to the log, because device not detected for two modules (08 and 15), which needs to be fixed by our engineers.
Please feel free to contact our tech support at support.eu@dji.com for further help.
Sorry again for the trouble.

I sent an email to the support.eu@ ...

BTW: also in my P3P logs I have the device 8 and 15 not detected, but my P3P works fine

Thank you

I'm having the exact same problem. Seems to be a bit of a design flaw if you ask me... I was in a similar situation - have had the drone for a little over a year but only been able to fly it a few times. It's been in a box in an air conditioned room since March (I know...) and now those two modules are failing. Sorry you're experiencing this as well, but it's good to know that I'm not alone.

jdavcfy Posted at 2016-10-17 20:38
I'm having the exact same problem. Seems to be a bit of a design flaw if you ask me... I was in a si ...

I do have the same exact problem with a P3P drone.

It sound like there is a major FLAW with the update.


[00015842]========== remo-con disconnect. boot(15) ============
[00015918]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x41410a6e].
[00015990]Packet upgrade start...
[00016069]Packet checking...
[00016144]Packet vlink 01.09.0060 <-> 01.08.0080.
[00016219]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00016290]Done.
[00016366]Version checking[1]...
[00016487][03 05][00] v34.2.0.9 -> v34.2.0.9
[00016608][03 06][00] v2.4.20.18 -> v2.4.20.18
[00016686][04 00][00] v1.44.0.0 -> v1.44.0.0
[00016846][11 00][00] v1.8.0.0 -> v1.8.0.0
[00017034][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00017106][11 01][00] v1.8.0.0 -> v2.0.0.33
[00017241][12 00][00] v1.10.0.0 -> v1.10.0.0
[00017353][12 01][00] v1.10.0.0 -> v1.10.0.0
[00017477][12 02][00] v1.10.0.0 -> v1.10.0.0
[00017616][12 03][00] v1.10.0.0 -> v1.10.0.0
[00030188][15 00][00] device not detected.
[00030311][17 00][00] v1.1.1.7 -> v1.1.1.7
[00030496][17 01][00] v1.0.2.7 -> v1.0.2.7
[00030609][19 00][00] v1.0.8.96 -> v1.0.8.96
[00030678][01 00][00] v1.30.5036 -> v1.30.5036
[00030765][01 01][00] v1.30.5036 -> v1.30.5036
[00043336][08 00][00] device not detected.
[00043427][09 00][00] v3.0.0.10 -> v3.0.0.10
[00043499]Packet upgrade failed at version checking.

I discovered a pinched wire going to the video encoder board in mine while trying to figure out what was going on. I'm starting to wonder if that could be the problem. I'm going to do some further testing tonight when I have better tools to see if that could be the culprit. Though the number of people having the same problem after this update is concerning me...