at this moment I can finally give you an answerIt is strange because when I load it on Airdata.com, I can see the real printed serial number "082AD4T0310K4V"
I also find the "196" value as the "Internal Serial" on airdata.com
What does it mean ?
I already answered thisok thanks so it means that the real SN is not systematicaly written in the logs ?
What about this flight ? the battery SN 0DQADBN03104X0 is readable directly in the raw file (open with Blocnote) but the battery SN coming from your converter is "0" ? Here also, AirData recognize the real battery SN and I have imported only one flight with this battery (this one).... ? it is strange
Thankfs for your uptdate !
I'll look into it. If those fields don't change their position within the log with every new DJI GO version, I'll try to add them... in the future.Is it something possible for a next evolution ?
decrypting algorithm is not shareableany chance of open-sourcing your tool?
decrypting algorithm is not shareable
and without it, source code is irrelevant
so, sorry, answer is no
Excellent -- many thanks.new version is out
- it fixes the FIRMWARE.version column (I forgot to decrypt it, so it couldn't work)
- most importantly, it brings battery data for Mavics, like capacities, cell voltages, temperature
new version is out
- most importantly, it brings battery data for Mavics, like capacities, cell voltages, temperature
Yes, they are also encrypted.Are the Phantom 3 TXT files encrypted?
We use essential cookies to make this site work, and optional cookies to enhance your experience.