P3 Firmware Phantom 3 Pro beeping (DD-DD)

Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
If it didn't work when it was given to you, and you don't know why it didn't work in the first place, I wouldn't spend any more time trying to fix it yourself. Ship it off to DJI and let them diagnose it. Start the process at the DJI site. Try not to send them the controller as the GL200A is known for higher output. DJI cut the power back with the release of later models.
correction : the RC is a GL300A
 
Joined
Jun 30, 2016
Messages
1,380
Reaction score
590
Location
PL
The drone consists of modules. Proper diagnosis involves figuring out which modules do not work.
This can be checked by sending DUML packets to each module, or by checking LOG_AB from FW update.

But sometimes people have luck with the strategy of "throw random things and see what sticks", so up to you.
 
  • Haha
Reactions: KachemakDiver
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
The drone consists of modules. Proper diagnosis involves figuring out which modules do not work.
This can be checked by sending DUML packets to each module, or by checking LOG_AB from FW update.

But sometimes people have luck with the strategy of "throw random things and see what sticks", so up to you.
If you are in my position.. what would you do? and what’s the use of DUML packets and how do i send those?
 
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
in the case of updating the firmware i now click the link button while turning on the AC to firmware reinstall instead of just turning it on normally is that alright?
 
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
Alright so i have found the LOG_AB file which is hidden so i forgot to check the show hidden files checkbox, Thanks to the O-Gs wiki (o-gs/dji-firmware-tools)
 

Attachments

  • P3X_FW_LOG_AB.txt
    27.1 KB · Views: 8
  • P3X_FW_LOG_AB.txt
    27.1 KB · Views: 6
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
im now trying to force update/downgrade it using the P3X FW Debug File zerobit forcing fw downgrade with P3X_FW_DEBUG · Issue #4 · o-gs/dji-firmware-tools
So far it's not crash beeping.

Update : Lights turned off after 5 mins. then turned back on a minute after. Gimbal then turned off then turned on for a minute or so.
ill post the logs if it has failed to update or not. for now im waiting.
 
Last edited:
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
yup failed to update.
 

Attachments

  • P3X_FW_RESULT_AB.txt
    3.3 KB · Views: 9
  • P3X_FW_LOG_AB.txt
    36.5 KB · Views: 6
