> 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/review-the-driver-connectable-points.md).

# Review the Driver Connectable Points

The driver’s connectable points enable the driver to exchange data with the model. **Once** the driver is configured, these connectable points are exposed.

Exposed connectable points appear in the **I/O Selector** window when clicking the **Edit I/O Connection** icon for a sensor in the HYPERSIM model:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5a38fd500c766f55df0e52c56d37cd0aaefe166b%2FDR-hyp-sync-connectable.png?alt=media" alt=""><figcaption></figcaption></figure>

In the **I/O Selector** window, **connectable points** are color‑coded based on their data direction:

* **Blue** connectable points indicate data **sent** **from the model** to the driver during execution
* **Red** connectable points indicate data **received** from the driver **into the model** during execution

## Time synchronization signals

These connectable points enable alignment with external systems or time‑synchronized environments.

<table><thead><tr><th width="185">Connectable name</th><th width="275">Description</th><th width="125">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Seconds</strong></td><td>Provides the number of seconds elapsed since <strong>00:00:00 on January 1, 1970 (UTC)</strong>, also known as <strong>Unix time</strong>, <strong>POSIX time</strong>, or <strong>Epoch time</strong>. The counter starts at <strong>0</strong> when the card is powered on and increments once per second. When the Oregano Syn1588 PCIe card synchronizes to an external <strong>IEEE‑1588 PTP</strong>, <strong>IRIG‑B</strong>, or <strong>1PPS</strong> source, this value updates to the absolute time provided by the external reference.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Nanoseconds</strong></td><td>Provides the number of nanoseconds within the current second. The value ranges from <strong>0</strong> to <strong>999,999,999</strong> (exclusive) and resets at each new second.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Shifted time/Seconds</strong></td><td>Provides the time in seconds after applying the configured <strong>Time offset (s)</strong> to the <strong>Time / Seconds</strong> value.</td><td>To model</td><td>Exposed when <strong>Time offset (s)</strong> is non‑zero in <strong>Synchronization interface</strong> configuration.</td></tr><tr><td><strong>Shifted time/Nanoseconds</strong></td><td>Provides the nanoseconds value after applying the configured <strong>Time offset (s)</strong> to the <strong>Time / Nanoseconds</strong> value. The value ranges from <strong>0</strong> to <strong>999,999,999</strong> (exclusive) and resets at each new second.</td><td>To model</td><td>Exposed when <strong>Time offset (s)</strong> is non‑zero in <strong>Synchronization interface</strong> configuration.</td></tr></tbody></table>

## Status and information signals

These connectable points provide extra status and information.

<table><thead><tr><th width="120">Connectable name</th><th width="345">Description</th><th width="125">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>PTP Sync State</strong></td><td>Indicates the current synchronization state of the card:<br><br><strong>1 – Initializing:</strong> Card is not ready yet<br><strong>2 – Faulty:</strong> Unexpected condition; contact OPAL‑RT Support<br><strong>3 – Disabled:</strong> Unexpected condition; contact OPAL‑RT Support<br><strong>4 – Listening:</strong> Waiting for synchronization<br><strong>5 – PreMaster:</strong> Initializing master mode<br><strong>6 – Master:</strong> Operating as an IEEE‑1588 PTP master; may be synchronized via IRIG‑B or 1PPS<br><strong>7 – Passive:</strong> IEEE‑1588 disabled; synchronized via IRIG‑B or 1PPS<br><strong>8 – Uncalibrated:</strong> Attempting to lock to an external time source<br><strong>9 – Slave:</strong> Operating as an IEEE‑1588 PTP slave synchronized to a master clock</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>PTP Slave Offset</strong></td><td>Valid only when operating in <strong>PTP Slave mode</strong> (state 9). Provides the offset, calculated once per second by the PTP algorithm, between the local clock and the PTP master clock. Smaller values indicate better synchronization. For optimal performance, all network equipment between the PTP master and the Oregano Syn1588 PCIe card must be <strong>IEEE‑1588 compliant</strong>.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Sync Accuracy</strong></td><td>Indicates the estimated synchronization accuracy, in nanoseconds, of the current time source. In <strong>PTP mode</strong>, this reflects the accuracy reported by the PTP master (for example, ~100,000 ns when running on a local oscillator, improving to ~100 ns when synchronized to GPS). When synchronized using a high‑quality <strong>IRIG‑B</strong> or <strong>1PPS</strong> signal, accuracy can reach approximately <strong>25 ns</strong>.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>


---

# 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/review-the-driver-connectable-points.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.
