> For the complete documentation index, see [llms.txt](https://www.ctrlaltftc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ctrlaltftc.com/practical-examples.md). # Practical Examples - [FTC Motor Control](https://www.ctrlaltftc.com/practical-examples/ftc-motor-control.md): This page will help teams that may be new to FTC begin by starting with basic motor movement and then working them through the various different ways to control such a motor. - [Drivetrain Control](https://www.ctrlaltftc.com/practical-examples/drivetrain-control.md): Drivetrains are arguably the most important part of a \*FIRST\* Tech Challenge autonomous and are crucial to get correct. - [Dealing with Angles](https://www.ctrlaltftc.com/practical-examples/controlling-heading.md): A very common use case for PID controllers in FTC is turning your robot to a desired heading. However, a few modifications are necessary. - [Roadrunner Control Explained](https://www.ctrlaltftc.com/practical-examples/roadrunner-control-explained.md): Roadrunner is a library used by many successful teams, and understanding why we utilize it in specific ways and not others is key to avoiding common pitfalls. --- # 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.ctrlaltftc.com/practical-examples.md?ask=&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.