Migrating to REVLib 2025
Summary
The 2025 version of REVLib introduced a series of breaking changes from the previous year. These changes include:
An overhauled configuration system
Updated import paths
Renamed classes
For a more complete changelog, please see our 2025 beta release notes on GitHub.
Below shows how to migrate certain common tasks from previous versions of REVLib to the 2025 release.
Including the library and creating a SPARK object
In the 2025 version, all SPARK related classes moved to a spark package in Java and a spark namespace in C++.
In addition, some of the classes were renamed:
CANSparkMaxis nowSparkMaxCANSparkFlexis nowSparkFlexCANSparkLowLevelis nowSparkLowLevelSparkPIDControlleris nowSparkClosedLoopController
Configuring a SPARK
Instead of imperatively configuring parameters of the SPARK by calling methods directly on it and its auxiliary objects (sensors, closed loop controller, etc.), configuration parameters are set in a more declarative way through configuration objects and applying that configuration to the SPARK.
Retrieving a configuration parameter from a SPARK
With the new configuration system, parameter getters moved to a configAccessor field in the SparkMax and SparkFlex.
Setting status periods
Previously, setting status periods required the user to know which periodic status frame a signal belonged to. Now, status signals' periods can be individually configured, and REVLib will handle figuring out which status frame to adjust.
These values can be configured through the new configuration system.
Was this helpful?

