Previous Releases

New
  • Published on May 18, 2026
  • 34 minute(s) read
  • JS
  • Matthew Toohey
 Prev Next

Commander 2.2.1 & Cortex 4.1.2

Release date: 6 February 2026

Always check the Supported Devices page before updating to ensure compatibility.

Overview

This release resolves a critical issue identified in Cortex 4.1 that may impact Hovermap ST and ST-X systems during autonomous flight operations.

All customers operating on Cortex 4.1+ are strongly advised to update to Cortex 4.1.2 and Commander 2.2.1 immediately.


Critical SLAM stability fix

Resolved an issue that could cause a loss of positioning (SLAM) during autonomous flight.

If SLAM loss occurred, the system would attempt recovery for up to 10 seconds. During this period, the aircraft could drift before initiating an emergency landing if recovery failed.

Observable symptoms included:

  • Aircraft hovering unexpectedly while attempting to stabilize

  • Aircraft drift requiring manual intervention

  • Critical SLAM loss alerts and audible warnings in Commander

This fix restores expected positioning stability and autonomous flight behavior.


Resolved issues

  • Resolved an issue causing incorrect encoder readings that could degrade SLAM stability.

  • Improvements to reduce robot position lag, resulting in more accurate and responsive positional updates during operation.

  • Resolved a power loss recovery failure that prevented scans from starting.

  • Resolved an issue with Onboard Processing.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Cortex 4.1.1

Release date: 20 January 2026
Version: 4.1.1

Always check the Supported Devices page before updating to ensure compatibility.

Overview

This release is a hotfix for Cortex 4.1 that resolves an issue affecting Hovermap ST payloads on Cortex versions 4.0 and later. Hovermap ST-X is not impacted. Hovermap ST users are strongly advised to update to this version.


Resolved issues

  • Resolved an issue on Hovermap ST where, under specific operating conditions, LiDAR rotation could become unstable, resulting in excessive payload vibration and degraded system usability. Scan quality was not impacted by this issue.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Commander 2.2 and Cortex 4.1

Release date: 10 December 2025
Version: 2.2 and 4.1

Always check the Supported Devices page before updating to ensure compatibility.

Overview

This release focuses on usability, visual clarity, and workflow efficiency. Highlights include High Density Visualization, Commander login, measurement tools, autonomy and Exploration refinements, Arm and Takeoff capability, and various workflow improvements.


Major changes

High Density Visualization

High Density Visualization enhances Commander's live point cloud display with higher point density and introduces colour-by-intensity view as the new default. The increased point density, combined with colour by intensity, provides clearer context and helps users distinguish surfaces and materials more easily. This improves situational awareness and confidence during capture, ensuring complete data coverage and supporting better real-time decision-making across autonomous and mapping operations.

Commander user login

Commander now includes Emesent account login, providing a consistent way to access features across the Emesent ecosystem. Commander still works completely offline, with only occasional authentication required. This change improves license visibility, aligns with Aura's concurrent user licensing, and prepares the platform for future enhancements.


Minor changes

  • Exploration improvements. This update refines Exploration mode, improving autonomous behaviour. Hovermap now follows surfaces and boundaries with greater accuracy, enhancing navigation, coverage, and performance.

  • Measurement tools. Commander now supports point-to-point and path measurements, delivering instant in-field insight without Aura processing.

  • Autonomy mission tile connection status. During mission tile selection, Commander now displays connection status and progress to supported robots, improving setup clarity, reducing errors, and improving operator confidence.

  • Arm and takeoff from Commander. Operators can now arm a connected robot and initiate takeoff directly within Commander. This reduces reliance on the system controller, simplifies launch steps, and supports a smoother, more confident setup.


Resolved issues

  • Improved IMU calibration for smoother and more stable flight control.

  • Enhanced upgrade robustness for greater reliability during software updates.

  • Improved trajectory generation for smoother and more natural flight paths.

  • Increased reliability of LiDAR connections during startup.

  • Improved USB data offloads for more reliable file handling.

  • Enhanced LiDAR synchronisation for consistent data alignment.

  • Improved obstacle detection to prevent false readings from small objects.

  • Reduced Autonomy mission startup times for faster deployment.

  • Reduced detection time when connecting to a robot.

  • Fixed an issue where the point cloud was not displayed after completing pre-checks.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Cortex 4.0.3

Release date: 25 August 2025
Version: 4.0.3

Always check the Supported Devices page before updating to ensure compatibility.

Overview

This release introduces a Cortex recovery mechanism for Hovermap, enhancing reliability and reducing downtime by enabling self-service recovery of devices that fail to start due to file system issues or interrupted upgrades. In such cases, the fault is indicated by continuous red flashing on the status LEDs during start-up.


Major changes

Cortex recovery mechanism

  • The recovery mechanism is available only after upgrading Hovermap to Cortex 4.0.3 or later.

  • Enables recovery from boot failures caused by file system issues or failed Cortex upgrades, reducing downtime.

  • Generates a feedback log to guide users through resolving issues encountered during recovery.

  • Requires Cortex recovery files provided by Emesent Client Support.

