Need Advice on Firmware

Joined
Dec 8, 2015
Messages
2
Reaction score
0
Age
37
Hello, I've got a refurbished Phantom 3 Pro that I bought from DJI, the unit works great and I've got no issues with it other than it doesn't seem to hover quite as steady as my P3S did. So I've checked the firmware on the Quad and it currently sits at 1.5.30+ and the RC is at 1.8.0.

Should I update to a newer firmware? I thought that I read over the winter that the newer firmware may cripple features or at least add more nanny's/restrictions. Is there an ideal firmware to be on?

I'm interested in playing with Litchi, which recommends updated firmware, but at the same time, if it isn't broke, don't fix it, right?

Thanks in advance.
 
Joined
Jan 15, 2017
Messages
82
Reaction score
41
So I've checked the firmware on the Quad and it currently sits at 1.5.30+ and the RC is at 1.8.0.
Wait, what?

I was given to understand that firmware past (I think) 1.8 required the newer RC versions due to changes in the encryption between the AC and RC.

The plus you are seeing is an indication that some part(s) of the system have different versions of firmware than what it's expecting. It's 'normal' to see the plus with things like batteries that have different FW versions (the battery I used to roll my AC back was flashed along with the rest of the modules, but the other two are still on the newer versions, so it shows a plus when I use those), but that base firmware level with a 1.8 RC...

There is value in the idea of not touching it if it's working fine for you, but that is just weird. I'd imagine there are some people out there that would be interested to know what FW versions are installed on your bird. :)
 

Oso

Premium Pilot
Joined
May 19, 2015
Messages
4,946
Reaction score
4,104
Location
Western US
I got that information from the about screen in the DJI app, is there somewhere to get a more accurate representation of what I've got?

New photo by Jonathan Ferri
I dont trust anything other than the LOG_AB file for many things including the FW versions on the AC.

** Note that the "LOG_AB" file is completely different from the routine "RESULT_AB" file you check for the "success" indication when you update FW.

In case you or anyone doesn't know about the LOG_AB file, 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.
The most common problem is an issue with the gimbal top (main) board which often presents as "No Image Transmission" and modules 8 and 15 showing as "device not detected."

To find your LOG_AB file, look on your SD card in the following path....

MISC/LOG/

Then find your LOG_AB file: P3X_FW_LOG_AB.txt (for P3P) -or- P3S_FW_LOG_AB.txt (for P3A)

** Some of the folders may be hidden. If you do not see them, set folders and files to show hidden.

If you don't know how to view hidden folders/files, here are two of the hundreds of sites which show you how to set them to be visible.
Use these or research on your own:
Windows
Mac

NOTE: The LOG_AB file is written by your AC and will remain on your SD card until you format the card. If you are showing hidden files and still do not see a file named exactly as above, you have likely deleted the LOG_AB file with an SD card formatting. You will need to get your AC to write the file again. What we routinely tell people is to put a very old FW .bin file alone in the root of the SD card. It should be older than your current AC FW so that it is sure to fail when you start up your AC. Your AC will write the LOG_AB file again and you should be able to see it.
 
Last edited:
Joined
Dec 8, 2015
Messages
5
Reaction score
0
Age
37
Ok, I've got a fresh SD card to go in the Aircraft. If I put it in and format it, will that install the log folder/files? I'd like to find out for sure what I've got before I go updating everything. I've learned the hard way in the past that the newest firmware isn't always the best firmware.

Is there a firmware that is deemed the "best" to be on? Didn't newer firmware limit height/distance? or am I totally incorrect there?
 
Joined
Oct 14, 2016
Messages
4,232
Reaction score
1,956
Age
67
Location
UK Brit living Latvia
After bricking my P3P yesterday - doing EVERYTHING by the book ... I advise :

DON'T FIX WHAT AIN'T BROKE !!

As to the SD Card ... as long as you haven't cleared the OTHER internal SD Card in the AC - when you put your new card in and switch on ... the MISC / DCIM folders will be created along with files. The LOG file will be there under MISC / LOG ...

It does this so that DJI can see what 'mischief' you've been up to !! ;)

You can actually get GO to delete the archive if you really want.

Nigel
 
  • Like
Reactions: Quest-So
Joined
Mar 25, 2017
Messages
13
Reaction score
1
Age
47
I dont trust anything other than my LOG_AB file for FW versions on the AC.

