P3P, double beep, no camera view/control

Colombo973 · Dec 11, 2018

Hi everybody,

I'm stuck with a P3P and i need some help please.
Aircraft is a P3A with a P3P camera.
At start, aircraft and gimbal power on, and front led on gimbal stay green, but it always emit a mild double beep (DD-DD-DD) that never stop.
RC is linked to aircraft correctly. I can access to DJIGO, but no camera view or parameter avalaible (no gimbal tilt control too). Telemetry is avalaible and i can launch take off procedure.
As DJIGo ask me to make aircraft firmware update, i've spent several hours trying to update it without success. Always failed with lot of "device not connected" in the txt log.
I would like to know if there is a way to know if it is an hardware issue or a firmware issue ?
I've bought the quad as is and i don't know his history.
Help will be greatly apprecied !

3rdof5 · Dec 11, 2018

I wish I could help, the beeping sounds as if it's still trying to do a FW update. I know the P3P camera can be used on the P3A but I've no idea which FW must be used once you've swapped cameras (advanced or pro FW). There are members here who do know that and hopefully one of them will help. All i can suggest in the meantime is when you are trying to update the FW, have a small fan blowing on the camera and gimbal as they are very sensitive to overheating.

Colombo973 · Dec 11, 2018

Yes, i always try to update with a fan closed to the quad.

Here is what the hidden log give :

[00012876]Delete history success.

[00013139]========== remo-con disconnect. boot(15) ============
[00013217]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x03c6ebb2].
[00013289]Packet upgrade start...

[00013374]Packet checking...
[00013448]Packet vlink 01.11.0020 <-> 01.11.0020.
[00013531]Record vlink 01.10.0090 <-> 01.10.0090 (flow = 0).
[00013603]Done.

[00013680]Version checking[1]...
[00026254][03 06][00] device not detected.
[00038828][03 05][00] device not detected.
[00038918][04 00][00] v1.48.0.0 -> v1.48.0.0
[00051564][11 00][00] device not detected.
[00064169][11 01][00] device not detected.
[00076748][12 00][00] device not detected.
[00089319][12 01][00] device not detected.
[00101892][12 02][00] device not detected.
[00114470][12 03][00] device not detected.
[00117603][15 00][00] device not detected.
[00130176][17 00][00] device not detected.
[00142750][17 01][00] device not detected.
[00155329][19 00][00] device not detected.
[00155398][01 00][00] v1.32.5432 -> v1.32.5432
[00155494][01 01][00] v1.32.5432 -> v1.32.5432
[00158085][08 00][00] v0.13.0.7 -> v0.13.0.7
[00170666][09 00][00] device not detected.
[00170739]Packet upgrade failed at version checking.

I think this is not normal to have a lot of "device not detected" lines.

Beeping is exactly like this one :

3rdof5 · Dec 11, 2018

Ok you are using the P3P FW and not the P3A. I don't know if that's the problem or not. My guess is, because it's actually an advanced, you will need to use the P3A FW but I could be wrong. Are you sure it's a P3A? Sure looks like a pro but the decals could have been changed.

Colombo973 · Dec 11, 2018

P3X_FW_V01.11.0020.bin is not supposed to be the same firmware for both P3P and P3A ?

3rdof5 · Dec 11, 2018

Colombo973 said:
P3X_FW_V01.11.0020.bin is not supposed to be the same firmware for both P3P and P3A ?

No they are different. Here's the link for the advanced FW:
Phantom 3 Advanced - Specs, FAQ, Tutorials, Downloads and DJI GO - DJI

3rdof5 · Dec 11, 2018

The advanced FW starts with P3A (not X)

Colombo973 · Dec 11, 2018

Ok, but once you put a p3p camera on a p3a aircraft, i should have to use a p3p firmware ? i've heard that p3a and p3p aircraft are the same, only gimbal/camera differs and defines the model. Is this statement right ?

3rdof5 · Dec 11, 2018

Colombo973 said:
Ok, but once you put a p3p camera on a p3a aircraft, i should have to use a p3p firmware ? i've heard that p3a and p3p aircraft are the same, only gimbal/camera differs and defines the model. Is this statement right ?

I don't know.

3rdof5 · Dec 11, 2018

When u connect to the AC in dji go what version of phantom does it bring up on the connect to camera screen? Advanced or Pro?

Colombo973 · Dec 11, 2018

3rdof5 said:
When u connect to the AC in dji go what version of phantom does it bring up on the connect to camera screen? Advanced or Pro?

Pro.
I'm almost convinced that the "device not detected" lines are due to several hardware issues on the gimbal mainboard that is very sensitive to overheating. But if this mainboard is defective, why led status is solid green ? I need to be 100% sure of that, i don't want to spend a lot of money for just a firmware issue.

3rdof5 · Dec 11, 2018

Colombo973 said:
Pro.
I'm almost convinced that the "device not detected" lines are due to several hardware issues on the gimbal mainboard that is very sensitive to overheating. But if this mainboard is defective, why led status is solid green ? I need to be 100% sure of that, i don't want to spend a lot of money for just a firmware issue.

