> 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/european-low-voltage-distribution-test-feeder.md).

# European Low Voltage Distribution Test Feeder

## Description

The **European Low Voltage Distribution Test Feeder** 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 **phasor15\_IEEE\_EURO\_LV**, then click **Finish**.

The **European Low Voltage system** is used to show how to run a distribution system simulation with the ePHASORSIM API and CYME (CYMDIST sub-module) network data files. In this network, there are 907 three phase nodes, 905 branches, 1 three phase transformer and 55 spot loads. Operations of the network will be implemented by the ePHASORSIM API routines in this demo. test\_sequence.py is the file that contains the ePHASORSIM API routines to define the scenarios and operations for this demo.

Outgoing pins are configured in **phasor15\_IEEE\_EURO\_LV.xlsx** file, and the network data is imported from the **phasor15\_IEEE\_EURO\_LV.sxst** file.

Figure below shows the single-line-diagram of this network.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-531ad7cbe7185c4fdc3cdc15292669880aa8735a%2FIEEE_EURO_LV.png?alt=media" alt=""><figcaption><p>European Low Voltage Distribution Test Feeder Diagram.</p></figcaption></figure>

## Requirements

* MATLAB R2019b and later

## Simulation and results

In "Pins" page of phasor15\_IEEE\_EURO\_LV.xlsx file the following outgoing pins are assigned:

<details>

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

* Current measurement for phases A, B, and C on lines 296, 110, 112 and 1.
* Voltage measurement for phases A, B, and C at nodes 899, 639, 248, 169 and 881.

</details>

This demo shows that how the consecutive load increase in the distribution grid will affect the system performance, such as voltage dropping and current rising. The simulation begins from steady state. Then starting from t=2 seconds all the loads in the system are increased by 10% every 2 seconds. Such a gradual increase continues till t=10 seconds when the loading of the system is increased by 40%. The magnitude and angle of voltage and current are displayed in the "signal centre" subsystem in the demo.

{% hint style="info" %}
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.
{% endhint %}

## References

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


---

# 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/european-low-voltage-distribution-test-feeder.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.
