Resources
Our documents and our code, in one place.
Our documents and our code, in one place.
Nothing matches that search.
How the team is organised: roles, expectations, how we run meetings and how decisions get made. The document we hand new members.
Logo usage, the colour sheet, typefaces and the rules we hold ourselves to. Useful if you are a sponsor putting our mark on something.
Our FTC Robot Controller workspace for Android Studio: the mecanum drive, three-wheel odometry, Pedro Pathing routines and the Limelight vision stack.
The repository behind our starter bot. A smaller, simpler codebase than the competition robot, and the better place to start reading if you are new to FTC.
The source of the site you are reading, tests included. Hand-written static HTML on GitHub Pages, no framework, if you want to build something like it.
Everything above is public on purpose. If you are a rookie FTC team, these are the ones worth your time first, and we are happy to answer questions about any of them.
The engineering portfolio shows the reasoning behind each subsystem, which is worth more than the finished source. Judges reward the reasoning too.
The starter bot is deliberately smaller than our competition code. Get a robot driving from that before you try to read the full workspace.
We were a rookie team recently enough to remember it. Portfolio structure, CAD, Pedro Pathing tuning, or how to approach a sponsor: kclmsftc@gmail.com.