> 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/inverse-time-overcurrent-relay.md).

# Inverse Time Overcurrent Relay

## Description

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

The **Inverse Time Overcurrent Relay** block, located in the **RT-LAB/ePHASORSIM/Others** library, is a generic protection relay based on positive-sequence current measurements. When the measured current magnitude exceeds the configured pickup current, the relay operates after a delay determined by the selected inverse-time characteristic and Time Dial Setting. As the current increases, the operating time decreases and approaches the instantaneous operating time.

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

The relay operating time is calculated using the **IEEE C37.112-1996** inverse-time overcurrent equation. The operating time depends on the measured current magnitude (*I*<sub>*mag*</sub>), the pickup current (*I*<sub>*pickup*</sub>), the Time Dial Setting *TDS*, and the coefficients (*a*, *b*, and *c*) associated with the selected relay characteristic curve. Ten inverse-time characteristics are available, including both **U.S.** and **IEC** standard curves.

$$
T\_{\mathrm{relay}} = TDS \left( a+ \frac{b} { \left(\frac{I\_{\mathrm{mag}}}{I\_{\mathrm{pickup}}}\right)^c-1 } \right)
$$

The relay uses the positive-sequence current magnitude *I*<sub>*mag*</sub>​ in per unit and is compatible with the *I*<sub>*mag*</sub> signals available from positive-sequence components. A single block can model multiple relays through vector inputs, parameters, and outputs.

The relay provides complementary `Trip` and `Trip'` outputs. When an overcurrent condition is detected, both outputs latch in their fault states. The outputs can be reset only when `Reset = 1` and the measured current has fallen below the pickup current.

| State            | Trip | Trip' |
| ---------------- | ---- | ----- |
| Normal condition | `0`  | `1`   |
| Fault condition  | `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-e3dab8f21b2c7758e2ab307880452fefc0b4d335%2Finverse-time-overcurrent-mask.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="151.5">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Simulation Time-step (s)</strong></td><td>Simulation time step used by the relay model, in seconds.</td></tr><tr><td><strong>Number of Relays</strong></td><td>Number of relays represented by the block. The current, reset, pickup-current, Time Dial Setting, and output vectors must be configured consistently with this value.</td></tr><tr><td><strong>Relay Characteristics (a, b, c)</strong></td><td>Selects the inverse-time characteristic and its associated coefficients. One characteristic applies to all relays represented by the block. The available selections include five U.S. curves and five IEC curves.</td></tr><tr><td><strong>Pickup Current (p.u.)</strong></td><td>Vector containing the minimum operating current <em>I</em><sub><em>pickup</em></sub>​ for each relay, in per unit. The relay begins timing when <em>I</em><sub><em>mag</em></sub> > <em>I</em><sub><em>pickup</em></sub>.</td></tr><tr><td><strong>Time Dial Setting (s)</strong></td><td>Vector containing the Time Dial Setting (<code>TDS</code>) for each relay. This setting scales the operating time defined by the selected inverse-time characteristic.</td></tr></tbody></table>

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

<table><thead><tr><th width="132.75">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Imag (p.u.)</strong></td><td>Positive-sequence current magnitude monitored by each relay. When <em>I</em><sub><em>mag</em></sub> exceeds the corresponding pickup current, the relay begins operating according to the selected inverse-time characteristic.</td></tr><tr><td><strong>Reset</strong></td><td>Resets the corresponding relay outputs to their normal states when <code>Reset = 1</code> and <em>I</em><sub><em>mag</em></sub> is below the pickup current. A reset command has no effect while the current remains above pickup.</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>Trip</strong></td><td>Asserted when the corresponding relay completes its operating delay. The output remains latched until the relay receives a valid reset condition.<br><code>0</code> = normal; <code>1</code> = fault</td></tr><tr><td><strong>Trip'</strong></td><td>Complement of <code>Trip</code>. The output remains latched until the relay receives a valid reset condition.<br><code>1</code> = normal; <code>0</code> = fault</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/inverse-time-overcurrent-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.
