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

# Requirements, Features & Limitations

## Software requirements

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

## Hardware requirements

The C37.118 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, C37.118 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 C37.118 master protocol:

| Feature Name         | Required Status      | Description                                                                    |
| -------------------- | -------------------- | ------------------------------------------------------------------------------ |
| DP\_C37\_118\_MASTER | enabled              | Enables C37118 Master                                                          |
| 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 C37.118:**\
One PMU reporting 3 voltage phasors + 3 current phasors + frequency + ROCOF + timestamp = **9 data points**.
{% endhint %}

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the C37.118 master protocol.

## Supported features

* Supports simulation on Windows and Linux
* IEEE Std C37.118.2-2011 compliant
* One driver instance can connect many PMUs
* Supports TCP only, UDP only or TCP and UDP
* Supports binding to a specific network interface
* Supports automatic data request or manual start of data transmission
* Supports automatic handling of phasor factor and digital masks
* Supports RTA mode simulation on Windows systems
* Support legacy configuration mode (using .io and .opal configuration files).

## Limitations

* It operates asynchronously from the model simulation step. It will try to receive data as fast as possible and provide it to the simulation.
* It needs to be configured manually by knowing in advance how the PMU is configured.
* It cannot receive PMU configuration frame 3 (CFG-3).
* It cannot receive encrypted data (SSL)


---

# 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/c37.118-master/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.
