> 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-general-settings.md).

# Configure IEC 61850 General Settings

When working with communication protocols, it is recommended to begin by configuring the protocol through the **I/O Interfaces** section in <code class="expression">space.vars.Software</code> before proceeding with other steps

## Configure the IEC 61850 I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

In RT-LAB Project Explorer, right-click **I/O Interfaces**, select **New I/O Interface**, and choose **IEC 61850**. Double-click the newly created interface to begin configuration.
{% endstep %}

{% step %}

### Configure the general settings

In the **Folders** list, click **General** and configure the general settings.

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

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Time synchronization</strong></td><td>Synchronization method used for all GOOSE and SV messages.<br><strong>Poll CPU clock:</strong> Uses the simulator’s system clock to compute protocol timings.<br><strong>Use connection in model:</strong> Synchronizes timings with an external clock provided through connection points. Required when using Spectracom TSync or Oregano boards.<br><strong>Poll synchronization hardware:</strong> Automatically detects and uses a supported synchronization device. Currently supported only with the Oregano Syn1588 PCIe card.</td></tr><tr><td><strong>Use an RT core for the MMS server</strong></td><td><strong>Checked:</strong> Reserves a dedicated real-time CPU core for for MMS server operations.<br><strong>Unchecked:</strong> Defaults to core 0.</td></tr><tr><td><strong>Enable fixed‑length encoding for GOOSE messages (61850‑8‑1 Ed.2 A.3)</strong></td><td><strong>Checked:</strong> GOOSE messages use fixed‑length encoding as defined in IEC 61850‑8‑1 Ed.2 A.3, disabling ASN.1 dynamic length compression for selected headers and data types.<br><strong>Unchecked:</strong> Standard ASN.1 variable‑length encoding is used.</td></tr><tr><td><strong>Enable simulation flag (Reserved 1) in every SV and GOOSE telegram</strong></td><td><strong>Checked:</strong> Sets the “simulation” bit in the Reserved 1 field of every outgoing SV and GOOSE message, marking them as simulation data.<br><strong>Unchecked:</strong> Messages are transmitted without the simulation flag set.</td></tr><tr><td><strong>Enable use of VLAN for SV and GOOSE telegrams</strong></td><td><strong>Checked:</strong> All SV and GOOSE frames are VLAN‑tagged using the configured VLAN ID (default values imported from SCL for GOOSE and IEC 61869‑9 SV).<br><strong>Unchecked:</strong> SV and GOOSE frames are sent without VLAN tags.</td></tr><tr><td><strong>Enable Sampled Values data integrity manipulation</strong></td><td><strong>Checked:</strong> Enables data‑integrity manipulation tools for SV 9‑2LE message transmission. The simulator license must also include the <strong>IEC61850_SAMPLED_VALUES_FAULT_INJECTION</strong> feature.<br><strong>Unchecked:</strong> Data integrity manipulation features are disabled.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage **SCL/SCD/ICD files**: add, remove, update, or reorder

Click **SCL/SCD/ICD files** and use:

* **+** icon to a add file, then click **Select SCL/ICD/CID file** and browse to the desired file
* **–** icon to remove a file
* **Arrow** icons to reorder a file

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

When a file **is added**, <code class="expression">space.vars.Software</code> parses it and extracts **all IED definitions**, including their data model, their datasets, and all **GOOSE**, **Sampled Values**, and **Report** control blocks. Each imported file is copied into the project’s `scl/` folder. If, on the next <code class="expression">space.vars.Software</code> launch, the original file is missing, the interface automatically falls back to the backup copy in that folder.

**Removing** a file deletes **all IEDs originating from it**, along with their data models, datasets, and control blocks.

When **replacing** an existing entry with a **modified version** of the same file, or a **different file entirely**, <code class="expression">space.vars.Software</code> uses a **change‑detection mechanism** to help determine how user‑editable parameters should be handled:

<details>

<summary>Details about updating an SCL file entry</summary>

**SCL file change workflow**

