No Robot Code

[azureflame241]

The cRIO that were using is imaged in LabView and we have the code loaded onto the cRIO, we are able to connect to the cRIO but it says no robot code in the driver station, can some one help us with this problem?

[Alan Anderson]

"No robot code" means that the Driver Station cannot communicate with a robot program running on the cRIO. If you are connected and the "Communication" indicator is green, then it means no code is running on the cRIO.

It can happen if no code was loaded before the system was booted. How did you load the code onto the cRIO?

It can also happen if code is present but the NO APP switch is turned on. If you are using an 8-slot cRIO with physical switches, make sure NO APP is OFF. If you have a 4-slot cRIO, use the imaging tool to make sure the virtual NO APP switch is off.

[eruiz22]

Hey my team had the same problem this year. I found that restarting the robot after building and deploying fixed our problem.
I think it's worth a try

[Alan Anderson]

Originally Posted by eruiz22

Hey my team had the same problem this year. I found that restarting the robot after building and deploying fixed our problem.
I think it's worth a try

If you use the Run As Startup command instead of Deploy, the robot will be rebooted as part of the process. There's never really a good reason to use the Deploy command in LabVIEW.

[azureflame241]

We used LabView to load the code on the robot, we used Robot Main.vi to load on the cRIO

[Tom Line]

Originally Posted by azureflame241

We used LabView to load the code on the robot, we used Robot Main.vi to load on the cRIO

Using robot main does not permanently place a copy of the compiled program onto the robot.

To do that, you need to use the project explorer, move to the bottom item "Build Specifications", and click the "+" symbol to expand it. Right click on the item that was revealed, then click "build". Once the build is complete, right click again and click "Run as startup". This will place your compiled code onto the cRIO so that it executes whenever the cRIO is powered on.