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

# Requirements, Features & Limitations

## Software requirements

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

## Hardware requirements

TCP and UDP protocols communicate 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, TCP and UDP can also operate over additional Ethernet ports provided by supported PCIe network cards.

## 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 TCP or UDP protocol:

| Feature Name      | Required Status      | Description                                                                    |
| ----------------- | -------------------- | ------------------------------------------------------------------------------ |
| 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 TCP-UDP:**\
1 Boolean status + vector of 3 floats (XYZ position) + vector of 3 floats (XYZ velocity) = **7 data points**
{% endhint %}

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the TCP or UDP protocol.

## Supported features

* Multiple streams:\
  Multiple streams/endpoints, allowing connection to multiple targets/applications/equipment
* User-configurable payload format:\
  UDP datagram or TCP stream payload format is configurable via the configuration interface, allowing matching with the remote transmission and expected format
* Allows controlling of endianness of sent/received data
* Single-client TCP server, TCP client, or UDP operation, using user-configurable local and remote ports
* Automatic reconnection in TCP modes
* NIC binding and NIC speed reconfiguration on Linux targets
* User-configurable decimation factor
* Runtime reception and transmission controls
* Transmission and reception statistics
* IP aliasing (on Linux platforms)
* MSB message serialization for custom data
* Configurable VLAN interface

## Limitations

* NIC binding and speed setting only available on Linux targets.
* Swap endianness only available with byte-aligned data.


---

# 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/tcp-and-udp/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.