If you encounter a continuous red flashing light error during start-up, contact our Client Support team via the Technical Support form.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Cortex 4.0.2

Release date: 22 July 2025
Version: 4.0.2

Always check the Supported Devices page before updating to ensure compatibility with your hardware.

Overview

This minor update to the 4.0 release includes expanded platform support and a small improvement to the organization of onboard processing results. Read about the 4.0 release for details on the major features introduced, including Autonomy Exploration Mode and Onboard Processing.


Major changes

Support for NDAA/Blue variants of Freefly Astro and Astro Max

Hovermap is now compatible with the Freefly Astro Blue and Astro Max Blue UAVs, enabling seamless operation on NDAA-compliant platforms. This integration expands deployment options for users with regulatory or operational constraints, supporting rugged and efficient aerial mapping in defense, critical infrastructure, and other sensitive environments.

Using Hovermap with Blue variants of Astro / Astro Max requires additional configuration.


Minor changes

  • Onboard-processed scans are now saved in the OnboardProcessingResults folder within the offloaded scan directory, making it easier to locate and manage processed data.

  • Added support for extended landing gear on the Freefly Astro/Astro Max to provide Hovermap with additional clearance during landing.


Resolved issues

  • Resolved an issue where an IP conflict occurred when using the Spot external camera with Hovermap. Both devices can now connect to Spot without conflict.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Cortex 4.0.1

Release date: 9 June 2025
Version: 4.0.1

Always check the Supported Devices page before updating to ensure compatibility with your hardware.

Overview

This minor update improves system stability and workflow efficiency with enhancements to start-up behaviour, data handling, flight performance, and scan file management.

Read about the 4.0 release for details on the major features introduced, including Autonomy Exploration Mode and Onboard Processing.


Resolved issues

  • Addressed a start-up issue that could prevent the payload from fully booting, resulting in a red flashing status indicator.

  • Resolved a data handling issue to improve the reliability of scan offloading and reduce the potential for corruption.

  • Resolved an issue that could prevent Explore missions from executing successfully in certain conditions.

  • Resolved an issue where Hovermap could indicate readiness prematurely, helping ensure more reliable scan capture.

  • Fixed a flight control issue that caused speed pulsing during vertical drone movement.

  • Fixed an issue where scan files couldn't be deleted via the WebUI after Wi‑Fi transfer until the WebUI was refreshed.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Commander 2.1 & Cortex 4.0

Release date: 24 April 2025
Version: Commander 2.1, Cortex 4.0

Always check the Supported Devices page before updating to ensure compatibility with your hardware.

Overview

This software release introduces Emesent's stope mapping solution, which combines one of our biggest advancements in autonomous navigation with new options for onboard scan processing to radically simplify and accelerate stope mapping reconciliation.


Major changes

Autonomy Exploration Mode

Hovermap can now explore a defined area without the need for manually placed waypoints. This new feature streamlines mission setup with a simple tap-and-drag gesture to define 3D exploration zones, reducing planning time and simplifying operation.

Onboard Processing

Hovermap can now process scans onboard and display a denser, more informative point cloud directly within Commander, enabling rapid in-field assessment. This goes beyond Commander's decimated live point cloud, offering greater detail to support scan quality checks and on-site decision-making. In addition, by removing the need to return to Aura for processing*, onboard processing reduces delays and provides faster access to actionable insights from captured data.

Scans processed onboard Hovermap will have different accuracy than scans processed in Aura. To understand the difference, please refer to our Aura vs Hovermap Onboard Processing Accuracy Comparison.

Tighter autonomy navigation

Thanks to improvements in Hovermap's autonomy system, the minimum clearance for autonomous navigation has been reduced from 3.0 metres to 2.4* metres. This allows Hovermap to operate more effectively in tighter spaces, such as narrow drives or stope entries, and reduces the need to switch to Pilot Assist mode.

*Minimum clearance distance is dependent on the platform in use.


Minor changes

  • External Control Mode verification. To help prevent incidents with drone aircraft at take-off, users will be alerted if they're conducting the workflow for an autonomous mission without the control switch set to the Hovermap flight mode.


Resolved issues

  • None.


Known issues and limitations

Please refer to the Known Issues and Limitations page for the most current information.


Next steps





Commander 2.0 & Cortex 3.4

Release date: 10 February 2025
Version: 2.0 / 3.4

Always check the Supported Devices page before updating to ensure compatibility.

Overview

Commander 1.5.1 is the latest supported version for LHD. There is no LHD compatible version of Commander 2.0, and it is not currently compatible with Cortex 3.4.0.

LHD users should continue using Cortex 3.3.3 with Commander 1.5.1 for LHD.

Commander 1.5.2 and Cortex 3.3.3 are the latest compatible versions for the M210 and other DJI platforms running firmware version 4 or earlier. Users on these systems should continue using Cortex 3.3.3 and Commander 1.5.2, or where possible, upgrade to DJI firmware V5.x.x.x or later.


