Continuing on from Collin’s REEFSCAPE by the Numbers post, another source of data about the season comes from the “Usage Reporting” data collected by the control system. This feature tracks what WPILib objects are created in each team's code and reports that data back to the field when the robot is connected. In addition, we also have some information to share about some new legal devices for the upcoming season.

Usage Insights

While we will continue to analyze the data in various ways over the coming weeks and months, here are a couple initial insights from the Usage Reporting that might drive change moving forward:

• Of the 119 teams that directly used the KitBot code templates, 113 of them were in Java. We’ll take a look at whether it makes sense to continue providing KitBot code in multiple languages.
• A handful of devices requiring explicit legality reported 0 usage in 2025 including Jaguar, Mindsensors SD540, Nidec Dynamo, and DMC60 motor controllers. We’ll look into removing these from the rules to reduce the size of the list.
• Among third party libraries with reporting, PathPlanner (2119 teams), PhotonVision (655 teams), AdvantageKit (606 teams), and YAGSL (520 teams) are all very popular. We’ll continue to look at how we can include these libraries in documentation and ensure they work seamlessly with WPILib.

Usage Data

Data from the 2025 season can be found in this zip folder (file automatically downloads). Some notes about the data:

• The data has been anonymized. Team numbers have been removed and the data has been re-sorted so teams are not in order by team number. A number of names of Network Tables clients have also been obscured in order to not be revealing, either directly or via GitHub code search.
• We can only track the objects teams create in code. If a team creates extra motor controllers that aren't on the robot, they will still be captured by this system. If a team creates motor controller objects of the wrong type, that wrong type will be captured by this system.
• Some objects naturally result in double counting (e.g. Encoders use Digital Inputs).
• Counted objects and TRUE/FALSE show the largest number of any given object used in any one match (i.e. if a robot plays match 1 with 3 Encoders and match 7 with 2 Encoders, 3 will be reported). This means that if a team switched motor controller types, or IMUs, or anything else during the season, the sheet will show numbers for both devices. Items like Language, Framework, and Dashboard report what was used in the last recorded match.
• The Quest and Limelight data is inferred from NetworkTables client names. These may not capture all uses of these devices.

New Legal Devices

We also have 2 new devices to announce. Over the past couple of years all new legal devices have typically been announced at once in the fall. This was driven by a combination of when suppliers were ready, as well as a desire to keep this information more centralized as opposed to spread over multiple posts throughout the offseason. When a supplier reached out wanting to release a device much earlier, we ultimately determined that the benefit of teams having these devices earlier should win out over centralizing the information.

Redux Robotics Nitrate

The Nitrate is an affordable and versatile standalone motor controller from Redux Robotics. It features advanced features like a secondary high-performance bus for auxiliary sensors, out of the box sensor fusion, built in PID and motion profiling engines, high rate odometry, and much more. More features can be found on this Redux Robotics product page.

Redux Robotics Cu60

The Cu60 is Redux's high performance brushless DC motor. Featuring a standard 2-inch bolt circle and 8mm pinion shaft, it is ready to be dropped into any existing application to provide a high-power solution in seconds. It also contains a secure and locking hall cable and works out of the box with the Redux Robotics Nitrate motor controller. More information can be found on this Redux Robotics product page.