> 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-goose/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 61850**, 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-906cbf435e292bb2702751fce7531df6ac9b5483%2FDR-rtlab-goose-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="250">Description</th><th width="115">Direction</th><th width="250">Exposure condition</th></tr></thead><tbody><tr><td><strong>Sync</strong></td><td>Binary synchronization indicator. Use <code>1</code> when the timestamp is synchronized to an accurate external source; otherwise use <code>0</code>. Mapped into each GOOSE message time-quality field to indicate timestamp validity.</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>; must increment once per second. Used to timestamp outgoing packets.</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>Microsecond count within the current second.</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>

## GOOSE publishers

GOOSE connectable points are grouped by **Publishers** and **Subscribers**. Each publisher instance exposes settings points plus data-set attribute points.

### Settings

<table><thead><tr><th width="132.3333740234375">Connectable name</th><th>Description</th><th width="114.77783203125">Direction</th><th width="153.4443359375">Exposure condition</th></tr></thead><tbody><tr><td><strong>Settings / Pause</strong></td><td>Controls GOOSE transmission. <code>1</code> suspends transmission; <code>0</code> enables it.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / stNum</strong></td><td>State number. Starts at <code>0</code> and increments whenever any data-set member value changes.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / sqNum</strong></td><td>Sequence number. Starts at <code>0</code> and increments for each GOOSE message sent <strong>without</strong> a data-set change. Resets to <code>0</code> when any data-set change is detected.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / simulation</strong></td><td>Controls the GOOSE header <strong>test</strong> flag. When set to <code>1</code> <strong>(TRUE)</strong>, subscribers are informed the payload represents test data.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / ndsCom</strong></td><td>Controls the GOOSE header <strong>needs commissioning</strong> flag.</td><td>From model</td><td>Always exposed.</td></tr></tbody></table>

### Data (publisher data set attributes)

Each attribute included in the configured GOOSE data set exposes a connectable point. The connectable point name follows the full IED path format:

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

<table><thead><tr><th width="139.00006103515625">Connectable name</th><th>Description</th><th width="114.77783203125">Direction</th><th width="154.555419921875">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;full IED path></strong></td><td>Value of the corresponding data-set attribute published in the GOOSE message.</td><td>From model</td><td>Always exposed.</td></tr></tbody></table>

## GOOSE subscribers

GOOSE connectable points are grouped by **Publishers** and **Subscribers**. Each subscriber instance exposes settings points plus data-set attribute points.

### Settings

<table><thead><tr><th width="132.44451904296875">Connectable name</th><th>Description</th><th width="117">Direction</th><th width="153.22216796875">Exposure condition</th></tr></thead><tbody><tr><td><strong>Settings / Pause</strong></td><td>Controls GOOSE reception. <code>1</code> suspends reception; <code>0</code> enables it.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / stNum</strong></td><td>Received state number. Starts at <code>0</code> and increments when a data-set member change is detected.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / sqNum</strong></td><td>Received sequence number. Increments for each message received without data-set changes; resets to <code>0</code> upon a detected change.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / State</strong></td><td>Reception status code:<br><code>0</code> = reception stopped or first message not yet received<br><code>1</code> = reception operational<br><code>-4</code> = message lost (interval exceeded <strong>TimeAllowedToLive</strong>)<br><code>-5</code> = message out of order (received sqNum/stNum older than previous)<br><code>-14</code> = pcap initialization error (verify NIC name in configuration)</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / simulation</strong></td><td>Value of the received GOOSE header <strong>test</strong> flag. <code>1</code> <strong>(TRUE)</strong> indicates payload is test data.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Settings / Header simulated bit</strong></td><td>Value of the simulation bit in the Reserved 1 header field. <code>1</code> indicates the data is considered to be sent by a simulated device.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

### Data (subscriber data set attributes)

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

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

<table><thead><tr><th width="147">Connectable name</th><th width="275">Description</th><th>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 received data-set attribute.</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/rt-lab/configure-ios/communication-protocol-ios/iec-61850-8-1-goose/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.
