Re: Hot Goal Timing Issues
 

Do you play some sort of technical role for FIRST?

I don't know which event volunteers were informed about the problem. Several teams in the practice area were complaining about the delays and it sounded like they were talking to the field techs but we did not.

Our auto code executes a script file. Some of the commands are timed internally, for example "MMOVE 14.0 1.0" (move forward 14 feet at full speed). But there are many other commands in the script. To transition from one command (or line) to the next we send a message from the task that receives the DS messages (which only runs when a message from the DS arrives). On the practice fields and the Dallas field this worked as expected. On the field in OKC there were long hesitations from one command to the next. We display the commands as they are executed on the dashboard. I added timestamps and the responses were delayed by pseudo-random amounts of time on the field. It was very late in the event that we diagnosed this. Our priority was to remove the dependency which we did by isolating the script engine in a task that required no input from the DS other than the state changes. Then we changed our auto on Saturday afternoon to simply pull forward a few feet (had alliance partners with reliable 2-ball autos) thus we recorded no valuable data.

Re: Hot Goal Timing Issues
 

Yep. The sounds are way out of sync as well. We're actually on the other half of the field from that video, and we shoot our last ball at 9 seconds. The 'auton over' sound routinely goes off before we've fired the ball, but the lights stay on and we score every time.

We've turned off vision entirely. It's not worth the guessing for 5 points.

In addition, there was usually 1-2 seconds remaining on the game clock at the end of teleop when the robots were disabled.

Re: Hot Goal Timing Issues
 

We also ran into his problem at the Granite State and Northeastern districts. Our autonomous detects which goal is hot at the beginning of autonomous and uses that to decides whether or not to wait to score.

This field bug meant that we couldn't tell teams that we could consistently score in the hot goal. Our robot only goes fast enough to reach the goal and score in just under five seconds, so it is not possible for us to wait a second before detecting the goal.