> 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/hypersim/configure-ios/communication-protocol-ios/iec-61850-8-1-mms/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **IEC 61850-8-1 MMS** 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-8-1 MMS 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-8-1 MMS 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 HYPERSIM license](https://www.opal-rt.com/docs/hypersim/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the IEC 61850-8-1 MMS protocol:

| Feature Name              | Required Status      | Description                                                                    |
| ------------------------- | -------------------- | ------------------------------------------------------------------------------ |
| DP\_IEC61850\_MMS\_SERVER | enabled              | Enables IEC 61850 MMS Server option                                            |
| 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-8-1 MMS:**

4 status values + 2 analog values + 1 quality attribute + 1 timestamp = **8 data points**
{% endhint %}

### Workstation license

**No additional feature is required** in the workstation license to run simulations in HYPERSIM using the IEC 61850-8-1 GOOSE protocol.

## Supported features

* MMS server capability for any parsed IED: Any IED created from parsing an SCL/SCD/ICD file can be instantiated as an MMS server.
* Reporting (server-to-client): The simulator can send MMS reports to connected clients according to configured trigger conditions for selected data attributes, based on datasets defined in the SCL file.
* Configurable trigger options & optional fields: Report trigger options and optional fields are initially populated from the SCL file but are fully configurable to match simulation needs.
* Client read/write via direct requests: Beyond reporting, MMS clients can read (poll) or write (where FC permits) to data attributes present in the server.
* Control commands supported (if controllable objects exist): Clients can issue control commands to controllable objects in the server, subject to control model and CDC applicability (details below).
* Linux network binding: On Linux, the server can bind to a specific network interface defined in the IED configuration.
* Linux IP aliasing for multi‑IED setups: On Linux, IP aliasing can be used so multiple IEDs with different IPs can share the same physical NIC.
* Asynchronous computation pinned to a core: MMS server asynchronous computation can be migrated to a dedicated CPU core.
* RMS accumulation outside the real‑time loop: Model data can be accumulated to compute RMS values before placing them in the server, and this computation occurs outside the real-time loop.
* Control service models implemented (IEC 61850): Control is implemented following IEC references and supports the five IEC 61850 control models:
  * Status only (no commands)
  * Direct operate (normal security)
  * Select-before-operate (SBO) (normal security)
  * Direct operate (enhanced security)
  * SBO (enhanced security, incl. select-with-value)
* CDC-based controllable object support: Control is supported for appropriate CDCs including SPC, DPC, INC, ENC, BSC, ISC, APC, BAC, with forced value behavior as described (including step-up/down for BSC/BAC and range constraints for step position types).
* Control eligibility rules enforced: Commands are accepted only when the CDC is appropriate, the control model is not “status only,” and the command matches the control model (e.g., no Select in direct operate).

## Limitations

* Supported basic attribute types restricted: MMS supports the following basic attribute types: BOOLEAN, INT8/16/32/64, INT8U/16U/32U, FLOAT32/64, Enum, Dbpos, Tcmd, Check, Quality, Timestamp, Struct.
* Timestamp treated as integer: The Timestamp data type is treated as a simple integer.
* Unsupported functional constraints (FC): The following IEC 61850 data attribute functional constraints are not supported: BR, RP, GO, MS, US, LG.


---

# 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/hypersim/configure-ios/communication-protocol-ios/iec-61850-8-1-mms/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.
