> 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/library-specific-guides/motor-drives/mechanical-models.md).

# Mechanical Models

## Mechanical Shaft Block

The **Mechanical Shaft block** is used to simulate a shaft interconnecting mechanically a motor drive block to a mechanical load block. Hence the Mechanical Shaft block allows decoupling of the mechanical parameters of the load from the ones of the motor. The mechanical shaft is represented by its stiffness coefficient *K*<sub>*sh*</sub> and damping coefficient *D*<sub>*sh*</sub>. The shaft transmitted torque *T*<sub>*sh*</sub> is computed with

$$
T\_{sh} = K\_{sh} \int (\omega\_m - \omega\_l), dt + D\_{sh} (\omega\_m - \omega\_l)
$$

where *ω*<sub>*m*</sub> and *ω*<sub>*l*</sub> are the speeds of the motor and the load, respectively.

The following figure shows the interconnections between the Motor Drive block, the Mechanical Shaft block, and the Mechanical Load block.

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-9a45a33124e77da1ae5d4b2ce30808e41b0adcee%2Fmechanical_model_shaft_load.png?alt=media" alt=""><figcaption><p>Interconnection Diagram of the Transmission Shaft</p></figcaption></figure>

The Mechanical Shaft block has two inputs, the load and motor speeds, and one output, the shaft transmitted torque. Note that the transmitted torque is applied at the load torque input of the motor. The transmitted torque is also applied at the input of the Mechanical Load block, which can be modeled by

$$
T\_{sh} = J\_l \frac{d\omega\_l}{dt} + B\_l \cdot \omega\_l
$$

where *J*<sub>*l*</sub> and *B*<sub>*l*</sub> are the inertia coefficient and the viscous friction coefficient, respectively.

## Speed Reducer Block

In many applications, the mechanical load requires high torque at low speed rather than low torque at high speed. This can be obtained by interconnecting the motor to the mechanical load by a speed reducer.

The **Speed Reducer block** is composed of a high-speed shaft and a low-speed shaft connected by a speed reduction device, as shown in the following figure. The Speed Reducer block has seven parameters: the stiffness and damping coefficients of the high-speed and the low-speed shafts, the reduction ratio, and the speed reduction device inertia and efficiency. The two inputs of the Speed Reducer block are the motor speed (high speed) and the load speed (low speed) while the outputs are the high-speed shaft torque *T*<sub>*h*</sub> and the low-speed shaft torque *T*<sub>*l*</sub>. The high-speed shaft torque must be applied to the load torque input of the motor. The low-speed shaft torque must be applied directly to the Mechanical Load block.

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-15377cb54119430f3984742f9905fc935c7ffe8a%2Fmecahnical_model_speed_reducer.png?alt=media" alt=""><figcaption><p><strong>Interconnection Diagram of the Three Internal Blocks of the Speed Reducer Block</strong></p></figcaption></figure>


---

# 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/library-specific-guides/motor-drives/mechanical-models.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.