Joined
Jun 30, 2016
Messages
1,380
Reaction score
590
Location
PL
You only have the well known m0800/m1500 problem, the rest of modules are booting. That's not bad.
See the spoiler section here for a fix procedure:
 
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
Nice diagram and quality of your thread. ill try to follow the diagram and report back here. Thank you very much for those who are helping me.
 
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
in the log files can you explain what this means? (sorry if the formatting is bad currently using my phone)
[01293127]Version checking[5]... [01293246][03 06][05] v2.4.20.50 -> v2.4.20.50 need upgrade. [01293346][03 05][05] v34.2.0.9 -> v34.2.0.9 need upgrade. [01293428][04 00][05] v1.48.0.0 -> v1.48.0.0 need upgrade. [01293566][11 00][05] v1.8.0.0 -> v1.8.0.0 need upgrade. [01293725][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support. [01293796][11 01][00] v1.8.0.0 -> v2.0.0.33 [01293914][12 00][05] v1.12.0.0 -> v1.12.0.0 need upgrade. [01294039][12 01][05] v1.12.0.0 -> v1.12.0.0 need upgrade. [01294151][12 02][05] v1.12.0.0 -> v1.12.0.0 need upgrade. [01294274][12 03][05] v1.12.0.0 -> v1.12.0.0 need upgrade. [01306847][15 00][00] device not detected. [01306970][17 00][05] v1.1.1.7 -> v1.1.1.7 need upgrade. [01307130][17 01][05] v1.0.2.7 -> v1.0.2.7 need upgrade. [01307230][19 00][00] v0.0.0.0 -> v1.0.8.96 need upgrade. [01307301][01 00][05] v1.32.5432 -> v1.32.5432 need upgrade [01307379][01 01][05] v1.32.5432 -> v1.32.5432 need upgrade [01319953][08 00][00] device not detected. [01320052][09 00][05] v4.1.0.0 -> v4.1.0.0 need upgrade. [01320124]Done.
You only have the well known m0800/m1500 problem, the rest of modules are booting. That's not bad.
See the spoiler section here for a fix procedure:
 
Joined
Jun 30, 2016
Messages
1,380
Reaction score
590
Location
PL
Yeah, I'll come back when you fix that formatting.

But not sure what you're missing. These are the logs, in text form. You can just read them, and guess how the software update algorithm works, based on them.

Let's say you are tasked with building a software which updates firmware in multiple components/modules. How would you do this? Asking yourself such question always helps understanding technology. It is made by people, after all. (For now.)
 
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
Yeah, I'll come back when you fix that formatting.

But not sure what you're missing. These are the logs, in text form. You can just read them, and guess how the software update algorithm works, based on them.

Let's say you are tasked with building a software which updates firmware in multiple components/modules. How would you do this? Asking yourself such question always helps understanding technology. It is made by people, after all. (For now.)
[00016316]========== remo-con disconnect. boot(15) ============ < what does this mean?
[00016392]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0xa0ce694e]. < card sn [0xa hex maybe?
[00016469]Packet upgrade start... < alright so packet upgrade is starting

[00016548]Packet checking... < checking
[00016631]Packet vlink 01.11.0020 <-> 01.11.0020. < vlink?
[00016733]Done.

[00016806]Version checking[1]... < so what are you checking?
[00016918][03 06][00] v2.4.20.50 -> v2.4.20.50 <v2.4.20.50?
[00017018][03 05][00] v34.2.0.9 -> v34.2.0.9 < esc module?
[00017110][04 00][00] v1.48.0.0 -> v1.48.0.0 < different modules maybe? or is it checking the version of the firmware?
[00017258][11 00][00] v1.8.0.0 -> v1.8.0.0
[00017418][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support. <v1.8?
[00017499][11 01][00] v1.8.0.0 -> v2.0.0.33
[00017604][12 00][00] v1.12.0.0 -> v1.12.0.0
[00017727][12 01][00] v1.12.0.0 -> v1.12.0.0
[00017858][12 02][00] v1.12.0.0 -> v1.12.0.0
[00017992][12 03][00] v1.12.0.0 -> v1.12.0.0
[00030580][15 00][00] device not detected. < what device is this checking?
[00030704][17 00][00] v1.1.1.7 -> v1.1.1.7
[00030865][17 01][00] v1.0.2.7 -> v1.0.2.7
[00030964][19 00][00] v1.0.8.96 -> v1.0.8.96
[00031042][01 00][00] v1.32.5432 -> v1.32.5432
[00031117][01 01][00] v1.32.5432 -> v1.32.5432
[00043697][08 00][00] device not detected. < also this?
[00043784][09 00][00] v4.1.0.0 -> v4.1.0.0
[00043863]Packet upgrade failed at version checking. < is packet upgrade the same as version checking?
 
Joined
Jun 30, 2016
Messages
1,380
Reaction score
590
Location
PL
[00016316]========== remo-con disconnect. boot(15) ============ < what does this mean?
It means Ambarella booted to mode 15. For you, it means nothing.

[00016392]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0xa0ce694e]. < card sn [0xa hex maybe?
Yes, but do you need that s/n for anything?

[00016631]Packet vlink 01.11.0020 <-> 01.11.0020. < vlink?
This doesn't mean much, just shows version of FW.

[00016806]Version checking[1]... < so what are you checking?
As was mentioned many times before, there are multiple modules. Every module has its firmware, and every firmware has its version.
The version of FW package is meaningless to the modules; each has its own FW version number.
Ambarella is only one module. It only knows its own FW version. So needs to query others.


[00017018][03 05][00] v34.2.0.9 -> v34.2.0.9 < esc module?
seriously? No, m0305 is no ESC. Try reading the O-Gs wiki.
 
Joined
Mar 27, 2021
Messages
20
Reaction score
0
Age
21
i now have this problem where it doesnt link the RC to the AC.
I turned on the AC then turned in the RC then I then pressed C1 C2 RECORD then waited for the beep (DASH DD)
then immediately clicked the mode dial button then it entered Linking mode (blue light beeping every blue flash.)
After that i clicked the AC linking button on the right side then it blinked red.
nothing happens.
tried updating the fw on the rc but cant connect to my dji go app.
reinstalled the dji fo several times.
tried flashing using the same firmware bin i used on the AC.
i used the emergency firmware update method from ogs and the simple method.
 

New Threads

Forum statistics

Threads
140,618
Messages
1,449,371
Members
102,427
Latest member
ldti