ITKAN MYCC
Raleigh, NC, USA
Rookie Year
2023
Members
11
Mentors
2
Type
Community Team
Meeting Hours/Week
20
Approx. Budget
3000 - 5000 USD
Workspace
Dedicated Robotics Lab
Sponsorship Status
4+ Sponsors
Drivetrain
Mecanum
Materials
3D-Printed Plastic, Wood, Custom Metal Parts
Product Sources
GoBILDA, REV Robotics, AndyMark, Studica Robotics, Misumi, Swyft Robotics
Odometry
GoBILDA Pinpoint
Sensors
No Sensors, Limelight 3A
Systems
Turntable, Shooting Mechanism, Wheel Roller Intake
Programming Language
Java (OnBot or External IDE)
Development Environment
Android Studio
3rd-Party Tools
Other
Vision
AprilTag Localization
Our robot is suprisingly simple. It does not feature any special indexing or unusually difficult to assemble mechansims. This has allowed us to rapidly develop our bot and make it consistent.
We aim to perform outreach by hosting events within our organization, because it is built for the community. Possible other outreach includes visiting local schools, hosting career fairs, etc.
One element of our software that is particularly advantageous is the modularity that it provides. This allows us to quickly make changes such as adjusting auto paths at runtime using Marrow, or quickly modifying commands before a match.
We will be attending 3 qualifiers in North Carolina, and we will also be attending state champs hopefully.
We have discord as our main method of organization. We use forums to divvy up tasks and assign collaborators. We manage time by doing as much computer work (like coding, cad, etc.) outside the meeting times, and using whatever time we can scrape together to test on the actual robot instead of slowly building the code within a short timeframe.
One strategic element that our team is employing is prioritizing simplicity. This allows us to have less faults, more consistency, and overall better chances at performing well at competition.
Our design philosophy is fail fast. We tend to explore various design types and upon discovery of any issues or problems being identified by other teams, we reiterate. For example, our initial design used a spindexer; now, we decided against it for more simple execution and also due to the fact that many teams noticed it wasn't as valuable in terms of points.
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).