Troubleshooting NavVis VLX warnings and errors

Prev Next

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 
ERR_LASER_HORIZ_RATE_LOW 

Message: Something went wrong! The current dataset will be stopped and saved

Cause: The sensor is not running with the expected rate. A long mapping time might be the cause for this behavior.

ERR_IMU_NO_MSGS_YET
ERR_LASER_HORIZ_NO_MSGS_YET

Message: Something went wrong! The current dataset will be stopped and saved

Cause: The sensor has not sent any data yet. This is most likely a hardware problem.

ERR_IMU_MSG_TOO_OLD
ERR_LASER_HORIZ_MSG_TOO_OLD

Message: Something went wrong. The current dataset will be stopped and saved.

Cause: The sensor stopped sending data. This is most likely a hardware problem, but a long mapping time might be the cause for this behavior.

 

ERR_NODE_NOT_RUNNING

Message: Something went wrong! The current dataset will be stopped and saved.

Cause: A critical software component is not running.

ERR_IMU_VALUES_NAN

Message: Something went wrong! The current dataset will be stopped and saved.

Cause: The IMU is sending invalid data. This is most likely a hardware problem

Troubleshooting procedure

  1. 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. 

  2. Once the dataset is saved, restart the device by pressing the power button.

  3. Start a new dataset. 


FAQ

What happens if the mobile scanning system detects a problem?

If a problem is detected, the system displays a notification, warning, or error.

Can warnings be resolved without stopping the mapping session?

Yes, warnings can be resolved by the operator without stopping the mapping session.

What should I do if I see the warning 'WARN_LASER_HORIZ_INVALID_MEAS'?

You should move the front of the device towards the closest wall that is less than 30 meters away.

What does the error 'ERR_IMU_RATE_LOW' indicate?

This error indicates that something went wrong, and the current dataset will be stopped and saved due to the sensor not running at the expected rate.

Is it necessary to restart the mapping session after an error occurs?

Yes, errors cannot be resolved without restarting the mapping session.

What should I do if I encounter a high system load warning?

You should slow down or pause the mapping for a while to achieve better results.

How can I manually stop and save the current dataset during an unexpected error?

From the Unexpected error screen, click 'Save dataset' to manually stop and save the current dataset.

What is the first step in the troubleshooting procedure after an error?

The first step is to click 'Save dataset' to manually stop and save the current dataset.

What causes the warning 'WARN_NODE_LOAD_HIGH'?

This warning is caused by a software component having high computation usage, often due to a long mapping time.