> 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/iec-61850-9-2-sv/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **IEC 61850-9-2 Sampled Values** driver is included by default with <code class="expression">space.vars.Software</code> and does not require any additional installation.

## Hardware requirements

The IEC 61850-9-2 Sampled Values 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, IEC 61850-9-2 Sampled Values can also operate over additional Ethernet ports provided by supported PCIe network cards. Refer to your system’s hardware modularity documentation to determine which external PCIe network and serial 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 IEC 61850-9-2 Sampled Values protocol:

| Feature Name                       | Required Status      | Description                                                                    |
| ---------------------------------- | -------------------- | ------------------------------------------------------------------------------ |
| DP\_IEC61850\_SAMPLED\_VALUES\_PUB | enabled              | Enables IEC 61850 Sampled Values publishing                                    |
| DP\_IEC61850\_SAMPLED\_VALUES\_SUB | enabled              | Enables IEC 61850 Sampled Values subscribing                                   |
| 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 IEC 61850-9-2 Sample Values:**\
A single SV frame containing 4 current samples + 4 voltage samples + 1 sample count + 1 timestamp = **10 data points**.
{% endhint %}

{% hint style="danger" %}
To enable IEC 61850 data‑integrity manipulation, the simulator license must also include the **IEC61850\_SAMPLED\_VALUES\_FAULT\_INJECTION** feature.
{% endhint %}

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the IEC 61850-9-2 Sampled Values protocol.

## Supported features

* SV publishing & subscribing (9‑2LE): The simulator can act as a Merging Unit (publisher) and/or an SV subscriber within an IEC 61850 architecture.
* Merging Unit logical node modeling (9‑2LE): The MU behavior includes the logical nodes TVTR (voltage transformer) and TCTR (current transformer), and can combine three‑phase + neutral currents/voltages into a dataset for SV transmission to subscribing IEDs.
* UCA 9‑2LE profile support: The SV implementation follows IEC 61850‑9‑2LE (UCA International Users Group recommendations), with datasets typically composed of 4 CT/VT and transmitted using 80 or 256 samples per cycle.
* Rate-driven driver execution: SV I/O is computed and sent/received by a driver application running at a frequency determined by the configured sample rate and nominal frequency.
* Publisher value integrity manipulation (I/O interface level): The SV interface supports data integrity manipulation of publisher values (with a noted compatibility limitation—see below).
* SV throughput scalability guidance (9‑2LE): Guidance is provided on how many SV streams can be supported per Ethernet adapter and CPU cores, including automatic driver adaptation that reserves additional cores as streams increase.
* IEC 61869‑9 SV publishing & subscribing: In addition to 9‑2LE, the simulator supports IEC 61869‑9 style SV, where the dataset can include a custom number of current/voltage values (often with quality), and the transmission rate is not limited to 80/256 samples per cycle.
* SCL-based configuration for SV: SV publishing/subscribing is configured by importing an SCL/SCD/ICD file and creating connection points for all attributes within the selected SV dataset.

## Limitations

* Multicast-address-only filtering (9‑2LE): SV subscribers can only filter by multicast address, so two SV messages cannot be published on the same multicast address without subscribers receiving both streams and producing erroneous information.
* Data integrity manipulation compatibility gap: The data integrity manipulation feature is not yet compatible with the IEC 61850 Data Integrity Manipulation component; support is planned for later versions. As a workaround, the feature can still be used by creating connections with other blocks.
* Throughput guideline caveat (mixing traffic): The throughput guidelines explicitly do not consider mixing SV with GOOSE, MMS server, or other protocols on the same Ethernet interface (i.e., real capacity may be lower in mixed-protocol scenarios).


---

# 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/iec-61850-9-2-sv/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.
