You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deadband: A set of operator inputs that are ignored as 'junk'
All joystick controllers have a small area "near zero" that is not actually zero, but we should treat as zero. When the joystick inputs are "almost" zero, the operator interface (OI) code should tell the robot they are actually zero.
Right now, that is handled in the CheesyDrive class in DriveTrain object, after passing raw stick values in from the OI. That's dumb, because the joystick will always need to have a deadband filter applied, no matter what part of the code is pulling the value, so the OI for the gamepad should handle this immediately instead of rewriting deadband code every time we use a joystick input.
The text was updated successfully, but these errors were encountered:
Deadband: A set of operator inputs that are ignored as 'junk'
All joystick controllers have a small area "near zero" that is not actually zero, but we should treat as zero. When the joystick inputs are "almost" zero, the operator interface (OI) code should tell the robot they are actually zero.
Right now, that is handled in the CheesyDrive class in DriveTrain object, after passing raw stick values in from the OI. That's dumb, because the joystick will always need to have a deadband filter applied, no matter what part of the code is pulling the value, so the OI for the gamepad should handle this immediately instead of rewriting deadband code every time we use a joystick input.
The text was updated successfully, but these errors were encountered: