Two weeks or so ago I updated my P3P.  After updating both the P3 and all of the batteries I formatted the card deleting the firmware update.

I now have two new batteries on the way.  What is the best way to update the firmware on these new batteries?  I assume just download the update again and put it back on the SD card?  Also will the new update still update the batteries even though the battery update was in one firmware version back?

For that matter is it really that critical or just wait for the next firmware update to update these two new batteries?

Thanks in advance!

The 1.4.10 firmware contains the same battery update as the 1.3.20 firmware does, so just use the latest one.

As to it being critical or not.. No idea.. But to be safe I would update them. I would think the firmware changes relate to battery care from the software/hardware or some calibration for efficiency. or maybe a massive BUG was discovered that can make it drop form the sky.. Who knows

Fair enough.  I will update them then.  

sploodge Posted at 2015-9-30 09:15
The 1.4.10 firmware contains the same battery update as the 1.3.20 firmware does, so just use the la ...

Is there a way to confirm the firmware on a battery?  I tried updating two batteries but they wouldnt update. Maybe they already had the current firmware but it would be nice to know for sure.

bill@northwoods Posted at 2015-10-1 20:42
Is there a way to confirm the firmware on a battery?  I tried updating two batteries but they would ...

I've wondered that myself.  The Phantom assistant for the Phantom 2 series would display the version information for the flight controller, the GPS, the transmitter, the gimbal, the camera and the battery.  Maybe the P3 will catch up eventually...

This got me thinking and I was just looking at the log files that are kept on the micro SD.  The version numbers of the various components are probably in there somewhere (maybe the "P3X_FW_LOG_AB.txt" file??) but I don't have the secret decoder ring to decrypt the information.  Anyone...?

gil Posted at 2015-10-2 09:31
This got me thinking and I was just looking at the log files that are kept on the micro SD.  The ver ...

Something like this:  

[00012680]========== remo-con disconnect. boot(15) ============
[00012715]Packet [C:\P3X_FW_V01.04.0010.bin] detected, card sn [0xa0ce47d3].
[00012753]Packet upgrade start...
[00077532]Version checking[2]...
[00077601][03 05][00] v34.2.0.9 -> v34.2.0.9                    03 05 -> Main Controller
[00077681][03 06][00] v2.2.6.19 -> v2.2.6.19                    03 06 -> Main Controller
[00077726][04 00][00] v1.40.0.0 -> v1.40.0.0                   04 00 -> Gimbal
[00077787][09 00][00] v1.7.0.3 -> v1.7.0.3                          09 00 -> OFDM Air End
[00077902][11 00][05] v1.7.0.0 -> v1.7.0.0                        11 00 -> Battery
[00077997][12 00][00] v1.8.0.0 -> v1.8.0.0                        12 00 -> M1 ESC
[00078072][12 01][00] v1.8.0.0 -> v1.8.0.0                        12 01 -> M2 ESC
[00078162][12 02][00] v1.8.0.0 -> v1.8.0.0                        12 02 -> M3 ESC
[00078247][12 03][00] v1.8.0.0 -> v1.8.0.0                        12 03 -> M4 ESC
[00078375][15 00][00] v1.1.2.0 -> v1.1.2.0                        15 00 -> Air End USB Transmit
[00078452][17 00][00] v1.1.1.7 -> v1.1.1.7                        17 00 -> Vision Positioning System
[00078572][17 01][00] v1.0.2.7 -> v1.0.2.7                        17 01 -> VPS
[00078627][19 00][00] v1.0.8.96 -> v1.0.8.96                  19 00 -> Air Base Band
[00078665][01 00][00] v1.23.3419 -> v1.23.3419                01 00 -> Camera
[00078780][01 01][00] v1.23.3419 -> v1.23.3419                01 01 -> Camera
[00078831][08 00][00] v0.12.0.4 -> v0.12.0.4                  08 00 -> Air Encoder
[00078870]Packet upgrade finish successfully.

