> 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/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **OPC UA Server** driver is included by default with <code class="expression">space.vars.Software</code> and does not require any additional installation.

### OPC DA applications

**OPC DA (classic)** applications **cannot connect directly to the OPC UA Server** and therefore **require an external gateway** to convert OPC UA communication to OPC DA.

### Simulator acting as the server

When the OPAL‑RT simulator acts as the server and an OPC DA client needs to connect, the following product is required:

* **OP3134 – OPC Gateway:** This product enables OPC DA (classic)–based client applications to connect to the OPAL‑RT simulator. It includes the [Cogent DataHub® gateway](https://cogentdatahub.com/products/datahub-opc-gateway/), which converts real‑time streaming OPC UA data to OPC DA. Using this gateway, OPC DA clients can connect to the simulation locally or over the plant network.

### Simulator acting as the client

When the OPAL‑RT simulator acts as the client and needs to connect to external OPC DA or OPC UA server applications, the following product is required:

* **OP3133 – OPC Gateway:** This product enables OPC DA (classic) and OPC UA client applications to connect to the OPAL‑RT simulator. It also includes the [Cogent DataHub® gateway](https://cogentdatahub.com/products/datahub-opc-gateway/), which converts real‑time streaming OPC UA data to OPC DA. Using this gateway, any OPC DA or OPC UA client can connect to the real‑time simulation locally or over the plant network.

## Hardware requirements

The OPC UA Server protocol communicates over Ethernet (TCP/IP) using the simulator’s built-in LAN ports, **eliminating the need for additional hardware**. Standard Ethernet cables are required to establish these connections. For systems requiring extra network interfaces, OPC UA Server can also operate over additional Ethernet ports provided by supported PCIe network cards. Check your hardware modularity options to determine which external PCIe network cards are supported.

## License requirements

### Simulator license

[Verify that an active RT-LAB license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the OPC UA Server protocol:

| Feature Name      | Required Status      | Description                                                                    |
| ----------------- | -------------------- | ------------------------------------------------------------------------------ |
| DP\_OPCUA\_SERVER | enabled              | Enables OPC-UA server                                                          |
| DP\_TOTAL\_NUMBER | 50 enabled (or more) | Number of activated I/O data points for Ethernet-based communication protocols |

{% hint style="info" %}
A **data point** represents any individual value exchanged with the simulator, such as a boolean, integer, analog value, status, coil, register, phasor, quality bit, timestamp, or event. For Ethernet‑based communication protocols, OPAL‑RT licensing counts each **transmitted or received data value** as **one data point**.

**Example for OPC UA Server:**

8 analog values + 6 Boolean values + 2 integer counters + 1 quality/status value = **17 data points**.
{% endhint %}

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the OPC UA Server protocol.

## Supported features

* **Data types:** boolean, int8, uint8, int16, uint16, int32, uint32, int64, uint64, float, double

## Limitations

* **Maximum array length:** 128
* **Security options:** SSL, certificates management, password, etc. are not implemented but can be added easily if it is required by the customer


---

# 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/requirements-features-and-limitations.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.
