Quote:
Originally Posted by billbo911
Hi Greg, I don't know what information you have on this already, but I saw it at least 3 times. I was working as an FTAA at CC. Every time we saw the unexpected estop, it appeared in Autonomous right around .006 -.007 seconds into the match.
The theory was, it was somehow cached by the DS prior to the start of the match, and sent to the FMS as soon as the the Autonomous Enable packet was received.
The workaround we used was to have each team restart the DS software as soon as they arrived at the field to connect and set up. As far as I am aware, no erroneous estops occured when this process was followed.
|
Thanks, Bill, for the information. Quick clarifification that the Cheesy Arena logs show that no robots were e-stopped and this manifested on the FMS side as lost robot communications. Possibly a bug in the driver station software. The fix Bill describes worked well throughout our event.