> 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/speed-reducer.md).

# Speed Reducer

This example shows the speed reducer model connected between a high-speed shaft and a low-speed shaft.

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-80bbc6012ed39956a6ea24b32448b2a1d3bce1ec%2Fspeed_reducer_ex.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>

The speed reducer is driven by a variable speed source and is connected to a load. The load has an inertia of 30 kg\*m^2 and a viscous friction term of 0.5 N.m.s.

The reduction device has a reduction ratio of 10 and its inertia with respect to the high-speed side is 0.0005 kg\*m^2.

The high-speed shaft has a stiffness of 17190 N.m and an internal damping factor of 600 N.m.s. This shaft is designed to have 0.1 degree of angular deflection for a 30 N.m load torque. The low-speed shaft, having a higher torque to transmit, has a stiffness of 171900 N.m and an internal damping factor of 6000 N.m.s. This shaft is designed to have 0.1 degree of angular deflection for a 300 N.m load torque.

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

Start the simulation. You can observe the driving (high-speed) and load speeds (low-speed), the torque transmitted by the high-speed shaft and the torque transmitted by the low-speed shaft on the scope.

At t = 0 s, the driving speed starts climbing to 1750 rpm with a 500 rpm/s acceleration ramp. This causes the transmitted torque of the high-speed shaft to jump to about 18 N.m. Because of the reduction device, the torque transmitted to the load by the low-speed shaft is a lot bigger and is worth about 170 N.m.

During the accelerating phase, both torques keep increasing in order to compensate the viscous friction of the load. Notice that the load accelerates with a ramp of +50 rpm/s due to the reduction ratio of the speed reducer.

At t = 3.5 s, the driving speed settles at 1750 rpm. Since no more accelerating torque is needed, the input and output torques decrease and stabilize respectively to 0.965 N.m and 9.16 N.m at t = 4 s. The load speed is now equal to 175 rpm.

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

1. The speed reducer has been discretized with a 1 us time step.

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

Example model name: reducer\_example

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

```matlab
open('reducer_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/speed-reducer.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.
