> 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/microgrid-system/virtual-test-bench.md).

# Virtual Test Bench

## Microgrid and controller diagramm

The simulated microgrid and its controller are shown in figures 1 and 2, respectively.

<figure><img src="https://4054096626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYbyVjpgEQX9nfCkpYoFP%2Fuploads%2FMY5afZZmD1eYenoOkoMN%2F144364ff-9d2a-4a7e-ac96-16b358cf2152.png?alt=media&amp;token=a641fb8a-219f-4db3-b626-84b64a7aeaa1" alt=""><figcaption><p><strong>Figure 1</strong>: Schematic Representation of the Microgrid</p></figcaption></figure>

<figure><img src="https://4054096626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYbyVjpgEQX9nfCkpYoFP%2Fuploads%2FdccuTMNuhWgi82CNYQB4%2F5aaf5567-0671-4520-b987-44cfd8c95e63.png?alt=media&amp;token=ca8f2de0-f8d5-464d-a6db-47c45cd53d13" alt=""><figcaption><p><strong>Figure 2</strong>: Schematic Representation of the Microgrid Controller</p></figcaption></figure>

## Virtual test bench components

* The main components of the studied microgrid are as follows:
* A **wind turbine generation system (WTGS)** that delivers at any time instant *t* an output power *P*<sub>*Wt*</sub> related to wind speed *v*<sub>*t*</sub> [**\[2\]**](https://www.opal-rt.com/docs/courseware/electric-courseware/renewable-energy/microgrid-system/references.md):
* $$P\_{wt} = \left{ \begin{matrix} 0 \quad v\_t < v\_{CI} ;\text{or}; v\_t \ge v\_{CO} \ P\_W^{\max},\dfrac{v\_t - v\_{CI}}{v\_R - v\_{CI}} \quad v\_{CI} \le v\_t < v\_R \ P\_W^{\max} \quad v\_R \le v\_t < v\_{CO} \end{matrix} \right. \\\[8pt]$$

where *P*<sub>*W*</sub><sup>*max*</sup> is the rated power, *v*<sub>*t*</sub> is the wind speed at instant *t*, *v*<sub>*CI*</sub> is the cut-in wind speed, *v*<sub>*CO*</sub> is the cut-out wind speed and *v*<sub>*R*</sub> is the rated wind speed.\
The values used as part of the simulation for these parameters are presented in table 1.

The WTGS is connected to the microgrid via a 50 kVA transformer, with primary and secondary voltages of 6.6 kV and 548 V, respectively.

<figure><img src="https://4054096626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYbyVjpgEQX9nfCkpYoFP%2Fuploads%2FwhCnYUlJ59rhYUprLakJ%2Fimage.png?alt=media&amp;token=ad5f10cf-4dda-434d-b49c-a374a85d701f" alt="" width="320"><figcaption><p>Table 1: Wind Turbine Power Curve Parameters</p></figcaption></figure>

* A **photovoltaic generation system (PVGS)** delivering a maximum power of 12 kW at an irradiance E = 1000 W/m2 and a temperature T = 25 °*C*.\
  The PVGS is connected to the microgrid through a 3-phase inverter and a 14.4 kVA transformer.\
  The primary and secondary voltages of this transformer are respectively 6.6 kV and 208 V.
* A 60 kW lithium-ion **battery energy storage system (BESS)**, connected to the microgrid through a 3-phase inverter and a 72 kVA transformer with primary and secondary voltages of 6.6 kV and 480 V respectively.\
  The role of the BESS is to deliver or to absorb the difference between the load demand and the total power generated by the microgrid [**\[3\]**](https://www.opal-rt.com/docs/courseware/electric-courseware/renewable-energy/microgrid-system/references.md).
* The microgrid **load demand** is represented by three loads with different characteristics in terms of importance.\
  The first load is a hospital, representing a critical load with a peak demand of 27 kW.
* The second one is a combination of a critical load demand of 25 kW and a demand response participation up to 9 kW.\
  And finally, the last one is a fully sheddable residential load of 18 kW.\
  It should be noted that a critical load refers to a load demand that needs to be met at all times, while part of a sheddable load demand can be disregarded when there is not enough power generation to serve the total load demand.
* The **microgrid controller** ensures the balance between load demand and power generation in the system.\
  As shown in figure 2 above, the controller gathers all the information coming from the loads, the PV and wind generation systems, the BESS, and the main grid.\
  A one-way communication can be seen between the critical load and the controller because the only action is to meet this demand once the command arrives.\
  As for the other two loads, a two-way communication is seen, meaning that the controller can take actions to partially meet their energy demand if there is no sufficient power generation.

From the generation side, maximum power point tracking is implemented at both the PV solar array and the wind turbine, which enables an increase in the power delivered but also enhances the lifetime of the renewable generation system [**\[4,5\]**.](https://www.opal-rt.com/docs/courseware/electric-courseware/renewable-energy/microgrid-system/references.md)\
The controller manages when the BESS needs to be charged or to provide power based on two criteria: the state of charge (SoC) of the battery bank and the difference between load demand and renewable power generation.\
Finally, the controller also enables when to connect or disconnect and when to buy or sell energy to the main grid utility.\
An islanding breaker enables the connection/disconnection to the main grid.


---

# 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/microgrid-system/virtual-test-bench.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.
