Hi, it is our third year using Arcade drive in FRC, and we have a problem…
in some of our backward turns, one side of the robot continues to get wpm values from the motor controller, although the driver stopped pressing the trigger (which is used to turn).
this causes our robot to spin undesirably…
this is what the driver does:
we use the controller’s joystick for driving and the two triggers for turns.
the driver pulls the joystick down to drive backwards and slightly presses the joystick for less than a second and then realeses it and continues pulling the joystick down.
Just a reminder that this only happens in backward turns and drive.
here are the logs that we made: Chassis Logs - Google Sheets
we checked the drivers of the controllers and their sensitivity and it seems like it’s not the cause for the problem.
we use the same code from last year (which it did work). We checked and it isn’t a problem with this year’s WPIlib update.
the command below is set as the default command for the Chassis subsystem