Waiting for RT cRIO to respond.

[Team3763 Adam]

While trying to deploy NEW code onto the cRIO, we stare at the message "Waiting for RT cRIO to respond" for 10+ miuntes. This is a reoccuring problem, and we can't figure out why.

We can find the cRIO with the cRIO Imaging tool.

I've pinged both IPs with communitcation. IP on the cRIO (10.37.63.2) and IP on the Host Computer (10.37.63.6 subnet mask 255.255.255.0).

There are no issues with a Firewall.

Up until this point, we could run, test, and change code.

At one point during "Run as Startup" the communication was established between computer and cRIO and it started deploying up until it said deploying 2013_Build_Redo (The name of the project); and it then gave us the unforgiving message "Waiting for RT cRIO to respond."

Our cRIO is the NI cRIO-FRC, 8-slot.
*Could it be the computer? Our IP remains static 10.37.63.6 subnet mask 255.255.255.0
We've checked our ethernet cord, our voltage, and I've rebuilt the program from scratch, unable to deploy even basic code onto the cRIO even after re-flashing via the Imaging tool.

We've ordered the new NI cRIO-FRC II, 4-slot cRIO given out to rookie teams this year and plan to use this one as a backup if need be.

[Greg McKaskle]

The issue is in the known issues list. It has to do with the dashboard's SmardDashboard client being connected to the robot and the robot having deployed code that it is trying to abort.

The WPI SmartDashboard fix will hopefully be available next week. In the meantime, before deploying to a target that already has deployed code, close the dashboard and any other SmartDashboard clients that may be running such as the Java SmartDashboard or RoboRealm.

Greg McKaskle

[Team3763 Adam]

At the time the only program open was just LabVIEW, not the dashboard or any other.window period.

I'll be looking forward to the patch then

[Wildcats1378]

Yeah, we've been having this exact same problem.... It is really frustrating for us and halted a lot of our development on the robot

[Greg McKaskle]

Do you have any SmartDashboard clients running on any laptops connected to the robot? That is the cause of the "waiting" issue that was discovered near kickoff.

Greg McKaskle

[dsherw00d]

Same issues we are having. Sometimes closing the driver station takes a bit to free up the cRIO. We also found that if it doesn't work, highlight the cRIO target in the project window go to utilities and restart the cRIO. This will kill any open ports and allow the code to deploy. Watch the cRIO user port and wait for it to flash green indicating active traffic before deploying. Actually, I think the user light may stay solid green when it doesn't work. Most of the time, closing the dashboard a few minutes before deploying has worked.

[BitTwiddler]

Originally Posted by Greg McKaskle

Do you have any SmartDashboard clients running on any laptops connected to the robot? That is the cause of the "waiting" issue that was discovered near kickoff.

Greg McKaskle

Ohhhh, so that's what's going on. It's been driving the programming team nuts since last night after we put down some controls and indicators on the Smart Dashboard. I never made the connection.

[KissMySass3763]

I'm not sure if this is connected directly to the issue known, but the User1 light on the cRIO fails to light up, yet the light on the port that connects the laptop to the cRIO is constantly and rapidly blinking yellow, even when it is not plugged in. This came around roughly the same time as the previous problems.

[kylernoe95]

So what our team did is we reimaged our cRio with the 2013 cRio imaging tool, and then you want check whatever program you are using but after it has reimaged you want it to wait for it to find the cRio again.

[team3039]

Close the DS, click Restart cRio and close DS before it regains connection.