This is really odd.
I updated my Inspire 1 Pro firmware which failed. I had the dreaded 0800 and 1500 device not detected errors. I cannot update the X5 at all any more.
So, I stuck my X3 on the craft and did the update for that. All fine and I can fly and view the camera output. Stuck the X5 back on and no joy.
With the X5 I can see the histogram changing as things pass the camera. I can take photos and videos. I can move the gimbal. I can do everything but update the firmware or see the live picture.
Stuff I've tried:

Format SD in camera
Clean contacts
Loosen connector screws slightly
Unlink and re-link controller

I got on to DJI who say there is a fault with my X5. I find this hard to believe seeing as it was working fine before the update.
They want me to send it back for repairs but this is going to cost me significantly and I don't see why I should have to pay for something that was fine before the Go app told me to update the firmware.

Any help appreceiated.

Error:

[00007230][04 00][00] v1.31.1.67 -> v1.31.1.67
[00019801][08 00][00] device not detected.
[00019853][01 00][00] v1.29.5379 -> v1.29.5379
[00019913][01 01][00] v1.29.5379 -> v1.29.5379
[00019983][01 04][00] v0.5.5085 -> v0.5.5085
[00022581][03 05][00] v34.1.0.5 -> v34.1.0.5
[00022662][03 06][00] v2.4.20.50 -> v2.4.20.50
[00022742][05 00][00] v3.0.6.2 -> v3.0.6.2
[00022826][09 00][00] v5.0.0.0 -> v5.0.0.0
[00022921][11 00][00] v3.9.0.0 -> v3.9.0.0
[00023041][12 00][00] v1.11.0.0 -> v1.11.0.0
[00023141][12 01][00] v1.11.0.0 -> v1.11.0.0
[00023261][12 02][00] v1.11.0.0 -> v1.11.0.0
[00023361][12 03][00] v1.11.0.0 -> v1.11.0.0
[00035918][15 00][00] device not detected.
[00038502][17 00][00] v1.1.0.8 -> v1.1.0.8
[00038642][17 01][00] v2.0.1.6 -> v2.0.1.6
[00038706][19 00][00] v1.0.8.96 -> v1.0.8.96
[00040766]Packet upgrade failed at version checking.

Sorry for the trouble caused, cleaning the contact is right, the cable can also be re-inserted.
Then leave the aircraft alone for 30 minutes and update again. If the 0800 and 1500 still can not be detected, the aircraft and the camera all need to be sent in for evaluation.

Did you happen to have the RC transmitter on during the update of the  aircraft ?  OR  turn on the RC with the  FW  still on the SD card inside the camera .

This can cause it , not every time but I have seen enough to notice a correlation .

donnie

**** More than likely need to go in for repair , I know it sucks and am sorry this happened to you , I agree updating should NOT cause this problem but It does sometimes .

DJI Mindy Posted at 2017-8-2 22:41
Sorry for the trouble caused, cleaning the contact is right, the cable can also be re-inserted.[view_image]
Then leave the aircraft alone for 30 minutes and update again. If the 0800 and 1500 still can not be detected, the aircraft and the camera all need to be sent in for evaluation.

     Miss Mindy , I have seen significant amount of the "Device Not Detected" on lines 0800 ( the encoder ) and 1500 ( the USB in the aircraft )  after members simply try to do an update to there systems  .

The only correlation I have ever seen is if members leave the RC transmitter on during Updates OR if they leave the Update FW  on the SD card and then turn on the RC transmitter  ( essentialy doing the same thing )

My theory makes sense as the RC may be trying to communicate with the AC as the Systems are BOTH on and it somehow corrupts or damages the encoder ( in most cases )

My question is can the engineers find a way to prevent this from happening OR can you make a release  of Information more boldly stating that the cameras encoder  module can be damaged If the RC is left on  while updating OR  with updates on the SD card .

I cannot definitively say that leaving the RC on during updating or having the RC on with the update still on the aircraft causes this , BUT I have seen this many times. ( I even wrote a post on how to diagnose if you have the Issue viewing the hidden file )

Something MUST be happening to cause the  dreaded error which is an expensive fix in some cases.  There must be a cause .  Meanwhile I continue to warn of not having the RC during the update process and removing the update immediately when finished .

I am not trying to cause trouble , just trying to solve what seems like a common problem among members who are simply complying with DJI systems request to update .  

donnie

I tend to leave the FW on the SD card even after the updates. I didn't know this would cause a problem. I've not seen it mentioned anywhere in the FW update documentation that I shouldn't do this.
I've raised a ticket for the X5 as the Inspire is fine (I can fly fine with the X3 and everything else works).

