> 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/hypersim/configure-ios/time-synchronization-driver/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **time synchronization** driver is included by default with <code class="expression">space.vars.Software</code> and does not require any additional installation.

## Hardware requirements

Time synchronization is supported using the **OP3812 Time Synchronization Oregano Syn1588 PCIe card** and requires an **OP5964 external clock adapter**. These components are sold together as a single kit at the time of purchase.

To verify whether the PCIe card is already included in your system, refer to your **System Description Document**. If the card is not included, consult the **Hardware Modularity** section of your hardware platform documentation to identify the compatible Oregano Syn1588 Time Synchronization PCIe kits available for your platform.

A **precision timing source** is **required but sold separately**. The time synchronization kit does **not** include an external time reference. Users must provide a compatible precision timing source capable of generating **1PPS**, **IRIG‑B**, or **IEEE‑1588 (PTP)** signals.

## License requirements

### Simulator license

[Verify that an active HYPERSIM license](https://www.opal-rt.com/docs/hypersim/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the time synchronization driver:

| Feature Name    | Required Status | Description                                                |
| --------------- | --------------- | ---------------------------------------------------------- |
| SYNCHRONIZATION | enabled         | Enables external time synchronization (IRIG-B, 1 PPS, PTP) |

### Workstation license

**No additional feature is required** in the workstation license to run simulations in HYPERSIM using the synchronization driver.

## Supported features

* Operate as an IEEE1588 master or an IEEE1588 slave node
* Supports IEEE-1588-2002 (PTP V1) and IEEE-1588-2008 (PTP V2)
* **Supports all standard profiles:**
  * Default (IEEE1588-2008 Annex J.3)
  * Default P2P (IEEE1588-2008 Annex J.4)
  * Power (C37.238 2011)
  * Power S (C37.238 2011 slave only)
  * Power 2 (C37.238 2014) - *only supported on 32-bit Linux platforms (x86)*
  * Power 2 S (C37.238 2014 slave only) - *only supported on 32-bit Linux platforms (x86)*
  * C37.238 2017 - *not supported on 32-bit Linux platforms (x86)*
  * C37.238 2017 - *not supported on 32-bit Linux platforms (x86)*
  * SMTPE (ST 2059-2)
  * SMTPE S (ST 2059-2 slave only)
  * Telecom (G.8265.1 master only)
  * Telecom2 (G.8275.1)
  * Telecom2 S (G.8275.1 slave only)
  * gPTP (IEEE 802.1AS-2001)
  * gPTP S (IEEE 802.1AS-2001 slave only)
* Generate demodulated IRIG-B or 1PPS signal to synchronize external devices
* Can be synchronized by an external IRIG-B or 1PPS signal
* Implements best-master-algorithm defined in the IEEE1588 standard based on the configurable priority
* Supports virtual LANs (VLAN)
* Supports peer-to-peer and end-to-end delay mechanisms
* Starts the simulation aligned to the 1PPS reference (next second change)

## Limitations

* The Oregano Syn1588 PCIe card accepts demodulated IRIG-B004 or IRIG-B007 signals (3.3V) only.
* The Oregano Syn1588 PCIe card can generate IRIG-B007 or 1PPS signals (3.3V) only.


---

# 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/hypersim/configure-ios/time-synchronization-driver/requirements-features-and-limitations.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.
