> 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/flip-out-mechanisms.md).

# Flip Out Mechanisms

Tips on building mechanisms that extend outside of the robot's starting size.

A lot of times a robot will need to have a mechanism that "flips out", or expands outside of the 18 inch box at the start of the match. There are a few different ways to do this.

A lot of teams will make flip out mechanisms that are triggered by the robot's lift going up - it's fairly easy to hold something in place that moves horizontally with a lift, since the lift is constrained horizontally.

Starstruck was a game that required a flip-out mech for the popular claw design. Many flip out mechanisms were triggered by the claws opening. Similar use of the intake to trigger a flip out is good for other games too.

One example of several flip-out mechanisms being utilized on one robot was [97934V's Starstruck Deploy](https://www.youtube.com/watch?v=u9XEYpPA-H4). Most notably, its claw was held behind its lift tower until the lift was raised.

![97934V's Starstruck Deploy](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7yGVyBrcpSR8SDSikj%2Fuploads%2Fgit-blob-236ade3a455049e409bd130f7bd94060bf7bdc95%2F97934vs-starstruck-deploy.png?alt=media)

Another successful flip-out mechanism was the [2019 Ri3D team's intake flipout](https://youtu.be/BC4ZlIcBB7I?t=145). It utilized a standoff to hold in the intakes until the lift was raised. Then, the intakes flipped out and locked with another standoff.

![2019 SoCal RI3D Intake Flipout](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7yGVyBrcpSR8SDSikj%2Fuploads%2Fgit-blob-116dbcb02b4106fe4735e8d7071b2b81b9aa10d1%2Fbens-intake-flipout.png?alt=media)

This mechanism was not a "flip-out" mechanism in the conventional way, but [Antichamber's Modular Cone Launcher](https://www.youtube.com/watch?v=zHS9VIAxNNM) was certainly interesting. In Vex In the Zone, several teams utilized their preload by launching it across the field to block another teams autonomous function. This was one particular mechanism for doing so.

![Antichamber's Modular Cone Launcher](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M7yGVyBrcpSR8SDSikj%2F-ME8lcQrxi76u_e2oMbf%2F-ME8mckDUIVdA1uowyxJ%2FAntichamber's%20Modular%20Cone%20Launcher.png?alt=media\&token=6dac6dba-982b-41bc-8206-7b6e5507711e)

## Contributing Teams to this Article:

* [2775J](https://www.youtube.com/channel/UCxpfFq6ShDvgmU9P4y6rc_Q?view_as=subscriber) (Jackson Area Robotics)


---

# 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/flip-out-mechanisms.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.