** Note that the "LOG_AB" file is completely different from the routine "RESULT_AB" file you check for the "success" indication when you update FW.

In case you or anyone doesn't know about the LOG_AB file, 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.
The most common problem is an issue with the gimbal top (main) board which often presents as "No Image Transmission" and modules 8 and 15 showing as "device not detected."

To find your LOG_AB file, look on your SD card in the following path....

MISC/LOG/

Then find your LOG_AB file: P3X_FW_LOG_AB.txt (for P3P) -or- P3S_FW_LOG_AB.txt (for P3A)

** Some of the folders may be hidden. If you do not see them, set folders and files to show hidden.

If you don't know how to view hidden folders/files, here are two of the hundreds of sites which show you how to set them to be visible.
Use these or research on your own:
Windows
Mac

NOTE: The LOG_AB file is written by your AC and will remain on your SD card until you format the card. If you are showing hidden files and still do not see a file named exactly as above, you have likely deleted the LOG_AB file with an SD card formatting. You will need to get your AC to write the file again. What we routinely tell people is to put a very old FW .bin file alone in the root of the SD card. It should be older than your current AC FW so that it is sure to fail when you start up your AC. Your AC will write the LOG_AB file again and you should be able to see it.
[00089068]Delete history success.

[00089376]========== remo-con disconnect. boot(15) ============
[00089445]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x34d8dbdd].
[00089519]Packet upgrade start...

[00089592]Packet checking...
[00089664]Packet vlink 01.11.0020 <-> 01.11.0020.
[00089733]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00089799]Done.

[00089875]Version checking[1]...
[00089976][03 06][00] v2.4.20.50 -> v2.4.20.50
[00090096][03 05][00] v34.2.0.9 -> v34.2.0.9
[00090179][04 00][00] v1.48.0.0 -> v1.48.0.0
[00090356][11 00][00] v1.8.0.0 -> v1.8.0.0
[00090516][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00090585][11 01][00] v1.8.0.0 -> v2.0.0.33
[00090715][12 00][00] v1.12.0.0 -> v1.12.0.0
[00090835][12 01][00] v1.12.0.0 -> v1.12.0.0
[00090955][12 02][00] v1.12.0.0 -> v1.12.0.0
[00091095][12 03][00] v1.12.0.0 -> v1.12.0.0
[00091264][15 00][00] v1.1.2.0 -> v1.1.2.0
[00091395][17 00][00] v1.1.1.7 -> v1.1.1.7
[00091556][17 01][00] v1.0.2.7 -> v1.0.2.7
[00012509]========== remo-con disconnect. boot(15) ============
[00012578]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x34d8dbdd].
[00012645]Packet upgrade start...

[00012729]Packet checking...
[00012797]Packet vlink 01.11.0020 <-> 01.11.0020.
[00012871]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00012943]Done.

[00013017]Version checking[1]...
[00013154][03 06][00] v2.4.20.50 -> v2.4.20.50
[00013269][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013352][04 00][00] v1.48.0.0 -> v1.48.0.0
[00013509][11 00][00] v1.8.0.0 -> v1.8.0.0
[00013654][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00013725][11 01][00] v1.8.0.0 -> v2.0.0.33
[00013850][12 00][00] v1.12.0.0 -> v1.12.0.0
[00013969][12 01][00] v1.12.0.0 -> v1.12.0.0
[00014109][12 02][00] v1.12.0.0 -> v1.12.0.0
[00014269][12 03][00] v1.12.0.0 -> v1.12.0.0
[00014440][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014569][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014730][17 01][00] v1.0.2.7 -> v1.0.2.7
[00027443][19 00][00] device not detected.
[00027554][01 00][00] v1.32.5432 -> v1.32.5432
[00027657][01 01][00] v1.32.5432 -> v1.32.5432
[00027782][08 00][00] v0.13.0.7 -> v0.13.0.7
[00027911][09 00][00] v0.0.0.0 -> v4.1.0.0 need upgrade.
[00028017]Done.

[00030119]Waiting for user confirm...
[00040219]Timeout, start upgrade automatically.

[00040381]Firmware upgrading[1]...
[00040476][09 00] Firmware checksum failed.
[00040578]Packet upgrade failed at firmware upgrade.



[00012609]========== remo-con disconnect. boot(15) ============
[00012715]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x34d8dbdd].
[00012819]Packet upgrade start...

