> 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/out-of-step-oos-detection-using-pmus.md).

# Out of Step (OOS) Detection Using PMUs

## Description

The **Out-of-Step Detection** example, located in **File > Open an Example File > Protection**, uses the well-known 4-machine, 2-area power system benchmark \[1] to demonstrate synchrophasor-based wide-area monitoring and control.

The objective is to evaluate an Out-Of-Step (OOS) detection algorithm that computes slip frequency and acceleration from positive-sequence voltage synchrophasors measured by two PMUs. The OOS detection asserts when the operating point remains outside the stable region for 200 ms. The model runs at 50 Hz with a fixed 50 µs time step.

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

## Requirements

This example model does not require any additional hardware or licenses.

An external clock is optional and requires a syn1588 PCIe Oregano card.

## Detailed explanation

The example model has two pages. The first page "**Power System**" contains the 4-machine 2-area power system benchmark which is shown in the image above along with highlighted busbars and switches.

The second page "**P\&C**" contains the PMU and the OOS block.

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

PMU1 and PMU2 are connected to Bus 3 and Bus 7, respectively. Each PMU sends the positive-sequence voltage angle to the OOS detection block. Both PMUs are configured for 50 Hz, P class, 50 frames per second.

### PMU block

The [**PMU (Based on IEEE Std C37.118.1 Annex C)**](https://www.opal-rt.com/docs/hypersim/examples/protection/out-of-step-oos-detection-using-pmus/pmu-based-on-ieee-std-c37.118.1-annex-c.md) block computes three-phase and positive-sequence phasors (magnitude–angle or real–imaginary), frequency, and rate of change of frequency (ROCOF) from three-phase instantaneous voltage or current inputs. The time reference can be the simulation time or an external timing reference.

* **Performance classes**: P class (faster response for protection) and M class (higher accuracy for measurement).
* **Reporting rate**: 0.5, 1, or 2 samples/cycle, corresponding to 25, 50, or 100 S/s at 50 Hz; 30, 60, or 120 S/s at 60 Hz.
* **Phasor output format**: magnitude–angle or real–imaginary.

### External clock

If the simulator includes a syn1588 PCIe Oregano card, the PMU block can use an external clock by selecting the “External clock” option. In this case, provide appropriate master clock signals to the PMU’s “Clock” input, define a [**Synchronization**](https://www.opal-rt.com/docs/hypersim/configure-ios/time-synchronization-driver.md) interface in the [**I/O Interface Configuration**](broken://spaces/N9x5CUu79pubjsBH7Ja1/pages/KaQ9kEO4w6pf3ygQpusj), and map the “Seconds” and “Nanoseconds” data points of the Synchronization interface to the input sensors of the clock block in HYPERSIM.

### Out-Of-Step detection block

The OOS detection algorithm is based on PMU measurements \[2]. The angle difference between the two buses is defined as:

$$
\delta = \angle V^{\mathrm{PMU1}}*{1} - \angle V^{\mathrm{PMU2}}*{2}
$$

Slip frequency and acceleration are computed as:

$$
S = \frac{\Delta \delta}{\Delta t} \\\[8pt]
A = \frac{\Delta S}{\Delta t}
$$

The OOS detection block sampling time is 15 ms. The stable region is defined as in \[2].

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

In this example: k = −15, b1 = 10, b2 = −10. The time delay setting is 200 ms: if the operating point remains outside the stable region for more than 200 ms, the OOS detection asserts.

## Simulation and results

### Simulation setup

{% stepper %}
{% step %}
Open Network → **Load Flow** and set the frequency to **50 Hz**. You do not need to execute the load flow in this dialog.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6028bb0eb8f6096010484c5402677483ae682962%2Fimage%20(165).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-5bd53d3a0eacc1f00dcda1664a0aa8855721c9ab%2Fimage%20(1572).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Open Simulation Settings, enable **Perform load flow and set initial conditions at simulation start**, set the time step to **50 µs**, select your simulator, and run the simulation.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-196673cb4f0c8dc3ad5c7976427e8d7683cfd734%2Fimage%20(1573).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-9bbb3b74dc4d4e8177c4fe723b3d30a481460642%2Fimage%20(1574).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Test scenario

Assume line distance protection at Bus 6 uses Zone 1 set to 80% of the line with instantaneous tripping and Zone 2 set to 120% with a 200 ms delay. The same settings are applied at Bus 4. The distance protection is not modeled; breaker operations emulate it.

Because the fault is near 0% of the line, the Bus 6 protection detects the fault quickly and trips BR2. Assume pickup one cycle after the fault and a 50 ms breaker opening time; BR2 opens at t = 1.07 s.

Without a transfer trip scheme, the Bus 4 distance protection picks up after a 200 ms delay and trips BR1. Assume pickup at t = 1.22 s and a 50 ms breaker opening time; BR1 opens at t = 1.27 s.

Start the simulation, open the ***Out\_of\_Step\_Detection\_50.xml*** template in ScopeView, enable **Sync** and **Trig** in the acquisition parameters, and click Start.

On the Out of Step page, the angle difference exceeds 180 degrees and the bus frequencies diverge from 50 Hz in opposite directions. The Slip vs. Acceleration trajectory moves outside the stable region after the fault and breaker operations. The OOS detection asserts at 4.09 s, which is 3.09 s after the fault.

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

The slip-acceleration trajectory plotted on the Slip VS Acceleration page (figure shown below) shows that the operating point goes outside the stable region after the fault and the breaker operation.

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

The OOS detection block is asserted at 4.09 s, which is 3.09 s after the fault occurs.

## References

\[1] Klein, M., G. J. Rogers, and P. Kundur. "A fundamental study of inter-area oscillations in power systems".\_IEEE Transactions on Power Systems\_6.3 (1991): 914-921.

\[2] Schweitzer, Edmund O., et al. "Advanced real-time synchrophasor applications."*proceedings of the 35th Annual Western Protective Relay Conference, Spokane, WA*. 2008.


---

# 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/out-of-step-oos-detection-using-pmus.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.
