Problem connecting to the CRIO

[Greg McKaskle]

The HW team is correct. The DS voltage will be incorrect, and you will need the module and breakout and jumper in order to pass inspection, but you don't need it right now.

My suspicion is that you have a great deal of Diagnostic errors being reported at the DS. If you can change the mode of the robot at the DS, you may find that one of the modes produces less errors and will have a better shot of deploying. If you fix the code issues that are causing the errors, the deploy issue will go away.

Also, you do not need to reimage the cRIO -- almost ever. Teams do this all the time, and I'm not sure why. The file system is very robust, and if not corrupt, why do it? You may sometimes need to turn on a setting such as the no-app switch or change the CAN or other settings.

Greg McKaskle