A green led status doesnt necessarily mean the board is working properly, it just means there's an sd card in and the camera is ready. Can u post a screenshot of the device not connected message? Also what does it say if you manually scroll to the advanced?

Colombo973 · Dec 11, 2018

"device not connected" lines are in the hidden txt log, i have no message in DJIGO, only aircraft status indicating the need of firmware update.
I'll try to scroll to the advanced.
One other thing, i've noticed one blinking red led inside the OFDM module (link led is still green on the side), close to the gimbal cable connector, is it normal ?

quaddamage · Dec 11, 2018

Colombo973 said:
Yes, i always try to update with a fan closed to the quad.

Here is what the hidden log give :

[00012876]Delete history success.

[00013139]========== remo-con disconnect. boot(15) ============
[00013217]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x03c6ebb2].
[00013289]Packet upgrade start...

[00013374]Packet checking...
[00013448]Packet vlink 01.11.0020 <-> 01.11.0020.
[00013531]Record vlink 01.10.0090 <-> 01.10.0090 (flow = 0).
[00013603]Done.

[00013680]Version checking[1]...
[00026254][03 06][00] device not detected.
[00038828][03 05][00] device not detected.
[00038918][04 00][00] v1.48.0.0 -> v1.48.0.0
[00051564][11 00][00] device not detected.
[00064169][11 01][00] device not detected.
[00076748][12 00][00] device not detected.
[00089319][12 01][00] device not detected.
[00101892][12 02][00] device not detected.
[00114470][12 03][00] device not detected.
[00117603][15 00][00] device not detected.
[00130176][17 00][00] device not detected.
[00142750][17 01][00] device not detected.
[00155329][19 00][00] device not detected.
[00155398][01 00][00] v1.32.5432 -> v1.32.5432
[00155494][01 01][00] v1.32.5432 -> v1.32.5432
[00158085][08 00][00] v0.13.0.7 -> v0.13.0.7
[00170666][09 00][00] device not detected.
[00170739]Packet upgrade failed at version checking.

I think this is not normal to have a lot of "device not detected" lines.

The Ambarella can only access itself (m0100, m0101), gimbal (m0400) and DaVinci (m0800). All these chips are placed on gimbal top board.

So the conclusion is that your gimbal top board is not connected to OFDM board.

Start by testing continuity of each wire in the ribbon cable with multimeter (test with plugs attached).

If it's not the ribbon cable or plugs, then either gimbal top board is damaged at output, or OFDM board is damaged at input.

Colombo973 · Dec 11, 2018

quaddamage said:
The Ambarella can only access itself (m0100, m0101), gimbal (m0400) and DaVinci (m0800). All these chips are placed on gimbal top board.

So the conclusion is that your gimbal top board is not connected to OFDM board.

Start by testing continuity of each wire in the ribbon cable with multimeter (test with plugs attached).

If it's not the ribbon cable or plugs, then either gimbal top board is damaged at output, or OFDM board is damaged at input.

Wow, i'm impressed !
I've spent so much time with update procedure, and googling...
Ribbon cable is new so i was confident with it but i've checked the connector on OFDM board, and first it appear to be intact. But when i connect the ribbon in it, i see it moving slightly : the welds are broken !
Tomorrow i'll bring it to a electronical technician to see if he can save the OFDM board.
No doubt this is the failure and beeping issue.
Thank a lot Quaddamage, and also 3rdof5 for the help in finding the default.
I'll keep you updated !

Colombo973 · Dec 13, 2018

Some update. An electronical technician made the job of resoldering the connector, but result is the same, no change.
I have serious doubts about his work.
Is there a way to verify connectivity on the mainboard ? I've checked all the labaled plots on the mainboard, and only one (GND) have connectivity with one pin (3rd one) on the connector.
Is someone have a list of test points on the mainboard ?

quaddamage · Dec 14, 2018

Colombo973 said:
Is someone have a list of test points on the mainboard ?

Not sure which board is main; anyway, here is my primary source of such info:
Hardware wiki on Github

Colombo973 · Dec 14, 2018

Well, the technician made a very bad job, i found some doc with test pads on RC Groups, and only one pin have continuity

So i decided to do it myself with a 10$ solder tool.

It doesn't look very nice but it works !
Now i have gimbal control, live view, and no more beep !
I've ordered a new OFDM board so it is just a temporary repair.
This week end i will check if everything is ok with the bird.
Thanks a lot for the help !

Colombo973 · Dec 20, 2018

quaddamage said:
Not sure which board is main; anyway, here is my primary source of such info:
Hardware wiki on Github

Ok guys, due to improper handling some of soldered points i've made on the board have dropped. I've tried to resolder on the pads but it was difficult because some some were torn off.
Anyway, after that, everything is fine but i don't have any live view (but it can take picture or video that are stored on sd card). I've tried several usb cable and android device, still the same problem.
I've tried to make a firmware upgrade and i have ony one line of device not detected : " [00117603][15 00][00] device not detected. "
I think one of the soldered pad is corrupted, is it possible to know which one with this error line ?

quaddamage · Dec 20, 2018

The communication to Cypress is either via CAN or via USB.

I'm almost certain it's USB. CAN is used to talk to m0900, and further to FC.

Pin explanation