> 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/examples/protection/iec-61850-substation-automation-system-sas-with-mms.md).

# IEC 61850 Substation Automation System (SAS) with MMS

## Description

The **IEC 61850 SAS MMS** example, located in **File > Open an Example File > Protection**, demonstrates how to integrate an IEC 61850 Substation Automation System (SAS) in HYPERSIM using GOOSE, Sampled Values (SV), and MMS. The example is based on the UCAIUG Interoperability (IOP) 2019 substation.

The main objectives are to configure IEC 61850 communication in the IEC 61850 v2 I/O interface, map IED data to HYPERSIM sensors, and illustrate three protection scenarios (Reverse Blocking, Breaker Failure, and MMS-based control of relay settings).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1316dd77dda1d115d45b2bad2da8789c0c9dd96f%2Fimage%20(149).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

A HYPERSIM simulator is required. To use MMS reports and client/server control, the simulator must have an **MMS Server license** enabled. If the simulator does not have an MMS license, disable all report control blocks and remove all MMS data points in the IEC 61850 v2 I/O interface before running the model.

An MMS client is required to view measurements and issue control commands. Any IEC 61850-compliant client can be used; this example uses the free tool **IED Explorer 0.79m**. Usage instructions are provided in the Detailed explanation section.

This example assumes familiarity with IEC 61850 concepts (GOOSE, Sampled Values, MMS) and HYPERSIM features (IEC 61850 v2 I/O interface configuration and the Target I/O Interface block). For additional background:

* IEC 61850 I/O interface
* Target I/O Interface block

## Detailed explanation

### Model overview

This example integrates an IEC 61850 SAS in HYPERSIM. The substation design originates from the UCAIUG IOP 2019 event \[1].

The SAS was engineered with a system configuration tool (SCT) using vendor IED configuration files (CID, ICD). The implementation in HYPERSIM follows these steps:

* **Build the single-line diagram** with HYPERSIM blocks corresponding to equipment in the SCD.
* **Import the SCD** into the IEC 61850 v2 I/O interface.
* **Enable selected GOOSE messages** and report control blocks, and configure SV streams (IEC 61850-9-2 LE).
* **Implement protection and communication** scenarios between IEDs using HYPERSIM blocks.
* **Use the Target I/O Interface block** to map HYPERSIM sensor data to IEC 61850 data attributes.

<details>

<summary><strong>Substation structure:</strong></summary>

* Voltage levels: 230 kV and 14.4 kV
* Two power transformers
* Three busbars: 230 kV BUS at 230 kV voltage level, Transfer BUS XF, 14.4 kV BUS A, and 14.4 kV BUS B.
* Twelve bays:
  * At 230kV:
    * L1, L2 (Line)
    * BP (Busbar Protection)
    * TXA, TXB (Transformer Protection)
  * At 14.4 kV:
    * IncA, IncB (Incomer)
    * BT (Tie Breaker)
    * XF (Busbar XF Protection)
    * A1, A2, B1, B2 (Feeder at busbars 14.4 kV BUS A and BUS B)
* IEDs (Intelligent Electronic Devices):\
  Multiple IEDs at each bay are in charge of protection (PU), control (BCU) or both (PUBCU) depending on the type of IED. Merging units (MU) are located in the process level and they are in charge of digitizing current and voltage values from instrument devices and transferring them via sampled values to bay units.

</details>

### Bays and IEDs in HYPERSIM

In the HYPERSIM model, only three bays and their respective IEDs are involved in the scenarios that are designed. They are located at the low voltage (LV) side of the substation which is 14.4 kV. HYPERSIM components are used to create internal logic and IEC 61850 communication section of the IEDs which are grouped as subcircuits. The Target I/O interface component block is used in place of a merging unit and in general for IEC 61850 data mapping to component sensors.

The table below gives a summary of the bays and IEDs that are involved in this example model. The bay names from the table and subsequent figure have the voltage level name next to them such as LV\_BT. This is just to indicate where each bay is located in regards to voltage level in a way to interpret the IEC 61850 single line diagram hierarchical naming in HYPERSIM.

| Bay name            | IED name    |
| ------------------- | ----------- |
| **LV\_BT (BT)**     | BTMU        |
|                     | BT\_PU      |
| **LV\_INCA (INCA)** | IncAMU      |
|                     | IncA\_PUBCU |
| **LV\_INCB (INCB)** | IncBMU      |
|                     | IncB\_PUBCU |

