[X-Istence]

I am posting this question, late. What we are seeing with our robot controller and operater interface is that at times the OI will get bad data from the RC, and the RC will get bad data from the OI.

When we turn the robot on, sometimes it will give us a random RLOD, this is normally fixed with a simple power off and on.

The other time is when everything seems fine, but randomly the belts on our robot will start running, or it will start running in circles, even when on the OI the FlightSticks are unplugged, and thus it can't be the fact that the joysticks are sending data. Also, on the OI all the lights will go on, as in all the extra LED's under the Robot Feedback header, when not all of them should be lit up. If I am connected to the programming port, I will see that the output appears all scrambled, and I get random crap thrown to my terminal window.

I am thinking there might be a problem with the interrupt that it is not saving enough data personally, but I don't understand why this would cause it to die upon startup. luckily for us it is immediatly evident, according to the CMUcam thread there are others with the same problem, so my team is not the only one fighting with the code at the moment trying to get it to work without any problems.

Kevin Watson, you posted elsewhere something else to add to save in the pragma before the InterruptHandlerLow, maybe that could help us?

Any other things I should do? I am going to email IFIrobotics and see what they have to say about this problem, besides that I am wondering how we are going to go through the competition if our robot is malfunctioning.

Bert JW Regeer
Senior Programmer