Drivers Station Anomaly

[protoserge]

I don't know if you have this covered, but check the following anyway:

• on-field IPv4 set to use DHCP
• IPv6 disabled
• Public domain firewall off.

I would recommend always relaunching the Driver Station software.

You have vaguely described the scenario you witnessed. Any further help will likely be limited unless you describe your observations in more detail or attach a copy or screenshot of your driver station log.

[messer5740]

This issue occasionally happens with our operator console. The problem usually is just the lag that is accociated with the long run time. Shut it down after every match and boot it up and reboot the code each and every time before each match to ensure the least laggy control of your robot. I hope this helps because it sure makes controlling robots difficult if the commands only work after a minute after you press a button or move the joystick

[SteveGarward]

Greta

First, great job this weekend! It was great working with you guys in the eliminations.

This is most likely Driver Station related and not code. Having said that, feel free to PM me, and we can help look over your code to check for any potential issues (we use Java too).

I will echo the previous replies, that it is best to restart the DS software for each match. This used to be more of an issue in the past, but it can never hurt to have a clean slate each match. We have been told by FTA's in previous years to do so, and now just do it routinely.