Thread: pic: Uber 3.0
View Single Post
  #2   Spotlight this post!  
Unread 06-08-2011, 09:43
apalrd's Avatar
apalrd apalrd is offline
More Torque!
AKA: Andrew Palardy (Most people call me Palardy)
VRC #3333
Team Role: College Student
 
Join Date: Mar 2009
Rookie Year: 2009
Location: Auburn Hills, MI
Posts: 1,347
apalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond repute
Re: pic: Uber 3.0

Two comments:

Quote:
Originally Posted by ratdude747 View Post
...in the code, use a button/toggle to scale back the joystick inputs to create a "virtual gear"....
While this does work, you are now limiting your motors to a max of a certain power output (since you can never feed them full voltage)

We implemented something like this to create an automatic "1.5" intermediate gear, of around 9 ft/sec (low is usually ~5.5, high 12) which was automatically used when the elevator was above the score-mid height (and another "1.7" intermediate gear of about 10-10.5 when the elevator was in the score mid range). However, we implemented this as a speed request instead of a power request, so the closed-loop speed control could give the motor full power to accelerate or push. Why? Because just blindly limiting motor power gives little benefit (why not just change the gear ratio to make it correct? For a chain drive it takes a few sprockets from Andymark to correct an error that should've been found when you did the initial drivetrain math). However, limiting speed but not power allows the speed control to give full power to accelerate, and we found it useful when scoring.



Also, while I like the cheesy poofs code (and 33 re-implemented it for an off-season project), I still don't get why the code Nick pointed to (cheesy poofs 2010) has a switch for QuickTurn vs SpeedTurn. Why not just do quicktunrs when the throttle is at 0 and speedturns the rest of the time?

That said, the cheesy drive algorithm is very solid.
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor

"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack
Reply With Quote