- Joined
- Jun 25, 2015
- Messages
- 592
- Reaction score
- 128
Beginner's question, feraript: does your tool only take DJI Go TXT's or also DATs from the flight recorder?
Beginner's question, feraript: does your tool only take DJI Go TXT's or also DATs from the flight recorder?
It doesn't have to affect all logs.I was unable to find any change whatsoever in the RECOVER section.
new version is out
just one little bugfix:
there was longitude in APP_GPS.latitude and latitude in APP_GPS.longitude
Are you sure you are using the latest version of my tool?In your generated CSV both "CUSTOM.distance" and "CUSTOM.distance.running_max" are identical throughout the flight
Thanks for your reply. Turns out I didn't have your latest app. Your software now converts them properly but my app still converts the distance as if it's max distance. I also grabbed your newest structure definition and noticed there is no "custom.distance.running_max" listed. I believe there used to be, but I overwrote the old structure. My logs are IOS. Is my problem that your structure is Android and mine is IOS? Since your app seems to work as expected with IOS, do you have an IOS structure laid out? Attached is the log I'm using as my test flight. Great work by the way.Are you sure you are using the latest version of my tool?
If you do, then send me that flightlog and also let me know, if you are using iOS or Android app.
Are you sure? I created CSV from that log and distance (in column E) looks fine to me, it's different than distance.running_max (in column H).my app still converts the distance as if it's max distance
This column is not present in the log, it's calculated by my tool.there is no "custom.distance.running_max" listed
Actually, there are only few differences in log from iOS and Android. Bigger problem is, that with newer versions of the apps, they change that structure. I already wrote that in structure xls, that it contains specification for version 5 of log. I won't be updating the file with newer versions of apps. If anybody is interested in exact specification of latest log versions, he will have to find it by himself.do you have an IOS structure laid out?
Thanks for getting me this far. I'll do some hacking to try and figure out what I need. At one time I believe you posted your source code for your app. Would you be able to point me too it? It was helpful in determining some of the data conversions. Again, I appreciate your responses.Are you sure? I created CSV from that log and distance (in column E) looks fine to me, it's different than distance.running_max (in column H).
This column is not present in the log, it's calculated by my tool.
Actually, there are only few differences in log from iOS and Android. Bigger problem is, that with newer versions of the apps, they change that structure. I already wrote that in structure xls, that it contains specification for version 5 of log. I won't be updating the file with newer versions of apps. If anybody is interested in exact specification of latest log versions, he will have to find it by himself.
Nope, I didn't and I don't plan to.I believe you posted your source code for your app.
Not sure if you saw mine here:Has any of you Gents finished a dashware profile yet?
these texts are actually not present in DJI GO decompiled sourcesAre you able to come come across additional input on what the numbers represent in the SMART_BATTERY.status text
these texts are actually not present in DJI GO decompiled sources
so I am just using what I found here
I have no idea if they are correct or not
aah, right, they have wrong values in first rowsI'm not seeing how the those names match with the numbers that appear in flight log that I posted.
We use essential cookies to make this site work, and optional cookies to enhance your experience.