> 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/dnp3-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 > DNP3 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-e30e5f0c3bc39cec04363bbb2625a6321b6cd4ce%2FDR-rtlab-dnp3sl-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.

## Analog, binary and double bit binary input signals

These connectable points allow the driver to **receive input values from the model** for analog, binary, and double bit binary points.

<table><thead><tr><th width="155">Connectable name</th><th>Description</th><th width="110">Direction</th><th width="180">Exposure condition</th></tr></thead><tbody><tr><td><strong>Analog input X</strong></td><td>Analog data value provided by the model.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Binary input X</strong></td><td>Binary data value provided by the model.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Double bit binary input X</strong></td><td>Double bit binary data value provided by the model.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

*X corresponds to the index of the point in its associated configuration list.*

## Analog and binary output signals

These connectable points allow the model to **send output commands** to the driver.

<table><thead><tr><th width="115">Connectable name</th><th width="215">Description</th><th width="120">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Analog output X</strong></td><td>Analog output value provided by the model.</td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Binary output X</strong></td><td>Binary output value provided by the model.</td><td>From model</td><td>Exposed when <strong>Operate as trip/close pair</strong> is <strong>unchecked</strong> in the <strong>DNP3 Slave</strong> <strong>interface</strong> configuration.</td></tr><tr><td><strong>Binary output X trip</strong></td><td>Binary data value for the <em>trip</em> command.</td><td>From model</td><td>Exposed when <strong>Operate as trip/close pair</strong> is <strong>checked</strong> in the <strong>DNP3 Slave</strong> <strong>interface</strong> configuration.</td></tr><tr><td><strong>Binary output X close</strong></td><td>Binary data value for the <em>close</em> command.</td><td>From model</td><td>Exposed when <strong>Operate as trip/close pair</strong> is <strong>checked</strong> in the <strong>DNP3 Slave</strong> <strong>interface</strong> configuration.</td></tr></tbody></table>

*X corresponds to the index of the point in its associated configuration list.*


---

# 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/dnp3-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.