The following picture shows the three bays and Target I/O interfaces as merging units which are connected to the current transformers. Each equipment is named to represent the name of their respective bays, eg CT1\_INCA, CB\_INCA, etc. 3-phase Breakers are chosen for circuit breakers and 3-phase Current Probes are used to represent current transformers. The busbars at 14.4kV are named: BUS\_A, BUS\_B, and TRANSFER\_XF.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7a99940644bdffc01e0267cf3dfe44db8b5d1bd1%2Fimage%20(140).png?alt=media" alt=""><figcaption></figcaption></figure>

| <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-45e58832ac6b37bbe1c8985eade7bcc91e3b84ea%2Fimage%20(141).png?alt=media" alt="" data-size="original"> | <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6006e03218f8c8387c490dd3f17cc8b8a0bcfde2%2Fimage%20(142).png?alt=media" alt="" data-size="original"> |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-495dbb5db1efaa2b9f2ef4d2c331c934511e3409%2Fimage%20(143).png?alt=media" alt="" data-size="original"> | <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-955bec6f415dab04fe8f315e2ba8ab18260b6a44%2Fimage%20(144).png?alt=media" alt="" data-size="original"> |
| <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d2655411a6084123306da5132a1ac8d326b6b3c2%2Fimage%20(145).png?alt=media" alt="" data-size="original"> | <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6af475a82a330a557984df8f12f073246e609d4b%2Fimage%20(146).png?alt=media" alt="" data-size="original"> |

The IEDs **BT\_PU** and **IncB\_PUBCU** contain overcurrent **protection relays** from the HYPERSIM library.

### Fault

A three-phase fault is applied in bay **BT**. It is triggered at **0.2 s** using ScopeView Acquisition (Trig) and lasts **0.2 s**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f29908e3b978b29d90abd3a38ae72557b278f045%2Fimage%20(147).png?alt=media" alt=""><figcaption></figcaption></figure>

### IEC 61850 v2 I/O Interface

The HYPERSIM I/O interface imports GOOSE and MMS definitions from the SCD and configures IEC 61850-9-2 LE Sampled Values. The interface enables mapping of IED data model attributes as MMS inputs or outputs to exchange commands and measurements with an MMS client.

SCD file is **IEC61850\_SAS\_MMS.scd**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b8574ef433fa8fa36b30783619d1237092cdc9a9%2Fimage%20(148).png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Only the parts relevant to this example are summarized here. For complete details, see IEC 61850.
{% endhint %}

## SCL and IED

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2a5ef3e1b00a843d3b83d948b989691e7349801d%2Fimage%20(1598).png?alt=media" alt=""><figcaption><p>SCL files</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c5b781c4935ebcf6896467ba9455bde359b51841%2Fimage%20(1599).png?alt=media" alt=""><figcaption><p>IED – List of IEDs (MMS Servers)</p></figcaption></figure>

The TCP ports used for MMS connections in this example are:

| IED name in HYPERSIM model | IED name in SCD file | TCP Port |
| -------------------------- | -------------------- | -------- |
| **IncA\_PUBCU**            | **K1IncA1PUBCU**     | **109**  |
| **IncB\_PUBCU**            | **K1IncB1PUBCU**     | **110**  |

## **IED – IED data model (MMS data points)**

IED **IncB\_PUBCU** receives MMS client commands through its data model. The attribute **StrVal.SetMag.f** is used as a writable MMS data point to change the pickup setting of the overcurrent function. In this example, it is used to switch relay setting groups. For details on services and data objects, refer to IEC 61850-7-2.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f39c5cd436d5a2e748e164ad2239b5c0a4bf7f80%2Fimage%20(1600).png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If the simulator **does not have an MMS Server license**, the **Add MMS data point** options must be **disabled** or the model will not run.
{% endhint %}

## GOOSE

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-cfcdc95916ecf2156fac3da808883d01221c619b%2Fimage%20(1601).png?alt=media" alt=""><figcaption></figcaption></figure>

The example enables two GOOSE control blocks:

| GOOSE ID             | HYPERSIM Scenario    |
| -------------------- | -------------------- |
| **BreakerFailureBT** | **Breaker Failure**  |
| **ProtectionBT**     | **Reverse Blocking** |

## Sampled Values

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5d4776849c2b4124987b3430eede61a8a3082835%2Fimage%20(1602).png?alt=media" alt=""><figcaption></figcaption></figure>

Sampled Values IEC 61850-9-2 Light Edition (LE) Sampled Values are used in this example model. Three streams are enabled to be published by merging units and subscribed to by IEDs at the three bays. In HYPERSIM, the current transformers (CT) publish these streams and different components (such as protection relays) at each IED subscribe to them.

| SV LE stream       | Publishing CT in HYPERSIM | Subscribing IED in HYPERSIM |
| ------------------ | ------------------------- | --------------------------- |
| **OPALRT\_BTMU**   | **CT1\_BT**               | **BT\_PU**                  |
| **OPALRT\_IncAMU** | **CT1\_INCA**             | **IncA\_PUBCU**             |
| **OPALRT\_IncBMU** | **CT1\_INCB**             | **IncB\_PUBCU**             |

## MMS Reports

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-66848c7c15aa98f6c3e30e658cafffa04d53b54b%2Fimage%20(1603).png?alt=media" alt=""><figcaption></figcaption></figure>

Two report control blocks are enabled (one per PUBCU IED). The SCD includes multiple reports for redundancy; only the following are used:

<table><thead><tr><th width="144.11114501953125">IED name in SCD</th><th width="130.4444580078125">IED name in HYPERSIM</th><th width="125.666748046875">Report Control Block (RCB)</th><th width="215">RCB content used in model</th><th>Data attribute type</th></tr></thead><tbody><tr><td><strong>K1IncA1PUBCU</strong></td><td><strong>IncA_PUBCU</strong></td><td><strong>rcb1</strong></td><td><strong>P1PTOC.Str.general</strong></td><td><strong>Binary</strong></td></tr><tr><td></td><td></td><td><strong>rcb6</strong></td><td><strong>MMXU.A.Phs(A,B,C)</strong></td><td><strong>Analog</strong></td></tr><tr><td><strong>K1IncB1PUBCU</strong></td><td><strong>IncB_PUBCU</strong></td><td><strong>rcb1</strong></td><td><strong>RBRF.OpEx.general</strong></td><td><strong>Binary</strong></td></tr><tr><td></td><td></td><td><strong>rcb6</strong></td><td><strong>MMXU.A.Phs(A,B,C)</strong></td><td><strong>Analog</strong></td></tr></tbody></table>

{% hint style="info" %}
Report datasets are listed under the IED section of the interface.
{% endhint %}

### Protection applications (scenarios)

The three scenarios involve IEDs **BT\_PU**, **IncA\_PUBCU**, and **IncB\_PUBCU**. Select a scenario using the constant **Scen\_Sel** at the top right of the model:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-48d6aa2907483e0c9e66754ea10e0ee0fd1d34b7%2Fimage%20(138).png?alt=media" alt=""><figcaption></figcaption></figure>

## Simulation and results

### Scenario selection

The scenarios can be selected by changing the value of the constant block "**Scen\_Sel**". The selector is located at the top right of the model page.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d97336047858b7bd907712682d0f90e018989400%2Fimage%20(139).png?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Reverse Blocking (RB)" %}
**Scen\_Sel**= 1

**IEDs in the scenario**: BT\_PU (overcurrent relay) IncA\_PUBCU

**Breakers in the scenario:** CB\_BT, CB\_INCA

**IEC 61850 communication:** GOOSE - Application: ProtectionBT

**IEC 61850 data:** PTOC.Str.ST.general

**Explanation:**

Fault at BT. BT\_PU detects and trips CB\_BT.

CB\_BT opens. IncA sees the fault but is blocked; CB\_INCA remains closed.
{% endtab %}

{% tab title="Breaker Failure (BF)" %}
**Scen\_Sel**= 2

**IEDs in the scenario**: BT\_PU (overcurrent relay) IncB\_PUBCU

**Breakers in the scenario:** CB\_BT, CB\_INCB

**IEC 61850 communication:** GOOSE - Application: BreakerFailureBT

**IEC 61850 data:** RBRF.OpEx.ST.general

**Explanation:**

Fault at BT. BT\_PU detects and issues a trip to CB\_BT, which fails to open.

IncB sees the fault and trips CB\_INCB to isolate the fault.
{% endtab %}

{% tab title="MMS Control" %}
**Scen\_Sel**= 3

**IEDs in the scenario**: IncB\_PUBCU (overcurrent relay)

**Breakers in the scenario:** CB\_INCB

**IEC 61850 communication:** MMS command: Change Setting Groups

**IEC 61850 data:** PTOC.StrVal.SP.SetMag.f

**Explanation:**

Fault at BT. IncB\_PUBCU detects the fault and trips CB\_INCB.

Trip time depends on the relay setting group (SG) changed by an MMS client.

**IncB\_PUBCU relay setting groups in Scenario 3 only**

<table><thead><tr><th width="100">Setting Group</th><th>Overcurrent type</th><th width="120">Parameters</th><th width="112">Expected Trip time</th><th width="98">Value sent by MMS Client</th><th>IEC 61850 data</th></tr></thead><tbody><tr><td><strong>SG1</strong></td><td><strong>Definite Time Overcurrent</strong></td><td><strong>Time delay = 0.1 s</strong></td><td><strong>0.3 s</strong></td><td><strong>1</strong></td><td><strong>PTOC.StrVal.SP.SetMag.f</strong><br><br></td></tr><tr><td><strong>SG2</strong></td><td><strong>Inverse Time Overcurrent</strong></td><td><strong>US Short Time Inverse (U5)</strong></td><td><strong>0.36 s</strong></td><td><strong>2</strong></td><td><strong>PTOC.StrVal.SP.SetMag.f</strong></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

### Run the simulation

The fault at BT bay will trigger at 0.2 seconds for 0.2 seconds. Depending on the protection scenario that is selected, the breaker operation at BT, IncA, and IncB bays are shown in this section.

The simulation should be run in steady state so make sure the network is initialized by the load flow.

{% stepper %}
{% step %}
Open Network → Load Flow, make sure the frequency is at 60 Hz and then press "Execute load flow".

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1cf85f01c77939d45a4ae1afaa7da28475998009%2Fiec61850-example-loadflow-0.png?alt=media" alt=""><figcaption></figcaption></figure>

You can also enable performing load flow when simulation starts in the "Simulation Settings".

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ea770ee0dcd4db55df109181bfa8013ec494248c%2Fiec61850-example-loadflow-5.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Run the simulation in real time on a target in real time.
{% endstep %}
{% endstepper %}

### Scenario 1: Reverse Blocking (RB)

Fault occurs at 0.2 seconds at BT. Fault is seen by both BT\_PU and IncA\_PUBCU. BT\_PU sends tripping signal to CB\_BT and it opens successfully. BT\_PU blocks IncA\_PUBCU from sending a trip signal to CB\_INCA so it does not open.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2d68cd80412c059f1f457a842c26c3d171b1a667%2Fiec61850-example-rb-1.png?alt=media" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}
Choose **Scen\_Sel = 1.**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bcc3bf36867a301726f5711898899a7f13fb91e6%2Fiec61850-example-bf-2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Open Template IEC61850\_SAS\_MMS.sv**t from the project folder.
{% endstep %}

{% step %}
**Open ScopeView**, click on both **Sync** and **Trig** to make sure fault is triggered at 0.2 seconds.
{% endstep %}

{% step %}
**Do an acquisition** by pressing on the Play button on that ab "BT\_Relay\_Fault"

From the diagrams in this tab, the overcurrent relay at BT\_PU IED sees the fault current at 0.2 seconds and issues a trip signal after 0.05 second delay (0.05 seconds is its protection relay setting). In the Reverse Blocking scenario, breaker CB\_BT receives the trip signal from the relay and opens at 0.25 seconds.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8eb4032e15dd659023c4f7b8c86a1ba7eb8c74cb%2Fiec61850-example-rb-simul-1.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Open the page "**Scenario1: Reverse Blocking (CB\_INCA)**".

This page shows the publishing of GOOSE message containing the data attribute PTOC.Str.general when the relay at BT has issued the tripping signal at 0.25 seconds. This message is sent to IED at IncA. By viewing the operation of CB\_BT and CB\_INCA, it can be seen that, as expected, CB\_BT is open at 0.25 seconds and CB\_INCA is blocked and has stayed closed during the fault period.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-11d56cdf1cd8ee3f25b8db5bd6b4e0e110367572%2Fiec61850-example-rb-simul-2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Scenario2: Breaker Failure (BF)

Fault occurs at 0.2 seconds at BT. Fault is seen by both BT\_PU and IncB\_PUBCU. BT\_PU sends tripping signal to CB\_BT and but does not open. IncB\_PUBCU sends trip signal to CB\_INCA and it opens instead.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-dd2736daa6b99299a1fcfb80e6b5c722c90144ac%2Fiec61850-example-bf-1.png?alt=media" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}
Choose **Scen\_Sel = 2**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bcc3bf36867a301726f5711898899a7f13fb91e6%2Fiec61850-example-bf-2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Make sure the simulation is running** and open ScopeView. Make sure the template IEC61850\_SAS\_MMS is open, view the page BT\_Relay\_Fault, and do an acquisition.

In this scenario, the overcurrent is seen by the relay and it issues a tripping signal but as it is shown, the breaker CB\_BT does not receive the message and so the breaker fails to open.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9f92e06d501df6a021cc0d36924f081d0c72e15f%2Fiec61850-example-bf-simul-1.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
View the page "**Scenario2: Breaker Failure (CB\_\_INCB)**".

