> 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/misc.-vex-parts-1/structure.md).

# Structure

Hardware used to attach parts to each other.

## Metal Material

While being a seemingly insignificant factor, choice in metal material can have a drastic impact on a robot's performance. There are two types of metal used in VEX products:

### Characteristics

<table data-header-hidden><thead><tr><th width="361.5">Steel</th><th>Aluminum</th></tr></thead><tbody><tr><td>Heavier Material</td><td>Lighter Material</td></tr><tr><td>More Rigid and Durable</td><td>Easier to Bend and Break</td></tr><tr><td>Appears Darker and more Reflective</td><td>Appears Lighter and flat</td></tr></tbody></table>

### On the Robot

Due to its lighter weight, aluminum should be used in subsystems that need to be kept as light as possible, such as lifts and game piece manipulators.

Steel is commonly used in areas where weight is less of a concern, or when a subsystem needs to be made heavier. In the event of a drive ratio favoring torque, a robot can be made heavier to help prevent being pushed by other robots.

As a general rule, however, aluminum should be used in the vast majority of places. Having a heavier robot, unless designed to be so, can be detrimental, and using aluminum instead of steel helps to drastically reduce the weight of a robot or subsystem.


---

# 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://wiki.purduesigbots.com/hardware/misc.-vex-parts-1/structure.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.