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

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

## Continue configuring the IEC 61850 I/O interface

{% stepper %}
{% step %}

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

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="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>

2. Expand **Access Points** and their submenus to view their content. The view presents a hierarchical tree expanded down to the **data attribute (DA)** level, providing a graphical representation of the logical structure defined in the SCL configuration.

   The tree is organized as follows:

   * **AP** – Access Point
   * **LD** – Logical Device
   * **LN** – Logical Node
   * **DO** – Data Object
   * **DA** – Data Attribute

   Items cannot be manually added or removed at any level of the tree. The intermediate levels (Access Point, Logical Device, Logical Node, and Data Object) do not contain configurable parameters; configuration is performed exclusively at the **data attribute** level.

   For **non‑controllable data objects**, no configuration is required. For **controllable data objects**, additional MMS‑specific parameters are available:

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

<table><thead><tr><th width="120">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable as controllable object</strong></td><td><p><strong>Checked:</strong> Exposes the control‑related attributes of the object on the MMS server. When enabled, attributes with <strong>functional constraint CO</strong>, along with any attributes affected by a control operation (such as <code>stVal</code>), are added to the MMS server. Attributes with FC = CO can only be exposed through this mechanism.</p><p>The following attributes are automatically added with <strong>Read/Write</strong> access, depending on the Common Data Class (CDC):</p><ul><li><code>stVal</code>, or <code>valWTr.posVal</code>, or <code>mxVal.i/f</code></li><li><code>ctlModel</code></li><li><code>sboTimeout</code></li></ul><p>Additional control‑related attributes may be required to observe detailed control execution information. These attributes are not added automatically but can be enabled manually as needed:</p><ul><li><code>ctlNum</code></li><li><code>origin.orCat</code></li><li><code>origin.orIdent</code></li><li><code>opRcvd</code></li><li><code>opOk</code></li><li><code>tOpOk</code></li></ul><p>Attributes with FC = CO are considered <strong>control parameters</strong> rather than regular data attributes. They are exposed in the IED tree but do not provide direct connection points for user interaction in the model.<br><strong>Unchecked:</strong> The object is not exposed as controllable on the MMS server. Control‑related attributes (FC = CO) are not available to MMS clients.</p></td></tr></tbody></table>

Selecting a data attribute displays its MMS‑specific properties

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

<table><thead><tr><th width="245">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Full attribute path, including nested structures.</td></tr><tr><td><strong>Functional constraint (FC)</strong></td><td>Functional constraint of the attribute. The following FCs are not supported: BR, RP, GO, MS, US, LG, SG, SE</td></tr><tr><td><strong>Data set reference(s)</strong></td><td>DataSets that include this attribute</td></tr><tr><td><strong>Control block reference(s)</strong></td><td>Control blocks using this attribute</td></tr><tr><td><strong>Add MMS data point*</strong></td><td><strong>Checked:</strong> Adds the data attribute to the MMS server. MMS clients can read and/or write the attribute, subject to the attribute’s <strong>functional constraint (FC)</strong>. If a report control block uses a DataSet containing this attribute, <strong>Add MMS data point</strong> is automatically enabled and cannot be disabled.<br><strong>Unchecked:</strong> The data attribute is not exposed on the MMS server. MMS clients cannot read or write this attribute, and it is not available for reporting or client access.</td></tr></tbody></table>

{% hint style="info" %}
\*The **Add MMS data point** field may be grayed out for the following reasons:

* The attribute has FC = CO and must be enabled through its parent controllable object
* The attribute is required by an active report control block
* The attribute’s functional constraint is not supported
  {% endhint %}

For attributes with **MX (measurement)** functional constraint, additional options are available when **Add MMS data point** is enabled:

<table><thead><tr><th width="245">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Output RMS</strong></td><td>Publishes the RMS value instead of the instantaneous value</td></tr><tr><td><strong>RMS number of samples</strong></td><td>Number of samples used for RMS calculation</td></tr><tr><td><strong>RMS gain</strong></td><td>Gain applied to the RMS result</td></tr></tbody></table>

3. Expand **Data Sets** and their submenus to view their content. The view displays the content of DataSets defined in the IED. This view is **read‑only** and contains no configurable parameters. It is intended to show how data attributes are grouped for use by MMS report control blocks. Each DataSet entry is composed of **Functional Constrained Data Attributes (FCDAs)**. FCDA elements cannot be added or removed manually and include the following fields:

<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 %}

### Configure MMS server

Click **MMS server configuration** to configure its settings.

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

<table><thead><tr><th width="155"></th><th></th></tr></thead><tbody><tr><td><strong>NIC name</strong></td><td>Network interface name. Select the correct interface based on your <strong>System Description Document</strong> or Linux <code>ifconfig</code> command. For local testing on the same simulator, use the loopback interface <strong>lo</strong>.</td></tr><tr><td><strong>IP address</strong></td><td>IP address used for MMS communication. IP aliasing may be used even when using a single network interface (e.g., <code>eno1:0</code>, <code>eno1:1</code>). Use <strong>ANY</strong> to automatically resolve the IP from the selected NIC.<br>For local testing on the same simulator, use <strong>127.0.0.1</strong>.</td></tr><tr><td><strong>TCP port</strong></td><td>TCP port used for MMS communication.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage and configure Reports

