Beta Testing cRIO Tasks

We installed our cRIO (I am loving its new size) and reimaged it with CAN settings since previously (for Task 5) we got our CAN Jaguars working. It successfully reimaged and we pushed down our code. The driver station said it had code but when we enabled our robot, the Jaguar lights continued to blink and the robot would not run. We had the following error in the diagnostics tab -

ERROR <Code> -1073807246 occurred at NetComm_CAN_Send.vi:3
VISA: (Hex 0xBFFF0072) The resource is valid, but VISA cannot currently access it.
Along with...
ERROR <Code> -44087 occurred at NetComm_CAN_Send.vi:11
FRC: JaguarCANDriver timed out waiting to receive a response from a Jaguar.

So we quickly changed out our wiring for PWMs and reimaged with non CAN settings. That was successful, we pushed code and the robot worked well. Just to make sure it wasn't an anomaly, we tested CAN again with the same result as before. Someone else had this error and made a post within the Hardware Section.

We also noticed two other things. We are unsure if these two are related to the new imaging tool or the cRIO II. The cRIO switches settings appear to be different, before all the switches were in the same position and the new setup is picture in the attached. Also, normally after you reimaged if you left the tool up (like you were planning to reimage again), once the cRIO was found it would show the green module spots. For this test we noticed that if you left the tool up the module spots would stay blank. Only after you closed the tool and reopened it would the modules show in green.