> 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/hypersim/model-and-simulation/modular-multilevel-converters-mmc.md).

# Modular Multilevel Converters (MMC)

## **Overview** <a href="#overview" id="overview"></a>

The **MMC (Modular Multilevel Converter) product for HYPERSIM** provides a high‑fidelity and scalable modeling environment for the simulation of MMC‑based power electronic systems. It is designed to support advanced studies, control development, and real‑time validation of MMC topologies commonly used in **HVDC, FACTS, and medium‑ to high‑voltage applications**.

The product enables accurate representation of converter dynamics across multiple levels of detail, from offline studies to real‑time and hardware‑in‑the‑loop (HIL) validation. Its modular architecture allows users to adapt the models to different converter configurations while maintaining a strong balance between numerical accuracy and real‑time performance.

## **Features** <a href="#features" id="features"></a>

* Execution flexibility:
  * Offline simulation
  * Real‑time execution on CPU
  * Real‑time execution on FPGA
* Real Time simulation of hundreds of sub‑modules per valve, with **time steps below one microsecond.**
* Adaptability to various MMC topologies and configurations (monopole, bipolar, multi-terminal HVDC, STATCOM, matrix converter) enabling rapid customization for specific applications.
* Multiple model types to match the required level of detail and development stage:
  * Offline detailed models
  * Average models
  * Switched‑function models
  * Models interconnected with real external controllers
* Real‑time interconnection with external control hardware, using:
  * High speed optical interconnection (5 Gbps using Aurora)
  * Gigabit Ethernet communication protocols
* Detailed sub‑module‑level modeling, including:
  * Individual sub‑module electrical behavior
  * Parameter mismatch between sub‑modules
  * Switch failure modeling (open‑circuit and short‑circuit)
* Integrated low‑level control functions, including:
  * Multiple capacitor voltage balancing strategies
  * Modulation algorithms
  * Protection mechanisms for sub‑module over‑voltage and under‑voltage conditions
* Advanced debugging and analysis tools, such as:
  * Sub‑module (SM) status monitoring
  * Forcing valve currents
  * Fixing capacitor voltages to predefined values independently of valve current

## **Typical Use Cases** <a href="#typical-use-cases" id="typical-use-cases"></a>

The MMC product for HYPERSIM is well suited for a wide range of applications, including:

* **HVDC and FACTS system studies**, with detailed analysis of converter dynamics and interactions with AC and DC networks
* **STATCOM Applications**
* **Control algorithm development and validation**, from early offline design to real‑time implementation
* **Hardware‑in‑the‑loop (HIL) testing**, enabling direct testing of real control hardware under realistic operating conditions
* **Fault and robustness analysis**, including sub‑module failures, parameter dispersions, and protection behavior

## **Licensing and detailed technical documentation** <a href="#licensing-and-detailed-technical-documentation" id="licensing-and-detailed-technical-documentation"></a>

For access to the Hypersim MMC product, licensing information, or extended technical documentation, users are invited to contact **their** [**OPAL‑RT** **representative**](https://www.opal-rt.com/find-local-contact/) for assistance tailored to their application needs.


---

# 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/hypersim/model-and-simulation/modular-multilevel-converters-mmc.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.
