cRIO - motor controller code (esp. victor)

[Alan Anderson]

Originally Posted by Dave Scheck

I was testing with servos controlled by a Victor class...

That's the root of the problem right there. Why weren't you using a Servo class? The software knows about and exploits the difference between the various output devices. If you lie to it about what you're connecting, you shouldn't be surprised that it doesn't give the results you want.

Originally Posted by Dave Scheck

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)

If you use a Victor that was calibrated in a different system, you're asking for trouble in any case. It's easier to reset to factory defaults than it is to calibrate to a new system. In my experience, every Victor acts the same, so it seems quite reasonable to set up the control software to match their behavior.

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()?

For teams unwilling to mess with reading the manual, you mean?

Remove power from the Victor. Press and hold the Victor's CAL button. Apply power. Wait for the Victor's LED to blink green. Release the Victor's CAL button. All done.