Major changes

  • Commander backend architecture has been redesigned to improve point cloud page performance and Wi-Fi connection stability.

  • Emesent's Hovermap ST and ST-X now support the Freefly Astro Max drone, in addition to existing Hovermap ST-X support for the Freefly Astro drone.

  • Astro Max motors are more powerful than the Astro's, improving the Astro Max's ability to navigate confined spaces and giving it the capacity to carry a 360-degree camera or GoPro alongside the Hovermap for image colorization.


Minor changes

  • Commander will now check the performance of a Samsung Galaxy Tab Active Pro tablet it's running on and notify the user if an upgrade is recommended.

  • Cortex tuning for autonomy flights has been made more responsive with course self-correction.

  • To minimise the chance that an automatic change in the radio frequency of a DJI drone remote controller would overlap and interfere with Hovermap's Wi-Fi signal, Commander now automatically sets the DJI's frequency to static values (shown in the Commander user manual section 1.4 Connecting to Hovermap). This setting can be disabled in Commander's settings, which will reset to DJI's default values.


Resolved issues

  • Vehicle RTK Path history is now displayed by default after being temporarily turned off by default due to a performance-related issue.


Known issues and limitations

Known issues

  • When using Freefly Astro or Astro Max, if you enable the FPV feed via Commander settings while Auterion is being run, it may result in FPV feed stuttering. For that reason, when Commander detects a Freefly Astro or Astro Max, the FPV feed is hidden by default and the point cloud is displayed in the Main View. The FPV feed can be manually enabled in Commander settings when Auterion is closed.

  • Changes to the performance of the Return to Home (RTH) function in Cortex may result in Hovermap not taking the most direct route home and this failsafe may therefore trigger earlier than expected. This issue occurs predominantly in open spaces, but can be mitigated by cancelling the RTH action and landing your aircraft when appropriate.

Known limitations

  • The 'Generate preview points clouds' function on the Web UI has been deactivated for the Cortex 3.4 release.


Supported devices

Platforms

Platform

Supported Robot Firmware

Supported Cortex Version

Supported Commander Version

Freefly Astro

1.4.6 and above

3.4.0

2.0.0

Freefly Astro Max

1.9.1

3.4.0

2.0.0

DJI M350

09.01.01.02 and above

3.4.0

2.0.0

DJI M300

SDK V5 and above

3.4.0

2.0.0

Boston Dynamics Spot

3.3.0 and above

3.4.0

2.0.0

DJI M300

SDK V4 and below

3.3.3

1.5.2

DJI M210

SDK V4 and below

3.3.3

1.5.2

Emesent LHD

N/A

3.3.3

1.5.2 LHD

Tablets

Commander can be used on any Android smartphone or tablet that meets the required specifications. While we recommend a number of tested devices, high-end models with similar performance should also work reliably. Performance may vary with untested devices.

The following Android devices meet the minimum or recommended specifications for running Commander:

Device

Minimum Version

Commander Compatibility

Freefly Pilot Pro Controller

Android 13

✅ Recommended Device

DJI RC Plus Remote Controller

Android 10

✅ Recommended Device

Samsung Galaxy Tab S9 5G

Android 13

✅ Recommended Device

Samsung Galaxy Tab Active4 Pro 5G

Android 13

⚠️ Minimum Supported Device

Samsung Galaxy Tab Active5

Android 14

⚠️ Minimum Supported Device

Samsung Galaxy S23

Android 13

⚠️ Minimum Supported Device

Tab Active Pro

Android 10

❌ Not Supported

Samsung Galaxy Tab Active3

Android 13

❌ Not Supported

We recommend using one of the recommended listed devices, as they have been thoroughly tested to ensure smooth and reliable performance.





Emesent Commander 1.5.2

Resolved issues

  • Vehicle RTK performance improvements

    • Enhanced RTK performance for improved positioning accuracy and stability across various operational conditions.

  • Vehicle RTK Path history display

    • RTK path history is now disabled by default for vehicles, helping to declutter the interface and improve focus on real-time data.





Emesent Commander 1.5.1

This update removes the restrictions for Freefly Astro users and is compatible with all supported platforms.

Resolved issues

  • Fixed the issue of frequent communication dropouts between Emesent Commander and Emesent Cortex despite stable Wi-Fi connections on Android devices due to outdated GRPC dependencies. This upgrade also improves stability during extended sessions.

  • Fixed an issue where the Hovermap failed pre-scan checks when using Backpack RTK and Vehicle RTK setups, leading to errors and inability to initiate scans. Corrections were made to the mission logic to prevent autonomy missions from triggering during RTK mapping operations.

  • Fixed an issue where the battery status is incorrectly displayed as 100% during Vehicle RTK or Backpack RTK missions even though battery information is unavailable from these RTK units.

  • When Freefly Astro is detected, the FPV feed is now hidden by default and the point cloud is displayed in the Main View. The FPV feed can be manually enabled via the Application settings when Auterion is closed.

  • Emesent Commander now remains active even without user interaction to ensure the point cloud is populated in the Main View.

  • Reduced unnecessary calls during mapping and RTK missions to improve optimization. This update helps lower the load on less powerful tablets, enhancing performance during longer missions. Note that while this improvement helps delay performance issues, it may not completely eliminate them on lower-spec devices.


