> 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/motor-drives/ac-drives/ac3-comparison-between-detailed-and-simplified-models.md).

# AC3 - Comparison Between Detailed and Simplified Models

This example shows the AC3 detailed model and the AC3 average model during speed regulation. The comparison is performed for normal condition and for inverter saturation condition.

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

O. Tremblay, L.-A. Dessaint (Ecole de technologie supérieure, Montreal)

## Description <a href="#description" id="description"></a>

This circuit uses two AC3 blocks of the SPS electric drives library. The AC3 block models a field-oriented control (FOC) induction motor drive with a braking chopper for a 200 HP AC motor. The first AC3 block is set to average value model and the second AC3 block is set to detailed model.

For the detailed model, the induction motor is fed by a PWM voltage source inverter, which is built using a Universal Bridge Block. The average value model uses ideal voltages and currents sources to feed the induction motor. The speed control loop uses a PI regulator to produce the flux and torque references for the FOC controller. The FOC controller computes the three reference motor line currents corresponding to the flux and torque references and then feeds the motor with these currents using a three-phase current regulator.

Motor currents, voltages, speed, and torque signals are available at the output of the block.

## Simulation <a href="#simulation" id="simulation"></a>

Start the simulation. You can observe the motor stator current, the rotor speed, the electromagnetic torque, the DC bus voltage and the magnitude of the rotor flux on the first scope. The speed set point and the torque set point are also shown. On the second scope, the dq currents and voltages are displayed. Note that all signals are multiplexed to compare the two models.

At time t = 0 s, the speed set point is 4000 rpm. Observe that the speed follows precisely the acceleration ramp.

At t = 0.5 s, the full load torque is applied to the motor shaft while the motor speed is still ramping.

At t = 0.65 s, the inverter is saturated due to the limited DC bus voltage. You can observe loss of current tracking which decreases the motor torque.

At t = 1.5 s, the speed set point is changed to -4000 rpm.

At t = 2 s, the deceleration ramp reaches the motor speed. The inverter comes back to normal mode.

At t = 2.5 s, the mechanical load passes from 792 N.m to -792 N.m.

At t = 3.45 s, the inverter is saturated due to insufficient DC bus voltage. You can observe loss of current tracking which decreases the motor torque.

Finally, notice that the results of the average-value model are similar to those of the detailed model except that the higher frequency signal components are not represented with the average-value converter.

#### Notes <a href="#notes" id="notes"></a>

To evaluate the speed gain of the average value model, see **ac3\_example\_simplified** and compare the simulation speed with **ac3\_example**.

## Command <a href="#command" id="command"></a>

Example model name: ac3\_example\_comparison

{% code lineNumbers="true" expandable="true" %}

```matlab
open('ac3_example_comparison')
```

{% 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/motor-drives/ac-drives/ac3-comparison-between-detailed-and-simplified-models.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.
