> 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/example-models/ephasorsim-example-models/modified-ieee-13-nodes-system.md).

# Modified IEEE 13 Nodes System

## Description

The **Modified IEEE 13 Nodes System** example can be created by starting a new RT‑LAB project. From the menu bar, select **File > New > RT‑LAB Project**. Enter a name and location for your project, then click **Next**. From the available templates list, navigate to **ePHASORsim** and select **phasor08\_IEEE13**, then click **Finish**.

The **modified IEEE 13-node Test Feeder distribution system** \[1] is used to show the basic features of ePHASORSIM for simulation of distribution systems. This model is modified from the standard IEEE 13 nodes system. A copy of standard IEEE 13 node system report exists in the demo folder.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-89f1ed549220731173648287887df9263336f848%2Fphasor08_IEEE13.jpg?alt=media" alt=""><figcaption></figcaption></figure>

This network is one feeder with 13 nodes that includes 3-phase voltage source, multiphase loads, multiphase shunts, transformers, and lines. Following modifications are made:

* The distributed load along the line 632 to 671 is replaced by a spot load located at bus 632.
* The voltage regulator between nodes 632 and 650 is substituted by a transformer (Yg-Yg), and a new node 651 is inserted.
* All loads have Yg concoction.

Comparison of OpenDSS Load Flow results and ePHASORSIM power flow results are presented.

## Requirements

* MATLAB R2019b and later

## Simulation and results

The network data as well as in-port and out-port configurations are given in **phasor08\_IEEE13.xlsx** file.

{% file src="/files/xoJy4D7FyxqVk2IMjvmZ" %}

In the "Pins" page of the Excel file the following outgoing and incoming pins are assigned:

<details>

<summary>Outgoing pins (measurements)</summary>

* Voltage measurement for desired phases at buses 611, 632, 633, 634, 675
* Current measurement for phases A, B, and C for lines 651-632 and 632-633

</details>

<details>

<summary>Incoming pins (control commands)</summary>

* Change three-phase tap position for transformer between node 633 and 634.
* Adjust P and Q load on phase B at bus 645.

</details>

In this model, the execution mode is set to 'Power flow and dynamic simulation', which will first run the power flow for the model and then run the dynamic simulation. Thus, the simulation will begin from steady state and two disturbances happen in the system as described below:

* At t = 1s: Taps of transformer are changed from 0 to 8 on three phases.
* At t = 5s: Active and reactive power of load 645 are doubled.

There are three types of load in the system: constant power, constant impedance, and constant current loads. The bandwidth of these loads are set to 0.2, which means if the voltage is over 1.2 p.u. or under 0.8 p.u., then the load will change to a constant impedance type.

The power flow results from ePHASORsim are compared with power flow results of OpenDSS, as it is shown in table below. The magnitude and angle differences for the corresponding signals defined in column 1 are in column 4 and column 5 respectively.

The corresponding OpenDSS script is given for further comparison purposes.

{% file src="/files/TM9Edx7yNKdsFw2zQ8JN" %}

<table data-search="false"><thead><tr><th>Result Type</th><th>OpenDSS Power Flow</th><th>ePHASORSIM Dynamic</th><th>Magnitude (%)</th><th>Angle (deg)</th></tr></thead><tbody><tr><td>V_611_c (V)</td><td>2121.9/115</td><td>2121.91/114.99</td><td>0.00</td><td>0.01</td></tr><tr><td>V_632_a (V)</td><td>2320/-2.6</td><td>2320.11/-2.56</td><td>0.00</td><td>0.04</td></tr><tr><td>V_632_b (V)</td><td>2355.1/-121.7</td><td>2355.14/-121.74</td><td>0.00</td><td>0.04</td></tr><tr><td>V_632_c (V)</td><td>2264.4/117.3</td><td>2264.41/117.32</td><td>0.00</td><td>0.02</td></tr><tr><td>V_633_a (V)</td><td>2312.4/-2.6</td><td>2312.44/-2.64</td><td>0.00</td><td>0.04</td></tr><tr><td>V_633_b (V)</td><td>2350.2/-121.8</td><td>2350.29/-121.79</td><td>0.00</td><td>0.01</td></tr><tr><td>V_633_c (V)</td><td>2257.5/117.3</td><td>2257.57/117.31</td><td>0.00</td><td>0.01</td></tr><tr><td>V_634_a (V)</td><td>259.76/-3.4</td><td>259.77/-3.39</td><td>0.00</td><td>0.01</td></tr><tr><td>V_634_b (V)</td><td>265.76/-122.3</td><td>265.767/-122.31</td><td>0.00</td><td>0.01</td></tr><tr><td>V_634_c (V)</td><td>254.83/116.8</td><td>254.834/116.75</td><td>0.00</td><td>0.05</td></tr><tr><td>V_675_a (V)</td><td>2249.2/-6.2</td><td>2249.30/-6.20</td><td>0.00</td><td>0.00</td></tr><tr><td>V_675_b (V)</td><td>2395.4/-122.1</td><td>2395.46/-122.15</td><td>0.00</td><td>0.05</td></tr><tr><td>V_675_c (V)</td><td>2126/115.3</td><td>2126.06/115.29</td><td>0.00</td><td>0.01</td></tr><tr><td>I_651_632_a (A)</td><td>549.3/-25.9</td><td>549.19/-25.90</td><td>0.02</td><td>0.01</td></tr><tr><td>I_651_632_b (A)</td><td>477.36/-146.3</td><td>477.24/-146.25</td><td>0.02</td><td>0.05</td></tr><tr><td>I_651_632_c (A)</td><td>621.99/90.9</td><td>621.935/90.92</td><td>0.01</td><td>0.02</td></tr><tr><td>I_632_633_a (A)</td><td>86.249/-37.9</td><td>86.2424/-37.90</td><td>0.01</td><td>0.00</td></tr><tr><td>I_632_633_b (A)</td><td>65.124/-159.2</td><td>65.123/-159.177</td><td>0.00</td><td>0.02</td></tr><tr><td>I_632_633_c (A)</td><td>67.915/79.9</td><td>67.9164/79.88</td><td>0.00</td><td>0.02</td></tr></tbody></table>

## References

\[1] [IEEE Distribution Test Feeders](http://ewh.ieee.org/soc/pes/dsacom/testfeeders/index.html).

{% file src="/files/B3SAU8WywLGJ31gb3k78" %}


---

# 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/example-models/ephasorsim-example-models/modified-ieee-13-nodes-system.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.
