Download this article here.
Notifications provide situational information regarding the status of your mission, including the Hovermap and your robot. In addition, a notification may also include the recommended operator action.
Notification Types
There are three different types of notifications.
-
Pre-mission Notifications: Shown in the mission workflow only when starting a scan, during pre-checks. They will not occur once pre-checks have been passed.
-
Notifications During Mission: These can occur at any point after a scan has started. If failures are associated with an active failsafe, the system will report it is running degraded.
-
DJI Notifications (only when connected to a remote control)
Notification Severities
Error Notifications
When a problem is encountered, notifications appear as a popup at the top of the application. In addition, you can tap the Notification button on the main view to see the list of all active critical errors, warnings, and status notifications. The list is ordered by severity and reported time (the highest severity with the most recently reported time is displayed at the top).
Notification | Description |
Critical | Indicated by a red icon and accompanied by three successive “beep” sounds. This notification indicates that the problem requires immediate attention. Swipe on the notification to close it. |
Warning | Indicated by an orange icon. This notification indicates that the problem may impact operation so continued observation is required. Swipe on the notification to close it. |
Caution | Indicated by a blue icon. This notification indicates that the problem requires monitoring but presents no hazard. This notification is only displayed when you tap the Notification button. |
Operational Status Notifications
Operational Status notifications provide information on ongoing actions and let you know when these actions are successful. They look similar to and appear in the same place as error notifications in the Main View, but have different icons. Also, there is no option to tap (for further action) or close these types of notifications.
Notification | Description |
Status | Indicated by a blue background. This notification provides information on system actions currently in progress. This notification automatically clears after 10 seconds. |
Success | Indicated by a green background. This notification shows when an action has been completed successfully (e.g. “Ready for mission”). This notification automatically clears after 10 seconds. |
Pre-mission Notifications
Notification | Description | Recommended Action |
Critical | ||
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. |
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 firmware version installed 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. |
Warning | ||
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. |
Caution | ||
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. | |
Waiting for robot’s position to stabilize | The robot or our own state estimation indicate that the robot is moving. This is likely to be 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 was lost | 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. |
Notifications During Mission
Notification | Description | Recommended Action |
Critical | ||
Hovermap battery critical | Robot will begin emergency decent. | |
Lost Hovermap control | The robot has unexpectedly taken back control of the robot from Hovermap. | Switch to robot control mode. |
Hovermap control refused | The robot has unexpectedly denied control to Hovermap. | Switch to robot control mode. |
Robot hardware failure | There has been a failure in robot or Hovermap hardware integrity. Generally, this means the robot has crashed. | Switch to robot control mode. |
Lost robot link | The control and telemetry link to the robot has been lost. This may be caused by a failure in the interface cable, or it becoming unplugged. | Switch to robot control mode. |
Navigation solution degraded | No usable state estimate available. The robot will return home via the rally point set. | Monitor for safe flight and switch to robot control mode if required. |
SLAM solution failed | The local SLAM solution has failed. This is a good indication that the data captured in this mission will not result in a good map. | Stop then restart your mission to continue. |
Warning | ||
High Hovermap temperature | The CPU has undergone throttling events recently, and the heatsink may be hot to touch. | Avoid touching Hovermap body while hot. |
Hovermap battery low | The remaining battery capacity has dropped to a level where the robot needs to return home. The robot will return home via the rally point if set. | Allow the failsafe to complete. The robot will return home via the rally point (if set). |
Connection between Hovermap and user device was lost | The link to the ground control station has been lost, at a time in the mission where it is required. The robot will return home. | Monitor for safe flight. |
Take off aborted | The robot encountered difficulty in executing the takeoff procedure. This can occur when there are obstacles in close proximity to the robot. | Check for obstacles near the robot. |
LiDAR point loss | The LiDAR has encountered an environment in which it cannot operate effectively. The robot will return home via the rally point set. | Allow the failsafe to complete. |
Dust failsafe triggered | The path planner is unable to make a plan, and is 'stuck'. This is most likely to happen because of excessive dust. The robot will return home via the rally point set. | Allow the failsafe to complete. |
Navigation solution degraded | Hovermap's state estimate accuracy is decreasing due to environmental conditions causing the SLAM system to be degraded. The robot will return home via the rally point set. | Monitor for safe flight and switch to robot control mode if required. |
Hovermap cannot take control | The preconditions required to allow Hovermap to take control of the robot are not satisfied. | Switch to robot control mode. |
Robot outside geofence | The robot indicates it is outside a geofence. | Return the robot to a safe distance inside the geofence to ensure a mission can be started and control maintained during a mission. |
Caution | ||
Remote control has been disconnected | The link to the remote control unit has been lost, at a time in the mission where it is required. The robot will return home. | To intervene when connection to the remote control has been recovered, change to Pilot Assist mode first then to robot control mode if required. |
DJI Notifications
Notification | Description | Recommended Action |
Critical | ||
Hovermap is using a different robot than the connected remote control | The RC and the Hovermap are connected to different, incompatible models. | Ensure the correct Hovermap is connected. If the problem persists, land and restart the mission. |
Take off failed | DJI reported that take off has failed for an unknown reason. | Investigate using the DJI Pilot app. |
DJI: Critical warnings present | DJI is reporting a critical issue which needs investigation. | Land as soon as possible. Investigate using the DJI Pilot app. |
DJI configuration changes: Multiple flight modes disabled | The Multiple Flight Modes setting could not be enabled, or it is currently trying to update to being enabled but the changes have not been applied yet. | The Multiple Flight Modes setting needs to be enabled for safe flight control with Hovermap. |
DJI configuration changes: Enabling Multiple flight modes failed | Attempting to enable the Multiple Flight Modes setting with DJI failed. | |
DJI configuration changes: Novice mode enabled | The Novice mode setting is reported as enabled. | The Novice mode setting needs to be disabled for safe flight control with Hovermap. |
DJI configuration changes: Changing collision avoidance state failed | Attempting to change the state of the Collision avoidance setting through DJI failed. | |
DJI configuration changes: Changing RTH obstacle avoidance state failed | Attempting to change the state of the RTH obstacle avoidance setting through DJI failed. | |
Battery overheating. | DJI has reported that the batteries in the drone are too hot. Robot may shut down mid-air. | Land immediately. |
Warning | ||
DJI: App is not registered | The DJI SDK registration could not be completed, which means you are unable to connect to the DJI RC. | Allow the tablet and DJI controller to reconnect to the internet to allow DJI to register, then reconnect to Hovermap and try again. |
DJI: Low GPS signal | GPS signal is poor, or satellite search produced an error. | Move the robot to an open area to use GPS. |
DJI: Warnings present | DJI reported a warning which needs investigation. | Investigate using the DJI Pilot app. |
DJI configuration changes: Battery critical threshold different | The critical battery threshold reported by DJI is different to the expected values. | |
DJI configuration changes: Settings battery critical threshold failed | Attempting to set the new Critical battery threshold with DJI failed. | |
DJI configuration changes: Smart RTH enabled | The Smart RTH setting is reported as being enabled by DJI. | The Smart RTH setting needs to be disabled for safe flight control with Hovermap. |
DJI configuration changes: Disabling Smart RTH failed | Attempting to disable the Smart RTH setting through DJI failed. | |
Geofence could not be disabled | The Geofence applied by DJI could not be disabled when starting an autonomous mission. This is likely caused by the RC not being plugged into the tablet. | Connect the RC to the tablet. |
Caution | ||
DJI: Low GPS signal | GPS signal is poor, or satellite search produced an error. | Move the robot to an open area to use GPS. |
Drone downward sensors need to be covered with stickers to resolve the current DJI error | DJI reported that its sensors have detected a problem. This is likely caused by the downward sensors being uncovered during takeoff. | |
DJI configuration changes: Battery critical threshold unknown | The current Critical battery threshold could not be provided by DJI. | |
DJI configuration changes: Battery warning threshold unknown | The current Warning battery threshold could not be provided by DJI. | |
DJI configuration changes: Smart RTH status unknown | The current Smart RTH setting could not be provided by DJI. | |
DJI configuration changes: Novice mode setting unknown | The current Novice mode setting could not be provided by DJI. | |
DJI configuration changes: Disabling novice mode failed | Attempting to disable the Novice mode setting through DJI failed. | |
DJI configuration changes: Downward vision positioning status unknown | The current Downward vision positioning setting could not be provided by DJI. | |
DJI configuration changes: Changing downward vision positioning failed | Attempting to change the state of the Downward vision positioning setting through DJI failed. | |
DJI configuration changes: Changing vision assisted positioning state failed | Attempting to change the state of the Vision assisted positioning setting through DJI failed. | |
DJI configuration changes: Changing active obstacle avoidance state failed | Attempting to change the state of the Active obstacle avoidance setting through DJI failed. | |
DJI configuration changes: Changing upward collision avoidance state failed | Attempting to change the state of the Upwards collision avoidance setting through DJI failed. | |
DJI configuration changes: Changing horizontal vision obstacle avoidance failed | Attempting to change the state of the Horizontal vision obstacle avoidance setting through DJI failed. | |
DJI configuration changes: Changing advanced pilot assistance state failed | Attempting to change the state of the Advanced pilot assistance setting through DJI failed. | |
Battery high age or wear | DJI has reported that the batteries in the drone have high age or wear. | |
Battery too cold |
DJI has reported that the batteries in the drone are too cold. |
|
Battery cell broken | DJI has reported that one of the batteries in the drone has a broken cell. | |
Geofence disabled | The Geofence applied by DJI is not active. | Use DJI Pilot to enable geofence. |
Tablet Notifications
Notification | Description | Recommended Action |
Warning | ||
Tablet battery critical and may shut down. Hovermap control can be lost. Bring the robot home as soon as possible. | The tablet battery is critical and the tablet is about to shut down. | Bring the robot home as soon as possible. |
Caution | ||
Tablet battery very low | The tablet battery is very low. | |
Tablet storage is low. It is recommended to free up space before starting your mission | The storage space on the tablet is low. | Free up storage space |
Tablet storage very low. Free up storage space. | The storage space on the tablet is very low. | Free up storage space |
Wi-Fi lost - attempting to connect | The tablet Wi-Fi was not available. |
Commander Status Notifications
Notification | Description | Recommended Action |
Critical | ||
Failed to change Shield Settings. Please try again. | Attempting to change the Shield settings failed for an unknown reason. | Try changing the settings again. |
Failed to change Mission Settings. Please try again. | Attempting to change the Mission Settings failed for an unknown reason. | Try changing the settings again. |
Status | ||
Starting Scan | A scan has been started by the user. | |
Stopping scan | A scan has been stopped by the user. | |
Establishing onboard communications | The connection from the tablet to the payload is not receiving data and the tablet is waiting for a response from the server. | |
The preferred Hovermap Wi-Fi is available | When a Hovermap drops out of Wi-Fi range and a new non-Hovermap network is connected, the last Hovermap network will be saved. When the Hovermap comes back in Wi-Fi range, you will receive this notification. | If the Wi-Fi does not automatically reconnect, re-select the preferred Hovermap from the Android Wi-Fi Manager. Disable the auto reconnect option for all other networks. |
A new Hovermap has been connected | When a scan is running and the Wi-Fi connection is changed to a new Hovermap network. | |
A new Wi-Fi network has been connected | The Hovermap being used to run the scan is no longer connected. The Wi-Fi connection is changed to a new non-Hovermap network. | You will need to manually reconnect using the Android Wi-Fi Manager. |
Success | ||
Ready for Mission | An autonomous scan has been started, all pre-checks have been completed, and the mission is ready to commence. | Arm your robot then press Take Off to start your mission. |
Ready for Mission | A mapping scan has been started, all pre-checks have been completed, and the mission is ready to commence. | Start your mission. |