> 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/machines/blocks/machines-control/ac-drives/space-vector-pwm-vsi-induction-motor-drive.md).

# Space Vector PWM VSI Induction Motor Drive

## Description

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

The Space Vector PWM VSI Induction Motor Drive block, located in the **OPAL-RT SPS Software/Electrical Machines/Control/AC Drives** library, commonly called the **AC2 motor drive**, models a classical closed-loop Volts/Hz control drive for induction motors.

The block contains a closed-loop speed control with slip regulation. The speed-control loop outputs the reference motor slip, which is added to the measured rotor speed to obtain the reference frequency of the stator flux. The reference stator voltage is derived from the Volts/Hz control and from the constant flux strategy. The stator frequency and voltage references are then used to obtain the required PWM signals for the inverter following the space vector modulation strategy.

The main advantage of this drive compared to vector-controlled drives is its implementation simplicity. However, as with most scalar-controlled drives, the dynamic response of this drive is slow due to the inherent coupling effect between the torque and flux present in the machine.

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

The Space Vector PWM VSI Induction Motor Drive block uses the following blocks from the Electric Drives / Fundamental Drive Blocks library:

* Speed Controller (Scalar Control)
* Space Vector Modulator
* DC Bus
* Inverter (Three-Phase)

The model is discrete. Good simulation results have been obtained with a 2 *µ*s time step. The control system has two different sampling times:

* The speed controller sampling time
* The space vector modulator controller sampling time

The speed controller sampling time has to be a multiple of the space vector modulator sampling time. The latter sampling time has to be a multiple of the simulation time step.

The simulation step size must be chosen in accordance with the inverter's switching frequency. A rule of thumb is to choose a simulation step size 100 times smaller than the switching period. If the simulation step size is set too high, the simulation results can be erroneous. The average-value inverter allows the use of bigger simulation time steps since it does not generate small time constants (due to the RC snubbers) inherent to the detailed converter. For a controller sampling time of 20 µs, good simulation results have been obtained for a simulation time step of 20 µs. This time step can, of course, not be higher than the controller time step.

### Model Specifications <a href="#model-specifications" id="model-specifications"></a>

The library contains a 3 hp and a 200 hp drive parameter set. The specifications of these two drives are shown in the following table.

**3 HP and 500 HP Drive Specifications**

|                          | 3 HP Drive                                              | 200 HP Drive                                              |
| ------------------------ | ------------------------------------------------------- | --------------------------------------------------------- |
| **Drive Input Voltage**  | <p>Amplitude: 220 V<br>Frequency: 60 Hz</p>             | <p>Amplitude: 575 V<br>Frequency: 60 Hz</p>               |
| **Motor Nominal Values** | <p>Power: 3 hp<br>Speed: 1705 rpm<br>Voltage: 220 V</p> | <p>Power: 200 hp<br>Speed: 1785 rpm<br>Voltage: 575 V</p> |

## Parameters

### General

<table data-header-hidden><thead><tr><th width="220.22222900390625"></th><th></th></tr></thead><tbody><tr><td><strong>Output bus mode</strong></td><td>Select how the output variables are organized.<br>If you select <strong>Multiple output buses</strong> (default), the block has three separate output buses for motor, converter, and controller variables.<br>If you select <strong>Single output bus</strong>, all variables output on a single bus.</td></tr><tr><td><strong>Model detail level</strong></td><td>Select between the detailed and the average-value inverter. Default is Detailed.</td></tr><tr><td><strong>Mechanical input</strong></td><td><p>Select between the load torque, the motor speed and the mechanical rotational port as mechanical input. Default is Torque Tm.</p><p>If you select and apply a <strong>load torque</strong>, the output is the motor speed according to the following differential equation that describes the mechanical system dynamics:</p><p><span class="math">T_e=J\frac{d}{dt}\omega_r+F\omega_r+T_m \\[4pt]</span></p><p>This mechanical system is included in the motor model.</p><p>For the <strong>mechanical rotational port</strong>, the connection port S counts for the mechanical input and output. It allows a direct connection to the Simscape environment. The mechanical system of the motor is also included in the drive and is based on the same differential equation.</p><p>If you select the <strong>motor speed</strong> as mechanical input, then you get the electromagnetic torque as output, allowing you to represent externally the mechanical system dynamics. The internal mechanical system is not used with this mechanical input selection and the inertia and viscous friction parameters are not displayed.</p></td></tr><tr><td><strong>Use signal names as labels</strong></td><td><p>When you select this check box, the Motor, Conv, and Ctrl measurement outputs use the signal names to identify the bus labels.<br>Select this option for applications that require bus signal labels to have only alphanumeric characters.</p><p>When this check box is cleared (default), the measurement output uses the signal definition to identify the bus labels. The labels contain non-alphanumeric characters that are incompatible with some Simulink® applications.</p></td></tr></tbody></table>

