Originally Posted by frcguy
...we're going to be using Cheesy Arena at Capital City Classic. Do you have any more details or theories? I know about the e-stop bug, but this is obviously separate.
Originally Posted by Thad House
The issue Code Orange had with their robot was related to a timing issue in Cheesy Arena during autonomous. There was a specific WPILib timing function that was not receiving the right inputs from the FMS (the GetMatchTime function). Most cases I've seen that use that function use it during teleop to detect the end of the match, which was correct. However, this has been fixed in Cheesy Arena, so Beach Blitz and Capital City Classic should not have this issue.
Regarding the e-stop issue, we are still working with FIRST to try and detect the cause and institute a fix. Our plan during Beach Blitz if we see it is to immediately replay the match, as the issue pops up right at the beginning of the match.
At this time, the e-stop issue appears to be manifestation of the DS being in "FMS Lite" mode and not having the space bar estop disabled. Until we have a solid answer as to the root cause, and/or a fix for the issue, CCC will be implementing the same workaround we used at Chezy Champs. Specifically, teams will be requested to restart the DS software before each match. In addition, we will also take the approach that Beach Blitz is using of immediately restarting a match where the estop issue pops up.
These are minor adjustments, but for the integrity of the tournament, we feel these measures are necessary.
BTW, if you were not aware, the new binaries for Cheesy Arena were posted 2 days ago. They include all updates from the start of Chezy Champs until now.