> 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/line-distance-protection-with-pott-including-testview-project.md).

# Line Distance Protection with POTT including TestView Project

## Description

The **Distance Relay POTT** example, located in **File > Open an Example File > Protection > Distance\_21\_POTT > bank > hnk**, includes a 300 km, 500 kV transmission line and demonstrates the 21 MHO distance relay with a permissive overreach transfer trip (POTT) scheme.

The main objective is to illustrate relay operation for Zone 1 and Zone 2 faults with POTT disabled and enabled on the local relay. Both the local and remote relays are configured with Zone 1 set to 80% of the line with a 1/2-cycle delay to avoid overreach, and Zone 2 set to 120% with a 200 ms delay. **TestView**, the automated testing tool in HYPERSIM, has been used to perform tests on the model in three cases which include 10 tests each.

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

## Requirements

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

## Detailed explanation

The model includes a 300 km, 500 kV transmission line for the demonstration of the 21 MHO Distance Relay. Both relays (Local and Remote) are configured:

* Zone 1: 80% of the line, 1/2-cycle time delay to avoid overreach.
* Zone 2: 120% of the line, 200 ms time delay.

Two different test cases: POTT disabled and POTT enabled on local relay are used to explain the operation of 21MHO Distance relay.

For more information about the distance relay, see the [21 - MHO Distance Relay](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/control-protection-relays/21-mho-distance.md) page.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c0cd9c3fdb1ed5d9f4fde0b4d297bb0dd7aa1ed8%2F6.png?alt=media" alt=""><figcaption><p>Parameters set for both the relays</p></figcaption></figure>

## Simulation and results

### Test 1 setup: Fault in Zone 2 for Local relay with POTT disabled

In this test, a single-line-to-ground fault is applied in Zone 2 of the **local relay** and Zone 1 of the **remote relay**. POTT is disabled.

{% stepper %}
{% step %}
Open the parameter forms of **21MHO1** and **21MHO2**. In the *Settings* tab, uncheck *Enable permissive tripping* to disable the permissive tripping scheme if it is selected.

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

{% step %}
Open the parameter form of **L1** and set *Distance of fault from (+) side* to 270 km so the fault is in Zone 2 of 21MHO1. In the *Timing* tab, set the fault time to t=0.2 s.

Under *Phase operated*, select Phase A and Ground to simulate a single-line-to-ground fault.

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

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

{% step %}
Start the simulation on the workstation (offline) or run in real time on a simulator. The results won't be different from what is shown in this page.
{% endstep %}

{% step %}
Launch ScopeView, open the template **Distance\_Relay\_POTT.svt** from the project folder

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

{% step %}
Check **Sync** and **Trig**, and start data acquisition.

From Page ‘Relay1’ as shown in below figure, it can be seen that Phase A fault current reaches a peak value of 3720A and Relay 1 is asserted at t=0.4112s, which is 0.2112s after the fault occurs. The breaker receives the trip command and opens the three phases to isolate the fault.

Relay1 trips 211.2ms after the fault occurs because the fault is in its Zone 2, which features a time delay setting of 200ms. Since POTT scheme is not enabled, Relay1 Zone 2 only trips when the fault is detected in Zone 2 and remains in Zone 2 for a duration longer than the time delay.

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

Below figure shows Page ‘Relay2’ in the template, it can be seen that Relay 2 trips at t=0.2166s, which is 0.0166s after the fault occurs. This is because the fault falls in the Zone 1 of Relay 2.

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

Below figure shows the measured impedance locus seen by Relay 1. The circles in red and blue represent the protection zones. It can be seen that the measured Phase A impedance (in green) enters and stays in the Zone 2 circle.
{% endstep %}
{% endstepper %}

### Test 2 setup: Fault in Zone 2 for Local relay with POTT enabled

In this test, the same single-line-to-ground fault is applied in Zone 2 of the local relay and Zone 1 of the remote relay. POTT is enabled.

{% stepper %}
{% step %}
Enable POTT by checking *Enable permissive tripping* in the *Settings* tab of **21MHO1** and **21MHO2**.

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

{% step %}
Keep the same fault configuration as in Test 1.
{% endstep %}

{% step %}
Run the simulation (if it has been stopped), open ScopeView template and do an acquisition with Sync and Trig on.

When POTT scheme is enabled, Relay 1 receives the permissive tripping signal from Relay 2 and detects the fault in its Zone 2, thus Relay 1 trips at t=0.2112s and opens the breaker, as shown in below figure.

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