Shazam!  Just like that!  (Hmmm, what the heck is the " OFDM Air End"??)

Now, if only DJI would make all that available in the DJI GO APP so we wouldn't have to remove the SD card and look up the codes!

On a related note, and maybe I'm just scratching something that shouldn't itch here, I rearranged the code sequence numbers and noticed some gaps in the code numbering they used.  Any idea of what or why these code line numbers are not used (I provided some guesses)?   
If I'm not cleared at this level of classification or it's one of those "I could tell you but then I'd have to kill you" things I PROMISE not to tell anybody!

[00013324]Version checking[1]...
[00015557][01 00][00] v1.23.3419 -> v1.23.3419         01 00 -> Camera
[00015720][01 01][00] v1.23.3419 -> v1.23.3419         01 01 -> Camera
                    [02 00] ?  ? Flux Capacitor
[00013417][03 05][00] v34.2.0.9 -> v34.2.0.9         03 05 -> Main Controller
[00013520][03 06][00] v2.3.0.13 -> v2.3.0.13         03 06 -> Main Controller
[00013590][04 00][00] v1.41.0.0 -> v1.41.0.0         04 00 -> Gimbal
                    [05 00] ?  ? Collision Avoidance
                    [06 00] ?  ? Automatic coffee retrieval
                    [07 00] ?  ? Coffee free refills counter
[00015803][08 00][00] v0.12.0.4 -> v0.12.0.4         08 00 -> Air Encoder
[00013669][09 00][00] v1.7.0.3 -> v1.7.0.3         09 00 -> OFDM Air End
                    [10 00] ?  ? Air to ground missle control
[00013815][11 00][00] v1.7.0.0 -> v1.7.0.0         11 00 -> Battery
[00013933][12 00][00] v1.10.0.0 -> v1.10.0.0         12 00 -> M1 ESC
[00014046][12 01][00] v1.10.0.0 -> v1.10.0.0         12 01 -> M2 ESC
[00014161][12 02][00] v1.10.0.0 -> v1.10.0.0         12 02 -> M3 ESC
[00014267][12 03][00] v1.10.0.0 -> v1.10.0.0         12 03 -> M4 ESC
                    [13 00] ?  ? Amazon package delivery
                    [14 00] ?  ? Amazon dropped-from-great-height-package return
[00015156][15 00][00] v1.1.2.0 -> v1.1.2.0         15 00 -> Air End USB Transmit
                    [16 00] ?  ? Cut-the-blue-wire bomb disarmmament
[00015266][17 00][00] v1.1.1.7 -> v1.1.1.7         17 00 -> Vision Positioning System
[00015403][17 01][00] v1.0.2.7 -> v1.0.2.7         17 01 -> VPS
                   [18 00] ?  ? Self-destruct
[00015494][19 00][00] v1.0.8.96 -> v1.0.8.96         19 00 -> Air Base Band[02 00] ?

gil Posted at 2015-10-2 10:43
Shazam!  Just like that!  (Hmmm, what the heck is the " OFDM Air End"??)

OFDM -> Orthogonal_Frequency_Division_Multiplexing -> (Wireless) -> OFDM

http://store.dji.com/product/pha ... iver-module-pro-adv

In other words, Lightbridge

sploodge Posted at 2015-9-30 09:15
The 1.4.10 firmware contains the same battery update as the 1.3.20 firmware does, so just use the la ...

I thought it had to be done from the Bin File? He stated that he deleted the Bin File from the SD Card. Could be wrong but all of the Tutorials that I have watched state to update the Batteries with the Bin File still on the Card before you delete the Bin from the Card.

rodger Posted at 2015-10-2 22:12
I thought it had to be done from the Bin File? He stated that he deleted the Bin File from the SD  ...

You are correct roger, the OP will need to place the extracted .bin file from the 1.4.10 update ZIP download, back on his SD Card to perform any update.  

