Quote:
Originally Posted by Alan Anderson
The motor's low resistance to the case is a compelling bit of evidence, but you're right to wonder why it would disable the robot. Just for completeness -- what control are you using to activate this motor? Is it a joystick axis, a gamepad button, a Dashboard variable, or what?
|
We code in C++, and we use one of the triggers on the front of an xbox controller for the intake roller.
Looking at the code though now, I see that it's set up so one trigger is forward and the other trigger is reverse. I'm wondering if there's some strange mode when both triggers are pressed and the code fires off two simultaneous commands, one forward driving the motor and one reverse driving the motor. We have deadbands and smoothing on the analog joysticks, nut none on the triggers.
That's probably a code robustness issue, but I still am not aware of any reason why that would disable the robot.