[sdaustin]

MAC filtering probably isn't the issue. I'm told the FMS does not send any traffic directly to the cRIO. It's all commands to the DS, which then in turn sends commands to the cRIO. We tried two different DLinks and a different DS.

I can't recall exactly what was displayed on the DS, other than that the uppermost indicator in the lower-left pane ("Comm", I believe) simply never turned green running under FMS. Without Comm, the robot battery voltage was probably not being displayed. The DS was usually on AC. When we swapped out the cRIO, we continued to use our existing modules and didn't change any of the wiring to/from them. Given that everything worked fine if the DS was hardwired directly to the cRIO or thru the DLink, or if we used a different cRIO, I think that rules out the battery and modules.

What's the RSL?

Autonomous wasn't an issue for the first five matches -we carried the robot off the field before they started. My recollection is that it was disabled for the first few matches w/ the new cRIO, then we enabled it. It was enabled for all of the Waterford competition and by about the 6th match our kids had it working very well, following the lines & hanging an ubertube. Woo Hoo!

This smells like an OSI Layer 1 or 2 network issue in the cRIO ethernet port to me.

Anyway, I have a high level of confidence that the NI application engineer working on this will get it resolved to our satisfaction soon. He has been truly awesome.