> 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/simulink-blocks-reference/rt-lab-library/double-blinder-out-of-step-relay.md).

# Double Blinder Out-of-Step Relay

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-1d40dbb774cde7c59b2f346a05b0f82faade8129%2Fdouble-blinder-out-of-step-relay.png?alt=media" alt="" width="222"><figcaption></figcaption></figure>

The **Double Blinder Out-of-Step Relay** block, located in the **RT-LAB/ePHASORSIM/Others** library, uses positive-sequence impedance to distinguish faults from stable and unstable power swings. The relay monitors the rate at which the measured impedance trajectory crosses two parallel blinders in the impedance plane. Fault trajectories typically cross the blinders faster than power-swing trajectories.

Timing begins when the impedance trajectory enters the outer blinder. If the trajectory remains between the outer and inner blinders longer than the configured **PSB Delay**, the relay identifies a power swing. A swing is classified as unstable if the trajectory subsequently enters the inner blinder zone; if the trajectory leaves the outer blinder without entering the inner zone, the swing is classified as stable.

For an unstable swing, the **Out-of-Step Trip (OST)** can operate either when the impedance trajectory enters the inner blinder zone, known as **Trip On-The-Way-In (TOWI)**, or when it leaves the inner blinder zone, known as **Trip On-The-Way-Out (TOWO)**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-adce407c4077afcaad1ee0ed27e55f80a6d99b24%2Fdouble-blinder-out-of-step-relay-graph.png?alt=media" alt=""><figcaption></figcaption></figure>

The **OOS** and **OST** outputs are complementary so that **OST** can interface with the `status` input available on positive-sequence components. The outputs remain latched after detection and can be reset only when `Reset = 1` and the impedance trajectory is outside the inner blinder zone

| State            | OOS | OST |
| ---------------- | --- | --- |
| Normal condition | `0` | `1` |
| OOS detection    | `1` | `0` |

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-399c71a86bad30b0e9dcc5c965ccba963e2acc30%2Fdouble-blinder-out-of-step-relay-mask.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="181.5">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Blinder Angle (deg)</strong></td><td>Inclination angle of the inner and outer blinders in the impedance plane, in degrees.</td></tr><tr><td><strong>Inner Blinder (p.u.)</strong></td><td>Perpendicular distance between the inner blinder and <em>Z</em><sub><em>Total</em></sub>, in per unit.</td></tr><tr><td><strong>Outer Blinder (p.u.)</strong></td><td>Perpendicular distance between the outer blinder and <em>Z</em><sub><em>Total</em></sub>​, in per unit.</td></tr><tr><td><strong>PSB Delay (ms)</strong></td><td>Minimum time that the impedance trajectory must remain between the outer and inner blinders to be classified as a power swing, in milliseconds.</td></tr><tr><td><strong>OOS Tripping Logic</strong></td><td>Selects when <strong>OST</strong> operates during an unstable swing.<br><code>0</code> : Operates when the impedance trajectory enters the inner blinder zone (<strong>TOWI</strong>).<br><code>1</code> : Operates when the impedance trajectory leaves the inner blinder zone (<strong>TOWO</strong>).</td></tr><tr><td><strong>Number of Relays</strong></td><td>Number of relays represented by the block. The block uses vector inputs and outputs to model multiple relays.</td></tr></tbody></table>

## Inputs <a href="#inputs" id="inputs"></a>

<table><thead><tr><th width="136.5">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Vmag (p.u.)</strong></td><td>Positive-sequence voltage magnitude used to calculate the impedance trajectory.</td></tr><tr><td><strong>Vang (deg)</strong></td><td>Positive-sequence voltage angle used to calculate the impedance trajectory.</td></tr><tr><td><strong>Imag (p.u.)</strong></td><td>Positive-sequence current magnitude used to calculate the impedance trajectory.</td></tr><tr><td><strong>Iang (deg)</strong></td><td>Positive-sequence current angle used to calculate the impedance trajectory.</td></tr><tr><td><strong>Reset</strong></td><td>Resets the corresponding <strong>OOS</strong> and <strong>OST</strong> outputs to their normal states when <code>Reset = 1</code> and the impedance trajectory is outside the inner blinder zone.</td></tr></tbody></table>

## Outputs <a href="#outputs" id="outputs"></a>

<table><thead><tr><th width="129.5">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>OOS</strong></td><td>Indicates that the corresponding relay has detected an unstable power swing. The output remains latched until a valid reset condition occurs.<br><code>0</code> = normal; <code>1</code> = out-of-step detection</td></tr><tr><td><strong>OST</strong></td><td>Complement of <strong>OOS</strong>, provided for compatibility with the <code>status</code> input of positive-sequence components. The output remains latched until a valid reset condition occurs.<br><code>1</code> = normal; <code>0</code> = out-of-step detection</td></tr></tbody></table>


---

# 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/simulink-blocks-reference/rt-lab-library/double-blinder-out-of-step-relay.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.