Known issues and limitations

  • When using Freefly Astro, enabling the FPV feed via the Application Settings while Auterion is being run may result in FPV feed stuttering.

  • When a mission has started, and the phone or tablet is locked, Emesent Commander may enter sleep mode, resulting in incomplete data and gaps in the point cloud visualization. While the Hovermap will continue to capture data, it may not be rendered in the app. To ensure you can visualize all captured data, do not lock your device while the mission is in progress.

  • When initiating a scan offload via the Web UI accessed through the application, users may encounter a situation where the download begins but subsequently fails. To mitigate this issue, it is recommended to use a web browser to access the Web UI and download the scan from there.

  • After upgrading the Hovermap and connecting it to a DJI M210, Emesent Commander displays a "Not available for connected platform" notification. However, the connection is established correctly following a restart of the app, the Hovermap, and the remote controller.

  • The documentation for the RC Plus controller indicates the possibility of calibration (independent of the drone), as outlined here: https://dl.djicdn.com/downloads/DJI_RC_Plus/20230518UM/DJI_RC_Plus_User_Manual_EN_v2.0.pdf
    DJI has not enabled integrators to add this feature to their apps and will need to be completed in the DJI native app.





Emesent Commander 1.5

Attention Freefly Astro users: This update is NOT RECOMMENDED for your device. We will soon release a version compatible with Astro, which includes the same updates as this version. If you are unsure about which update applies to you, please contact Emesent Technical Support Services at customer-success@emesent.io.

Major changes

RTK (Real-Time Kinematics) Status

In this release, RTK status information is now accessible in Emesent Commander, allowing users to easily monitor key details when using Vehicle RTK or Backpack RTK, including:

  • RTK Status (Fixed, Float, Single, No GPS, Offline)

  • number of satellites in use by the GNSS receiver

  • the GNSS receiver's reported location and precision

With RTK information directly available in Emesent Commander, users can stay updated without switching to the GNSS receiver's native application to check for information.

Mission Report

Emesent Commander now includes a Mission Report feature that allows for annotating and reviewing scans directly within the app before offloading data. Users can access key mission attributes on the Mission Report page, gaining valuable insights into mission performance. Detailed notes can also be added to the selected scan, enhancing documentation for thorough analysis and reporting.

Robot path saved even during loss of connection

With this update, Hovermap automatically saves the robot's path even if the connection is lost. Users can view the complete path in Emesent Commander, ensuring that no segments are missing in the path data due to a temporary loss of connectivity.

Multi-language support

Multi-language Support, previously released in beta, is now fully featured. With this update, users can now enjoy enhanced functionality and stability.


Known issues and limitations

  • When initiating a scan offload via the Web UI accessed through the application, users may encounter a situation where the download begins but subsequently fails. To mitigate this issue, it is recommended to use a web browser to access the Web UI and download the scan from there.

  • After upgrading the Hovermap and connecting it to a DJI M210, Emesent Commander displays a "Not available for connected platform" notification. However, the connection is established correctly following a restart of the app, the Hovermap, and the remote controller.

  • The documentation for the RC Plus controller indicates the possibility of calibration (independent of the drone), as outlined here: https://dl.djicdn.com/downloads/DJI_RC_Plus/20230518UM/DJI_RC_Plus_User_Manual_EN_v2.0.pdf
    DJI has not enabled integrators to add this feature to their apps and will need to be completed in the DJI native app.





Emesent Commander 1.4

Major changes

Multi-language support (beta release)

This feature is in Beta and may undergo further refinement. For questions and feedback, contact Emesent Technical Support Services at customer-success@emesent.io.

The Emesent Commander offers comprehensive multilingual support for nine major markets, enhancing accessibility and user experience for our global audience. This update introduces localized language options to cater to users in key regions, ensuring a seamless and comfortable experience in their preferred language.

Supported languages:

  • English (existing language)

  • Spanish

  • French

  • German

  • Simplified Chinese

  • Japanese

  • Italian

  • Russian

  • Portuguese (Brazil)

Imperial measurement system support

The Emesent Commander now supports the imperial system alongside the metric system. This enhancement gives users the flexibility to select their preferred unit of measurement directly within the application settings. Easily switch between meters and feet with a simple toggle for optimal usability across different regions and contexts.

Map Widget integration (DJI only)

The Emesent Commander app has been seamlessly integrated with the Map Widget, changing how users navigate and visualize scanning operations. This integration allows users to access high-quality mapping data and powerful visualization tools.

The Map Widget provides real-time mapping capabilities, for DJI users when the remote controller is connected. This enables users to monitor drone telemetry data overlaid on a map, ensuring situational awareness even without a reliable connection. This capability is essential, particularly in Pilot Assist and Autonomous missions, where precision and operational insight are critical. In addition, the Overlay feature facilitates seamless transitions between the map, first-person view (FPV), and point cloud view, ensuring a comprehensive understanding of the operational environment.





Emesent Commander 1.3

Major changes

Android smartphone support

