7305 / up close
The intake
The intake photographed with the two different ball sizes used in BIOBUZZ: POLLEN and NECTAR
FTC 7305 / Inside the build
Our Robot
Meet the hardware behind the Gearcats’ ideas Explore our robot, look inside its mechanisms, and see the prototypes along the way
Explore the mechanismsLook closer
Parts with a purpose
These photos from our Portfolio show the intake, side prong, and launcher Tap a photo to explore the details
7305 / the details
The side prong
The team’s three-photo sequence shows the side prong and how it sits beside the field structure
7305 / inside the build
The launcher
A side view of the robot and a close-up inside the launcher, with labels added by the team
Ideas taking shape
Our prototypes
Prototypes are builds used to try ideas These team photos show frames, rollers, and a robot on the practice field
Robot prototype
Prototype frame up close
An upright metal frame and wheel assembly on the workbench, with tools and spare parts nearby
Robot prototype
Prototype rollers on the workbench
A metal frame with a row of black rollers, surrounded by parts on the workbench
Robot prototype
Prototype on the practice field
A full view of the robot on the practice field, showing its wheels, wiring, and raised mechanism
7305 / Coding
The code behind the robot
Programming turns a robot’s hardware into actions Code connects driver controls, motors, and sensors so the robot can respond to instructions
From buttons to movement
Driver-control code translates joystick and button inputs into actions, such as driving or moving a mechanism Clear controls help drivers operate the robot
Follow a path with Pedro
We use Pedro Pathing, a programming library that helps our robot follow planned paths during autonomous—the part of a match without driver input We can break a route into smaller steps, test it on the field, and adjust our code
Test, debug, repeat
Debugging means finding and fixing problems in code Testing small changes on the real robot helps show whether the program behaves as intended