> 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/hypersim/examples/i-o-interfaces/op4810-io-or-op4815-io-with-op48h10.md).

# OP4810-IO or OP4815-IO with OP48H10

## Description

The **OP4810\_OP4815\_Generic\_Integration** example, located in **File > Open an Example File > IO Interfaces**, demonstrates how to configure Analog, Static Digital, Pulse Width Modulation (PWM) signals on OP4810-IO or OP4815-IO expansion units.

The example illustrates I/O configuration, loopback wiring using an **OP48H10** module installed in slot 1, and I/O validation with ScopeView.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bbf2cf0e9bedc4f0e8bc09cb31c8cf030f6d143c%2Fimage%20(1715).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

* **One** OPAL-RT simulator with support for an I/O expansion unit.
* **One** OP4810-IO or OP4815-IO expansion unit with an OP48H10 module installed in slot 1.
* **One** PCIe cable between the simulator and the expansion unit.
* **Two** Ethernet cables.
* **Two** DB37 loopback cables.

## Detailed explanation

### Connect the expansion unit

Follow the instructions provided in the **System Description Document** delivered with your system, or refer to:

* [Connect the OP4810-IO expansion unit](https://www.opal-rt.com/docs/op4810-io/get-started/connect-the-expansion-unit)
* [Connect the OP4815-IO expansion unit](https://www.opal-rt.com/docs/op4815-io/get-started/connect-the-expansion-unit)

### Connect loopbacks to the OP48H10 module

Connect the loopback cables as follows:

* **Digital I/O:** Connect **P1** to **P2** on the OP48H10 module installed in slot 1.
* **Analog I/O:** Connect **P3** to **P4** on the OP48H10 module installed in slot 1.

### Configure the OPAL-RT Board I/O Interface

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c82a66911a79fb91b0d44dd5be3e298356372c0b%2Fimage%20(1718).png?alt=media" alt=""><figcaption></figcaption></figure>

In HYPERSIM, configure the **OPAL-RT Board** according to your hardware:

* **Chassis Type:** Select the expansion unit model: **OP4810 (Versal)** or **OP4815 (Versal)**.
* **IP Address** and **Chassis ID:** Configure these parameters to match the expansion unit settings. Refer to the **System Description Document** or the information displayed on the expansion unit LCD screen.
* **Chassis Name:** Configure this parameter to match the expansion unit name. Refer to the **System Description Document** or the information displayed on the expansion unit LCD screen.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-89c87f00fb76c337c8724c26cc6c6c333f7d12f3%2Fimage%20(1719).png?alt=media" alt=""><figcaption></figcaption></figure>

## Simulation and results

The example includes designs for three I/O types supported by the OP48H10 module:

1. Analog I/Os
2. Static digital I/Os
3. PWM I/Os

After starting the simulation, inspect and compare inputs and outputs in ScopeView. A predefined template file named **OP40810\_OP4815\_Generic\_Integration.svt** is available in the example project directory.

### Analog I/Os

Each OP48H10 module has four banks of eight analog I/O channels:

Two banks are analog outputs:

1. Aout channels 0–7 (connector P3)
2. Aout channels 8–15 (connector P3)

Two banks are analog inputs:

1. Ain channels 0–7 (connector P4)
2. Ain channels 8–15 (connector P4)

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-da4da9e0f2b851004f92216d4b7649e067540cbe%2Fimage%20(1721).png?alt=media" alt=""><figcaption><p>Analog I/O’s Configuration</p></figcaption></figure>

The example defines sixteen reference analog signals sent to the two analog output banks.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-117b272ebc758b9638fcc8c1b6459d38c812dce4%2Fimage%20(1722).png?alt=media" alt=""><figcaption><p><em>Analog I/O’s model</em></p></figcaption></figure>

ScopeView page AIO displays the 16 analog inputs for slot 1; each graph shows one analog input with its corresponding reference analog output.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-01e863a22e2191a513ccad597382ed9d29e6f735%2Fimage%20(1723).png?alt=media" alt=""><figcaption><p><em>Analog I/O’s ScopeView</em></p></figcaption></figure>

### Static digital I/Os

The OP48H30 module has four banks of eight configurable digital I/O channels. Two banks are configured as static digital I/Os:

1. DI/O channels 0–7: static digital inputs (connector P1)
2. DI/O channels 16–23: static digital outputs (connector P2)

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a50385f7198961ca16c5dd5e077640e051a63cfb%2Fimage%20(1724).png?alt=media" alt=""><figcaption><p><em>Static digital I/O’s configuration</em></p></figcaption></figure>

The example defines eight random binary reference signals that are sent to the static digital output bank.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bfb79b6beb0639dca27057a3620bda7168eafb35%2Fimage%20(1725).png?alt=media" alt=""><figcaption><p><em>Static digital I/O’s model</em></p></figcaption></figure>

ScopeView page DIO displays static digital inputs 0–7; each graph shows an input and its associated reference output.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-19ca6635921e41ce6449e8f84fbe721850ec944c%2Fimage%20(1726).png?alt=media" alt=""><figcaption><p><em>Static Digital I/O’s ScopeView</em></p></figcaption></figure>

### Pulse Width Modulated PWM I/Os

The OP48H30 module has four banks of eight configurable digital I/O channels. Two banks are configured as PWM I/Os:

1. DI/O channels 8–15: PWM digital inputs (connector P1)
2. DI/O channels 24–31: PWM digital outputs (connector P2)

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d0e9319c3964cc5559eee13aea255741a4be16c6%2Fimage%20(1727).png?alt=media" alt=""><figcaption><p><em>PWM I/O’s configuration</em></p></figcaption></figure>

The example defines eight frequencies (100 Hz to 800 Hz) and eight duty cycle ratios (0.1 to 0.8) that are sent to the PWM digital output bank.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-799f6cbb98ef6b080b40ebb0a3e680d97c862fc7%2Fimage%20(1728).png?alt=media" alt=""><figcaption><p><em>PWM I/O’s model</em></p></figcaption></figure>

ScopeView page PWM displays the frequencies and duty cycle ratios detected on the PWM input channels; each graph shows the detected value and its reference.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5cc52df57248f88c8772b832f3fb051989f00baa%2Fimage%20(1729).png?alt=media" alt=""><figcaption><p><em>PWM I/O’s ScopeView</em></p></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/hypersim/examples/i-o-interfaces/op4810-io-or-op4815-io-with-op48h10.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.
