> 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/op4605xg2/operate-the-simulator/connect-analog-and-digital-i-o.md).

# Connect Analog & Digital I/O

OPAL-RT simulators are delivered with **DB37 loopback cables and modules** that provide different options for connecting, testing, and routing I/O signals. These can be used as-is, or replaced by custom cables and harnesses depending on system requirements.

<figure><img src="https://1703604534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVzOnY8t4DxHCd5YLPVOx%2Fuploads%2FiMt5ImelrvsDrl2QrnGn%2Fimage.png?alt=media&amp;token=38510d38-3c61-49f3-bd1b-fe4a70a920e3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Before connecting any cables, review your **System Description Document** to identify the installed I/O modules, their physical locations, and their pin assignments.
{% endhint %}

## Connect DB37 loopback cables

1. Insert the end of the DB37 loopback cable with the PCB board into the DB37 connector of the desired **Output module** of the unit.
2. Connect the other end of the DB37 loopback cable to the DB37 connector to the desired **Input module** of the unit to loop back the output signal.

{% hint style="danger" %}
Review the documentation of your **Output modules**. For Output modules that require external power, each bank of 16 signals must have its own supply. Power each DB37 loopback cable through its **Vuser** and **Vrtn** pins.
{% endhint %}

For 126-0361 **Rev 2.x** DB37 board&#x73;**:**

1. Set the DIP switch on the board to **EXT** (as shown above).
2. Do **not** set the switch to **INT.12V** unless specifically indicated in the **System Description Document**.
3. Connect an external power supply to the 2-pin screw terminal (refer to the I/O module’s documentation for voltage limits).

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/qZGyDdDBHHHDqBRoaZvE" alt=""><figcaption><p>126-0361 <strong>Rev 2.x</strong></p></figcaption></figure>

{% hint style="info" %}
The other end of the DB37 loopback cable could also be connected to the Input module of external hardware or DUT.
{% endhint %}

## Connect DB37 breakout boards

The **OP5980-2 DB37 breakout diagnostic board** provides access to individual pins for testing and isolation.

1. Insert the breakout board into the required DB37 connector of the unit.
2. Refer to the **System Description Document** or I/O module pin assignment for the correct pin usage.&#x20;
   1. **E06-0639** DB37 boards: Pinout is organized by I/O channels.
   2. **BRKSD37M** DB37 boards: Pinout is organized by pins; users must refer to the System Description Document or the I/O module documentation for the correct mapping.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/6DCZgMfhwqmm8gKzGbgh" alt="" width="563"><figcaption><p>E06-0639 (left) &#x26; BRKSD37M (right) </p></figcaption></figure>

{% hint style="danger" %}
For **Output modules** that require external power, each bank of 16 signals must have its own supply. Power each DB37 through its **Vuser** and **Vrtn** pins.
{% endhint %}

## Connect custom cables or harnesses

Review the documentation of your **I/O modules** and connect the cables accordingly.


---

# 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/op4605xg2/operate-the-simulator/connect-analog-and-digital-i-o.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.
