No live feed after gimbal repair, everything else works

[Faze82]

I replaced the yaw motor last week and put the gimbal back together. Now when I start the drone, I do not see any image on the screen of my phone. Gimbal/camer seems to work, there is no error message. I tried to take pictures and it works, they are stored on the SD card. But the video feed is still blank

 

[Faze82]

anyone? :/

 

[quaddamage]

Pro or Adv?
Why the flat foam wire was broken?
Which RC version do you have?

Put a very old FW on SD-card. I mean, OLD one - so that your drone WILL NOT start update. Then check the last entry in update log inside a hidden folder.

 

[Faze82]

It's a PRO. I am not sure what you mean by flat foam wire.

So you mean basically downgrade the firmware? I did not update it at all after the motor replacement though

 

[quaddamage]

I am not sure what you mean by flat foam wire.

I mus have been tired when answering. You only mentioned replacing a motor, not the cable. And I meant flat flex cable, no foam wires in the drone .

It's a PRO.

Then you likely have the m0800 and m1500 problem, update logs will tell.

So you mean basically downgrade the firmware?

No. Placing old firmware will not start any upgrade, that's the point. What you need is the latest update log.

I did not update it at all after the motor replacement

Good. It is best to fix one problem at a time. Do not upgrade nor downgrade.

 

[Faze82]

I did it, the only thing in the logs was:


========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3X_FW_V01.02.0006.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

 

[quaddamage]

This is a simplified log. The correct log is in a hidden folder.

 

[Faze82]

oh, right

[00016991]========== remo-con disconnect. boot(15) ============
[00017126]Firmware [C:\DM368Fw.bin] detected, card sn [0x70ce2a83].
[00017160][08 00] Firmware upgrade start...
[00521043][08 00] Firmware upgrade finished successfully.
[00521083]Done.

[00014593]========== remo-con disconnect. boot(15) ============
[00014628]Packet [C:\P3X_FW_V01.02.0006.bin] detected, card sn [0x5dfb5574].
[00014666]Packet upgrade start...

[00014701]Packet checking...
[00014735]Packet vlink 01.01.0000 <-> 01.01.0000.
[00014806]Done.

[00014844]Version checking[1]...
[00014930][03 05][00] v34.2.0.9 -> v34.2.0.9
[00015009][03 06][00] v2.4.20.28 -> v2.2.6.8
[00015053][04 00][00] v1.40.0.0 -> v1.38.0.0
[00015105][09 00][00] v3.0.0.10 -> v1.7.0.3
[00015230][11 00][00] v1.8.0.0 -> v1.6.0.0
[00015318][12 00][00] v1.11.0.0 -> v1.8.0.0
[00015417][12 01][00] v1.11.0.0 -> v1.8.0.0
[00015517][12 02][00] v1.11.0.0 -> v1.8.0.0
[00015617][12 03][00] v1.11.0.0 -> v1.8.0.0
[00028155][15 00][00] device not detected.
[00028239][17 00][00] v1.1.1.7 -> v1.1.1.6
[00028379][17 01][00] v1.0.2.7 -> v1.0.2.5
[00028425][19 00][00] v1.0.8.96 -> v1.0.8.96
[00028464][01 00][00] v1.23.3419 -> v1.15.3056
[00028498][01 01][00] v1.23.3419 -> v1.15.3056
[00041032][08 00][00] device not detected.
[00041069]Packet upgrade failed at version checking.

 

[quaddamage]

This is a classical m0800+m1500 problem. You will find many threads on the forum about this.
Some people claim that DJI repairs these for free.

This is caused by your drone overheating during the update. Only the gimbal top board is damaged. Search the forum for many discussions about it.

If you want to fix it for yourself, you may try reflashing the NAND chip. Instructions are here:
Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub

And here is my story of replacing the chip on a board when it got damaged and couldn't be reflashed:
Fixing flash in DM365 chip within Ph3 Pro gimbal

Here's a download of more step-by-step manual for flashing bootloader, by SunsetCatcher:
No image transmission signal - P3P

 

[Faze82]

yeah no way I'm able to fix that it just irritates me because it was working properly, I might have shorten the board while disassembling the gimbal to replace the motor

 

[quaddamage]

yeI might have shorten the board while disassembling the gimbal to replace the motor

I doubt that. As I said, this is a design flaw. If the drone is turned on for ~30 minutes in a warm room, without flying, then it overheats and gets this issue.