> 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-8500-node-test-system.md).

# Modified IEEE 8500 Node Test System

## Description

The **Modified IEEE 8500 Node Test 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 **phasor25\_IEEC8500**, then click **Finish**.

This demo simulates a simple scenario on a modified IEEE 8500 node test feeder distribution system. The following modification are made to the original IEEE 8500 node test feeder provided in \[1]. The network data are given in .dss file inside OpenDSS\_IEEE8500\_modified directory.

1. All split-phase transformers are replaced by three 2-winding transformers with phase-shift and no load loss parameter values are set to zero.
2. All loads are converted to constant impedance type.
3. All switches in the original system are closed as default.
4. All voltage regulators on transformer and capacitor banks are disabled in OpenDSS model.

For this demo, a switch replacement scenario is considered, where an existing switch is replaced by a new switch. The switch SW1 used for the demonstration connects a considerably large feeder area, highlighted in the Figure 1, to the main feeder.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8ab14c43f828798fc24b5a95e1277a3855e550a0%2FIEEE8500_mod.png?alt=media" alt=""><figcaption><p>Figure 1. - Modified IEEE 8500 node test system with higher feeder line used in this demo.</p></figcaption></figure>

The in-port and out-port configurations are given in **phasor25\_IEEE8500.xlsx** file.

{% file src="/files/2DxIrcgO6Eqo3TQ5FZAh" %}

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

<details>

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

* Vmag: Voltage magnitude of selected buses around the SW1 (V)
* Imag: Current magnitude of selected lines around the SW1 (A)
* P\_from: Active Power of selected lines around the SW1 (kW)
* Q\_from: Reactive Power of selected lines around the SW1 (kVAr)

</details>

<details>

<summary>Incoming pin (control command)</summary>

* Switch SW1 status: To open the SW1
* Switch SW2 status: To close SW2

</details>

## Requirements

* MATLAB R2019b and later

## Simulation and results

In this model, the '**Initialization method**' for power-flow calculation is set to Smart Start. The simulation will begin from steady state and two disturbances occur in the system as described below:

* At t = 2s: Open Switch SW1.
* At t = 3s: Close Switch SW2.

The power-flow result comparison between OpenDSS and ePHASORSIM, mainly voltage magnitude and angles at each node, is shown in the figure below. The maximum voltage magnitude and angle error observed are below 0.30 % and 0.30 degree, respectively.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-fad2ba138e9beda4a39bff6f85e4d8ef9d404888%2FPowerflowComparison.png?alt=media" alt=""><figcaption><p>Figure 2. - ePHASORSIM vs OpenDSS Power-flow comparison of all node voltage and angle.</p></figcaption></figure>

The power-flow results comparison at some of the nodes are also shown in the table below. The corresponding OpenDSS script can be found in \[2] for further comparison purposes.

**Power-flow comparison of selected buses.**

<table data-search="false"><thead><tr><th>Result Type</th><th>OpenDSS Power-flow</th><th>ePHASORSIM Power-flow</th><th>Absolute difference Magnitude (%)</th><th>Absolute difference Angle (deg)</th></tr></thead><tbody><tr><td>V_sx3216358a_a (V)</td><td>101.6/-41.5</td><td>101.6/-41.6</td><td>0.00</td><td>0.10</td></tr><tr><td>V_sx3216358a_b (V)</td><td>101.6/-41.5</td><td>101.6/-41.6</td><td>0.00</td><td>0.10</td></tr><tr><td>V_sx3142049c_a (V)</td><td>115.3/81.9</td><td>115.3/81.7</td><td>0.00</td><td>0.20</td></tr><tr><td>V_sx3142049c_b (V)</td><td>115.3/81.9</td><td>115.3/81.7</td><td>0.00</td><td>0.20</td></tr><tr><td>V_x2802481a_a (V)</td><td>112.3/-37.8</td><td>112.3/-37.9</td><td>0.00</td><td>0.10</td></tr><tr><td>V_x2802481a_b (V)</td><td>112.3/-37.8</td><td>112.3/-37.9</td><td>0.00</td><td>0.10</td></tr><tr><td>V_l3047289_a (V)</td><td>6847.3/-36.7</td><td>6843.9/-36.8</td><td>0.05</td><td>0.10</td></tr><tr><td>V_l3047289_b (V)</td><td>6773.1/-156.6</td><td>6764.0/-156.7</td><td>0.13</td><td>0.10</td></tr><tr><td>V_l3047289_c (V)</td><td>6873.6/82.3</td><td>6869.8/82.2</td><td>0.06</td><td>0.10</td></tr><tr><td>V_sx3029510b_a (V)</td><td>103.4/-162.9</td><td>103.3/-163.0</td><td>0.10</td><td>0.10</td></tr><tr><td>V_sx3029510b_b (V)</td><td>103.4/-162.9</td><td>103.3/-163.0</td><td>0.10</td><td>0.10</td></tr><tr><td>V_sx3216988b_a (V)</td><td>112.5/-158</td><td>112.5/-158.1</td><td>0.00</td><td>0.10</td></tr><tr><td>V_sx3216988b_b (V)</td><td>112.5/-158</td><td>112.5/-158.1</td><td>0.00</td><td>0.10</td></tr><tr><td>V_sx2763153a_a (V)</td><td>106.9/-37</td><td>106.9/-37.1</td><td>0.00</td><td>0.10</td></tr><tr><td>V_sx2763153a_b (V)</td><td>106.9/-37</td><td>106.9/-37.1</td><td>0.00</td><td>0.10</td></tr><tr><td>V_x2822863c_a (V)</td><td>113.6/82</td><td>113.7/81.8</td><td>0.10</td><td>0.20</td></tr><tr><td>V_x2822863c_b (V)</td><td>113.6/82</td><td>113.7/81.8</td><td>0.10</td><td>0.20</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/example-models/ephasorsim-example-models/modified-ieee-8500-node-test-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.
