[RyanCahoon]

What's your usage case? This would mean that the encoder values from previous matches would be restored when you switched on the robot. Perhaps this could be beneficial for debugging, but I don't know why you'd want to start off the actual encoder readings with the old values. I'm not debating so much as I'm just curious.

If you do want to do something like this, I'd recommend periodically writing the current encoder value to a file on the cRIO, then add code to read from that file when the cRIO boots up. Make sure to not write to the file every time through your main code loop as it will slow down your robot's responsiveness. You might want to start a different task if using WindRiver, or create a parallel while loop if using LabVIEW.

As far as I know, there's no other way to retain data through a power cycle.

--Ryan