> 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/get-started-with-sps/three-phase-rectifier.md).

# Three Phase Rectifier

This example shows how to use the diode block to simulate a three-phase rectifier.

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

## Description

A 10 ohm load is fed in DC through a three-phase rectifier from an inductive source (5 mH; 120 V rms). The rectified current is filtered by a 200mH inductance.

Diodes are connected in parallel with RC snubbers (1000 ohms-0.1 uF) The measurement output of Diode2 and Diode3 is used to observe the diode voltage and current.

## Simulation

{% stepper %}
{% step %}

### **Simulation with continuous integration method**

Check the simulation parameters in the Simulation -> Configuration Parameters menu. The Variable-step auto (Automatic solver selection) solver is selected. Note that the Simulation type parameter of the Powergui block is not accessible, and it is set to Continuous. Start the simulation and observe waveforms on the four-trace Scope block. Note that Simulink® selected the Ode23tb solver to simulate the model.

After a transient period, the load current Id stabilizes at 12.7 A. Note that most of the third harmonic which can be seen in the rectified voltage Vd (mean value 127 V) is filtered out by the smoothing reactor.

Also observe the commutation period due to the source inductances. The 3.3 degrees overlap is clearly seen on trace 3 of the scope showing currents in diodes 2 and 3.

Zoom on the Diode3 voltage (trace 4) during the conduction period. The voltage magnitude is the sum of the specified forward voltage (0.8 V) and the voltage developed across the diode resistance (0.01 ohm).
{% endstep %}

{% step %}

### **Simulation with discretized system**

Open the Configuration parameters of the model and select the Fixed-step auto (Automatic solver selection) solver. Restart the simulation. Note that the Simulation type parameter of the Powergui is automatically changed to Discrete, with a sample time of 50e-6 usec. Note that Simulink selected the FixedStepDiscrete solver to simulate the model.
{% endstep %}
{% endstepper %}

Compare waveforms with those obtained with the continuous integration algorithm.

## Command

Example model name: power\_rectifier

{% code lineNumbers="true" %}

```matlab
open('power_rectifier')
```

{% 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/get-started-with-sps/three-phase-rectifier.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.
