[Greg McKaskle]

The driver station (DS) has high level diagnostics on the left that summarizes communications, code, and stop button. Additional information, especially about communications is provided on the Diagnostics tab. This pings each of the elements to help tell what is wrong with the comms or USB elements.

If No Code is the message on the DS, and everything else is fine, I'd probably use the development tool to run the code, perhaps look a the serial output, until you believe that your code is running that way. One possible issue with the code starting could be the language that the cRIO was formatted for. The language selection determines the libraries and some startup settings. The Diagnostics tab displays the cRIO language settings near the version string. The updated version of the DS does anyway.

Once you have code running in the development environment, then you can focus on deployment.

Greg McKaskle