> 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/artemis-library/21-mho-distance-relay.md).

# 21 MHO Distance Relay

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-e90f8ff5cddd658fb08283eed2a782dea5adaf80%2FArtemis_21MHO_dist_relay_block.png?alt=media" alt="" width="128"><figcaption></figcaption></figure>

**MHO Phase Distance Relay**, located in the **ARTEMiS/Tools/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 operates on 50 Hz or 60 Hz systems.

The relay measures three-phase voltages and currents at one end of a transmission line and applies MHO characteristics on the R–X plane with two forward-looking protection zones. Each MHO circle is centered on the line impedance axis and passes through the origin; the circle diameter equals the total line impedance multiplied by the configured zone reach percentage. For a line with positive-sequence resistance R<sub>1</sub> and reactance X<sub>1</sub>, the impedance angle is $$\Theta = atan \frac{X\_1} {R\_1}$$ and the total line impedance magnitude is $$Z\_line = \sqrt(R\_1^2 + X\_1^2)$$ .

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-d52bfc34e1299d1a35672eaed4efe5bc0a0d8d75%2FArtemis_21MHO_dist_relay_charca.png?alt=media" alt="" width="284"><figcaption><p>Relay characteristics on the R-X plane</p></figcaption></figure>

**Zone reach examples**

Zone 1 at 80% and Zone 2 at 120% of the total line impedance.

{% hint style="info" %}
For Zone 1, a half-cycle delay is recommended to avoid overreach.
{% endhint %}

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 $$I\_0 = \frac{1}{3} (I\_a + I\_b + I\_c)$$. Using these phasors, it computes 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 example, $$Z\_a = \frac{V\_a}{I\_a + kI\_0}$$and $$Z\_{ab} = \frac{V\_a - V\_b}{I\_a + I\_b}$$, where the residual compensation factor $$k = \frac{Z\_0 - Z\_1}{Z\_1 }$$.

If any computed impedance enters a zone circle and remains inside for the configured time delay, the relay asserts a trip. With POTT enabled, when Zone 2 picks up, the local relay sends a permissive tripping signal (SPT) to the remote relay. If a relay receives a permissive signal (RPT) and detects a Zone 2 fault, it trips immediately without waiting for the Zone 2 delay. Advanced features such as polarizing quantities, memory actions, loss of potential, reactance functions, and load encroachment are not included.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-2c9183016cd29cf4909c3497a553013febb2e140%2FArtemis_21MHO_dist_relay_schem.png?alt=media" alt="" width="336"><figcaption><p>The relay tripping logic</p></figcaption></figure>

{% hint style="danger" %}
This block requires a valid RT-LAB license on the simulator with the feature ARTEMiS enabled. Refer to[ ARTEMiS Requirements](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/power-systems-with-artemis/artemis-requirements.md) for details.
{% endhint %}

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-64aa328ea3c13aa1231f913820da68b62cb84afc%2FArtemis_21MHO_dist_relay_mask.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

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

| Parameter                        | Description                                                           |
| -------------------------------- | --------------------------------------------------------------------- |
| **Frequency**                    | Nominal frequency of the measured signals (Hz). Supports 50 or 60 Hz. |
| **Line length**                  | Total line length (km).                                               |
| **Positive sequence resistance** | Positive-sequence resistance of the line (ohm/km).                    |
| **Positive sequence inductance** | Positive-sequence inductance of the line (H/km).                      |
| **Zero sequence resistance**     | Zero-sequence resistance of the line (ohm/km).                        |
| **Zero sequence inductance**     | Zero-sequence inductance of the line (H/km).                          |
| {% endtab %}                     |                                                                       |

{% tab title="Protection settings" %}

| Parameter                           | Description                                                                        |
| ----------------------------------- | ---------------------------------------------------------------------------------- |
| **Enable MHO distance relay**       | Enable or disable relay operation.                                                 |
| **Zone 1**                          | Forward-looking reach of Zone 1 as a percentage of line length (% of line length). |
| **Zone 2**                          | Forward-looking reach of Zone 2 as a percentage of line length (% of line length). |
| **Zone 1 delay**                    | Time delay for Zone 1 (s). A half-cycle delay is recommended to avoid overreach.   |
| **Zone 2 delay**                    | Time delay for Zone 2 (s).                                                         |
| **Enable permissive transfer trip** | Enable the permissive overreach transfer tripping (POTT) logic.                    |
| {% endtab %}                        |                                                                                    |
| {% endtabs %}                       |                                                                                    |

## Conservating ports

<table><thead><tr><th width="240.4000244140625">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>V</strong><sub><strong>abc</strong></sub></td><td>Three-phase voltages: Va, Vb, Vc.</td></tr><tr><td><strong>Iabc</strong></td><td>Three-phase currents: Ia, Ib, Ic.</td></tr><tr><td><strong>RPT</strong></td><td>Received permissive tripping signal from the remote relay. If received while a Zone 2 fault is detected, the relay trips immediately (Zone 2 delay is bypassed).</td></tr><tr><td><strong>Reset</strong></td><td>Relay reset signal. The relay resets when this input becomes 1.</td></tr><tr><td><strong>Trip</strong></td><td>Trip command (default 0). Becomes 1 when a Zone 1 or Zone 2 fault persists for the configured delay, or when a permissive trip is received and the fault is in Zone 2.</td></tr><tr><td><strong>SPT</strong></td><td>Permissive tripping signal sent from the local relay. Asserted when a fault is detected in Zone 2.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

<table><thead><tr><th width="241.199951171875">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>m</strong></td><td>Monitoring signals</td></tr></tbody></table>

<details>

<summary>m: vector of monitoring signals</summary>

**Zone1\_trip:** Zone 1 trip command (default 0). Becomes 1 when a Zone 1 fault persists for the configured delay.\
**Zone2\_trip:** Zone 2 trip command (default 0). Becomes 1 when a Zone 2 fault persists for the configured delay.\
**RPT\_trip:** Trip command triggered by a received permissive signal (default 0). Becomes 1 when a permissive trip is received and the fault is in Zone 2.\
**RX:** measured by the relay

| Name     | Description                      |
| -------- | -------------------------------- |
| **R\_0** | Ra measured by the relay (ohm).  |
| **R\_1** | Rb measured by the relay (ohm).  |
| **R\_2** | Rc measured by the relay (ohm).  |
| **R\_3** | Rab measured by the relay (ohm). |
| **R\_4** | Rbc measured by the relay (ohm). |
| **R\_5** | Rca measured by the relay (ohm). |
| **X\_0** | Xa measured by the relay (ohm).  |
| **X\_1** | Xb measured by the relay (ohm).  |
| **X\_2** | Xc measured by the relay (ohm).  |
| **X\_3** | Xab measured by the relay (ohm). |
| **X\_4** | Xbc measured by the relay (ohm). |
| **X\_5** | Xca measured by the relay (ohm). |

</details>


---

# 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/artemis-library/21-mho-distance-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.