### Asynchronous Machine Tab <a href="#asynchronous-machine-tab" id="asynchronous-machine-tab"></a>

The **Asynchronous Machine** tab displays the parameters of the Asynchronous Machine block of the Fundamental Blocks (powerlib) library.

### Converters and DC Bus Tab <a href="#converters-and-dc-bus-tab" id="converters-and-dc-bus-tab"></a>

The **Converters and DC bus** tab displays the parameters of the Universal Bridge block (diode bridge configuration) of the Fundamental Blocks / Power Electronics library as well as the DC Bus and Inverter (Three-Phase) blocks of the Electric Drives / Fundamental Drive Blocks library.

### Controller Tab <a href="#controller-tab" id="controller-tab"></a>

The **Controller** tab displays the parameters of the Speed Controller (Scalar Control) and Space Vector Modulator blocks of the Electric Drives / Fundamental Drive Blocks library.

### Parameters <a href="#parameters" id="parameters"></a>

<table data-header-hidden><thead><tr><th width="220.2222900390625"></th><th></th></tr></thead><tbody><tr><td><strong>Schematic</strong></td><td>When you click this button, a diagram illustrating the speed and current controllers schematics appears.</td></tr></tbody></table>

## Inputs

<table data-header-hidden><thead><tr><th width="220.22222900390625"></th><th></th></tr></thead><tbody><tr><td><strong>SP</strong></td><td>The speed or torque set point. The speed set point can be a step function, but the speed change rate will follow the acceleration / deceleration ramps.<br>If the load torque and the speed have opposite signs, the accelerating torque will be the sum of the electromagnetic and load torques.</td></tr><tr><td><strong>Tm</strong> or <strong>Wm</strong></td><td>The mechanical input: load torque (Tm) or motor speed (Wm).<br>For the mechanical rotational port (S), this input is deleted.</td></tr><tr><td><strong>A, B, C</strong></td><td>The three phase terminals of the motor drive.</td></tr></tbody></table>

## Outputs

<table data-header-hidden><thead><tr><th width="220.22222900390625"></th><th></th></tr></thead><tbody><tr><td><strong>Wm</strong>, <strong>Te</strong> or <strong>S</strong></td><td>The mechanical output: motor speed (Wm), electromagnetic torque (Te) or mechanical rotational port (S).</td></tr><tr><td><strong>Motor*</strong></td><td>if <strong>Output bus mode</strong> parameter is set to <strong>Multiple output buses</strong><br>The motor measurement vector. This vector allows you to observe the motor’s variables using the Bus Selector block.</td></tr><tr><td><strong>Conv*</strong></td><td><p>if <strong>Output bus mode</strong> parameter is set to <strong>Multiple output buses</strong><br>The three-phase converters measurement vector. This vector contains:</p><ul><li>The rectifier output voltage</li><li>The inverter output voltage</li><li>The rectifier input current</li><li>The inverter output current</li></ul><p>Note that all current and voltage values of the bridges can be visualized with the Multimeter block.</p></td></tr><tr><td><strong>Ctrl*</strong></td><td><p>if <strong>Output bus mode</strong> parameter is set to <strong>Multiple output buses</strong></p><p>The controller measurement vector. This vector contains:</p><ul><li>The firing angle computed by the current controller</li><li>The speed error (difference between the speed reference ramp and actual speed)</li><li>The speed reference ramp</li></ul></td></tr></tbody></table>

**\*** When the **Output bus mode parameter** is set to **Single output bus**, the block groups the Motor, Conv, and Ctrl outputs into a single bus output.

## Examples <a href="#examples" id="examples"></a>

The [AC2 - Space Vector PWM VSI Induction 3HP Motor Drive](https://opal-rt.atlassian.net/wiki/spaces/PSPS/pages/2449244204) (ac2\_example) example illustrates an AC2 induction motor drive simulation with standard load conditions.

## References <a href="#references" id="references"></a>

\[1] Bose, B. K. *Modern Power Electronics and AC Drives*. Upper Saddle River, NJ: Prentice-Hall, 2002.

\[2] Grelet, G., and G. Clerc. *Actionneurs électriques, Éditions*. Paris: Eyrolles, 1997.

\[3] Krause, P. C. *Analysis of Electric Machinery*. New York: McGraw-Hill, 1986.


---

# 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/machines/blocks/machines-control/ac-drives/space-vector-pwm-vsi-induction-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.
