Update 6

[Jeremy_Mc]

Originally Posted by briholton

Sensors are not controls. How in the world can you be certain of how your program works without having motors attached? Particularly for rookie teams. How can you see how fast a line driver is going to work - how choppy it will be? anyone who writes a computer control program without testing it is doomed to failure - that is SOP for any app. If you don't believe me, try writing a C program that is over 100 lines and don't debug it. If you can get it to work first try - and it controls everything the way you expect, well, you are a DARN good programmer- better than anyone on a rookie team that we are trying to support.

They give you the code to track the beacon. All you have to do is use the dashboard to make sure your motors are turning at the right time. Move the beacon around to make sure the sensors are giving the right input and outputting the right PWM's.

I'm not saying don't debug it. I would be a fool to say that. I'm saying there are other ways of doing everything and there is another way of testing it other than using a victor/motor setup.

Of course, this is all relevant only if you don't have time to test it beforehand (which if you're REALLY on the ball about it and serious about getting a GOOD auto program done, you will be).