> 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/op4610-io/op4610-io-overview/specifications-and-architecture.md).

# Specifications & Architecture

<figure><img src="https://2177945155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F37kP1apvOZ3FqT1kLTJk%2Fuploads%2Fq6xFDNS3rSB7PJfNgjln%2Fimage.png?alt=media&amp;token=a3a9c4a3-1224-48be-90ac-267b432ddc9f" alt=""><figcaption></figcaption></figure>

## Description

The **OP4610-IO** is a compact I/O expansion unit designed to **extend the capabilities of OPAL-RT simulators**. It provides up to **128 fast I/O channels** with signal conditioning, **12 channels for RS-422 or optional low-speed fiber-optic communication**, and **4 high-speed SFP ports** for multi-system or remote I/O connections.

Equipped with a **Xilinx® Kintex®-7 410T FPGA**, the OP4610-IO delivers reliable, low-latency signal processing for Hardware-in-the-Loop (HIL) and Rapid Control Prototyping applications. It is fully compatible with **RT-LAB** **(2022.1 and higher)** and **HYPERSIM (2022.1 and higher)**: <https://www.opal-rt.com/download-center/>.

The unit can be used as a **desktop, shelf-top, or mounted in a standard 19″ rack**, providing flexible installation options for diverse testing environments.

<table data-search="false"><thead><tr><th width="261">Category</th><th>Specification</th></tr></thead><tbody><tr><td><strong>Form Factor</strong></td><td>3U rackmount (mounting brackets included)</td></tr><tr><td><strong>Dimensions (W × D × H)</strong></td><td>43.18 × 28 × 14 cm (17” × 11” × 5.5”)</td></tr><tr><td><strong>Weight</strong></td><td>Approx. 5 kg (11 lbs)</td></tr><tr><td><strong>Power supply</strong></td><td>115 VAC ±15 V / 220 VAC ±20 V, 50–60 Hz, 8.0 A–4.0 A, 400 W max</td></tr><tr><td><strong>Operating Temperatures</strong></td><td>10–40°C (50–104°F)</td></tr><tr><td><strong>Storage Temperatures</strong></td><td>-20 to 70º C (-4 to 158º F)</td></tr><tr><td><strong>Relative Humidity</strong></td><td>10 to 90% non-condensing</td></tr><tr><td><strong>Max Altitude</strong></td><td>2000 m (6,562 ft.)</td></tr><tr><td><strong>Pollution</strong></td><td>Degree 2</td></tr><tr><td><strong>Ventilation Requirements</strong></td><td>Allow 15 cm (6") of clearance when not rack-mounted</td></tr><tr><td><strong>Intended Use</strong></td><td>Indoor use only</td></tr></tbody></table>

## Expansion unit architecture <a href="#op4610xgsystemdescription-simulatorarchitecture" id="op4610xgsystemdescription-simulatorarchitecture"></a>

The diagram below shows the general architecture of the OP4610-IO expansion unit.

<figure><img src="https://2177945155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F37kP1apvOZ3FqT1kLTJk%2Fuploads%2FbsN5CjzpbnJeqAQwrpRU%2Fimage.png?alt=media&amp;token=9bcac31c-0ea9-4da3-9170-a47e607018fe" alt=""><figcaption></figcaption></figure>

The main housing is divided into two functional sections.

### Lower section: power supply

This section contains the power supply and, in some configurations, one of the following PCIe adapters for communication with a simulator:

* Optional Dolphin SW-Link PCIe Adapter (PXH832)
* Optional PCIe Target Cable Adapter (OSS-PCIe-HIB25-x4-T)

### Upper section: FPGA and I/O modules

This section includes the high-speed FPGA and the I/O modules for up to 128 I/O channels.

<table><thead><tr><th width="180" valign="top">Component</th><th>Specification</th></tr></thead><tbody><tr><td valign="top"><strong>FPGA</strong></td><td><p><strong>Xilinx® Kintex®-7 410T FPGA</strong>, programmable from the real-time computer via PCIe</p><ul><li>Executes FPGA-based simulations using OPAL-RT’s RT-XSG toolbox</li><li>Manages all I/O lines</li><li>Exchanges data with the CPU via a high-speed PCIe link</li></ul></td></tr><tr><td valign="top"><strong>Carrier Board</strong></td><td><strong>4-slot</strong> <strong>carrier board</strong> supporting up to four I/O modules, for a total of <strong>up to 128 I/O channels</strong>.</td></tr><tr><td valign="top"><strong>SFP ports</strong></td><td><p><strong>4 SFP ports</strong> for high-speed communication with other FPGA-based systems or external devices</p><ul><li>Supports Xilinx Aurora protocol (1–5 Gbps) by default</li><li>Optional support for other protocols (e.g., Gigabit Ethernet)</li><li><p><strong>MuSE (Multi-System Expansion) support</strong> enables the expansion unit to operate as a remote expansion unit for I/O scalability:</p><ul><li>One SFP port connects to a central simulator</li><li>Expands I/O capacity by up to <strong>128 channels</strong> per remote expansion unit</li><li>Remaining SFP ports can be used for <strong>Generic Aurora</strong> communication links</li></ul></li></ul></td></tr></tbody></table>


---

# 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/op4610-io/op4610-io-overview/specifications-and-architecture.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.