The GOOSE message containing the data RBRF.OpEx.general is published to the bay INCB. As it can be seen, the breaker at BT has failed to open and remained closed. So, the IED at INCB has issued a signal to its breaker CB\_INCB to be open instead. It can be seen that at 0.25 seconds, the breaker CB\_BT is closed and CB\_INCB has opened and thus isolated the fault and protected the busbar.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2412e6c4a1ee9990f96d39ae9713bc43170c0436%2Fiec61850-example-bf-simul-2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Scenario3: MMS Control

Fault occurs at 0.2 seconds. It is seen by IncB\_PUBCU and its overcurrent relay sends trip signal to breaker CB\_INCB. Trip time and breaker operation time can differ based on relay setting group (SG). The setting group can be changed between 1 and 2 by MMS Client.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-707d42665273fdd7b6f9b2cbada9b77eae2f1157%2Fiec61850-example-mmsctrl-1.png?alt=media" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}
Choose **Scen\_Sel = 3**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bcc3bf36867a301726f5711898899a7f13fb91e6%2Fiec61850-example-bf-2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Make sure the simulation is running**, open ScopeView template SAS\_IEC6150\_MMS.svt and view the tab **Scenario3: MMS Control**.

This tab shows the output of the overcurrent relay at IncB\_PUBCU. The relay sees the fault and issues a tripping signal to CB\_INCB. The trip time depends on the relay setting groups. The graph **SG1: Definite Time Overcurrent** in this page shows the relay's trip time according to **Setting Group 1 (SG1)** . The time is about **0.3** seconds which corresponds to the 0.1 second delay of the relay's setting. The graph CB\_INCB Status shows the breaker CB\_INCB opening with this time.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a7ea7458cf227ab0626cb04f8458d2432de7c661%2Fiec61850-example-mmsctrl-simul-1.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Use an MMS client to change the setting group to 2**. The picture below shows how it can be done using the free MMS client called "**IED Explorer**".

Once the setting group has changed by the MMS client, do an acquisition in ScopeView to see the new results.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-82e67d6f7d12b45a2af9a9d439e406de2e525504%2Fiec61850-example-mmsctrl-simul-2.png?alt=media" alt=""><figcaption></figcaption></figure>

As it can be seen, the graph **SG2:Inverse Time Overcurrent** shows the relay's trip signal when **Setting Group 2 (SG2)** is selected. The time is approximately **0.36s** which corresponds to the expected time. As seen from the graph CB\_INCB Status, the breaker CB\_INCB has opened at 0.36 seconds.
{% endstep %}
{% endstepper %}

### MMS reports and data

In ScopeView, view the diagrams in the tabs MMS(IncA\_PUBCU) and MMS(IncB\_PUBCU) in ScopeView. They show the data that is transmitted to the MMS client. The analog signals are current phasor magnitude and angles. The binary signals are those from logical nodes for either overcurrent protection (PTOC) or breaker failure (RBRF). Both analog and binary data are sent to the MMS client via Reports.

The following diagrams are taken during **Scenario1: Reverse Blocking**. The values are the **same** for **all scenarios**.

As it can be seen from both pictures, MMS report for IncA\_PUBCU contains data for phasor magnitudes and angles while reports for IncB\_PUBCU only contain phasor magnitudes. This is because of the data model for each IED and depends on how they were designed.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-05ba29469a118376595e9769248a247debf68bf5%2Fiec61850-example-mmsctrl-data-1.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-17f4f4ba8c6f3fe1a84e3db4a60174bbc70903c4%2Fiec61850-example-mmsctrl-data-2.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This information can also be seen on an MMS client. On the client, the reports that are sent by the MMS servers (IEDs in the model) can be viewed, enabled and their data sets can be monitored with values changing during the simulation runtime.
{% endhint %}

The pictures below show the report control blocks and monitored data of the measurement from IncA\_PUBCU IED on the application IED Explorer.

The first picture shows the IED's current phasor measurement during normal operation and the second picture shows the phasors during fault. As it can be seen, the current phasor magnitudes are very high.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-37ddf477ee21e76f68961acb346a778124efb2e6%2Fiec61850-example-mmsctrl-data-3.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b804bb4e4ca28c2ac914369cd93ef298fc062910%2Fiec61850-example-mmsctrl-data-4.png?alt=media" alt=""><figcaption></figcaption></figure>

The next two pictures shows data from binary overcurrent protection signal and measurement from IncA\_PUBCU IED on the application IEDScout. The first picture is normal operation and the second one is from the exact moment the fault occurred, As it can be seen, the current magnitudes are very high.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-95874185a1ba0a8c149dc825a3b4197b43eed54e%2Fiec61850-example-mmsctrl-data-5.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ade6075f57fd3ee31f62a75dbb0158035c74e497%2Fiec61850-example-mmsctrl-data-5-1.png?alt=media" alt=""><figcaption></figcaption></figure>