Expand the **Reports** folder to display all available GOOSE items.

Reports are automatically added when SCL files containing report definitions are parsed.\
A report can be removed by deleting its reporting IED from the IED list or by removing the corresponding SCL file 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-0fa31a01973ef119b638b956111c14ad8b62f2e6%2FDR-rtlab-mms-reports.png?alt=media" alt=""><figcaption></figcaption></figure>

Change parameters as desired:

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

<table><thead><tr><th width="200">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Rpt ID</strong></td><td>Unique identification of the report control block.</td></tr><tr><td><strong>Report control block name</strong></td><td>Name of the report control block as taken from the SCL file.</td></tr><tr><td><strong>RCB path</strong></td><td>Path of the report control control block within the IED.</td></tr><tr><td><strong>RCB type</strong></td><td>Type of report control block: buffered or unbuffered.</td></tr><tr><td><strong>Dataset</strong></td><td>Name of the dataset used by the report control block.</td></tr><tr><td><strong>Dataset path</strong></td><td>Full path within the IED of the dataset used by the report control block.</td></tr><tr><td><strong>Description</strong></td><td>Description of the report control block, retrieved from the SCL file.</td></tr><tr><td><strong>Configuration revision</strong></td><td>Configuration revision number of the report control block.</td></tr></tbody></table>
{% endtab %}

{% tab title="Report" %}

<table data-header-hidden><thead><tr><th width="190">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Enable reporting</strong></td><td>Enables sending reports when the configured trigger conditions are met for any DataSet member. When enabled, the connection points required to transmit the report are created.</td></tr><tr><td><strong>Server IED</strong></td><td>Name of the IED that sends the report. This field is non‑editable.</td></tr><tr><td><strong>Client LN</strong></td><td>Logical Nodes acting as report clients. This field is non‑editable and not used during real‑time simulation.</td></tr><tr><td><strong>Maximum number of clients</strong></td><td>Maximum number of clients allowed to connect to this report. This field is non‑editable.</td></tr><tr><td><strong>Indexed reports</strong></td><td>Indicates whether reports are indexed. When enabled, report names are suffixed with an instance index from 1 to 99. This field is non‑editable.</td></tr><tr><td><strong>Integrity period [ms]</strong></td><td>Applicable only when <strong>Periodic integrity</strong> triggering is enabled. Reports containing all DataSet members are sent periodically at the specified interval (milliseconds). This field is non‑editable.</td></tr><tr><td><strong>Buffer time [ms]</strong></td><td>Time delay between trigger detection and report transmission. All triggers occurring within this interval are grouped into a single report. This field is non‑editable.</td></tr></tbody></table>
{% endtab %}

{% tab title="Trigger options" %}

<table data-header-hidden><thead><tr><th width="190">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Data change (dchg)</strong></td><td>Triggers sending a report when a change is detected in any of the DataSet members’ data attributes.</td></tr><tr><td><strong>Quality change (qchg)</strong></td><td>Triggers sending a report when a change is detected in the quality attributes of any DataSet member.</td></tr><tr><td><strong>Data update (dupd)</strong></td><td>Triggers sending a report when a DataSet member is updated, even if the new value is identical to the previously stored value.</td></tr><tr><td><strong>Periodic integrity</strong></td><td>Enables periodic transmission of reports containing all DataSet members. The reporting interval is defined by the <strong>Integrity period [ms]</strong> parameter.</td></tr><tr><td><strong>General interrogation (gi)</strong></td><td>Enables report transmission upon explicit request from an MMS client.</td></tr></tbody></table>
{% endtab %}

{% tab title="Optional fields" %}

<table data-header-hidden><thead><tr><th width="190">Parameter</th><th>Value</th></tr></thead><tbody><tr><td><strong>Sequence number (seqNum)</strong></td><td>When enabled, includes the report sequence number in the transmitted reports.</td></tr><tr><td><strong>Timestamp (timeStamp)</strong></td><td>When enabled, includes the entry timestamp in the transmitted reports.</td></tr><tr><td><strong>Dataset (dataSet)</strong></td><td>When enabled, includes the name of the DataSet associated with the report control block.</td></tr><tr><td><strong>Reason code (reasonCode)</strong></td><td>When enabled, includes the reason for report transmission, determined by the trigger condition that caused the report to be sent.</td></tr><tr><td><strong>Data reference (dataRef)</strong></td><td>When enabled, includes the reference of the data attribute that triggered the report transmission.</td></tr><tr><td><strong>Entry identification (entryID)</strong></td><td>When enabled, includes the entry identifier associated with the report.</td></tr><tr><td><strong>Configuration reference (confRev)</strong></td><td>When enabled, includes the configuration revision number of the report control block.</td></tr><tr><td><strong>Buffer overflow (bufOvfl)</strong></td><td>When enabled, includes information indicating whether a report buffer overflow has occurred.</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-mms/configure-iec-61850-8-1-mms-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.