1\. Click on a valid entry to browse and select an SCL file (the same or different). This will bring up the refresh menu, asking how to proceed with the configuration's editable parameters that originated from the initial SCL file. The parameters affected by this choice are the ones marked as **keep or reset** in the table below, in the **Updating common elements** section.

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

**Keep all modified values:** The values of the editable parameters that originated from the initial SCL file will be unaltered. This will ensure that any user modifications are maintained.

**Reset all modified values:** The values of the editable parameters that originated from the initial SCL file will be reset to the values found in the new file. All user modifications will be lost.

2\. Select the type of refresh and click **OK***.* A pop-up window will appear, listing all the changes and requesting user input on whether or not to apply them.

3\. Click **Yes** to apply the changes.

**Detecting changes within IED**

The unique identifier of an IED is its name. Therefore, if its name is no longer found in the new file, the IED in question will be removed; conversely, new IED can be added as a result of parsing the new file. The same principle applies to all layers of the data model: access points, logical devices, logical nodes, data objects and data attributes.\
For data sets, their unique identifier is their full path within the IED. For FCDA, the identifier is considered to be the combination of their parameters: node path, data object, data attribute and functional constraint.

This is best illustrated in the two examples below:

**Example 1:** SCL file A contains information about IED1 and IED2; SCL file B contains information about IED2 and IED3. When file A is changed for file B, the following happens:

* IED1 along with its data model, data sets and control blocks will be removed: it was part of file A, but not part of file B
* IED2 will be kept: it was part of both files
* IED3 along with its data model, data sets and control blocks will be added: it was not part of file A, but it is part of file B

**Example 2:** Starting with the same two files as above, assume IED2's definition in file A contains a logical device LD10. In file B, IED2's definition sees this logical device change name from LD10 to LD20. When file A is changed for file B, the following happens in the structure of IED2:

* LD10 will be removed along with its logical nodes, and consequently its data objects and attributes
* LD20 will be added with its own structure of nodes, data objects and attributes

Note that the same principle applies if a file is refreshed i.e. its own content is re-applied after a modification.

**Detecting changes within control blocks**

A GOOSE, SV or Report control block is considered the same either if its ID is the same or if its path within the IED is the same. Let's look at a few examples:

**Example 3:** Keeping with the same setup as in the examples above, assume IED2 (which was found in both files A and B) has a GOOSE control block that changed its ID from GoID10 to GoID20. Its name and path within the IED have not changed.\
In this scenario, the GOOSE control block will be considered the same and its ID will be successfully changed to GoID20.

**Example 4:** Now assume that IED2 has another GOOSE control block, whose ID is the same in both files but whose name has changed from gcb\_name30 to gcb\_name40. As a result, its path within the IED is considered changed.\
In this scenario, as in the one above, the GOOSE control block will be considered the same and its name will be successfully changed to gcb\_name40.

**Example 5:** In file A, GOOSE message with ID GoID50 was defined within IED2; However, in file B, GoID50 is now part of IED3. As in the example above, the GOOSE ID is unchanged, but the path is different.\
Again, the GOOSE control block will be considered the same and its path will be successfully updated to show that it is published by IED3.

**Example 6:** Finally, according to file A, IED2 is publishing a GOOSE message with ID GoID60; according to file B, there no longer is any IED publishing a GOOSE message with that ID.\
Moreover, according to file B, IED2 is now publishing a GOOSE message with ID GoID70, which was not previously defined in file A.\
When file A is changed for file B, the following happens:

* GOOSE message with ID GoID60 (published by IED2) will be removed from the configuration: it was part of file A, but not part of file B
* GOOSE message with ID GoID70 (published by IED2) will be added to the configuration: it was not part of file A, but it is part of file B

**Updating common elements**

The parameters of the elements that were deemed common to both files according to the constraints explained above (such as IED2 in the examples) can be divided into 3 categories:

