> 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/examples/protection/directional-overcurrent-protection.md).

# Directional Overcurrent Protection

## Description

The **Directional Overcurrent** example, located in **File > Open an Example File > Protection**, demonstrates the operation and coordination of Directional Overcurrent (505167) relays on a 25 kV, 60 Hz distribution feeder with both an upstream grid and a distributed generator (DG).

This example highlights relay selectivity, the role of backup protection, and the impact of enabling or disabling the directional element, the focus is on feeder protection.

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

## Requirements

This example model does not require any additional hardware or licenses.

{% hint style="danger" %}

## For real-time execution

When executing in real time on a Red Hat simulator, this model does not work with the “opicc” compiler setting (Settings > Target > Compiler and Linkerworks).
{% endhint %}

## Detailed explanation

Protection systems help in the safe operation of a power network by isolating the faulted section through breakers. The relays within that section respond in a coordinated fashion to achieve high selectivity. While the majority of the relays in the existing network are non-directional, there are certain cases where direction-based discrimination is required to determine if a relay should respond or not. The co-ordinated response of relays along with directionality ensures the safe operation of the network and minimizes service interruptions. Directional overcurrent protection relays are very useful in this regard.

Directional overcurrent protection is used to protect the system when fault currents could circulate in either direction along the network line. With the increasing penetration of Distributed Generation (DG) sources at the distribution network, it becomes even more important to implement directional protection to provide correct fault detection and ensure protection co-ordination.

### Network overview

A 25 kV, 60 Hz distribution feeder includes two sources: an upstream grid (voltage source) and a 5 MVA, 2.4 kV DG (synchronous machine) connected through a 2.4 kV / 25 kV Delta-lead/Star-grounded transformer. The DG operates at 1.8 MW in PV mode. The feeder supplies diverse loads, including dynamic loads, unbalanced loads, and induction motors.

Current Transformer (CT) and Voltage Transformer (VT) behavior is emulated using sensors with ratios of 100 A / 1 A (CT) and 25 kV / 110 V (VT).

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

The network is divided into three sections (1, 2, and 3). Six relays protect the sections as configured below.

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

|                       | **Relay** | <p><strong>Directional /</strong><br><strong>Non-Directional</strong></p> | **Set direction** |
| --------------------- | --------- | ------------------------------------------------------------------------- | ----------------- |
| **Downstream Relays** | 1         | Non-directional                                                           | -                 |
|                       | 2         | Directional                                                               | Left to Right     |
|                       | 3         | Directional                                                               | Left to Right     |
| **Upstream Relays**   | 4         | Non-directional                                                           | -                 |
|                       | 5         | Directional                                                               | Right to Left     |
|                       | 6         | Directional                                                               | Right to Left     |

{% hint style="info" %}
**Assumptions**

* Fuses, reclosers, and sectionalizers are not modeled. Lateral lines are protected by main-line directional overcurrent relays.
* DG protection is not covered; the focus is feeder protection.
  {% endhint %}

### Relay parameters

## Directional settings

In relays 2, 3, 5, and 6, the directional element (67P) is enabled by checking “*Enable phase directional 67P*.” The Element Characteristic Angle (ECA) is set to 30 degrees. In relays 1 and 4, the directional element (67P) is disabled.

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

## Coordination of the downstream relays

The table below shows the parameters of the downstream relays, and the methodology of time dial calculation is followed:

| Relay | Base Current (A) | Base Voltage (V) | 51P Pickup current (pu) | Time Dial (s) | Curve Type        |
| ----- | ---------------- | ---------------- | ----------------------- | ------------- | ----------------- |
| 1     | 0.59             | 65.508           | 2.0                     | 0.418         | U.S. Inverse (U2) |
| 2     | 0.18             | 65.508           | 2.2                     | 0.286         | U.S. Inverse (U2) |
| 3     | 0.29             | 65.508           | 1.3                     | 0.04          | U.S. Inverse (U2) |

Pickup current selection guideline: 1.2 I<sub>full\_load</sub> < I<sub>pickup</sub> < 1/3I<sub>min\_fault</sub>

Operating time for the U.S. Inverse (U2) curve per IEEE C37.112-2018:

