View Single Post
  #8   Spotlight this post!  
Unread 23-03-2009, 13:11
marccenter's Avatar
marccenter marccenter is offline
Registered User
FRC #3548 (RoboRavens2)
Team Role: Coach
 
Join Date: Sep 2004
Rookie Year: 2004
Location: Royal Oak
Posts: 406
marccenter has a spectacular aura aboutmarccenter has a spectacular aura about
Smile Re: May we have some traction control help?

Quote:
Originally Posted by Doug Leppard View Post
Our drivers are happy with our traction control. We have the driven wheel encoder and a vex Omni wheel on the floor called the undriven wheel.

We found 20% slippage is the best. Our moving algorithm follows the joystick either increasing power or decreasing power according to the joystick position and wheel slippage.

But you have the 0 or little speed situation, for instance you may be in a pushing war and going almost 0.

For that we don’t do a ratio of slippage because it does not make sense. But we allow a certain number of rpms of the wheel which is slippage at a standstill.

It is very simple.

BTW we put a toggle switch on the driver’s station that allows the drivers to turn off and on the traction control; sometimes the drivers use the large amount of slippage to their advantage especially in turning.
Doug,
In order of implementing a traction control algorithm I have proposed for a FRC conference presentation paper with VEX and Easy-C Pro implementation: 1) rate-limiting joystick command input to motor command output - solves a multitude of problems, 2) control maximum motor speed command as a function of undriven wheel speed (non-feedback based slip control) Joystick position can be independent of the maximum motor speed command but you have indicated that you did
add joystick dependence. Can you indicate why? 3) feedback based slip control (driven wheel speed based to undriven
wheel speed)
__________________
Marc Center
FIRST FRC Mentor/Coach - Team 3548 Royal Oak RoboRavens#2 - on Sabbatical 2017 season
marc.center@gmail.com
Mobile: 248-255-7377