> 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-60870-5-104-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 **Dashboards > Interfaces > IEC 60870-5-104 Slave**, 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-1b3442af6510311d667cf5748ce7d79a701fab25%2FDR-rtlab-iec104-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.

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://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-7577d22c67cfa74845156f9f7d5e48c1fea3c3c3%2FDR-hyp-iec104-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

## Slave connectable points

The driver exposes a set of connectable points that depends on the **number of configured slaves** and on the **number and type of points configured for each slave**. The following table lists all connectable points available **for a given slave**.

<table><thead><tr><th width="175">Connectable name</th><th>Description</th><th width="125">Direction</th><th width="165">Exposure condition</th></tr></thead><tbody><tr><td><strong>Single point inputs</strong></td><td>Single point values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Single point outputs</strong></td><td>Single point values reported to the master.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Double point inputs</strong></td><td>Double point values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Double point outputs</strong></td><td>Double point values reported to the master.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Regulating step inputs</strong></td><td>Regulating step values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Regulating step outputs</strong></td><td>Regulating step values reported to the master.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Bitstring inputs</strong></td><td>Bitstring values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Bitstring outputs</strong></td><td>Bitstring values reported to the master.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Normalized point inputs</strong></td><td>Normalized point values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Normalized point outputs</strong></td><td>Normalized point values reported to the master.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Scaled point inputs</strong></td><td>Scaled point values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Scaled point outputs</strong></td><td>Scaled point values reported to the master.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Floating‑point inputs</strong></td><td>Floating‑point values controlled by the master.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Floating‑point outputs</strong></td><td>Floating‑point values reported to the master.</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-60870-5-104-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.
