public class Victor extends PWMSpeedController
PWM.PeriodMultiplierkAnalogInputChannels, kAnalogOutputChannels, kDigitalChannels, kPCMModules, kPDPChannels, kPDPModules, kPwmChannels, kRelayChannels, kSolenoidChannels, kSystemClockTicksPerMicrosecondDEFAULT_SAFETY_EXPIRATION| Constructor and Description |
|---|
Victor(int channel)
Constructor.
|
get, getInverted, pidWrite, set, setInverteddisable, Feed, getDescription, getExpiration, isAlive, isSafetyEnabled, setExpiration, setSafetyEnabled, stopMotorenableDeadbandElimination, free, getChannel, getPosition, getRaw, getRawBounds, getSmartDashboardType, getSpeed, getTable, initTable, setBounds, setDisabled, setPeriodMultiplier, setPosition, setRaw, setRawBounds, setSpeed, setZeroLatch, startLiveWindowMode, stopLiveWindowMode, updateTablecheckAnalogInputChannel, checkAnalogOutputChannel, checkDigitalChannel, checkPDPChannel, checkPDPModule, checkPWMChannel, checkRelayChannel, checkSolenoidChannel, checkSolenoidModule, getDefaultSolenoidModule, setDefaultSolenoidModuleclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitdisable, stopMotorpublic Victor(int channel)
Note that the Victor uses the following bounds for PWM values. These values were determined empirically and optimized for the Victor 888. These values should work reasonably well for Victor 884 controllers also but if users experience issues such as asymmetric behaviour around the deadband or inability to saturate the controller in either direction, calibration is recommended. The calibration procedure can be found in the Victor 884 User Manual available from VEX Robotics: http://content.vexrobotics.com/docs/ifi-v884-users-manual-9-25-06.pdf
- 2.027ms = full "forward" - 1.525ms = the "high end" of the deadband range - 1.507ms = center of the deadband range (off) - 1.49ms = the "low end" of the deadband range - 1.026ms = full "reverse"
channel - The PWM channel that the Victor is attached to. 0-9 are
on-board, 10-19 are on the MXP port