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

# Connect the Expansion Unit

## Safety precautions <a href="#safety-precautions" id="safety-precautions"></a>

{% 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

The expansion unit supports multiple communication interfaces for connecting to a master simulator. The available connection type depends on the configuration ordered with the unit.

* Using **SFP socket** and **MuSE** (**default**)
* Using optional Dolphin SW-Link PCIe adapter
* Using optional PCIe Target Cable Adapter

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

{% hint style="info" %}
Once the expansion unit is connected to the master simulator, refer to the **Analog and Digital I/O section** of your software platform documentation (RT-LAB or HYPERSIM) for instructions on preparing a simulation that uses the expansion unit’s FPGA and I/O modules.
{% endhint %}

### Default option: via SFP (MuSE configuration only)

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

In a MuSE configuration, the expansion unit acts as a **remote** and the simulator serves as the **central**. Use the supplied SFP transceivers and LC-LC multimode fiber cable to connect one of the expansion unit’s SFP ports to any available SFP port on the simulator. Unless otherwise specified in the **System Description Document**, any SFP port may be used for MuSE. The remaining ports are available for additional MuSE links or other communication protocols (e.g., Generic Aurora). The number of remote units is limited only by the number of available SFP ports on the central simulator. Because MuSE links include the synchronization signal, no additional cabling is required.&#x20;

{% hint style="danger" %}
MuSE is only compatible with the OPAL-RT Board workflow. The S-Function workflow, as defined in the RT-LAB documentation, is not supported.
{% endhint %}

### Second option: via PCIe

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

{% stepper %}
{% step %}

#### Connect the PCIe cable

Use the supplied **PCIe cable** to connect the simulator to the expansion unit. If the cable is fiber optic, connect the end labeled **Host** to the simulator and the end labeled **Target** to the expansion unit

{% hint style="danger" %}
These PCIe adapters must be ordered at the time of purchase and are factory-installed in the unit.

If the expansion unit was purchased separately, it includes a **matching PCIe interface board** that must be installed in the simulator before connecting the cable. For installation assistance, contact [OPAL-RT Technical Support.](https://opal-rt.com/contact-technical-support/)
{% endhint %}
{% endstep %}

{% step %}

#### Connect the synchronization cable

To ensure precise timing alignment between simulators and expansion units, synchronization signals are exchanged through the **front-panel TX/RX ports**. These ports transmit clock and trigger signals that keep all units operating in lock-step.\
Use the supplied **fiber-optic cable** to connect the **TX port** **of the simulator** to the **RX port of the first expansion unit**. If multiple expansion units are used, the synchronization signal received on an expansion unit’s RX port is automatically **f**orwarded from its TX port to the next unit in the chain.

{% hint style="info" %}
Your unit may be equipped with copper cable ports (3.5 mm audio jacks) for synchronization with legacy units. Use a standard 3.5 mm audio cable for connection.
{% endhint %}
{% endstep %}
{% endstepper %}

<figure><img src="https://2177945155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F37kP1apvOZ3FqT1kLTJk%2Fuploads%2Ffkg8nSNbH4PdJXyvX8LT%2Fimage.png?alt=media&amp;token=2cccdaa0-16df-432b-a90f-bd7ccdfde9b4" alt=""><figcaption><p>OP4610-IO TX/RX Synchronization Ports</p></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/op4610-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.
