Quote:
Originally Posted by Pat Roche
The code was a simple drive forward for x seconds then do nothing for x number seconds (sorry I cannot recall the exact number of seconds but it was approximately 19). There was nothing executing beyond that. We tested this during our system check field side. It worked 50 matches in a row successfully. It was the only autonomous code we had in our robot. It makes no sense that after match 50+X all of a sudden a timing issue like that would begin occurring without changing something in the software.
|
Are you using SimpleRobot or IterativeRobot?
Also, how are you implementing the "do nothing for 19 seconds" part? Timer.delay()? Thread.sleep()? wait()?