[Greg McKaskle]

It may be useful to connect a serial cable and see if anything on the console corresponds to the drops in communications.

As for the different LED patterns. Here is what they mean.

The communications LED is an overall litmus test indicating that the DS is receiving some number of valid response packets from the robot in a given second. If that is on, the no code LED means that the communications task is sending back packets, but nothing in the robot code is not providing updates to it.

The other lights under communications are approximately ping results. The first should mirror your link light for the DS NIC. The FMS indicates the FMS has sent control packets, and the others are a successful ping of that device.

So, if the Robot LED stays green, it pretty much rules out the low level networking stuff. It means that the DS can successfully ping the robot every few seconds. If it is going on/off, check to see that the cRIO is not rebooting. Ten to fifteen seconds is all it takes. You can watch for the yellow LED on the cRIO, or watch the serial console.

Once again, if you don't figure it out soon, I'd be interested in the output of the serial console.

Also, you say this works successfully on the laptop DS. What about another PC? If this were being caused by the DS, it would more likely show up as an unresponsive screen or as system watchdogs.

Greg McKaskle