new version is out
- problem reported by some of you has been solved
- new column CUSTOM.height.running_max was added
- new optional parameter, I, was added for command line use - imperial units will be used
well, this day had to come, sooner or later@ferraript, do you have any idea what DJI changed in this log file? I noticed your log viewer is not able to read it.
Check out the CSV file it generates. It contains a lot of bad data for the log I linked to above.Hmm, weird, encryption huh... djilogs.com converts those two log files just fine.
Check out the CSV file it generates. It contains a lot of bad data for the log I linked to above.
Hmm. Perhaps we're looking at different logs. For the log I'm referring to, more than half of the rows contain bad data somewhere.
I uploaded it again and the data looks good now. Strange.I was looking at DJIFlightRecord_2016-08-21_[18-39-19].txt. Maybe try again?
yeah, they must have figured out that tooI uploaded it again and the data looks good now. Strange
I only tried one log there earlier today. The first upload resulted in invalid data in many of the CSV rows. I uploaded the same file ~15 minutes later and it magically worked. Perhaps the developer is watching this thread.So the file did not work at djilogs yesterday, but now does?
I only tried one log there earlier today. The first upload resulted in invalid data in many of the CSV rows. I uploaded the same file ~15 minutes later and it magically worked. Perhaps the developer is watching this thread.
For what it's worth, flytrex seems to be having issues with the latest logs from iOS Dji go 2.8.7 as well.
Isn't there like a code between devs to share on topics like this? Better to work together and against the big company, than each other?
We use essential cookies to make this site work, and optional cookies to enhance your experience.