### GOOSE and SV additional data

**View the pages "BF GOOSE data", "RB GOOSE data"** to find data such as status number and sequence number for GOOSE publisher and subscriber of the two Reverse Blocking and Breaker Failure applications.

* **stNum (Status Number) for publisher and subscriber:** This data attribute increments whenever the status of the GOOSE message changes. So, in the case of the protection functions in this model, whenever the output of the relay BT\_PU.5051OC (Q) changes its status, this number increments by 1. If a connection between publisher and subscriber is maintained, stNum for both publisher and subscriber should be the same value.
* **sqNum (Sequence Number) for publisher and subscriber:** This data attribute increments whenever the GOOSE message is retransmitted which differs for each GOOSE control block. It rests to 0 or 1 (depending on the GOOSE control block parameters). So, in this model, whenever the fault is reinitialized and the relay output changes its status, sqNum resets to 0. sqNum should be the same for both publisher and subscriber as long as their connection is established and maintained.
* **State for subscriber:** This data attribute has the value of 1 when the connection between publisher and subscriber is established. If they lose connection, the value drops to 0. If subscriber falls out of sync with the publisher (so it is not following it anymore). the value changes to -5.

As shown in the picture, the values for stNum, sqNum for both publisher and subscriber are the same. As it is explained, stNum increments every time there is a change in data which in this case, is when fault occurs and is cleared by doing the acquisition in ScopeView. Also, sqNum shows it drops to zero every time fault occurs or clears by pressing the acquisition. It increments again constantly until the acquisition is pressed again. State = 1 so a connection has been successfully established between GOOSE publisher and subscriber.

{% hint style="info" %}
The values shown in the diagram for both stNum and sqNum could be different on your ScopeView since it depends on what values they had and how long the simulation was running before the acquisition.
{% endhint %}

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-56ca56c6656d91b3d1469d7470c3519d737b00e2%2Fiec61850-example-mmsctrl-data-6.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-85fe3428631e8961a711a96c4e9c544a0726803e%2Fiec61850-example-mmsctrl-data-7.png?alt=media" alt=""><figcaption></figcaption></figure>

**Open the tab SV Data to view Sampled Value streams quality and the Sample Value count** of the OPALRT\_BTMU stream.

The SV Publisher and Subscriber Quality waveforms are taken from the constant blocks SVPub\_Q which are publishing the quality value for current SV streams. If the subscriber values are the same as the publisher values, as shown in the figure, it means the connection between the publisher and subscriber is valid.

SV Sample Count shows the smpCnt value of the SV stream. This data attribute is typically used for synchronization validation. According to the standard, an IEC 61850-9-2 LE compliant merging unit can publish analog data at a fixed rate which is 80 samples per power cycle. The number of samples per second is 4800 for a 60 Hz system (like this model) and 4000 for a 50 Hz system. The figure shows how smpCnt reaches 4800 in one second.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3c1c9b34fe0d86a8234656d5524b6a752449de0b%2Fiec61850-example-mmsctrl-data-8.png?alt=media" alt=""><figcaption></figcaption></figure>

## Additional Information

### Substation Origins

The model is based on the substation designed by the IEC 61850 User Group under the UCA International User Group (UCAIUG) during the IOP conferences of 2017 and 2019 \[1]. The single line diagram of the model can be seen in the figure below.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-13b284d3f1e30305f9d26d84d4c5cd51a4bb6e1f%2Fiec61850-example-mmsctrl-data-9.png?alt=media" alt=""><figcaption></figcaption></figure>

Helinks STS, a vendor-independent system configuration tool was used to design the SAS based on the IOP substation \[2]. The design focuses on three bays at the 14.4 kV voltage level: **IncA, IncB, BT**. The result of the SAS design in Helinks STS is an SCD file which contains all information from the substation including communication.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a10f486123d9dc67dd89d691f899a739f29c1d56%2Fiec61850-example-mmsctrl-data-10.png?alt=media" alt=""><figcaption><p>The design of the three bays in Helinks STS</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-daaf5ad60205a9170354b0c606d50f86b78af749%2Fiec61850-example-mmsctrl-data-11.png?alt=media" alt=""><figcaption><p>A part of the SCD file, specifically the GOOSE communication section</p></figcaption></figure>

### GOOSE and SV Sensor Mapping

This segment shows the mapping sensors of HYPERSIM library parts to IEC 61850 data from GOOSE and sampled values. The information is given for each bay.

<details>

<summary><strong>BT</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-69ef45f20842e89b12f6039220461fdced762dad%2Fimage%20(1590).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b7dd678a665214c5c28a22af8fab714d38241b95%2Fimage%20(1591).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>BT_PU IED</strong></summary>

