> 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/two-and-three-level-voltage-source-controllers.md).

# Two and Three Level Voltage Source Controllers

This example shows the operation of two-level and three-level voltage source controllers.

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

## Description

The upper circuit represents a two-level voltage source converter represented by a six pulse IGBT bridge with inverse-parallel diodes. The voltage at the AC terminals of each phase is switched between the positive and negative potential values of the DC terminals.

The lower circuit represents a three-level voltage source converter with neutral-point clamp. This topology can synthesize three voltage levels from positive DC value, zero (neutral), and negative DC value at the AC terminal of each phase. In this neutral-point clamped configuration, the clamping diode valves are replaced by IGBT valves, to allow more control on the generated AC waveforms.

## Command

Example model name: power\_2and3LevelVSC

{% code lineNumbers="true" %}

```matlab
open('power_2and3LevelVSC')
```

{% 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/two-and-three-level-voltage-source-controllers.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.
