Phantom 3 Pro - Intermittent no video feed problem

[edmundC]

I've read many threads on this forum about no video feed on mobile device (including posts by a few experts like Suncatcher, Quaddamage, Oso etc..) I'm not sure if I can follow their advices to solve my problem... I recently replaced the gimbal top board and a new flexi flat cable as a result of a crash. My P3P worked perfectly after the part replacements until yesterday when i tried to do gimbal calibration suddenly I lost my video feed on my mobile device. What's interesting is when i left the AC power off for few minutes and power on again I got the video feed back. The same thing happened when I flew my bird this morning the video feed worked perfectly during the first flight i.e. I could record perfect video, took photos and control gimbal yaw and pitch but when I stopped the AC and changed a second battery, upon power up the AC I lost the video feed on my mobile device but I still got strong RC and HD signals, there was not any video error msg on the screen just that the screen was black and the video setting menu bar on the left side of the Go app was faded (video setting buttons were unselectable at this point) I tried to powered off and on the AC, the RC and restarted the Go app many times but it made no different. At this point I noticed whenever I powered off the battery it took 10 seconds for the battery LEDs to go off. (Under normal condition it takes less than 1 second) I also noticed that there was an extra "Gimbal Pan SmoothTrack" option appeared in the gimbal setting (this option never appear under normal condition when the video feed is fine). So I decided to bring the AC back to my car and cool it down in front of the air conditioner and when I powered up this time the video feed came back! So my question is this a hardware or a firmware problem? Will reflashing my gimbal top board or force re install firmware solve my problem? Note that my video feed problem is INTERMITTENT meaning sometimes I get the video feed completely fine and sometimes I don't. On the other hand, there is no AB Log file in my P3P SD card, would appreciate if anyone can share an old enough firmware so that I can use it to copy a new log file from my AC. Your suggestions and advice are very much appreciated

 

[edmundC]

 

[Fly Dawg]

would appreciate if anyone can share an old enough firmware so that I can use it to copy a new log file from my AC. Your suggestions and advice are very much appreciated

Scroll to the bottom of this page. All the P3P firmware versions are listed and downloadable there.

P3P Firmware

 

[Oso]

I recently replaced the gimbal top board and a new flexi flat cable as a result of a crash.

Where did you get the new gimbal board? Do you know what firmware it had on it when you installed the new board? Did you reflash it to match what you had prior when you installed it? What did you have prior?

The screen shot you posted shows AC as 1.3.2+ but your RC as 1.9.2. Are you aware that AC FW 1.8 and RC FW 1.6 were released together with an encryption change. If you have one (or later), you must have the other (or later) or you will have issues. DJI also noted this in the release notes, but even so we have seen several people here who were not aware and inadvertently created an encryption mismatch.

Is it safe to assume that since your RC is 1.9.2 that you previously had 1.8 or higher on your AC and that your assorted batteries had the appropriate FW as well?

At this point I noticed whenever I powered off the battery it took 10 seconds for the battery LEDs to go off. (Under normal condition it takes less than 1 second)

Per @quaddamage - "The battery is "intelligent" - when turning it off, it sends message "save settings, power off is imminent" to FC and camera, and waits for acknowledgement. Just to be sure, it sends that message 3 times. If it receives back message "affirmative, settings saved" then it turn off immediately. If no such message arrives, it waits for like 10 seconds, then turns off anyway."

So my question is this a hardware or a firmware problem? Will reflashing my gimbal top board or force re install firmware solve my problem? Note that my video feed problem is INTERMITTENT meaning sometimes I get the video feed completely fine and sometimes I don't. On the other hand, there is no AB Log file in my P3P SD card, would appreciate if anyone can share an old enough firmware so that I can use it to copy a new log file from my AC. Your suggestions and advice are very much appreciated

Its hard to guess if you are having a HW or a FW problem. Since you swapped out significant HW components, some which may have had mismatching FW, you could have both a FW and a HW problem.

If it were mine, I would have reflashed FW so that the new board FW matched what I had prior. If you did not do that, perhaps consider starting there. Always remember of course to have some sort of fan blowing on your AC. It may be tricky if the new board had a later version FW and/or you don't know what it had prior to installing it or what you had prior to installing it. Also, try to get the AC to write a LOG_AB file to the card.

