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

# Specifications & Architecture

<figure><img src="https://1076585587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoFy31JPo94xIV8nCRsjv%2Fuploads%2FCdCLSkFOxF3qjadFf1H5%2Fimage.png?alt=media&amp;token=6f23b3fd-fa59-4bf4-b678-b8e3b6045b43" alt=""><figcaption></figcaption></figure>

## Description

The **OP5020XG2** is a compact, entry-level simulator that combines all of our strengths in high-performance Rapid Control Prototyping (RCP) and Hardware-in-the-Loop (HIL) simulation.

It has **3 PCIe slots** available for third-party PCIe I/O and communication cards. Only **1 PCIe slot** can be used to **connect an FPGA processor and expansion unit**. The remaining PCIe slots are free to use for other types of I/O and communication cards.

Note that the **OP5020XG2 supports a maximum of 1 FPGA** for processing capabilities, regardless of the number of FPGA processor and expansion units connected. It is possible to connect more FPGA processor and expansion units by using **OPAL-RT’s MuSE protocol** and **SFP connectors** to expand the number of I/O channels.

Powered by a high-end **Intel**<sup>**®**</sup>**&#x20;Core**<sup>**TM**</sup>**&#x20;i3 4 cores** **processor**, the OP5020XG2 delivers strong computational performance and sub-microsecond time steps for fast, accurate power electronics simulation. It is fully compatible with **RT-LAB** **(2022.1 and higher)** and **HYPERSIM (2022.1 and higher):** [**https://www.opal-rt.com/download-center/**](https://www.opal-rt.com/download-center/)

The unit can be used as a desktop, shelf-top, or mounted in a standard 19″ rack.

## Specifications

<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>2U</td></tr><tr><td><strong>Dimensions (W × D × H)</strong></td><td>42.8 × 43.03 × 9 cm (16.84” × 16.94” × 3.5”)</td></tr><tr><td><strong>Weight</strong></td><td>Approx. 7.7 kg (17 lbs)</td></tr><tr><td><strong>Power Supply Unit (PSU)</strong></td><td>Input voltage: 115 VAC, +/-15 V, 220 VAC +/-20 V<br>Input frequency: 50-60 Hz<br>Power: 400 W</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 85% 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>

## Architecture <a href="#op4610xgsystemdescription-simulatorarchitecture" id="op4610xgsystemdescription-simulatorarchitecture"></a>

<table><thead><tr><th width="229">Component</th><th>Specification</th></tr></thead><tbody><tr><td><strong>Motherboard</strong></td><td>microATX</td></tr><tr><td><strong>Processor</strong></td><td>Intel® Core™ i3 4 cores, 3.5 GHz</td></tr><tr><td><strong>RAM</strong></td><td>16 GB DRAM</td></tr><tr><td><strong>Storage</strong></td><td>1 TB NVMe M.2 2280 SSD storage</td></tr><tr><td><strong>Operating System</strong></td><td>OPAL-RTLinux (real-time OS)</td></tr><tr><td><strong>Ports</strong></td><td>4 network ports (10/100/1000 Mbps), 1 VGA port, DVI-D port (not used), HDMI 2.0 port (not used), 1 serial port, 4 USB 3.2 Gen2 ports, and 3 PCIe slots.</td></tr></tbody></table>

<figure><img src="https://1076585587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoFy31JPo94xIV8nCRsjv%2Fuploads%2FgHr0P2pJW9wnLgOR08t0%2Fimage.png?alt=media&amp;token=f856d59c-8d6c-4f49-8a68-3d26003be74d" alt="" width="375"><figcaption></figcaption></figure>

## Typical use case

A **typical use case for the OP5020XG2** is to link it to an [**OP4810-IO**](https://www.opal-rt.com/docs/op4810-io/) or [**OP4815-IO**](https://www.opal-rt.com/docs/op4815-io/) **FPGA and expansion unit** to get a full-featured, powerful Hardware-in-the-Loop (HIL) simulation system.

The **OP5020XG2** needs to have a **One Stop System (OSS) PCIe host adapter installed to communicate with the OP48xx-IO** FPGA and expansion unit.

<figure><img src="https://1076585587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoFy31JPo94xIV8nCRsjv%2Fuploads%2Fp428zBTjkP7MaAi8Yb9b%2FOP5020XG2_usecase.png?alt=media&amp;token=7f2a2bc3-3ffb-4226-b48a-a905ecdb8d93" 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/op5020xg2/op5020xg2-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.
