> 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/sensor-mounting.md).

# Mounting the sensors

Four sensors hang high around the stage. Clamp them to the truss if there is one; otherwise put them on light stands. Either way they sit **3–5 m** above the floor with the **LiDAR facing down**. See [What's included](/movin-tracin-stage/install-the-hardware/whats-included.md) for the parts you need.

<figure><img src="/files/xpGcDaOtHFHG03NNDgs7" alt="Sensors clamped to truss and sensors on light stands, both at a mounting height of 3 to 5 m"><figcaption><p>Top: clamped to truss. Bottom: on light stands. Either way, 3–5 m (10–16 ft) above the floor.</p></figcaption></figure>

## Where to place them

Mark out the stage (tracking) area as a rectangle and put **one sensor at the middle of each side** — that is the recommended layout. Where mid-side leaves no room, the **four corners** work too.

<figure><img src="/files/T9mkY16eH2wDPshd6C2q" alt="Sensor layout seen from above — mid-side (recommended) and corners, plus the minimum and maximum tracking area"><figcaption><p>Mid-side is recommended; corners are fine too. The tracking area runs from 3 × 3 m up to 10 × 10 m.</p></figcaption></figure>

* **Tracking area** — keep it between 3 × 3 m (10 × 10 ft) and 10 × 10 m (33 × 33 ft).
* **Height** — **3 m (10 ft) minimum, 5 m (16 ft) maximum** above the stage floor. The steeper the view from above, the less people block one another.
* **Overlap** — neighbouring sensors must see overlapping ground. During calibration the wand has to be visible to two or more sensors at once for the alignment to work.
* **Clear line of sight** — keep speakers, lighting fixtures, set pieces, and drapes out of the way. Anything blocked is not tracked.

## How to mount

1. Spread the stand's legs wide and weight it with a sandbag. When rigging to truss, use a safety cable.
2. Grip the clamp onto the pole or pipe and tighten it firmly.
3. Screw the sensor's 3/8 inch hole onto the stud, then level it so the **LiDAR faces down**, and lock it.
4. Run the cable down along the stand and secure it with cable ties, leaving a little slack just below the sensor.

<figure><img src="/files/2A7mR6f6A2zgpIAm4mbJ" alt="A LiDAR sensor held facing down on a mount by a stud"><figcaption><p>On the stud — the LiDAR faces down.</p></figcaption></figure>

<figure><img src="/files/hRDN70FbXu8tcHDu1NRm" alt="A LiDAR sensor hanging from a clamp on top of a light stand"><figcaption><p>Clamped to a light stand.</p></figcaption></figure>

## Cabling

Each sensor takes one network cable, and that cable carries both power and data — nothing else has to reach the sensor.

<figure><img src="/files/93VII1NAgumju3JyArt3" alt="Four sensor cables in the supplied switch&#x27;s PoE ports"><figcaption><p>One cable per sensor into the PoE ports; the port on the right goes to the server.</p></figcaption></figure>

1. Run each sensor's cable down to the switch supplied with the system and plug it into any **PoE port** — the numbered group on the left. The PoE light for that port comes on once the sensor is powered.
2. Join the switch to the server with one more cable: use port **17** or **18** on the right — those two do not supply power — and plug the other end into the server's **LIDAR** port. See [The back of the server](/movin-tracin-stage/install-the-hardware/server-back.md).

Once the sensors are up, go to [Stage 1 · Calibration](/movin-tracin-stage/setup/calibration.md).

{% hint style="warning" %}
Calibration is computed from where the sensors sit. If a sensor is moved, or a stand drifts during a show, tracked positions shift — keep stands out of walkways.
{% endhint %}


---

# 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/sensor-mounting.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.