Relay 2 acts in the same way as before. It detects the fault in Zone 1 and when the ½ cycle time delay is satisfied, the trip signal is asserted at t=0.2112s.

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

Below figure shows the measured impedance locus of Relay 1. Since the fault is closer to Relay 2, Relay 2 detects the fault first and sends a transfer trip to Relay 1. As soon as Relay 1 detects the fault in Zone 2, it trips. The impedance locus also shows that Relay 1 trips immediately after the Phase A impedance enters the Zone 2 circle.

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

The above results shows that for the two different test cases: Zone-2 fault with and without POTT (Permissive Overreach Transfer Trip), 21MHO-distance relay can pick up faults in different zones with corresponding time delay settings. POTT function can be enabled to accelerate the operation upon faults in Zone-2.
{% endstep %}
{% endstepper %}

## TestView project

### Introduction

A TestView project is provided to automate testing for three cases, each with 10 tests: **POTT\_DISABLED**, **POTT\_ON\_RELAY1**, and **POTT\_ON\_RELAY1&2**. Each test uses a different fault type and location on the line. The parameters for each test are listed below.

<table><thead><tr><th>Test Number</th><th>Fault distance from WES7 (km)</th><th width="119.1112060546875">Fault type</th><th width="94.666748046875" align="center">Phase A</th><th width="91.111083984375" align="center">Phase B</th><th width="90" align="center">Phase C</th><th width="100" align="center">Phase D</th></tr></thead><tbody><tr><td>1</td><td>30</td><td>L1N</td><td align="center">X</td><td align="center">-</td><td align="center">-</td><td align="center">X</td></tr><tr><td>2</td><td>45</td><td>L2L3</td><td align="center">-</td><td align="center">X</td><td align="center">X</td><td align="center">-</td></tr><tr><td>3</td><td>75</td><td>L1L2L3</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">-</td></tr><tr><td>4</td><td>105</td><td>L2L3N</td><td align="center">-</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>5</td><td>135</td><td>L1N</td><td align="center">X</td><td align="center">-</td><td align="center">-</td><td align="center">X</td></tr><tr><td>6</td><td>165</td><td>L2L3</td><td align="center">-</td><td align="center">X</td><td align="center">X</td><td align="center">-</td></tr><tr><td>7</td><td>195</td><td>L2N</td><td align="center">-</td><td align="center">X</td><td align="center">-</td><td align="center">X</td></tr><tr><td>8</td><td>225</td><td>L2L3N</td><td align="center">-</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>9</td><td>255</td><td>L1N</td><td align="center">X</td><td align="center">-</td><td align="center">-</td><td align="center">X</td></tr><tr><td>10</td><td>270</td><td>L2L3</td><td align="center">-</td><td align="center">X</td><td align="center">X</td><td align="center">-</td></tr></tbody></table>

### Step-by-step guide

This guide shows you how to open the project in TestView, set it up successfully, and run one test case **POTT\_DISABLED**. By following the guide and running the test case, you should be able to run the other two without any problems.

