> 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/communication-protocol-ios/c37.118-slave/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-367de58312eb21c78cdb98cc9ebf89dd1ad17ea3%2FDR-hyp-c37sl-connectable.png?alt=media" alt="" width="327"><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 connectable points

The C37.118 slave driver can automatically detect and use an available synchronization source provided by an **Oregano Syn1588 PCIe card**. See the **Time Synchronization Driver** section for detailed information.

Alternatively, clock connectable points can be **explicitly exposed and connected through the model**. When this approach is used, clock synchronization is handled **manually by the model** rather than automatically by the driver.

This mode is intended for advanced configurations where external clock behavior must be controlled or overridden at the model level.

<table><thead><tr><th width="135">Connectable name</th><th width="190">Description</th><th width="130">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Synchronized</strong></td><td>Boolean indicating whether the external clock is properly synchronized.</td><td>From model</td><td>Exposed when <strong>Use external clock</strong> is <strong>checked</strong> and<br><strong>Auto-connect to external synchronization if present</strong> is <strong>unchecked</strong> in the <strong>C37.118 Slave</strong> <strong>interface</strong> configuration.</td></tr><tr><td><strong>Epoch</strong></td><td>External clock epoch time value (seconds).</td><td>From model</td><td>Exposed when <strong>Use external clock</strong> is <strong>checked</strong> and<br><strong>Auto-connect to external synchronization if present</strong> is <strong>unchecked</strong> in the <strong>C37.118 Slave</strong> <strong>interface</strong> configuration.</td></tr><tr><td><strong>Nanoseconds</strong></td><td>External clock nanoseconds value.</td><td>From model</td><td>Exposed when <strong>Use external clock</strong> is <strong>checked</strong> and<br><strong>Auto-connect to external synchronization if present</strong> is <strong>unchecked</strong> in the <strong>C37.118 Slave</strong> <strong>interface</strong> configuration.</td></tr></tbody></table>

## Monitoring queues connectable points

These connectable points provide visibility into the internal processing queues of the driver.

<table><thead><tr><th width="130">Connectable name</th><th>Description</th><th width="105">Direction</th><th width="160">Exposure condition</th></tr></thead><tbody><tr><td><strong>Main Queue</strong></td><td>Utilization rate (percentage) of the main processing queue of the driver.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>PMU Queues</strong></td><td>Utilization rate (percentage) of the processing queue associated with each configured PMU (slave).</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

## Slave connectable points

Slave connectable points allow the model to **send measurement data to the driver**, which then transmits the data to the PMU Master.

### Frequency-related connectable points

<table><thead><tr><th width="125">Connectable name</th><th>Description</th><th width="115">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Frequency ROC</strong></td><td>Frequency Rate Of Change value (Hz/s).<br>If the stream format is <strong>INT16</strong>, the value provided by the model is multiplied by 100 by the driver.<br>If the stream format is <strong>FLOAT</strong>, the value is transmitted as is.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Frequency deviation</strong></td><td>Frequency deviation value (mHz).<br>If the stream format is <strong>INT16</strong>, the value is transmitted as is.<br>If the stream format is <strong>FLOAT</strong>, the driver computes the actual frequency by adding the nominal frequency to the frequency deviation (converted from mHz to Hz).</td><td>From model</td><td>Always exposed.</td></tr></tbody></table>

### Phasor connectable points

The number and names of phasor signal connectable points depend on the configuration. Each configured phasor stream is exposed as two distinct connectable points, represented either as **magnitude** and **angle** or as **real** and **imaginary** components, in accordance with the C37.118 Slave interface configuration.

<table><thead><tr><th width="130">Connectable name</th><th width="185">Description</th><th width="105">Direction</th><th width="330">Exposure condition</th></tr></thead><tbody><tr><td><strong>Magnitude</strong></td><td>Phasor magnitude value.</td><td>To model</td><td>Exposed when <strong>Phasors representation</strong> is <strong>POLAR</strong> in the <strong>C37.118 Slave interface</strong> configuration.</td></tr><tr><td><strong>Angle</strong></td><td>Phasor angle value, expressed in radians.</td><td>To model</td><td>Exposed when <strong>Phasors representation</strong> is <strong>POLAR</strong> in the <strong>C37.118 Slave interface</strong> configuration.</td></tr><tr><td><strong>Real part</strong></td><td>Real component of the phasor value.</td><td>To model</td><td>Exposed when <strong>Phasors representation</strong> is <strong>RECTANGULAR</strong> in the <strong>C37.118 Slave interface</strong> configuration.</td></tr><tr><td><strong>Imaginary part</strong></td><td>Imaginary component of the phasor value.</td><td>To model</td><td>Exposed when <strong>Phasors representation</strong> is <strong>RECTANGULAR</strong> in the <strong>C37.118 Slave interface</strong> configuration.</td></tr></tbody></table>

{% hint style="info" %}
**Angle scaling note:**\
If the phasor format is **INT16**, the driver automatically applies a scaling factor of **10⁴**, as defined by the standard. For example, an angle of 3.1222 radians is transmitted as 31222. Most third-party tools (such as PMU Connection Tester and Wireshark) automatically apply the inverse scaling and convert the value to degrees.

If the phasor format is **FLOAT**, no scaling is applied.
{% endhint %}

### Analog and digital signals

Each configured **analog** or **digital** point exposes **a single connectable point**.

<table><thead><tr><th width="155">Connectable name</th><th>Description</th><th width="130">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;Analog name></strong></td><td>Analog value provided by the model for transmission.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>&#x3C;Digital name></strong></td><td>Digital value provided by the model for transmission.</td><td>From 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/communication-protocol-ios/c37.118-slave/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.
