Problem connecting to the CRIO

[silas13579]

Well the reimaging of the CRIO seemed to help. We just tried deploying a default robot project, and the CRIO was still not accepting it. Then we switched to our practice bot, with a different CRIO and a different ethernet and tried deploying our code, which didn't work, and then tried deploying a default project onto that, and that too did not work. They both were stuck in the same "waiting for the target (RT CompactRIO target) to respond."

[Mark McLeod]

Reimaging the cRIO works (in a brute force kind of way), because as a side effect it wipes out your user code that is responsible for the problem.

The No App switch (a DIP switch on the 8-slot or for the 4-slot virtual through the cRIO Imaging Tool) disables your user code when the cRIO is reset and is quicker.

[silas13579]

Alright so I'm getting confused now. What is the diagnostics screen? The part of the driver station? Because I'm not sure how it may be in our code, seeing as the default robot project didn't deploy either.

[Mark McLeod]

It's not the code you are deploying. It's the code already running on the cRIO from the previous deploy.

The Diagnostics tab on the Driver Station has a message window.
There are a lot of warnings that can obscure the real error messages, so copying and pasting all of them into a text file makes them a lot easier to look through.

You can also look at the Driver Station log from the Charts tab, in the lower right is "Launch Viewer."
You have to pick the latest log or two by date, then look at the Event List tab for error messages.