Quote:
Originally Posted by FRC4ME
You guys seem to have a lot of issues getting stuck in autonomous mode. Moreso than other teams. Perhaps you're doing something unusual in autonomous that is causing problems with FMS. I would be interested in seeing your auto code if possible (from either 2010 or 2009). Not because I'm saying that your code is the problem; if the problem is FMS, though, your code seems to contain the trigger that reproduces the problem.
|
We had very few teams have this happen at VCU, and it just so happened that 134 experienced this problem in back-to-back matches. 134 communicated with the FMS before beginning the match, but would not move in the tele-operated period, and seemed to still be stuck in their autonomous program although FMS had successfully placed 134 into tele-operated. As FRC4ME said, this could be a programming issue, although I can't say for sure. Can anyone on 134's programming team shed some light on how they got working again?
Quote:
Originally Posted by Zach Purser
When you say you did not have working code, do you mean that the robot wasn't working before you put it on the field, or are you saying that the reboot somehow affected your code?
|
The robot did not have working code loaded onto the cRIO before beginning the initial match. I referenced the re-started match simply because that is the match this happened to occur in. All other robots in that match rebooted their robots before the restart, and worked properly for the duration of the re-play.