Control System Beta Testing and Usage Reporting

Default FIRST Image

The Control System software teams have been hard at work over the summer making various improvements and bug fixes and are about ready for teams to jump in and start testing. The testing will again be facilitated using a public GitHub project. The GitHub project is live now, and software is expected to be posted within the next few days. 

2024 Usage Reporting

One of the most helpful tools we use for robot rules and technical decision is the data collected from the Control System “Usage Reporting”. 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. Data from the 2024 season can be found in this zip folder. 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. 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. Language and Framework report what was used in the last recorded match.
  • A bug in the reporting resulted in many of the newly added items not being recorded properly. These have been omitted from the data.