> 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-8-1-goose/configure-iec-61850-8-1-goose-specific-settings.md).

# Configure IEC 61850-8-1 GOOSE 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‑8‑1 GOOSE specific settings.

## Continue configuring the IEC 61850 I/O interface

{% stepper %}
{% step %}

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

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.

1. 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-f16075022f553c780b400abe3a343b033bbcca70%2FDR-rtlab-goose-info.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="131">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>

2. Expand **Access Points** and their submenus to view their content. An Access Point defines the Ethernet interface through which an IED publishes and subscribes to GOOSE messages. An IED may expose one or multiple Access Points, each mapped to a distinct network interface. Every GOOSE control block is bound to a single Access Point, which determines the Layer‑2 context used for GOOSE communication, including the physical interface and multicast scope. Reviewing the Access Point is required to identify where GOOSE frames are sent and received and how traffic is separated when multiple networks are used.
3. Click **Data sets** to view their content. A data set defines a list of **Functional Constrained Data Attributes (FCDAs)** used by the IED’s control blocks (GOOSE, Sampled Values, or Reports). This view is **read‑only**: no items can be added or removed manually. It is intended to help you understand how attributes are grouped and used by the IED.

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

<table data-header-hidden><thead><tr><th width="125"></th><th></th></tr></thead><tbody><tr><td><strong>Node path</strong></td><td>Full path of the node within the IED. The format is IED / Access point / Logical device / Logical node.<br>The items referenced in the <strong>Data object</strong> and <strong>Data attribute</strong> columns are part of this node.</td></tr><tr><td><strong>Data object</strong></td><td>Data object referenced by the FCDA.<br>If set to <em>&#x3C; all ></em>, all attributes matching the criteria in the <strong>Data attribute</strong> and <strong>Functional constraint</strong> columns are selected.<br>If <strong>Data attribute</strong> is also set to <em>&#x3C; all ></em>, then all attributes that are part of the node referenced in the <strong>Node path</strong> column and have FC equal to the value in the <strong>Functional constraint</strong> column are selected.</td></tr><tr><td><strong>Data attribute</strong></td><td>Data attribute referenced by the FCDA.<br>If set to <em>&#x3C; all ></em>, all attributes that are in the data object referenced in the <strong>Data object</strong> column and have FC equal to the value in the <strong>Functional constraint</strong> column are selected.<br>If <strong>Data object</strong> is also set to <em>&#x3C; all >,</em> then all attributes that are part of the node referenced in the <strong>Node path</strong> column and have FC equal to the value in the <strong>Functional constraint</strong> column are selected.</td></tr><tr><td><strong>Functional constraint</strong></td><td>Main criteria used for selecting attributes from the location specified in the other columns.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage and configure GOOSE items

Expand the **GOOSE** folder to display all available GOOSE items. These items are automatically created when SCL/SCD/ICD files containing GOOSE message definitions are imported. GOOSE item can be removed by deleting the publishing IED from the IED list or by removing the SCL file where the GOOSE message is defined from the SCL/SCD/ICD files list.

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

Change parameters as desired:

{% tabs %}
{% tab title="General" %}
This section provides read‑only information extracted from the SCL file.

<table><thead><tr><th width="220">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>GOOSE ID</strong></td><td>Unique identifier of the GOOSE message.</td></tr><tr><td><strong>GOOSE control block name</strong></td><td>Name of the GOOSE Control Block (GoCB) associated with this message.</td></tr><tr><td><strong>GOOSE path</strong></td><td>Full hierarchical path of the GoCB inside the IED.</td></tr><tr><td><strong>Dataset</strong></td><td>Name of the dataset referenced by the GoCB.</td></tr><tr><td><strong>Dataset path</strong></td><td>Full path of the dataset inside the IED.</td></tr><tr><td><strong>Description</strong></td><td>Description of the GOOSE message (from the SCL file).</td></tr><tr><td><strong>Configuration revision</strong></td><td>Configuration revision number (ConfRev) from the SCL definition.</td></tr></tbody></table>
{% endtab %}

{% tab title="Publish" %}
This section configures the **publishing** of the GOOSE message.

<table><thead><tr><th width="200">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable publishing</strong></td><td>Enables publication of the GOOSE message. When enabled, the corresponding connection points are created and publishing begins at simulation start.</td></tr><tr><td><strong>Publishing Ethernet adapter</strong></td><td>Network interface used to publish GOOSE frames. Select an adapter based on <code>ifconfig</code> (Linux) or <code>ipconfig</code> (Windows) output.</td></tr><tr><td><strong>Publishing IED</strong></td><td>Name of the publishing IED. This field is read‑only.</td></tr></tbody></table>
{% endtab %}

{% tab title="Subscribe" %}
This section configures **subscription** to the GOOSE message.

<table><thead><tr><th width="175">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable subscribing</strong></td><td>Enables subscription to the GOOSE message. When enabled, the corresponding connection points are created and subscription begins at simulation start.</td></tr><tr><td><strong>Subscribing Ethernet adapter</strong></td><td>Network interface used to receive GOOSE frames. Select an adapter based on <code>ifconfig</code> (Linux) or <code>ipconfig</code> (Windows) output.</td></tr><tr><td><strong>Subscribing IED</strong></td><td>List of IEDs intended to subscribe to the message. This list is user‑defined and may contain multiple entries. <em>(Note: This field is not used during real‑time simulation.)</em></td></tr></tbody></table>
{% endtab %}

{% tab title="GSE elements" %}
This section contains parameters specific to GOOSE messaging.

<table><thead><tr><th width="145">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>MAC address</strong></td><td>Destination multicast MAC address for the GOOSE message (e.g., <code>01-0C-CD-04-00-00</code>). Pre-filled from the SCL file; user‑editable. Must follow the format <code>xx-xx-xx-xx-xx-xx</code>.</td></tr><tr><td><strong>App ID</strong></td><td>Application ID of the GOOSE message. Pre-filled from SCL and must be unique in the IEC 61850 network. This field is read‑only.</td></tr><tr><td><strong>VLAN ID</strong></td><td>VLAN identifier (1–4095). Used only if <strong>Enable use of VLAN for SV and GOOSE telegrams</strong> is enabled in the general configuration. Pre-filled from SCL; user‑editable.</td></tr><tr><td><strong>VLAN priority</strong></td><td>VLAN priority (1–7). Used only if VLAN support is enabled. Pre-filled from SCL; user‑editable.</td></tr><tr><td><strong>Min duration [ms]</strong></td><td>Minimum retransmission interval following a dataset change. Pre-filled from SCL; defaults to 62.5 ms if unspecified. User‑editable.</td></tr><tr><td><strong>Max duration [ms]</strong></td><td>Maximum retransmission interval when no dataset changes occur. Pre-filled from SCL; defaults to 1000 ms if unspecified. User‑editable.</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-8-1-goose/configure-iec-61850-8-1-goose-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.
