Troubleshooting NavVis VLX warnings and errors
- 13 Mar 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Troubleshooting NavVis VLX warnings and errors
- Updated on 13 Mar 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Introduction
Problem description
If the mobile scanning system detects a problem, it displays a notification, warning, or error. Warnings can be resolved by the operator without stopping the mapping session, while errors cannot be resolved without restarting the mapping session.
Types of warnings
The following shows a list of warning messages displayed during scanning:
Code | Description |
WARN_LASER_HORIZ_INVALID_MEAS | Message: Please move the front of the device towards the closest (< 30m) wall. |
Cause: The horizontal laser is not acquiring enough close points for a stable and consistent localization of the device. | |
WARN_SYSTEM_LOAD_HIGH | Message: Please slow down or pause the mapping for a while. |
Cause: The system has a high computation usage. This can be due to a long mapping time. To achieve best results, the system should not work at full capacity. | |
WARN_NODE_LOAD_HIGH | Message: Please slow down or pause the mapping for a while. |
Cause: A software component has a high computation usage. This can be due to a long mapping time. In order to achieve best results, a software component should not work at full capacity. |
Types of errors
The following shows a list of error messages displayed during scanning:
Code | Description |
ERR_IMU_RATE_LOW | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: The mentioned sensor is not running with the expected rate. A long mapping time might be the cause for this behavior. | |
ERR_TF_RATE_LOW | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: A software component is not running with the expected rate. A long mapping time might be the cause for this behavior. | |
ERR_IMU_NO_MSGS_YET | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: The motion sensor has not sent any data yet. This is most likely a hardware problem. | |
ERR_TF_NO_MSGS_YET | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: A software component has not sent any data yet. This is most likely a hardware problem. | |
ERR_IMU_MSG_TOO_OLD | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: The mentioned sensor stopped sending data. This is most likely a hardware problem, but a long mapping time might be the cause for this behavior. | |
ERR_TF_MSG_TOO_OLD | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: A software component stopped sending data. This is most likely a software problem, but a long mapping time might be the cause for this behavior. | |
ERR_NODE_NOT_RUNNING | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: A critical software component is not running. | |
ERR_IMU_VALUES_NAN | Message: Sorry, something went wrong. Please finish your current dataset and reboot the device |
Cause: The IMU is sending invalid data. This is most likely a hardware problem. |
Troubleshooting procedure
From the Unexpected error screen, click Save dataset to manually stop and save the current dataset. The NavVis VLX automatically saves the dataset after 20 seconds.
Once the dataset is saved, restart the NavVis VLX 3 by pressing the power button.
Start a new dataset.
Was this article helpful?
