Communication issues
 

This one has really been baffling us. Quite often when we attempt to connect to the bot using the DS for testing and code deployment, we are able to connect to the Gaming Adapter onboard the bot, but not to the cRIO. It seems to happen randomly, which to me suggests a weak connection between the gaming adapter and the cRIO.

However, our electrical team assures us that the cable we are using and the connectors are good, so I'm posting this issue anyway. Could it be anything besides the cable or connectors, and if so, what would the issue be and how can we fix it?

Re: Communication issues
 

Is the gaming adapter plugged into the cRIO port 1 or 2, and is it a standard CAT5 cable?

It should be in port 1, and it should NOT be crossover.

Re: Communication issues
 

try makeing sure everything is connected to the router then reste the router(power off for 15 sec) for some reason any device that is connected to the linksys router doesnt work right if it isnt connected when the router boots... thats what gave us troubles at least

Re: Communication issues
 

There's a known issue on a cold powerup. Sometimes the WGA takes longer to boot than the cRIO. If the cRIO finishes its network configuration before the WGA is ready to look for network activity, some routing information doesn't get set and the link to the robot doesn't get established. (There is not yet a software update to work around this.)

If this happens again, reset the cRIO only (there's a tiny reset button near the serial port) without removing power. The WGA will already be operating and the network configuration will succeed.

If that doesn't fix it, you probably do have either an intermittent connection or a faulty WGA.

Re: Communication issues
 

Thanks for the help. I'll make sure that everyone on my team knows this in case it comes up.

Re: Communication issues
 

The new DS update that was just posted should work around this issue: http://joule.ni.com/nidu/cds/view/p/lang/en/id/1535

Re: Communication issues
 

we also found out that you need to update not only the drivers station, but a new labview from this week. worked for our similar problem