Vision Processing can't send data over FMS

[AWoL]

At our district event this weekend I had the same problem our first couple of matches but then I heard about the mDNS issue with NetworkTables and switched everything to static IP addresses, and that worked. I used the standard IP scheme from 2014, with the driver station on 10.2.25.10 and the roboRIO on 10.2.25.2, as well as our IP camera on 10.2.25.11. I put everything on the 255.0.0.0 subnet, and I believe that may be a requirement as I helped a team next to us in the pits that couldn't connect to their camera when it was on the 255.255.255.0 subnet, but could on the 255.0.0.0 subnet. As for the default gateway, I just left it blank on everything, as I didn't need it in my case; depending on your coprocessor setup, you might.

[mwtidd]

You definitely want to switch to use static IPs, that's a good starting point.

Please read this post:

http://www.chiefdelphi.com/forums/sh...3&postcount=16

I will not be able to 100% confirm it works until UNH this weekend, but I suspect you will see further issues if you use those gateways.

At the events, the gateway doesn't exist until you connect to the field. So in the pits, it doesn't attempt to route packets through the gateway. That being said on the field the gateway does exist, and as such packets are routed through that gateway rather than following the most direct path. It is my belief this causes the delays you see because of the way the FMS handles packets. We were seeing a 2 - 3 second delay with traffic that should have remained local in our case.

Basically I was where you're at after week zero, and now after Reading, I think I'm getting closer to a stable off-board setup.