$$
t\_{\text{Operation}} = \text{T.D.} \left( 0.18 + \frac{5.95}{\left( \frac{I\_{\text{fault}}}{I\_{\text{pickup}}} \right)^{2} - 1} \right)
$$

where T.D. is the Time Dial setting.

**Time Dial calculation**

**Step 1: Set Time Dial for relay 3**

Choose the lowest Time Dial for relay 3 (0.04 s). No intentional time delay is added because it has no backup responsibility.

For a close-in three-phase-to-ground fault at relay 3 (I<sub>fault</sub> = 6.5 A), the operation time is:

$$
t\_{\text{Operation}} = 0.04 \left( 0.18 + \frac{5.95}{\left( \frac{6.50}{1.3 \times 0.29} \right)^2 - 1} \right)\\\[8pt]
t\_{\text{Operation}} = 0.008\ \text{s}
$$

**Step 2: Set Time Dial for relay 2**

Coordinate relay 2 with relay 3 for the same close-in fault at relay 3. The expected operation time for relay 2 is:

$$
0.008 s + 0.05 s = 0.058 s \\\[8pt]

0.058 = \text{T.D.} \left( 0.18 + \frac{5.95}{\left( \frac{6.50}{2.2 \times 0.18} \right)^2 - 1} \right) \`\`\`

```\text{T.D.} = 0.286\ \text{s}
$$

**Step 3: Coordinate relay 1 with relay 2**

Apply the same methodology to set relay 1.

<figure><img src="/files/XCUFdGxBLjePORNHhyJt" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Fault studies were performed to determine fault currents used in the coordination calculations.
{% endhint %}

## Coordination of the upstream relays

Upstream relay settings:

<table><thead><tr><th width="84.66668701171875">Relay</th><th width="123.111083984375">Base Current (A)</th><th width="125">Base Voltage (V)</th><th width="126.8887939453125">51P Pickup current (pu)</th><th width="128.4444580078125">Time Dial (s)</th><th>Curve Type</th></tr></thead><tbody><tr><td>4</td><td>0.41</td><td>65.508</td><td>1.3</td><td>0.38</td><td>U.S. Inverse (U2)</td></tr><tr><td>5</td><td>0.09</td><td>65.508</td><td>2</td><td>0.305</td><td>U.S. Inverse (U2)</td></tr><tr><td>6</td><td>0.25</td><td>65.508</td><td>1.3</td><td>0.04</td><td>U.S. Inverse (U2)</td></tr></tbody></table>

Characteristic curves corresponding to the above settings are provided in the model.

<figure><img src="/files/YhJW8flOxBKoN4XHAtql" alt=""><figcaption></figcaption></figure>

## Simulation and results

Initialize the network using Load Flow before starting the simulation.

* Open Network > Load Flow and set frequency to **60 Hz**.
* Open Simulation Settings and enable “Perform load flow and set initial conditions at simulation start.”
* Set the time step to **50 us**.

### Case 1: Overcurrent coordination and the role of the backup protection scheme

Apply an ABC-G fault at t = 0.2 s on a 7 km lateral line (L8) connected at Bus 14 in section 2. Relays 2 and 5 should detect and clear the fault by opening CB 2 and CB 5.

This case also demonstrates breaker-failure backup: if CB 2 fails, relay 1 (backup for section 2) must clear the fault by opening CB 1.

<figure><img src="/files/PNlDtXhkqqiXZnv5GyNr" alt=""><figcaption></figcaption></figure>

## Steps

* Open the L8 line control panel (7 km lateral at Bus 14, section 2). In the “_Timing_” tab, enable “_Time programming_.”
* Open Brk2. In the “_General_” tab, change “_Control type_” from “_External (input pins)_” to “_Internal_” to simulate breaker failure (Brk2 not controlled by relay 2 output).

<figure><img src="/files/NrcGaq7YpxNNImRP3T2g" alt=""><figcaption></figcaption></figure>

* Start the simulation and open ScopeView. Load the “Directional\_Overcurrent.xml” template. Ensure both “Sync” and “Trig” are checked, then start data acquisition.