DJI has historically maintained an archive of FW versions on their site even though they don't always show links to them. For archived FW versions directly from DJI, follow the links in this post.

 

[edmundC]

Where did you get the new gimbal board? Do you know what firmware it had on it when you installed the new board? Did you reflash it to match what you had prior when you installed it? What did you have prior?

I bought the used gimbal top board from a China seller. I have no idea which firmware it had on it (i didn't think about FW as I mainly worried about replacing the damaged hardware . Reflash it? I suppose you mean updating the AC, RC & batteries to latest FW. Anyway I managed to get the Log AB file from the AC: -

[00012236][01 00] Firmware upgrade finished successfully.
[00012345]Done.

[00012380]Packet [C:\P3X_FW_V01.03.0020.bin] resumed, card sn [0x90ce5c96].
[00012418]Packet vlink 01.03.0020 <-> 01.01.0009.
[00012484]Version checking[2]...
[00012548][03 05][00] v34.2.0.8 -> v34.2.0.9 need upgrade.
[00012607][03 06][00] v2.1.6.18 -> v2.2.6.19 need upgrade.
[00012651][04 00][00] v1.36.0.0 -> v1.40.0.0 need upgrade.
[00012700][09 00][00] v1.7.0.3 -> v1.7.0.3
[00012807][11 00][00] v1.6.1.0 -> v1.7.0.0 need upgrade.
[00012875][12 00][00] v1.8.0.0 -> v1.8.0.0
[00012955][12 01][00] v1.8.0.0 -> v1.8.0.0
[00013021][12 02][00] v1.8.0.0 -> v1.8.0.0
[00013095][12 03][00] v1.8.0.0 -> v1.8.0.0
[00013212][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013316][17 00][00] v1.1.1.2 -> v1.1.1.7 need upgrade.
[00013436][17 01][00] v1.0.2.4 -> v1.0.2.7 need upgrade.
[00013481][19 00][00] v1.0.8.96 -> v1.0.8.96
[00013512][01 00][05] v1.23.3419 -> v1.23.3419
[00013544][01 01][00] v1.6.2736 -> v1.23.3419 need upgrade
[00013582][08 00][00] v0.11.0.4 -> v0.12.0.4 need upgrade.
[00013613]Done.

I think you are right, there seems like FW mismatches as there is a lot of modules need an upgrade. By looking at this, what would you recommend me to do? Appreciate your help very much

 

[edmundC]

Btw I haven't done any FW update since I replaced the Gimbal Top Board. But I used the oldest FW as a way to retrieve the Log AB file from my AC. The result: -

Result: Success.

========== 2015.08.19 21:12:40 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.08.20 21:06:19 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.08.22 22:09:25 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.08.25 17:58:47 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.08.27 23:46:31 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.08.28 18:37:16 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.08.30 20:22:05 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.09.01 23:20:23 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.09.02 22:00:24 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.09.02 22:16:15 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.09.02 22:16:56 =====================
Packet: P3X_FW_V01.03.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2018.11.14 18:36:38 =====================
Packet: P3X_FW_V01.10.0090.bin
Upgrading ...

========== 2018.11.14 18:57:49 =====================
Packet: P3X_FW_V01.10.0090.bin
Upgrading ...

========== 2018.11.14 19:09:10 =====================
Packet: P3X_FW_V01.10.0090.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2018.11.14 19:11:17 =====================
Packet: P3X_FW_V01.10.0090.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.01.0008.bin
Result: Corrupted.
Firmware bin file is corrupted, download it again from the DJI offical website.

 

[edmundC]

Where did you get the new gimbal board? Do you know what firmware it had on it when you installed the new board? Did you reflash it to match what you had prior when you installed it? What did you have prior?

The screen shot you posted shows AC as 1.3.2+ but your RC as 1.9.2. Are you aware that AC FW 1.8 and RC FW 1.6 were released together with an encryption change. If you have one (or later), you must have the other (or later) or you will have issues. DJI also noted this in the release notes, but even so we have seen several people here who were not aware and inadvertently created an encryption mismatch.

Is it safe to assume that since your RC is 1.9.2 that you previously had 1.8 or higher on your AC and that your assorted batteries had the appropriate FW as well?



Per @quaddamage - "The battery is "intelligent" - when turning it off, it sends message "save settings, power off is imminent" to FC and camera, and waits for acknowledgement. Just to be sure, it sends that message 3 times. If it receives back message "affirmative, settings saved" then it turn off immediately. If no such message arrives, it waits for like 10 seconds, then turns off anyway."



Its hard to guess if you are having a HW or a FW problem. Since you swapped out significant HW components, some which may have had mismatching FW, you could have both a FW and a HW problem.

If it were mine, I would have reflashed FW so that the new board FW matched what I had prior. If you did not do that, perhaps consider starting there. Always remember of course to have some sort of fan blowing on your AC. It may be tricky if the new board had a later version FW and/or you don't know what it had prior to installing it or what you had prior to installing it. Also, try to get the AC to write a LOG_AB file to the card.

DJI has historically maintained an archive of FW versions on their site even though they don't always show links to them. For archived FW versions directly from DJI, follow the links in this post.

You said reflashing do you mean updating to the latest FW or do i need to do some soldering on the gimbal board followed Suncatcher's method?

 

[edmundC]

Here's the Log AB file when video feed was fine

 

[edmundC]

Here are the Log AB file when the video feed was NOT ok

 

[edmundC]

I don't understand what do all these mean, please help, thanks

 

[3rdof5]

I don't understand what do all these mean, please help, thanks

I dont see the typical 8/15 device not detected, which is what you would have if the FW on the DaVinci module was corrupt. All looks normal in those files to me.

 

[edmundC]

I dont see the typical 8/15 device not detected, which is what you would have if the FW on the DaVinci module was corrupt. All looks normal in those files to me.

What do those "need upgrade" mean? Do they mean i need to update the FW for those modules?

 

[Oso]

Do they mean i need to update the FW for those modules?

Yes, that's what it means. If you follow the log_ab link in my post #4 above, you'll see more info on that and the individual modules.

 

[Oso]

If it were mine, I would have reflashed FW so that the new board FW matched what I had prior.

You said reflashing do you mean updating to the latest FW or do i need to do some soldering on the gimbal board followed Suncatcher's method?

When I said "reflashed the FW," I was referring to the FW and nothing about soldering. There are many different modules on the AC and the batteries and they each have their own FW versions which are included in the single FW bin file which is used to update. Not all modules are updated every time.

As I noted, I was speculating that the FW on your new gimbal board was a different version than what you had before. What we don't know is if it was older or newer than what you had before so it's harder to give good advice.

Your files seem to show that you were perhaps at 1.10 on your AC before you made changes. If you know that to be true, you can try to reflash 1.10. If you don't know what your had on your AC before, perhaps think about just going to the latest 1.11.20 but make sure you understand the changes related to AC FW 1.11.20. It was released in July 2017 and introduced forced flight restrictions similar to beginner mode if you haven't "registered" your app with DJI. Click here for more info.

Good luck sir.

 

[edmundC]

Oso, I powered up my AC this morning and guess what, the AC version shows 1.11.20. Remembered that I took a snapshot of the AC version it was 1.3.20+ I had done absolutely nothing to it somehow it 'changed' to the latest AC version?? I'm confused [emoji53] Should I try to reflash or leave it alone?

When I said "reflashed the FW," I was referring to the FW and nothing about soldering. There are many different modules on the AC and the batteries and they each have their own FW versions which are included in the single FW bin file which is used to update. Not all modules are updated every time.

As I noted, I was speculating that the FW on your new gimbal board was a different version than what you had before. What we don't know is if it was older or newer than what you had before so it's harder to give good advice.

Your files seem to show that you were perhaps at 1.10 on your AC before you made changes. If you know that to be true, you can try to reflash 1.10. If you don't know what your had on your AC before, perhaps think about just going to the latest 1.11.20 but make sure you understand the changes related to AC FW 1.11.20. It was released in July 2017 and introduced forced flight restrictions similar to beginner mode if you haven't "registered" your app with DJI. Click here for more info.

Good luck sir.

 

[edmundC]

I retrieved the Log AB file again after the AC version miraclely changed to 1.11.20. I don't see any discrepancy compared with the Log AB when the AC version was 1.3.20+ The file still showing the same thing. Should Igo ahead reflash/force reinstall FW1.11.20 or leave it alone?