Loss of this information is expected, as we are only using a relative encoder to control the climber actuator.
Some options for enabling climber actuator position to persist through robot reboots:
Assume that code boots in a state where robot has been properly prepared for a match, and actuator is at kHomePosition
Repeatedly publish current position to RobotPreferences, and set the position using the value from RobotPreferences upon code boot. This is similar to what we do with the swerve module absolute encoders.
Loss of this information is expected, as we are only using a relative encoder to control the climber actuator.
Some options for enabling climber actuator position to persist through robot reboots:
Assume that code boots in a state where robot has been properly prepared for a match, and actuator is at kHomePosition
Repeatedly publish current position to RobotPreferences, and set the position using the value from RobotPreferences upon code boot. This is similar to what we do with the swerve module absolute encoders.