Quote:
Originally Posted by David
You could have a few status lights on the robot to tell the robocoach what programming set he had on.
If this rule is interpreted literally you would have to have, for example, a button to turn left then a button to stop turning. I believe this rule is intended so teams cannot change code "on-the-fly" during a match (i.e. downloading new code through some remotely operate serial cable). I do not believe this rule prevents cycling through commands like Chrisms and others have stated. Also if your team had PID or traction control and one of your commands was drive straight, then, if interpreted literally, you would have violated this rule (the robot is dynamically changing motor speed depending on the robot's speed).
|
I believe that it is pretty apparent that the intention of the rules is to only have
four commands ever sent to the robot. The GDC went as far as to state this in three separate rules <G01> <R65> and <R69>. I think the best way to interpret this rule is by the 3x5 card where you have to state what the four commands are, if you can write the commands in such a way that there are only 4 commands, i would say it is legal.
for more information i would suggest looking into this topic
http://www.chiefdelphi.com/forums/sh...&highlight=R65
specific rules are listed in my previous post on this matter
http://www.chiefdelphi.com/forums/sh...4&postcount=25