[00012933]Packet checking...
[00013036]Packet vlink 01.11.0020 <-> 01.11.0020.
[00013143]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00013256]Done.

[00013359]Version checking[1]...
[00013537][03 06][00] v2.4.20.50 -> v2.4.20.50
[00013715][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013827][04 00][00] v1.48.0.0 -> v1.48.0.0
[00014035][11 00][00] v1.8.0.0 -> v1.8.0.0
[00014235][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014341][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014515][12 00][00] v1.12.0.0 -> v1.12.0.0
[00014676][12 01][00] v1.12.0.0 -> v1.12.0.0
[00014836][12 02][00] v1.12.0.0 -> v1.12.0.0
[00015015][12 03][00] v1.12.0.0 -> v1.12.0.0
[00015232][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015395][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015595][17 01][00] v1.0.2.7 -> v1.0.2.7
[00028200][19 00][00] device not detected.
[00028309][01 00][00] v1.32.5432 -> v1.32.5432
[00028411][01 01][00] v1.32.5432 -> v1.32.5432
[00028531][08 00][00] v0.13.0.7 -> v0.13.0.7
[00028656][09 00][00] v0.0.0.0 -> v4.1.0.0 need upgrade.
[00028755]Done.

[00030864]Waiting for user confirm...
[00040969]Timeout, start upgrade automatically.

[00041142]Firmware upgrading[1]...
[00041268][09 00] Firmware upgrade start...
[00093508][09 00] Firmware upgrade finished successfully.
[00093754]Done.

[00093866]Version checking[2]...
[00094003][03 06][00] v2.4.20.50 -> v2.4.20.50
[00094143][03 05][00] v34.2.0.9 -> v34.2.0.9
[00094288][04 00][00] v1.48.0.0 -> v1.48.0.0
[00094463][11 00][00] v1.8.0.0 -> v1.8.0.0
[00094648][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00094764][11 01][00] v1.8.0.0 -> v2.0.0.33
[00094912][12 00][00] v1.12.0.0 -> v1.12.0.0
[00095061][12 01][00] v1.12.0.0 -> v1.12.0.0
[00095216][12 02][00] v1.12.0.0 -> v1.12.0.0
[00095401][12 03][00] v1.12.0.0 -> v1.12.0.0
[00095629][15 00][00] v1.1.2.0 -> v1.1.2.0
[00095776][17 00][00] v1.1.1.7 -> v1.1.1.7
[00095977][17 01][00] v1.0.2.7 -> v1.0.2.7
[00096116][19 00][00] v255.255.255.254 -> v1.0.8.96
[00096232][01 00][00] v1.32.5432 -> v1.32.5432
[00096340][01 01][00] v1.32.5432 -> v1.32.5432
[00096457][08 00][00] v0.13.0.7 -> v0.13.0.7
[00096592][09 00][05] v4.1.0.0 -> v4.1.0.0
[00096707]Packet upgrade finish successfully.
 
D

Deleted member 120647

Guest
By the "SD" card are people refering to the mSD in the camera gimbal? I assume so but just want to check.

Solentlife by "the OTHER internal SD Card " are you referring to the mSD card that seems stuck into a socket/holder on the drone's mainboard? I had assumed that that was where the drone stores the DAT files and therefore could only written to by the drone, if I am mistaken do you happen to know where the DAT files are physically storted?
 

Fly Dawg

"Electricity is really just organized lightning"
Premium Pilot
Joined
Apr 29, 2016
Messages
4,655
Reaction score
2,076
Location
Watkinsville, Georgia
do you happen to know where the DAT files are physically storted?
The AC Dat files are on the main board SD card only. That is all that card is used for as far as I know.
 
  • Like
Reactions: JoBe
Joined
Nov 12, 2015
Messages
653
Reaction score
222
Age
40
By the "SD" card are people refering to the mSD in the camera gimbal? I assume so but just want to check.
yes

by "the OTHER internal SD Card " are you referring to the mSD card that seems stuck into a socket/holder on the drone's mainboard?
yes

I had assumed that that was where the drone stores the DAT files and therefore could only written to by the drone, if I am mistaken do you happen to know where the DAT files are physically storted?
you are no mistaken
 

Members online

Forum statistics

Threads
142,376
Messages
1,461,933
Members
104,178
Latest member
YashIndustries