I programmed an autonomous selection program on the pre_auton section of the competition template because I wanted it to run before the autonomous started so my team could select an autonomous before the match started. Something messed up because the robot stopped moving as soon as I implemented the code into the robot brain. The only code so far I had was a code to change the color and text of buttons. It was merely a graphical program. Our team had not programmed autonomous yet so we could not implement the code to change autonomous. I could not figure out the problem because nothing in the code could effect the motors in any way. The only thing I theorized that might be effecting the motors is the wait function I put in. I told the program to:
before being able to change text and color again because I had the problem of the colors and text switching a thousand times after I tapped it once. That is the only way that I could think to stop that problem was to use a wait function. I discovered that my motors would run if I held the joysticks at a position (it can be any position) and then tap a button. The robot was locked in that motion until I held the joysticks at a different position and pressed another button. Then the robot would be locked in the new motion. I put the joysticks at rest and then pressed a button. The result was that the robot stopped.
Does anybody know how to fix the problem?