The Emesent Commander app is now compatible with Android smartphones. When launched, the app automatically detects the device type being used. On a smartphone, the app presents a streamlined interface that has been optimized for smaller screens. This interface allows you to perform scanning missions in Mapping mode. In addition, the smartphone version also allows you to start and stop scans, turn on Observer Mode, access the Web UI, download logs, and configure application settings.


Minor changes

  • An important update has been introduced to enhance user safety during Mapping mode missions on compatible robots. Previously, users could start Mapping mode missions without being aware that Hovermap's Shield protection and Assisted Flight were not enabled. This is often not desirable, particularly in GPS-denied environments.

    With this update, users will now receive a confirmation message when they initiate a Mapping mode mission on a compatible platform. This aims to ensure that users only choose a Mapping mode mission when they do not require Shield protection and Assisted Flight. By selecting Mapping mode, users are aware that they won't have the assistance of Shield protection, which could expose the drone to risks in GPS-denied environments. They can either proceed without Shield or cancel and plan an Autonomous mode mission to provide additional protection against obstacles.

  • A new Network Settings window has been added to the system for managing and configuring network connections. The screen displays the existing network connection, which can be changed through the Network Settings screen (accessed via the Menu Options) or the Connectivity page of the Mission Workflow. The list of available or inactive networks displays any previous connections based on the availability of the Wi-Fi network.

  • Users can now view the task ID when setting tasks for a mission. This enhancement improves mission tracking and management by providing users with a clear indication of tasks in the Task Manager.

  • When performing a mission in Autonomous mode, once the scan has started and the robot is armed, the Shield Indicator automatically displays while taking off to ensure any obstacles can be seen. During arming and take-off, audio is not played if obstacles are reported below the robot.

  • The Follow Robot function, which allows you to follow the Hovermap as you move through the 3D View is enabled by default.

  • The display notification for an active failsafe has been improved. When a failsafe is triggered, it will be displayed as a notification in the Active Failsafe area beside the Notification button. All other notifications (if any) are shown below the failsafe in order of severity. Once the failsafe has been completed, it will be removed from the Active Failsafe area and notifications are displayed as per normal operation.





Emesent Commander 1.2

Major changes

Freefly Astro drone support

This release introduces support for the Freefly Astro drones utilizing the Hovermap as a payload. In addition to the drone support, Emesent Commander can be installed on the Freefly Pilot Pro tablet via an external USB storage device or the Freefly Updater app.


Minor changes

  • Attempting to start the scan with unsaved changes to the scan name on the Scan Setup page of the Mission Workflow will display a message prompt confirming whether you want to save the changes before continuing.

  • The RC Mode selection is hidden from the Pre-mission settings page of the Mission Workflow and the Mission Controls in the Main View when connected to Astro.

  • When the Shield settings panel is open in the Main View and Emesent Commander loses connection with the Hovermap, a message at the top of the panel shows that the Hovermap is disconnected and you need to re-establish the connection to continue.





Emesent Commander 1.1

Major changes

Observer Mode

Observer Mode enables viewing of the ongoing mission in real-time on multiple Android devices simultaneously, ensuring that stakeholders, supervisors, or team members can monitor the progress from different locations or using different devices. While observers can view the mission progress, control over mission settings or robot operation is disabled to ensure that those monitoring cannot inadvertently interfere with the ongoing operation.

Integrated Compass Calibration in Mission Workflow

Compass calibration can be done directly through Emesent Commander's Mission Workflow, ensuring the compass is accurately calibrated before takeoff, without the need to navigate through complex remote controller menus. Emesent Commander provides a user-friendly, step-by-step guide of the calibration process with clear instructions and visual cues.

Enhanced experience for DJI Matrice 350 owners with RC Plus controller

For DJI Matrice M350 drone owners, the new RC Plus controller features an optimized Emesent Commander user interface. The menu items and fonts are tailored to seamlessly adapt to the RC Plus controller's 7-inch screen, ensuring effortless navigation through the app's extensive functions and settings.

Spot: remote start and stop operation

This feature allows for the remote start and stop operation of your Spot robot (Boston Dynamics). This functionality, which can be accessed via the robot's controller or the Scout desktop software, enables you to perform pre-planned autonomous Autowalk missions.


Minor changes

  • The Point Coloring section in the Display Settings panel now features additional color ranges.





Emesent Commander 1.0

Release date: 29 September 2023

The Hovermap app is no longer supported and will not work with the latest firmware.

Major changes

Sleek redesigned user interface (UI)

The application is given a fresh new look that features a modern and intuitive user interface. The sleeker and more visually appealing design enhances usability and makes navigating within the application a breeze. The improved UI provides a consistent and seamless experience across all sections of the application.

Streamlined user workflow

Significant improvements have been made to the user workflow, resulting in a more intuitive and efficient experience. Whether you are planning a Mapping mission or an Autonomy mission, the updated user flow guarantees a seamless experience from start to finish.

Enhanced performance and speed

A lot of effort has been made to ensure to enhance performance and speed of the application, allowing for quick and efficient completion of tasks. Users can expect significantly reduced load times, smoother screen transitions, and an overall improvement in the responsiveness of the application.

