> 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/op4605xg2/operate-the-simulator/connect-small-form-factor-pluggable-sfp-modules.md).

# Connect Small Form-factor Pluggable (SFP) Modules

<figure><img src="https://1703604534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVzOnY8t4DxHCd5YLPVOx%2Fuploads%2F2UaVyMORhlKz9TSS9R4i%2Fimage.png?alt=media&amp;token=ffd36574-db95-4e4b-ab48-0c9ceb15b129" alt=""><figcaption></figcaption></figure>

The simulator is equipped with **SFP module connectors** to provide high-speed communication links between multiple OPAL-RT systems or compatible third-party devices. These connectors allow flexible, high-bandwidth interconnections for advanced multi-system setups.

Each SFP socket corresponds to a **single communication link**, consisting of one **input and one output signal**, enabling **up to four independent high-speed links** per simulator.

## **Key purposes and capabilities**

1. **Multi-simulator co-simulation:**
   * Multiple simulators can run **different real-time models independently** while sharing data via their FPGAs in real-time.
2. **External equipment communication:**
   * Enables clean, low-latency data transfer to external devices, including amplifiers, MMC controllers, or other third-party hardware.
   * Generally uses **Generic Aurora communication**, configured according to the requirements of the targeted application. Communication speed is configurable between **1 and 5 Gbps**, with appropriate SFP transceivers selected accordingly.
   * Additional protocols, such as Gigabit Ethernet, can also be implemented if required.
3. **Expand I/O capabilities:**
   * **MuSE** (Multi-System Expansion) is OPAL-RT’s high-speed communication protocol that allows a single simulator to connect to multiple I/O expansion units. This increases the number of available channels and enhances system flexibility, enabling simulators to support larger and more complex hardware-in-the-loop (HIL) configurations. For setup instructions, refer to the **Connect the Expansion Unit section** of your expansion unit’s documentation.

## **SFP transceivers and cables**

* **SFP transceivers** and **fiber-optic cables** must be purchased separately.
* The type and speed of the transceiver and cable must match the **communication protocol** used in your setup.
* To ensure proper communication, the **two SFP transceivers at both ends of the fiber-optic link must share the same specifications**. Ideally, they should be the **same part number** to guarantee compatibility and optimal performance. Ensure that all components are compatible with both your OPAL-RT system and any third-party devices.


---

# 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/op4605xg2/operate-the-simulator/connect-small-form-factor-pluggable-sfp-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.