<figure><img src="/files/qPITmIND7BUP7XBLnNj2" alt=""><figcaption></figcaption></figure>

* Downstream: Relay 2 picks up in 0.067 s after fault inception; because Brk2 fails, relay 1 picks up in 0.1975 s and clears the fault by opening CB 1. **This clearly demonstrates the coordination among the relays and the importance of a backup protection scheme.**

<figure><img src="/files/G2Zmu5pCeqNulbGdvlT1" alt=""><figcaption></figcaption></figure>

* Upstream: Relay 5 picks up in 0.0727 s and opens CB 5. Relays 4 and 6 do not operate.

<figure><img src="/files/p6cNkpWsOoZYuvjFhPmb" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1zSfEGrfgQ5HP0XUcksG" alt=""><figcaption></figcaption></figure>

### Case 2: Importance of the directional element

## A. Directional element enabled

Apply an ABC-G fault at t = 0.2 s on a 6 km line (L6) between Bus 26 and Bus 30 in section 3. Downstream relays 1, 2, and 3 see the fault in the set direction; relay 3 has the lowest Time Dial and should clear the fault. Upstream relays 5 and 6 see the reverse direction and should not operate. Upstream non-directional relay 4 should clear the fault.

<figure><img src="/files/7XUOsm34k6FfpvAe1xTX" alt=""><figcaption></figcaption></figure>

**Steps**

* Stop the simulation. In relays 2, 3, and 5, ensure “_Enable phase directional 67P_” is checked.

<figure><img src="/files/gVjbBqtIqDXQJ9LEBBjJ" alt=""><figcaption></figcaption></figure>

* Open the control panel of the line L8 and disable “_Time programming_” in the “_Timing_” tab.
* Open the control panel of the line L6 and enable “_Time programming_” in the “_Timing_” tab.
* Open the control panel of Brk2. In the “_General_” tab, change “_Control type_” from “_Internal_” back to “_External (input pins)_.”
* Start the simulation and observe results in ScopeView.

<figure><img src="/files/OPtUYefEa0av0XUUhwiS" alt=""><figcaption></figcaption></figure>

* Downstream: Relay 3 picks up first in 0.0161 s and opens CB 3.

<figure><img src="/files/LFeYs6Rz0hnoi6WBPx0f" alt=""><figcaption></figcaption></figure>

* Upstream: Relay 4 picks up in 0.1237 s and opens CB 4. Relays 5 and 6 do not operate.

<figure><img src="/files/c0lZ2WDe8VVztEcol4Nb" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Yfm33VmTXr9cYIbfvNSP" alt=""><figcaption></figcaption></figure>

## B. Directional element disabled

The response of the protection system when the directional element (67P) is disabled is shown in this case. The fault conditions are similar as described in Case 2A.

**Steps**

* Stop the simulation and uncheck “_Enable phase directional 67P_” in relays 2, 3, 5, and 6.
* Start the simulation and observe results in ScopeView.

<figure><img src="/files/C31AMcE5r5jiKDzg4Xrw" alt=""><figcaption></figcaption></figure>

* Downstream: All relays see the fault; relay 3 (Time Dial 0.04 s) picks up first in 0.0161 s and opens CB 3.

<figure><img src="/files/LFeYs6Rz0hnoi6WBPx0f" alt=""><figcaption></figcaption></figure>

* Upstream: Relay 6 (now non-directional, Time Dial 0.04 s) picks up in 0.0158 s and opens CB 6, isolating sections 2 and 3. The DG continues to feed the fault in section 3, so relay 4 picks up in 0.1236 s and opens CB 4.

<figure><img src="/files/LvOhRP3SLQgOyt6ZaZhE" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/2fLkPuidBZEU4eK3AWnU" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Even though relay 6 opened in 0.0158 s, relay 3 still sees fault current during breaker operating delay and thus picks up in 0.0161 s because of the breaker operation time dela&#x79;**.**
{% endhint %}

This shows that in the absence of directional elements the relays fail to discriminate between the healthy and faulty sections. This clearly demonstrates the **importance of the directional element which provides selectivity to the Overcurrent relay.**
```


---

# 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/examples/protection/directional-overcurrent-protection.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.
