More RoboCoach Questions

[FRC449]

Our team would like to make the robot as autonomous as possible, but we are not entirely convinced of our robot's ability to sense and dodge other robots at high speed. Therefore, we are trying to use our RoboCoach commands as follows:

1) Drive Straight while button is pressed (for dodging other robots if necessary)
2) Drive Left while button is pressed (for dodging other robots if necessary)
3) Drive Right while button is pressed (for dodging other robots if necessary)
4) STOP the robot

We also have an autonomous routine, which would execute automatically if no button is pressed and which would drive the robot around the field. We would like the first three buttons to, when released, switch back automatically to the autonomous method. However, we would like the stop button to simply stop the robot and not go back to the autonomous method. To have the robot continue to drive around, we would press one of the other RoboCoach buttons, to make it temporarily drive straight/right/left, then release and have the release of that button make the robot to go back to the autonomous method. The functions of the buttons could also be described as follows:

1) Drive Straight while the button is pressed, and then continue the autonomous program
2) Drive Left while the button is pressed, and then continue the autonomous program
3) Drive Right while the button is pressed, and then continue the autonomous program
4) STOP, and then do not go back to the autonomous program

Would this be violating either the letter or the spirit of the rules?

[GDC]

The application described violates the intent of the Robocoach signalling rule. The contact with the button should be momentary. By having your command contingent upon the length of the button press, you have encoded a variable "how long" command in addition to the "what" command.