> 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/configure-iec-61850-9-2-sv-specific-settings.md).

# Configure IEC 61850-9-2 SV Specific Settings

Once the general settings are configured, the SCL/SCD/ICD files are added, and the IED has been reviewed, proceed with configuring the IEC 61850‑9-2 SV specific settings.

## Continue configuring the IEC 61850 I/O interface

{% stepper %}
{% step %}

### Review the IED(s) information for SV

Expand the **IED** folder to display all available IEDs. In most cases, the IEDs shown in the list below are imported directly from the SCL/SCD/ICD files provided in the **SCL/SCD/ICD files** section.

Click any IED in the list to view the source file from which it was imported:

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-0bc69f9b153ee0c26c1e3e74050f3713adcfd06a%2FDR-rtlab-sv-template.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="130">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>File name</strong></td><td>The file from which the IED information was extracted from.<br>= N/A (IED added manually) when IED was added manually.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Review and manage SV items

Click the **Sampled Values** folder to display all available SV items. These entries are created automatically when SCL/SCD/ICD files containing SV message definitions are imported. The list may include both supported SV types, **IEC 61850‑9‑2LE** and **IEC 61869‑9**, but they are added and removed in different ways.

**SV 9‑2LE**\
9‑2LE Sampled Values items are **manually created** by the user.

* To add a 9‑2LE SV stream, click the **+** button.
* To remove an item, select it and click the **–** button.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-a684753b2f5a6bc6ea6387066ea2d3ba5371ebd4%2FDR-rtlab-sv-items.png?alt=media" alt=""><figcaption></figcaption></figure>

This reflects the fact that 9‑2LE SV streams are not defined in SCL files and must be configured explicitly.

**SV IEC 61869‑9**\
IEC 61869‑9 Sampled Values items are created **automatically** when their definitions are parsed from SCL/SCD/ICD files.

* These items **cannot** be manually added or removed.
* To remove an IEC 61869‑9 SV element, you must either remove its publishing IED from the IED list, or remove the SCL file containing the SV definition from the SCL/SCD/ICD file list.

This ensures consistency with the SCL-defined SV Control Blocks and associated datasets.
{% endstep %}

{% step %}

### Configure SV items

Expand the **Sampled Values** folder and select an SV item to display its configuration parameters. The list may include Sampled Values of both supported types, namely **IEC 61850 9‑2LE** and **IEC 61869 9**, and each type follows a different configuration workflow.

The following section describes the parameters available for **SV 9‑2LE**. Modify the values as required and save the configuration once all changes are complete.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-857b9f3fea2a1e065cf1564733e6fe64323835a8%2FDR-rtlab-sv-item-conf.png?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General" %}

<table><thead><tr><th width="140">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>SV ID</strong></td><td>The unique identification of the SV message. Recommended format per IEC 61850‑9‑2LE: <em>xxxxMUnn</em> (substation-voltage-bay + measuring point number).</td></tr><tr><td><strong>SV type</strong></td><td>Fixed to <strong>9‑2LE</strong> (non-editable).</td></tr><tr><td><strong>Sampling rate</strong></td><td>Number of transmitted or received samples per cycle, associated with the SV message (typically 80 or 256 samples/cycle).</td></tr><tr><td><strong>Nominal frequency</strong></td><td>Power system frequency associated with the SV message.</td></tr><tr><td><strong>Configuration revision</strong></td><td>Configuration revision number of the SV message.</td></tr><tr><td><strong>Number of ASDU</strong></td><td>Number of samples embedded in each packet of the SV message. Automatically determined: 1 ASDU for 80 samples/cycle, 8 for 256 samples/cycle (non‑editable).</td></tr></tbody></table>
{% endtab %}

{% tab title="Publish" %}

<table><thead><tr><th width="210">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable publishing</strong></td><td>Enables creation of publishing connection points. It also ensures that publishing starts as soon as the simulation starts.</td></tr><tr><td><strong>Publishing Ethernet adapter</strong></td><td>Network interface name used to publish the SV message.</td></tr><tr><td><strong>Publishing IED</strong></td><td>Name of the IED publishing the SV message (not used in real‑time simulation).</td></tr></tbody></table>
{% endtab %}

{% tab title="Subscribe" %}

