Quote:
|
Originally Posted by Eldarion
While ours did not die completely, every now and then (actually about 50% of the time  ), the autonomous_mode flag will be cleared for an instant and then reset, forcing the auto mode code to restart from the beginning. We are using the dongle, and the error does not appear to be in our (custom, not Kevin's) code. Has anyone else seen this? |
There was another team at BAE that had similar symptoms to yours - where they had different behavior off then field then on the field.
There was a "feature" in last years field controls that put the robots into Operator Control mode for a short time before starting Autonomous. I don't know for sure, but have heard that the problem is still there this year. There was some work put into WPILib and EasyC to try to make them work in this environment since they actually yank the program out of the Autonomous or OperatorControl functions when the field state changes.
I helped a team track down a problem that they believe was caused by this. They had a motor that would start moving to some position in Operator control mode. After the motor was started, the program then started running the autonomous code that wasn't checking for the motor position. So it ended up "running away" since there was no reason to check it - it wasn't supposed to be moving.
They ended up making a bunch of changes at the same time, but they thought this was happening to them.
You might want to verify that this isn't happening to you - if there are some variables that are being modified in operator control that your autonomous code is depending on not being changed, it could cause all kinds of problems that you would only see when on the actual field.
You could simulate this by starting your robot disabled & operator, then enable for a second, then change to autonomous. This can be done in the pits teathered.