[vinnie]

We had a problem with "phantom autonomous" at a scrimmage yesterday. In our case, it was because we did not reboot the robot after previously driving it, and since our robot was driving when it got disabled, the cRIO held the last PWM values and started sending them again as soon as it was enabled, even though there was no drive code in autonomous. We fixed our problem by sending a drive command of 0 during autonomous to make the motors stop.