5051OC Relay for SV Current Input and PTOC.Str.general publishing

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-df187fdeb09ca95d0e450db787df357d44d877a9%2Fimage%20(1592).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5ff354bd66e5d3c72b5bcc149004a8176480148b%2Fimage%20(1593).png?alt=media" alt=""><figcaption></figcaption></figure>

Gain "RBRF\_OpEx\_general" for RBRF.OpEx.general publishing

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7225a40852b83f72a7d75473b431df3cfb128ef8%2Fimage%20(1594).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d2643d0bfc9700ad66351b3bc9373dd204055ee4%2Fimage%20(1595).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>IncA</strong></summary>

CT1\_INCA

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-eb12b4031432b9acb2ac2f77b150d544c0acfc8f%2Fimage%20(124).png?alt=media" alt="" width="377"><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-de914fb404e0ee78f38814f9af9c69e5f31d6b1a%2Fimage%20(125).png?alt=media" alt=""><figcaption></figcaption></figure>

IncA\_PUBCU

SV Subscription and MMS transmission of magnitude and angle of current phasors in the subcircuit IncA\_MMS\_Logic

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2cb5af9f35d842b11179284de4ddf59daab69e23%2Fimage%20(126).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a39eb372bb7231c264ee45d598a368ee7731d05f%2Fimage%20(127).png?alt=media" alt=""><figcaption></figcaption></figure>

PTOC.Str.general GOOSE subscription and MMS transmission of PTOC signal in subcircuit IncA\_Trip\_Logic

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fdcfbec048e8ad59712c650882cdc60d6613a38e%2Fimage%20(1605).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-47564de272712778f0a7b35b3e476ab93e10b28d%2Fimage%20(1606).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>IncB</strong></summary>

CT1\_INCB

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2cbb1233300504775431fede6b03bc508b6a9dd9%2Fimage%20(1607).png?alt=media" alt="" width="371"><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9d5a70c950838d7743d31eee0e65ff4e97a726f5%2Fimage%20(1608).png?alt=media" alt=""><figcaption></figcaption></figure>

Incb\_PUBCU

SV subscription on gains

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7d3d009bcd9606225050b8bf279fd1260e17289f%2Fiec61850-example-mmsctrl-sv.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-03c778a0cd6ac6f44794d4150e1a22f449d3bf27%2Fimage%20(1609).png?alt=media" alt=""><figcaption></figcaption></figure>

MMS transmission of magnitude of current phasors in the subcircuit IncB\_MMD\_Logic

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-aa1fe6c8a73d1f335663ea42ee209f267b4b2024%2Fimage%20(1610).png?alt=media" alt="" width="223"><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c5ba6e71c5c262870e800cfb988acfec8a240308%2Fimage%20(1611).png?alt=media" alt=""><figcaption></figcaption></figure>

\
GOOSE subscription to RBRF.OpEx.general from BT\_PU and MMS transmission of RBRF.OpEx.general in the subcircuit IncB\_Trip\_Logic

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b422e4cf570bc88d6a238f104b47e54ca9f1f44b%2Fiec61850-example-mms-goose-1.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2d7b1d410b4ca39a5f9f0bbef911b28d9da116ff%2Fiec61850-example-mms-goose-2.png?alt=media" alt=""><figcaption></figcaption></figure>

MMS reception of PTOC.SE.StrVal data which is used to change setting groups in Subcircuit Relay\_SG

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d97c4f522eb6dcae9fe84347de0fe8a748378011%2Fiec61850-example-mms-goose-3.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9abeb570d80c3f26d2221a9675f8760fd9220c99%2Fimage%20(1612).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

### GOOSE and SV Monitoring Data

GOOSE monitoring data for Breaker Failure and Reverse Blocking Applications

<details>

<summary><strong>Gains for Pub_BF, Sub_BF for stNum, sqNum, State</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d151a9117c97dd5560b1fe93a729f55585353607%2Fiec61850-example-mms-goose-4.png?alt=media" alt=""><figcaption></figcaption></figure>

**Breaker Failure (BF)**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-13e9db9760483073e431c37dad34fc46de32f415%2Fimage%20(112).png?alt=media" alt=""><figcaption></figcaption></figure>

**Reverse Blocking (RB)**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8452b1a0a80e1775d1115385e5d7fc35d9110bf8%2Fimage%20(113).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Constants for SV quality publishing and Gains for SV quality subscription and Sample Count</strong></summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8e5aa92f4cd25e50372a7174edf68e27892a34e7%2Fimage%20(114).png?alt=media" alt=""><figcaption></figcaption></figure>

