[mwtidd]

Originally Posted by Joe Ross

It's documented in this years documentation. http://wpilib.screenstepslive.com/s/...g-at-the-event



As documented at the link above, the driver station netmask must be 255.0.0.0 or else it won't connect to FMS.

Another important thing to note is that if you specify a the default gateways as 10.TE.AM.1 it appears that all traffic goes to the fms. This caused for significant delays to be introduced only when we connected to the field as data was being passed from the Rio to the FMS, then from the FMS to the Kangaroo, then from the Kangaroo to the FMS, and finally from the FMS to the Rio. In reality it was probably also going through the Driver Station as the FMS does not connect directly to the robot, but short of doing a traceroute I couldn't tell you definitively.

In reality this traffic should have been able to stay local and should not have been subject to the bandwidth limitations the FMS imposes.

In windows you can leave that gateway empty and be all right. On the rio, it can be configured via the web dashboard and should probably be set to 0.0.0.0 as suggested by the images in the screensteps document you listed.