> 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/loss-calculation-in-a-three-phase-3-level-inverter.md).

# Loss Calculation in a Three Phase 3 Level Inverter

## Loss Calculation in a Three-Phase 3-Level Inverter

This example shows how to compute switching losses in a three-phase 3-level inverter, combining SPS and Simscape™ blocks.

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

## Description

From a +/- 1800 volts DC source, a 400-kW, three-phase 3-level inverter delivers variable power to a distribution power system. The inverter output is connected to the 25-kV, 40 MVA, 50-Hz system through a 2200 V / 25 kV transformer. The inverter topology is based on the model described in \[1]. Each 3-level leg of the inverter comprises three commercial half-bridge IGBT modules. The IGBT pulsing of module 3 is not required since only the anti-parallel diodes are operating as neutral clamping diodes. The control system contains two PI controllers (one PQ regulator and one current regulator) to generate the required inverter pulses to achieve the reference output power.

The Phase-A leg is implemented using three Half-bridge IGBT with Loss Calculation blocks. Both switching and conduction losses are calculated and injected into a thermal network. The simulation illustrates the achievable output power versus switching frequency for the three-phase, 3-level inverter.

### The Half-bridge IGBT with Loss Calculation Block

The half-bridge is modeled by two IGBT/Diode blocks. The upper and lower IGBT/Diode blocks are pulsed from an external pulse generator. The loss calculations are based on the specifications found on the manufacturer's data sheets.

The IGBTs losses are computed as follows:

* Turn-on loss: Pre-switching value of the voltage across the device, post-switching value of the current flowing into the device, and the junction temperature are used to determine the energy losses with the help of a 3-D lookup table. This energy is converted into a power pulse which is injected into the thermal network.
* Turn-off loss: Pre-switching value of the current flowing into the device, post-switching value of the voltage across the device, and the junction temperature are used to determine the energy losses with the help of a 3-D lookup table. This energy is converted into a power pulse which is injected into the thermal network.
* Conduction loss: Value of the current (Ic) flowing in the device and its junction temperature determine what would be the saturation voltage (Vce) across the IGBT using a 2-D look-up table. This Vce is then multiplied by Ic to obtain the losses which are injected into the thermal network.

The diode's losses are computed as follows:

* Reverse recovery loss: Pre-switching value of the current flowing into the device, post switching value of the voltage across the device, and the junction temperature are used to determine the energy losses with the help of a 3-D lookup table. This energy is converted into a power pulse which is injected into the thermal network.
* Conduction loss: Value of the current (If) flowing in the device and its junction temperature determine what would be the on-state voltage (Vf) across the diode using a 2-D look-up table. This Vf is then multiplied by If to obtain the losses which are injected into the thermal network.

The thermal capacitance of the device junction as well as its junction-to-case thermal resistance are represented by a one-cell Cauer network modeled with a Simulink® State-space block.

### The Thermal Network

Simscape blocks from the thermal foundation library are used to build a two-cell Cauer network based on the thermal capacitances (case and heat sink) and resistances (case-to-sink and sink-to-ambient). For the sake of simplicity, the two-cell Cauer network uses arbitrary values for the thermal capacitances in order to reduce the time required to simulate the thermal phenomena.

## Simulation

Run the simulation and observe the following operating points:

* From t=0 sec to t=5 sec: the inverter outputs 372 kW (power factor = 0.85) using a switching frequency of 850 Hz. The converter total losses are 2.7 kW and the highest junction temperature (125 C) is observed on IGBT1 of Module 1 (or IGBT2 of Module 2). See Tj(Celsius) Scope block inside the Additional Scopes & Measurements block.
* From t=5 sec to t=12 sec, the inverter outputs 210 kW (power factor = 0.85) using a switching frequency of 1850 Hz. The converter total losses are 2.7 kW and the highest junction temperature (125 C) is still observed on IGBT1 of Module 1.

## Command

Example model name: power\_switchinglosses

{% code lineNumbers="true" %}

```matlab
open('power_switchinglosses')
```

{% endcode %}

## Reference

\[1] Raffael Schnell, Manager Application, ABB Switzerland, "High-Voltage Phase-Leg Modules for Medium Voltage Drives and Inverters".


---

# 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/loss-calculation-in-a-three-phase-3-level-inverter.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.
