Search Results

The PARTs library is a public Java / Gradle library full of utilities that we use for our robot. We've felt a need to make our own library as our amount of reusable code skyrocketed. It's hard to keep track of all code that's reusable and with the more modular...

Explanation & History A PARTs Unit is a simple and robust way to manage different used units across the robot code. The user creates a new PARTs Unit and specifies the starting value and its unit. After that, the PARTs Unit can be used anywhere to convert the ...

Explanation & History PARTs Preferences is a wrapper and handler for the WPI Lib Preferences feature. There are two parts to this feature, PARTs Preferences, and PARTs Preference. PARTs Preference is the object that handles the preference's type of data, and i...

Explanation & History 🔎 Keep in Mind This includes IPARTsSubsystem as it acts as the recipe for the subsystem. We have all these tools that we use but now we run in the issue of repeating all this code just to use them. We also want a good custom lo...

Explanation & History PARTs Command Utilities are used for commands in the robot project. Commands are actions that tell the robot what to do with its subsystems. Currently the only feature this class provides is naming our commands for logging and debugging r...

Explanation & History The days of Retroreflection are over, AprilTags are here. AprilTags are small QR-Code-like visual tags used in robotics. They provide low overhead, high accuracy localization for lots of applications. They are used in FRC for robot locali...

Explanation & History Since we've started working with full-field localization, we have had a need for a software defined field with the april tags and other field data. This base field is meant to be game-agnostic. It gets extended and that years AprilTags ar...

Explanation ⚠️ Warning This page only contains technical information. Last updated: April 2nd, 2026 This guide explains how to setup and include PARTsLib into your robot project. There are two ways to add PARTsLib...

Explanation & History Sending and getting data from the dashboard and other network devices requires a lot of tedious work which clutters up our code as we work and test. This utility of the library fixes that issue by making the proces extremely easy. Not onl...

Explanation & History When constructing a the right dashboard for competition, we found it difficult to easily control the dashboard in a reliable fashion. That's why we make PARTs Dashboard which serves as a helper to control the dashboard.

Explanation & History As our complexity of our robot grew, logging became important. Not only is it a good source of information for debugging, but the data can also be used for simulation of the robot. Robot simulation is an essential tool in programming and ...

Our robot, aptly named Big Bad Beanie, is our most complex bot in the last four years. This robot contains six subsystems, with many features. Drivetrain Shooter Intake / Pivot Arm Kicker Hopper Turret Features Shoot On The Move Shoot On The Move, or SOTM f...