Our team’s programmers-in-training are having some difficulties getting our VEX robot to follow EasyC programs. Our biggest problems come when using a program created from a template: it’s supposed to have a short half-second initialize before it runs for 20 secs in autonomous, afterwards going to operator control. It seems that the robot is randomly choosing parts of the code to follow, e.g. in one run it might follow the whole code, but in another, as is most often, it will skip straight to operator control. There’s nothing wrong with the code–it was working very well one day, and then the next it was once again refusing to run in autonomous. We’ve tried to download just a simple autonomous code onto the robot–that only works half the time, as well.
Anyone experiencing similar problems, or have any idea of what could be wrong with the robot (specifically, not just that it’s probably broken somehow–we already know that) ?
Intermittent reception from the transmitter can cause it to behave erratically.
That could happen when the battery contacts loosening up or the battery needs charging. The battery connector on the transmitter side open up over time and can be closed up again with a small blade screwdriver.
Uh…
I’m not too sure why. If you could post some of the code here, that’d help debug your code. But if you’re sure that there is not problem with the code
then I would try a different micro-controller.
Are you using one of the provided compeition templates? If so, be sure there are no jumpers in interrupts five or six, as these will cause the robot to switch into either only autonomous or operator. As others have said, check to make sure your radio connection and power are good.
If you post your code, it will be much easier for everyone to help you, because looking in from the outside, it seems like a code error. Just to be sure, redownload the Vex master code.