> 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-sensorless-field-oriented-control-induction-motor-drive.md).

# AC3 - Sensorless Field-Oriented Control Induction Motor Drive

This example shows the Sensorless Field-Oriented Control 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-dfaff545bed74783271965326d9a05bc289b92ff%2FAC3_sensorless.png?alt=media" alt=""><figcaption></figcaption></figure>

Souleman Njoya M., Louis-A. Dessaint (Ecole de technologie supérieure, Montreal))

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

This circuit uses a modified version of the AC3 block of SPS library. It models a sensorless field-oriented control (FOC) induction motor drive with a braking chopper for a 200HP AC motor. The motor speed is estimated from terminal voltages and currents based on the MRAS (Model Referencing Adaptive System) technique \[1]. Consequently, the speed sensor (necessary in AC3) is no more required.

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 PI controller 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 current, speed (reference, real and estimated), 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>

1. The power system has been discretized with a 2 us time step. The speed controller uses a 100 us sampling time and the vector controller uses a 20us sampling time in order to simulate a microcontroller control device.
2. A simplified version of the model using average-value inverter can be used by selecting 'Average' in the 'Model detail level' menu of the graphical user-interface. The time step can then be increased up to 40 us. This can be done by typing 'Ts = 40e-6' in the workspace and by changing the speed controller sampling time to 120e-6 and the vector controller sampling time to 40e-6. See also **ac3\_sensorless\_simplified** model.

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

Example model name: ac3\_sensorless

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

```matlab
open('ac3_sensorless')
```

{% endcode %}

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

1. Bose, Bimal K., "Modern Power Electronics And AC Drives", Prentice-Hall, Inc., Upper Saddle River, NJ 07458, 2002.


---

# 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-sensorless-field-oriented-control-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.
