[linuxboy]

There are a few places I've seen this. The first would be when Debugging using java you need to connect to the debugger before it will run Robot Code. By far the most common reason for this is something went wrong with the Deploy eg The network cable came out during the upload or for some reason the compiled image that is sent to the cRIO is corrupt. I believe that exceptions in C++ may also cause the Robot Code to stop running. If I remember correctly when things are working correctly the Robot sends a heartbeat saying Robot Code is running. If there is an exception that may crash the code to the point where the heartbeat is no longer sent.

In C++ good places to look are "unresolved symbols", basically things declared in headers that aren't in implementation files. I believe that unless you are debugging the code won't run if you have unresolved symbols.

As a rule a good place to look for exceptions is anywhere that you may be using an index as those can result in index out of bounds errors.

Another good thing to do is keep the NetConsole for the cRIO open. This will tell you what is going on, for example if the Program that you uploaded is corrupt it will say something along the lines of "Could not load FRCUserProgram"

Good Luck!!