Quote:
Originally Posted by mattiej
We could reproduce it every test, but not by doing something. They just happened (but sometimes it did seem like moving the joystick caused it, but that was just because you can see it best in those situations).
|
You can reproduce it, but not by doing something? I don't follow that at all. It sounds like it's occurring at random, and there isn't anything you can do to make it happen.
Quote:
|
Sorry! Stick is a term we like to use. Stick means the motor freezes at an output when it isn't supposed to.
|
A motor sticking/freezing seems like a mechanical issue. When it happens, can you turn the motor by hand (after disconnecting power, of course)?
Quote:
|
Our victors would be either showing disconnected or driving the motors when the joystick was at a neutral state.
|
Wait, what? Can you verify that the joystick was indeed commanding neutral but the cRIO was telling the motors to move? Look at the Dashboard display to see what the joystick is being read as, and what the motor output PWM values are being set to. But I'm lost -- I thought the problem was the motors freezing when they were supposed to be moving, not the other way around.
Quote:
|
We are using the mecanum code, and all we do is pass the joystick axis values into the x, y, and rotation. Not sure what you mean by changing the spin?
|
Spin is the same thing as rotate. Command the robot to rotate to the left and see if the problem occurs more or less often. Then command it to rotate to the right.