DJI P3 Pro Update Device Subsystem Numbers from failed FW update
1973 13 2015-11-9
Uploading and Loding Picture ...(0/1)
o(^-^)o
m4schler
New

United States
Offline

So I have encountered the dreaded device [15 00] and [08 00] device not detected firmware update failure.  First, does anyone have a list of what the device numbers actually relate to?  Second, it seems that MANY here have encountered this same issue.  In my case, the DJI P3 Pro has been sitting on the test bench since the last update and I have never flown it or moved it, so I fail to see how this could be related to a true hardware failure.  I have visually checked the cables and all appears to be connected well.  I will try reseating them CAREFULLY tonight, but the only thing I did between the last successful update and the latest failed update was to remove the foam piece above the gimbal that I did not realize was there until the first pass at upgrading to 1.04.0010 via SD card failed (I'm using the original SD card and a fresh battery).  I'm pretty sure I didn't disrupt any cables in that process, as my visual examination occured AFTER i removed the foam piece.

Like I said, it seems there are WAY too many people on here with failed updates on the same subsystem devices for this not to be an engineering or QA failure on the part of DJI.

Any help anyone can provide would be helpful.  I continue to believe that there is nothing physically wrong with the P3 Pro, but rather a malfunction of the update.

Regards,
Matt Foerschler

2015-11-9
Use props
m4schler
New

United States
Offline

So, in looking at the logs from last night, I believe that I can safely assume the device [11 00] is the battery.  I have 2 batteries and I switched them last night to the effect of an update to the [11 00] subsystem.  So, SOMETHING is actually working in the firmware update.  Actually, most every other subsystem found DID update.  It's just those darned [15 00] and [08 00] subsystems that have disappeared from the aircraft.
2015-11-9
Use props
Xterminator.971
lvl.1

France
Offline

can you post a log file to compare with mine I have the same problem

thank  !
2015-11-10
Use props
rodger
First Officer
Flight distance : 20145135 ft
  • >>>
United States
Offline

Possible damage to the Gimbal?? Just a guess. With the foam left in place there would be a lot of strain on the Gimbal with power applied.
2015-11-10
Use props
m4schler
New

United States
Offline

rodger Posted at 2015-11-10 07:56
Possible damage to the Gimbal?? Just a guess. With the foam left in place there would be a lot of st ...

I would grant that, but the gimbal subsystem seems to be working fine.  It's that camera and video comms that are not working and none of the ribbon cables are damaged ill seated in their connectors.  Thanks for the response, though.
2015-11-10
Use props
m4schler
New

United States
Offline

Having been asked to post a recent log, I've included it below.  It follows EXACTLY what many others are seeing after trying this update.  As I've said above, the video was working after the initial update because I leveled the camera after that update using the video link to the iPad Mini.  Last night I tried to connect to the P3 again and get the dreaded No Signal in the header (on the latest RC firmware) and no video in the window.  The gimbal and all other functions seem to be operating normally.  Again, I did NOT fly it but only bench tested it without props.  Takeoff sequence seem to initiate with no problems.

Here is the log showing the nondetected subsystems.  I validated that all cables and connectors are firmly seated and no wire seems to be out of place connecting the camera/gimbal assembly to the main aircraft.

[00014230][01 00] Firmware upgrade finished successfully.
[00014342]Done.

[00014372]Packet [C:\P3X_FW_V01.04.0010.bin] resumed, card sn [0xa0ce1b4a].
[00014414]Packet vlink 01.04.0010 <-> 01.03.0020.
[00014482]Version checking[2]...
[00014550][03 05][00] v34.2.0.8 -> v34.2.0.9 need upgrade.
[00014634][03 06][00] v2.1.6.18 -> v2.3.0.13 need upgrade.
[00014670][04 00][00] v1.36.0.0 -> v1.41.0.0 need upgrade.
[00014734][09 00][00] v1.7.0.3 -> v1.7.0.3
[00014850][11 00][00] v1.6.0.0 -> v1.7.0.0 need upgrade.
[00014924][12 00][00] v1.8.0.0 -> v1.10.0.0 need upgrade.
[00015006][12 01][00] v1.8.0.0 -> v1.10.0.0 need upgrade.
[00015083][12 02][00] v1.8.0.0 -> v1.10.0.0 need upgrade.
[00015159][12 03][00] v1.8.0.0 -> v1.10.0.0 need upgrade.
[00027693][15 00][00] device not detected.
[00027779][17 00][00] v1.1.1.2 -> v1.1.1.7 need upgrade.
[00027899][17 01][00] v1.0.2.4 -> v1.0.2.7 need upgrade.
[00027954][19 00][00] v1.0.8.59 -> v1.0.8.96 need upgrade.
[00027987][01 00][05] v1.23.3419 -> v1.23.3419
[00028016][01 01][00] v1.5.2735 -> v1.23.3419 need upgrade
[00040557][08 00][00] device not detected.
[00040589]Done.

[00040629]Firmware upgrading[2]...
[00040774][01 01] Firmware upgrade start...
[00071034][01 01] Firmware upgrade finished successfully.
[00071083][12 00] Firmware upgrade start...
[00141913][12 00] Firmware upgrade finished successfully.
[00141962][12 01] Firmware upgrade start...
[00210576][12 01] Firmware upgrade finished successfully.
[00210632][12 02] Firmware upgrade start...
[00279581][12 02] Firmware upgrade finished successfully.
[00279633][12 03] Firmware upgrade start...
[00346242][12 03] Firmware upgrade finished successfully.
[00346299][17 00] Firmware upgrade start...
[00491127][17 00] Firmware upgrade finished successfully.
[00491174][17 01] Firmware upgrade start...
[00575371][17 01] Firmware upgrade finished successfully.
[00575413][11 00] Firmware upgrade start...
[00628966][11 00] Firmware upgrade finished successfully.
[00629106][03 05] Firmware upgrade start...
[00699574][03 05] Firmware upgrade finished successfully.
[00699811][03 06] Firmware upgrade start...
[01019209][03 06] Firmware upgrade finished successfully.
[01022196][19 00] Firmware upgrade start...
[01032535][19 00] stop streaming timeout, continue upgrade.
[01177638][19 00] start streaming timeout, continue upgrade.
[01207673][19 00] Firmware upgrade finished successfully.
[01207737][04 00] Firmware upgrade start...
[01266544][04 00] Firmware upgrade finished successfully.
[01266579]Done.

[01266614]Version checking[3]...
[01266690][03 05][05] v34.2.0.9 -> v34.2.0.9
[01266770][03 06][05] v2.3.0.13 -> v2.3.0.13
[01266809][04 00][05] v1.41.0.0 -> v1.41.0.0
[01266875][09 00][00] v1.7.0.3 -> v1.7.0.3
[01266965][11 00][05] v1.7.0.0 -> v1.7.0.0
[01267039][12 00][05] v1.10.0.0 -> v1.10.0.0
[01267119][12 01][05] v1.10.0.0 -> v1.10.0.0
[01267195][12 02][05] v1.10.0.0 -> v1.10.0.0
[01267294][12 03][05] v1.10.0.0 -> v1.10.0.0
[01279841][15 00][00] device not detected.
[01279914][17 00][05] v1.1.1.7 -> v1.1.1.7
[01280034][17 01][05] v1.0.2.7 -> v1.0.2.7
[01280094][19 00][05] v1.0.8.96 -> v1.0.8.96
[01280129][01 00][05] v1.23.3419 -> v1.23.3419
[01280163][01 01][05] v1.23.3419 -> v1.23.3419
[01292700][08 00][00] device not detected.
[01292732]Packet upgrade failed at version checking.
2015-11-10
Use props
rodger
First Officer
Flight distance : 20145135 ft
  • >>>
United States
Offline

m4schler@gmail. Posted at 2015-11-10 09:55
I would grant that, but the gimbal subsystem seems to be working fine.  It's that camera and video ...

Maybe you should send it in?
2015-11-11
Use props
dobova
lvl.3
Flight distance : 664337 ft
Italy
Offline

That's very strange anyway.
Section [11 00] is the battery.
Section [08 00] is TI Davinci DSP firmware, present only in the P3P (P3X_*) firmware, becouse in the P3A (camera) it's not installed.
I can't remind what's section [15 00], but it is something related to the camera (gimbal ST32F code if I'm right).

Can you switch on the P3 ? Or is it bricked ?
2015-11-11
Use props
m4schler
New

United States
Offline

dobova Posted at 2015-11-11 09:06
That's very strange anyway.
Section [11 00] is the battery.
Section [08 00] is TI Davinci DSP firm ...

It switches on, links and responds to commands from the controller.  However, it shows 'no signal' on the DJI Go screen and there is no video.  If I take a picture or start a video it acts like it is responding.  Gimbal seems to function normally when I move the airframe around and tilt it.  This is turning into a very strange problem for a machine that has never flown and never moved off the test bench.
2015-11-11
Use props
m4schler
New

United States
Offline

rodger Posted at 2015-11-11 08:04
Maybe you should send it in?

Yes, that's what I'm thinking as well.  It's getting close to 6 months since I purchased it and certain warranty items exit coverage at that point.  I think I'll call to day and get an RMA just in case.  I called yesterday and talked to somebody essentially reading a script of things to try.  I am well beyond that point now.  I've built these things from the ground up, programmed them and integrated complex systems such as the ones that exist on the DJI.  I don't need to be read a script.  I need someone to help me troubleshoot and fix the problem or determine whether it is due to defective systems so I can get it fixed.  As it is, its no better that a Blade Nano to me.
2015-11-11
Use props
dobova
lvl.3
Flight distance : 664337 ft
Italy
Offline

m4schler@gmail. Posted at 2015-11-11 17:06
It switches on, links and responds to commands from the controller.  However, it shows 'no signal'  ...


@m4schler is right.. probably you got a partially DOA Phantom 3 becouse for sure you have a dead camera encoder for the video TX .
Have you looked the images and videos saved on the P3 SD card ?
2015-11-11
Use props
m4schler
New

United States
Offline

dobova Posted at 2015-11-11 10:49
@m4schler is right.. probably you got a partially DOA Phantom 3 becouse for sure you have a dead  ...

No, I haven't.  Frankly I didn't even think about that, instead concentrating on getting the thing updated which requires a wipe of the SD card each time.  I'll have to try that.  Thanks!
2015-11-11
Use props
rodger
First Officer
Flight distance : 20145135 ft
  • >>>
United States
Offline

m4schler@gmail. Posted at 2015-11-11 11:12
Yes, that's what I'm thinking as well.  It's getting close to 6 months since I purchased it and cer ...

I would. Winter is setting in anyway.
2015-11-12
Use props
m4schler
New

United States
Offline

Well, I called DJI and got an RMA number to send the P3P back to them. I'm disappointed that the unit failed after no flights and simple updating while sitting on the test bench.  I even tried resetting the firmware update with the MVOMV0Fw.bin file, which seemed to work but did not reset the version numbers, so the subsequent try to update with 1.1.9 failed.  Interestingly enough, on a suggestion by dobova, I tried taking pictures and videos.  Both were successful on the SD card and I saw perfect images.  But there is still no signal to the iPad Mini and subsystems 15 and 08 continue to fail.  I've done all I can.  It's time to send the unit back to DJI for repair/replacement.  I have to tell you, this makes me think twice - no three times - about buying another DJI product.  I have never received an email response to either of my posts to their support address and the lady I talked to on the phone, nice though she may have been, was completely nontechnical.  There was never even an offer to connect me with someone who could possibly help.  If some company comes along and actually truly supports their clients instead of treating them like they are doing them a favor talking to them, they'll win enormous business in this burgeoning field.  They'd win my business for sure.  DJI is spoiled and non helpful - fat and happy - until someone comes to knock them off their perch.
2015-11-14
Use props
Advanced
You need to log in before you can reply Login | Register now

Credit Rules