Pre-mission Notifications

Hovermap battery critical

The remaining battery capacity is insufficient to start a mission.

Replace or charge the battery.

Hovermap hardware link not connected

The hardware connection between the Hovermap and the robot is not working. The connecting cable may be faulty or unplugged.

Check the cable connection. If the failure persists, try using a different cable.

Please wait until Hovermap is ready before starting a mission

Hovermap's state estimation is not ready. A possible cause is a payload hardware error, but there are other possibilities.

Robot baud rate incompatible

The data rate on the robot connection is set to an unsupported value. Consult the Hovermap user manual and reconfigure the robot.

Use DJI assistant to change the baud rate on the robot.

Robot firmware incompatible

The version of firmware on the robot is unsupported.

Change your firmware version to continue.

Robot platform type not supported

The robot is not supported for autonomous operations.

Change the type of robot connected to continue.

Robot hardware failure

There is a critical hardware error. For example, the system has crashed.

Refer to the user manual provided by the manufacturer or reach out to their customer support team.

Autonomous flight unavailable

Autonomous missions cannot be performed as planning the path between waypoints or detecting potential collisions is currently not possible.

Restart Hovermap and contact Technical Support Services via https://emesent.com/customer-support/

Robot requires restart

The robot requires a restart before pre-mission checks can be completed.

Restart the robot.

License Expired

The mission cannot be started as the license for the current mission type has expired.

Update your software license. Contact licensing@emesent.io

Hovermap storage full

The remaining storage capacity is insufficient to start a mission.

Transfer scans off of Hovermap before starting a new mission. Once transferred, delete the scans from Hovermap to free up storage space.

Remote control not detected

The robot's remote control unit is not connected.

Power on the remote control unit, and ensure it can be used to control the robot.

Cannot arm - not ready

All pre-conditions required to allow arming have not been met. Other pre-mission checks failures may or may not indicate why this is.

Ensure all required pre-mission checks are completed.

Robot's onboard health checks failed

The robot's own onboard health checks have failed

Refer to the user manual provided by the manufacturer or reach out to their customer support team.

Robot’s position not stable

The initial state estimation reports that the robot is not stationary.

If the robot is stationary, the robot will need to be restarted.

Waiting for robot’s position to stabilize

The robot or our own state estimation indicates that the robot is moving. This is likely because of errors induced by a previous landing, or the environment.

If the robot is stationary, the robot will need to be restarted.

Robot communication is not activated

The robot SDK has not been activated, which results in Hovermap being unable to communicate with the robot.

Refer to SDK activation with the DJI M300 and Hovermap for more information on how to activate the SDK.

Connection between Hovermap and user device not detected

There is no link to the Hovermap ground control station.

Ensure ground control station hardware is connected to the Hovermap Wi-Fi or Long Range Radio network.

Robot sensor error

The robot's sensors are providing the data required by Hovermap.

Refer to the user manual provided by the manufacturer or reach out to their customer support team.

Robot internal error

The robot is not ready for some unspecified reason.

Refer to the user manual provided by the manufacturer or reach out to their customer support team.