Driver Station slow to connect to roboRIO

[Crossle86]

We are consistently seeing the connection time driver station to roboRIO, after roboRIO power up, to be one minute plus. This seems excessive compared to last year. Anyone else see this or have a comment?

[Greg McKaskle]

Is this over wifi, ethernet, or USB? It may be useful to do all three and report the timings.

Greg McKaskle

[Crossle86]

At this point, the connection "delay" is in the time the driver station PC takes to detect and reconnect to the robot radio when the robot power is cycled. I'm doing more testing, but it appears that once WIFI connection is established, the time the DS software takes to connect to the roboRIO is reasonable.

[Greg McKaskle]

I haven't tested it with this year's settings, but in past years, I think I measured the DLink to take 51 seconds to come up and either bridge or build the AP. I believe with other settings, that modified the Mac address cloning, the time could be in the thirties.

So once you understand where it comes from, you can control it and should be able to improve your productivity.

Greg McKaskle

[Crossle86]

What settings are referring to?

[Greg McKaskle]

I'm not looking at it now, but it was a DLink setting that affected whether bridge mode would clone the MAC address of one of its subnet devices or not.

Are you in bridge mode or AP? I may be able to time it later today.

Greg McKaskle

[Crossle86]

AP mode. Team meets later today. I will look at the router for the setting you mention. Thanks for the clue.