Skip to main content
Skip table of contents

Leica FlightPro 6.2.5 Release Notes

Release Systems

  • Leica CityMapper-2

  • Leica TerrainMapper-2

Main features

  • No new features were added in Leica FlightPro 6.2.5 for all systems

Main fixes

  • 3D views: Fixed issue in the 3D experimental views

  • Flight Execution: Fixed that prevented system from leaving flight execution mode shortly after entering flight execution mode

  • LiDAR Unit: Improved T0 detection

  • LiDAR Unit: Fixed issue that caused incorrect LiDAR Unit configuration

  • Maps: It is now easier to delete second map file

  • MFC Cameras: Fixed error that prevented FlightPro from entering Flight Execution mode

  • UI: Removed extra warning message when no DTM files were found

Main Changes

  • SPAN/GNSS: Improved the robustness of the real-time solution to prevent “PAV is ignoring invalid heading information. Stabilisation is not working correctly. Recorded data might be useless” error messages.

Known Issues

  • MM30: Formatting of MM30 Mass Memory 7680GB M2 with FlightPro takes nearly an hour on some systems with older software

Upgrade Notes

  • Recommended upgrade steps are:

    • Leica FlightPro 6.2.4

  • Customers with Leica FlightPro 5.4.8 or 5.4.10 must update to Leica FlightPro 5.5.1 first.

  • Customers with Leica FlightPro 5.5.1 must update to Leica FlightPro 6.0.3 first.

  • Customers with Leica FlightPro 6.0.3 must update to Leica FlightPro 6.1.2 first.

  • Customers with Leica FlightPro 6.1.2 must update to Leica FlightPro 6.2.4 first.

Workflow requirements

Software

Version

Leica MissionPro

  • 12.8.1 or greater is mandatory for CityMapper-2

  • 12.15.0 or greater is recommended

NovAtel Inertial Explorer

  • 8.80.2305 or greater is mandatory

  • 9.00.0731 or greater is mandatory with All selected for Selected GNSS systems.

  • 9.00.0731 or greater is recommended

HxMap

  • 4.4.0 or greater is mandatory

  • 4.7.0 or greater is recommended

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.