23509
RoboRibbits
Atlanta, GA, USA
Rookie Year
2023
Members
7
Mentors
8
Type
Community Team
Meeting Hours/Week
6
Approx. Budget
1000 - 3000 USD
Workspace
Home Workspace (garage, basement, etc.)
Sponsorship Status
1 - 3 Sponsors
Drivetrain
Mecanum
Materials
Prefabricated Metal Parts, Cardboard, 3D-Printed Plastic, Other
Product Sources
REV Robotics, GoBILDA, AndyMark, Other
Odometry
GoBILDA Pinpoint, Other
Sensors
HuskyLens, Other, Distance, External IMU/Gyro, Touch
Systems
Wheel Roller Intake, Other, Shooting Mechanism
Programming Language
OnBot Blocks
Development Environment
OnBot Java/Blocks
3rd-Party Tools
Other
Vision
AprilTag Localization
What is something that you think is unique about your robot this season? What about your robot do you think would make it stand out at competition?
Our robot traditionally is uniquely distinct, and this season is shaping up to have an unforgettable little bot with some surprising quirks.
What types of Outreach do you plan to do for this season? Which of those Outreach initiatives are you most proud of?
This season, we have increased our outreach numbers and ability to host hands-on METAL robotics workshops that allow people to build and program a metal FTC style robot, and see themselves in STEAM and experience what FIRST is!
Describe an element of your code which you think will be most advantageous to your performance over the season.
We anticipate the most advantageous element of our blocks code this season to be simple automations that allow the robot to intake, select, and shoot an artifact with the push of a single button.
What competitions will you be attending? Which of the ones that you listed are you looking forward to the most?
Were hoping to make Cowtown and the girls drive team event in the Midwest along with possibly returning to Kentucky for Run for the Robots, as we greatly enjoyed our experience there in 2025.
How will you be organizing your team at competitions?
It is important to our young team to ensure that EVERY team member gets a chance to build and code a robot when they join the team. Comprising numerous middle school students, we strive to keep team members from feeling boxed into a particular aspect of robotics, and instead plan to break into smaller groups to develop our multiple subsystems and their unique coding applications. At competitions, our drive captain and team captains take the lead on rotating drivers and scouts through league meets, networking with teams throughout the state, country and global FIRST networks to elevate our team’s strategy and game play as well as those of other teams.
Describe a unique or noteworthy strategic device or element that you think would be useful for this game.
This season we have begun by analyzing the competition manual and season reveal video to create a concise problem statement from which we will work throughout the season. Decisions matrixes help us to distance personal feelings from the team strategy and prototype only the most likely solutions that will further our team’s goals. We have some fun twists in mind for later in the league competition but first want to ensure we have a stylish, sturdy robot that can score effectively in auto and tele-op.
How would you describe your design process? How many options/strategies do you compare? How do you visualize your designs before building?
Engineering design process. We begin with a list of constraints, needs, and wants to write our problem statement which sets goals & percentile accuracy. Then we bring real world solutions, and ideas to share, discussing they can be implemented. The pros and cons of integration and how viable it is to our problem statement. The viable options are put to a depiction matrix with driving base, intake/output combined so that we can decide on our strongest robot design. The top contenders are further researched through prototyping and testing, then another matrix emphasizing our team strategy, scoring, and the game is done to identify the our solution. We get to work!
Made with by Electric Mayhem Robotics and external contributors
Check out our code on GitHub
Contact Us: contact@ftcopenalliance.org
FIRST TECH CHALLENGE OPEN ALLIANCE is fiscally sponsored by The Hack Foundation (d.b.a. Hack Club), a 501(c)(3) nonprofit (EIN: 81-2908499).