robrogkr
lvl.2
Flight distance : 293976 ft
Poland
Offline
|
I would like to present you the conclusions that I have so far and information of what in my case has changed as far as stability of the bird’s flight on different firmwares is concerned.
You probably know that the complete firmware includes different parts regarding certain modules in P3 (camera, radio, barometer, vps etc.). In the newest firmware version, DJI doesn’t always do update for all the modules. The software of some modules is the same as in the 1.18 version.
Personally, I had big changes in the flight stability after the update to the 1.2.8 version, also having VPS switched off. I was wondering why some people had the same problems I had and so many people didn’t have any at all.
I have done about 20 tests of downgrade and upgrade firmware in different order (only in the bird).
- Downgrade from the 1.2.8 version to 1.1.9 and then 1.1.8 through deleting parts of the software by using the bin service file.
- Update from the state after having deleted the parts of software as well as from firmware 1.18 to 1.1.9 and to 1.2.8.
I never had any problems with the security of flight using the software 1.1.8 and 1.1.9.
However, after some update from firmware 1.1.9 to 1.2.8 the flight sometimes completed without any problems and sometimes some issues occurred.
There were no problems at all when the bird was programmed to the 1.2.8 version just after clearing the previous software.
Many years ago, I was playing around with programming of the memory Eprom with bin files. I remember that the process didn’t always go correctly and that’s why in the past, in the end there was always done a comparative test checking if all the eprom sectors were saved properly (not only by checksum).
I don’t know if such test is being done after the update of the software DJI.
I have an impression that such test wasn’t done and maybe that’s why the result after update is not identical in all the users, and the correct programming happens always only in the clear version but not always with update. Maybe with the update sometimes something unchanged from the old firmware remains in some eprom sector. I know, many “maybe”.
In my case, I can use now the newest firmware 1.2.8 which I inserted after clearing the previous version – no issues so far. Of course I have done relatively few tests to be sure 100% about my conclusions. However, at the moment, I am flying safely on the newest firmware 1.2.8.
I would like you to pay attention to the fact that I’m not a professional programmer but I’m just doing it as hobby and I’m aware of the fact that I may not know something. Also, English isn’t my mother tongue so despite it, I hope that my explanation is clear to all of you.
Maybe someone here deals with the programming of the eprom memory and could help me to solve some doubts.
P.S. All the tests I did with 1.2.0 Pilot app because I hadn’t noticed any differences with the Pilot 1.1.1.
|
|