> 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/50-inst-time-overcurrent-1-ph.md).

# 50 - Inst/Time Overcurrent 1-ph

## Description

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

The **50 - Inst/Time Overcurrent 1-ph** block, located in the **Control Protection Relays** library, operates when the monitored current exceeds a specified pickup value for a configured time delay. The operating quantity can be the RMS value of a phase current, or the positive, negative, or zero sequence of a three-phase current. If the input remains above the pickup value longer than the time delay, the relay asserts the Trip output to 1; otherwise it remains 0. With a time delay set to zero, the element acts as an instantaneous phase overcurrent element; with a non‑zero time delay, it acts as a definite‑time overcurrent element. If the measured current is not above pickup long enough to exceed the time delay, the internal timer resets and no trip is issued.

## Mask parameters

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

<table><thead><tr><th width="220">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Pick up current</strong></td><td>Overcurrent limit value (pu or A) must match the input units.</td></tr><tr><td><strong>Time delay</strong></td><td>Time after which the Trip output becomes 1 if the input remains greater than the pickup current (s).</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="220">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>I</strong></td><td>Single-dimensional signal (pu or A). Use the RMS value of a phase current, or the positive, negative, or zero sequence of a three-phase current.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="220">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Trip</strong></td><td>Output of the 50 overcurrent relay.<br>Defaults to 0; becomes 1 when an overcurrent condition is detected.</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/hypersim/library-blocks-reference/control-protection-relays/50-inst-time-overcurrent-1-ph.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.
