> 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/communication-protocol-ios/iec-61850-8-1-mms/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 **Dashboards > Interfaces > IEC 60850**, under **Simulator Channel:**

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4e18acc0fe55414b91d9b12f9d9b8e936aaad6f9%2FDR-rtlab-mms-connectable.png?alt=media" alt=""><figcaption></figcaption></figure>

Depending on the **connectable point** data **direction**, channels can be mapped to:

* an **OpOutput** block, to **send** data **from the model** to the driver during execution, or
* an **OpInput** block, to **receive and monitor** data from the driver **into the model** during execution

The Simulink model must then be adapted to create matching model connectable points. These points are then connected together using the **Dashboards** interface.

## Time synchronization connectable points

The IEC61850 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="140">Connectable name</th><th width="245">Description</th><th width="115">Direction</th><th width="245">Exposure condition</th></tr></thead><tbody><tr><td><strong>Sync</strong></td><td>Binary synchronization indicator. This connection is not required for MMS.</td><td>From model</td><td>Exposed when <strong>Time synchronization</strong> is set to <strong>Use connection in model</strong> in the <strong>IEC61850 interface</strong> configuration.</td></tr><tr><td><strong>Epoch</strong></td><td>Number of seconds since <strong>Jan 1, 1970 (Unix epoch).</strong> This connection is not required for MMS.</td><td>From model</td><td>Exposed when <strong>Time synchronization</strong> is set to <strong>Use connection in model</strong> in the <strong>IEC61850 interface</strong> configuration.</td></tr><tr><td><strong>Microseconds</strong></td><td><br>This connection is not required for MMS.</td><td>From model</td><td>Exposed when <strong>Time synchronization</strong> is set to <strong>Use connection in model</strong> in the <strong>IEC61850 interface</strong> configuration.</td></tr></tbody></table>

## MMS data point connectable points

The direction and presence of MMS data point connectable points depends mainly on the **functional constraint (FC)** and whether the attribute belongs to a **controllable object**.

### General rule

* Attributes enabled in the IED tree and **not used in reports** expose at least one connectable point **from the model to the driver**.
* If the attribute is **read/write** for MMS clients (typically based on FC), or if it becomes effectively writable due to control behavior, it also exposes a second connectable point **from the driver to the model** to reflect values written/changed externally.

A small set of attributes may become effectively read/write when their data object has **Enable as controllable object = true**, including:

* stVal
* valWTr.posVal
* mxVal.i / mxVal.f
* ctlNum
* origin.orCat / origin.orIdent
* opRcvd, opOk, tOpOk

### MMS data point connectable points

<table><thead><tr><th width="145">Connectable name</th><th>Description</th><th width="120">Direction</th><th width="165">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;full IED path></strong></td><td>Value of an attribute enabled in the IED tree and used outside of reports.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>&#x3C;full IED path> (write)</strong></td><td>Value written or changed externally (by an MMS client) for eligible attributes (based on FC or controllable-object behavior). Suffix “(write)” indicates externally written value feedback.</td><td>To model</td><td>Exposed when attribute is eligible for external write/feedback.</td></tr></tbody></table>

## Reports

Each attribute included in a report data set exposes a connectable point. Naming follows the full IED path format:

**IED / Access point / Logical device / Logical node / Data object / Data attribute**

<table><thead><tr><th width="155">Connectable name</th><th>Description</th><th width="115">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;full IED path></strong></td><td>Value of the corresponding attribute included in the report data set.</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/rt-lab/configure-ios/communication-protocol-ios/iec-61850-8-1-mms/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.