Advanced navigation

As an added convenience, Commander's advanced navigation feature automatically determines the type of environment it is in and intelligently selects the most appropriate navigation method. This takes the guesswork out, enabling the user to confidently perform mission objectives.

Enhanced visualization

3D rendering improvements such as Eye Dome Lighting (EDL), rounded points and point size attenuation have been added to enhance point cloud quality, clarity and depth perception.

Personalized display settings

The application offers fine-tuning and customization capabilities of the 3D display and navigation. Users can tailor the display parameters to their preferences to get a better visualization of the live point cloud.

Light Mode

The highly requested Light Mode feature greatly improves the application's visibility in well-lit environments. Changing the application's color profile ensures optimal contrast and readability, reducing eye strain, and enhancing user experience.

Improved notifications

The revamped notification display keeps the user informed of critical updates. These notifications help users determine the best course of action for their mission.


Known issues and limitations

  • Users may experience difficulties in receiving DJI data within the app. In certain instances, it may be necessary to unplug and re-connect the USB cable in order to establish a consistent flow of data.

  • The DJI Compass Calibration feature is not supported in this release.

  • It is encouraged to turn off the auto reconnect option in the Android Wi-Fi Manager for office/other Wi-Fi networks that are in range during flights. This is done so that when you lose connection to your Hovermap network, you can automatically reconnect when it comes back in range.





Emesent Cortex 3.3.3

This update removes the restrictions for Freefly Astro users and is compatible with all supported platforms.

Resolved issues

  • Timing synchronization fix for long-scan operations

    • Resolved issues with Double PPS (Pulse Per Second) and timing synchronization failures associated with long-scan operations, ensuring greater data accuracy and reliability during extended scans.

    • Trimble R10/R12 and R12i Support (Available with Aura 1.8 and upcoming hardware support)

  • Leica GNSS Support (Available with an upcoming Aura release and upcoming hardware support)

  • Firmware downgrade prevention

    • Prevented downgrades to firmware version 3.2.3 to maintain system integrity and avoid compatibility issues.





Emesent Cortex 3.3.2

Attention Freefly Astro users: This update is NOT RECOMMENDED for your device. We will soon release a version compatible with Astro, which includes the same updates as this version. If you are unsure about which update applies to you, contact Emesent Technical Support Services at customer-success@emesent.io.

Resolved issues

  • Resolved an issue where scans, in rare cases, could not be downloaded from the Hovermap when offloading via USB.


Known issues and limitations

  • Changes to the Return to Home (RTH) performance may result in Hovermap not taking the most direct route home and this failsafe may therefore trigger earlier than expected. This issue occurs predominantly in open spaces but can be mitigated by cancelling the RTH action and landing your aircraft when appropriate.





Emesent Cortex 3.3.1

Attention Freefly Astro users: This update is NOT RECOMMENDED for your device. We will soon release a version compatible with Astro, which includes the same updates as this version. If you are unsure about which update applies to you, contact Emesent Technical Support Services at customer-success@emesent.io.

Resolved issues

  • Resolved an issue affecting some Hovermap ST-X units where time synchronization errors occurred during long scans (around 26 minutes or more) in challenging thermal conditions, causing RTK georeferencing to fail.





Emesent Cortex 3.3

Attention Freefly Astro users: This update is NOT RECOMMENDED for your device. We will soon release a version compatible with Astro, which includes the same updates as this version. If you are unsure about which update applies to you, contact Emesent Technical Support Services at customer-success@emesent.io.

Major changes

Fast data offload

Improvements to the handling and compression of scan files now result in significantly reduced offload times, whether to USB devices or over Wi-Fi.


Minor changes

RTK Status in Emesent Commander

In this release, RTK status information is now accessible in Emesent Commander, allowing users to easily monitor key details when using Vehicle RTK or Backpack RTK, including:

  • RTK Status (Fixed, Float, Single, No GPS, Offline)

  • number of satellites in use by the GNSS receiver

  • the GNSS receiver's reported location and precision

With RTK information directly available in Emesent Commander, users can stay updated without switching to the GNSS receiver's native application to check for information. In addition, this release features enhanced support for Emlid RS2/RS2+/RS3 receivers.

Improved Backpanel USB Ethernet connectivity

For users with Wi-Fi turned off and connecting via the back panel USB Ethernet, the connection now features a built-in DHCP server. While the traditional method of connecting via the back panel USB Ethernet remains functional, this latest update streamlines the connection process by eliminating the need for static network configuration. Simply connect your machine to the Ethernet port and navigate to hover.map or 192.168.3.115 to access the network.

Dynamic SSID renaming for Long Range Radio (LRR)

When connected to Hovermap, the Long Range Radio's SSID is dynamically renamed to match the Hovermap, ensuring that the SSID always reflects the Hovermap it is currently paired with.

Previously, the LRR's SSID was hard-coded with the Hovermap serial number during production. This meant that the SSID remained regardless of the Hovermap it was connected to. With this update, when a Hovermap is booted up with an LRR attached, the Hovermap checks the LRR's SSID and if different, automatically renames to reflect the Hovermap's serial number ensuring clear identification and alignment between the devices.

