> 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/courseware/electric-courseware/electric-motor-drives/doubly-fed-induction-machine-dfim-drive/exercises.md).

# Exercises

After completing the following series of exercises, the student will understand the design of controllers for a doubly fed induction machine.\
Real-time simulation results are shown in the laboratory panel.

## Subsynchronous mode <a href="#subsynchronous-mode" id="subsynchronous-mode"></a>

* Load the model with the **default settings**.
* Apply an **input torque of 0.2 p.u.**, then a reference speed of 240 rpm.
  * Does the measured torque follow the input torque?
  * Does the measured speed follow the reference speed?\
    ***Hint**: Look at waveforms under DFIM Control and Triggering Scopes to answer the questions above.*
* Increase the **input torque to 0.4 p.u.**
  * How does the increase in input torque impact the rotor and stator currents?\
    Explain your observation.
  * Does the measured torque follow the input torque?

## Synchronous mode <a href="#synchronous-mode" id="synchronous-mode"></a>

* Set the **input torque to zero**.
* Set the reference speed to its **nominal value of 277 rpm**.
  * Does the measured speed follow the reference speed?\
    Show your result.
* Increase the **input torque to 0.2 p.u.**
  * Observe the waveforms of rotor currents and explain their non-sinusoidal shapes.
  * Does the measured torque follow the input torque?\
    Show your result.

## Hypersynchronous mode <a href="#hypersynchronous-mode" id="hypersynchronous-mode"></a>

* Set the **input torque to zero**.
  * What do you expect as values for rotor currents?\
    Explain.
* Set the **reference speed to 280 rpm**.
  * Does the measured torque follow the input torque?
  * Does the measured speed follow the reference speed?
* Increase the **input torque to 0.5 p.u.,** then the **reference speed to 304 rpm**.
  * Show that the torque and speed controllers are working properly.
  * Show the current controllers for *I*<sub>*d*</sub> and *I*<sub>*q*</sub> are working properly.\
    ***Hint**: Showing the waveforms is enough as a solution.*
* Increase the **reference current&#x20;*****I***<sub>***d***</sub>**&#x20;to 0.2 p.u**.
  * Does the measured current *I*<sub>*d*</sub> follow the reference?\
    Show your result.
  * **Waveforms 1**: Save the waveforms of rotor and stator currents, via a screenshot, for example.
* Increase the **reference current&#x20;*****I***<sub>***d***</sub>**&#x20;to 0.4 p.u**.
  * **Waveforms 2**: Save the waveforms of rotor and stator currents.
  * How does the increase in current *I*<sub>*d*</sub> impact the rotor and stator currents.\
    ***Hint**: Analyze the results of Waveforms 1 and 2.*


---

# 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/courseware/electric-courseware/electric-motor-drives/doubly-fed-induction-machine-dfim-drive/exercises.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.
