Here you can view some info on robots we have built for past games
Feel free to look through our code and CAD models for each robot. We use GitHub for storing code and PTC Creo (and Windchill) for CAD. (But beware, CAD models and code may be a bit messy) If you have any questions about our models, code, or just robots in general, please contact us.
Python was our 2017-2018 robot for the Relic Recovery season. In Relic Recovery, our robot needed to pick up 6in cubes from a center pit and stack them into columns on the wall, as well as knock off wiffle balls autonomously.
Our robot's capabilities: our robot's intake could extend four feet away and pick up blocks from the pit, as well as reliably sense wiffle ball colors and knock off the correct ball.
Why it's named Python: our intake originally could snap forward and backward, so it became known as a snake, and Python is also a programming language (We also printed out a photo of a snake head and attached it to our Lexan bucket on the intake).
CAD and Code
- 3rd place Inspire Award at the San Diego Regional
- Connect Award at San Diego League Tournament
Slug was our robot for the 2016-2017 FTC season, Velocity Vortex. Velocity Vortex required robots to pick up wiffle balls and shoot them into a center structure, as well as sense the colors of "beacons" and change them to red or blue, depending on the team.
Our robot's capabilities: shooting in the center vortex, reliably collecting beacons in autonomous
Why it's named Slug: it weighed one slug (measure of mass in the Imperial system) when we first weighed it.
CAD and Code
- 2nd place Inspire Award at the San Diego Regional
- Inspire Award Winner at a San Diego League Tournament
- PTC Design Award Winner at Super Regional: West
- Connect Award Winner at the San Diego Regional
- Finalist Alliance at the San Diego Regional
- Finalist for both Rockwell Collins Innovate and PTC Design at the FIRST Championship: Houston
- Semifinalist at FIRST Championship: Houston
Pheonix was our robot for Res-Q. Res-Q had a mountain for robots to climb, with boxes stationed at intervals up the mountain. These boxes could be filled with blocks and balls for points.
Our robot's capabilities this year: Filling the buckets.
Why it's named Pheonix: after our first qualifier, we discovered that the shifter we were using was made illegal, and our robot wasn't working at our standards. We decided to redesign almost the entire robot. Pheonixes are born from the ashes of the old one dying.
CAD and Code
- Captain, winning alliance, Hemmet qualifier
- 2nd place inspire, Hemmet qualifier
This was our robot for Cascade Effect. In Cascade Effect, we were tasked with getting wiffle balls into tall tubes of varying heights.
Our robot's capabilities this year: Pulling around the goals. (Ball-loader was not functional)
Why it's named "Mom": our team was bad at naming things.
- Motivate Award, San Diego Regional