View Single Post
  #24   Spotlight this post!  
Unread 22-03-2013, 13:34
MrRoboSteve MrRoboSteve is online now
Mentor
AKA: Steve Peterson
FRC #3081 (Kennedy RoboEagles)
Team Role: Mentor
 
Join Date: Mar 2012
Rookie Year: 2011
Location: Bloomington, MN
Posts: 582
MrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond repute
Re: Speed Controllers: Which is best?

Regarding cable retention, Jaguars have a tab below the PWM connector that you should run the cable through. I'd recommend having a tie down nearby for controllers that are purely friction fit for PWM connections, to lower the chance that things wiggle loose. A bit of black electrical tape doesn't hurt either.

There's per-controller tuning in WPILib; don't know whether the same tuning is present for LabVIEW. This means that, for the most accurate response, you want to create speed controller instances that match the controller in use. Having a different controller will function, but with a curve that will seem nonlinear.

Pro tip for WPILib users: declare your speed controllers as SpeedControllers in your header:

Code:
	SpeedController *leftMotor;
	SpeedController *rightMotor;
but create instances that match your controllers in use:

Code:
	this->leftMotor = new Talon(PWM_SLOT, DRIVE_MOTOR_L_1);
	this->rightMotor = new Talon(PWM_SLOT, DRIVE_MOTOR_R_1);
This makes it easier to switch controllers by making changes only where you construct the instances.