To actually see if the battery was updated, you need to examine the detail update log that is hidden on the SD Card. Our P3 airframes have 16 components that may be updated within each firmware release. At the conclusion of each update, the P3 records a summary in the P3X_FW_RESULT_AB.txt (professional) file. DJI hides a MISC folder on the SD Card that contains four hidden subfolders (IDX, LOG, THM, & XCODE). In the hidden LOG folder, you will find a detailed P3X_FW_LOG_AB.txt file that show each component update status and version.

The battery is component [11 00] when you look at the P3X_FW_LOG_AB.txt. The battery firmware was originally v1.6.0.0. In firmware 1.3.20, the battery was updated to v1.7.0.0. So batteries updated at version 1.3.20 do not need further updates. New batteries should be checked for updates using the latest firmware and then taking a look at the detailed hidden log to see what version of firmware is on the battery. Currently it should be at version v1.7.0.0.

Additionally, when the firmware is on your SD Card, the P3 will check versions of all components and  if everything is current, then the upgrade will abort. If the battery needs updating, you can look at the battery leds. During battery firmware update, the two center leds will illuminate during the process.

terrylewis Posted at 2015-10-4 11:47
You are correct roger, the OP will need to place the extracted .bin file from the 1.4.10 update ZI ...

Thanks Terry. If memory serves the Battery updates have been done since the beginning as all of the DJI Batteries have circuitry in them.

OK on the Abort also. I figured that would show up ;when the Program encountered a system that was up to date. It just made sense.

rodger Posted at 2015-10-5 02:28
Thanks Terry. If memory serves the Battery updates have been done since the beginning as all of th ...

Sploodge just posted that the GO App will actually tell you if your battery needs updating. I did not know that, as I deliberately updated all my batteries at 1.3.20. It certainly makes sense though!

I did replace the bin file. I will have to go into the hidden log and double check.

terrylewis Posted at 2015-10-4 14:38
Sploodge just posted that the GO App will actually tell you if your battery needs updating. I did  ...

Really, Sploodge is always up to speed. DJI is very innovated in what they . Their Programs are truly amazing. With the boundaries that they are breaking you have to expect a hiccup or two here and there. I truly don't understand why some people get so upset over a little glitch. It happens to every developer. No one is immune to it. It is the nature of the beast. I have a few Phantoms and an Inspire. When I read about a glitch here on the forum I will avoid putting myself in that situation. If it is serious and I want to fly I grab ole reliable Phantom 2 Vision. That bird is as reliable as they come. Never an issue.

bill@northwoods Posted at 2015-10-4 15:18
I did replace the bin file. I will have to go into the hidden log and double check.

Bill, don't worry about the log. Put the Bin File back in and then cycle your Batteries through the Phantom. Terry has a Post where he mentions that Sploodge states that there will be a pop up when you put a Battery in and it needs to be updated. What you may want to do is keep the card with the Bin File on it separate and use it when you buy another Battery(s). The Cards are cheap enough. I must have at least 30 of them in a container with all os my SD Card items.

terrylewis Posted at 2015-10-1 21:09
Something like this:  

[00012680]========== remo-con disconnect. boot(15) ============

Thanks Terry, you da man! I've been looking everywhere for that information.

The two most common items that I have seen listed as device not detected are 8 and 15. Looks like Air encoder, and air end USB transmit.

Those sound like Lightbridge components, but I just was able to update a P3 with everything detected by replacing the camera / gimbal.

Any further info you could provide would be much appreciated. Thanks again.

put the firmware on the sd card and stick it in the drone. put in battery 1 and update. when its done same thing for battery 2. just make sure you delete the result.txt

terrylewis Posted at 2015-10-1 18:09
Something like this:  

[00012680]========== remo-con disconnect. boot(15) ============

what is air end usb transmitter i have this issue and have no idea what to buy haha

[15 00][00] device not detected.

djiuser_Im5C5ZlV9GVS Posted at 12-16 14:49
what is air end usb transmitter i have this issue and have no idea what to buy haha

[15 00][00] device not detected.

This thread is 4 years old !!

Maybe someone can jump in and answer ...