> 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/accessories-conditioning-modules/accessories/op8210-connection-interface-series/install-and-connect.md).

# Install and Connect

* Place the **module in the rack** and **secure it** with the **four (4) screws** that come with it.
  * If there is not enough room in the rack, cables can be run through it and attached to the back of the module before it is put in place.
* Connect the **DB37 cables provided** to the **OP8210 connector interface** at the **back of the module**.
* **Connect** the **external device** to the **connector interface** on the **front of the module** by connecting it to the **appropriate channel connectors**.

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FYvWcBLf7MbesIjYQo81Y%2Fimage.png?alt=media&amp;token=0e38844b-1eb8-4d09-968f-39256228e04e" alt=""><figcaption><p>OP8210 rear and front connection examples</p></figcaption></figure>

* If required, connect the **Vuser external power supply**.
  * Depending on the type of board used in the simulator, the OP8210 connector interface may require an external power supply, for example when using a **digital output board**.
  * For more information about the use of **Vuser** and **Vrtn** please refer to this article in the OPAL-RT knowledge base: [**Powering DB37 Boards for Digital Output Modules**](https://portal.opal-rt.com/Knowledge-Base/Article/?id=3bb5144d-9356-ef11-bfe3-002248b1d264).

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2F3IUvg7zTocMX1nnDeHCH%2Fimage.png?alt=media&amp;token=8c009a19-a460-41af-a918-74c3af8d61ff" alt="" width="563"><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://www.opal-rt.com/docs/accessories-conditioning-modules/accessories/op8210-connection-interface-series/install-and-connect.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.
