> 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/rt-lab/configure-ios/time-synchronization-driver/connect-the-hardware.md).

# Connect the Hardware

The required hardware setup depends on the timing signal provided by the external time source (**1PPS, IRIG‑B, or IEEE‑1588 (PTP)**) and on how the time reference will be used within the system. The following sections describe the most common use cases and their corresponding hardware connection requirements.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-f407acf58ba9eccbbffcf6689c0ebb0850bd30ea%2FDR-rtlab-oregano-hw.png?alt=media" alt=""><figcaption><p>Oregano card ports</p></figcaption></figure>

## Receiving an IRIG‑B clock signal for model timestamping

{% stepper %}
{% step %}

### Connect the IRIG-B signal to the X4 SMA input

Connect the IRIG‑B output of the external time source to the **X4 SMA input** on the Oregano card. Once connected, the time synchronization driver uses this signal to align the simulator clock and/or to provide accurate timestamps to the real‑time model.

The IRIG‑B signal connected to the **X4 SMA input** must meet the specifications below:

* Input impedance: 50 Ω nominal
* Input coupling: DC
* Voltage level: 0 to 3.3 V
* Absolute maximum voltage: 0.5 V to 4.25 V
* Minimum pulse width: 500 ns
* Logic high threshold: 2.0 V
* Logic low threshold: 0.8 V

{% hint style="danger" %}
**Important:** Only **demodulated IRIG‑B** signals are supported. Many time sources output **5 V IRIG‑B**; a **5 V to 3.3 V voltage divider** is provided and should be used if required.

<img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-c79b67ba49fd0e9a7ea23ef2e79f5fdd222ac72c%2FDR-rtlab-oregano-hw2.png?alt=media" alt="" data-size="original">
{% endhint %}
{% endstep %}
{% endstepper %}

## Receiving a 1PPS clock signal for model timestamping

{% stepper %}
{% step %}

### Connect the 1PPS signal to the X4 SMA input

Connect the 1PPS output of the external time source to the **X4 SMA input** on the Oregano card. Once connected, the time synchronization driver uses this signal to align the simulator clock and/or to provide accurate timestamps to the real‑time model.

The 1PPS signal connected to the **X4 SMA input** must meet the specifications below:

* Input impedance: 50 Ω nominal
* Input coupling: DC
* Voltage level: 0 to 3.3 V
* Absolute maximum voltage: 0.5 V to 4.25 V
* Minimum pulse width: 500 ns
* Logic high threshold: 2.0 V
* Logic low threshold: 0.8 V
  {% endstep %}
  {% endstepper %}

## Receiving a PTP clock signal for model timestamping

{% stepper %}
{% step %}

### Connect the PTP signal to a transceiver

Connect the PTP output of the external time source to a compatible **SFP or RJ45 transceiver** using a standard Ethernet or fiber‑optic cable. The Oregano card supports both transceiver types. The default transceivers supplied with the **OP3812 Time Synchronization kit** are:

* **FLD‑SG‑MMD‑1** (fiber‑optic)
* **FLD‑SASG‑T** (RJ45)

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-225fcc699130ac2e9dcec611281011756c585447%2FDR-rtlab-oregano-hw3.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Install the transceiver to the Oregano card

Insert the selected transceiver into the Oregano card. Once connected, the time synchronization driver uses the PTP signal to align the simulator clock and/or to provide accurate timestamps to the real‑time model.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-49715f9856e44517d8ef4db99819af779b66c7b7%2FDR-rtlab-oregano-hw4.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Using the Oregano card as a clock source

When no external master clock is connected, the Oregano card can operate as a **local time source** for the simulator and connected devices. In this configuration, the simulator generates and distributes time internally, and **no additional external hardware connections are required**.

## Propagating IRIG‑B or 1PPS to the FPGA

For **CPU‑only simulations**, the synchronized time can be directly linked to the simulation time within RT‑LAB, and no additional hardware connections are required. For **FPGA‑based simulations** (for example, when using eHS or I/O modules), the synchronized clock must be routed to the FPGA using the connections described below.

{% stepper %}
{% step %}

### Connect the IRIG‑B or 1PPS signal to the Oregano card

Connect the IRIG‑B or 1PPS output of the external time source to the **X4 SMA input** on the Oregano card.
{% endstep %}

{% step %}

### Connect the Oregano Card to the OP5964 adapter

Connect the **X7 SMA output** on the Oregano card to the **Ext. Sync In** (SMA) on the OP5964 external clock adapter.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-ab7ced8e85e5b865eea71480b1199c23d509b9d6%2FDR-rtlab-oregano-hw5.png?alt=media" alt="" width="470"><figcaption><p>SMA to SMA cable, connects the <strong>X7 output</strong> to the <strong>Ext. Sync In</strong></p></figcaption></figure>
{% endstep %}

{% step %}

### Connect the OP5964 to the FPGA synchronization port

Complete the connection between the OP5964 and the OPAL‑RT Synchronization Board:

* **Fiber‑optic OP5964:** Connect **Sync TX** (OP5964) to **Sync RX** on the OPAL‑RT Synchronization Board.
* **Copper OP5964:** Connect **Sync TX** to the **LVDS RX** on the OPAL‑RT Synchronization Board.

Once these connections are in place, the external time reference is distributed to the FPGA, enabling deterministic and time‑aligned operation.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-045c7d46cacc65b0c41c236ed7fd002e5a12080c%2FDR-rtlab-oregano-hw6.png?alt=media" alt=""><figcaption><p>Signal propagation from the Oregano to the FPGA, fiber optic on the left, copper right</p></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/rt-lab/configure-ios/time-synchronization-driver/connect-the-hardware.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.
