> 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/opc-ua-da/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 > OPCUA Server**, 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-fef888357e5fac50aeaaf6efa9130f89787a1b96%2FDR-rtlab-opcua-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.

## Time synchronization signals

The OPC UA Server driver can use an available synchronization source, ideally provided by an **Oregano Syn1588 PCIe card**. See the **Time Synchronization Driver** section for detailed information. Clock synchronization is handled **manually by the model** via the following connectable points:

<table><thead><tr><th width="135">Connectable name</th><th width="280">Description</th><th width="125">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Timestamp epoch time</strong></td><td>Provides the number of seconds elapsed since <strong>00:00:00 on January 1, 1970 (UTC)</strong>, also known as <strong>Unix time</strong>, <strong>POSIX time</strong>, or <strong>Epoch time</strong>.</td><td>From model</td><td>Exposed when <strong>Use external synchronization</strong> is <strong>checked</strong> in <strong>OPC UA Server interface</strong> configuration.</td></tr><tr><td><strong>Timestamp ns</strong></td><td>Provides the number of nanoseconds within the current second. The value ranges from <strong>0</strong> to <strong>999,999,999</strong> (exclusive) and resets at each new second.</td><td>From model</td><td>Exposed when <strong>Use external synchronization</strong> is <strong>checked</strong> in <strong>OPC UA Server interface</strong> configuration.</td></tr></tbody></table>

## Data signals

The number and names of data signal connectable points depend on the **Points setup** configuration. Each configured data point is exposed as an individual connectable signal, allowing it to be connected independently within the model.

<table><thead><tr><th width="135">Connectable name</th><th width="280">Description</th><th width="160">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Name</strong> as configured</td><td>Data point value with the data type and size defined by the <strong>Type</strong> and <strong>Array length</strong> parameters.</td><td>From model (When <strong>Direction</strong> is set to <strong>Server to client</strong>)</td><td>Exposed for each data point configured.</td></tr><tr><td><strong>Name</strong> as configured</td><td>Data point value with the data type and size defined by the <strong>Type</strong> and <strong>Array length</strong> parameters.</td><td>To model (When <strong>Direction</strong> is set to <strong>Client to server</strong>)</td><td>Exposed for each data point configured.</td></tr></tbody></table>

## Information signals

These connectable points apply to individual data point and allow the model to control data point quality.

<table><thead><tr><th width="145">Connectable name</th><th width="275">Description</th><th width="125">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;Data point</strong> <strong>Name>_quality</strong></td><td>Provides allowing it to be monitored independently by the OPC UA client.</td><td>From model</td><td>Exposed when <strong>Enable quality control</strong> in <strong>OPC UA Server 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/opc-ua-da/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.
