> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/transmitting-power/introduction-to-motion.md).

# Introduction to Motion

**Power transmission** is the system of components that transfers motion from your motors to the moving parts of your robot. The easiest way to think of it is how you get things like wheels, arms, or intake mechanisms to spin. In FTC, choosing the right transmission method can impact your performance, efficiency, reliability, and maintainability.

This page provides an overview of common power transmission systems used in FTC, along with guidance on when and why to use each one.

### Common Power Transmission Methods

Each of the following methods has its own strengths, weaknesses, and ideal use cases:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Chain and Sprocket</td><td><p></p><ul><li><strong>Pros</strong>: Allows flexible placement, strong under load</li><li><strong>Cons</strong>: Requires tensioning, can be noisy</li><li><strong>Use Cases</strong>: Drivetrains, arms, elevator mechanisms</li></ul></td><td><a href="https://1127739367-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD2GXZ5NUEk64Zn6lJiL2%2Fuploads%2FbOY35VQZQDpuWXGQHBTO%2Fimage.png?alt=media&amp;token=95e41169-5163-44c8-8abf-ccd5c70013f3">image.png</a></td></tr><tr><td>Belts and Pulleys</td><td><p></p><ul><li><strong>Pros</strong>: Quiet, lightweight, flexible layouts</li><li><strong>Cons</strong>: Can slip if not properly tensioned, lower load capacity</li><li><strong>Use Cases</strong>: Intakes, transfer systems, turrets</li></ul></td><td><a href="https://1127739367-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD2GXZ5NUEk64Zn6lJiL2%2Fuploads%2FoW4WeIvKRmrZOUxpH8vf%2Fimage.png?alt=media&amp;token=fcaa0d77-248b-4f89-8155-46d1620bfbf7">image.png</a></td></tr><tr><td>Spur Gears</td><td><ul><li><strong>Pros</strong>: High efficiency, compact, precise</li><li><strong>Cons</strong>: Requires rigid mounting, sensitive to misalignment</li><li><strong>Use Cases</strong>: Drivetrains, linear slides, arms</li></ul></td><td><a href="https://1127739367-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD2GXZ5NUEk64Zn6lJiL2%2Fuploads%2FU3nkNv62la6K2cuRLwWS%2Fimage.png?alt=media&amp;token=1b2e631d-581f-4156-a934-b6bba6e45ce6">image.png</a></td></tr></tbody></table>

### Tutorials and Examples

* [Designing a Custom Gearbox in Onshape](https://www.ftcwiki.org/intro-to-cad/level-2/b.-power-transmission-wip.md#examples)
* [Chain Tensioning Techniques](https://www.youtube.com/watch?v=vi2FfGqCeGI)


---

# 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.ftcwiki.org/transmitting-power/introduction-to-motion.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.
