Free online DJI flight log viewer

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

  • ADDED: Added map type toggle at the top of the map window to change the Google Map type between hybrid, roadmap, satellite, and terrain.

  • ADDED: Added play and stop buttons on the map window to automatically play back the flight route on the Google Map.

1 Like

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

  • ADDED: Added support for the Mavic 3 Pro.

  • ADDED: Added 1/4x and 1/2x play back speeds.

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

  • ADDED: Added support for the Air 3.

  • ADDED: Added new “OSD.directionOfTravel” field to show the direction (between 0 to 360 degrees) the aircraft is traveling based on the change in latitude and longitude.

  • ADDED: Added message when the RTH altitude or max altitude is changed.

  • ADDED: Added new warning messages for the following scenarios: “Propeller fell off”, “Not enough force (ESC error)”, and “Motor is blocked”.

  • FIXED: In previous versions, the following fields were sometimes not storing the correct values: OSD.isAcceletorOverRange, OSD.isVibrating, OSD.isBarometerDeadInAir, OSD.isNotEnoughForce, OSD.isMotorBlocked, OSD.isPropellerCatapult, OSD.isGoHomeHeightModified, and OSD.isOutOfLimit.

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

When I upload a .txt file from my Air 3 I get a server error. I have the most recent version of Flight Log Viewer. What can I do to get it to work?

Please send that TXT flight log file to me at [email protected] so I can take a look.

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

  • Added “Flight mode changed to {flight mode}” message in the “APP.tip” field when the flight mode changes.

  • Removed the “APP.message” field and merged its content with the “APP.tip” field since both fields were showing informational messages.

  • Resolved an issue that was preventing the “HOME.heightLimit” field from being populated for some drone models.

  • Resolved incorrectly formatted messages in the “APP.tip” and “APP.warning” fields when those messages were logged in non-English languages.

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

  • Added the following new log fields:

    • WEATHER.isFacingWind: When true, the front of the aircraft is currently facing a headwind.

    • WEATHER.isFlyingIntoWind: When true, the aircraft is currently flying into a headwind.

    • WEATHER.windDirection: The cardinal direction the wind is blowing from at the aircraft’s current location.

    • WEATHER.windRelativeDirection: The cardinal direction the wind is blowing from relative to the direction the aircraft is currently facing. For example, an East wind would be blowing toward the right side of the aircraft.

    • WEATHER.windSpeed [MPH]: The wind speed (in MPH) at the aircraft’s current location.

    • WEATHER.maxWindSpeed [MPH]: Maximum wind speed (in MPH) at the aircraft’s current location (so far in the flight log).

    • WEATHER.windStrength: Calm, Moderate, or Strong to indicate the wind strength at the aircraft’s current location.

  • Renamed the HOME.wind field to WEATHER.windStrength

Note: These fields might not be populated if you’re flying a DJI drone model released more than a few years ago.

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

  • Added support for processing Avata 2 flight logs.

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

  • Added support for processing Mini 4K flight logs.

  • Added support for processing Neo flight logs.

  • Removed the repeated “Auto returning to home” placemarks from KML while the aircraft is returning home.

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

  • Tips and warning messages that repeat in consecutive rows are now displayed once and not shown again until logged again later in the flight.

  • Some flight logs were populating the aircraft component serial number fields with unreadable characters.

  • Some battery fields were populated with a “0” when no data was available in the flight log.

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

  • Added support for processing Air 3S flight logs.

  • Added support for processing Specta Mini flight logs.

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

  • Added support for processing Flip flight logs.

  • Added support for processing Matrice 3TD flight logs.

  • Improved the message extraction logic to ensure more consistent formatting of tips and warning messages.

  • The “OSD.mileage [ft]” and “OSD.mileage [m]” fields now use speed data to calculate the distance traveled when GPS location data is unavailable.

  • Resolved flight log decryption issues that sometimes caused photo capture points to be recorded incorrectly.

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

  • Added support for processing Matrice 4E & Matrice 4T flight logs.

  • For drones with dual batteries, the serial numbers for both batteries are now stored in the SERIAL.battery and SERIAL.battery2 fields.

  • Serial numbers can be found in the RECOVER.*, DETAILS.*, and SERIAL.* fields depending on where they are extracted from flight logs. All serial numbers have been combined together and stored in the SERIAL.* fields. When referencing serial numbers, use the SERIAL.* fields as they now provide the most complete data.

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

  • Resolved an issue that prevented photo and video data from being extracted from Mini 2 flight logs.

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

  • Added support for processing Mavic 4 Pro flight logs.