> 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/library-blocks-reference/control-protection-relays/21-mho-distance.md).

# 21 - MHO Distance

## Description

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

The **21 - MHO Distance** block, located in the **Control Protection Relays** library, models a **generic MHO phase distance element** with two protection zones and an optional permissive overreach transfer trip (POTT) logic. The relay does not include polarizing quantities, memory actions, loss of potential, reactance functions, or load encroachment.

The relay uses the three-phase voltages and currents measured at its end of the transmission line. It implements two MHO protection zones whose characteristics are circles on the R–X plane.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f5309113e5c5e15770fdfc4b6bde60b0886615df%2Fimage%20(584).png?alt=media" alt="" width="275"><figcaption><p>In this example, zone 1 has an 80% reach<br>and zone 2 has a 120% reach.</p></figcaption></figure>

The circle centers lie on the impedance axis and pass through the origin. The diameter of each circle equals the total line impedance multiplied by the zone reach percentage.

$$
\theta = \operatorname{atan}!\left( \frac{X\_1}{R\_1} \right), \quad Z\_{\text{line}} = \sqrt{R\_1^2 + X\_1^2}
$$

R<sub>1</sub> and X<sub>1</sub> are the total positive-sequence resistance and reactance of the line.

The model uses a Discrete Fourier Transform to compute the fundamental phasors (magnitude and angle) of V<sub>a</sub>, V<sub>b</sub>, V<sub>c</sub>, I<sub>a</sub>, I<sub>b</sub>, and I<sub>c</sub>. The zero-sequence current phasor is calculated from the three-phase currents as:

$$
I\_0 = \frac{1}{3}(I\_a+I\_b+I\_c)
$$

These phasors are used to compute six impedances: Z<sub>a</sub>, Z<sub>b</sub>, Z<sub>c</sub>, Z<sub>ab</sub>, Z<sub>bc</sub>, and Z<sub>ca</sub>. For phase A, for example:

$$
Z\_a = \frac{V\_a}{I\_a + k I\_0}
$$

$$
Z\_{ab} = \frac{V\_a - V\_b}{I\_a - I\_b}
$$

where the residual compensation factor k is:

$$
k=\frac{Z\_0-Z\_1}{Z\_1}
$$

If any computed impedance enters a zone circle and remains inside for that zone’s time delay, the trip signal changes from 0 to 1. The POTT logic operates as follows: when the local zone 2 picks up, the relay sends a permissive tripping signal (SPT) to the remote end. If the remote relay has permissive tripping enabled, receives the signal, and detects the fault in its zone 2, it trips immediately (without waiting for the zone 2 time delay). Similarly, the local relay trips immediately if it receives a remote permissive tripping signal (RPT) and detects a zone 2 fault.

## Mask parameters

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

{% tabs %}
{% tab title="Line parameters" %}

<table><thead><tr><th width="258.5086669921875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Frequency</strong></td><td>Frequency of the measured current signals (Hz). Supported values: 50 or 60 Hz. Default: 60.</td></tr><tr><td><strong>Line Length</strong></td><td>Total line length (km). Default: 200.</td></tr><tr><td><strong>Positive Sequence Resistance</strong></td><td>Positive-sequence resistance of the line (ohm/km). Default: 0.011748.</td></tr><tr><td><strong>Zero Sequence Resistance</strong></td><td>Zero-sequence resistance of the line (ohm/km). Default: 0.29014.</td></tr><tr><td><strong>Positive Sequence Inductance</strong></td><td>Positive-sequence inductance of the line (H/km). Default: 0.00077518.</td></tr><tr><td><strong>Zero Sequence Inductance</strong></td><td>Zero-sequence inductance of the line (H/km). Default: 0.0030241.</td></tr></tbody></table>
{% endtab %}

{% tab title="Settings" %}

<table><thead><tr><th width="258.5086669921875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Zone 1 reach</strong></td><td>Forward-looking protected distance in zone 1 (% of total line impedance). Default: 80.</td></tr><tr><td><strong>Zone 2 reach</strong></td><td>Forward-looking protected distance in zone 2 (% of total line impedance). Default: 120.</td></tr><tr><td><strong>Zone 1 Time Delay</strong></td><td>Time delay for zone 1 (s). A half-cycle delay is recommended to avoid overreach. Default: 0.0083.</td></tr><tr><td><strong>Zone 2 Time Delay</strong></td><td>Time delay for zone 2 (s). Default: 0.3333.</td></tr><tr><td><strong>Enable Permissive Tripping</strong></td><td>Enable/disable POTT logic. Default: disabled.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## Inputs

<table><thead><tr><th width="259.900146484375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Vabc</strong></td><td>Three-element voltage input (V): Va, Vb, Vc.</td></tr><tr><td><strong>Iabc</strong></td><td>Three-element current input (A): Ia, Ib, Ic.</td></tr><tr><td><strong>RPT</strong></td><td>Remote permissive tripping signal (binary). If RPT = 1 and a zone 2 fault is detected, the relay trips immediately, bypassing the zone 2 time delay.</td></tr><tr><td><strong>Reset</strong></td><td>Reset command (binary). The relay resets when this signal becomes 1.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="259.900146484375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Trip</strong></td><td>Trip command (binary). Defaults to 0. Becomes 1 if a fault is detected and remains within zone 1 or zone 2 for the configured time delay, or if permissive tripping is active (RPT received) and a zone 2 fault is detected.</td></tr><tr><td><strong>SPT</strong></td><td>Local permissive tripping signal (binary). Asserted when a zone 2 fault is detected.</td></tr><tr><td><strong>m</strong></td><td>Ra, Rb, Rc, Rab, Rbc and Rca measured by the relay (ohm)<br>Xa, Xb, Xc, Xab, Xbc and Xca measured by the relay (ohm)</td></tr></tbody></table>

{% hint style="info" %}
Ra, Rb, Rc, Rab, Rbc and Rca named as outputs R\_0 to R\_5 and Xa, Xb, Xc, Xab, Xbc and Xca named as outputs X\_0 to X\_5.
{% endhint %}

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6675de08b670ef34744a7ad9940360f0afbc2ee8%2Fimage%20(586).png?alt=media" alt="" width="563"><figcaption><p>Za trajectory during a phase A-to-ground fault (Plot in ScopeView, with “versus (R_0, X_0)”)</p></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/library-blocks-reference/control-protection-relays/21-mho-distance.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.
