> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/hardware/vex-drivetrains/best-practices.md). # Best Practices {% embed url="" %} This video does a great job show casing some of the best practices when building a drivetrain. ### Core Components **Bearing Blocks** When installed, the bearing flats are mounted directly onto the VEX V5 structure and provide a stable and secure platform for the shaft to rotate. The shaft is inserted through the center of the bearing flats and is held in place by the flats, which prevent the shaft from shifting or moving out of position. They are used to drastically reduce friction when shafts and screws are used. **Stand Offs** Using standoffs in the design of a VEX drive base provides several advantages, most notably increased rigidity. A drive base that is not rigid enough will have a lot of wobble, causing the robot to move around unpredictably and making it difficult to control. Standoffs can help prevent this by providing a solid, immovable structure that prevents the base from flexing and shaking during movement. **C-Channels** C-channels come in various lengths and widths that can be easily cut and modified to suit the specific needs of the robot's design. They can be used to create a variety of structures, and act as the basic building block for drivetrains. One of the main advantages of using C-channels in the design of a VEX drive base is their ability to provide additional support and stability to the structure. The C-channel's U-shape allows it to distribute force evenly across its length, helping to prevent any bending or warping of the metal plates. \
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.purduesigbots.com/hardware/vex-drivetrains/best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.