[Mackenzie W]

Team 1305 also had a similar CRIO issue at Waterloo. It worked perfectly fine the first day, but on the final day it suddenly stopped working when connected to FMS. It worked perfectly in our pit as well in all of the modes, none of the volunteers or other teams could replicate the problem off of the field. We solved it by switching out the CRIO as well, and were able to compete in our next two regionals without issue.

To any teams who have this issue and need a quick fix, reboot the CRIO in the driver station before the match starts while connected to FMS. In our driver station logs, we determined that the CRIO never entered disabled mode, somehow dying in the middle of starting up, no matter what the code was. By rebooting the CRIO, it somehow let the robot enter this disabled mode, and therefore function normally.

We have no clue what triggered it to fail though, we only left it overnight.