> For the complete documentation index, see [llms.txt](https://ascendrobotics.gitbook.io/ascend/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ascendrobotics.gitbook.io/ascend/vex-robotics/building/drive-trains.md).

# Drive Trains

Drive trains are not technically required, but nearly every robot has one. They allow the robot to traverse the field, and serve as a foundation for the rest of the the robot.

Here's the simplest possible drivetrain you can have:

<figure><img src="/files/GIXoEVNGE1pWDE950Yxq" alt=""><figcaption><p>Simple tank drivetrain CAD</p></figcaption></figure>

This tank drivetrain features at least 2 omniwheels on each side of the robot. Usually, 4 or 6 motors will power these omniwheels either directly or through gears. This drivetrain can turn in place and go forwards and backwards, but it cannot strafe side-to-side (which is usually not necessary).&#x20;

Here's another example of a more complex tank drive with 6 motors, 6 wheels, and a gear system:

<figure><img src="https://lh5.googleusercontent.com/uZzR-ZprCYNac6vcJL1AmIYF_gnEuAteK7570AeTmFzUJvtQUL8EsPDtlk6i_707hXqUjh3-ekcbZHOpOUk1_OhwapOqqHQ1QqiaZOmmwZ6cu9oJ4ifs3ujX85GLSTq0TWlDwKMkf6oZBltjFSselHY" alt=""><figcaption><p>Example drivetrain CAD</p></figcaption></figure>

Another type of drivetrain is the X-drive. This drive has more maneuverability, but reduced torque and pushing power relative to the standard tank drive.

<figure><img src="/files/EiRSJrRnjByWI2vZHmZX" alt=""><figcaption><p>Photo credit: Team 1619Z</p></figcaption></figure>

While the increased maneuverability does offer an advantage in niche scenarios, X-drives are very weak against defense by others teams. For example, out of the 20 teams that won their division during Spin Up Worlds (i.e. top 20 teams in the world), all 20 of them used a tank drive.

There are another couple types of drivetrains, but these are not competitively viable in VEX Robotics.

![](https://lh6.googleusercontent.com/fm7KAo3V9DicBPDrqN_xbHWLRtWfoh4wiH7waIToToQDcGb6ryHB3jdOdp6oAt1pKwZ5z3vCIYHBY2SwosG3I9nkhqvuKYkkwSi39Bd7xR6ulI81RM0AzeTDDbFiZ2UPgucMLpqpMADL9BvzE87qxlY)![](/files/ldDY4WXlPEPczpGmhuxa)

Overall, the recommended drivetrain for both new and experienced teams is the standard tank drive.

## Design Guidelines

Let's assume you're going with the tank drivetrain (please do!). Here's a few general guidelines to keep in mind while designing it.

* Smaller is generally better, but don't make a drive so small that it can't fit other mechanisms on the top of the robot
* Don't use any more gears than is absolutely necessary, to reduce friction
* Have the wheels as far apart as possible, which makes it harder for the robot to tip over
* Use 2-3 cross-braces, and have them as far apart as possible. This keeps the chassis from bending under heavy defense

Here's another example CAD that follows these guidelines. Always CAD the drivetrain before building it!

<figure><img src="https://lh3.googleusercontent.com/vpbr3QGlgUUPM_iGoT-J4Tay6OJ8blknSbqUvCiIsQnAVs5XoH6vXGqj5agjIO9hNjrWCwlLfpXxlCoQEdPnkJQ-sr_3M9AYaS24eYewKAZz_7J7fwbmiCS4-TGMgg9vwuVLFPG2TS1l3QU8fBnBRJQ" alt=""><figcaption><p>Over Under drivetrain CAD from 96504C</p></figcaption></figure>

## Additional Resources

Here's two videos on how to square the chassis--this is very important for having consistent autonomous and a low friction drivetrain.

{% embed url="<https://youtu.be/yC_6j7vawfk>" %}

{% embed url="<https://youtu.be/BgPrhM-p79w>" %}


---

# 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:

```
GET https://ascendrobotics.gitbook.io/ascend/vex-robotics/building/drive-trains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
