Welcome to PhantomPilots.com

Sign up for a weekly email of the latest drone news & information

No signal after crash or firmware update failure.

Discussion in 'Pro/Adv Discussion' started by Amty lolo, May 27, 2016.

  1. Amty lolo

    Joined:
    May 13, 2016
    Messages:
    21
    Likes Received:
    4
    I fix drones. I faced the ( device not detected ) issue many times. If u show the hidden files, the bin log will state :



    [00441851]Firmware upgrading[5]...

    [00444803][19 00] Firmware upgrade start...
    [00486387]Done.
    [00486466]Version checking[6]...
    [00486563][03 05][00] v34.2.0.9 -> v34.2.0.8
    [00486681][03 06][00] v2.2.6.8 -> v2.1.6.18
    [00486759][04 00][00] v1.38.0.0 -> v1.36.0.0
    [00486851][09 00][00] v1.7.0.3 -> v1.7.0.3
    [00487001][11 00][00] v1.6.0.0 -> v1.6.0.0
    [00487131][12 00][00] v1.8.0.0 -> v1.8.0.0
    [00487258][08 00][00] device not detected.
    [00487366][12 02][00] v1.8.0.0 -> v1.8.0.0
    [00487492][12 03][00] v1.8.0.0 -> v1.8.0.0
    [00520097][15 00][00] device not detected.
    [00520208][17 00][00] v1.1.1.6 -> v1.1.1.2
    [00520368][17 01][05] v1.0.2.4 -> v1.0.2.4
    [00520473][19 00][00] v0.0.0.0 -> v1.0.8.59 upgrade failed.

    This log means u hav 2 ways only to solve it. One is RMA back to dji. The second way which needs luck is changing the MGCB. main gimbal circuit board. U cant buy it alone coz its a part of the gimbal. U can try ur luck with someone with a crashed drone and i my self did find 3 working boards from ppl who crashed and replaced their gimbals.
    ....................................


    The second no signal issue. The hidden log indicates the only 15 DEVICE NOT DETECTED. With some error. Like this.



    [00441851]Firmware upgrading[5]...

    [00444803][19 00] Firmware upgrade start...
    [00456309][19 00] Firmware upgrade finish failed (step = 4, err = 0xaa, idx = 0, los = 1, ng = 0, usb = 1).
    [00486387]Done.
    [00486466]Version checking[6]...
    [00486563][03 05][00] v34.2.0.9 -> v34.2.0.8
    [00486681][03 06][00] v2.2.6.8 -> v2.1.6.18
    [00486759][04 00][00] v1.38.0.0 -> v1.36.0.0
    [00486851][09 00][00] v1.7.0.3 -> v1.7.0.3
    [00487001][11 00][00] v1.6.0.0 -> v1.6.0.0
    [00487131][12 00][00] v1.8.0.0 -> v1.8.0.0
    [00487258][12 01][00] v1.8.0.0 -> v1.8.0.0
    [00487366][12 02][00] v1.8.0.0 -> v1.8.0.0
    [00487492][12 03][00] v1.8.0.0 -> v1.8.0.0
    [00520097][15 00][00] device not detected.
    [00520208][17 00][00] v1.1.1.6 -> v1.1.1.2
    [00520368][17 01][05] v1.0.2.4 -> v1.0.2.4
    [00520473][19 00][00] v0.0.0.0 -> v1.0.8.59 need upgrade.
    [00520546][01 00][00] v1.14.3090 -> v1.7.2735
    [00520622][01 01][00] v1.14.3090 -> v1.7.2735
    [00520698]Packet upgrade failed at firmware upgrade.

    This problem is easy to solve and no need for RMA. Usualy it happens after a crash. It means the u hav to change the cable that connect the gimbal with the transmitter or u should change the transmitter its self. The transmitter its self is the OFDM board exist above the IMU sensors board. Its sold alone at DJI with aprice 69$ i guess.
    I did fix more than 7 drones having these issues.
    AND DONT FORGET to upgrade firmware after changing or replacing any part of these.

    Wish that helps u.

    GOODLUCK ALL.
     
    #1 Amty lolo, May 27, 2016
    Last edited: May 27, 2016
    Ordy and Romonaga like this.
  2. alokbhargava

    Joined:
    Sep 28, 2015
    Messages:
    5,112
    Likes Received:
    1,646
    Location:
    San Francisco, CA
    Which are these log files?
     
  3. Oso

    Oso

    Joined:
    May 19, 2015
    Messages:
    2,523
    Likes Received:
    1,476
    Location:
    Sacramento CA
    They look like the log_ab files.

    In case anyone doesnt know about these files, look on your SD card in the path below. The log_ab file show the FW version of the assorted modules / components of your Phantom and if they did or did not need a change during a FW update. P3A and P3P have a couple of different components, so you may see "device not detected" for that reason.

    Note that the log_ab file is a different txt file than you look at for the general overall "success" indication. Once you've done an update, look on your SD card in the following path....

    Some of the folders may be hidden:
    MISC/LOG/
    Then find your log_ab file - P3X_FW_LOG_AB.txt (P3P) or P3S_FW_LOG_AB.txt (P3A).
     
    #3 Oso, May 27, 2016
    Last edited: May 27, 2016
  4. Ordy

    Joined:
    Jul 24, 2016
    Messages:
    2
    Likes Received:
    1

    Is it possible to replace the MGCB of a P3 Pro with one from a P3 Adv? (And will the camera work just the same with 4k, etc?)

    Thanks for sharing this btw. I'm getting the first issue you mentioned with devices 08 and 15 missing, and it's tough to find any documentation for repair other than just sending it in to DJI.
     
  5. Amty lolo

    Joined:
    May 13, 2016
    Messages:
    21
    Likes Received:
    4
    No my freind u can't just change the p3p MGAC board with a p3a one. Coz the p3a board is missing a chip that's responsible for the 4k. U should search for a crashed p3p gimbal and try to purchase the MGCB. i tried many times with the dji customers service stuff but they r useless regarding this issue. Their conclusion was there is a bad manufacturing glitch in the p3p MGCB due to this 4k chip. And they offer no promises about any future firmware that fix this issue. The only way they can help is replacing ur whole gimbal through RMA.

    Goodluck. Wish ur bird back in the sky soon.

    Sent from my SM-N920C using PhantomPilots mobile app
     
    mikesmiley and Ordy like this.
  6. Ordy

    Joined:
    Jul 24, 2016
    Messages:
    2
    Likes Received:
    1
    Aw man, ok got it. Thanks again @Amty lolo ! Appreciate the help.
     
    Amty lolo likes this.
  7. Hartmut Eichenberg

    Joined:
    Sep 22, 2016
    Messages:
    1
    Likes Received:
    0
    Great info, thanks. But what if you have the no signal/can't link rc issue and all devices are detected in the log file? Just got through replacing some suspect cables and came across this post, but this is what I got after the firmware failed to take:

    [00424554]Firmware upgrading[5]...

    [00427676][19 00] Firmware upgrade start...

    [00470265][19 00] Firmware upgrade finish failed (step = 2, err = 0xaa).

    [00500344]Done.



    [00500420]Version checking[6]...

    [00500522][03 05][00] v34.2.0.9 -> v34.2.0.9

    [00500622][03 06][00] v2.4.20.18 -> v2.4.20.18

    [00500703][04 00][00] v1.44.0.0 -> v1.44.0.0

    [00500846][11 00][05] v1.8.0.0 -> v1.8.0.0

    [00501002][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.

    [00501079][11 01][00] v1.8.0.0 -> v2.0.0.33

    [00501190][12 00][00] v1.10.0.0 -> v1.10.0.0

    [00501316][12 01][00] v1.10.0.0 -> v1.10.0.0

    [00501475][12 02][00] v1.10.0.0 -> v1.10.0.0

    [00501602][12 03][00] v1.10.0.0 -> v1.10.0.0

    [00501771][15 00][00] v1.1.2.0 -> v1.1.2.0

    [00501890][17 00][00] v1.1.1.7 -> v1.1.1.7

    [00502051][17 01][00] v1.0.2.7 -> v1.0.2.7

    [00502271][19 00][00] v0.0.0.0 -> v1.0.8.96 need upgrade.

    [00502354][01 00][00] v1.30.5036 -> v1.30.5036

    [00502435][01 01][00] v1.30.5036 -> v1.30.5036

    [00502533][08 00][00] v0.13.0.7 -> v0.13.0.7

    [00502631][09 00][00] v3.0.0.10 -> v3.0.0.10

    [00502706]Packet upgrade failed at firmware upgrade.
     
  8. flyNfrank

    Joined:
    Feb 1, 2014
    Messages:
    4,212
    Likes Received:
    910
    Location:
    Indy, USA
    1fwData.jpg

    Does anyone know the Names of the Modules listed in the Blue Column?

    I'm guessing:
    03 06 - Battery Firmware
    11 00 - Aircraft Firmware
    12 00 - ESC
    12 01 - ESC
    12 02 - ESC
    12 03 - ESC

    If those guesses are wrong, let me know. Anyone know what the others might be?
     
  9. Oso

    Oso

    Joined:
    May 19, 2015
    Messages:
    2,523
    Likes Received:
    1,476
    Location:
    Sacramento CA
    Hi Frank. Below is what we have been noting here on the forum since about October/November of 2015. Most of it was mapped by @Dome if I recall correctly.

    FW module decoder snippet.JPG
     
    Argonaise likes this.