**SV Quality publishing**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-106a874fc441d943c73303b694758a5c229485bf%2Fimage%20(115).png?alt=media" alt=""><figcaption></figcaption></figure>

**SV Quality subscription and Sample Count**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e8ab78931732b53bf9fef85fb97cec3f047210d5%2Fimage%20(116).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

### Using IED Explorer

The free IEC 61850 tool IED Explorer is used as an MMS client. This section shows how to use it.

## Change Setting Groups

The first thing to do is to make sure the data that is transmitted via the MMS Client/Server communication is shown in the tool. This is related to the section Scenario3: MMS Control.

Press the setting option, a window opens which lets the user set up the connection parameters to the server.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-898544b6182d9e7b1f38cac3c8dd0362b18183e4%2Fiec61850-example-mms-goose-5.png?alt=media" alt=""><figcaption></figcaption></figure>

The next picture shows the server parameters. The IP address is for the simulator that is used for this example model. The TCP Port is the one used for IncB\_PUBCU which was shown in the section IEC 61850 I/O Interface on this page. After the simulator and IED is setup, press OK to save this information.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9f2c24a17ebecf5f537eb2d466bef46fe35e16a1%2Fiec61850-example-mms-goose-6.png?alt=media" alt=""><figcaption></figcaption></figure>

The simulator can be selected from the drop down menu and by pressing Play, in the IED View (MMS), you should be able to see the name of the simulator appear.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-0a57bcefeedd5919faab6b9a1f16091607af9f4d%2Fiec61850-example-mms-goose-7.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-88b719e0eb508b464191b2065efaad715785d66f%2Fiec61850-example-mms-goose-8.png?alt=media" alt=""><figcaption></figcaption></figure>

Expand the IED with simulator IP address to view the IED data model. You need to find the following information: **K1IncB1PUBCUOC4\_1.** This is the logical device that has data which is used in the model. It is the same one as shown in the IEC 61850 I/O interface page, in the data model of the IED

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-77ca919068b70fe3a7bb01efc99e9df55b48cca1%2Fiec61850-example-mms-goose-9.png?alt=media" alt=""><figcaption></figcaption></figure>

As it can be seen, the value of this data attribute is 0. Use the right mouse click on "f" on the left side of the screen after you have expanded the IED data model. Choose Write Data.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9dc751d3590047df9569105e7a7a77c3aa7c120b%2Fiec61850-example-mms-goose-10.png?alt=media" alt=""><figcaption></figcaption></figure>

Highlight the field "New Value" on the next screen and type 1 or 2.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-61f627b722e63e6c5467b21d6ccdd55995ae4149%2Fiec61850-example-mms-goose-11.png?alt=media" alt=""><figcaption></figcaption></figure>

If you press OK, the setting groups will be changed between 1 and 2.

{% hint style="info" %}
You can use other values here too but the model will consider 1 or 2.
{% endhint %}

## Show Reports and Data Sets

This section shows how to enable reports and view data in data sets. It is relevant to viewing MMS reports in the Simulation and Results section.

First, establish a connection to the IED using the TCP Port and simulator address. You can find the TCP Port for each IED.

For this example, the information for **IncAPUBCU** is used. It has the TCP port of **109**. So, click on the setting option, keep the IP address of the simulator the same value and change TCP port to 109. You might need to press play again for the tool to find the reports from this IED.

Once the communication is established and IED Explorer is showing the data model and information for the IED, click on IEC View (61850) in the IedTreeView panel and expand the K1IncA1PUBCUCFG. You need to expand one of these logical nodes to find the Logical Node LLN0 and the subsequent rcb.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-dec88c36eb13e9f5720266ccd6eb629336c57c71%2Fiec61850-example-mms-goose-12.png?alt=media" alt=""><figcaption></figcaption></figure>

Expand on ds\_rcb4 to view the measurements from bay INCA. Expand until you reach **phsA** and click on it to show its values on the right side of the page under the IedDataView.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-0983bdf6babf31ab99278803038d4ce2c4516c2b%2Fiec61850-example-mms-goose-13.png?alt=media" alt=""><figcaption></figcaption></figure>

Press play in the IedDataView page to see the values for both magnitude and phase of the current phase A be updated automatically as the simulation is running. Once you do an acquisition on ScopeView, you might be able to catch the high current value in IED Explorer too. But that depends on whether data in IED Explorer is updated fast enough to catch the quick fluctuations of the current.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3bc6d2a2969eebb2c55f63a1e57e940c40bc2345%2Fimage%20(117).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/examples/protection/iec-61850-substation-automation-system-sas-with-mms.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.