By simplifying identification in multi-drone environments, users can interchange LRR's between Hovermap units without confusion caused by mismatched SSIDs.

Hovermap Wi-Fi password change support

Users can now change the Hovermap Wi-Fi password directly through the Web UI. In previous versions, the password was preset during production and not customizable. In this release, users have the flexibility to set and modify the password according to their security preferences and operational needs.

Hovermap Wi-Fi disable confirmation

To prevent unintentional deactivation of the Hovermap Wi-Fi, a confirmation checkbox has been implemented in the Web UI. This change prevents scenarios where users might inadvertently disable Wi-Fi without an alternative connection, potentially causing operational disruptions or difficulties in re-establishing connectivity.

Automatic robotic platform detection enhancement

Enhancements were made to enable the automatic detection of Backpack RTK and Vehicle RTK data in Emesent Aura to allow for a more seamless user experience.


Resolved issues

  • Fixed an issue that occasionally prevents transitioning from Autonomous to Pilot Assist mode.

  • Fixed an issue that could prevent the Hovermap from stopping a scan during a handheld mission.





Emesent Cortex 3.2.3

Resolved issues

  • Addressed an issue with yaw control stuttering during Pilot Assist missions when Hovermap detects that it has drifted from its desired position. This is now limited to scenarios where the aircraft is "locked in" by Shield constraints. In such instances, pilot-initiated yaw control will temporarily pause while Hovermap readjusts to its designated position to ensure stable flight.





Emesent Cortex 3.2.2

This is a critical update for all Emesent Cortex version 3.1 and above users.

The Hovermap Software has been renamed as Emesent Cortex. All future software releases will be under this new name.

Minor changes

  • Minor change to support the Emlid RS2/2+ RTK GNSS Receiver for Vehicle RTK.

  • Minor change to support a Freefly Astro firmware update (1.5.18).

  • Improvements to reduce Emesent Cortex memory bandwidth usage.

  • Reduced the time to enable the full Shield from 15 seconds to 7 seconds in Pilot Assist (Plus) missions.


Resolved issues

  • Fixed an issue in Pilot Assist (Plus) mode where an aircraft could slowly drift and crash if locked in by obstacles for a long period.

  • Fixed an issue where the Hovermap would issue multiple "Hovermap Ready" alerts after passing pre-mission checks.

  • Greatly improved an issue in Pilot Assist (Plus) flights where very small obstacles may be reported, even when none are visible. This issue is very rarely observed now.





Cortex 3.2.1

This is a critical update for all Cortex version 3.1 users.

Resolved issues

  • Fixed an issue that may cause loss of perception for short periods during flight, resulting in the inability to detect obstacles and potentially leading to a collision during a Pilot Assist flight.


Known issues and limitations

  • An issue exists with Pilot Assist flights where it may report the presence of very small obstacles, such as single points, even when there are no visible obstacles. Performing a clearing turn does not eliminate these false obstacle signals, and they could trigger a dust failsafe if the user switches to Autonomous mode.

  • An issue exists that occasionally prevents transitioning from Autonomous to Pilot Assist mode and then landing, forcing the user to wait for the battery failsafe to trigger and land the drone automatically.

  • Changes to the Return to Home (RTH) performance may result in Hovermap not taking the most direct route home and this failsafe may therefore trigger earlier than expected. This issue occurs predominantly in open spaces but can be mitigated by cancelling the RTH action and landing your aircraft when appropriate (e.g. when the remaining battery passes 20%).





Cortex 3.2

Major changes

Freefly Astro drone support

This update introduces support for Freefly Astro drones utilizing the Hovermap as a payload.


Resolved issues

  • Enhanced the USB size detection for data offload procedure.

  • Fixed a bug that, in rare cases, causes the DJI M350 to fail to disarm on auto-landing.

  • Fixed a bug that would occasionally result in scans being unable to be processed.





Cortex 3.1

Major changes

M350 drone support

This update introduces support for DJI M350 drones utilizing the Hovermap as a DJI payload. Note the following key changes:

  • The activation process for the Hovermap payload has been eliminated.

  • To configure the Hovermap on an M350 or M300, adjusting the baud rate within the OSDK settings is required. Other components remain unaffected by this adjustment.

Auto power-on

A new Auto power-on option has been introduced in the Web UI to facilitate automatic activation. When enabled, the Hovermap will boot automatically as soon as power is supplied. This setting persists until manually disabled.

Enhanced pose estimation for improved safety

Drone safety has been improved with significant upgrades to the accuracy and reliability of the drone position estimation. This ensures safer flights and results in smoother flight experiences.


