Quote:
Originally Posted by Pat Fairbank
It wasn't as obvious as you might think. It happened to us twice -- once during qualifications (Match 92), and once during eliminations (SF 1-1).
In Match 92, the autonomous appeared to progress normally, except that our second shot went wild (over the top of the goal, as if the shooter hood were in the wrong position) and the third ball failed to shoot before teleop started. 192 also failed to shoot their second ball, so my immediate thought from the stands was that autonomous was 1-2 seconds short for everyone.
Our code logs a bunch of stuff on the robot's file system every match, including teleop vs. auton and enabled vs. disabled states, so upon examination of the log file after the match we were surprised to find that the robot was in autonomous enabled mode for the first 1.5 seconds, then teleop disabled for 0.5, then autonomous enabled again for 8. We brought it to the attention of the FTA, and the match was replayed (it could be that they were able to correlate this with the FMS logs, but I don't know for sure).
Has anyone seen this at previous events? If not, seems like it's yet another new and exciting failure mode for FMS.
|
Not to derail the thread, but yes, we've seen something like it, where the driver station log showed about .5 seconds of teleop enabled in the middle of auto mode. When teleop starts, the robot automatically creates a file on the cRIO. After the match, when I went to check the file to see why the robot stopped driving forward too quickly and our 2 ball timing was off, I noticed there were two of these files, meaning we went into teleop twice in the match.
EDIT- The field also seemed to have a few other issues too, where people would have to constantly unplug then reconnect the timers/team displays/ethernet cables from the driver station control case at the blue side.