Deep dive into Inspire 1 Firmwares... Trying to debunk the funk...

[Brian Fist]

Which software are you using to unpack the .bin files in that manner?

D

That listing is from the log files in the MISC/LOG directory on the MicroSD card used for the update.

Turns out that every time you do an update it logs the process into internal memory of the aircraft. Every update you do amends to that log and writes the new version to the MicroSD card.

You can tell if an aircraft is a refurb or has a new N-Core in that the log will be quite short (usually only 1 update before the one you are doing). My Osmo+ is a refurb and it didn't have a scrubbed log, which means it was sent back for either an issue that had nothing to do with the camera (like a handle/battery malfunction), or someone returned it saying there was a problem and none existed they could tell. In my case I think it had to do with the cooling fan since it has started making noise on me. Doesn't matter since when you start recording it shuts the fan off, but it is still annoying to have a "new"/"refurb" product have any sort of defect.

Back on topic, there *is* a utility that breaks out the firmware modules into individual .bin files, but it is far too complicated for *most* users to get going, thus why I won't post it here (it also might be frowned upon).

 

[Gary Patterson]

Found this location for old firmware:

Download DJI Drone / Helicopter / Multicopter / Controller drivers for Windows

Download DJI Drone / Helicopter / Multicopter / Controller drivers, firmware, bios, tools, utilities

drivers.softpedia.com

You'll need to make a "magic key" file for downgrade to work properly. See Donnie Frank's YT video here:

 

[Bison]

First off, I want to start by making some observations in regards to the upgrades/downgrades. It would seem as if DJI *REALLY* doesn't want anyone downreving from v01.11.01.50. But, I do believe there is some confusion in regards to how they do it. I do NOT think the hardware in the drone itself has any ability to "lockup"/"freeze"/"brick" in any *real* sense. It is a controller with system modules and will do it's thing.

What I do think is they have engineered things to use the cameras as the "fault" point in doing upgrades/downgrades. If cameras are at certain revisions, I do believe the order in which they do the updates to the the various systems (which include the camera) ends up causing the "issues" people have, including bricking cameras and the Inspire craft itself.

They know the camera is the interface to the MicroSD card. If you screw with that you can prevent downgrades. Change the order of the downgrade and if you try going from say v01.11.01.50 to v01.08.01.00 you will create chaos because they have made multiple revisions to the camera system in the interim firmware updates. They elude to this in their release notes for various cameras by stipulating that with certain revisions you can only go back to certain other revisions (ie, safe revisions to downgrade to). Funny part is that v01.11.01.50 does not have any notes like this, thus they never intend a downgrade once installed at that revision.

I have found a "hack" to get around bricking my own cameras. I have a X3, Z3 and X5. I *DID* brick the X5, but it was a "half-brick" in that the camera starts but doesn't communicate with the aircraft (this happened well before I did more investigating early on). Now I was not willing to sacrifice my other cameras (X3, Z3) so I went the next step and used a FC350Z camera from my Osmo+. Since it identifies as a FC350Z the FC350Z firmware will load with it, but since they hamstrung that camera so the gimbal will not work with the Inspire 1 I figured it would not allow the same "fault" to happen that bricks others X3 and X5 cameras. Now, this assumption might be totally wrong and it might be the fact that it is the Z3 (FC350Z) and they are "immune" to the "fault" that they use to make downgrades difficult, but in any case, I am just letting everyone know what *I* know works.

The rest here will look at the firmwares themselves and try to determine exactly where the radio module changed to cause all the issues in range after the v01.10.01.40 firmware.

Another note is the earliest firmware for the Z3 is the v01.09.01.30 firmware. The next is v01.09.01.40 and then you jump to v01.10.01.40 which is where all the problems start. The only last revision for the Z3 is the v01.11.01.50 that is the latest for all cameras. So the z3 has only had 4 firmwares posted for it that I can find anywhere.

Can we "assume" that major system changes (radio, camera) or flight parameter systems (NFZ, height) changes would cause major firmware revisions (v01.10.x.x vs v01.09.x.x)???

Below is a listing of the various firmwares and the module revisions per the log using a Z3 camera for updates on a Inspire 1v1.

