Decrypt any DJI flight log with Flight Reader

[msinger]

A new version of Flight Reader is available. Release 1.5.25 includes the following changes:

• New aircraft/battery usage reports are available to show the aircraft/battery usage stats (min/max/average/total) for any time frame. To access these reports, right click any flight in the main Flight Reader window and choose the desired aircraft/battery usage report from the “Reports” menu.
  
  
• “FLIGHT.mileage”, “TAKEOFF.location”, and “TAKEOFF.locationAddress” fields have been added to the Aircraft Report. The new location fields show the city/region/address closest to the flight location.
  
  
• “DETAILS.location” and “DETAILS.locationAddress” fields have been added to the Aircraft Log to show the city/region/address closest to the flight location.
  
  
• “Location”, “Flight Start Time Actual”, “Flight End Time Actual”, and “Total Mileage” columns have been added to the flight list in the main Flight Reader window. The new Time Actual columns show times in the time zone at the flight location.
  
  
• Added seconds to the flight start/end times in the aircraft/battery reports for additional precision.
  
  
• In the main Flight Reader window, flights on the same date are now sorted by time in descending order (most recent flight at the top).
  
  
• Resolved an issue that prevented some flights from being deleted from the flight list in the main flight reader window.
  
  
• Added missing tooltip descriptions to the “Available Fields” and “Selected Fields” lists in the “Logs/Reports” section of the Flight Reader Options window.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.29 includes the following changes:

• Select multiple flights in the main Flight Reader window, right click, and choose “KML” to load all selected flight paths into Google Earth (or your default KML viewer) at the same time.
  
  
• New median fields have been added to the battery usage report. This might be useful in cases where the average is skewed due to an extreme value existing within the selected report range. Those new fields include “MED.chargeLevelEnd”, “MED.chargeLevelStart”, “MED.batteryTemperature [C]”, “MED.batteryTemperature [F]”, and “MED.flightDuration”.
  
  
• New battery usage report fields have been added to show stats for the battery cell deviation. Those new fields include “MIN.highCellDeviation [%]”, “MAX.highCellDeviation [%]”, “AVG.highCellDeviation [%]”, and “MED.highCellDeviation [%]”.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.34 includes 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.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.37 includes the following changes:

• Extracted additional battery percentage and cell voltage data for dual battery drones. Depending on the drone model you're flying and the data recorded in the TXT flight log, some or all of the individual battery data might not be available in the TXT flight log file for extraction.
  
  
• In Flight Reader 1.5.28, a change was made to use the longest available aircraft serial number (since there can be several aircraft serial numbers inside the TXT flight log file). This release will update the displayed aircraft serial number for any flights using the old shorter serial number if another flight log was processed for the same aircraft and it's displaying a longer serial number.
  
  
• Swapped the values for the "Date Actual" and "Date Local" columns and the "Flight Start/End Time Actual" and "Flight Start/End Time Local" columns in the main Flight Reader window since they were displaying in the wrong columns.
  
  
• When right clicking a flight in the main Flight Reader window to generate a report from the "Reports" menu, the aircraft/battery serial number displayed in the report menu items was not always displaying the correct serial number. This was only a display issue with the menu as the generated reports still included the data for the correct aircraft/battery.
  
  
• When a flight log is processed, Flight Reader extracts any snapshot images it finds inside of the TXT flight log file. When a snapshot image is exported, a thumbnail image for that snapshot should also be created for display in the "Photo" column of the main Flight Reader window. This release corrects an issue where the thumbnail image was sometimes not being created and displayed in the main Flight Reader window.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.44 includes the following changes:

• Added the following log fields for drones equipped with a DJI D-RTK antenna: RTK.aircraftLatitude, RTK.aircraftLongitude, RTK.baseStationLatitude, RTK.baseStationLongitude, RTK.baseStationAltitude [ft], and RTK.baseStationAltitude [m].
  
  
• Resolved an issue that was sometimes preventing pilots from being auto assigned to flight logs downloaded from the DJI Cloud when syncing flight logs.
  
  
• Improved the logic used to populate the “CAMERA.isPhoto” and “CAMERA.isVideo” fields to account for various inconsistencies across DJI drone models and DJI flight application versions.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.46 includes the following changes:

• Made additional improvements to resolve incorrect data that was sometimes being populated in the "CAMERA.isPhoto" and "CAMERA.isVideo" fields.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.47 includes the following changes:

• The columns in the map window can now be added/removed/reordered/renamed by configuring the “Map Log” fields in the “Logs/Reports” section of the Flight Reader Options window.
  
  
• Added new “BATTERY.cellVoltageDeviation [V]” and “BATTERY2.cellVoltageDeviation [V]” fields to show the current difference in voltage among the battery cells.
  
  
• Added new “RTK.aircraftAltitude [ft]” and “RTK.aircraftAltitude [m]” fields to show the aircraft’s current altitude as reported by the RTK module.
  
  
• Added new “RTK.aircraftHeight [ft]”, “RTK.aircraftHeight [m]”, “RTK.aircraftHeightMax [ft]”, and “RTK.aircraftHeightMax [m]” fields to show the aircraft’s current or maximum height above the takeoff location as reported by the RTK module.
  
  
• Updated the “RTK.baseStationAltitude [ft]” and “RTK.baseStationAltitude [m]” fields to display altitude values when negative. Previous versions of Flight Reader were hiding these values when they were below zero.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.48 includes the following changes:

