> 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/op5707-io/op5707-io-overview/hardware-modularity.md).

# Hardware Modularity

## Analog & Digital I/Os

The OP5707-IO supports **up to 8 I/O modules** based on the user's configuration.

{% hint style="info" %}
**Detailed pin assignments for all connectors** can be found in the **System Description Document** provided with your order, or refer to the pin assignment of the [**OP53xx series I/O module**](https://www.opal-rt.com/docs/op53xx/) associated with each DB37 connector.
{% endhint %}

<details>

<summary>List of the supported I/O modules</summary>

* OP5330
* OP5340
* OP5342
* OP5351
* OP5352
* OP5353
* OP5354
* OP5360
* OP5363
* OP5367
* OP5369

</details>

{% hint style="danger" %}
All I/O modules are factory installed. I/O modules can only be changed by OPAL-RT, its affiliates, or certified distributors. Opening the FPGA processor and I/O expansion unit enclosure **voids the product warranty**.
{% endhint %}

## PCIe optional cards <a href="#op4610xg-pcie-optional-i-o-cards-inlineextension" id="op4610xg-pcie-optional-i-o-cards-inlineextension"></a>

* Dolphin SW-Link PCIe adapter (Dolphin PXH832)
* OneStop PCIe Target Cable Adapter (OSS-PCIE-HIB25-X4-H-4287)

{% hint style="danger" %}
PCIe optional cards must be **selected at the time of purchase** and **factory-installed**.
{% 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/op5707-io/op5707-io-overview/hardware-modularity.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.
