No Image Transmission Signal

[GrammatonxXXxCleric]

Seeing that dreaded "Device not detected" line.... Try unplugging/replugging camera power cable out/in.. (worth a try).

 

[dbryant]

That is the app revision. There are two others. (Drone needs to be on) (Controller on too for it's rev.)

AC 1.10.90, RC 1.8.0

 

[GrammatonxXXxCleric]

If no go... Call DJI for a new one.

 

[GrammatonxXXxCleric]

If you unplug camera, turn drone on. Buzzing/red lights still? then turn it off, plug camera back in. What noises/light color?

 

[GrammatonxXXxCleric]

Most likely the drone itself is ok and flyable. If the camera system is like Oso said, you need a new camera. Seven months is still in warranty. You'd get a new one.

 

[dbryant]

Will you please post your LOG_AB file. I'd like to see if it shows "device not detected" for modules 8 and 15 which could indicate that your gimbal board overheated during an extended FW update.

In case you or anyone doesnt know about these files, look on your SD card in the path below. The LOG_AB file shows 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 or if a component is bad such as a gimbal board burning out.

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 (for P3P) -or- P3S_FW_LOG_AB.txt (for P3A)

I posted it and I do see 8 and 15 not detected???

 

[Oso]

Im very new at this but I think this is what you are asking for

[00015204]========== remo-con disconnect. boot(15) ============
[00015298]Packet [C:\P3X_FW_V01.10.0090.bin] detected, card sn [0xda5db32f].
[00015388]Packet upgrade start...

[00015484]Packet checking...
[00015580]Packet vlink 01.10.0090 <-> 01.10.0090.
[00015674]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00015771]Done.

[00015860]Version checking[1]...
[00015988][03 05][00] v34.2.0.9 -> v34.2.0.9
[00016107][03 06][00] v2.4.20.28 -> v2.4.20.28
[00016208][04 00][00] v1.48.0.0 -> v1.48.0.0
[00016367][11 00][00] v1.8.0.0 -> v1.8.0.0
[00016527][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00016620][11 01][00] v1.8.0.0 -> v2.0.0.33
[00016766][12 00][00] v1.11.0.0 -> v1.11.0.0
[00016896][12 01][00] v1.11.0.0 -> v1.11.0.0
[00017038][12 02][00] v1.11.0.0 -> v1.11.0.0
[00017180][12 03][00] v1.11.0.0 -> v1.11.0.0
[00029778][15 00][00] device not detected.
[00029922][17 00][00] v1.1.1.7 -> v1.1.1.7
[00030097][17 01][00] v1.0.2.7 -> v1.0.2.7
[00030217][19 00][00] v255.255.255.254 -> v1.0.8.96
[00030311][01 00][00] v1.32.5432 -> v1.32.5432
[00030400][01 01][00] v1.32.5432 -> v1.32.5432
[00042994][08 00][00] device not detected.
[00043257][09 00][00] v3.0.0.10 -> v3.0.0.10
[00043351]Packet upgrade failed at version checking.

Yes, that's the one.
Check out this post and a few after that one for some insight from @hunch. Hunch is one of the go-to members here for camera/gimbal related issues.

 

[dbryant]

Most likely the drone itself is ok and flyable. If the camera system is like Oso said, you need a new camera. Seven months is still in warranty. You'd get a new one.

Yes I can fly it...just don't have the visual

 

[dbryant]

Yes, that's the one.
Check out this post and a few after that one for some insight from @hunch. Hunch is one of the go-to members here for camera/gimbal related issues.

Wow! Just read it!!

 

[GrammatonxXXxCleric]

So looking at that code Oso, it actually looks like the lightbridge is out, not the camera?

 

[Oso]

So looking at that code Oso, it actually looks like the lightbridge is out, not the camera?

Those codes are indicative of a bad main gimbal board (video chip bad or FW corrupted) as noted earlier. So yes, not the camera itself but the board above it.

Check out these search results. As @hunch noted, it's much too common.
I'd have to say that based on what we have seen historically, I'd guess that this is the issue.
@hunch or @Ted4797 can add more since they are the experts here, but what Hunch noted in that thread is pretty clear.

 

[dbryant]

So looking at that code Oso, it actually looks like the lightbridge is out, not the camera?

Crazy question..Will DJI hire someone to fix that's pretty close to my city / state or will I need to mail?

 

[GrammatonxXXxCleric]

They will give you a rma#. They ALWAYS have it sent in (from my experience).

 

[GrammatonxXXxCleric]

You'll prbly get a replacement very quickly. Within 1-2 weeks.

 

[dbryant]

You'll prbly get a replacement very quickly. Within 1-2 weeks.

Thanks!