Quote:
|
Originally Posted by Jeremy_Mc
[long post]
You don't need victors and motors to test...
Since you have THAT much time to spend on programming, you SHOULD be able to get a dynamic autonomous program (such as the beacon tracking or line tracking) code going that's pretty independent of things like motors in the long run. All you need for that are sensors (which might be included in the controls? That may be something that FIRST needs to clear up...) ]
|
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.