Quote:
Originally Posted by jacobhurwitz
I don't think having the robot stop if you press nothing is allowed. R65 says you can't use changes in the signal state to encode longer messages. I think pressing/releasing a button is a change in signal state, so you can't use that as an additionally message.
|
Let's apply the "same thing every time" litmus test to this one. Call the command "drive for 500 milliseconds and then stop". Your robot will do that every time you press the button. As far as I can tell, you are allowed to interrupt an action in progress with another button press. As such, if your robocoach is madly mashing the button, then the robot will continue going. When he stops, the robot stops. The robot performs the same action every time you press the button... you just don't happen to let it complete the action. This sounds legal to me.