> 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/blocks-functions-tools/power-converters/converters/full-bridge-mmc-external-dc-links.md).

# Full-Bridge MMC (External DC Links)

## Description

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

The **Full Bridge MMC (External DC Links)** bloc&#x6B;**,** located in the **OPAL-RT SPS Software/Power Electronics** library, implements a full-bridge modular multilevel converter with external DC links.

The converter consists of multiple series-connected power modules. Each power module consists of one H-Bridge with external DC outputs.

You can choose from three model types:

* **Power Electronics** — The converter uses IGBT/diode pairs.
* **Switching function** — The converter is based on a switching-function model.
* **Average model (Uref-controlled)** — The converter is modeled using a switching-function model directly controlled by the reference voltage signals.

## Ports

### Input

<table data-header-hidden><thead><tr><th width="189.20001220703125"></th><th></th></tr></thead><tbody><tr><td><strong>g</strong> — Firing pulse gate<br>Vector</td><td><p>Gate signal that controls the converter. The gate signal contains the firing pulses to control four switches at each power module in the converter (four times the <strong>Number of power modules</strong> pulses).<strong>Dependencies</strong> This port is visible only when you set the <strong>Model type</strong> parameter to Switching devices or Switching function.</p><p><strong>Data Types:</strong> single | double | Boolean</p></td></tr><tr><td><strong>Uref</strong> — Reference<br>Vector</td><td><p>Reference voltage signal that controls the converter. The vectorized signal contains one reference voltage for each power module in the converter.</p><p><strong>Dependencies</strong> This port is visible only when you set the <strong>Model type</strong> parameter to Average model (Uref-controlled).<strong>Data Types:</strong>single | double</p></td></tr><tr><td><strong>BL</strong> — Firing pulse block<br>Scalar</td><td>Input used to block all firing pulses when the signal is 1. To block all firing pulses to the converter, input a value of 1.<strong>Data Types:</strong> single | double | Boolean</td></tr></tbody></table>

### Output

<table data-header-hidden><thead><tr><th width="207.39996337890625"></th><th></th></tr></thead><tbody><tr><td><strong>c1+</strong> — Positive DC terminal<br>Scalar</td><td>Positive DC terminal of the first power module. Additional positive DC terminals, labeled <strong>c2+</strong>, <strong>c3+</strong>, <strong>c4+</strong>, and so on, are added to the block for the corresponding number of power modules defined by the <strong>Number of power modules</strong> parameter.</td></tr><tr><td><strong>c1-</strong> — Negative DC terminal<br>Scalar</td><td>Negative DC terminal of the first power module. Additional negative DC terminals, labeled <strong>c2-</strong>, <strong>c3-</strong>, <strong>c4-</strong>, and so on, are added to the block for the corresponding number of power modules defined by the <strong>Number of power modules</strong> parameter.</td></tr><tr><td><strong>1</strong> — Output terminal<br>Vector</td><td>Output terminal 1 of the converter.</td></tr><tr><td><strong>2</strong> — Output terminal<br>Vector</td><td>Output terminal 2 of the converter.</td></tr></tbody></table>

## Parameters

<table data-header-hidden><thead><tr><th width="217.20001220703125"></th><th></th></tr></thead><tbody><tr><td><strong>Model type</strong> — Converter model<br>Switching devices | Switching function | Average model (Uref-controlled)</td><td><p>Specify the model type to use for the switching devices. You can choose from three model types:</p><ul><li>Switching devices — The converter uses IGBT/diode pairs. A multilevel PWM generator produces firing pulses (0/1 signals), which trigger switching in the converter.</li><li>Switching function — The converter is based on a switching-function model. The model uses two voltage sources and two diodes on the AC side, and two current sources on the DC side. The converter is controlled by firing pulses produced by a PWM generator (0/1 signals) or by firing pulses averaged over a specified period (PWM averaging: signals from 0 through 1). Both modes of operation produce harmonics normally generated by a PWM-controlled converter, and also correctly simulate the rectifying operation and blanking time. This model type is suitable for real-time simulation</li><li>Average model (Uref-controlled) — The converter is modeled using a switching-function model directly controlled by the reference voltage signals. A PWM generator is not required. This model provides the fastest simulations.</li></ul><p><strong>Dependencies</strong> Each <strong>Model type</strong> option enables a particular set of parameters.</p></td></tr><tr><td><strong>Number of power modules</strong> — Number of modules<br>1 (default)</td><td>Number of series-connected power modules that are in the converter.</td></tr><tr><td><strong>Device on-state resistance (Ohms)</strong> — Resistance<br>1e-3 (default)</td><td><p>Internal resistance of the switching devices.</p><p><strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching devices.</p></td></tr><tr><td><strong>Snubber resistance (Ohms)</strong> — Resistance<br>1e6 (default) | inf</td><td><p>To eliminate the snubbers, set the snubber resistance to inf.</p><p><strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching devices.</p></td></tr><tr><td><strong>Snubber capacitance (F)</strong> — Capacitance<br>inf (default)</td><td>Snubber resistance of the switching device. To eliminate the snubbers, set the snubber capacitance to 0.<strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching devices.</td></tr><tr><td><strong>Diode on-state resistance (Ohms)</strong> — Resistance<br>1e-3 (default)</td><td>Internal resistance of the diodes, <strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching function or Average model (Uref-controlled).</td></tr><tr><td><strong>Diode snubber resistance (Ohms)</strong> — Resistance<br>1e6 (default) | inf</td><td><p>Snubber resistance of the diode device. To eliminate the snubbers, set the snubber resistance to inf.</p><p><strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching function or Average model (Uref-controlled).</p></td></tr><tr><td><strong><code>Diode snubber capacitance (F)</code></strong><code> — Capacitance</code><br><code>inf (default) | 0</code></td><td>Snubber capacitance of the diode. To eliminate the snubbers, set the snubber capacitance to 0.<strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching function or Average model (Uref-controlled).</td></tr><tr><td><strong>Diode forward voltage (V)</strong> — Voltage<br>1e-3 (default)</td><td><p>Forward voltage across the diode when it is conducting.</p><p><strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching function or Average model (Uref-controlled).</p></td></tr><tr><td><strong>Current source snubber resistance (Ohms)</strong> — Resistance<br>inf (default)</td><td><p>The snubber resistance across the two current sources. To eliminate the snubbers, set the snubber resistance to inf.</p><p><strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching function or Average model (Uref-controlled).</p></td></tr><tr><td><strong>Sample time (s)</strong> — Computation rate<br>10e-6 (default)</td><td><p>Sample time of the block. To implement a continuous block, set to 0.</p><p><strong>Dependencies</strong> This parameter is enabled when the <strong>Model type</strong> parameter is set to Switching function or Average model (Uref-controlled).</p></td></tr></tbody></table>

### Model Examples

* [Switching Function Converter Controlled by Averaged Firing Pulses](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/example-models/power-converters/switching-function-converter-controlled-by-averaged-firing-pulses.md) The advantages of power electronics converters that can be simulated using one of four selectable modeling techniques.
* [MMC-STATCOM with 22 Power Modules per Phase](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/example-models/power-transmission-and-distribution/mmc-statcom-with-22-power-modules-per-phase.md) A 12 MVA, 34.5 kV Static Synchronous Compensator using 22 power modules per phase.
* [1.5-MVA Multicell Motor Drive](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/example-models/motor-drives/1.5-mva-multicell-motor-drive.md) The operation of a 1.5-MVA motor drive using a multicell power converter.


---

# 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/blocks-functions-tools/power-converters/converters/full-bridge-mmc-external-dc-links.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.
