> 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/smart-power-simulation-software-sps/example-models/power-converters/buck-boost-converter.md).

# Buck Boost Converter

This example shows the operation of buck boost converters using the inverting and non-inverting topologies.

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-2549d9d225edd1ee767798853661d188bce5efe6%2Fbuck_boost_converter_example.png?alt=media" alt=""><figcaption></figcaption></figure>

## Description

The buck boost converter is a DC/DC converter with the output voltage magnitude that is either greater than or less than the input voltage magnitude. It is comparable to a flyback converter where an inductor is used in place of a transformer. The theoretical transfer function of the buck boost converter is:

$$
abs(V\_{out})=D/(1-D) \times V\_{in}
$$

where D is the duty cycle.

The inverting buck-boost topology produces an output voltage that is of the opposite polarity as the input voltage. The output voltage is determined by the duty cycle of the MOSFET transistor.

The non-inverting topology, also named the 4-switch topology, produces an output voltage that is of the same polarity as the input voltage. In the buck mode, the output voltage is determined by the operation of the MOSFET and diode D1. In the boost mode, the output voltage is determined by the operation of the IGBT and diode D2.

## Command

Example model name: power\_BuckBoostConverter

{% code lineNumbers="true" %}

```matlab
open('power_BuckBoostConverter')
```

{% endcode %}


---

# 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/smart-power-simulation-software-sps/example-models/power-converters/buck-boost-converter.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.
