Quote:
|
Originally Posted by KenWittlief
I dont understand how putting a deadband around 127 will make the joystick less sensitive
in fact, your bot is going to lurch when the joystick is moved just outside the deadband
|
I've got to agree with Ken on this one. This deadband approach will make the joysticks
more sensitive, because the motor output is proportional to the joystick deflection. If you ignore the stick input unless it's greater than 135 or less than 119, then as the stick moves out of the deadband and starts the motor moving, the motor's smallest non-zero speed is even faster than without the deadband. The result will be jerkiness as the bot starts moving.
Ken's solution sounds good, and is obviously more efficient than what I'm about to suggest here. I haven't tried my idea on the bot yet, and I'm a little sketchy about putting a lookup table of any size into the user routine because I don't want to slow it down too much. But here's the principle: make a slightly non-linear lookup table to de-emphasize the stick input near neutral, but not near the max/min. I've attached an example of the kind of curve I'm thinking of. Notice that near 127, it "dumbs down" the stick input to drive the motors slower and make the sticks less sensitive, but near the high or low end of the input it looks almost linear to make the driveability at high speeds feel pretty normal.
Try it out and let me know what you think! Like I said, I haven't tried this on the bot yet...
EDIT: I just changed the .xls to a zipped up .xls.