> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/op8120/op8120-gen-1-modular-signal-conditioning-chassis-mscc-legacy/install-and-operate.md).

# Install and Operate

The **OP8120** chassis has rails that allow quick installation of the modules in the appropriate slot.

<figure><img src="https://content.gitbook.com/content/re3d8M3OpCkdPOndYEMH/blobs/P95XDd5dFnitn8ossBPF/image.png" alt=""><figcaption><p><em>Installation drawing</em></p></figcaption></figure>

* Simply position the module in alignment with the desired slot and push in firmly until the connector is pressed into the backplane connector.
* When the module is in place, affix it using the 4 screws provided.
* When all modules are in place, plug the power cable of the power supply (located in the back of the unit) into a power source.
* Power on the unit, using the power switch at the front. The LED should light up.
* The conditioning chassis is now operational.

{% hint style="info" %}
For details on how to operate each module, please consult the sections pertaining to the module in question.
{% 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 by asking a question.

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

```
GET https://www.opal-rt.com/docs/op8120/op8120-gen-1-modular-signal-conditioning-chassis-mscc-legacy/install-and-operate.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.
