> For the complete documentation index, see [llms.txt](https://help.movin3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.movin3d.com/movin-tracin-stage/install-the-hardware/whats-included.md).

# What's included

The system ships with the equipment below. Stands, clamps, and network cables differ from venue to venue, so those have to be sourced separately.

<figure><img src="/files/G5VPQx3vwFvpPgHA9U1M" alt="Kit contents — LiDAR sensors, server, PoE switch and calibration wand in the box; stand, super clamp and network cable supplied by you"><figcaption><p>Top: what ships with the system. Bottom: what you supply.</p></figcaption></figure>

## In the box

| Item                 | Qty | What it does                                                               |
| -------------------- | --- | -------------------------------------------------------------------------- |
| **LiDAR sensor**     | 4   | Scans the stage and builds the point cloud.                                |
| **Server**           | 1   | A 2U rack unit. Processes the sensor data and serves the workspace screen. |
| **PoE switch**       | 1   | Feeds each sensor power and network over a single cable.                   |
| **Power cable**      | 2   | One for the server, one for the PoE switch.                                |
| **Calibration wand** | 1   | Used in Stage 1 to align the sensors into one shared coordinate system.    |

The number of sensors can differ with the size of the stage.

## What you supply

Per sensor you need one stand (or one spot on the truss), one clamp, one stud, and one network cable.

| Item                               | Qty          | How to choose                                                                                                   |
| ---------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------- |
| **Stand or truss**                 | 1 per sensor | A light stand that reaches 3–5 m (10–16 ft), or truss already rigged over the stage.                            |
| **Super clamp**                    | 1 per sensor | Grips a stand pole or truss pipe, and lets you angle the sensor and lock it in place.                           |
| **3/8 inch male stud (spigot)**    | 1 per sensor | Joins the clamp to the sensor. If the clamp only offers 1/4 inch, add a 1/4-to-3/8 adapter.                     |
| **Network cable (Cat6 or better)** | Sensors + 1  | One from each sensor to the switch, one from the switch to the server. Add one more if OSC goes out over cable. |

The threaded hole in the sensor body is **3/8 inch** (3/8-16). The 1/4 inch thread of a small camera tripod does not fit. This is the standard thread on lighting and photo stands, so the brand does not matter.

Once you have everything, go to [Mounting the sensors](/movin-tracin-stage/install-the-hardware/sensor-mounting.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.movin3d.com/movin-tracin-stage/install-the-hardware/whats-included.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
