> 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/ac4-space-vector-pwm-dtc-induction-200-hp-motor-drive.md).

# AC4 - Space Vector PWM-DTC Induction 200 HP Motor Drive

This example shows a Space Vector PWM DTC Induction Motor Drive during speed regulation.

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

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

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

This circuit uses a modified version of the AC4 block of the SPS electric drives library. It models a direct torque control (DTC) induction motor drive with space vector pulse width modulation. The particularity of this modified version is that the DTC is no longer based on hysteresis regulation that implies switching at variable frequency but on a fixed frequency PMW inverter. As in AC4 it uses a braking chopper for a 200HP AC motor.

The induction motor is fed by a PWM voltage source inverter which is built using a Universal Bridge Block. The speed control loop uses a proportional-integral controller to produce the flux and torque references for the DTC block. The DTC block computes the motor torque and flux estimates and compares them to their respective reference. The torque and flux are then controlled by independent PI regulators that compute a reference voltage vector. The voltage source inverter is then controlled by the space vector modulation method in order to output the desired reference voltage.

Motor current, 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 and the DC bus voltage on the scope. The speed set point and the torque set point are also shown.

At time t = 0 s, the speed set point is 500 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 to its final value. This forces the electromagnetic torque to increase to the user-defined maximum value (1200 N.m) and then to stabilize at 820 N.m once the speed ramping is completed and the motor has reached 500 rpm.

At t = 1 s, the speed set point is changed to 0 rpm. The speed decreases down to 0 rpm by following precisely the deceleration ramp even though the mechanical load is inverted abruptly, passing from 792 N.m to - 792 N.m, at t = 1.5 s. Shortly after, the motor speed stabilizes at 0 rpm.

Finally, note how well the DC bus voltage is regulated during the whole simulation period.

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

The power system has been discretized with a 2us time step. The speed controller uses a 140 us sample and the DTC controller uses a 20 us sample time in order to simulate a microcontroller control device. The inverter switching frequency is set to 5 kHz.

## Command

Example model name: ac4\_svm\_dtc

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

```matlab
open('ac4_svm_dtc')
```

{% 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/ac4-space-vector-pwm-dtc-induction-200-hp-motor-drive.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.
