> 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-master/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-f0562cba2905ec5fa27e58b6d671b72e16c3e822%2FDR-hyp-c37-1.png?alt=media" alt="" width="334"><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

## Master connectable points

The following connectable points are exposed by the C37.118 Master to exchange status, timing, and measurement information with the model.

<table><thead><tr><th width="125">Connectable name</th><th width="350">Description</th><th width="110">Direction</th><th width="160">Exposure condition</th></tr></thead><tbody><tr><td><strong>Frequency ROC</strong></td><td>Rate of change of frequency sent by the PMU, as defined in IEEE Std C37.118.2-2011, Section 4.3.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Frequency</strong></td><td>Frequency measurement sent by the PMU, as defined in IEEE Std C37.118.2-2011, Section 6.2.2.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Epoch time (sec)</strong></td><td>Epoch time (seconds) sent by the PMU, as defined in IEEE Std C37.118.2-2011, Section 6.2.2.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Fraction of second (ns)</strong></td><td>Fraction of second timestamp (nanoseconds) sent by the PMU, as defined in IEEE Std C37.118.2-2011, Section 6.2.2.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Clock locked</strong></td><td>Time quality indicator as defined in IEEE Std C37.118.2-2011, Section 6.2.2.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Timebase</strong></td><td>Resolution of the fraction-of-second timestamp, as defined in IEEE Std C37.118.2-2011, Section 6.4.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Status</strong></td><td>Connection status of the PMU:<br><code>0</code> = Connected<br><code>1</code> = Disconnected<br><code>2</code> = Receiving<br><code>3</code> = Error</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Error</strong></td><td>Error state of the Master–PMU communication:<br><code>0</code> = No error<br><code>1</code> = PMU unreachable<br><code>2</code> = Communication timeout<br><code>3</code> = Received PMU ID different than expected</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Mismatch</strong></td><td>Indicates whether there is a mismatch between the remote PMU and the PMU configured in the Master:<br><code>0</code> = No mismatch<br><code>1</code> = Mismatch detected<br>When a mismatch is detected, additional details are available in the <strong>Diagnostics</strong> tab of the Target display. The Diagnostics tab must be set to <strong>exhaustive mode</strong>. Mismatch information is only reported at model reset.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Enable reception of data</strong></td><td>Enables or disables PMU data transmission. When the value changes from <code>0</code> to <code>1</code>, the Master sends a command to start data transmission. When it changes from <code>1</code> to <code>0</code>, the Master sends a command to stop data transmission.</td><td>From model</td><td>Exposed when <strong>Enable reception of data</strong> is <strong>unchecked</strong> in the <strong>C37.118 Master interface</strong> configuration.</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 Master interface configuration.

<table><thead><tr><th width="125">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 Master 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 Master 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 Master 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 Master interface</strong> configuration.</td></tr></tbody></table>

## Analog signals

For a given stream, each configured analog signal is exposed as two distinct connectable points: the **analog value** itself and an associated **scaling factor**. Because IEEE Std C37.118 does not define how analog factors must be applied, it is the user’s responsibility to apply the factor appropriately, either by multiplying or dividing the analog value by the factor provided to the model.

<table><thead><tr><th width="140">Connectable name</th><th width="345">Description</th><th width="100">Direction</th><th width="165">Exposure condition</th></tr></thead><tbody><tr><td><strong>Value</strong></td><td>Raw analog value received from the PMU.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Factor</strong></td><td>Scaling factor associated with the analog value.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

## Digital signals

For a given stream, each configured digital signal is exposed as **16 individual connectable points**, corresponding to the **16 bits** of the digital word.

<table><thead><tr><th width="165">Connectable name</th><th>Description</th><th width="100">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Digital bit [0–15]</strong></td><td>Individual bit state of the 16-bit digital value.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Normal state status word</strong></td><td>Normal status word of the digital signal.</td><td>To model</td><td>Exposed when <strong>Enable reception of normal bit states</strong> is <strong>checked</strong> in the <strong>C37.118 Master interface</strong> configuration.</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-master/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.