<table><thead><tr><th width="210">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable subscribing</strong></td><td>Enables creation of subscribing connection points. It also ensures that subscription starts as soon as the simulation starts.</td></tr><tr><td><strong>Subscribing Ethernet adapter</strong></td><td>Network interface name used to subscribe to the SV message.</td></tr><tr><td><strong>Subscribing IEDs</strong></td><td>List of subscribing IED (not used in real‑time simulation).</td></tr></tbody></table>
{% endtab %}

{% tab title="SV elements" %}

<table><thead><tr><th width="170">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>MAC address</strong></td><td>MAC multicast destination address associated with the SV message. First 8 digits pre‑filled; full address can be overridden.</td></tr><tr><td><strong>AppID</strong></td><td>Fixed to <strong>0x4000</strong> (non‑editable).</td></tr><tr><td><strong>VLAN ID</strong></td><td>Editable (1–4095), used only if VLAN option enabled.</td></tr><tr><td><strong>VLAN priority</strong></td><td>Editable (1–7), used only if VLAN option enabled.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

The following section describes the parameters available for **SV 9‑2LE**. Modify the values as required:

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-76bcc537c19a970e142b7418e6156186b3c305cf%2FDR-rtlab-sv-param.png?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General" %}

<table><thead><tr><th width="140">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>SV ID</strong></td><td>The unique identification of the SV message.<br>Read‑only; defined in SCL.</td></tr><tr><td><strong>SV control block name</strong></td><td>Name of the control block describing the SV message.<br>Read‑only; defined in SCL.</td></tr><tr><td><strong>SV path</strong></td><td>Path of the SV control block within the IED.<br>Read‑only; defined in SCL.</td></tr><tr><td><strong>SV type</strong></td><td>Fixed to <strong>IEC 61869‑9</strong> (non-editable).</td></tr><tr><td><strong>Sampling rate</strong></td><td>Number of transmitted or received samples per cycle, associated with the SV message.<br>Read‑only; defined in SCL (may be any rate, not limited to 80/256).</td></tr><tr><td><strong>Nominal frequency</strong></td><td>Power system frequency associated with the SV message.</td></tr><tr><td><strong>Dataset</strong></td><td>Name of the dataset used by the SV message.<br>Read‑only; defined in SCL.</td></tr><tr><td><strong>Dataset path</strong></td><td>Full path within the IED of the dataset used by the SV message.<br>Read‑only; defined in SCL.</td></tr><tr><td><strong>Description</strong></td><td>Description of the SV message. Read‑only; from SCL.</td></tr><tr><td><strong>Configuration revision</strong></td><td>Configuration revision number of the SV message.</td></tr><tr><td><strong>Number of ASDU</strong></td><td>Number of samples embedded in each packet of the SV message. Read‑only; defined in SCL.</td></tr></tbody></table>
{% endtab %}

{% tab title="Publish" %}

<table><thead><tr><th width="185">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable publishing</strong></td><td>Enables creation of publishing connection points. It also ensures that publishing starts as soon as the simulation starts.</td></tr><tr><td><strong>Publishing Ethernet adapter</strong></td><td>Network interface name used to publish the SV message.</td></tr><tr><td><strong>Publishing IED</strong></td><td>Name of the IED publishing the SV message. Read‑only; determined by SCL (required for real‑time simulation).</td></tr></tbody></table>
{% endtab %}

{% tab title="Subscribe" %}

<table><thead><tr><th width="210">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable subscribing</strong></td><td>Enables creation of subscribing connection points. It also ensures that subscription starts as soon as the simulation starts.</td></tr><tr><td><strong>Subscribing Ethernet adapter</strong></td><td>Network interface name used to subscribe to the SV message.</td></tr><tr><td><strong>Subscribing IEDs</strong></td><td>List of subscribing IED (not used in real‑time simulation).</td></tr></tbody></table>
{% endtab %}

{% tab title="SV elements" %}

<table><thead><tr><th width="170">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>MAC address</strong></td><td>MAC multicast destination address associated with the SV message. Pre‑filled from SCL but <strong>editable</strong> if needed.</td></tr><tr><td><strong>AppID</strong></td><td>Read‑only; filled from SCL; must be unique in the IEC 61850 network.</td></tr><tr><td><strong>VLAN ID</strong></td><td>Pre‑filled from SCL but editable if VLAN option enabled.</td></tr><tr><td><strong>VLAN priority</strong></td><td>Pre‑filled from SCL but editable if VLAN option enabled.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Save the configuration

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-44bd03ce3c41f8ba5c990b61c29b38c9b80ae5f2%2FDR-rtlab-save.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

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