View Single Post
  #1   Spotlight this post!  
Unread 06-12-2008, 11:17
Dave Scheck's Avatar
Dave Scheck Dave Scheck is offline
Registered User
FRC #0111 (WildStang)
Team Role: Engineer
 
Join Date: Feb 2003
Rookie Year: 2002
Location: Arlington Heights, IL
Posts: 574
Dave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond reputeDave Scheck has a reputation beyond repute
Re: cRIO - motor controller code (esp. victor)

I was testing with servos controlled by a Victor class and noticed that I wasn't getting full range on the output. That got me digging through the source of the library (an excellent reason for open source code) and noticed the output limits based on empirical data as well.

Quote:
Originally Posted by Alan Anderson View Post
Those empirically established values match the factory calibration of every Victor I have taken the time to characterize.
Any idea why they chose to limit to the default factory values instead of letting the full range out and using the manual calibration of the Victors like years past? If a veteran team pulls Victors from a previous year's robot, they're going to have problems if their Victor is calibrated (as Eric has already found out)

Alan, you mentioned setting the factory defaults for the Victor. What's the procedure for that for teams that don't want to mess with SetBounds()?