> 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/modular-multi-level-converter.md).

# Modular Multi Level Converter

This example shows the operation of a Modular Multi-Level Converter.

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

## Description

This example uses the half-bridge arm blocks to model an MMC consisting of eight power modules. The control system allows you to choose between two types of pulse generators - PWM and Nearest level. You can toggle the switch to see the impact on the output signals of the converter.

The use of MATLAB® functions within PM1 to PM8 subsystems allows coloring the modules in red when they are activated during the simulation. The use of these functions also allows us to slow down Simulink® in order to observe the activation and deactivation of the modules.

Note that only one half-bridge block can be used to model the positive half-arm and/or negative half-arms of the converter.

## Command

Example model name: power\_HalfBridgeMMC

{% code lineNumbers="true" %}

```matlab
open('power_HalfBridgeMMC')
```

{% 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/modular-multi-level-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.
