> 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/scpi/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 > SCPI**, 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-4444e2d55e287d209c085831b7f3a22f00fc49e4%2FDR-rtlab-scpi-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.

## Endpoints connection

<table><thead><tr><th width="135">Connectable name</th><th>Description</th><th width="110">Direction</th><th width="165">Exposure condition</th></tr></thead><tbody><tr><td><strong>Connected</strong></td><td>Indicates whether the local endpoint is currently connected to the remote endpoint.<br><code>0</code> = Not connected<br><code>1</code> = Connected</td><td>To model<br></td><td>Always exposed.</td></tr></tbody></table>

## Command signals

The number and names of command connectable points depend on the devices configuration. **Each configured Measurement and Control command is exposed as a separate connectable point, using the command name defined in the SCPI interface. Initial commands** and **Reset commands** do not expose any connectable points.

<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;Measurement name></strong></td><td>Data for the configured measurement command.</td><td>To model<br></td><td>Always exposed.</td></tr><tr><td><strong>&#x3C;Control name></strong></td><td>Data for the configured control command.</td><td>From model</td><td>Always exposed.</td></tr></tbody></table>

## Control and metric

<table><thead><tr><th width="135">Connectable name</th><th width="295">Description</th><th width="125">Direction</th><th width="200">Exposure condition</th></tr></thead><tbody><tr><td><strong>Reception error</strong></td><td><p>Indicates <code>1</code> when an error occurs during the reception of a SCPI response. Two types of errors are reported:</p><ul><li>The SCPI device returns a measurement response that does not contain a numerical value.</li><li>The SCPI device does not respond to a request, in which case the OPAL‑RT SCPI driver automatically attempts to re‑establish the connection with the device.</li></ul></td><td>To model</td><td>Exposed when measurement commands have been configured.</td></tr><tr><td><strong>&#x3C;Measurement name> trigger</strong></td><td>Trigs the <strong>&#x3C;Measurement name></strong> command directly from the model when the trigger value reaches <code>1</code>.</td><td>From model</td><td>Exposed when <strong>Request on trigger</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/scpi/configure-scpi.md#configure-the-device-s-commands"><strong>SCPI</strong></a> <strong>interface</strong> configuration.</td></tr><tr><td><strong>&#x3C;Control name> trigger</strong></td><td>Trigs the <strong>&#x3C;Control name></strong> command directly from the model when the <strong>Send when trigger value is</strong> value defined in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/scpi/configure-scpi.md#configure-the-device-s-commands"><strong>SCPI</strong></a> <strong>interface</strong> is reached.</td><td>From model</td><td>Exposed when <strong>Send on trigger</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/scpi/configure-scpi.md#configure-the-device-s-commands"><strong>SCPI</strong></a> <strong>interface</strong> configuration.<br></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/scpi/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.