Minor changes

  • Data offload

    • Improved support for Sandisk USB Extreme Pro and USB 3.2 Gen 1x1 (USB 3.1 Gen 1 or USB 3.0)

  • Perception system improvement

    • The perception safety system has been improved to allow more robust flying around obstacles.

  • External device support

    • Added ability to connect to an external RTK device for future integrations.

  • Backpanel LED

    • LEDs immediately respond to button presses and maintain for at least 7 seconds or until released, whichever comes first.

    • USB data offloads on a Hovermap ST will have a wiping blue bar instead of a light blue breathing pattern.

  • Failsafes

    • A new logic for the Lidar Data Integrity failsafe has been introduced, including an additional warning. For more information, refer to the Hovermap Operational Failsafes and Hovermap Notifications sections in the Hovermap User Manual.

  • Web UI

    • USB logs now present information in a more structured or clearer format.

    • GPS Status indicator is present when a supported GPS or RTK module is attached.


Resolved issues

  • Fixed an issue where starting a scan with battery level under the low battery threshold caused the battery failsafes to not trigger.





Cortex 3.0.4

This is a critical update for Hovermap 100 users.

Resolved issues

  • Fixed an issue where the IMU configuration occasionally failed to initialize correctly due to a timing issue in the boot sequence. This ensures consistent and proper IMU configuration upon system startup.

  • Fixed an issue preventing the safe upgrade of very old Cortex versions to 3.0 on Hovermap 100.





Cortex 3.0.3

Resolved issues

  • Fixed the startup process for mission management, reducing CPU load during operation.





Cortex 3.0.0

Major changes

Advanced Navigation (State Estimation)

Commander automatically determines the environment it is in and automatically selects the most appropriate navigation source (SLAM, GPS, INS), removing the guesswork so you can confidently perform mission objectives.

  • SLAM is always used as the primary navigation source. In the event of any issues with SLAM, the drone will Return to Home.

  • In a GPS environment, the system will drop to GPS if SLAM is lost. If GPS is subsequently lost, then it will drop into drone INS.

Improved perception

A new perception pipeline (with increased precision, accuracy, and range) has been introduced to fix known issues with the previous system.

  • The drone can now fly up to 1.5 meters further away from obstacles, whenever the environment allows it. This improvement has helped the robot reach its target speed of 2 meters per second more frequently. Additionally, there's less interference from LiDAR occlusion and shadowing, resulting in better mapping coverage.

  • When running a mission in Pilot Assist mode, the obstacle proximity indicators for Hovermap's collision avoidance system (Shield) have been improved to ensure a safe distance is kept from even the most hard-to-detect obstacles for safer flying.

  • The robot can no longer land while rotating when Shield is enabled.

Dust filtering

An advanced algorithm has been introduced to effectively eliminate noise and artifacts, caused by dust particles, from LiDAR data captured on a Hovermap ST-X while preserving the original surrounding data.

  • Allows Hovermap ST-X to operate better in dusty environments.

  • Prevents misrepresentation of objects or terrain due to dust interference.

  • Ensures the Hovermap ST-X can continue data collection without the need for frequent interruptions.

Improved notifications

The usability of the app notifications for the built-in failsafes including the pre-flight checks has been improved.

  • Critical Errors and Warning notifications: Displayed at the top of the screen, including solutions so users know how to respond.

  • Caution notifications: Only shown in the Notification panel to avoid overwhelming the user with too much information.

  • Status and Success notifications: Notifies users of successful actions and state changes that do not need interaction. These notifications clear automatically after 10 seconds.

Notifications are color-coded according to severity. For more information, refer to the Hovermap Operational Failsafes and Hovermap Notifications sections in the Hovermap User Manual.

Improved LiDAR lockout handling

Environmental factors such as the presence of fog or gas can cause a LiDAR point drop, leading to Hovermap's inability to perceive its surroundings. In the past, a point drop would result in a LiDAR lockout, which required users to contact Emesent to unlock their system. In this version, Hovermap will no longer lock the LiDAR. The system will simply return home when a LiDAR point drop occurs. After experiencing a LiDAR point drop and successfully returning home, Hovermap will be ready for continued use.

To minimize the chance of a point drop, Emesent recommends using anti-fog spray and allowing some time for Hovermap to adjust to the ambient temperature of its surroundings.

Networking

  • Hovermap ST users can now disable Wi-Fi on their payloads from the Web UI.

  • Users can configure the network address assigned to the Ethernet on the Fischer connector via the Web UI.

  • Connecting a USB-Ethernet adaptor to the back panel USB now provides a rescue interface:

    • Hovermap 100: 192.168.2.115/24

    • Hovermap ST: 192.168.3.115/24

  • Network hostnames are now based on device serial numbers.


Minor changes

  • DJI M300 low battery mark is set globally at 20%.

  • The take off height is set at 1m.

  • The Direct RTH feature has been removed.

  • The Start button on the Web UI has been changed to Start Mapping Mission, which launches a mission in Mapping mode.

  • RTK PPS signals logging has been added to the public bag files.

  • Solid red lights indicate a microcontroller firmware is being upgraded.


Known issues and limitations

  • When an RTH (Return to Home) Failsafe is already in progress and another RTH Failsafe is activated, a brief and noticeable interruption occurs in the RTH sequence.

  • There is a delay (less than 10 seconds) in the time it takes for the user to take off again after landing. During the period when the state estimation is stabilizing, the system will indicate a "Degraded" state to ensure that take-off is not allowed.