> 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/power-electronics/dc-to-dc-converters/buck-converter/panels-overview.md).

# Panels Overview

## Understand the panels

The **Buck Converter** model file, located in the folder **OP1130 - Power Electronics Courseware,** is **PE\_Buck-version.zip**

When starting the demo, the panel in figure 13 below 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%2FdrbcQaCEw4zkWJ9r7kfJ%2Fimage.png?alt=media&amp;token=3f6812b3-63c8-4175-978e-ffe7d95b104b" alt=""><figcaption><p>Figure 13: Start-Up Panel of Buck Converter Laboratory</p></figcaption></figure>

For operation of the buck converter panel, the student can [**refer to the panel operation of the boost converter**](https://www.opal-rt.com/docs/courseware/electric-courseware/power-electronics/dc-to-dc-converters/boost-converter/panels-overview.md), because the panels of both models are very similar.\
The differences in control parameters, content of scopes, and nameplate ratings for the buck converter are presented in the following tables.

### Control parameters of the buck converter

| Control Parameters           | Default Value | Interval of Variation |
| ---------------------------- | ------------- | --------------------- |
| **DC Source Voltage (V)**    | 100           | \[0; 400]             |
| **Switching Frequency (Hz)** | 1500          | \[1500; 3600]         |
| **Duty Cycle**               | 0.5           | \[0.1; 0.9]           |
| **Inductance (mH)**          | 100           | 50 or 100             |
| **Capacitance (µF)**         | 400           | 400 or 800            |

### Scopes and displayed waveforms

| Scope                      | Content of Scopes & Displayed Waveforms                                |
| -------------------------- | ---------------------------------------------------------------------- |
| **Scope**<sub>**11**</sub> | Load output voltage and switching signal (multiplied by a factor of 5) |
| **Scope**<sub>**21**</sub> | Input current of the DC source and inductor current                    |
| **Scope**<sub>**12**</sub> | Load output current                                                    |
| **Scope**<sub>**22**</sub> | Input power of the DC source and load output power                     |

### Buck converter nameplate ratings

| **Nominal Power**  | 10 kW       |
| ------------------ | ----------- |
| **Input Voltage**  | \[0; 400] V |
| **Output Voltage** | \[0; 360] V |
| **Output Current** | \[0; 28] A  |


---

# 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/power-electronics/dc-to-dc-converters/buck-converter/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.