For general information about TestView, see [TestView documentation](https://www.opal-rt.com/docs/hypersim/automation-api-and-scripting/automate-using-testview.md).

{% stepper %}
{% step %}
Open **Distance\_Relay\_POTT.ecf** model from the folder **DISTANCE\_21\_POTT\bank\hnk** of the folder in which you've saved the example model.

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

{% step %}
Open **TestView** (HYPERSIM tab > Tools > TestView). If prompted for analysis, select Yes.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-890812ceb5f46c4d8aba2af2d63bd6d92af7a6a8%2FBTN-testview-ribbon.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In TestView, choose File > Open Project and select **DISTANCE\_21\_POTT.prj** from the model directory.

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

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

{% step %}
Expand **DISTANCE\_21\_POTT** in the Project panel and open the **POTT\_DISABLED** test.

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

{% step %}
Expand DISTANCE\_21\_POTT from the "project" panel on the left to open three tests. Double-click on the "**POTT\_DISABLED**" test.

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

{% step %}
In the panel that will open on the right, double-click on the "Table: \[Export operate time to Excel report]" tree node.

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

{% step %}
Under "Excel export options", specify your Excel File Path by pointing to DISTANCE\_21\_POTT.xlsx which you can find in the model directory. Press "Apply" or "Unlock and Apply" to close the dialog. If you get a notification about unlocking the test, press Yes.

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

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

{% step %}
Double-click on the "HypExcel\_1" tree node.

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

{% step %}
On the next window, choose the same exact excel file in the model directory as before. Press Select HYPERSIM Excel File and afterwards, press Apply.

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

{% step %}
Double-click on the "HyperWorks Test" tree node.

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

{% step %}
Update your session ID by changing your user name in the string. The string's format should be: **/Hypersim/%WINDOWS\_USER%/HyWorks-1**, where %WINDOWS\_USER% is your Windows user name. Press Apply.

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

{% step %}
Double click on In the second toolbar 'HyperWorks Settings' as shown below.

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

{% step %}
Click on the "HYPERSIM Connections ..." button which is the two computers icon as highlighted below.

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

{% step %}
In the next window, make sure the "Current design" section has your name and the name of the .ecf file from the folder DISTANCE\_21\_POTT\bank\hnk.

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

Otherwise, you need to Disconnect the current host, change the Current design to the model name and Connect again. Once the correct file is selected, press Close.

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

{% step %}
Back in "HyperWorks Settings" menu, find the Sensors selection. If there is no sensor file selected and it is showing "none", click on the "..." next to it. If there is already a sensor file DISTANCE\_Relay\_POTT selected. Or if it shows in the drop down menu, then you can skip to the Load Preferences step.

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

{% step %}
The next window is to choose the sensor file for the project. Click on Files of type at the bottom and choose "All files".

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

{% step %}
Move to the model folder and find the sensor file "**Distance\_Relay\_POTT.csv"** from DISTANCE\_21\_PIOTT\bank\hnk folder. Find the file and click on Select Sensor-IO.

<div><figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-272f8f8793342acf1ff4c3aac6b10f982299d2a9%2Fimage%20(191).png?alt=media" alt=""><figcaption></figcaption></figure> <figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-99040b7852a2df697c5706605542d7bdfcf27124%2Fimage%20(192).png?alt=media" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
The file will be loaded and in the Sensors selection of HyperWorks Settings menu.

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

{% step %}
In the HyperWorks settings menu, click on "Load Preferences from HYPERSIM" and press "Apply". Now you can close the HyperWorks menu.

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

{% step %}
On the testview window, right-click on the "POTT\_DISABLED" test in the "project" panel on the left and click Save.

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

{% step %}
In the middle panel, under "View" tab, choose how to process the results. If you press Show under Processing, once you run the test sequence, for each test, ScopeView opens with the specified diagrams (from relay 1 and relay 2) and you have to press OK to move the test to the next one. If you don't choose this option, the test sequence will go through the 10 tests without showing the ScopeView graphs.

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

{% step %}
In the middle panel, under the "Runner" tab, click the purple play button.

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

{% hint style="info" %}
If the test does not run successfully, the window 'Stdout' displays the error message. Debug the model accordingly and re-run the test again to automate the results.
{% endhint %}
{% endstep %}

{% step %}
While the test is running, you can check out Stdout to see the test parameters.

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

{% step %}
If Show is enabled in the View → Processing option, after passing each test, you will see a ScopeView template with two pages. Page 1 shows the results for Relay 1 and Page 2 shows the results for Relay 2.

The graphs that are shown at each page from top to bottom are: Voltage input to the relay, Current input to the relay, and the output Trip signal of the relay.
{% endstep %}

{% step %}
You can press OK to move to the next test.

{% hint style="info" %}
If you don't wish to view any more results, simply disable Show from View → Processing and press OK on the ScopeView template.
{% endhint %}

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

{% step %}
After the tests are done, you can see its notification in stdout.

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

{% step %}
Try and run the two other tests: **POTT\_ON\_RELAY1** and **POTT\_ON\_RELAY1&2** by following the same steps.
{% endstep %}
{% endstepper %}

### Test results export

Test results are saved to **DISTANCE\_21\_POTT.xlsx** in the project folder.

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

The workbook contains:

* General Information: Diagram and model information.
* Input: Parameters for each test such as Fault location and its operating phases.
* Output: Test results for each test. They include the relay clearing and operating times for both relay 1 and relay 2.
* Plot: Operating time plots for both relays.

The picture below shows the **Output** sheet. The results of each test are placed in their respective section: POTT disabled, POTT enabled on one relay, and POTT enabled on both relays.

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

The results can be analyzed, saved, copied, etc.

{% hint style="info" %}
Each time the tests are run, the **results are overwritten with new values and an updated date**.
{% endhint %}


---

# 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/line-distance-protection-with-pott-including-testview-project.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.