v01.11.0150 v01.10.0140 v01.09.0140 v01.09.0130 System
------------------------------------------------------------------------------
[01 00][00] v2.77.5657 -> v2.73.5514 -> v2.73.5514 -> v0.1.5346 Video Processing Loader ----------
[01 01][00] v2.77.5657 -> v2.73.5514 -> v2.73.5514 -> v0.1.5346 Video Processing App ----------
[01 04][00] v1.11.5658 -> v1.8.5460 -> v1.8.5460 -> v1.7.5327 Camera BCPU ----------
[03 05][00] v34.1.0.5 -> v34.1.0.5 -> v34.1.0.5 -> v34.1.0.5 Flight Controller Loader
[03 06][00] v2.4.20.50 -> v2.4.20.50 -> v2.4.20.18 -> v2.4.20.18 Flight Controller App **********
[04 00][00] v1.31.1.83 -> v1.30.1.47 -> v1.30.1.47 -> v1.30.1.21 Gimbal Master ----------
[04 01][00] v1.4.26.18 -> v1.4.23.18 -> v1.4.23.18 -> v1.4.15.18 Gimbal Module ----------
[04 02][00] v1.4.26.18 -> v1.4.23.18 -> v1.4.23.18 -> v1.4.15.18 Gimbal Module ----------
[04 03][00] v1.4.26.18 -> v1.4.23.18 -> v1.4.23.18 -> v1.4.15.18 Gimbal Module ----------
[05 00][00] v3.0.6.2 -> v3.0.6.2 -> v3.0.6.2 -> v3.0.6.2 Central Board
[09 00][00] v5.0.0.0 -> v5.0.0.0 -> v3.0.0.4 -> v3.0.0.4 Lightbridge Comms **********
[11 00][00] v3.10.0.0 -> v3.9.0.0 -> v3.9.0.0 -> v3.9.0.0 Battery Module
[12 00][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[12 01][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[12 02][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[12 03][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[17 00][00] v1.1.0.8 -> v1.1.0.8 -> v1.1.0.8 -> v1.1.0.8 VPS Camera Module
[17 01][00] v2.0.1.6 -> v2.0.1.6 -> v2.0.1.6 -> v2.0.1.6 VPS Sonar Module

---- Uprev in module from firmware to firmware
**** Different from v01.09.x.x to v01.10.x.x


This is a refresh on Inspire 1 V2 w/01.11.01.50
----------------------------------------------------------------------
[04 00][00] v1.31.1.77 -> v1.31.1.67 Gimbal Master ======== (no [04 01/02/03])
[08 00][00] v2.14.9.42 -> v2.14.9.42 FPV Feed ++++++++
[01 00][00] v1.22.5037 -> v1.29.5379 Video Processing Loader ========
[01 01][00] v1.22.5037 -> v1.29.5379 Video Processing App ========
[01 04][00] v0.2.4270 -> v0.5.5085 Camera BCPU ========
[03 05][00] v34.1.0.5 -> v34.1.0.5 Flight Controller Loader
[03 06][00] v2.4.20.50 -> v2.4.20.50 Flight Controller App
[05 00][00] v3.0.6.2 -> v3.0.6.2 Central Board
[09 00][00] v5.0.0.0 -> v5.0.0.0 Lightbridge Comms
[11 00][00] v3.9.0.0 -> v3.9.0.0 Battery Module
[12 00][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[12 01][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[12 02][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[12 03][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[15 00][00] v1.1.2.0 -> v1.1.2.0 USB Controller (Camera) ++++++++
[17 00][00] v1.1.0.8 -> v1.1.0.8 VPS Camera Module
[17 01][00] v2.0.1.6 -> v2.0.1.6 VPS Sonar Module
[19 00][00] v1.0.8.96 -> v1.0.8.96 ++++++++

==== Different between Cameras
++++ Additional with X5

Now if we can ascertain which system each item is, we could understand better which function is which. In my research I have come across the following:

[01 xx] Camera (Camera sensor? Camera MicroSD card interface? Gimbals?)
[11 xx] Battery
[12 xx] ESC

Based on the logfile differences between a FC550 (X5) and a FC350Z (Z3) we have major differences in [04 00] as well as [01 00/01/04], along with [08 00]/[15 00]/[19 00] all being present in the FC500 (X5) but not the FC350Z (Z3). Conversely why is [04 01/02/03] missing in the FC550 (X5) vs the FC350Z (Z3)?

Again, the only difference between the logs is one has the FC350Z (Z3) camera mounted vs the FC550 (X5) camera during the firmware load.

Now, it would seem logical that I would install the X3 and do a downgrade to v01.08.01.00 and finish off the listing here, but that is where I am asking if anyone has a v01.08.01.00 logfile available? (hopefully someone has one saved on thier system somewhere)

If so, if you can post the same block of revision chains like I did I can add the v01.08.01.00 revision to the listing above and we can get a complete view of the modules being changed per rev from v01.08.01.00 up to the latest.

I am of the mind that camera revisions only help the cameras do their job better with "fixes" and "enhancements" since they are not part of the rest of the subsystems, thus I want my cameras to all be running the latest (greatest?) revisions available for them, thus "downgrading" the firmware is not an option for me.

Now, there is a tool out there that allows for breaking down the firmware into individual modules. It is used to change flight parameters. I am wondering if it can also be used to "build" a custom firmware that would include, say, everything from the latest firmware (v01.11.01.50), but with the radio module that allows for the best distance while keeping video intact (ie, v01.08.01.00). NOTE: It is not needed, because if you update to v01.11.01.50 and then use a different camera (Osmo+ FC350Z for example) to downgrade the craft, the camera subsystems do not get downgraded. So ultimately a downgraded aircraft to v1.08/v1.09 with a latest-version camera is the same except for the radio/flight controller, which is all we are worried about.

I think if the module functions can be ascertained as to what subsystem each is responsible for, we can move forward in getting that accomplished.

I am still doing research and believe I came across a reference to the subsystem modules, so I will edit with those clarifications if I can find them again.

Hi.
I downgraded my Inspire 1, v2, X3 to 1.8.1.00 direct from v01.11.01.50+ (see attached files) and it seems ok until I look att the .txt file.
I also downgraded the controls to 1.6.0

Does this look ok?

========== 2014.01.01 00:00:04 remo-con disconnect======
Packet: WM610_FW_V01.03.00.00.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2015.12.13 14:01:09 =====================
Packet: WM610_FW_V01.04.00.10.bin
Upgrading ...
Result: Success.

========== 2015.12.13 15:36:02 =====================
Packet: WM610_FW_V01.04.00.10.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.12.13 16:08:28 =====================
Packet: WM610_FW_V01.05.00.30.bin
Upgrading ...
Result: Success.

========== 2015.12.13 18:11:57 =====================
Packet: WM610_FW_V01.05.00.30.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.06.00.40.bin
Upgrading ...

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.06.00.40.bin

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.06.00.40.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Upgrading ...

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Upgrading ...
Result: Success.

========== 2018.04.04 10:57:52 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.04 10:58:54 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.04 11:08:02 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.06 10:16:32 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.06 10:30:34 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.06.13 09:48:51 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2019.03.06 09:15:46 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.08.01.00.bin
Upgrading ...


, Bison

 

[Brian Fist]

Bison, I take it you used the force file to downgrade?

If so, and the second picture is what it shows you should be all good.

Since your log file is so extensive, why did you attempt to do so many 1.11.1.50 upgrades?

Honestly, you grabbed the wrong .txt file. You grabbed the status file not the actual update log file. Look in the directories on the microSD card and you will see another logfile that has the details of what modules got changed. That will tell you exactly what changed from what to what.

 

[Donnie Frank]

First off, I want to start by making some observations in regards to the upgrades/downgrades. It would seem as if DJI *REALLY* doesn't want anyone downreving from v01.11.01.50. But, I do believe there is some confusion in regards to how they do it. I do NOT think the hardware in the drone itself has any ability to "lockup"/"freeze"/"brick" in any *real* sense. It is a controller with system modules and will do it's thing.

What I do think is they have engineered things to use the cameras as the "fault" point in doing upgrades/downgrades. If cameras are at certain revisions, I do believe the order in which they do the updates to the the various systems (which include the camera) ends up causing the "issues" people have, including bricking cameras and the Inspire craft itself.

They know the camera is the interface to the MicroSD card. If you screw with that you can prevent downgrades. Change the order of the downgrade and if you try going from say v01.11.01.50 to v01.08.01.00 you will create chaos because they have made multiple revisions to the camera system in the interim firmware updates. They elude to this in their release notes for various cameras by stipulating that with certain revisions you can only go back to certain other revisions (ie, safe revisions to downgrade to). Funny part is that v01.11.01.50 does not have any notes like this, thus they never intend a downgrade once installed at that revision.

I have found a "hack" to get around bricking my own cameras. I have a X3, Z3 and X5. I *DID* brick the X5, but it was a "half-brick" in that the camera starts but doesn't communicate with the aircraft (this happened well before I did more investigating early on). Now I was not willing to sacrifice my other cameras (X3, Z3) so I went the next step and used a FC350Z camera from my Osmo+. Since it identifies as a FC350Z the FC350Z firmware will load with it, but since they hamstrung that camera so the gimbal will not work with the Inspire 1 I figured it would not allow the same "fault" to happen that bricks others X3 and X5 cameras. Now, this assumption might be totally wrong and it might be the fact that it is the Z3 (FC350Z) and they are "immune" to the "fault" that they use to make downgrades difficult, but in any case, I am just letting everyone know what *I* know works.

The rest here will look at the firmwares themselves and try to determine exactly where the radio module changed to cause all the issues in range after the v01.10.01.40 firmware.

Another note is the earliest firmware for the Z3 is the v01.09.01.30 firmware. The next is v01.09.01.40 and then you jump to v01.10.01.40 which is where all the problems start. The only last revision for the Z3 is the v01.11.01.50 that is the latest for all cameras. So the z3 has only had 4 firmwares posted for it that I can find anywhere.

Can we "assume" that major system changes (radio, camera) or flight parameter systems (NFZ, height) changes would cause major firmware revisions (v01.10.x.x vs v01.09.x.x)???

Below is a listing of the various firmwares and the module revisions per the log using a Z3 camera for updates on a Inspire 1v1.

v01.11.0150 v01.10.0140 v01.09.0140 v01.09.0130 System
------------------------------------------------------------------------------
[01 00][00] v2.77.5657 -> v2.73.5514 -> v2.73.5514 -> v0.1.5346 Video Processing Loader ----------
[01 01][00] v2.77.5657 -> v2.73.5514 -> v2.73.5514 -> v0.1.5346 Video Processing App ----------
[01 04][00] v1.11.5658 -> v1.8.5460 -> v1.8.5460 -> v1.7.5327 Camera BCPU ----------
[03 05][00] v34.1.0.5 -> v34.1.0.5 -> v34.1.0.5 -> v34.1.0.5 Flight Controller Loader
[03 06][00] v2.4.20.50 -> v2.4.20.50 -> v2.4.20.18 -> v2.4.20.18 Flight Controller App **********
[04 00][00] v1.31.1.83 -> v1.30.1.47 -> v1.30.1.47 -> v1.30.1.21 Gimbal Master ----------
[04 01][00] v1.4.26.18 -> v1.4.23.18 -> v1.4.23.18 -> v1.4.15.18 Gimbal Module ----------
[04 02][00] v1.4.26.18 -> v1.4.23.18 -> v1.4.23.18 -> v1.4.15.18 Gimbal Module ----------
[04 03][00] v1.4.26.18 -> v1.4.23.18 -> v1.4.23.18 -> v1.4.15.18 Gimbal Module ----------
[05 00][00] v3.0.6.2 -> v3.0.6.2 -> v3.0.6.2 -> v3.0.6.2 Central Board
[09 00][00] v5.0.0.0 -> v5.0.0.0 -> v3.0.0.4 -> v3.0.0.4 Lightbridge Comms **********
[11 00][00] v3.10.0.0 -> v3.9.0.0 -> v3.9.0.0 -> v3.9.0.0 Battery Module
[12 00][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[12 01][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[12 02][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[12 03][00] v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 -> v1.11.0.0 ESC Module
[17 00][00] v1.1.0.8 -> v1.1.0.8 -> v1.1.0.8 -> v1.1.0.8 VPS Camera Module
[17 01][00] v2.0.1.6 -> v2.0.1.6 -> v2.0.1.6 -> v2.0.1.6 VPS Sonar Module

---- Uprev in module from firmware to firmware
**** Different from v01.09.x.x to v01.10.x.x


This is a refresh on Inspire 1 V2 w/01.11.01.50
----------------------------------------------------------------------
[04 00][00] v1.31.1.77 -> v1.31.1.67 Gimbal Master ======== (no [04 01/02/03])
[08 00][00] v2.14.9.42 -> v2.14.9.42 FPV Feed ++++++++
[01 00][00] v1.22.5037 -> v1.29.5379 Video Processing Loader ========
[01 01][00] v1.22.5037 -> v1.29.5379 Video Processing App ========
[01 04][00] v0.2.4270 -> v0.5.5085 Camera BCPU ========
[03 05][00] v34.1.0.5 -> v34.1.0.5 Flight Controller Loader
[03 06][00] v2.4.20.50 -> v2.4.20.50 Flight Controller App
[05 00][00] v3.0.6.2 -> v3.0.6.2 Central Board
[09 00][00] v5.0.0.0 -> v5.0.0.0 Lightbridge Comms
[11 00][00] v3.9.0.0 -> v3.9.0.0 Battery Module
[12 00][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[12 01][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[12 02][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[12 03][00] v1.11.0.0 -> v1.11.0.0 ESC Module
[15 00][00] v1.1.2.0 -> v1.1.2.0 USB Controller (Camera) ++++++++
[17 00][00] v1.1.0.8 -> v1.1.0.8 VPS Camera Module
[17 01][00] v2.0.1.6 -> v2.0.1.6 VPS Sonar Module
[19 00][00] v1.0.8.96 -> v1.0.8.96 ++++++++

==== Different between Cameras
++++ Additional with X5

Now if we can ascertain which system each item is, we could understand better which function is which. In my research I have come across the following:

[01 xx] Camera (Camera sensor? Camera MicroSD card interface? Gimbals?)
[11 xx] Battery
[12 xx] ESC

Based on the logfile differences between a FC550 (X5) and a FC350Z (Z3) we have major differences in [04 00] as well as [01 00/01/04], along with [08 00]/[15 00]/[19 00] all being present in the FC500 (X5) but not the FC350Z (Z3). Conversely why is [04 01/02/03] missing in the FC550 (X5) vs the FC350Z (Z3)?

Again, the only difference between the logs is one has the FC350Z (Z3) camera mounted vs the FC550 (X5) camera during the firmware load.

Now, it would seem logical that I would install the X3 and do a downgrade to v01.08.01.00 and finish off the listing here, but that is where I am asking if anyone has a v01.08.01.00 logfile available? (hopefully someone has one saved on thier system somewhere)

If so, if you can post the same block of revision chains like I did I can add the v01.08.01.00 revision to the listing above and we can get a complete view of the modules being changed per rev from v01.08.01.00 up to the latest.

I am of the mind that camera revisions only help the cameras do their job better with "fixes" and "enhancements" since they are not part of the rest of the subsystems, thus I want my cameras to all be running the latest (greatest?) revisions available for them, thus "downgrading" the firmware is not an option for me.

Now, there is a tool out there that allows for breaking down the firmware into individual modules. It is used to change flight parameters. I am wondering if it can also be used to "build" a custom firmware that would include, say, everything from the latest firmware (v01.11.01.50), but with the radio module that allows for the best distance while keeping video intact (ie, v01.08.01.00). NOTE: It is not needed, because if you update to v01.11.01.50 and then use a different camera (Osmo+ FC350Z for example) to downgrade the craft, the camera subsystems do not get downgraded. So ultimately a downgraded aircraft to v1.08/v1.09 with a latest-version camera is the same except for the radio/flight controller, which is all we are worried about.

I think if the module functions can be ascertained as to what subsystem each is responsible for, we can move forward in getting that accomplished.

I am still doing research and believe I came across a reference to the subsystem modules, so I will edit with those clarifications if I can find them again.

Revisiting this topic...

If I'm reading you correctly, I can use an X3 running FW v1.08.xx to roll back an Inspire 1 running FW v1.11.xx??? I conclude this because, as you said, it's the latest *camera* FW that hamstrings the roll back. Is this correct thinking?

Note: I'm okay with the camera's legacy FW. So I don't require the latest modules for my cameras.

D

 

[Brian Fist]

Actually I have not found them able to "brick" a X3 via a firmware rollback. Only the X5 series can be brick because of a firmware rollback.

So, in essence, ANY X3 camera firmware can be used to rollback an aircrafts firmware. What you end up with is the camera also running the rolled-back firmware revision.

Ultimately, the "ideal" camera firmware you want is the LATEST firmware revision due to "fixes" made in the cameras firmware.

If you are happy with the legacy camera firmware, then by all means run it. I just know that DJI made a number of "fixes" to the cameras themselves with later firmware revisions.

I might be able to put together a "camera update" that would ONLY update a cameras firmware to the latest. If there is any interest in that I will pull the camera firmware modules and package them in a separate firmware image. Just let me know.

 

[Donnie Frank]

Actually I have not found them able to "brick" a X3 via a firmware rollback. Only the X5 series can be brick because of a firmware rollback.

So, in essence, ANY X3 camera firmware can be used to rollback an aircrafts firmware. What you end up with is the camera also running the rolled-back firmware revision.

Ultimately, the "ideal" camera firmware you want is the LATEST firmware revision due to "fixes" made in the cameras firmware.

If you are happy with the legacy camera firmware, then by all means run it. I just know that DJI made a number of "fixes" to the cameras themselves with later firmware revisions.

I might be able to put together a "camera update" that would ONLY update a cameras firmware to the latest. If there is any interest in that I will pull the camera firmware modules and package them in a separate firmware image. Just let me know.

Do you know specifically what DJI fixed on the cameras? Honestly, both my cameras work well and without trouble. Very curious to hear your answer...

D

 

[Brian Fist]

Actually, I do believe I have a technical brief that outlines the camera fixes themselves here somewhere...

I know the changes for the X5 series included white balance, aperture and color map fixes. ie, for the X5 they are more or less "required" to get the best possible image out of the X5 series.

In regards to the X3/Z3 I do believe it was white balance, color mapping and for the Z3 it included gimbal control and zoom fixes.

I will look through my research a little later tonight and see if I can find the tech info I downloaded.

 

[Donnie Frank]

Actually, I do believe I have a technical brief that outlines the camera fixes themselves here somewhere...

I know the changes for the X5 series included white balance, aperture and color map fixes. ie, for the X5 they are more or less "required" to get the best possible image out of the X5 series.

In regards to the X3/Z3 I do believe it was white balance, color mapping and for the Z3 it included gimbal control and zoom fixes.

I will look through my research a little later tonight and see if I can find the tech info I downloaded.

Thanx. Your efforts are appreciated, but don't put yourself out. I just thought you might have that information readily available.

D

 

[svarteld]

Nice info, thanks.

I still fly a couple of Inspire 1 + X5R commercially, with custom FW parameters (like 60° tilt, no NFZ or limits, calmer BMS, manual mode, etc). It's both amazingly fast now, and less picky about all sort of stuff.

I've got 6 crafts, some being modified hardware-wise (mostly replaced leg mechanics for lighter weight).

I'm at the latest FW though. Would a FW rollback bring the FCC, RF power, channel hacks via config files etc back, with an older Android DJI GO app?

I'm an engineer, but crappy at programming

Thanks in advance /Peter

 

[Jimmy6616]

Brian and the gang, I plan to use either an X3 or a FC350Z to roll back my 1.11.50 to 1.8.01

Is there a way, and mentioned above, to then bring the camera only back to current and have the extra camera functions associated with 1.11.50? I have the Python software which will disassemble the main bin file into the component parts but after that I’m a bit sketchy about which module bin’s the camera needs and how to create a new camera only bin file ? Ta in advance