---
title: "NavVis VLX cannot start mapping with error NO_MSGS_YET"
slug: "vlx-mapping-cannot-start-with-error-err-laser-horiz-veoldyne-no-msgs-yet"
description: "NavVis VLX shows no live map and errors ERR_LASER_HORIZ_VEOLDYNE_NO_MSGS_YET or ERR_LASER_VERT_VELODYNE_NO_MSGS_YET. Causes: incomplete ROS package install, a wrong ros-stable repository entry, or Velodyne cabling."
tags: ["G11", "Error message", "NavVis IVION Processing", "G10", "G9"]
updated: 2025-09-23T12:46:41Z
published: 2025-09-23T12:46:41Z
canonical: "knowledge.navvis.com/vlx-mapping-cannot-start-with-error-err-laser-horiz-veoldyne-no-msgs-yet"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.navvis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# NavVis VLX mapping cannot start with error 'ERR_LASER_HORIZ_VEOLDYNE_NO_MSGS_YET'

## Introduction

### Problem description

After you started mapping with a NavVis VLX, no live map was displayed. Instead an error popped up with the message:

```plaintext
ERR_LASER_HORIZ_VEOLDYNE_NO_MSGS_YET;
ERR_LASER_VERT_VELODYNE_NO_MSGS_YET
```

### Scope

This solution applies to all NavVis VLX devices.

## Troubleshooting procedure

### Cause 1: ROS package installation is incomplete

The horizontal and/or vertical Velodyne nodelet wasn't set up correctly, thus no message was transferred to the system.

1. Use the terminal to check for updates on the NavVis VLX.
2. Install the software packages fully
3. Observe if there are any errors/warnings during the updates.

### Cause 2: ros-stable repository set incorrectly

Similar to cause 1, the ros packages are not set correctly, because the repository is incorrect.

1. Check during updating in the terminal, if there are any unusual warnings. Example:

![](https://cdn.document360.io/bf174766-fa1a-4fe1-a4d7-b1db1e7cb996/Images/Documentation/image-1707401335508.png)
2. Check in the `/etc/apt/sources.list.d/navvis-map.list` if the entries there are all correct. For example, here in the ros-stable repository, the component at the end should be "main" instead of "non-free"

![](https://cdn.document360.io/bf174766-fa1a-4fe1-a4d7-b1db1e7cb996/Images/Documentation/image-1707401395346.png)
3. Change the repository entry to the correct one (`deb http://repo2.navvis.com/repository/ros-stable/ bionic main`), then perform updates again and check mapping functionalities.

### Cause 3: hardware issues with Velodynes or cable connections

1. The cable connection from the Velodyne could be problematic. To check this, send the [device logs](/v1/docs/log-files-1) to NavVis Customer Support.
2. See this [troubleshooting article](/v1/docs/vlx-mapping-fails-with-err-msg-too-old-for-both-velodynes), if the error message is:

```plaintext
ERR_LASER_HORIZ_VELODYNE_MSG_TOO_OLD
```

The cause of this error could be an unstable cable connection.

---

### FAQ

#### What error message appears when no live map is displayed after starting mapping with a NavVis VLX?

The error message displayed is: ERR_LASER_HORIZ_VEOLDYNE_NO_MSGS_YET; ERR_LASER_VERT_VELODYNE_NO_MSGS_YET.

#### Does this troubleshooting solution apply to all NavVis VLX devices?

Yes, this solution applies to all NavVis VLX devices.

#### What could cause the Velodyne nodelet to not set up correctly?

An incomplete installation of the ROS package could cause the Velodyne nodelet to not set up correctly.

#### How can I check for updates on the NavVis VLX?

You can use the terminal to check for updates on the NavVis VLX.

#### What should I do if the ros-stable repository is set incorrectly?

You should check for unusual warnings during updates and verify the entries in /etc/apt/sources.list.d/navvis-map.list to ensure they are correct.

#### What should I do if I suspect hardware issues with Velodynes or cable connections?

You should send the device logs to NavVis Customer Support to check for any cable connection problems.

#### Is there a specific error message related to unstable cable connections?

Yes, the error message ERR_LASER_HORIZ_VELODYNE_MSG_TOO_OLD may indicate an unstable cable connection.