What's concerning me is that I'm now going to be out of pocket to the tune of whatever DJI decide to charge me for the repair. I should have just ignore the warnings about out of date firmware. I wish I had now. I will not be updating any of my DJI gear again that's for sure.

I have three machines grounded for over a month now with the same exact problem with no solutions. The boards are failing because they cannot effectively cool properly and after xx hrs of operation they all fail.

I never upgrade a machine as long as its flying properly, all three machines I lost had original firmware over a year old.  All three machines lost video in the period of a day. The odds of this happening from thermal failure is a million to one, its almost impossible!  

Here's my thread:

https://forum.dji.com/thread-102137-2-1.html

The thing is, I can't be an age thing. I've got less than 2 hours flight time on the X5. I've been unable to fly for quite some time due to ill health.
I just think the FW has screwed up the X5. I'm really rather annoyed about this. It seems to be a very common issue across Inspires, P3s, etc. and to expect us to pay for repairs is really poor from DJI. I just wish they had a decent competitor because I could take my business elsewhere. Money talks, and when it walks businesses take notice.

As a test I stuck the X5 on my Osmo. Doesn't work there either. I tried to do a FW update via the Osmo and it fails in the same way. My X3 works on both the Osmo and the Inspire. This tells me it's definately the X5 that has the issue.

Donnie * Posted at 2017-8-3 05:10
Miss Mindy , I have seen significant amount of the "Device Not Detected" on lines 0800 ( the encoder ) and 1500 ( the USB in the aircraft )  after members simply try to do an update to there systems  .

The only correlation I have ever seen is if members leave the RC transmitter on during Updates OR if they leave the Update FW  on the SD card and then turn on the RC transmitter  ( essentialy doing the same thing )

Donnie, I understand, really appreciate what you have done in Forum.
But this theory need to be confirmed by our engineers, actually we suggest customers to update the aircraft with the RC turning off. Hope customers will do this.

fansde0e8de5 Posted at 2017-8-3 22:33
As a test I stuck the X5 on my Osmo. Doesn't work there either. I tried to do a FW update via the Osmo and it fails in the same way. My X3 works on both the Osmo and the Inspire. This tells me it's definately the X5 that has the issue.

We are sorry for the trouble that has been caused, please send in the X5 as soon as possible. Local repair team will take good care of it and get it addressed for you.

fansde0e8de5 Posted at 2017-8-3 10:54
I tend to leave the FW on the SD card even after the updates. I didn't know this would cause a problem. I've not seen it mentioned anywhere in the FW update documentation that I shouldn't do this.
I've raised a ticket for the X5 as the Inspire is fine (I can fly fine with the X3 and everything else works).

Did you happen to have the RC transmitter on during the update process of the aircraft  ?  

Please let me know as I cam collecting data.

You can shoot me a Personal Message or email  if you wish  .

donaldjames1990@gmail.com

donnie
*** The documentation does say to NOT have the RC on during the update process, there must be a reason for that .  If you think about it ( after you complete the update ) , if the SD card on the AC has FW on it and you turn on the RC during  the start up process the system is doing the same thing as it msut go through the Initial FW update process if ANY FW is on it.....do you understand what I mean ..... ( I am jsut trying to figure out why this is happening to some and not all  during the update process and a common denominator I have found is RC on with Fw on the SD card )

DJI Mindy Posted at 2017-8-4 02:02
Donnie, I understand, really appreciate what you have done in Forum.
But this theory need to be confirmed by our engineers, actually we suggest customers to update the aircraft with the RC turning off. Hope customers will do this.

If you would ask them to look into it that would be great .

Just trying to find a cause  of this very common problem . ( find a way to prevent it )  And why  it happens to some members and not all, there must be a cause .

I think the RC being on has something to do with it for sure

donnie

Pretty sure I didn't have the TX on during the update process. I could be mistaken though.
The procedure I follow always when updating the Inspire is as follows:

Grab Inspire FW (for X3 model)
Format SD card in Inspire
Stick SD card in PC and copy FW file over
Stick SD card back in X3 and power on
Let craft update
Shut down craft and remove X3
Grab Inspire Pro FW
Stick SD card in PC and copy FW across
Attach X5 and power on
Let craft update
Power off craft
Power on Tx and iPad and update them online
Swap batteries and let them update in Inspire.

Now, the Tx would probably have been on during the battery update process.

Well, we have a result. DJI will be repairing my X5 FoC!
Thanks DJI and all those who provided input.

fansde0e8de5 Posted at 2017-8-15 06:45
Well, we have a result. DJI will be repairing my X5 FoC!
Thanks DJI and all those who provided input.

That's great, hope you will get it back soon, please keep me updated if you need any assistance in repair process.