* **keep**: applies to parameters that did not originate from an SCL file, such as the MMS server configuration parameters. The values of these parameters will remain unaltered during SCL file changes
* **reset**: applies to **read-only** parameters that did originate from an SCL file, such as the dataset path of GOOSE items. Their value will be reset to the value found in the new SCL file
* **keep or reset**: applies to **editable** parameters that did originate from an SCL file, such as the MAC address of GOOSE items. Their value can be either kept or reset, depending on the user preference

The table below shows how each parameter is handled during an SCL file change. Each column represents a section of the I/O interface.

| IED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | GOOSE                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | SV (IEC 61869-9 only)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Reports                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>In the generic section:</p><ul><li><em>Name</em> → <strong>reset</strong></li><li><em>File name</em> → <strong>reset</strong></li></ul><p>In the <em>MMS sever configuration</em> section:</p><ul><li><em>NIC name</em> → <strong>keep</strong></li><li><em>IP address</em> → <strong>keep</strong></li><li><em>TCP port</em> → <strong>keep</strong></li></ul><p>In the data model section, only applicable parameters are in the data attributes:</p><ul><li><em>Name</em> → <strong>reset</strong></li><li><em>Functional constraint</em> → <strong>reset</strong></li><li><em>Data set reference(s)</em> → <strong>reset</strong></li><li><em>Control block reference(s)</em> → <strong>reset</strong></li><li><em>Add MMS data point</em> → <strong>keep</strong></li></ul><p>The information below applies only if the FC (Functional Constraint) was and remained MX (measurement):</p><ul><li><em>Output RMS</em> → <strong>keep</strong></li><li><em>RMS number of samples</em> → <strong>keep</strong></li><li><em>RMS gain</em> → <strong>keep</strong></li></ul><p>In the <em>Data sets</em> section, FCDAs can only be flagged as added or removed. This happens when the combination of node path, data object, data attribute and functional constraint cannot be found in both files.<br>Therefore, it can be said that the entire contents of a data set is reset. For each FCDA of the data set:</p><ul><li><em>Node path</em> → <strong>reset</strong></li><li><em>Data object</em> → <strong>reset</strong></li><li><em>Data attribute</em> → <strong>reset</strong></li><li><em>Functional constraint</em> → <strong>reset</strong></li></ul> | <p>In the <em>General</em> section:</p><ul><li><em>GOOSE ID</em> → <strong>reset</strong></li><li><em>GOOSE control block name</em> → <strong>reset</strong></li><li><em>GOOSE path</em> → <strong>reset</strong></li><li><em>Dataset</em> → <strong>reset</strong></li><li><em>Dataset path</em> → <strong>reset</strong></li><li><em>Description</em> → <strong>reset</strong></li><li><em>Configuration revision</em> → <strong>reset</strong></li></ul><p>In the <em>Publish</em> section:</p><ul><li><em>Enable publishing</em> → <strong>keep</strong></li><li><em>Publishing Ethernet adapter</em> → <strong>keep</strong></li><li><em>Publishing IED</em> → <strong>reset</strong></li></ul><p>In the <em>Subscribe</em> section:</p><ul><li><em>Enable subscribing</em> → <strong>keep</strong></li><li><em>Subscribing Ethernet adapter</em> → <strong>keep</strong></li><li><em>Subscribing IED</em> → <strong>keep</strong><br>(IED that were removed during the file change will also be removed from this field)</li></ul><p>In the <em>GSE elements</em> section:</p><ul><li><em>MAC address</em> → <strong>keep or reset</strong></li><li><em>App ID</em> → <strong>reset</strong></li><li><em>VLAN ID</em> → <strong>keep or reset</strong></li><li><em>VLAN priority</em> → <strong>keep or reset</strong></li><li><em>Min duration \[ms]</em> → <strong>keep or reset</strong></li><li><em>Max duration \[ms]</em> → <strong>keep or reset</strong></li></ul> | <p>In the <em>General</em> section:</p><ul><li><em>SV ID</em> → <strong>reset</strong></li><li><em>SV control block name</em> → <strong>reset</strong></li><li><em>SV path</em> → <strong>reset</strong></li><li><em>SV type</em> → <strong>reset</strong></li><li><em>Sampling rate</em> → <strong>reset</strong></li><li><em>Nominal frequency</em> → <strong>keep</strong></li><li><em>Dataset</em> → <strong>reset</strong></li><li><em>Dataset path</em> → <strong>reset</strong></li><li><em>Description</em> → <strong>reset</strong></li><li><em>Configuration revision</em> → <strong>reset</strong></li><li><em>Number of ASDU</em> → <strong>reset</strong></li></ul><p>In the <em>Publish</em> section:</p><ul><li><em>Enable publishing</em> → <strong>keep</strong></li><li><em>Publishing Ethernet adapter</em> → <strong>keep</strong></li><li><em>Publishing IED</em> → <strong>reset</strong></li></ul><p>In the <em>Subscribe</em> section:</p><ul><li><em>Enable subscribing</em> → <strong>keep</strong></li><li><em>Subscribing Ethernet adapter</em> → <strong>keep</strong></li><li><em>Subscribing IED</em> → <strong>keep</strong><br>(IED that were removed during the file change will also be removed from this field)</li></ul><p>In the <em>SV elements</em> section:</p><ul><li><em>MAC address</em> → <strong>keep or reset</strong></li><li><em>App ID</em> → <strong>reset</strong></li><li><em>VLAN ID</em> → <strong>keep or reset</strong></li><li><em>VLAN priority</em> → <strong>keep or reset</strong></li></ul> | <p>In the <em>General</em> section:</p><ul><li><em>Rpt ID</em> → <strong>reset</strong></li><li><em>Report control block name</em> → <strong>reset</strong></li><li><em>RCB path</em> → <strong>reset</strong></li><li><em>RCB type</em> → <strong>reset</strong></li><li><em>Dataset</em> → <strong>reset</strong></li><li><em>Dataset path</em> → <strong>reset</strong></li><li><em>Description</em> → <strong>reset</strong></li><li><em>Configuration revision</em> → <strong>reset</strong></li></ul><p>In the <em>Report</em> section:</p><ul><li><em>Enable reporting</em> → <strong>keep</strong></li><li><em>Server IED</em> → <strong>reset</strong></li><li><em>Client LN</em> → <strong>reset</strong></li><li><em>Maximum number of clients</em> → <strong>reset</strong></li><li><em>Indexed reports</em> → <strong>reset</strong></li><li><em>Integrity period \[ms]</em> → <strong>reset</strong></li><li><em>Buffer time \[ms]</em> → <strong>reset</strong></li></ul><p>In the <em>Trigger options</em> section:</p><ul><li><em>Data change (dchg)</em> → <strong>keep or reset</strong></li><li><em>Quality change (qchg)</em> → <strong>keep or reset</strong></li><li><em>Data update (dupd)</em> → <strong>keep or reset</strong></li><li><em>Periodic integrity</em> → <strong>keep or reset</strong></li><li><em>General interrogation (gi)</em> → <strong>keep or reset</strong></li></ul><p>In the Optional fields section:</p><ul><li><em>Sequence number (seqNum)</em> → <strong>keep or reset</strong></li><li><em>Timestamp (timeStamp)</em> → <strong>keep or reset</strong></li><li><em>Dataset (dataSet)</em> → <strong>keep or reset</strong></li><li><em>Reason code (reasonCode)</em> → <strong>keep or reset</strong></li><li><em>Data reference (dataRef)</em> → <strong>keep or reset</strong></li><li><em>Entry identification (entryID)</em> → <strong>keep or reset</strong></li><li><em>Configuration reference (confRef)</em> → <strong>keep or reset</strong></li><li><em>Buffer overflow (bufOvfl)</em> → <strong>keep or reset</strong></li></ul> |

