Embedded Files
Here you can view some info on robots we have built for past games.
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.
TONK: 2021-2022
TONK: 2021-2022
Tonk was our 2021-2022 robot for the Freight Frenzy season. In Freight Frenzy, our robot needed to pick up plastic cubes and balls like those seen in the Rover Ruckus season. These objects would be placed either onto an alliance or shared scoring depot. The match endgame consisted of either spinning rubber ducks off of a turntable or capping the team depot.
Our robot's capabilities: Our robot could intake and outtake blocks and balls, along with being able to spin ducks and cap simultaneously thanks to a measuring tape capping mechanism inspired by our previous robot Yoshi.
Why it's named Tonk: Due to the turret, weight, metal-sided drive base, and green color scheme of this robot, we thought it looked like a tank and chose to name it Tonk.
CAD and Code
CAD and Code
Season Summary
Season Summary
ONION: 2020-2021
ONION: 2020-2021
Python was our 2020-2021 robot for the Ultimate Goal season. In Ultimate Goal, our robot was tasked with launching orange foam rings into a goal. Endgame consisted of shooting rings at three precision targets.
Our robot's capabilities: Our robot could intake and hold multiple disks and launch them using a flywheel mechanism.
Why it's named Onion: Our robot was named onion as a reference to the famous Shrek movie franchise, the robot had many layers of tape, and due to the many technical issues faced through the season, one of our members noted that it shared several features to an onion such as "having layers and making us cry."
Season Summary
Season Summary
YOSHI: 2019-2020
YOSHI: 2019-2020
Yoshi was our 2019-2020 robot for the Skystone season. In Skystone, our robot needed to pick up large yellow blocks and stack them into towers, moving the plaform of the towers in endgame.
Our robot's capabilities: Our robot could stack the blocks and move the platform.
Why it's named Yoshi: This year's robot featured a measuring
tape "tongue" that would reach out from the robot.
Season Summary
Season Summary
NIGHTWING: 2018-2019
NIGHTWING: 2018-2019
Nightwing was our 2018-2019 robot for the Rover Ruckus season. In Rover Ruckus, our robot needed to pick up plastic cubes and balls from inside the "craters" and place them into the center scoring depot. In the endgame, the robot would lift itself off the ground, suspended by a hook.
Our robot's capabilities: Our robot could intake, sort, and outtake blocks and balls, and fully hang off the depot hook.
Why it's named Nightwing: Our robot in one weekend was named Bat, and the accomplice of batman is named Nightwing.
CAD and Code
CAD and Code
Season Summary
Season Summary
PYTHON: 2017-2018
PYTHON: 2017-2018
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
CAD and Code
CAD download (PTC CREO .asm zip)
Season Summary
Season Summary
3rd place Inspire Award at the San Diego Regional
Connect Award at San Diego League Tournament
SLUG: 2016-2017
SLUG: 2016-2017
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
CAD and Code
Season Summary
Season Summary
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
PHOENIX: 2015-2016
PHOENIX: 2015-2016
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
CAD and Code
Season Summary
Season Summary
Captain, winning alliance, Hemmet qualifier
2nd place inspire, Hemmet qualifier
"Mom": 2014-2015
"Mom": 2014-2015
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.
Code
Code
(we did not know CAD yet)
Season Summary
Season Summary
Motivate Award, San Diego Regional
Report abuse