Quote:
Originally Posted by Mike Soukup
You better make sure that your drive team completely understands this limitation. At an event I was watching this weekend, the robots were enabled for autonomous, the foghorn sounded .5 second later, then the robots were re-enabled .5 second later. It was probably a mistake by the field operator who fat-fingered the stop button. My first reaction was "didn't that just mess up everyone's autonomous? What if they can only run autonomous once?" If you have the limitation that Chris mentioned, you'd better be sure your drive team raises a stink if that ever happens in your match.
Greg, I'll be happy if someone fixes the bug I reported a month ago. Can anyone else confirm that this is a problem with their setup? |
We've been doing it that way since 2003, so Ken is well aware. We decided a long time ago to keep it that way to avoid the safety issues Dave brought up (and most years we allow autonomous to run into teleop depending on the game so our auton scripts can often last longer than 15 seconds). They know that if a match is foghorned, they need to cycle the power to the robot. The FTAs complain a little, but they should expect that some robot reset is going to be necessary if they blow a match dead.
We have the same issue on our gamepad, but I really don't want the bug fixed at this stage because I don't want to re-write things now that we have our software working with the current limitation.