> 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/op5705xg/supplementary-operations/install-op53xx-i-o-modules.md).

# Install OP53xx I/O Modules

{% hint style="danger" %}
**OP53nn I/O** **modules** are **pre-installed** on the carrier board of the simulator or expansion unit. The procedure outlined below pertains to **the installation of a new module or the replacement of a defective module by the customer, with the approval of OPAL-RT and under its supervision**.

* Always handle the module with care. Use an **electrostatic wrist strap** when manipulating the module.
* The module must only be used with **OPAL-RT carrier boards**.&#x20;
  {% endhint %}

The OP5300 I/O modules feature **two Samtec Q Strip High-Speed 80-position connectors** located on the bottom side of the PCB. These connectors are labeled either **J1/J2** or **P1/P2**:

* **Connector J2 (or P2):** Interfaces with the FPGA, carrying IDs, EEPROM signals, control data, measured data, and 3.3 V / 5 V power signals.
* **Connector J1 (or P1):** Interfaces with external devices, carrying power signals (12 V / 18 V), data signals, and other I/O signals.

The modules include **four mounting holes** to secure it to the carrier board.

## Installation steps

{% stepper %}
{% step %}

### Remove the top cover of the unit

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/dchR8rshMrP2gQ5Djy20" alt="" width="375"><figcaption><p>Remove 6 screws (3 per side) on OP56xx/OP57xx units</p></figcaption></figure>

1. Remove the 6 screws (3 on each side of the unit).
2. Use a flat, rigid tool (e.g., a flat-headed screwdriver) to lift the top cover.
   {% endstep %}

{% step %}

### Remove the OP53xx module

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/ciKgXYeMULVsnPjMHiC8" alt="" width="375"><figcaption><p>Top view of the carrier board for OP56xx/OP57xx units</p></figcaption></figure>

1. Unscrew the four mounting screws at each corner of the module.
2. Gently pull the module vertically out of the carrier board connectors.
3. Ensure the plastic stand-offs remain attached to the carrier board.
   {% endstep %}

{% step %}

### Install the OP53xx module

1. Verify that the plastic stand-offs are installed on the carrier board.
2. Orient the module so that the polarized connectors align with the carrier board connectors.
3. Apply light vertical pressure to seat the module fully; only the top of the PCB should be visible.
4. Align the four mounting holes with the plastic stand-offs.
5. Secure the module using the four screws to ensure a stable connection.

{% hint style="danger" %}
The **OP5332** module must be **installed in Group 1A or Group 1B only**. It also requires a special power cable (part #113-0987) and additional standoff screws (part #T00-9236). Contact [OPAL-RT support](https://www.opal-rt.com/contact-technical-support/) if assistance is needed.
{% endhint %}
{% endstep %}

{% step %}

### Reinstall the top cover

Reinstall the top cover and secure it with the 6 screws (3 on each side of the unit).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Module signals are **routed through the carrier board** to dedicated **DB37F connectors** at the back of the chassis. Users do **not** access signals directly on the module.
{% endhint %}


---

# 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/op5705xg/supplementary-operations/install-op53xx-i-o-modules.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.
