We just finished our first regional and are preparing for our second. We had some weird issues with our drivers station that we are looking to fix.
Firstly, on one occasion we did not close our drivers station between practice matches. During the second practice match, our controls did not respond like they normally do. We did not see this problem again and were wondering if we could attribute it to not closing the drivers station between practice matches.
Secondly, we had a qualification match that was E-stopped about 30 seconds in. We did not close our drivers station. During the match, our controls again behaved oddly.
We were wondering if there could be errors in our code causing this. We use Java and the iterative robot set up.
If you can reproduce it, go to the gear in the Driver Station and press ‘view console’. This will show you all errors. If your code is broken, it will show here.
Also, wrt controls behaving oddly, make sure your connections are secure. We had some problems during one of our matches due to a loose connection.
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.
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:D
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.