• Made improvements to numeric value formatting to prevent those values from ending with a decimal symbol or a zero decimal place value when the number is also 0 (e.g. 0.0).
  
  
• When using the default Map Log fields in the Map window, the “IMU Height” column was displaying the max height instead of the current height.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.5.49 includes 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.windSpeed [m/s]: The wind speed (in m/s) at the aircraft’s current location.
    
    
  • WEATHER.windSpeed [km/h]: The wind speed (in km/h) 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.maxWindSpeed [m/s]: Maximum wind speed (in m/s) at the aircraft’s current location (so far in the flight log).
    
    
  • WEATHER.maxWindSpeed [km/h]: Maximum wind speed (in km/h) 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.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.0 includes the following changes:

• Added support for processing Avata 2 flight logs.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.3 includes the following changes:

• Added support for processing Mini 4K flight logs.
  
  
• When flight logs are synced using the “File” → “Sync Flight Logs” menu item at the top of the main Flight Reader window, TXT flight logs found on any Android devices (phone/tablet/DJI RC) connected to your computer will be automatically imported into Flight Reader. If Flight Reader is started after connecting an Android device, the TXT flight logs will be synced automatically when Flight Reader starts.
  
  Note: Make sure your Android device is connected to your computer using a USB cable that supports data transfers (some USB cables are for charging only). For Android phones/tablets, choose the “File Transfer” USB mode when prompted after connecting the USB cable. For DJI RCs (with a screen), check that you have the latest firmware installed if you have any trouble transferring flight logs.
  
  
• New settings have been added in the “KML” section of the Flight Reader Options window to set the width, color, and transparency of the ground line in the generated KML files.
  
  
• Resolved an issue that was causing some flight logs to fail to process when flight log fields contained an empty value.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.6 includes the following changes:

• Resolved an issue that was sometimes causing the main Flight Reader window status to get stuck at “Processing flight logs” while attempting to sync flight logs.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.9 includes the following changes:

• Added support for processing Neo flight logs.
  
  
• When using the “File” → “Sync Flight Logs” feature to sync flight logs from a local Android device (as documented here), flight logs will also be synced from Litchi if installed.
  
  
• Removed the repeated “Auto returning to home” placemarks from the map and KML while the aircraft is returning home.
  
  
• When adding new fields in the “Logs/Reports” section of the Flight Reader Options window, the new field is added below (instead of above) the field selected in the “Selected Fields” list.
  
  
• The “Sync History” menu item is only displayed in the “File” menu when history data is available.
  
  
• Resolved issue causing Flight Reader to crash when attempting to open an aircraft log while the associated CSV file was open in Excel or other CSV reader that locks the CSV file upon opening it.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.11 includes the following changes:

• Added Flight Log Transfer Service to allow flight logs to be transferred to Flight Reader over a local network from a mobile web browser on an Apple or Android mobile device.
  
  
• SRT files can be converted to KML files by dragging and dropping them onto the main Flight Reader window.
  
  
• Tips and warning messages that repeat in consecutive rows are now displayed once and not shown again until logged again later in the flight.
  
  
• When exporting files from Flight Reader, files in the export folder location are no longer deleted before exporting the selected files.
  
  
• 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.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.14 includes the following changes:

• Added Charts to generate line charts from flight data in the aircraft CSV.
  
  
• Discovered the best local IP address for the Service Location displayed in the Flight Log Transfer service window.
  
  
• Resolved an issue that prevented the aircraft CSV from auto loading into CsvView when the file path contained spaces.
  
  
• Resolved an issue causing the “OSD.flyTime” field to be set to 0 when the last line of the flight log was still saving while the drone powered off.
  
  
• Resolved an issue causing the “APP.tip” and “APP.warning” field values to spill into other columns of the Aircraft CSV when Windows uses “;” as the CSV separator.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.17 includes the following changes:

• Added support for processing Air 3S flight logs.
  
  
• Added support for processing Specta Mini flight logs.
  
  
• Added ability to process GUTMA flight logs.
  
  
• Removed “sep=” line from the top of generated CSV files.
  
  
• Allowed “&” to be included in the name when saving a favorite chart.
  
  
• Resolved several crashes that can occur after removing fields from the Aircraft Log in the Flight Reader Options.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.21 includes the following changes:

• Added a new "OSD.yaw [unwrapped]" field for easier visualization of aircraft yaw changes. This field shows the aircraft's cumulative rotation angle, with positive values indicating clockwise turns and negative values indicating counterclockwise turns, reflecting total degrees turned in either direction.
  
  
• Added an optional "Battery Times Charged" column to the Flight Reader main window. To add this column, right click the column headers and select "Customize Columns".
  
  
• Updated the "Flight Date" dropdown at the top of the Flight Reader main window to include the count of flights displayed in the main window.
  
  
• Enhanced performance and precision of the fly time line drawn on charts when moving the mouse pointer over graphed lines.
  
  
• Removed the Byte Order Mark (BOM) from the first line of CSV files generated by Flight Reader. This change ensures compatibility with CsvView and other CSV viewers that cannot process CSV files with BOMs.
  
  
• Remember the last selected column sort order in the Flight Reader main window and improved performance when loading or reloading flights.

See the release notes for a complete list of changes.

 

[msinger]

A new version of Flight Reader is available. Release 1.6.24 includes the following changes:

• Added support for processing Anzu drone flight logs.
  
  
• The "OSD.mileage [ft]" and "OSD.mileage [m]" fields now use speed data to calculate the distance traveled when GPS location data is unavailable.
  
  
• Updated existing DJI remote controller syncing functionality to check for flight logs located in the "dji.pilot.pad" and "com.dji.industry.pilot" directories.
  
  
• Resolved several issues where images and controls appeared smaller than expected on displays with Windows scaling set above 100%.

See the release notes for a complete list of changes.