> 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/op4810-io/get-started/connect-the-expansion-unit.md).

# Connect the Expansion Unit

## Safety precautions

{% hint style="danger" %}

* Use **only the approved power cable** supplied with the product. Do **not** replace it with an inadequately rated cord.
* **Do not block ventilation vents**. Leave at least **15 cm (6")** clearance at the sides and rear when not rack-mounted.
* Detailed safety instructions are available in the **Overview** documentation page of the expansion unit.
  {% endhint %}

## Connect the power cable

Use the supplied power cable to connect the expansion unit to a grounded outlet.

## Connect the expansion unit to the master simulator

{% stepper %}
{% step %}

### Make the PCIe connection

Use the supplied PCIe x4 cable to connect the PCI Express port on the rear panel of the expansion unit to the OneStop PCIe x4 host adapter on the master simulator. This PCIe connection is required for proper operation.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/JvxNDeLP270KGSPQLleX" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Make the Ethernet connection

Use an Ethernet cable to connect Ethernet port #1 on the expansion unit to the simulator’s LAN2 (eno2) port. This point‑to‑point Ethernet connection is required for proper operation.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/2FA7CAMjrbV4hAPCZtXc" alt=""><figcaption></figcaption></figure>

**When the expansion unit is shipped together with a simulator**, the system is delivered fully configured and operational. No additional network configuration is required. Detailed Ethernet settings and IP addressing information are provided in the **System Description Document** supplied with your order.

**When the expansion unit is shipped separately as an add‑on to an existing simulator**, additional configuration may be required. The simulator’s LAN2 (eno2) Ethernet port must be enabled and configured to communicate with Ethernet port #1 on the expansion unit. Both ports must be on the same subnet.\
By default, the expansion unit’s Ethernet port #1 is configured for DHCP and typically assigns itself the IP address `192.168.3.5`, as specified in its **System Description Document**. In this case, the simulator’s LAN2 (eno2) can be configured with a fixed IP address such as `192.168.3.7/24`. Refer to the **Set Up the Simulator’s IP Address** section of the simulator documentation for detailed instructions.

**When connecting two expansion units or more to the same simulator**, a closed local network must be used. One expansion unit may use DHCP; however, all additional units must be configured with distinct static IP addresses (e.g. `192.168.3.8`, `192.168.3.9`, etc) to prevent address conflicts. Refer to the **Change the IP Address** section of this expansion unit documentation for the detailed procedure.

{% hint style="info" %}
All information related to your specific configuration is provided in your **System Description Document.**
{% endhint %}
{% endstep %}

{% step %}

### Validate the Ethernet connection

| Status                 | Green LED (Activity) | Yellow LED (Link) |
| ---------------------- | -------------------- | ----------------- |
| No link                | Off                  | Off               |
| Link up, no activity   | Off                  | Solid On          |
| Link up, with activity | Blinking             | Solid On          |

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/g5BFj3i4vb0Uj1xB5oCm" alt="" width="169"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/op4810-io/get-started/connect-the-expansion-unit.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.
