> 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/modbus-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-7ea9d6d9967ae5648f835f53701a7b37e3a79b92%2FDR-hyp-modm-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

## Master-slave connection

<table><thead><tr><th width="135">Connectable name</th><th>Description</th><th width="100">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Connected</strong></td><td>Indicates whether the Modbus slave is currently connected.<br><code>0</code> = Not connected<br><code>1</code> = Connected</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

## Operation connectable points

The number and names of operation connectable points depend on the operations configuration. **Each configured operation is exposed as a separate connectable point, using the operation name defined in the Modbus Master interface.**

<table><thead><tr><th width="175">Connectable name</th><th>Description</th><th>Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;Operation name></strong></td><td>Data for the configured operation; type and size depend on the configuration.</td><td>To model (read operation)<br>From model (write operation)</td><td>Always exposed.</td></tr><tr><td><strong>&#x3C;Operation name> / Trigger</strong></td><td>Executes the configured Modbus operation on a <strong>rising edge</strong> (<code>0</code> → <code>1</code>). The trigger must return to <code>0</code> before it can be executed again.</td><td>From model</td><td>Exposed when <strong>Triggered Operation</strong> is <strong>checked</strong> in the <strong>Modbus Master interface</strong> configuration for the operation.</td></tr><tr><td><strong>&#x3C;Operation type>_ErrorCode</strong></td><td>Error code associated with the last execution of the configured operation.</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/hypersim/configure-ios/communication-protocol-ios/modbus-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.
