> 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/op4610xg-with-op4300-io.md).

# OP4610XG with OP4300 I/O

## Description

The **OP4610XG\_OP4300IO** example, located in **File > Open an Example File > IO Interfaces**, demonstrates how to use the OPAL-RT Board interface to exercise Analog, Static Digital, Pulse Width Modulation (PWM), and Time-Stamped Digital (TSDIO) I/Os available on the OP4300-IO Expansion Unit connected to an OP4610XG real-time simulator.

The model loops back the output signals to the corresponding inputs to validate configuration and signal integrity. More information is available in the Hardware Platforms Documentation for the [OP4610XG](https://www.opal-rt.com/docs/op4610xg/) and [OP4300-IO](https://www.opal-rt.com/docs/op4300/).

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

## Requirements

To run this example, the following are required:

* One OP4610XG simulator, or any other simulator that supports remote chassis;
* One OP4300-IO expansion unit;
* Two Ethernet cables to establish communication between the simulator and the Windows workstation, and communication with the OP4300-IO;
* Two Small Form-factor Pluggable (SFP) modules connected to a pair of fiber-optic cables between the OP4610XG and OP4300-IO;
* Three loopback cables with D-subminiature DC-37 (commonly named DB-37) male-to-male connectors.

## Detailed explanation

### Hardware setup

## Connections e**thernet**

Connect the OP4610XG real-time simulator to the same network as the workstation.

Connect the OP4300-IO chassis to the network, or to a local network with the OP4610XG. Use Port 0 (bottom port) on the OP4300-IO for Ethernet.

## **Small Form-factor Pluggable (SFP)**

Connect the OP4300-IO chassis to the OP4610XG chassis using SFP transceivers and fiber-optic cables.

## **I/O loopbacks**

The OP4300-IO has six DB-37 female connectors on the top of the chassis.

| P1 – Analog In Ch. 0 – 15   | P4 – Analog Out Ch. 0 – 15   |
| --------------------------- | ---------------------------- |
| P2 – Digital In Ch. 0 – 15  | P5 – Digital Out Ch. 0 – 15  |
| P3 – Digital In Ch. 16 – 31 | P6 – Digital Out Ch. 16 – 31 |

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c10f3e1b70ca281e4ed122eb2c6cc2742a700555%2FOP4610XG-OP4300-2.png?alt=media" alt="" width="480"><figcaption><p>Loopback configuration to be used with the OP4300-IO expansion unit</p></figcaption></figure>

### Chassis identification

Identify the central and remote chassis by running the **flash\_update -enumRemote** command on the OPAL-RT Linux system.

<details>

<summary><strong>Output of the Flash Update command</strong></summary>

{% code lineNumbers="true" %}

```
--- TE0741 cards enumeration ---
----- CENTRAL BOARD -----
TE0741 board found (VendorID=0x1B2C, DeviceID=0xF410)
        PCI Index:      0
        IRQ Number:     11
        RT-XSG:         3.9.0.9
        Chassis ID:     0
…
        ----- REMOTE BOARD(S) -----
Central SFP port 0:
        OP4300 board found (VendorID = 0x1B2C, DeviceID = 0x4300)
                RT-XSG:         3.9.0.9
                Chassis ID:     0
                Card type:      OP4300_5R
                SFP port used:  0
                Bus type:       MX
                Minor ID:       1
                Revision ID:    0
                ARM Core:
                   Software version: 1.1.1
                   Ethernet 0:
                      MAC address: 54:91:AF:00:00:00
                      IP:          192.168.3.5 (Reachable)
                      Netmask:     255.255.255.0
                      Gateway:     192.168.3.1
         Connector |        Category        |    More Information    |
            P1     |          AIN           |         2 MSPS         |
            P2     |          DIN           |        Ch 0-15         |
            P3     |          DIN           |        Ch 16-31        |
            P4     |          AOUT          |     1 MSPS/ 2 MSPS     |
            P5     |          DOUT          |        Ch 0-15         |
            P6     |          DOUT          |        Ch 16-31        |
OP4300 hardware search done.
Found 1 remote device(s)
Enumeration of remote boards done
```

{% endcode %}

</details>

The command prints the chassis IDs for the OP4610XG (TE0741 bitstream) and the OP4300-IO, as well as the OP4300-IO IP address.

{% hint style="info" %}
The OP4300-IO LCD displays its IP address. On a local network with the OP4610XG simulator, it is typically 192.168.3.5. If connected to a broader network, a DHCP server may assign a different address.
{% endhint %}

**Set the chassis IDs and IP address of the central and remote boards** using the information from the flash\_update command output and the OP4300-IO LCD. The OP4300-IO LCD can also display a user-defined chassis name.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-35eb49147c9d452d33d2b7de43cd015bff7e3b45%2FOP4610XG-OP4300-3.png?alt=media" alt=""><figcaption><p>OP4610XG Configuration</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6c803e637db20cc8de95b52b252bf670a400ebfd%2FOP4610XG-OP4300-4.png?alt=media" alt=""><figcaption><p>OP4300 Configuration</p></figcaption></figure>

### I/O configurations

All OPAL-RT Board configurations are defined in HYPERSIM under the project’s I/O Interface. In this project, the I/O interface has a central board configured as an OP4610XG (Kintex-7) connected to an OP4300 (Kria) remote board.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6166f8e1d55eda2e8a24f0db155f40ce8769ce68%2FOP4610XG-OP4300-5.png?alt=media" alt=""><figcaption></figcaption></figure>

The I/O configuration of the OP4610 OPAL-RT Board in this project uses only Slot 1A and Slots 2A and 2B.

* Slot 1A: two banks of Digital Inputs (Static and PWM), followed by two banks of Digital Outputs (Static and PWM). Connect the two Slot 1A connectors with a DB-37 loopback cable.
* Slots 2A and 2B: Analog I/Os. Connect the first Slot 2A connector to the first Slot 2B connector with a DB-37 loopback cable.

The I/O configuration of the OP4300 remote in this project uses all supported types of I/O; the DIO are configured as Static, PWM and Time-Stamped I/Os (TSDIO).

* P1 and P4: Analog I/Os. Connect P1 to P4 with a DB-37 loopback cable.
* P2 and P5: Static Digital I/Os. Connect P2 to P5 with a DB-37 loopback cable.
* P3 and P6: channel banks are configured as follows:

  * Channels 0–7: PWM.
  * Channels 8–15: Time-Stamped Digital I/Os with Time unit set to Ratio.

  <figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-61dda8bf1103c95816818a13021202798b2bec14%2FOP4610XG-OP4300-6.png?alt=media" alt=""><figcaption></figcaption></figure>

## Simulation and results

The HYPERSIM model includes a ScopeView Template File with four pages:

### Analog I/Os

Displays two banks of eight analog outputs and inputs (channels 0–15). Each graph pairs one input with its corresponding output.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f350e0f48ffa8c772df3f2cf403d07764c2bb005%2FOP4610XG-OP4300-7.png?alt=media" alt=""><figcaption></figcaption></figure>

### Digital I/Os

Displays two banks of eight static digital outputs and inputs (channels 0–15). Each graph pairs one input with its corresponding output.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f1f6e84f82cc1bb543fdd05db1ac2ceffca29ef9%2FOP4610XG-OP4300-8.png?alt=media" alt=""><figcaption></figcaption></figure>

### Pulse Width Modulated PWM I/Os

Displays one bank of PWM inputs and outputs (channels 0–7). For each channel, the plots show:

* input and output frequencies
* input and output duty cycles

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6fdd6073d6da23648fb8ab616b64677dd7a2cc43%2FOP4610XG-OP4300-9.png?alt=media" alt=""><figcaption></figcaption></figure>

### Time-Sampled Digital TSD I/Os

Displays one bank of Time-Stamped inputs and outputs with four events (channels 8–15). For each channel, the plots show:

* four detected event ratios
* four generated event ratios

The event edge types (rising or falling) are not shown.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-350f182ca8b204b5571d72c0de6bfe26f9c5e845%2Fimage%20(1714).png?alt=media" alt=""><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/hypersim/examples/i-o-interfaces/op4610xg-with-op4300-io.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.
