> 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/simplified-wecc-network-with-10-wind-penetration.md).

# Simplified WECC Network with 10% Wind Penetration

## Description

The **Simplified WECC Network with 10% Wind Penetration** 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 **phasor16\_WECC**, then click **Finish**.

This demo shows transient simulation of a simplified and modified version of Western Electricity Coordinating Council (WECC) transmission network \[1] considering 10% of the total generation as wind power. The diagram of the network is shown in the following link which is visualized by GEPHI \[2]. The network includes 301-buses, 40 wind turbine generators, 26 Synchronous machines, 104 constant power loads, 65 fixed shunts and 142 two\_winding transformers.

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

## Requirements

* MATLAB R2019b and later

## Simulation and results

The WT4G1 and WT4E1 are used to model the wind-turbine generators in this demo. All the other GenUnits use the same models for synchronous generator, exciter, power system stabilizer and turbine/governor which are GENROU, EXST1, IEEEST and IEEEG1 respectively.

Wind turbines operate in different controlling modes which are defined by three flags, PFAFLG, VARFLG and PQFLAG. The following table shows configuration of these three flags for all wind turbine generators in the network.

<table><thead><tr><th>Control mode</th><th width="70.39996337890625">VARFLG</th><th width="69.60003662109375">PFAFLG</th><th width="69.20001220703125">PQFLAG</th><th>bus ID</th></tr></thead><tbody><tr><td>Constant reactive power control and active power in priority</td><td>0</td><td>0</td><td>1</td><td>184, 187, 190, 193, 196, 199, 202, 205, 208, 211</td></tr><tr><td>Constant power factor control and active power in priority</td><td>0</td><td>1</td><td>1</td><td>214, 217, 220, 223, 226, 229, 232, 235, 238, 241</td></tr><tr><td>Voltage control and active power in priority</td><td>1</td><td>0</td><td>1</td><td>244, 247, 250, 253, 256, 259, 262, 265, 268, 271</td></tr><tr><td>Voltage control and reactive power in priority</td><td>1</td><td>0</td><td>0</td><td>274, 277, 280, 283, 286, 289, 292, 295, 298, 30</td></tr></tbody></table>

To validate wind turbine models in different controlling modes, the power reference of all WT4E1 components is increased by 10% at t = 5s.

Figure below show simulation results, i.e. terminal voltage deviation from initial value, ETERM, Injected reactive power deviation, QELEC, and power factor deviation, PF, for three wind turbine generators, gen\_208\_1, gen\_235\_1 and gen\_274\_1. Each of these generators work in different control mode. i.e. gen\_208\_1 works in voltage control mode, gen\_235\_1 works in power factor control mode and finally gen\_274\_1 works in reactive power control mode.

As can be seen in Figure (a), while gen\_274\_1 is able to maintain the voltage at its initial value after the transient, the other two wind turbines can not reduce the steady state error to zero. However, gen\_208\_1 is able to control the reactive power, as shown in Figure (b) and gen\_235\_1 is able to control the power factor as shown in Figure (c).

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

The in-port and out-port configurations are given in **phasor16\_WECC.xlsx** file.

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

Moreover the network data as well as dynamic data are given in **phasor16\_WECC.raw** and **phasor16\_WECC.dyr** files respectively.

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

<details>

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

* Vmag: Bus voltage magnitude (p.u.)
* Vang: Bus voltage angle (degrees)
* Wind, ETERM: Terminal voltage magnitude of wind turbine generator (p.u.)
* Wind, PELEC: Active power injection by wind turbine (p.u. on machine base)
* Wind, QELEC: Reactive power injection by wind turbine (p.u. on machine base)
* Wind, WIPCMD: Ip command (p.u. on machine base)
* Wind, WIQCMD: Iq command (p.u. on machine base)
* Slip: Synchronous machine frequency deviation (p.u.)

</details>

<details>

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

* dPref: variation of active power reference power (p.u.)

</details>

## References

\[1] The network data is provided by [CURENT Laboratory](http://curent.utk.edu/) at University of Tennessee at Knoxville

\[2] <https://gephi.org/>


---

# 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/simplified-wecc-network-with-10-wind-penetration.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.
