> 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/courseware/electric-courseware/renewable-energy/wind-turbine-generation-system-wtgs/panels-overview.md).

# Panels Overview

## Main interface

The **WTGS** model file, located in the folder **OP1142 - Renewable Energy,** is **RE\_WTGS-version.zip**

When starting the demo and letting the simulation stabilize, the panel in Figure 9 appears first with the default settings.

<figure><img src="https://4054096626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYbyVjpgEQX9nfCkpYoFP%2Fuploads%2FOoU3ao84XEY7BuR0CFbM%2Fa208d37a-d5a3-4887-be02-0896f4cff9a2.png?alt=media&amp;token=d45ee34a-949c-444b-9622-8684f35292c5" alt=""><figcaption><p><strong>Figure 9</strong>: Start-Up Panel of the Wind Turbine Generation System Laboratory</p></figcaption></figure>

### Control parameters of the WTGS

The panel is to be operated as follows:

* In the top left corner, under **Setpoint**, the student can change the control parameters, which are summarized in Table 2.

| Control Parameters                   | Default Value | Interval of Variation |
| ------------------------------------ | ------------- | --------------------- |
| **Wind Speed (m/s)**                 | 8             | \[7; 12]              |
| **Reactive Power Reference (VAR)**   | 400000        | \[-400000; 400000]    |
| **Reference Speed from User rad/s)** | 140           | \[0; 240]             |

* The switch “User/Predefined” allows students to impose their own reference speed when the option “User” is selected.\
  In this scenario, the optimal rotational speed obtained via MPPT from the wind speed is replaced by the reference speed.

### Scopes and displayed waveforms on main interface tab.

* After setting the control parameters, the students can observe the waveforms displayed in six scopes.\
  More details about the displayed waveforms are given in Table 3.

On scope localization, the indices used will be like those of matrix elements.\
Hence, the first scope on **Main Interface** tab, located in the upper left corner (first row, first column) is denoted Scope<sub>11</sub>, while the second scope in the upper right corner (first row, second column) is Scope<sub>12</sub>.\
By the same token, the other four scopes are denoted Scope<sub>21</sub>, Scope<sub>22</sub>, Scope<sub>31</sub>, and Scope<sub>32</sub>.

| Scope                      | Content of Scopes & Displayed Waveforms |
| -------------------------- | --------------------------------------- |
| **Scope**<sub>**11**</sub> | Stator voltages at phases A, B, and C.  |
| **Scope**<sub>**12**</sub> | Stator currents at phases A, B, and C.  |
| **Scope**<sub>**21**</sub> | Rotor currents at phases A, B, and C.   |
| **Scope**<sub>**22**</sub> | Reference and measured torques.         |
| **Scope**<sub>**31**</sub> | Reference and measured DC voltages.     |
| **Scope**<sub>**32**</sub> | Reference and measured reactive powers. |

## Secondary interface <a href="#secondary-interface" id="secondary-interface"></a>

When clicking on the “Secondary Interface” tab and changing the wind speed to 11 m/s, the panel in Figure 10 is displayed.\
The content of scopes and displayed waveforms of the “Secondary Interface” are summarized in Table 4.

<figure><img src="https://4054096626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYbyVjpgEQX9nfCkpYoFP%2Fuploads%2FNIKvJlUUjAcujuHZVv9P%2F88bd38a3-ce80-46ce-b3ad-4a8f34d17340.png?alt=media&amp;token=4ec7a0e8-896f-434a-adac-c78527d0f659" alt=""><figcaption><p><strong>Figure 10</strong>: Secondary Interface Panel of the Wind Turbine Generation System Laboratory</p></figcaption></figure>

### Scopes and displayed waveforms on secondary interface tab

| Scope                      | Content of Scopes & Displayed Waveforms                                  |
| -------------------------- | ------------------------------------------------------------------------ |
| **Scope**<sub>**11**</sub> | Reference and measured speeds.                                           |
| **Scope**<sub>**12**</sub> | Reference and measured torques.                                          |
| **Scope**<sub>**21**</sub> | Reference and measured *I*<sub>*d*</sub> currents at rotor-side control. |
| **Scope**<sub>**22**</sub> | Reference and measured *I*<sub>*q*</sub> currents at rotor-side control. |
| **Scope**<sub>**31**</sub> | Reference and measured *I*<sub>*d*</sub> currents at grid-side control.  |
| **Scope**<sub>**32**</sub> | Reference and measured *I*<sub>*q*</sub> currents at grid-side control.  |

## Help tab <a href="#help-tab" id="help-tab"></a>

When clicking on the “Help Contents” tab, the panel in Figure 11 is displayed.\
In this panel, the student can see live displays of power flow at different parts of the WTGS.\
The student can validate the simulation results by checking that the power flow is balanced.

<figure><img src="https://4054096626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYbyVjpgEQX9nfCkpYoFP%2Fuploads%2FnoRAWyiPqkCYTNHVUesv%2F4106ac38-e132-4432-9943-c3d80a87e4ce.png?alt=media&amp;token=c8069e90-aa18-40ee-86fa-af0999c87736" alt=""><figcaption><p><strong>Figure 11</strong>: Help Contents Panel of the Wind Turbine Generation System Laboratory</p></figcaption></figure>


---

# 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/courseware/electric-courseware/renewable-energy/wind-turbine-generation-system-wtgs/panels-overview.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.
