Free online DJI flight log viewer

[msinger]

I released a new version today with the following changes:

• ADDED: Added missing model names for the Matrice 210 RTK V2 and MG-1P drones.
  
  
• CHANGED: Updated times to display two hundredths of a second.

@christofhapp

 

[christofhapp]

Thanks!
Now it became more precise, but the problem of the non-consistent times remains. Do you have a clue why?

the OSD.flytime timestep is always 10 ms but the CUSTOM.updateTime timestep is mostly between 100 and 110 ms, but sometimes it's 20 ms or 180 ms or something else.

Which time belongs to the GPS coordinates? Does the GPS sometimes send 2 locations very close together or is just the timestamp incorrect?

CUSTOM.date [local], CUSTOM.updateTime [local], OSD.flyTime, OSD.flyTime ,
8/10/2021,6:40:19.53 PM,0m 0.7s,0.7,
8/10/2021,6:40:19.63 PM,0m 0.8s,0.8,
8/10/2021,6:40:19.74 PM,0m 0.9s,0.9,
8/10/2021,6:40:19.84 PM,0m 1.0s,1.0,
8/10/2021,6:40:19.94 PM,0m 1.1s,1.1,
8/10/2021,6:40:20.05 PM,0m 1.2s,1.2,
8/10/2021,6:40:20.07 PM,0m 1.3s,1.3,
8/10/2021,6:40:20.25 PM,0m 1.4s,1.4,

Thanks for updating the code though!

Christof

 

[msinger]

the problem of the non-consistent times remains. Do you have a clue why?

My log viewers show the actual data from the logs DJI creates. You'd need to contact DJI for more information on how/why they log the data like that.

 

[msinger]

I released a new version today with the following changes:

• ADDED: Added incomplete records that sometimes appear at the end of DJI TXT flight logs. While these records are often missing key data, the data they expose could be useful for troubleshooting purposes.

 

[msinger]

I released a new version today with the following changes:

• FIXED: The battery data could not be decrypted in some flight logs. That failure was causing Flight Reader to generate empty log and KML files.
  
  
• FIXED: Resolved an issue that sometimes caused the max speed to display as infinite.

 

[Urkman]

My free online flight log viewer can be used to process and view flight log data from DJI TXT flight logs (from any version of DJI GO, DJI Fly, or apps using the DJI SDK), Litchi CSV flight logs, or Map Pilot CSV flight logs. These flight logs are automatically created on your mobile device when flying. After retrieving the TXT/CSV flight log from your mobile device and uploading it here, the data will be displayed in a format like this:

View attachment 131661


Here are some things you’ll be able to do after uploading your flight log:

• View the flight path of your drone on a Google map
• View important flight details in the table below the map
• Drag the slider at the top of the table to replay your flight
• See the location of the remote controller sticks at the bottom, right corner of the map
• Download a KML file to view your flight path in Google Earth
• Download CSV files that contain more columns of flight data
• Share your flight log with other people

I’ll use this thread to keep track of changes made to my log viewer. If you have any suggestions to improve it or run into any trouble using it, please post below.

BTW, if you’re processing a large amount of flight logs, doing commercial drone work, and/or want to keep your flight logs private, Flight Reader might be a better option for you.


Change Log:
See the recent posts below for a list of new features, changes, and/or fixes.

Thanks for this great tool that I occasionally use for detailed analyses - today I however run into the daily limit and wonder what the limit is and when I will be able to use it again.

 

[msinger]

wonder what the limit is and when I will be able to use it again

The limit is 10 logs within 48 hours. If you have more than that, you can save some time by using Flight Reader.

 

[msinger]

I released a new version today with the following changes:

• ADDED: Added support for the Matrice 210 RTK & Phantom 4 Multispectral drones.
  
  
• FIXED: Handled several edge cases that were causing logs to fail to process when bad data was discovered.

 

[msinger]

I released a new version today with the following changes:

• ADDED: Added "RC.downlinkSignal" and "RC.uplinkSignal" for Litchi flight logs.
  
  
• FIXED: Correctly converted the "BATTERY.current [A]" value for Litchi flight logs.

 

[msinger]

I released a new version today with the following changes:

• ADDED: Added support for processing Mini 3 Pro flight logs.
  
  
• ADDED: Added ability to process Drone Harmony CSV flight logs.
  
  
• FIXED: Get all 16 characters for serial numbers in the RECOVER section.

 

[msinger]

I released a new version today with the following changes:

• FIXED: Added a description for battery statuses that were displaying "Other" in the "Battery.status" column.
  
  
• FIXED: "Forced Landing" was incorrectly being displayed in the "OSD.flycState" column in cases where the state was "Confirm Landing".
  
  
• FIXED: The map view was sometimes displaying data in the wrong columns for the first several lines of Mini 3 Pro flight logs.

 

[msinger]

I released a new version today with the following changes:

• ADDED: Added support for processing Matrice 30T flight logs.

 

[Steve_UK_M4P]

I want to look at a particular flight log from my Mini 3 Pro (I have downloaded the log from my Mini 3 Pro to my PC using the DJI Assistant software), however the flight log is in .DAT format, will this format work with your flight log viewer?

 

[msinger]

the flight log is in .DAT format, will this format work with your flight log viewer?

No. The DAT flight logs cannot be decrypted.

Follow the instructions near the bottom of this page to locate your Mini 3 Pro TXT flight logs. Those will most likely contain whatever data you're seeking.

 

[Steve_UK_M4P]

No. The DAT flight logs cannot be decrypted.

Follow the instructions near the bottom of this page to locate your Mini 3 Pro TXT flight logs. Those will most likely contain whatever data you're seeking.

Thanks, found them now

 

[msinger]

I released a new version today with the following changes:

• FIXED: Corrected a few issues preventing some DJI GS Pro flight logs from being processed.

 

[msinger]

I released a new version today with the following changes:

• ADDED: Added support for processing Avata flight logs.

 

[msinger]

I released a new version today with the following changes:

• FIXED: Resolved a calculation issue that was sometimes allowing incorrect "OSD.hSpeed" values to be shown for some operating systems and/or architectures due to the way the .NET math library performs calculations.

 

[msinger]

I released a new version of my log viewer today with the following changes:

• ADDED: Added "OSD.mileage [ft]" and "OSD.mileage [m]" fields to show the total distance travelled as the flight progresses.
  
  
• ADDED: Added support for the Mavic 3 Enterprise and Mavic 3 Thermal drones.
  
  
• FIXED: Resolved an issue that was causing some flight logs to show too many battery cells.
  
  
• FIXED: Resolved an encryption issue that was preventing some flight logs from being processed.

 

[msinger]

I released a new version of my log viewer today with the following changes:

• ADDED: Added battery cell voltage data for the Matrice 300 RTK.
  
  
• FIXED: The incorrect drone model name was sometimes being displayed for the Mavic 3 Enterprise and Mavic 3 Thermal.
  
  
• FIXED: An incorrect flight date was sometimes being displayed for the Mavic 3 Enterprise and Mavic 3 Thermal.