View Single Post
  #17   Spotlight this post!  
Unread 17-11-2004, 10:17
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Spikes

Quote:
Originally Posted by Andy A.
Regardless, there is no harm in calibrating, assuming you do it correctly, and no good reason not to. There is a significant difference between joysticks, and I see no reason why that should have to be compensated in programming or by the driver when the victor can be matched to each stick.
I can immediately think of three reasons not to.
  1. It's easier to replace a Victor if you don't have to recalibrate afterwards.
  2. Sometimes the joystick value isn't directly coupled to the motor output (i.e., one-stick control, or a holonomic drivebase).
  3. Autonomous control is seriously impaired if the Victors aren't consistent.

The only compelling reason I see for calibrating a Victor to a specific joystick is if your program is simply copying the input value to the output. For a basic robot under complete manual control, that is perfectly appropriate. As soon as the program gets at all fancy, however, it becomes important to separate the input calibrations from the output calibrations.