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

# Connect the 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 simulator.
  {% endhint %}

## **Connect the** power cable

Connect the power cord to the unit and to an appropriate power source (outlet).

{% hint style="info" %}
**The OP4300 frame and I/Os are grounded through the 18 V power supply unit (PSU) that is provided to the unit.** Using a non-grounded PSU will make the equipment floating. Proper grounding helps prevent electric shocks, and provides increased immunity from EMI by lowering noise levels and emissions.
{% endhint %}

## **Connect the unit to the master simulator**

When used as an **FPGA processor and I/O expansion unit**, 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 OP4300 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.

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

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

Connect the I/O **communication cables** from OP4300 to the **master unit :** use the SFP transceivers and LC-LC multimode fiber cable purchased with the unit to connect one SFP port of the unit to one SFP port of the real-time simulator.

<figure><img src="https://2927401004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRx4mGAP0TDheRyJ3CrkF%2Fuploads%2FA4gsrcnBHFpwF0fRh0kL%2FOP4300%20-%20Use%20case%201.png?alt=media&amp;token=6c94d6fc-f40c-4b31-b417-49e92026698f" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Make sure the simulator **bitstream** has been configured for **MuSE** **communication** also.
{% endhint %}

An **Ethernet link** from the real-time simulator is **required** to **flash the bitstream** to the OP4300.

{% columns %}
{% column width="41.66666666666667%" %}
**Ethernet ports** at 1 Gb/s must be connected to a free **Ethernet port** on the simulator side.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/q4pLCAxS0OKbOWfPLPdN" alt="" width="82"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="58.33333333333333%" %}

| **Status**              | <p><strong>Green LED</strong></p><p><strong>Activity</strong></p> | <p><strong>Yellow LED</strong></p><p><strong>Link State</strong></p> |
| ----------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------- |
| No link                 | Off                                                               | Off                                                                  |
| Link up but no activity | Solid On                                                          | Solid On                                                             |
| Link up with activity   | Blink                                                             | Solid On                                                             |
| {% endcolumn %}         |                                                                   |                                                                      |
| {% endcolumns %}        |                                                                   |                                                                      |

## External Devices <a href="#external-devices" id="external-devices"></a>

Connect **DB37 cables** from OP4300 to the **external devices** (motor, controller, etc.).

{% hint style="danger" %}
**Before connecting the cables**, make sure that the amplitudes are compatible with OPAL-RT DB37 amplitudes.
{% 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/op4300/get-started/connect-the-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.
