|
Re: Joystick doesn't update, motors don't drive until button press
I would, but another team member just figured out the problem. We had a command code that woudl manage our SmartDashboard, and it had a 'require drive subsystem' type line that would interfere with the Robot drive method. And pressing the button interrupted the smartDashboard and allowed the drive to continue, starting the drive. This is consistent with the fact that before the button press, the drive method was called exactly once (instead of continuously).
|