Quote:
Originally Posted by wesleyac
...The main issue with the default WPILib one* (or at least the implementation that many team seem to use) is that it has a network read to figure out what auto mode to run at the start of auto. We don't want to use that, because we tend to do a lot of buzzer-beater autos (2016 two-ball, 2015 chokehold, 2014 three ball, etc). Having the round trip latency from a network read would have killed us...
|
I was thinking about this the other day. Isn't NetworkTables implemented so that it is a server running on the RoboRIO. Meaning that when a value is changed on driver station, the change is pushed immediately to the RoboRIO, and therefore, there would be no network latency from the RoboRIO reading from its local server? I'm not sure if I'm interpreting this correctly.
I second trying to find an alternative way to set your autonomous. Last year at worlds, we didn't run an autonomous in several matches because we couldn't get the SmartDashboard to connect before the match started. We will probably stick with it though because it's just the easiest option.