</details>
{% endstep %}

{% step %}

### Review and manage IEDs: add, remove, rename, or reorder

Review the IEDs imported from the SCL file. You may also add IEDs manually to create a configuration that more closely reflects a real system. These manually added IEDs do not influence the real‑time simulation, but they can be used as GOOSE or SV subscribers, or as SV 9‑2LE publishers.

Because manually added IEDs lack a data model template and control blocks, MMS configuration options are not available for them.

Removing an IED deletes its entire data model, datasets, and all associated control blocks. **Only manually added IEDs can be renamed.**

Click **IED** and use:

* **+** icon to add IED
* **–** icon to remove IED
* **Arrow** icons to reorder IED

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

{% step %}

### Configure Data Logger (optional)

The Data Logger logs the data points during simulation and allows to view them live in ScopeView and auto‑retrieved them post‑reset.

In the **Folders** list, select **Data Logger**, then enable **Record data** to log all interface data points during the simulation. Configure the Data Logger's parameters.

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

<table><thead><tr><th width="150">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Record data</strong></td><td><strong>Checked:</strong> Enables data logging and displays all Data Logger configuration parameters.<br><strong>Unchecked:</strong> Logging is disabled; Data Logger parameters are hidden.</td></tr><tr><td><strong>Recorder log level</strong></td><td>Sets the verbosity of Recorder‑related messages (e.g., errors only, warnings, detailed logs).</td></tr><tr><td><strong>Mode</strong></td><td>Defines how recording starts and stops.<br><strong>Manual:</strong> Recording is controlled via API calls (start/stop).<br><strong>Automatic:</strong> Recording starts automatically when the model loads and stops on reset.</td></tr><tr><td><strong>Export format</strong></td><td>Selects the output file format: <strong>OPREC</strong> (native, high‑performance), <strong>CSV</strong> or <strong>MATLAB</strong> (.mat).</td></tr><tr><td><strong>Output file auto‑naming</strong></td><td><strong>Checked:</strong> Automatically generates a unique file name using: <em>model name + subsystem + timestamp</em>.<br><strong>Unchecked:</strong> User manually specifies the Output File Name. It is recommended to add <em>Append Timestamp (YYYY‑MM‑DD‑HHMMSS)</em> as without timestamp, repeated runs overwrite the file.</td></tr><tr><td><strong>Decimation Factor</strong></td><td>Saves one sample every <em>N</em> simulation steps.<br>Example: <code>1 = log every step</code>, <code>10 = log every 10 steps</code>.</td></tr><tr><td><strong>Frame length</strong></td><td>Defines the number of consecutive steps recorded per frame. No data loss occurs <em>within</em> a frame. However, gaps (“blind areas”) may occur <em>between</em> frames depending on:<br>• Number of logged signals<br>• Sampling rate<br>• Simulator performance<br>• Disk throughput</td></tr><tr><td><strong>Frame length unit</strong></td><td>Defines the unit for the frame length.</td></tr><tr><td><strong>Number of frames to record</strong></td><td>Sets how many frames to capture.<br>No loss occurs within frames; loss may occur between frames depending on system load.</td></tr><tr><td><strong>Show trigger configuration</strong></td><td><p><strong>Checked:</strong> Expands advanced trigger settings:</p><ul><li><strong>Trigger level</strong> is the numeric threshold used to evaluate trigger conditions.</li><li><strong>Trigger function</strong> defines how the trigger activates: <strong>Edge</strong> fires as soon as the signal enters the threshold region, while <strong>Level</strong> fires only after the condition remains true for a specified duration.</li><li><strong>Trigger polarity</strong> determines the direction of the trigger condition: <strong>Positive</strong> fires when the signal is ≥ the trigger level, while <strong>Negative</strong> fires when the signal is ≤ the trigger level.</li><li><strong>Pre‑trigger percentage</strong> specifies the percentage of each frame that is recorded before the trigger event occurs.</li><li><strong>Trigger holdoff</strong> specifies the number of simulation steps ignored after a frame completes before the trigger can rearm.</li></ul><p><strong>Unchecked:</strong> No trigger.</p></td></tr></tbody></table>
{% 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-general-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.
