> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/user-guides/holoplot-system-deployment/rigging/x1-custom-rigging.md).

# X1 custom rigging

### Integration information

HOLOPLOT's standard rigging is designed for modules in landscape orientation. Custom solutions are required for arrays with modules in portrait orientation.

* To safely rig an MD96, at least four of the eight available M10 rigging points must be used together, and at least two on each side of the Audio Module (left and right).
* To safely rig the MD80-S, all eight M10 points must be used together.

Each rigging screw shall be fixed with an appropriate torque not exceeding 65 Nm.

<figure><img src="https://1870956965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWZvA6Ecdn48SRkbJ1C8%2Fuploads%2F2gbHc9c04WLoWgQgSimI%2FCleanShot%202024-04-18%20at%2017.16.52%402x.png?alt=media&amp;token=7bb38916-69e0-4b69-a6ec-08b5743a46c2" alt=""><figcaption></figcaption></figure>

### Areas not to be covered

A custom rigging system should not cover any loudspeaker drivers at the front of the Audio Module.

The four infrared transceivers on the sides of the module should not be covered. Obstructing these sensors will prevent the module from automatically recognizing and configuring its position within a Matrix Array.

If automatic configuration is unavailable due to obstructed infrared transceivers, the Audio Module position can be configured manually via HOLOPLOT Plan.

The areas not to be covered are shown in red in the illustrations below, along with relevant dimensions.

<figure><img src="https://1870956965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWZvA6Ecdn48SRkbJ1C8%2Fuploads%2FizTYojkuTyKcSHJ5fq9x%2FCleanShot%202024-04-18%20at%2017.20.23%402x.png?alt=media&amp;token=bd5e58d5-1a74-434a-b6c7-549f1bd90412" alt=""><figcaption></figcaption></figure>

\ <br>


---

# 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://docs.holoplot.com/user-guides/holoplot-system-deployment/rigging/x1-custom-rigging.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.
