> For the complete documentation index, see [llms.txt](https://ms-kb.msd.unimelb.edu.au/next-lab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ms-kb.msd.unimelb.edu.au/next-lab/3d-scanning/guides/vlx.md).

# VLX LiDAR SLAM Scanner

Wearable Scanner

<div data-full-width="true"><figure><img src="https://1820679795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FvVaU307aHblGDv8BnFkZ%2Fimage.png?alt=media&amp;token=a681b0be-67b9-40b1-8e33-e8d56b8336bf" alt=""><figcaption></figcaption></figure></div>

The VLX 3 is a wearable terrestrial scanner - it sits on your body and captures the environment around you. The VLX 3 uses LiDAR-based **SLAM (Simultaneous Localisation and Mapping)** technology. \
\
It is often used in navigation where there is continuous movement; i.e., in cars. SLAM is able to map out the environment and also place the device spatially in that same environment.\
\
In the VLX 3, as you walk around it will automatically build up the dataset, aligning individual scans is not as required in this workflow, making it faster and more accessible.

***

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Training LMS ⧉</strong></td><td>Complete relevant 3D Scanning training modules to access Equipment Loans.</td><td><a href="https://ms-training.msd.unimelb.edu.au/view_course/344">https://ms-training.msd.unimelb.edu.au/view_course/344</a></td></tr><tr><td><strong>Equipment Loan ⧉</strong></td><td>Loan from the Media Hub once you have finished your training.</td><td><a href="https://msd.unimelb.edu.au/maker-spaces/loans-desk">https://msd.unimelb.edu.au/maker-spaces/loans-desk</a></td></tr><tr><td><strong>Consultations ⧉</strong></td><td>Consult one of our Technicians about your projects or for technical guidance.</td><td><a href="https://msd.unimelb.edu.au/maker-spaces/next-lab/main#resources-services">https://msd.unimelb.edu.au/maker-spaces/next-lab/main#resources-services</a></td></tr></tbody></table>

## The Kit

The VLX 3 kit comes in a hard case containing the following:&#x20;

<figure><img src="https://1820679795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FdiJHbg26TZfocvw2YM0V%2Fimage.png?alt=media&amp;token=1b32c75b-f1fb-4270-9c83-b86122ce2b87" alt=""><figcaption></figcaption></figure>

There will also be some cleaning cloths, replacement parts and other miscellaneous items.

## Credentials

Please speak to NExT Lab about setting up credentials to access the processing workflow.

***

## Scanning Parameters

| Distance                                         | Accuracy |
| ------------------------------------------------ | -------- |
| 10m, 30m or 50m depending on scanning parameters | +- 5mm   |

***

## Workflow

### Evaluate + Plan

For any 3D scanning project, it is best to plan out how you will approach the scanning - where to best take the scans, how many scans as an indicator of time, scan quality, and more. You can start with the BLK360 Benchmarking guide here:

{% content-ref url="/pages/-MQKAJqyiPoLMIrJS\_Qr" %}
[BLK360 Benchmark](/next-lab/3d-scanning/guides/leica-blk-360/blk360-benchmark.md)
{% endcontent-ref %}

The main differences are instead of individual single scans, the VLX 3 will scan continuously as you move; so you will need to consider your route as a continuous walk and ensure you are navigating around occlusions to ensure a complete scan.

Planning out your route means that you prepare exactly how to approach the walk - having a floorplan or visiting the location early can help - you don't want to just start scanning without an idea on how you intend to move. More details are covered in 2.

### Scanning Workflow

{% content-ref url="/pages/4cZs6jHrC6UvQp62EYPh" %}
[VLX setup](/next-lab/3d-scanning/guides/vlx/vlx-setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/Mjv7EYGEXXSgX4gc0EkH" %}
[Preparing to Scan](/next-lab/3d-scanning/guides/vlx/preparing-to-scan.md)
{% endcontent-ref %}

{% content-ref url="/pages/ezBGjKfF9pbHX1s5pHM5" %}
[Using the Scanner](/next-lab/3d-scanning/guides/vlx/using-the-scanner.md)
{% endcontent-ref %}

{% content-ref url="/pages/4AKw1w42Nl0rI8pcK3XO" %}
[Processing the Scans](/next-lab/3d-scanning/guides/vlx/processing-the-scans.md)
{% endcontent-ref %}

## Training modules&#x20;

In addition to the Next-Lab knowledge base on the VLX, you can create a NavVis account [here](https://support.navvis.com/).&#x20;

<figure><img src="https://1820679795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FNNlm1MWbWsVqK8MetHSP%2Fimage.png?alt=media&amp;token=c2f70caf-e4e5-4c7a-bfc8-7cbbf002bfe7" alt=""><figcaption></figcaption></figure>

Once you've signed in, you can access the training modules linked below:

{% embed url="<https://knowledge.navvis.com/>" %}

<figure><img src="https://1820679795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FKkBmfWpZM2twxJLQhqT9%2Fimage.png?alt=media&amp;token=3afbb268-4e36-4b41-97af-ef422fb11511" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ms-kb.msd.unimelb.edu.au/next-lab/3d-scanning/guides/vlx.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.