> 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/machines/permanent-magnet-synchronous-machine.md).

# Permanent Magnet Synchronous Machine

This example shows the Permanent Magnet Synchronous Machine in a closed-loop speed and current control on a 1.1 kW, 3000 rpm industrial motor.

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

## Description

A three-phase motor rated 1.1 kW, 220 V, 3000 rpm is fed by a PWM inverter. The PWM inverter is built entirely with standard Simulink® blocks. Its output goes through Controlled Voltage Source blocks before being applied to the PMSM block's stator windings. The load torque applied to the machine's shaft is originally set to its nominal value (3 N.m) and steps down to 1 N.m at t = 0.04 s.

Two control loops are used. The inner loop regulates the motor's stator currents. The outer loop controls the motor's speed.

## Simulation

Observe that the stator currents are quite "noisy," which is to be expected when using PWM inverters. Also, the amplitude of these currents decreases at t = 0.04 s, when the load is decreased. The noise introduced by the PWM inverter is also observed in the electromagnetic torque waveform Te. However, the motor's inertia prevents this noise from appearing in the motor's speed waveform.

## Command

Example model name: power\_pmmotor

{% code lineNumbers="true" %}

```matlab
open('power_pmmotor')
```

{% 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/machines/permanent-magnet-synchronous-machine.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.
