[lscime]

We've had similar issues in the past. Our current understanding (after talking to NI and doing our own testing) is that sometimes the cRIO is "too busy" running already deployed code to communicate with the computer properly. We came up with a solution that has worked well for us and other teams that have tried it. The steps are listed below:

1. Turn off your robot.
2. Flip the "no app" dip switch on the front of the cRIO. This tells the cRIO not to run the code on startup.
3. Turn on the robot and wait for it to boot.
4. Build and deploy your code.
5. When LabVIEW prompts you to restart the robot - flip the "no app" dip switch back to the original position and finish rebooting the robot.
6. Now you should be ready to rock and roll.

Hope this helps,

-Luke