> 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/dc-drives/dc5-one-quadrant-chopper-5-hp-dc-drive.md).

# DC5 - One-Quadrant Chopper 5 HP DC Drive

This example shows the DC5 one-quadrant chopper DC 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-368370044cc4d2fc7901829ff6f97ce560755276%2FDC5_drive.png?alt=media" alt=""><figcaption></figcaption></figure>

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

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

This circuit uses the DC5 block of SPS. It models a one-quadrant chopper (buck converter) drive for a 5 HP DC motor.

The 5 HP DC motor is separately excited with a constant 150 V DC field voltage source. The armature voltage is provided by an IGBT buck converter controlled by two PI regulators. The buck converter is fed by a 280 V DC voltage source.

The first regulator is a speed regulator, followed by a current regulator. The speed regulator outputs the armature current reference (in p.u.) used by the current controller in order to obtain the electromagnetic torque needed to reach the desired speed. The speed reference change rate follows acceleration and deceleration ramps in order to avoid sudden reference changes that could cause armature over-current and destabilize the system. The current regulator controls the armature current by computing the appropriate duty ratio of the IGBT 5 kHz pulses (Pulse Width Modulation). This generates the average armature voltage needed to obtain the desired armature current. In order to limit the amplitude of the current oscillations, a smoothing inductance is placed in series with the armature circuit.

## Simulation <a href="#simulation" id="simulation"></a>

Start the simulation. You can observe the motor armature voltage and current, the IGBT pulses and the motor speed on the scope. The current and speed references are also shown.

The speed reference is set at 500 rpm at t = 0 s. Initial load torque is 15 N.m.

Observe that the motor speed follows the reference ramp accurately (+250 rpm/s) and reaches steady state around t = 2.5 s. The armature current follows the current reference very well, with fast response time and small ripples. Notice that the current ripple frequency is 5 kHz.

At t = 2.5 s, the load torque passes from 15 N.m to 20 N.m. The motor speed recovers fast and is back at 500 rpm at t = 3 s. The current reference rises to about 16.7 A to generate a higher electromagnetic torque to maintain the speed reference. As observed before, the armature current follows its reference perfectly.

At t = 3 s, the speed reference jumps down to 350 rpm. The armature current lowers in order for the speed to decrease following the negative speed slope (-250 rpm/s) with the help of the load torque.

At t = 4 s, the speed stabilizes around its reference.

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

1. The power system has been discretized with a 1us time step. The speed and current controllers use a 100 us and 20 us sampling time respectively in order to simulate a microcontroller control device.
2. In order to reduce the number of points stored in the scope memory, a decimation factor of 25 is used. Some transitions may thus not appear on the scope. To view detailed simulation results, reduce the decimation factor to 1.
3. A simplified version of the model using an average-value converter 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 the smallest control system sample time value. This can be done by typing 'Ts = 20e-6' in the workspace in the case of this example. See also **dc5\_example\_simplified** model.

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

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

Example model name: dc5\_example

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

```matlab
open('dc5_example')
```

{% 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/dc-drives/dc5-one-quadrant-chopper-5-hp-dc-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.
