View Single Post
  #1   Spotlight this post!  
Unread 18-01-2006, 18:20
Chris_Elston's Avatar
Chris_Elston Chris_Elston is offline
Controls Engineer
AKA: chakorules
FRC #1501 (Team THRUST)
Team Role: Engineer
 
Join Date: Feb 2004
Rookie Year: 2001
Location: Huntington, Indiana
Posts: 746
Chris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond repute
Manual Velocity PID, anyone successful?

Has anyone been successful implementing a manual velocity PID for manual driving?

Did you use single or tank drive joysticks?

What worked better for you? Converting your PWM values to a percent based power where 255 = 100%, or just sticking with PWM values.

Did you design two independent PID's for each wheel? Then how did you integrate them together to make the robot drive straight? Did you have something joining your two PIDs together?

Basically, I was wondering if anyone wanted to share their theory if you've ever got this to work.

Seem rather tricky measuring a velocity from encoders, converting to a "PWM value or percent based command", then reading a joystick value, and integrating the encoder feedback two ways for each wheel, then trying to slave them together, and trying to TURN too....confusing control theory....

Anyone want to share?
__________________
Team T.H.R.U.S.T. 1501
Download all of our past robot's source code here:Repository

Favorite CD quote:
"That can't be their 'bot. not nearly enough (if any) rivets to be a 1501 machine." ~RogerR: Team #1369