> 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/modbus-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 > Modbus 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-cca3ad0704451f47de68df996c82625d6b2bd6a9%2FDR-rtlab-modsl-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.

## Master-slave connection (TCP only)

When the slave is configured to use **TCP**, an additional **Connected** connectable point becomes available.

<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

### Discrete inputs and input registers

The number and names of discrete input and input register connectable points depend on the configured operations. **Each configured discrete input or input register is exposed as a separate connectable point, using the corresponding name defined in the Modbus Slave interface.**

<table><thead><tr><th width="155">Connectable name</th><th>Description</th><th width="110">Direction</th><th width="165">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;Discrete input name></strong></td><td>Discrete input value written by a Modbus master and mapped to the slave input.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>&#x3C;Input register name></strong></td><td>Input register value written by a Modbus master and mapped to the slave input.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

### Coils and holding registers

The number and names of coil and holding register connectable points depend on the configured operations. **Each configured coil or holding register is exposed as a separate connectable point, using the corresponding name defined in the Modbus Slave interface.**

Coils and holding registers can be configured with one of the following **Control** modes:

* **From Master**\
  Represents a slave input written by a Modbus master and directly mapped to the physical slave output (coil or holding register). The value is returned to the simulation at the beginning of each simulation time step.
* **From Model**\
  Represents a value written by the simulation. This value overwrites the slave output at an interval defined by the **Cycle output ratio** (ms).
* **Both**\
  Enables both master‑ and model‑driven control. When this mode is selected, **two connectable points** are exposed for the operation, one for values written by the Modbus master and one for values written by the simulation.

<table><thead><tr><th width="155">Connectable name</th><th>Description</th><th width="120">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;Coil name> / From master</strong></td><td><strong>Coil</strong> value written by a Modbus master and mapped to the slave input.</td><td>To model</td><td>Exposed when <strong>Control</strong> is set to <strong>From Master</strong> or <strong>Both</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>&#x3C;Holding register> / From master</strong></td><td><strong>Holding register</strong> value written by a Modbus master and mapped to the slave input.</td><td>To model</td><td>Exposed when <strong>Control</strong> is set to <strong>From Master</strong> or <strong>Both</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>&#x3C;Coil name> / From model</strong></td><td><strong>Coil</strong> value written by the simulation and applied to the slave output.</td><td>From model</td><td>Exposed when <strong>Control</strong> is set to <strong>From Model</strong> or <strong>Both</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>&#x3C;Holding register> / From model</strong></td><td><strong>Holding register</strong> value written by the simulation and applied to the slave output.</td><td>From model</td><td>Exposed when <strong>Control</strong> is set to <strong>From Model</strong> or <strong>Both</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr></tbody></table>

## Advanced fault injection (TCP only)

When the slave is configured to use **TCP**, and **Advanced fault injection options** are enabled, additional connectable points are exposed for each Modbus slave.

### Slave availability faults

<table><thead><tr><th width="135">Connectable name</th><th>Description</th><th width="120">Direction</th><th width="205">Exposure condition</th></tr></thead><tbody><tr><td><strong>Slave failure</strong></td><td>Disables connectivity to the TCP Modbus slave when set to <code>1</code>, and enables connectivity when set to <code>0</code>. <strong>Defaults to <code>0</code> when not connected.</strong></td><td>From model</td><td>Exposed when <strong>Slave failure</strong> is <strong>checked</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr></tbody></table>

### Slave response delay faults

<table><thead><tr><th width="135">Connectable name</th><th>Description</th><th width="115">Direction</th><th width="215">Exposure condition</th></tr></thead><tbody><tr><td><strong>Slave delay enable</strong></td><td>Enables response delay injection when set to <code>1</code>, and disables it when set to <code>0</code>. <strong>Defaults to <code>0</code> when not connected.</strong></td><td>From model</td><td>Exposed when <strong>Slave delay</strong> is <strong>checked</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>Slave delay (ms)</strong></td><td>Response delay applied to slave replies (50 ms to 30 000 ms). Delay values are rounded to the nearest power of 5 below 500 ms and to the nearest power of 10 above 500 ms.</td><td>From model</td><td>Exposed when <strong>Slave delay</strong> is <strong>checked</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>Number of delayed replies</strong></td><td>Specifies the number of requests affected by the response delay (<code>0</code> = delay applied indefinitely). The delay counter can be reset by toggling <strong>Slave delay enable</strong> and monitored via <strong>Remaining delayed replies</strong>.</td><td>From model</td><td>Exposed when <strong>Slave delay</strong> is <strong>checked</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>Remaining delayed replies</strong></td><td>Number of delayed replies remaining before the delay is disabled internally.</td><td>To model</td><td>Exposed when <strong>Slave delay</strong> is <strong>checked</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr><tr><td><strong>Slave delay active</strong></td><td>Indicates whether the delay mechanism is currently active.</td><td>To model</td><td>Exposed when <strong>Slave delay</strong> is <strong>checked</strong> in the <strong>Modbus Slave interface</strong> configuration.</td></tr></tbody></table>

{% hint style="danger" %}
These fault‑injection features intentionally disrupt normal Modbus behavior and may cause unexpected or invalid protocol states.
{% endhint %}

## Bus activity (RTU only)

When the slave is configured to use **RTU**, an additional connectable point is available.

<table><thead><tr><th width="135">Connectable name</th><th>Description</th><th width="110">Direction</th><th width="245">Exposure condition</th></tr></thead><tbody><tr><td><strong>Bus Activity</strong></td><td>Indicates whether the Modbus slave is currently receiving requests from a Modbus master.</td><td>To model</td><td>Exposed when <strong>Mode</strong> is set to <strong>RTU</strong> in the <strong>Modbus Slave interface</strong> configuration.</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/modbus-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.
