Class CoreTalonFX
- All Implemented Interfaces:
CommonTalon
,CommonTalonWithFOC
,HasTalonControls
,HasTalonSignals
,SupportsFOC
,SupportsMusic
- Direct Known Subclasses:
TalonFX
// Constants used in TalonFX construction final int kTalonFXId = 0; final String kTalonFXCANbus = "canivore"; // Construct the TalonFX TalonFX talonfx = new TalonFX(kTalonFXId, kTalonFXCANbus); // Configure the TalonFX for basic use TalonFXConfiguration configs = new TalonFXConfiguration(); // This TalonFX should be configured with a kP of 1, a kI of 0, a kD of 10, and a kV of 2 on slot 0 configs.Slot0.kP = 1; configs.Slot0.kI = 0; configs.Slot0.kD = 10; configs.Slot0.kV = 2; // Write these configs to the TalonFX talonfx.getConfigurator().apply(configs); // Set the position to 0 rotations for initial use talonfx.setPosition(0); // Get Position and Velocity var position = talonfx.getPosition(); var velocity = talonfx.getVelocity(); // Refresh and print these values System.out.println("Position is " + position.refresh().toString()); System.out.println("Velocity is " + velocity.refresh().toString());
-
Nested Class Summary
Nested classes/interfaces inherited from class com.ctre.phoenix6.hardware.ParentDevice
ParentDevice.MapGenerator<T>
-
Field Summary
Fields inherited from class com.ctre.phoenix6.hardware.ParentDevice
_emptyControl, deviceIdentifier
-
Constructor Summary
ConstructorDescriptionCoreTalonFX
(int deviceId) Constructs a new Talon FX motor controller object.CoreTalonFX
(int deviceId, CANBus canbus) Constructs a new Talon FX motor controller object.CoreTalonFX
(int deviceId, String canbus) Constructs a new Talon FX motor controller object. -
Method Summary
Modifier and TypeMethodDescriptionClear sticky fault: Device boot while detecting the enable signalclearStickyFault_BootDuringEnable
(double timeoutSeconds) Clear sticky fault: Device boot while detecting the enable signalClear sticky fault: Bridge was disabled most likely due to supply voltage dropping too low.clearStickyFault_BridgeBrownout
(double timeoutSeconds) Clear sticky fault: Bridge was disabled most likely due to supply voltage dropping too low.Clear sticky fault: Device temperature exceeded limitclearStickyFault_DeviceTemp
(double timeoutSeconds) Clear sticky fault: Device temperature exceeded limitClear sticky fault: Forward limit switch has been asserted.clearStickyFault_ForwardHardLimit
(double timeoutSeconds) Clear sticky fault: Forward limit switch has been asserted.Clear sticky fault: Forward soft limit has been asserted.clearStickyFault_ForwardSoftLimit
(double timeoutSeconds) Clear sticky fault: Forward soft limit has been asserted.Clear sticky fault: The remote sensor used for fusion has fallen out of sync to the local sensor.clearStickyFault_FusedSensorOutOfSync
(double timeoutSeconds) Clear sticky fault: The remote sensor used for fusion has fallen out of sync to the local sensor.Clear sticky fault: Hardware fault occurredclearStickyFault_Hardware
(double timeoutSeconds) Clear sticky fault: Hardware fault occurredClear sticky fault: The remote Talon used for differential control is not present on CAN Bus.clearStickyFault_MissingDifferentialFX
(double timeoutSeconds) Clear sticky fault: The remote Talon used for differential control is not present on CAN Bus.Clear sticky fault: The remote limit switch device is not present on CAN Bus.clearStickyFault_MissingHardLimitRemote
(double timeoutSeconds) Clear sticky fault: The remote limit switch device is not present on CAN Bus.Clear sticky fault: The remote soft limit device is not present on CAN Bus.clearStickyFault_MissingSoftLimitRemote
(double timeoutSeconds) Clear sticky fault: The remote soft limit device is not present on CAN Bus.Clear sticky fault: Supply Voltage has exceeded the maximum voltage rating of device.clearStickyFault_OverSupplyV
(double timeoutSeconds) Clear sticky fault: Supply Voltage has exceeded the maximum voltage rating of device.Clear sticky fault: Processor temperature exceeded limitclearStickyFault_ProcTemp
(double timeoutSeconds) Clear sticky fault: Processor temperature exceeded limitClear sticky fault: The remote sensor's data is no longer trusted.clearStickyFault_RemoteSensorDataInvalid
(double timeoutSeconds) Clear sticky fault: The remote sensor's data is no longer trusted.Clear sticky fault: The remote sensor position has overflowed.clearStickyFault_RemoteSensorPosOverflow
(double timeoutSeconds) Clear sticky fault: The remote sensor position has overflowed.Clear sticky fault: The remote sensor has reset.clearStickyFault_RemoteSensorReset
(double timeoutSeconds) Clear sticky fault: The remote sensor has reset.Clear sticky fault: Reverse limit switch has been asserted.clearStickyFault_ReverseHardLimit
(double timeoutSeconds) Clear sticky fault: Reverse limit switch has been asserted.Clear sticky fault: Reverse soft limit has been asserted.clearStickyFault_ReverseSoftLimit
(double timeoutSeconds) Clear sticky fault: Reverse soft limit has been asserted.Clear sticky fault: Static brake was momentarily disabled due to excessive braking current while disabled.clearStickyFault_StaticBrakeDisabled
(double timeoutSeconds) Clear sticky fault: Static brake was momentarily disabled due to excessive braking current while disabled.Clear sticky fault: Stator current limit occured.clearStickyFault_StatorCurrLimit
(double timeoutSeconds) Clear sticky fault: Stator current limit occured.Clear sticky fault: Supply current limit occured.clearStickyFault_SupplyCurrLimit
(double timeoutSeconds) Clear sticky fault: Supply current limit occured.Clear sticky fault: Device supply voltage dropped to near brownout levelsclearStickyFault_Undervoltage
(double timeoutSeconds) Clear sticky fault: Device supply voltage dropped to near brownout levelsClear sticky fault: An unlicensed feature is in use, device may not behave as expected.clearStickyFault_UnlicensedFeatureInUse
(double timeoutSeconds) Clear sticky fault: An unlicensed feature is in use, device may not behave as expected.Clear sticky fault: Supply Voltage is unstable.clearStickyFault_UnstableSupplyV
(double timeoutSeconds) Clear sticky fault: Supply Voltage is unstable.Clear sticky fault: Using Fused CANcoder feature while unlicensed.clearStickyFault_UsingFusedCANcoderWhileUnlicensed
(double timeoutSeconds) Clear sticky fault: Using Fused CANcoder feature while unlicensed.Clear the sticky faults in the device.clearStickyFaults
(double timeoutSeconds) Clear the sticky faults in the device.StatusSignal<edu.wpi.first.units.measure.AngularAcceleration>
Acceleration of the device in mechanism rotations per second².StatusSignal<edu.wpi.first.units.measure.AngularAcceleration>
getAcceleration
(boolean refresh) Acceleration of the device in mechanism rotations per second².StatusSignal<edu.wpi.first.units.measure.Temperature>
Temperature of device from second sensor.StatusSignal<edu.wpi.first.units.measure.Temperature>
getAncillaryDeviceTemp
(boolean refresh) Temperature of device from second sensor.The applied rotor polarity as seen from the front of the motor.getAppliedRotorPolarity
(boolean refresh) The applied rotor polarity as seen from the front of the motor.The applied output of the bridge.getBridgeOutput
(boolean refresh) The applied output of the bridge.Closed loop derivative componentgetClosedLoopDerivativeOutput
(boolean refresh) Closed loop derivative componentThe difference between target reference and current measurementgetClosedLoopError
(boolean refresh) The difference between target reference and current measurementFeedforward passed by the usergetClosedLoopFeedForward
(boolean refresh) Feedforward passed by the userClosed loop integrated componentgetClosedLoopIntegratedOutput
(boolean refresh) Closed loop integrated componentClosed loop total outputgetClosedLoopOutput
(boolean refresh) Closed loop total outputClosed loop proportional componentgetClosedLoopProportionalOutput
(boolean refresh) Closed loop proportional componentValue that the closed loop is targetinggetClosedLoopReference
(boolean refresh) Value that the closed loop is targetingDerivative of the target that the closed loop is targetinggetClosedLoopReferenceSlope
(boolean refresh) Derivative of the target that the closed loop is targetingThe slot that the closed-loop PID is using.getClosedLoopSlot
(boolean refresh) The slot that the closed-loop PID is using.Gets the configurator to use with this device's configsThe type of motor attached to the Talon.getConnectedMotor
(boolean refresh) The type of motor attached to the Talon.The active control mode of the motor controller.getControlMode
(boolean refresh) The active control mode of the motor controller.Indicates if device is actuator enabled.getDeviceEnable
(boolean refresh) Indicates if device is actuator enabled.StatusSignal<edu.wpi.first.units.measure.Temperature>
Temperature of device.StatusSignal<edu.wpi.first.units.measure.Temperature>
getDeviceTemp
(boolean refresh) Temperature of device.StatusSignal<edu.wpi.first.units.measure.Angle>
Average component of the differential position of device.StatusSignal<edu.wpi.first.units.measure.Angle>
getDifferentialAveragePosition
(boolean refresh) Average component of the differential position of device.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
Average component of the differential velocity of device.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
getDifferentialAverageVelocity
(boolean refresh) Average component of the differential velocity of device.Differential closed loop derivative componentgetDifferentialClosedLoopDerivativeOutput
(boolean refresh) Differential closed loop derivative componentThe difference between target differential reference and current measurementgetDifferentialClosedLoopError
(boolean refresh) The difference between target differential reference and current measurementDifferential Feedforward passed by the usergetDifferentialClosedLoopFeedForward
(boolean refresh) Differential Feedforward passed by the userDifferential closed loop integrated componentgetDifferentialClosedLoopIntegratedOutput
(boolean refresh) Differential closed loop integrated componentDifferential closed loop total outputgetDifferentialClosedLoopOutput
(boolean refresh) Differential closed loop total outputDifferential closed loop proportional componentgetDifferentialClosedLoopProportionalOutput
(boolean refresh) Differential closed loop proportional componentValue that the differential closed loop is targetinggetDifferentialClosedLoopReference
(boolean refresh) Value that the differential closed loop is targetingDerivative of the target that the differential closed loop is targetinggetDifferentialClosedLoopReferenceSlope
(boolean refresh) Derivative of the target that the differential closed loop is targetingThe slot that the closed-loop differential PID is using.getDifferentialClosedLoopSlot
(boolean refresh) The slot that the closed-loop differential PID is using.The active control mode of the differential controller.getDifferentialControlMode
(boolean refresh) The active control mode of the differential controller.StatusSignal<edu.wpi.first.units.measure.Angle>
Difference component of the differential position of device.StatusSignal<edu.wpi.first.units.measure.Angle>
getDifferentialDifferencePosition
(boolean refresh) Difference component of the differential position of device.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
Difference component of the differential velocity of device.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
getDifferentialDifferenceVelocity
(boolean refresh) Difference component of the differential velocity of device.The calculated motor output for differential followers.getDifferentialOutput
(boolean refresh) The calculated motor output for differential followers.The applied motor duty cycle.getDutyCycle
(boolean refresh) The applied motor duty cycle.Device boot while detecting the enable signal Default Value: False Default Rates: CAN: 4.0 HzgetFault_BootDuringEnable
(boolean refresh) Device boot while detecting the enable signal Default Value: False Default Rates: CAN: 4.0 HzBridge was disabled most likely due to supply voltage dropping too low.getFault_BridgeBrownout
(boolean refresh) Bridge was disabled most likely due to supply voltage dropping too low.Device temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzgetFault_DeviceTemp
(boolean refresh) Device temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzForward limit switch has been asserted.getFault_ForwardHardLimit
(boolean refresh) Forward limit switch has been asserted.Forward soft limit has been asserted.getFault_ForwardSoftLimit
(boolean refresh) Forward soft limit has been asserted.The remote sensor used for fusion has fallen out of sync to the local sensor.getFault_FusedSensorOutOfSync
(boolean refresh) The remote sensor used for fusion has fallen out of sync to the local sensor.Hardware fault occurred Default Value: False Default Rates: CAN: 4.0 HzgetFault_Hardware
(boolean refresh) Hardware fault occurred Default Value: False Default Rates: CAN: 4.0 HzThe remote Talon used for differential control is not present on CAN Bus.getFault_MissingDifferentialFX
(boolean refresh) The remote Talon used for differential control is not present on CAN Bus.The remote limit switch device is not present on CAN Bus.getFault_MissingHardLimitRemote
(boolean refresh) The remote limit switch device is not present on CAN Bus.The remote soft limit device is not present on CAN Bus.getFault_MissingSoftLimitRemote
(boolean refresh) The remote soft limit device is not present on CAN Bus.Supply Voltage has exceeded the maximum voltage rating of device.getFault_OverSupplyV
(boolean refresh) Supply Voltage has exceeded the maximum voltage rating of device.Processor temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzgetFault_ProcTemp
(boolean refresh) Processor temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzThe remote sensor's data is no longer trusted.getFault_RemoteSensorDataInvalid
(boolean refresh) The remote sensor's data is no longer trusted.The remote sensor position has overflowed.getFault_RemoteSensorPosOverflow
(boolean refresh) The remote sensor position has overflowed.The remote sensor has reset.getFault_RemoteSensorReset
(boolean refresh) The remote sensor has reset.Reverse limit switch has been asserted.getFault_ReverseHardLimit
(boolean refresh) Reverse limit switch has been asserted.Reverse soft limit has been asserted.getFault_ReverseSoftLimit
(boolean refresh) Reverse soft limit has been asserted.Static brake was momentarily disabled due to excessive braking current while disabled.getFault_StaticBrakeDisabled
(boolean refresh) Static brake was momentarily disabled due to excessive braking current while disabled.Stator current limit occured.getFault_StatorCurrLimit
(boolean refresh) Stator current limit occured.Supply current limit occured.getFault_SupplyCurrLimit
(boolean refresh) Supply current limit occured.Device supply voltage dropped to near brownout levels Default Value: False Default Rates: CAN: 4.0 HzgetFault_Undervoltage
(boolean refresh) Device supply voltage dropped to near brownout levels Default Value: False Default Rates: CAN: 4.0 HzAn unlicensed feature is in use, device may not behave as expected.getFault_UnlicensedFeatureInUse
(boolean refresh) An unlicensed feature is in use, device may not behave as expected.Supply Voltage is unstable.getFault_UnstableSupplyV
(boolean refresh) Supply Voltage is unstable.Using Fused CANcoder feature while unlicensed.getFault_UsingFusedCANcoderWhileUnlicensed
(boolean refresh) Using Fused CANcoder feature while unlicensed.Integer representing all fault flags reported by the device.getFaultField
(boolean refresh) Integer representing all fault flags reported by the device.Forward Limit Pin.getForwardLimit
(boolean refresh) Forward Limit Pin.Whether the device is Phoenix Pro licensed.getIsProLicensed
(boolean refresh) Whether the device is Phoenix Pro licensed.Check if Motion Magic® is running.getMotionMagicIsRunning
(boolean refresh) Check if Motion Magic® is running.StatusSignal<edu.wpi.first.units.measure.Per<TorqueUnit,
CurrentUnit>> The torque constant (K_T) of the motor.StatusSignal<edu.wpi.first.units.measure.Per<TorqueUnit,
CurrentUnit>> getMotorKT
(boolean refresh) The torque constant (K_T) of the motor.StatusSignal<edu.wpi.first.units.measure.Per<AngularVelocityUnit,
VoltageUnit>> The velocity constant (K_V) of the motor.StatusSignal<edu.wpi.first.units.measure.Per<AngularVelocityUnit,
VoltageUnit>> getMotorKV
(boolean refresh) The velocity constant (K_V) of the motor.Assess the status of the motor output with respect to load and supply.getMotorOutputStatus
(boolean refresh) Assess the status of the motor output with respect to load and supply.StatusSignal<edu.wpi.first.units.measure.Current>
The stall current of the motor at 12 V output.StatusSignal<edu.wpi.first.units.measure.Current>
getMotorStallCurrent
(boolean refresh) The stall current of the motor at 12 V output.StatusSignal<edu.wpi.first.units.measure.Voltage>
The applied (output) motor voltage.StatusSignal<edu.wpi.first.units.measure.Voltage>
getMotorVoltage
(boolean refresh) The applied (output) motor voltage.StatusSignal<edu.wpi.first.units.measure.Angle>
Position of the device in mechanism rotations.StatusSignal<edu.wpi.first.units.measure.Angle>
getPosition
(boolean refresh) Position of the device in mechanism rotations.StatusSignal<edu.wpi.first.units.measure.Temperature>
Temperature of the processor.StatusSignal<edu.wpi.first.units.measure.Temperature>
getProcessorTemp
(boolean refresh) Temperature of the processor.Reverse Limit Pin.getReverseLimit
(boolean refresh) Reverse Limit Pin.StatusSignal<edu.wpi.first.units.measure.Angle>
Position of the motor rotor.StatusSignal<edu.wpi.first.units.measure.Angle>
getRotorPosition
(boolean refresh) Position of the motor rotor.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
Velocity of the motor rotor.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
getRotorVelocity
(boolean refresh) Velocity of the motor rotor.Get the simulation state for this device.StatusSignal<edu.wpi.first.units.measure.Current>
Current corresponding to the stator windings.StatusSignal<edu.wpi.first.units.measure.Current>
getStatorCurrent
(boolean refresh) Current corresponding to the stator windings.Device boot while detecting the enable signal Default Value: False Default Rates: CAN: 4.0 HzgetStickyFault_BootDuringEnable
(boolean refresh) Device boot while detecting the enable signal Default Value: False Default Rates: CAN: 4.0 HzBridge was disabled most likely due to supply voltage dropping too low.getStickyFault_BridgeBrownout
(boolean refresh) Bridge was disabled most likely due to supply voltage dropping too low.Device temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzgetStickyFault_DeviceTemp
(boolean refresh) Device temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzForward limit switch has been asserted.getStickyFault_ForwardHardLimit
(boolean refresh) Forward limit switch has been asserted.Forward soft limit has been asserted.getStickyFault_ForwardSoftLimit
(boolean refresh) Forward soft limit has been asserted.The remote sensor used for fusion has fallen out of sync to the local sensor.getStickyFault_FusedSensorOutOfSync
(boolean refresh) The remote sensor used for fusion has fallen out of sync to the local sensor.Hardware fault occurred Default Value: False Default Rates: CAN: 4.0 HzgetStickyFault_Hardware
(boolean refresh) Hardware fault occurred Default Value: False Default Rates: CAN: 4.0 HzThe remote Talon used for differential control is not present on CAN Bus.getStickyFault_MissingDifferentialFX
(boolean refresh) The remote Talon used for differential control is not present on CAN Bus.The remote limit switch device is not present on CAN Bus.getStickyFault_MissingHardLimitRemote
(boolean refresh) The remote limit switch device is not present on CAN Bus.The remote soft limit device is not present on CAN Bus.getStickyFault_MissingSoftLimitRemote
(boolean refresh) The remote soft limit device is not present on CAN Bus.Supply Voltage has exceeded the maximum voltage rating of device.getStickyFault_OverSupplyV
(boolean refresh) Supply Voltage has exceeded the maximum voltage rating of device.Processor temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzgetStickyFault_ProcTemp
(boolean refresh) Processor temperature exceeded limit Default Value: False Default Rates: CAN: 4.0 HzThe remote sensor's data is no longer trusted.getStickyFault_RemoteSensorDataInvalid
(boolean refresh) The remote sensor's data is no longer trusted.The remote sensor position has overflowed.getStickyFault_RemoteSensorPosOverflow
(boolean refresh) The remote sensor position has overflowed.The remote sensor has reset.getStickyFault_RemoteSensorReset
(boolean refresh) The remote sensor has reset.Reverse limit switch has been asserted.getStickyFault_ReverseHardLimit
(boolean refresh) Reverse limit switch has been asserted.Reverse soft limit has been asserted.getStickyFault_ReverseSoftLimit
(boolean refresh) Reverse soft limit has been asserted.Static brake was momentarily disabled due to excessive braking current while disabled.getStickyFault_StaticBrakeDisabled
(boolean refresh) Static brake was momentarily disabled due to excessive braking current while disabled.Stator current limit occured.getStickyFault_StatorCurrLimit
(boolean refresh) Stator current limit occured.Supply current limit occured.getStickyFault_SupplyCurrLimit
(boolean refresh) Supply current limit occured.Device supply voltage dropped to near brownout levels Default Value: False Default Rates: CAN: 4.0 HzgetStickyFault_Undervoltage
(boolean refresh) Device supply voltage dropped to near brownout levels Default Value: False Default Rates: CAN: 4.0 HzAn unlicensed feature is in use, device may not behave as expected.getStickyFault_UnlicensedFeatureInUse
(boolean refresh) An unlicensed feature is in use, device may not behave as expected.Supply Voltage is unstable.getStickyFault_UnstableSupplyV
(boolean refresh) Supply Voltage is unstable.Using Fused CANcoder feature while unlicensed.getStickyFault_UsingFusedCANcoderWhileUnlicensed
(boolean refresh) Using Fused CANcoder feature while unlicensed.Integer representing all (persistent) sticky fault flags reported by the device.getStickyFaultField
(boolean refresh) Integer representing all (persistent) sticky fault flags reported by the device.StatusSignal<edu.wpi.first.units.measure.Current>
Measured supply side current.StatusSignal<edu.wpi.first.units.measure.Current>
getSupplyCurrent
(boolean refresh) Measured supply side current.StatusSignal<edu.wpi.first.units.measure.Voltage>
Measured supply voltage to the device.StatusSignal<edu.wpi.first.units.measure.Voltage>
getSupplyVoltage
(boolean refresh) Measured supply voltage to the device.StatusSignal<edu.wpi.first.units.measure.Current>
Current corresponding to the torque output by the motor.StatusSignal<edu.wpi.first.units.measure.Current>
getTorqueCurrent
(boolean refresh) Current corresponding to the torque output by the motor.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
Velocity of the device in mechanism rotations per second.StatusSignal<edu.wpi.first.units.measure.AngularVelocity>
getVelocity
(boolean refresh) Velocity of the device in mechanism rotations per second.Full Version of firmware in device.getVersion
(boolean refresh) Full Version of firmware in device.App Bugfix Version number.getVersionBugfix
(boolean refresh) App Bugfix Version number.App Build Version number.getVersionBuild
(boolean refresh) App Build Version number.App Major Version number.getVersionMajor
(boolean refresh) App Major Version number.App Minor Version number.getVersionMinor
(boolean refresh) App Minor Version number.setControl
(CoastOut request) Request coast neutral output of actuator.setControl
(com.ctre.phoenix6.controls.compound.Diff_DutyCycleOut_Position request) Differential control with duty cycle average target and position difference target.setControl
(com.ctre.phoenix6.controls.compound.Diff_DutyCycleOut_Velocity request) Differential control with duty cycle average target and velocity difference target.setControl
(com.ctre.phoenix6.controls.compound.Diff_MotionMagicDutyCycle_Position request) Differential control with Motion Magic® average target and position difference target using dutycycle control.setControl
(com.ctre.phoenix6.controls.compound.Diff_MotionMagicDutyCycle_Velocity request) Differential control with Motion Magic® average target and velocity difference target using dutycycle control.setControl
(com.ctre.phoenix6.controls.compound.Diff_MotionMagicTorqueCurrentFOC_Position request) Differential control with Motion Magic® average target and position difference target using torque current control.setControl
(com.ctre.phoenix6.controls.compound.Diff_MotionMagicTorqueCurrentFOC_Velocity request) Differential control with Motion Magic® average target and velocity difference target using torque current control.setControl
(com.ctre.phoenix6.controls.compound.Diff_MotionMagicVoltage_Position request) Differential control with Motion Magic® average target and position difference target using voltage control.setControl
(com.ctre.phoenix6.controls.compound.Diff_MotionMagicVoltage_Velocity request) Differential control with Motion Magic® average target and velocity difference target using voltage control.setControl
(com.ctre.phoenix6.controls.compound.Diff_PositionDutyCycle_Position request) Differential control with position average target and position difference target using dutycycle control.setControl
(com.ctre.phoenix6.controls.compound.Diff_PositionDutyCycle_Velocity request) Differential control with position average target and velocity difference target using dutycycle control.setControl
(com.ctre.phoenix6.controls.compound.Diff_PositionTorqueCurrentFOC_Position request) Differential control with position average target and position difference target using torque current control.setControl
(com.ctre.phoenix6.controls.compound.Diff_PositionTorqueCurrentFOC_Velocity request) Differential control with position average target and velocity difference target using torque current control.setControl
(com.ctre.phoenix6.controls.compound.Diff_PositionVoltage_Position request) Differential control with position average target and position difference target using voltage control.setControl
(com.ctre.phoenix6.controls.compound.Diff_PositionVoltage_Velocity request) Differential control with position average target and velocity difference target using voltage control.setControl
(com.ctre.phoenix6.controls.compound.Diff_TorqueCurrentFOC_Position request) Differential control with torque current average target and position difference target.setControl
(com.ctre.phoenix6.controls.compound.Diff_TorqueCurrentFOC_Velocity request) Differential control with torque current average target and velocity difference target.setControl
(com.ctre.phoenix6.controls.compound.Diff_VelocityDutyCycle_Position request) Differential control with velocity average target and position difference target using dutycycle control.setControl
(com.ctre.phoenix6.controls.compound.Diff_VelocityDutyCycle_Velocity request) Differential control with velocity average target and velocity difference target using dutycycle control.setControl
(com.ctre.phoenix6.controls.compound.Diff_VelocityTorqueCurrentFOC_Position request) Differential control with velocity average target and position difference target using torque current control.setControl
(com.ctre.phoenix6.controls.compound.Diff_VelocityTorqueCurrentFOC_Velocity request) Differential control with velocity average target and velocity difference target using torque current control.setControl
(com.ctre.phoenix6.controls.compound.Diff_VelocityVoltage_Position request) Differential control with velocity average target and position difference target using voltage control.setControl
(com.ctre.phoenix6.controls.compound.Diff_VelocityVoltage_Velocity request) Differential control with velocity average target and velocity difference target using voltage control.setControl
(com.ctre.phoenix6.controls.compound.Diff_VoltageOut_Position request) Differential control with voltage average target and position difference target.setControl
(com.ctre.phoenix6.controls.compound.Diff_VoltageOut_Velocity request) Differential control with voltage average target and velocity difference target.setControl
(ControlRequest request) Control device with generic control request object.setControl
(DifferentialDutyCycle request) Request a specified motor duty cycle with a differential position closed-loop.setControl
(DifferentialFollower request) Follow the differential motor output of another Talon.Requests Motion Magic® to target a final position using a motion profile, and PID to a differential position setpoint.setControl
(DifferentialMotionMagicVoltage request) Requests Motion Magic® to target a final position using a motion profile, and PID to a differential position setpoint.setControl
(DifferentialPositionDutyCycle request) Request PID to target position with a differential position setpoint.setControl
(DifferentialPositionVoltage request) Request PID to target position with a differential position setpointsetControl
(DifferentialStrictFollower request) Follow the differential motor output of another Talon while ignoring the master's invert setting.setControl
(DifferentialVelocityDutyCycle request) Request PID to target velocity with a differential position setpoint.setControl
(DifferentialVelocityVoltage request) Request PID to target velocity with a differential position setpoint.setControl
(DifferentialVoltage request) Request a specified voltage with a differential position closed-loop.setControl
(DutyCycleOut request) Request a specified motor duty cycle.setControl
(DynamicMotionMagicDutyCycle request) Requests Motion Magic® to target a final position using a motion profile.Requests Motion Magic® to target a final position using a motion profile.setControl
(DynamicMotionMagicVoltage request) Requests Motion Magic® to target a final position using a motion profile.setControl
(Follower request) Follow the motor output of another Talon.setControl
(MotionMagicDutyCycle request) Requests Motion Magic® to target a final position using a motion profile.setControl
(MotionMagicExpoDutyCycle request) Requests Motion Magic® to target a final position using an exponential motion profile.Requests Motion Magic® to target a final position using an exponential motion profile.setControl
(MotionMagicExpoVoltage request) Requests Motion Magic® to target a final position using an exponential motion profile.setControl
(MotionMagicTorqueCurrentFOC request) Requests Motion Magic® to target a final position using a motion profile.setControl
(MotionMagicVelocityDutyCycle request) Requests Motion Magic® to target a final velocity using a motion profile.Requests Motion Magic® to target a final velocity using a motion profile.setControl
(MotionMagicVelocityVoltage request) Requests Motion Magic® to target a final velocity using a motion profile.setControl
(MotionMagicVoltage request) Requests Motion Magic® to target a final position using a motion profile.setControl
(MusicTone request) Plays a single tone at the user specified frequency.setControl
(NeutralOut request) Request neutral output of actuator.setControl
(PositionDutyCycle request) Request PID to target position with duty cycle feedforward.setControl
(PositionTorqueCurrentFOC request) Request PID to target position with torque current feedforward.setControl
(PositionVoltage request) Request PID to target position with voltage feedforwardsetControl
(StaticBrake request) Applies full neutral-brake by shorting motor leads together.setControl
(StrictFollower request) Follow the motor output of another Talon while ignoring the master's invert setting.setControl
(TorqueCurrentFOC request) Request a specified motor current (field oriented control).setControl
(VelocityDutyCycle request) Request PID to target velocity with duty cycle feedforward.setControl
(VelocityTorqueCurrentFOC request) Request PID to target velocity with torque current feedforward.setControl
(VelocityVoltage request) Request PID to target velocity with voltage feedforward.setControl
(VoltageOut request) Request a specified voltage.setPosition
(double newValue) Sets the mechanism position of the device in mechanism rotations.setPosition
(double newValue, double timeoutSeconds) Sets the mechanism position of the device in mechanism rotations.setPosition
(edu.wpi.first.units.measure.Angle newValue) Sets the mechanism position of the device in mechanism rotations.setPosition
(edu.wpi.first.units.measure.Angle newValue, double timeoutSeconds) Sets the mechanism position of the device in mechanism rotations.Methods inherited from class com.ctre.phoenix6.hardware.ParentDevice
getAppliedControl, getDeviceHash, getDeviceID, getNetwork, getResetOccurredChecker, hasResetOccurred, isConnected, isConnected, lookupStatusSignal, lookupStatusSignal, optimizeBusUtilization, optimizeBusUtilization, optimizeBusUtilization, optimizeBusUtilizationForAll, optimizeBusUtilizationForAll, resetSignalFrequencies, resetSignalFrequencies, resetSignalFrequenciesForAll, setControlPrivate
-
Constructor Details
-
CoreTalonFX
Constructs a new Talon FX motor controller object.Constructs the device using the default CAN bus for the system:
- "rio" on roboRIO
- "can0" on Linux
- "*" on Windows
- Parameters:
deviceId
- ID of the device, as configured in Phoenix Tuner.
-
CoreTalonFX
Constructs a new Talon FX motor controller object.- Parameters:
deviceId
- ID of the device, as configured in Phoenix Tuner.canbus
- Name of the CAN bus this device is on. Possible CAN bus strings are:- "rio" for the native roboRIO CAN bus
- CANivore name or serial number
- SocketCAN interface (non-FRC Linux only)
- "*" for any CANivore seen by the program
- empty string (default) to select the default for the system:
- "rio" on roboRIO
- "can0" on Linux
- "*" on Windows
-
CoreTalonFX
Constructs a new Talon FX motor controller object.- Parameters:
deviceId
- ID of the device, as configured in Phoenix Tuner.canbus
- The CAN bus this device is on.
-
-
Method Details
-
getConfigurator
Gets the configurator to use with this device's configs- Returns:
- Configurator for this object
-
getSimState
Get the simulation state for this device.This function reuses an allocated simulation state object, so it is safe to call this function multiple times in a robot loop.
- Returns:
- Simulation state
-
getVersionMajor
App Major Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionMajor
in interfaceHasTalonSignals
- Returns:
- VersionMajor Status Signal Object
-
getVersionMajor
App Major Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionMajor
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- VersionMajor Status Signal Object
-
getVersionMinor
App Minor Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionMinor
in interfaceHasTalonSignals
- Returns:
- VersionMinor Status Signal Object
-
getVersionMinor
App Minor Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionMinor
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- VersionMinor Status Signal Object
-
getVersionBugfix
App Bugfix Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionBugfix
in interfaceHasTalonSignals
- Returns:
- VersionBugfix Status Signal Object
-
getVersionBugfix
App Bugfix Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionBugfix
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- VersionBugfix Status Signal Object
-
getVersionBuild
App Build Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionBuild
in interfaceHasTalonSignals
- Returns:
- VersionBuild Status Signal Object
-
getVersionBuild
App Build Version number.- Minimum Value: 0
- Maximum Value: 255
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersionBuild
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- VersionBuild Status Signal Object
-
getVersion
Full Version of firmware in device. The format is a four byte value.- Minimum Value: 0
- Maximum Value: 4294967295
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersion
in interfaceHasTalonSignals
- Returns:
- Version Status Signal Object
-
getVersion
Full Version of firmware in device. The format is a four byte value.- Minimum Value: 0
- Maximum Value: 4294967295
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVersion
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Version Status Signal Object
-
getFaultField
Integer representing all fault flags reported by the device.These are device specific and are not used directly in typical applications. Use the signal specific GetFault_*() methods instead.
- Minimum Value: 0
- Maximum Value: 4294967295
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFaultField
in interfaceHasTalonSignals
- Returns:
- FaultField Status Signal Object
-
getFaultField
Integer representing all fault flags reported by the device.These are device specific and are not used directly in typical applications. Use the signal specific GetFault_*() methods instead.
- Minimum Value: 0
- Maximum Value: 4294967295
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFaultField
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- FaultField Status Signal Object
-
getStickyFaultField
Integer representing all (persistent) sticky fault flags reported by the device.These are device specific and are not used directly in typical applications. Use the signal specific GetStickyFault_*() methods instead.
- Minimum Value: 0
- Maximum Value: 4294967295
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFaultField
in interfaceHasTalonSignals
- Returns:
- StickyFaultField Status Signal Object
-
getStickyFaultField
Integer representing all (persistent) sticky fault flags reported by the device.These are device specific and are not used directly in typical applications. Use the signal specific GetStickyFault_*() methods instead.
- Minimum Value: 0
- Maximum Value: 4294967295
- Default Value: 0
- Units:
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFaultField
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFaultField Status Signal Object
-
getMotorVoltage
The applied (output) motor voltage.- Minimum Value: -40.96
- Maximum Value: 40.95
- Default Value: 0
- Units: V
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorVoltage
in interfaceHasTalonSignals
- Returns:
- MotorVoltage Status Signal Object
-
getMotorVoltage
The applied (output) motor voltage.- Minimum Value: -40.96
- Maximum Value: 40.95
- Default Value: 0
- Units: V
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorVoltage
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- MotorVoltage Status Signal Object
-
getForwardLimit
Forward Limit Pin. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getForwardLimit
in interfaceHasTalonSignals
- Returns:
- ForwardLimit Status Signal Object
-
getForwardLimit
Forward Limit Pin. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getForwardLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ForwardLimit Status Signal Object
-
getReverseLimit
Reverse Limit Pin. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getReverseLimit
in interfaceHasTalonSignals
- Returns:
- ReverseLimit Status Signal Object
-
getReverseLimit
Reverse Limit Pin. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getReverseLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ReverseLimit Status Signal Object
-
getAppliedRotorPolarity
The applied rotor polarity as seen from the front of the motor. This typically is determined by the Inverted config, but can be overridden if using Follower features. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getAppliedRotorPolarity
in interfaceHasTalonSignals
- Returns:
- AppliedRotorPolarity Status Signal Object
-
getAppliedRotorPolarity
The applied rotor polarity as seen from the front of the motor. This typically is determined by the Inverted config, but can be overridden if using Follower features. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getAppliedRotorPolarity
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- AppliedRotorPolarity Status Signal Object
-
getDutyCycle
The applied motor duty cycle.- Minimum Value: -2.0
- Maximum Value: 1.9990234375
- Default Value: 0
- Units: fractional
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDutyCycle
in interfaceHasTalonSignals
- Returns:
- DutyCycle Status Signal Object
-
getDutyCycle
The applied motor duty cycle.- Minimum Value: -2.0
- Maximum Value: 1.9990234375
- Default Value: 0
- Units: fractional
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDutyCycle
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DutyCycle Status Signal Object
-
getTorqueCurrent
Current corresponding to the torque output by the motor. Similar to StatorCurrent. Users will likely prefer this current to calculate the applied torque to the rotor.Stator current where positive current means torque is applied in the forward direction as determined by the Inverted setting.
- Minimum Value: -327.68
- Maximum Value: 327.67
- Default Value: 0
- Units: A
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getTorqueCurrent
in interfaceHasTalonSignals
- Returns:
- TorqueCurrent Status Signal Object
-
getTorqueCurrent
Current corresponding to the torque output by the motor. Similar to StatorCurrent. Users will likely prefer this current to calculate the applied torque to the rotor.Stator current where positive current means torque is applied in the forward direction as determined by the Inverted setting.
- Minimum Value: -327.68
- Maximum Value: 327.67
- Default Value: 0
- Units: A
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getTorqueCurrent
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- TorqueCurrent Status Signal Object
-
getStatorCurrent
Current corresponding to the stator windings. Similar to TorqueCurrent. Users will likely prefer TorqueCurrent over StatorCurrent.Stator current where Positive current indicates motoring regardless of direction. Negative current indicates regenerative braking regardless of direction.
- Minimum Value: -327.68
- Maximum Value: 327.66
- Default Value: 0
- Units: A
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStatorCurrent
in interfaceHasTalonSignals
- Returns:
- StatorCurrent Status Signal Object
-
getStatorCurrent
Current corresponding to the stator windings. Similar to TorqueCurrent. Users will likely prefer TorqueCurrent over StatorCurrent.Stator current where Positive current indicates motoring regardless of direction. Negative current indicates regenerative braking regardless of direction.
- Minimum Value: -327.68
- Maximum Value: 327.66
- Default Value: 0
- Units: A
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStatorCurrent
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StatorCurrent Status Signal Object
-
getSupplyCurrent
Measured supply side current.- Minimum Value: -327.68
- Maximum Value: 327.66
- Default Value: 0
- Units: A
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getSupplyCurrent
in interfaceHasTalonSignals
- Returns:
- SupplyCurrent Status Signal Object
-
getSupplyCurrent
Measured supply side current.- Minimum Value: -327.68
- Maximum Value: 327.66
- Default Value: 0
- Units: A
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getSupplyCurrent
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- SupplyCurrent Status Signal Object
-
getSupplyVoltage
Measured supply voltage to the device.- Minimum Value: 4
- Maximum Value: 29.575
- Default Value: 4
- Units: V
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getSupplyVoltage
in interfaceHasTalonSignals
- Returns:
- SupplyVoltage Status Signal Object
-
getSupplyVoltage
Measured supply voltage to the device.- Minimum Value: 4
- Maximum Value: 29.575
- Default Value: 4
- Units: V
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getSupplyVoltage
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- SupplyVoltage Status Signal Object
-
getDeviceTemp
Temperature of device.This is the temperature that the device measures itself to be at. Similar to Processor Temperature.
- Minimum Value: 0.0
- Maximum Value: 255.0
- Default Value: 0
- Units: ℃
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDeviceTemp
in interfaceHasTalonSignals
- Returns:
- DeviceTemp Status Signal Object
-
getDeviceTemp
Temperature of device.This is the temperature that the device measures itself to be at. Similar to Processor Temperature.
- Minimum Value: 0.0
- Maximum Value: 255.0
- Default Value: 0
- Units: ℃
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDeviceTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DeviceTemp Status Signal Object
-
getProcessorTemp
Temperature of the processor.This is the temperature that the processor measures itself to be at. Similar to Device Temperature.
- Minimum Value: 0.0
- Maximum Value: 255.0
- Default Value: 0
- Units: ℃
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getProcessorTemp
in interfaceHasTalonSignals
- Returns:
- ProcessorTemp Status Signal Object
-
getProcessorTemp
Temperature of the processor.This is the temperature that the processor measures itself to be at. Similar to Device Temperature.
- Minimum Value: 0.0
- Maximum Value: 255.0
- Default Value: 0
- Units: ℃
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getProcessorTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ProcessorTemp Status Signal Object
-
getRotorVelocity
Velocity of the motor rotor. This velocity is not affected by any feedback configs.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getRotorVelocity
in interfaceHasTalonSignals
- Returns:
- RotorVelocity Status Signal Object
-
getRotorVelocity
Velocity of the motor rotor. This velocity is not affected by any feedback configs.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getRotorVelocity
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- RotorVelocity Status Signal Object
-
getRotorPosition
Position of the motor rotor. This position is only affected by the RotorOffset config and calls to setPosition.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getRotorPosition
in interfaceHasTalonSignals
- Returns:
- RotorPosition Status Signal Object
-
getRotorPosition
Position of the motor rotor. This position is only affected by the RotorOffset config and calls to setPosition.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getRotorPosition
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- RotorPosition Status Signal Object
-
getVelocity
Velocity of the device in mechanism rotations per second. This can be the velocity of a remote sensor and is affected by the RotorToSensorRatio and SensorToMechanismRatio configs.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 50.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVelocity
in interfaceHasTalonSignals
- Returns:
- Velocity Status Signal Object
-
getVelocity
Velocity of the device in mechanism rotations per second. This can be the velocity of a remote sensor and is affected by the RotorToSensorRatio and SensorToMechanismRatio configs.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 50.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getVelocity
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Velocity Status Signal Object
-
getPosition
Position of the device in mechanism rotations. This can be the position of a remote sensor and is affected by the RotorToSensorRatio and SensorToMechanismRatio configs, as well as calls to setPosition.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 50.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getPosition
in interfaceHasTalonSignals
- Returns:
- Position Status Signal Object
-
getPosition
Position of the device in mechanism rotations. This can be the position of a remote sensor and is affected by the RotorToSensorRatio and SensorToMechanismRatio configs, as well as calls to setPosition.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 50.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getPosition
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Position Status Signal Object
-
getAcceleration
Acceleration of the device in mechanism rotations per second². This can be the acceleration of a remote sensor and is affected by the RotorToSensorRatio and SensorToMechanismRatio configs.- Minimum Value: -2048.0
- Maximum Value: 2047.75
- Default Value: 0
- Units: rotations per second²
- CAN 2.0: 50.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getAcceleration
in interfaceHasTalonSignals
- Returns:
- Acceleration Status Signal Object
-
getAcceleration
public StatusSignal<edu.wpi.first.units.measure.AngularAcceleration> getAcceleration(boolean refresh) Acceleration of the device in mechanism rotations per second². This can be the acceleration of a remote sensor and is affected by the RotorToSensorRatio and SensorToMechanismRatio configs.- Minimum Value: -2048.0
- Maximum Value: 2047.75
- Default Value: 0
- Units: rotations per second²
- CAN 2.0: 50.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getAcceleration
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Acceleration Status Signal Object
-
getControlMode
The active control mode of the motor controller. Default Rates:- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getControlMode
in interfaceHasTalonSignals
- Returns:
- ControlMode Status Signal Object
-
getControlMode
The active control mode of the motor controller. Default Rates:- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getControlMode
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ControlMode Status Signal Object
-
getMotionMagicIsRunning
Check if Motion Magic® is running. This is equivalent to checking that the reported control mode is a Motion Magic® based mode. Default Rates:- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotionMagicIsRunning
in interfaceHasTalonSignals
- Returns:
- MotionMagicIsRunning Status Signal Object
-
getMotionMagicIsRunning
Check if Motion Magic® is running. This is equivalent to checking that the reported control mode is a Motion Magic® based mode. Default Rates:- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotionMagicIsRunning
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- MotionMagicIsRunning Status Signal Object
-
getDeviceEnable
Indicates if device is actuator enabled. Default Rates:- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDeviceEnable
in interfaceHasTalonSignals
- Returns:
- DeviceEnable Status Signal Object
-
getDeviceEnable
Indicates if device is actuator enabled. Default Rates:- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDeviceEnable
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DeviceEnable Status Signal Object
-
getClosedLoopSlot
The slot that the closed-loop PID is using.- Minimum Value: 0
- Maximum Value: 2
- Default Value: 0
- Units:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopSlot
in interfaceHasTalonSignals
- Returns:
- ClosedLoopSlot Status Signal Object
-
getClosedLoopSlot
The slot that the closed-loop PID is using.- Minimum Value: 0
- Maximum Value: 2
- Default Value: 0
- Units:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopSlot
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopSlot Status Signal Object
-
getMotorOutputStatus
Assess the status of the motor output with respect to load and supply.This routine can be used to determine the general status of motor commutation. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorOutputStatus
in interfaceHasTalonSignals
- Returns:
- MotorOutputStatus Status Signal Object
-
getMotorOutputStatus
Assess the status of the motor output with respect to load and supply.This routine can be used to determine the general status of motor commutation. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorOutputStatus
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- MotorOutputStatus Status Signal Object
-
getDifferentialControlMode
The active control mode of the differential controller. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialControlMode
in interfaceHasTalonSignals
- Returns:
- DifferentialControlMode Status Signal Object
-
getDifferentialControlMode
The active control mode of the differential controller. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialControlMode
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialControlMode Status Signal Object
-
getDifferentialAverageVelocity
Average component of the differential velocity of device.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialAverageVelocity
in interfaceHasTalonSignals
- Returns:
- DifferentialAverageVelocity Status Signal Object
-
getDifferentialAverageVelocity
public StatusSignal<edu.wpi.first.units.measure.AngularVelocity> getDifferentialAverageVelocity(boolean refresh) Average component of the differential velocity of device.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialAverageVelocity
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialAverageVelocity Status Signal Object
-
getDifferentialAveragePosition
Average component of the differential position of device.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialAveragePosition
in interfaceHasTalonSignals
- Returns:
- DifferentialAveragePosition Status Signal Object
-
getDifferentialAveragePosition
public StatusSignal<edu.wpi.first.units.measure.Angle> getDifferentialAveragePosition(boolean refresh) Average component of the differential position of device.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialAveragePosition
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialAveragePosition Status Signal Object
-
getDifferentialDifferenceVelocity
public StatusSignal<edu.wpi.first.units.measure.AngularVelocity> getDifferentialDifferenceVelocity()Difference component of the differential velocity of device.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialDifferenceVelocity
in interfaceHasTalonSignals
- Returns:
- DifferentialDifferenceVelocity Status Signal Object
-
getDifferentialDifferenceVelocity
public StatusSignal<edu.wpi.first.units.measure.AngularVelocity> getDifferentialDifferenceVelocity(boolean refresh) Difference component of the differential velocity of device.- Minimum Value: -512.0
- Maximum Value: 511.998046875
- Default Value: 0
- Units: rotations per second
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialDifferenceVelocity
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialDifferenceVelocity Status Signal Object
-
getDifferentialDifferencePosition
Difference component of the differential position of device.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialDifferencePosition
in interfaceHasTalonSignals
- Returns:
- DifferentialDifferencePosition Status Signal Object
-
getDifferentialDifferencePosition
public StatusSignal<edu.wpi.first.units.measure.Angle> getDifferentialDifferencePosition(boolean refresh) Difference component of the differential position of device.- Minimum Value: -16384.0
- Maximum Value: 16383.999755859375
- Default Value: 0
- Units: rotations
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialDifferencePosition
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialDifferencePosition Status Signal Object
-
getDifferentialClosedLoopSlot
The slot that the closed-loop differential PID is using.- Minimum Value: 0
- Maximum Value: 2
- Default Value: 0
- Units:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopSlot
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopSlot Status Signal Object
-
getDifferentialClosedLoopSlot
The slot that the closed-loop differential PID is using.- Minimum Value: 0
- Maximum Value: 2
- Default Value: 0
- Units:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopSlot
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopSlot Status Signal Object
-
getMotorKT
The torque constant (K_T) of the motor.- Minimum Value: 0.0
- Maximum Value: 0.025500000000000002
- Default Value: 0
- Units: Nm/A
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorKT
in interfaceHasTalonSignals
- Returns:
- MotorKT Status Signal Object
-
getMotorKT
public StatusSignal<edu.wpi.first.units.measure.Per<TorqueUnit,CurrentUnit>> getMotorKT(boolean refresh) The torque constant (K_T) of the motor.- Minimum Value: 0.0
- Maximum Value: 0.025500000000000002
- Default Value: 0
- Units: Nm/A
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorKT
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- MotorKT Status Signal Object
-
getMotorKV
The velocity constant (K_V) of the motor.- Minimum Value: 0.0
- Maximum Value: 2047.0
- Default Value: 0
- Units: RPM/V
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorKV
in interfaceHasTalonSignals
- Returns:
- MotorKV Status Signal Object
-
getMotorKV
public StatusSignal<edu.wpi.first.units.measure.Per<AngularVelocityUnit,VoltageUnit>> getMotorKV(boolean refresh) The velocity constant (K_V) of the motor.- Minimum Value: 0.0
- Maximum Value: 2047.0
- Default Value: 0
- Units: RPM/V
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorKV
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- MotorKV Status Signal Object
-
getMotorStallCurrent
The stall current of the motor at 12 V output.- Minimum Value: 0.0
- Maximum Value: 1023.0
- Default Value: 0
- Units: A
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorStallCurrent
in interfaceHasTalonSignals
- Returns:
- MotorStallCurrent Status Signal Object
-
getMotorStallCurrent
The stall current of the motor at 12 V output.- Minimum Value: 0.0
- Maximum Value: 1023.0
- Default Value: 0
- Units: A
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getMotorStallCurrent
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- MotorStallCurrent Status Signal Object
-
getBridgeOutput
The applied output of the bridge. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getBridgeOutput
in interfaceHasTalonSignals
- Returns:
- BridgeOutput Status Signal Object
-
getBridgeOutput
The applied output of the bridge. Default Rates:- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getBridgeOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- BridgeOutput Status Signal Object
-
getIsProLicensed
Whether the device is Phoenix Pro licensed.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getIsProLicensed
in interfaceHasTalonSignals
- Returns:
- IsProLicensed Status Signal Object
-
getIsProLicensed
Whether the device is Phoenix Pro licensed.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getIsProLicensed
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- IsProLicensed Status Signal Object
-
getAncillaryDeviceTemp
Temperature of device from second sensor.Newer versions of Talon have multiple temperature measurement methods.
- Minimum Value: 0.0
- Maximum Value: 255.0
- Default Value: 0
- Units: ℃
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getAncillaryDeviceTemp
in interfaceHasTalonSignals
- Returns:
- AncillaryDeviceTemp Status Signal Object
-
getAncillaryDeviceTemp
public StatusSignal<edu.wpi.first.units.measure.Temperature> getAncillaryDeviceTemp(boolean refresh) Temperature of device from second sensor.Newer versions of Talon have multiple temperature measurement methods.
- Minimum Value: 0.0
- Maximum Value: 255.0
- Default Value: 0
- Units: ℃
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getAncillaryDeviceTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- AncillaryDeviceTemp Status Signal Object
-
getConnectedMotor
The type of motor attached to the Talon.This can be used to determine what motor is attached to the Talon FX. Return will be "Unknown" if firmware is too old or device is not present. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getConnectedMotor
in interfaceHasTalonSignals
- Returns:
- ConnectedMotor Status Signal Object
-
getConnectedMotor
The type of motor attached to the Talon.This can be used to determine what motor is attached to the Talon FX. Return will be "Unknown" if firmware is too old or device is not present. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getConnectedMotor
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ConnectedMotor Status Signal Object
-
getFault_Hardware
Hardware fault occurred- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_Hardware
in interfaceHasTalonSignals
- Returns:
- Fault_Hardware Status Signal Object
-
getFault_Hardware
Hardware fault occurred- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_Hardware
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_Hardware Status Signal Object
-
getStickyFault_Hardware
Hardware fault occurred- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_Hardware
in interfaceHasTalonSignals
- Returns:
- StickyFault_Hardware Status Signal Object
-
getStickyFault_Hardware
Hardware fault occurred- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_Hardware
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_Hardware Status Signal Object
-
getFault_ProcTemp
Processor temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ProcTemp
in interfaceHasTalonSignals
- Returns:
- Fault_ProcTemp Status Signal Object
-
getFault_ProcTemp
Processor temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ProcTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_ProcTemp Status Signal Object
-
getStickyFault_ProcTemp
Processor temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ProcTemp
in interfaceHasTalonSignals
- Returns:
- StickyFault_ProcTemp Status Signal Object
-
getStickyFault_ProcTemp
Processor temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ProcTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_ProcTemp Status Signal Object
-
getFault_DeviceTemp
Device temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_DeviceTemp
in interfaceHasTalonSignals
- Returns:
- Fault_DeviceTemp Status Signal Object
-
getFault_DeviceTemp
Device temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_DeviceTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_DeviceTemp Status Signal Object
-
getStickyFault_DeviceTemp
Device temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_DeviceTemp
in interfaceHasTalonSignals
- Returns:
- StickyFault_DeviceTemp Status Signal Object
-
getStickyFault_DeviceTemp
Device temperature exceeded limit- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_DeviceTemp
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_DeviceTemp Status Signal Object
-
getFault_Undervoltage
Device supply voltage dropped to near brownout levels- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_Undervoltage
in interfaceHasTalonSignals
- Returns:
- Fault_Undervoltage Status Signal Object
-
getFault_Undervoltage
Device supply voltage dropped to near brownout levels- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_Undervoltage
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_Undervoltage Status Signal Object
-
getStickyFault_Undervoltage
Device supply voltage dropped to near brownout levels- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_Undervoltage
in interfaceHasTalonSignals
- Returns:
- StickyFault_Undervoltage Status Signal Object
-
getStickyFault_Undervoltage
Device supply voltage dropped to near brownout levels- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_Undervoltage
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_Undervoltage Status Signal Object
-
getFault_BootDuringEnable
Device boot while detecting the enable signal- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_BootDuringEnable
in interfaceHasTalonSignals
- Returns:
- Fault_BootDuringEnable Status Signal Object
-
getFault_BootDuringEnable
Device boot while detecting the enable signal- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_BootDuringEnable
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_BootDuringEnable Status Signal Object
-
getStickyFault_BootDuringEnable
Device boot while detecting the enable signal- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_BootDuringEnable
in interfaceHasTalonSignals
- Returns:
- StickyFault_BootDuringEnable Status Signal Object
-
getStickyFault_BootDuringEnable
Device boot while detecting the enable signal- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_BootDuringEnable
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_BootDuringEnable Status Signal Object
-
getFault_UnlicensedFeatureInUse
An unlicensed feature is in use, device may not behave as expected.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_UnlicensedFeatureInUse
in interfaceHasTalonSignals
- Returns:
- Fault_UnlicensedFeatureInUse Status Signal Object
-
getFault_UnlicensedFeatureInUse
An unlicensed feature is in use, device may not behave as expected.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_UnlicensedFeatureInUse
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_UnlicensedFeatureInUse Status Signal Object
-
getStickyFault_UnlicensedFeatureInUse
An unlicensed feature is in use, device may not behave as expected.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_UnlicensedFeatureInUse
in interfaceHasTalonSignals
- Returns:
- StickyFault_UnlicensedFeatureInUse Status Signal Object
-
getStickyFault_UnlicensedFeatureInUse
An unlicensed feature is in use, device may not behave as expected.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_UnlicensedFeatureInUse
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_UnlicensedFeatureInUse Status Signal Object
-
getFault_BridgeBrownout
Bridge was disabled most likely due to supply voltage dropping too low.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_BridgeBrownout
in interfaceHasTalonSignals
- Returns:
- Fault_BridgeBrownout Status Signal Object
-
getFault_BridgeBrownout
Bridge was disabled most likely due to supply voltage dropping too low.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_BridgeBrownout
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_BridgeBrownout Status Signal Object
-
getStickyFault_BridgeBrownout
Bridge was disabled most likely due to supply voltage dropping too low.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_BridgeBrownout
in interfaceHasTalonSignals
- Returns:
- StickyFault_BridgeBrownout Status Signal Object
-
getStickyFault_BridgeBrownout
Bridge was disabled most likely due to supply voltage dropping too low.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_BridgeBrownout
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_BridgeBrownout Status Signal Object
-
getFault_RemoteSensorReset
The remote sensor has reset.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_RemoteSensorReset
in interfaceHasTalonSignals
- Returns:
- Fault_RemoteSensorReset Status Signal Object
-
getFault_RemoteSensorReset
The remote sensor has reset.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_RemoteSensorReset
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_RemoteSensorReset Status Signal Object
-
getStickyFault_RemoteSensorReset
The remote sensor has reset.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_RemoteSensorReset
in interfaceHasTalonSignals
- Returns:
- StickyFault_RemoteSensorReset Status Signal Object
-
getStickyFault_RemoteSensorReset
The remote sensor has reset.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_RemoteSensorReset
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_RemoteSensorReset Status Signal Object
-
getFault_MissingDifferentialFX
The remote Talon used for differential control is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_MissingDifferentialFX
in interfaceHasTalonSignals
- Returns:
- Fault_MissingDifferentialFX Status Signal Object
-
getFault_MissingDifferentialFX
The remote Talon used for differential control is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_MissingDifferentialFX
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_MissingDifferentialFX Status Signal Object
-
getStickyFault_MissingDifferentialFX
The remote Talon used for differential control is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_MissingDifferentialFX
in interfaceHasTalonSignals
- Returns:
- StickyFault_MissingDifferentialFX Status Signal Object
-
getStickyFault_MissingDifferentialFX
The remote Talon used for differential control is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_MissingDifferentialFX
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_MissingDifferentialFX Status Signal Object
-
getFault_RemoteSensorPosOverflow
The remote sensor position has overflowed. Because of the nature of remote sensors, it is possible for the remote sensor position to overflow beyond what is supported by the status signal frame. However, this is rare and cannot occur over the course of an FRC match under normal use.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_RemoteSensorPosOverflow
in interfaceHasTalonSignals
- Returns:
- Fault_RemoteSensorPosOverflow Status Signal Object
-
getFault_RemoteSensorPosOverflow
The remote sensor position has overflowed. Because of the nature of remote sensors, it is possible for the remote sensor position to overflow beyond what is supported by the status signal frame. However, this is rare and cannot occur over the course of an FRC match under normal use.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_RemoteSensorPosOverflow
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_RemoteSensorPosOverflow Status Signal Object
-
getStickyFault_RemoteSensorPosOverflow
The remote sensor position has overflowed. Because of the nature of remote sensors, it is possible for the remote sensor position to overflow beyond what is supported by the status signal frame. However, this is rare and cannot occur over the course of an FRC match under normal use.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_RemoteSensorPosOverflow
in interfaceHasTalonSignals
- Returns:
- StickyFault_RemoteSensorPosOverflow Status Signal Object
-
getStickyFault_RemoteSensorPosOverflow
The remote sensor position has overflowed. Because of the nature of remote sensors, it is possible for the remote sensor position to overflow beyond what is supported by the status signal frame. However, this is rare and cannot occur over the course of an FRC match under normal use.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_RemoteSensorPosOverflow
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_RemoteSensorPosOverflow Status Signal Object
-
getFault_OverSupplyV
Supply Voltage has exceeded the maximum voltage rating of device.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_OverSupplyV
in interfaceHasTalonSignals
- Returns:
- Fault_OverSupplyV Status Signal Object
-
getFault_OverSupplyV
Supply Voltage has exceeded the maximum voltage rating of device.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_OverSupplyV
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_OverSupplyV Status Signal Object
-
getStickyFault_OverSupplyV
Supply Voltage has exceeded the maximum voltage rating of device.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_OverSupplyV
in interfaceHasTalonSignals
- Returns:
- StickyFault_OverSupplyV Status Signal Object
-
getStickyFault_OverSupplyV
Supply Voltage has exceeded the maximum voltage rating of device.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_OverSupplyV
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_OverSupplyV Status Signal Object
-
getFault_UnstableSupplyV
Supply Voltage is unstable. Ensure you are using a battery and current limited power supply.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_UnstableSupplyV
in interfaceHasTalonSignals
- Returns:
- Fault_UnstableSupplyV Status Signal Object
-
getFault_UnstableSupplyV
Supply Voltage is unstable. Ensure you are using a battery and current limited power supply.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_UnstableSupplyV
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_UnstableSupplyV Status Signal Object
-
getStickyFault_UnstableSupplyV
Supply Voltage is unstable. Ensure you are using a battery and current limited power supply.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_UnstableSupplyV
in interfaceHasTalonSignals
- Returns:
- StickyFault_UnstableSupplyV Status Signal Object
-
getStickyFault_UnstableSupplyV
Supply Voltage is unstable. Ensure you are using a battery and current limited power supply.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_UnstableSupplyV
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_UnstableSupplyV Status Signal Object
-
getFault_ReverseHardLimit
Reverse limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ReverseHardLimit
in interfaceHasTalonSignals
- Returns:
- Fault_ReverseHardLimit Status Signal Object
-
getFault_ReverseHardLimit
Reverse limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ReverseHardLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_ReverseHardLimit Status Signal Object
-
getStickyFault_ReverseHardLimit
Reverse limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ReverseHardLimit
in interfaceHasTalonSignals
- Returns:
- StickyFault_ReverseHardLimit Status Signal Object
-
getStickyFault_ReverseHardLimit
Reverse limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ReverseHardLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_ReverseHardLimit Status Signal Object
-
getFault_ForwardHardLimit
Forward limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ForwardHardLimit
in interfaceHasTalonSignals
- Returns:
- Fault_ForwardHardLimit Status Signal Object
-
getFault_ForwardHardLimit
Forward limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ForwardHardLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_ForwardHardLimit Status Signal Object
-
getStickyFault_ForwardHardLimit
Forward limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ForwardHardLimit
in interfaceHasTalonSignals
- Returns:
- StickyFault_ForwardHardLimit Status Signal Object
-
getStickyFault_ForwardHardLimit
Forward limit switch has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ForwardHardLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_ForwardHardLimit Status Signal Object
-
getFault_ReverseSoftLimit
Reverse soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ReverseSoftLimit
in interfaceHasTalonSignals
- Returns:
- Fault_ReverseSoftLimit Status Signal Object
-
getFault_ReverseSoftLimit
Reverse soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ReverseSoftLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_ReverseSoftLimit Status Signal Object
-
getStickyFault_ReverseSoftLimit
Reverse soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ReverseSoftLimit
in interfaceHasTalonSignals
- Returns:
- StickyFault_ReverseSoftLimit Status Signal Object
-
getStickyFault_ReverseSoftLimit
Reverse soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ReverseSoftLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_ReverseSoftLimit Status Signal Object
-
getFault_ForwardSoftLimit
Forward soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ForwardSoftLimit
in interfaceHasTalonSignals
- Returns:
- Fault_ForwardSoftLimit Status Signal Object
-
getFault_ForwardSoftLimit
Forward soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_ForwardSoftLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_ForwardSoftLimit Status Signal Object
-
getStickyFault_ForwardSoftLimit
Forward soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ForwardSoftLimit
in interfaceHasTalonSignals
- Returns:
- StickyFault_ForwardSoftLimit Status Signal Object
-
getStickyFault_ForwardSoftLimit
Forward soft limit has been asserted. Output is set to neutral.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_ForwardSoftLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_ForwardSoftLimit Status Signal Object
-
getFault_MissingSoftLimitRemote
The remote soft limit device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_MissingSoftLimitRemote
in interfaceHasTalonSignals
- Returns:
- Fault_MissingSoftLimitRemote Status Signal Object
-
getFault_MissingSoftLimitRemote
The remote soft limit device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_MissingSoftLimitRemote
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_MissingSoftLimitRemote Status Signal Object
-
getStickyFault_MissingSoftLimitRemote
The remote soft limit device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_MissingSoftLimitRemote
in interfaceHasTalonSignals
- Returns:
- StickyFault_MissingSoftLimitRemote Status Signal Object
-
getStickyFault_MissingSoftLimitRemote
The remote soft limit device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_MissingSoftLimitRemote
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_MissingSoftLimitRemote Status Signal Object
-
getFault_MissingHardLimitRemote
The remote limit switch device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_MissingHardLimitRemote
in interfaceHasTalonSignals
- Returns:
- Fault_MissingHardLimitRemote Status Signal Object
-
getFault_MissingHardLimitRemote
The remote limit switch device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_MissingHardLimitRemote
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_MissingHardLimitRemote Status Signal Object
-
getStickyFault_MissingHardLimitRemote
The remote limit switch device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_MissingHardLimitRemote
in interfaceHasTalonSignals
- Returns:
- StickyFault_MissingHardLimitRemote Status Signal Object
-
getStickyFault_MissingHardLimitRemote
The remote limit switch device is not present on CAN Bus.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_MissingHardLimitRemote
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_MissingHardLimitRemote Status Signal Object
-
getFault_RemoteSensorDataInvalid
The remote sensor's data is no longer trusted. This can happen if the remote sensor disappears from the CAN bus or if the remote sensor indicates its data is no longer valid, such as when a CANcoder's magnet strength falls into the "red" range.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_RemoteSensorDataInvalid
in interfaceHasTalonSignals
- Returns:
- Fault_RemoteSensorDataInvalid Status Signal Object
-
getFault_RemoteSensorDataInvalid
The remote sensor's data is no longer trusted. This can happen if the remote sensor disappears from the CAN bus or if the remote sensor indicates its data is no longer valid, such as when a CANcoder's magnet strength falls into the "red" range.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_RemoteSensorDataInvalid
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_RemoteSensorDataInvalid Status Signal Object
-
getStickyFault_RemoteSensorDataInvalid
The remote sensor's data is no longer trusted. This can happen if the remote sensor disappears from the CAN bus or if the remote sensor indicates its data is no longer valid, such as when a CANcoder's magnet strength falls into the "red" range.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_RemoteSensorDataInvalid
in interfaceHasTalonSignals
- Returns:
- StickyFault_RemoteSensorDataInvalid Status Signal Object
-
getStickyFault_RemoteSensorDataInvalid
The remote sensor's data is no longer trusted. This can happen if the remote sensor disappears from the CAN bus or if the remote sensor indicates its data is no longer valid, such as when a CANcoder's magnet strength falls into the "red" range.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_RemoteSensorDataInvalid
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_RemoteSensorDataInvalid Status Signal Object
-
getFault_FusedSensorOutOfSync
The remote sensor used for fusion has fallen out of sync to the local sensor. A re-synchronization has occurred, which may cause a discontinuity. This typically happens if there is significant slop in the mechanism, or if the RotorToSensorRatio configuration parameter is incorrect.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_FusedSensorOutOfSync
in interfaceHasTalonSignals
- Returns:
- Fault_FusedSensorOutOfSync Status Signal Object
-
getFault_FusedSensorOutOfSync
The remote sensor used for fusion has fallen out of sync to the local sensor. A re-synchronization has occurred, which may cause a discontinuity. This typically happens if there is significant slop in the mechanism, or if the RotorToSensorRatio configuration parameter is incorrect.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_FusedSensorOutOfSync
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_FusedSensorOutOfSync Status Signal Object
-
getStickyFault_FusedSensorOutOfSync
The remote sensor used for fusion has fallen out of sync to the local sensor. A re-synchronization has occurred, which may cause a discontinuity. This typically happens if there is significant slop in the mechanism, or if the RotorToSensorRatio configuration parameter is incorrect.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_FusedSensorOutOfSync
in interfaceHasTalonSignals
- Returns:
- StickyFault_FusedSensorOutOfSync Status Signal Object
-
getStickyFault_FusedSensorOutOfSync
The remote sensor used for fusion has fallen out of sync to the local sensor. A re-synchronization has occurred, which may cause a discontinuity. This typically happens if there is significant slop in the mechanism, or if the RotorToSensorRatio configuration parameter is incorrect.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_FusedSensorOutOfSync
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_FusedSensorOutOfSync Status Signal Object
-
getFault_StatorCurrLimit
Stator current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_StatorCurrLimit
in interfaceHasTalonSignals
- Returns:
- Fault_StatorCurrLimit Status Signal Object
-
getFault_StatorCurrLimit
Stator current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_StatorCurrLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_StatorCurrLimit Status Signal Object
-
getStickyFault_StatorCurrLimit
Stator current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_StatorCurrLimit
in interfaceHasTalonSignals
- Returns:
- StickyFault_StatorCurrLimit Status Signal Object
-
getStickyFault_StatorCurrLimit
Stator current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_StatorCurrLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_StatorCurrLimit Status Signal Object
-
getFault_SupplyCurrLimit
Supply current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_SupplyCurrLimit
in interfaceHasTalonSignals
- Returns:
- Fault_SupplyCurrLimit Status Signal Object
-
getFault_SupplyCurrLimit
Supply current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_SupplyCurrLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_SupplyCurrLimit Status Signal Object
-
getStickyFault_SupplyCurrLimit
Supply current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_SupplyCurrLimit
in interfaceHasTalonSignals
- Returns:
- StickyFault_SupplyCurrLimit Status Signal Object
-
getStickyFault_SupplyCurrLimit
Supply current limit occured.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_SupplyCurrLimit
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_SupplyCurrLimit Status Signal Object
-
getFault_UsingFusedCANcoderWhileUnlicensed
Using Fused CANcoder feature while unlicensed. Device has fallen back to remote CANcoder.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_UsingFusedCANcoderWhileUnlicensed
in interfaceHasTalonSignals
- Returns:
- Fault_UsingFusedCANcoderWhileUnlicensed Status Signal Object
-
getFault_UsingFusedCANcoderWhileUnlicensed
Using Fused CANcoder feature while unlicensed. Device has fallen back to remote CANcoder.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_UsingFusedCANcoderWhileUnlicensed
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_UsingFusedCANcoderWhileUnlicensed Status Signal Object
-
getStickyFault_UsingFusedCANcoderWhileUnlicensed
Using Fused CANcoder feature while unlicensed. Device has fallen back to remote CANcoder.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_UsingFusedCANcoderWhileUnlicensed
in interfaceHasTalonSignals
- Returns:
- StickyFault_UsingFusedCANcoderWhileUnlicensed Status Signal Object
-
getStickyFault_UsingFusedCANcoderWhileUnlicensed
Using Fused CANcoder feature while unlicensed. Device has fallen back to remote CANcoder.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_UsingFusedCANcoderWhileUnlicensed
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_UsingFusedCANcoderWhileUnlicensed Status Signal Object
-
getFault_StaticBrakeDisabled
Static brake was momentarily disabled due to excessive braking current while disabled.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_StaticBrakeDisabled
in interfaceHasTalonSignals
- Returns:
- Fault_StaticBrakeDisabled Status Signal Object
-
getFault_StaticBrakeDisabled
Static brake was momentarily disabled due to excessive braking current while disabled.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getFault_StaticBrakeDisabled
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- Fault_StaticBrakeDisabled Status Signal Object
-
getStickyFault_StaticBrakeDisabled
Static brake was momentarily disabled due to excessive braking current while disabled.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_StaticBrakeDisabled
in interfaceHasTalonSignals
- Returns:
- StickyFault_StaticBrakeDisabled Status Signal Object
-
getStickyFault_StaticBrakeDisabled
Static brake was momentarily disabled due to excessive braking current while disabled.- Default Value: False
- CAN: 4.0 Hz
This refreshes and returns a cached StatusSignal object.
- Specified by:
getStickyFault_StaticBrakeDisabled
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- StickyFault_StaticBrakeDisabled Status Signal Object
-
getClosedLoopProportionalOutput
Closed loop proportional componentThe portion of the closed loop output that is the proportional to the error. Alternatively, the p-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopProportionalOutput
in interfaceHasTalonSignals
- Returns:
- ClosedLoopProportionalOutput Status Signal object
-
getClosedLoopProportionalOutput
Closed loop proportional componentThe portion of the closed loop output that is the proportional to the error. Alternatively, the p-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopProportionalOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopProportionalOutput Status Signal object
-
getClosedLoopIntegratedOutput
Closed loop integrated componentThe portion of the closed loop output that is proportional to the integrated error. Alternatively, the i-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopIntegratedOutput
in interfaceHasTalonSignals
- Returns:
- ClosedLoopIntegratedOutput Status Signal object
-
getClosedLoopIntegratedOutput
Closed loop integrated componentThe portion of the closed loop output that is proportional to the integrated error. Alternatively, the i-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopIntegratedOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopIntegratedOutput Status Signal object
-
getClosedLoopFeedForward
Feedforward passed by the userThis is the general feedforward that the user provides for the closed loop. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopFeedForward
in interfaceHasTalonSignals
- Returns:
- ClosedLoopFeedForward Status Signal object
-
getClosedLoopFeedForward
Feedforward passed by the userThis is the general feedforward that the user provides for the closed loop. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopFeedForward
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopFeedForward Status Signal object
-
getClosedLoopDerivativeOutput
Closed loop derivative componentThe portion of the closed loop output that is the proportional to the deriviative the error. Alternatively, the d-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopDerivativeOutput
in interfaceHasTalonSignals
- Returns:
- ClosedLoopDerivativeOutput Status Signal object
-
getClosedLoopDerivativeOutput
Closed loop derivative componentThe portion of the closed loop output that is the proportional to the deriviative the error. Alternatively, the d-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopDerivativeOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopDerivativeOutput Status Signal object
-
getClosedLoopOutput
Closed loop total outputThe total output of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopOutput
in interfaceHasTalonSignals
- Returns:
- ClosedLoopOutput Status Signal object
-
getClosedLoopOutput
Closed loop total outputThe total output of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopOutput Status Signal object
-
getClosedLoopReference
Value that the closed loop is targetingThis is the value that the closed loop PID controller targets. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopReference
in interfaceHasTalonSignals
- Returns:
- ClosedLoopReference Status Signal object
-
getClosedLoopReference
Value that the closed loop is targetingThis is the value that the closed loop PID controller targets. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopReference
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopReference Status Signal object
-
getClosedLoopReferenceSlope
Derivative of the target that the closed loop is targetingThis is the change in the closed loop reference. This may be used in the feed-forward calculation, the derivative-error, or in application of the signage for kS. Typically, this represents the target velocity during Motion Magic®. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopReferenceSlope
in interfaceHasTalonSignals
- Returns:
- ClosedLoopReferenceSlope Status Signal object
-
getClosedLoopReferenceSlope
Derivative of the target that the closed loop is targetingThis is the change in the closed loop reference. This may be used in the feed-forward calculation, the derivative-error, or in application of the signage for kS. Typically, this represents the target velocity during Motion Magic®. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopReferenceSlope
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopReferenceSlope Status Signal object
-
getClosedLoopError
The difference between target reference and current measurementThis is the value that is treated as the error in the PID loop. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopError
in interfaceHasTalonSignals
- Returns:
- ClosedLoopError Status Signal object
-
getClosedLoopError
The difference between target reference and current measurementThis is the value that is treated as the error in the PID loop. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getClosedLoopError
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- ClosedLoopError Status Signal object
-
getDifferentialOutput
The calculated motor output for differential followers.This is a torque request when using the TorqueCurrentFOC control output type, and a duty cycle in all other control types. Default Rates:
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialOutput
in interfaceHasTalonSignals
- Returns:
- DifferentialOutput Status Signal object
-
getDifferentialOutput
The calculated motor output for differential followers.This is a torque request when using the TorqueCurrentFOC control output type, and a duty cycle in all other control types. Default Rates:
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialOutput Status Signal object
-
getDifferentialClosedLoopProportionalOutput
Differential closed loop proportional componentThe portion of the differential closed loop output that is the proportional to the error. Alternatively, the p-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopProportionalOutput
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopProportionalOutput Status Signal object
-
getDifferentialClosedLoopProportionalOutput
Differential closed loop proportional componentThe portion of the differential closed loop output that is the proportional to the error. Alternatively, the p-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopProportionalOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopProportionalOutput Status Signal object
-
getDifferentialClosedLoopIntegratedOutput
Differential closed loop integrated componentThe portion of the differential closed loop output that is proportional to the integrated error. Alternatively, the i-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopIntegratedOutput
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopIntegratedOutput Status Signal object
-
getDifferentialClosedLoopIntegratedOutput
Differential closed loop integrated componentThe portion of the differential closed loop output that is proportional to the integrated error. Alternatively, the i-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopIntegratedOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopIntegratedOutput Status Signal object
-
getDifferentialClosedLoopFeedForward
Differential Feedforward passed by the userThis is the general feedforward that the user provides for the differential closed loop. Default Rates:
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopFeedForward
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopFeedForward Status Signal object
-
getDifferentialClosedLoopFeedForward
Differential Feedforward passed by the userThis is the general feedforward that the user provides for the differential closed loop. Default Rates:
- CAN 2.0: 100.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopFeedForward
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopFeedForward Status Signal object
-
getDifferentialClosedLoopDerivativeOutput
Differential closed loop derivative componentThe portion of the differential closed loop output that is the proportional to the deriviative the error. Alternatively, the d-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopDerivativeOutput
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopDerivativeOutput Status Signal object
-
getDifferentialClosedLoopDerivativeOutput
Differential closed loop derivative componentThe portion of the differential closed loop output that is the proportional to the deriviative the error. Alternatively, the d-Contribution of the closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopDerivativeOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopDerivativeOutput Status Signal object
-
getDifferentialClosedLoopOutput
Differential closed loop total outputThe total output of the differential closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopOutput
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopOutput Status Signal object
-
getDifferentialClosedLoopOutput
Differential closed loop total outputThe total output of the differential closed loop output. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopOutput
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopOutput Status Signal object
-
getDifferentialClosedLoopReference
Value that the differential closed loop is targetingThis is the value that the differential closed loop PID controller targets. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopReference
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopReference Status Signal object
-
getDifferentialClosedLoopReference
Value that the differential closed loop is targetingThis is the value that the differential closed loop PID controller targets. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopReference
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopReference Status Signal object
-
getDifferentialClosedLoopReferenceSlope
Derivative of the target that the differential closed loop is targetingThis is the change in the closed loop reference. This may be used in the feed-forward calculation, the derivative-error, or in application of the signage for kS. Typically, this represents the target velocity during Motion Magic®. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopReferenceSlope
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopReferenceSlope Status Signal object
-
getDifferentialClosedLoopReferenceSlope
Derivative of the target that the differential closed loop is targetingThis is the change in the closed loop reference. This may be used in the feed-forward calculation, the derivative-error, or in application of the signage for kS. Typically, this represents the target velocity during Motion Magic®. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopReferenceSlope
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopReferenceSlope Status Signal object
-
getDifferentialClosedLoopError
The difference between target differential reference and current measurementThis is the value that is treated as the error in the differential PID loop. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopError
in interfaceHasTalonSignals
- Returns:
- DifferentialClosedLoopError Status Signal object
-
getDifferentialClosedLoopError
The difference between target differential reference and current measurementThis is the value that is treated as the error in the differential PID loop. Default Rates:
- CAN 2.0: 4.0 Hz
- CAN FD: 100.0 Hz (TimeSynced with Pro)
This refreshes and returns a cached StatusSignal object.
- Specified by:
getDifferentialClosedLoopError
in interfaceHasTalonSignals
- Parameters:
refresh
- Whether to refresh the StatusSignal before returning it; defaults to true- Returns:
- DifferentialClosedLoopError Status Signal object
-
setControl
Request a specified motor duty cycle.This control mode will output a proportion of the supplied voltage which is supplied by the user.
- DutyCycleOut Parameters:
- Output: Proportion of supply voltage to apply in fractional units between -1 and +1
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DutyCycleOut Parameters:
-
setControl
Request a specified motor current (field oriented control).This control request will drive the motor to the requested motor (stator) current value. This leverages field oriented control (FOC), which means greater peak power than what is documented. This scales to torque based on Motor's kT constant.
- TorqueCurrentFOC Parameters:
- Output: Amount of motor current in Amperes
- MaxAbsDutyCycle: The maximum absolute motor output that can be applied, which effectively limits the velocity. For example, 0.50 means no more than 50% output in either direction. This is useful for preventing the motor from spinning to its terminal velocity when there is no external torque applied unto the rotor. Note this is absolute maximum, so the value should be between zero and one.
- Deadband: Deadband in Amperes. If torque request is within deadband, the bridge output is neutral. If deadband is set to zero then there is effectively no deadband. Note if deadband is zero, a free spinning motor will spin for quite a while as the firmware attempts to hold the motor's bemf. If user expects motor to cease spinning quickly with a demand of zero, we recommend a deadband of one Ampere. This value will be converted to an integral value of amps.
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- TorqueCurrentFOC Parameters:
-
setControl
Request a specified voltage.This control mode will attempt to apply the specified voltage to the motor. If the supply voltage is below the requested voltage, the motor controller will output the supply voltage.
- VoltageOut Parameters:
- Output: Voltage to attempt to drive at
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- VoltageOut Parameters:
-
setControl
Request PID to target position with duty cycle feedforward.This control mode will set the motor's position setpoint to the position specified by the user. In addition, it will apply an additional duty cycle as an arbitrary feedforward value.
- PositionDutyCycle Parameters:
- Position: Position to drive toward in rotations.
- Velocity: Velocity to drive toward in rotations per second. This is typically used for motion profiles generated by the robot program.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in fractional units between -1 and +1.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- PositionDutyCycle Parameters:
-
setControl
Request PID to target position with voltage feedforwardThis control mode will set the motor's position setpoint to the position specified by the user. In addition, it will apply an additional voltage as an arbitrary feedforward value.
- PositionVoltage Parameters:
- Position: Position to drive toward in rotations.
- Velocity: Velocity to drive toward in rotations per second. This is typically used for motion profiles generated by the robot program.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in volts
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- PositionVoltage Parameters:
-
setControl
Request PID to target position with torque current feedforward.This control mode will set the motor's position setpoint to the position specified by the user. In addition, it will apply an additional torque current as an arbitrary feedforward value.
- PositionTorqueCurrentFOC Parameters:
- Position: Position to drive toward in rotations.
- Velocity: Velocity to drive toward in rotations per second. This is typically used for motion profiles generated by the robot program.
- FeedForward: Feedforward to apply in torque current in Amperes. User can use motor's kT to scale Newton-meter to Amperes.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- PositionTorqueCurrentFOC Parameters:
-
setControl
Request PID to target velocity with duty cycle feedforward.This control mode will set the motor's velocity setpoint to the velocity specified by the user. In addition, it will apply an additional voltage as an arbitrary feedforward value.
- VelocityDutyCycle Parameters:
- Velocity: Velocity to drive toward in rotations per second.
- Acceleration: Acceleration to drive toward in rotations per second squared. This is typically used for motion profiles generated by the robot program.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in fractional units between -1 and +1.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- VelocityDutyCycle Parameters:
-
setControl
Request PID to target velocity with voltage feedforward.This control mode will set the motor's velocity setpoint to the velocity specified by the user. In addition, it will apply an additional voltage as an arbitrary feedforward value.
- VelocityVoltage Parameters:
- Velocity: Velocity to drive toward in rotations per second.
- Acceleration: Acceleration to drive toward in rotations per second squared. This is typically used for motion profiles generated by the robot program.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in volts
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- VelocityVoltage Parameters:
-
setControl
Request PID to target velocity with torque current feedforward.This control mode will set the motor's velocity setpoint to the velocity specified by the user. In addition, it will apply an additional torque current as an arbitrary feedforward value.
- VelocityTorqueCurrentFOC Parameters:
- Velocity: Velocity to drive toward in rotations per second.
- Acceleration: Acceleration to drive toward in rotations per second squared. This is typically used for motion profiles generated by the robot program.
- FeedForward: Feedforward to apply in torque current in Amperes. User can use motor's kT to scale Newton-meter to Amperes.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- VelocityTorqueCurrentFOC Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile. Users can optionally provide a duty cycle feedforward.Motion Magic® produces a motion profile in real-time while attempting to honor the Cruise Velocity, Acceleration, and (optional) Jerk specified via the Motion Magic® configuration values. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is duty cycle based, so relevant closed-loop gains will use fractional duty cycle for the numerator: +1.0 represents full forward output.
- MotionMagicDutyCycle Parameters:
- Position: Position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in fractional units between -1 and +1.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicDutyCycle Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile. Users can optionally provide a voltage feedforward.Motion Magic® produces a motion profile in real-time while attempting to honor the Cruise Velocity, Acceleration, and (optional) Jerk specified via the Motion Magic® configuration values. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is voltage-based, so relevant closed-loop gains will use Volts for the numerator.
- MotionMagicVoltage Parameters:
- Position: Position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in volts
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicVoltage Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile. Users can optionally provide a torque current feedforward.Motion Magic® produces a motion profile in real-time while attempting to honor the Cruise Velocity, Acceleration, and (optional) Jerk specified via the Motion Magic® configuration values. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is based on torque current, so relevant closed-loop gains will use Amperes for the numerator.
- MotionMagicTorqueCurrentFOC Parameters:
- Position: Position to drive toward in rotations.
- FeedForward: Feedforward to apply in torque current in Amperes. User can use motor's kT to scale Newton-meter to Amperes.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicTorqueCurrentFOC Parameters:
-
setControl
Request a specified motor duty cycle with a differential position closed-loop.This control mode will output a proportion of the supplied voltage which is supplied by the user. It will also set the motor's differential position setpoint to the specified position.
- DifferentialDutyCycle Parameters:
- TargetOutput: Proportion of supply voltage to apply in fractional units between -1 and +1
- DifferentialPosition: Differential position to drive towards in rotations
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialDutyCycle Parameters:
-
setControl
Request a specified voltage with a differential position closed-loop.This control mode will attempt to apply the specified voltage to the motor. If the supply voltage is below the requested voltage, the motor controller will output the supply voltage. It will also set the motor's differential position setpoint to the specified position.
- DifferentialVoltage Parameters:
- TargetOutput: Voltage to attempt to drive at
- DifferentialPosition: Differential position to drive towards in rotations
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialVoltage Parameters:
-
setControl
Request PID to target position with a differential position setpoint.This control mode will set the motor's position setpoint to the position specified by the user. It will also set the motor's differential position setpoint to the specified position.
- DifferentialPositionDutyCycle Parameters:
- TargetPosition: Average position to drive toward in rotations.
- DifferentialPosition: Differential position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- TargetSlot: Select which gains are applied to the primary controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialPositionDutyCycle Parameters:
-
setControl
Request PID to target position with a differential position setpointThis control mode will set the motor's position setpoint to the position specified by the user. It will also set the motor's differential position setpoint to the specified position.
- DifferentialPositionVoltage Parameters:
- TargetPosition: Average position to drive toward in rotations.
- DifferentialPosition: Differential position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- TargetSlot: Select which gains are applied to the primary controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialPositionVoltage Parameters:
-
setControl
Request PID to target velocity with a differential position setpoint.This control mode will set the motor's velocity setpoint to the velocity specified by the user. It will also set the motor's differential position setpoint to the specified position.
- DifferentialVelocityDutyCycle Parameters:
- TargetVelocity: Average velocity to drive toward in rotations per second.
- DifferentialPosition: Differential position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- TargetSlot: Select which gains are applied to the primary controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialVelocityDutyCycle Parameters:
-
setControl
Request PID to target velocity with a differential position setpoint.This control mode will set the motor's velocity setpoint to the velocity specified by the user. It will also set the motor's differential position setpoint to the specified position.
- DifferentialVelocityVoltage Parameters:
- TargetVelocity: Average velocity to drive toward in rotations per second.
- DifferentialPosition: Differential position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- TargetSlot: Select which gains are applied to the primary controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialVelocityVoltage Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile, and PID to a differential position setpoint.Motion Magic® produces a motion profile in real-time while attempting to honor the Cruise Velocity, Acceleration, and (optional) Jerk specified via the Motion Magic® configuration values. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is duty cycle based, so relevant closed-loop gains will use fractional duty cycle for the numerator: +1.0 represents full forward output.
- DifferentialMotionMagicDutyCycle Parameters:
- TargetPosition: Average position to drive toward in rotations.
- DifferentialPosition: Differential position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- TargetSlot: Select which gains are applied to the primary controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialMotionMagicDutyCycle Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile, and PID to a differential position setpoint.Motion Magic® produces a motion profile in real-time while attempting to honor the Cruise Velocity, Acceleration, and (optional) Jerk specified via the Motion Magic® configuration values. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is voltage-based, so relevant closed-loop gains will use Volts for the numerator.
- DifferentialMotionMagicVoltage Parameters:
- TargetPosition: Average position to drive toward in rotations.
- DifferentialPosition: Differential position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- TargetSlot: Select which gains are applied to the primary controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- DifferentialSlot: Select which gains are applied to the differential controller by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialMotionMagicVoltage Parameters:
-
setControl
Follow the motor output of another Talon.If Talon is in torque control, the torque is copied - which will increase the total torque applied. If Talon is in percent supply output control, the duty cycle is matched. Motor direction either matches master's configured direction or opposes it based on OpposeMasterDirection.
- Follower Parameters:
- MasterID: Device ID of the master to follow.
- OpposeMasterDirection: Set to false for motor invert to match the master's configured Invert - which is typical when master and follower are mechanically linked and spin in the same direction. Set to true for motor invert to oppose the master's configured Invert - this is typical where the the master and follower mechanically spin in opposite directions.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Follower Parameters:
-
setControl
Follow the motor output of another Talon while ignoring the master's invert setting.If Talon is in torque control, the torque is copied - which will increase the total torque applied. If Talon is in percent supply output control, the duty cycle is matched. Motor direction is strictly determined by the configured invert and not the master. If you want motor direction to match or oppose the master, use FollowerRequest instead.
- StrictFollower Parameters:
- MasterID: Device ID of the master to follow.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- StrictFollower Parameters:
-
setControl
Follow the differential motor output of another Talon.If Talon is in torque control, the torque is copied - which will increase the total torque applied. If Talon is in percent supply output control, the duty cycle is matched. Motor direction either matches master's configured direction or opposes it based on OpposeMasterDirection.
- DifferentialFollower Parameters:
- MasterID: Device ID of the differential master to follow.
- OpposeMasterDirection: Set to false for motor invert to match the master's configured Invert - which is typical when master and follower are mechanically linked and spin in the same direction. Set to true for motor invert to oppose the master's configured Invert - this is typical where the the master and follower mechanically spin in opposite directions.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialFollower Parameters:
-
setControl
Follow the differential motor output of another Talon while ignoring the master's invert setting.If Talon is in torque control, the torque is copied - which will increase the total torque applied. If Talon is in percent supply output control, the duty cycle is matched. Motor direction is strictly determined by the configured invert and not the master. If you want motor direction to match or oppose the master, use FollowerRequest instead.
- DifferentialStrictFollower Parameters:
- MasterID: Device ID of the differential master to follow.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DifferentialStrictFollower Parameters:
-
setControl
Request neutral output of actuator. The applied brake type is determined by the NeutralMode configuration.- NeutralOut Parameters:
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- NeutralOut Parameters:
-
setControl
Request coast neutral output of actuator. The bridge is disabled and the rotor is allowed to coast.- CoastOut Parameters:
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- CoastOut Parameters:
-
setControl
Applies full neutral-brake by shorting motor leads together.- StaticBrake Parameters:
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- StaticBrake Parameters:
-
setControl
Plays a single tone at the user specified frequency.- MusicTone Parameters:
- AudioFrequency: Sound frequency to play. A value of zero will silence the device. The effective frequency range is 10-20000 Hz. Any nonzero frequency less than 10 Hz will be capped to 10 Hz. Any frequency above 20 kHz will be capped to 20 kHz.
- Specified by:
setControl
in interfaceSupportsMusic
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MusicTone Parameters:
-
setControl
Requests Motion Magic® to target a final velocity using a motion profile. This allows smooth transitions between velocity set points. Users can optionally provide a duty cycle feedforward.Motion Magic® Velocity produces a motion profile in real-time while attempting to honor the specified Acceleration and (optional) Jerk. This control mode does not use the CruiseVelocity, Expo_kV, or Expo_kA configs.
If the specified acceleration is zero, the Acceleration under Motion Magic® configuration parameter is used instead. This allows for runtime adjustment of acceleration for advanced users. Jerk is also specified in the Motion Magic® persistent configuration values. If Jerk is set to zero, Motion Magic® will produce a trapezoidal acceleration profile.
Target velocity can also be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is duty cycle based, so relevant closed-loop gains will use fractional duty cycle for the numerator: +1.0 represents full forward output.
- MotionMagicVelocityDutyCycle Parameters:
- Velocity: Target velocity to drive toward in rotations per second. This can be changed on-the fly.
- Acceleration: This is the absolute Acceleration to use generating the profile. If this parameter is zero, the Acceleration persistent configuration parameter is used instead. Acceleration is in rotations per second squared. If nonzero, the signage does not matter as the absolute value is used.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in fractional units between -1 and +1.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicVelocityDutyCycle Parameters:
-
setControl
Requests Motion Magic® to target a final velocity using a motion profile. This allows smooth transitions between velocity set points. Users can optionally provide a torque feedforward.Motion Magic® Velocity produces a motion profile in real-time while attempting to honor the specified Acceleration and (optional) Jerk. This control mode does not use the CruiseVelocity, Expo_kV, or Expo_kA configs.
If the specified acceleration is zero, the Acceleration under Motion Magic® configuration parameter is used instead. This allows for runtime adjustment of acceleration for advanced users. Jerk is also specified in the Motion Magic® persistent configuration values. If Jerk is set to zero, Motion Magic® will produce a trapezoidal acceleration profile.
Target velocity can also be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is based on torque current, so relevant closed-loop gains will use Amperes for the numerator.
- MotionMagicVelocityTorqueCurrentFOC Parameters:
- Velocity: Target velocity to drive toward in rotations per second. This can be changed on-the fly.
- Acceleration: This is the absolute Acceleration to use generating the profile. If this parameter is zero, the Acceleration persistent configuration parameter is used instead. Acceleration is in rotations per second squared. If nonzero, the signage does not matter as the absolute value is used.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in torque current in Amperes. User can use motor's kT to scale Newton-meter to Amperes.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicVelocityTorqueCurrentFOC Parameters:
-
setControl
Requests Motion Magic® to target a final velocity using a motion profile. This allows smooth transitions between velocity set points. Users can optionally provide a voltage feedforward.Motion Magic® Velocity produces a motion profile in real-time while attempting to honor the specified Acceleration and (optional) Jerk. This control mode does not use the CruiseVelocity, Expo_kV, or Expo_kA configs.
If the specified acceleration is zero, the Acceleration under Motion Magic® configuration parameter is used instead. This allows for runtime adjustment of acceleration for advanced users. Jerk is also specified in the Motion Magic® persistent configuration values. If Jerk is set to zero, Motion Magic® will produce a trapezoidal acceleration profile.
Target velocity can also be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is voltage-based, so relevant closed-loop gains will use Volts for the numerator.
- MotionMagicVelocityVoltage Parameters:
- Velocity: Target velocity to drive toward in rotations per second. This can be changed on-the fly.
- Acceleration: This is the absolute Acceleration to use generating the profile. If this parameter is zero, the Acceleration persistent configuration parameter is used instead. Acceleration is in rotations per second squared. If nonzero, the signage does not matter as the absolute value is used.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in volts
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicVelocityVoltage Parameters:
-
setControl
Requests Motion Magic® to target a final position using an exponential motion profile. Users can optionally provide a duty cycle feedforward.Motion Magic® Expo produces a motion profile in real-time while attempting to honor the Cruise Velocity (optional) and the mechanism kV and kA, specified via the Motion Magic® configuration values. Note that unlike the slot gains, the Expo_kV and Expo_kA configs are always in output units of Volts.
Setting Cruise Velocity to 0 will allow the profile to run to the max possible velocity based on Expo_kV. This control mode does not use the Acceleration or Jerk configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is duty cycle based, so relevant closed-loop gains will use fractional duty cycle for the numerator: +1.0 represents full forward output.
- MotionMagicExpoDutyCycle Parameters:
- Position: Position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in fractional units between -1 and +1.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicExpoDutyCycle Parameters:
-
setControl
Requests Motion Magic® to target a final position using an exponential motion profile. Users can optionally provide a voltage feedforward.Motion Magic® Expo produces a motion profile in real-time while attempting to honor the Cruise Velocity (optional) and the mechanism kV and kA, specified via the Motion Magic® configuration values. Note that unlike the slot gains, the Expo_kV and Expo_kA configs are always in output units of Volts.
Setting Cruise Velocity to 0 will allow the profile to run to the max possible velocity based on Expo_kV. This control mode does not use the Acceleration or Jerk configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is voltage-based, so relevant closed-loop gains will use Volts for the numerator.
- MotionMagicExpoVoltage Parameters:
- Position: Position to drive toward in rotations.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in volts
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicExpoVoltage Parameters:
-
setControl
Requests Motion Magic® to target a final position using an exponential motion profile. Users can optionally provide a torque current feedforward.Motion Magic® Expo produces a motion profile in real-time while attempting to honor the Cruise Velocity (optional) and the mechanism kV and kA, specified via the Motion Magic® configuration values. Note that unlike the slot gains, the Expo_kV and Expo_kA configs are always in output units of Volts.
Setting Cruise Velocity to 0 will allow the profile to run to the max possible velocity based on Expo_kV. This control mode does not use the Acceleration or Jerk configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is based on torque current, so relevant closed-loop gains will use Amperes for the numerator.
- MotionMagicExpoTorqueCurrentFOC Parameters:
- Position: Position to drive toward in rotations.
- FeedForward: Feedforward to apply in torque current in Amperes. User can use motor's kT to scale Newton-meter to Amperes.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- MotionMagicExpoTorqueCurrentFOC Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile. This dynamic request allows runtime changes to Cruise Velocity, Acceleration, and Jerk. Users can optionally provide a duty cycle feedforward. This control requires use of a CANivore.Motion Magic® produces a motion profile in real-time while attempting to honor the specified Cruise Velocity, Acceleration, and (optional) Jerk. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is duty cycle based, so relevant closed-loop gains will use fractional duty cycle for the numerator: +1.0 represents full forward output.
- DynamicMotionMagicDutyCycle Parameters:
- Position: Position to drive toward in rotations.
- Velocity: Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Acceleration: Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation
- Jerk: Jerk for profiling. The signage does not matter as the
device will use the absolute value for profile generation.
Jerk is optional; if this is set to zero, then Motion Magic® will not apply a Jerk limit.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in fractional units between -1 and +1.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DynamicMotionMagicDutyCycle Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile. This dynamic request allows runtime changes to Cruise Velocity, Acceleration, and Jerk. Users can optionally provide a voltage feedforward. This control requires use of a CANivore.Motion Magic® produces a motion profile in real-time while attempting to honor the specified Cruise Velocity, Acceleration, and (optional) Jerk. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is voltage-based, so relevant closed-loop gains will use Volts for the numerator.
- DynamicMotionMagicVoltage Parameters:
- Position: Position to drive toward in rotations.
- Velocity: Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Acceleration: Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Jerk: Jerk for profiling. The signage does not matter as the
device will use the absolute value for profile generation.
Jerk is optional; if this is set to zero, then Motion Magic® will not apply a Jerk limit.
- EnableFOC: Set to true to use FOC commutation (requires Phoenix
Pro), which increases peak power by ~15%. Set to
false to use trapezoidal commutation.
FOC improves motor performance by leveraging torque (current) control. However, this may be inconvenient for applications that require specifying duty cycle or voltage. CTR-Electronics has developed a hybrid method that combines the performances gains of FOC while still allowing applications to provide duty cycle or voltage demand. This not to be confused with simple sinusoidal control or phase voltage control which lacks the performance gains.
- FeedForward: Feedforward to apply in volts
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideBrakeDurNeutral: Set to true to static-brake the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0V to the motor.
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DynamicMotionMagicVoltage Parameters:
-
setControl
Requests Motion Magic® to target a final position using a motion profile. This dynamic request allows runtime changes to Cruise Velocity, Acceleration, and Jerk. Users can optionally provide a torque current feedforward. This control requires use of a CANivore.Motion Magic® produces a motion profile in real-time while attempting to honor the specified Cruise Velocity, Acceleration, and (optional) Jerk. This control mode does not use the Expo_kV or Expo_kA configs.
Target position can be changed on-the-fly and Motion Magic® will do its best to adjust the profile. This control mode is based on torque current, so relevant closed-loop gains will use Amperes for the numerator.
- DynamicMotionMagicTorqueCurrentFOC Parameters:
- Position: Position to drive toward in rotations.
- Velocity: Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Acceleration: Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Jerk: Jerk for profiling. The signage does not matter as the
device will use the absolute value for profile generation.
Jerk is optional; if this is set to zero, then Motion Magic® will not apply a Jerk limit.
- FeedForward: Feedforward to apply in torque current in Amperes. User can use motor's kT to scale Newton-meter to Amperes.
- Slot: Select which gains are applied by selecting the slot. Use the configuration api to set the gain values for the selected slot before enabling this feature. Slot must be within [0,2].
- OverrideCoastDurNeutral: Set to true to coast the rotor when output is zero (or within deadband). Set to false to use the NeutralMode configuration setting (default). This flag exists to provide the fundamental behavior of this control when output is zero, which is to provide 0A (zero torque).
- LimitForwardMotion: Set to true to force forward limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- LimitReverseMotion: Set to true to force reverse limiting. This allows users to use other limit switch sensors connected to robot controller. This also allows use of active sensors that require external power.
- IgnoreHardwareLimits: Set to true to ignore hardware limit
switches and the LimitForwardMotion and
LimitReverseMotion parameters, instead
allowing motion.
This can be useful on mechanisms such as an intake/feeder, where a limit switch stops motion while intaking but should be ignored when feeding to a shooter.
The hardware limit faults and Forward/ReverseLimit signals will still report the values of the limit switches regardless of this parameter.
- UseTimesync: Set to true to delay applying this control request
until a timesync boundary (requires Phoenix Pro and
CANivore). This eliminates the impact of
nondeterministic network delays in exchange for a
larger but deterministic control latency.
This requires setting the ControlTimesyncFreqHz config in MotorOutputConfigs. Additionally, when this is enabled, the UpdateFreqHz of this request should be set to 0 Hz.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- DynamicMotionMagicTorqueCurrentFOC Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_DutyCycleOut_Position request) Differential control with duty cycle average target and position difference target.- Diff_DutyCycleOut_Position Parameters:
- AverageRequest: Average DutyCycleOut request of the mechanism.
- DifferentialRequest: Differential PositionDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_DutyCycleOut_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_PositionDutyCycle_Position request) Differential control with position average target and position difference target using dutycycle control.- Diff_PositionDutyCycle_Position Parameters:
- AverageRequest: Average PositionDutyCycle request of the mechanism.
- DifferentialRequest: Differential PositionDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_PositionDutyCycle_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_VelocityDutyCycle_Position request) Differential control with velocity average target and position difference target using dutycycle control.- Diff_VelocityDutyCycle_Position Parameters:
- AverageRequest: Average VelocityDutyCYcle request of the mechanism.
- DifferentialRequest: Differential PositionDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VelocityDutyCycle_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_MotionMagicDutyCycle_Position request) Differential control with Motion Magic® average target and position difference target using dutycycle control.- Diff_MotionMagicDutyCycle_Position Parameters:
- AverageRequest: Average MotionMagicDutyCycle request of the mechanism.
- DifferentialRequest: Differential PositionDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_MotionMagicDutyCycle_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_DutyCycleOut_Velocity request) Differential control with duty cycle average target and velocity difference target.- Diff_DutyCycleOut_Velocity Parameters:
- AverageRequest: Average DutyCycleOut request of the mechanism.
- DifferentialRequest: Differential VelocityDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_DutyCycleOut_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_PositionDutyCycle_Velocity request) Differential control with position average target and velocity difference target using dutycycle control.- Diff_PositionDutyCycle_Velocity Parameters:
- AverageRequest: Average PositionDutyCycle request of the mechanism.
- DifferentialRequest: Differential VelocityDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_PositionDutyCycle_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_VelocityDutyCycle_Velocity request) Differential control with velocity average target and velocity difference target using dutycycle control.- Diff_VelocityDutyCycle_Velocity Parameters:
- AverageRequest: Average VelocityDutyCycle request of the mechanism.
- DifferentialRequest: Differential VelocityDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VelocityDutyCycle_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_MotionMagicDutyCycle_Velocity request) Differential control with Motion Magic® average target and velocity difference target using dutycycle control.- Diff_MotionMagicDutyCycle_Velocity Parameters:
- AverageRequest: Average MotionMagicDutyCycle request of the mechanism.
- DifferentialRequest: Differential VelocityDutyCycle request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_MotionMagicDutyCycle_Velocity Parameters:
-
setControl
Differential control with voltage average target and position difference target.- Diff_VoltageOut_Position Parameters:
- AverageRequest: Average VoltageOut request of the mechanism.
- DifferentialRequest: Differential PositionVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VoltageOut_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_PositionVoltage_Position request) Differential control with position average target and position difference target using voltage control.- Diff_PositionVoltage_Position Parameters:
- AverageRequest: Average PositionVoltage request of the mechanism.
- DifferentialRequest: Differential PositionVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_PositionVoltage_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_VelocityVoltage_Position request) Differential control with velocity average target and position difference target using voltage control.- Diff_VelocityVoltage_Position Parameters:
- AverageRequest: Average VelocityVoltage request of the mechanism.
- DifferentialRequest: Differential PositionVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VelocityVoltage_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_MotionMagicVoltage_Position request) Differential control with Motion Magic® average target and position difference target using voltage control.- Diff_MotionMagicVoltage_Position Parameters:
- AverageRequest: Average MotionMagicVoltage request of the mechanism.
- DifferentialRequest: Differential PositionVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_MotionMagicVoltage_Position Parameters:
-
setControl
Differential control with voltage average target and velocity difference target.- Diff_VoltageOut_Velocity Parameters:
- AverageRequest: Average VoltageOut request of the mechanism.
- DifferentialRequest: Differential VelocityVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VoltageOut_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_PositionVoltage_Velocity request) Differential control with position average target and velocity difference target using voltage control.- Diff_PositionVoltage_Velocity Parameters:
- AverageRequest: Average PositionVoltage request of the mechanism.
- DifferentialRequest: Differential VelocityVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_PositionVoltage_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_VelocityVoltage_Velocity request) Differential control with velocity average target and velocity difference target using voltage control.- Diff_VelocityVoltage_Velocity Parameters:
- AverageRequest: Average VelocityVoltage request of the mechanism.
- DifferentialRequest: Differential VelocityVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VelocityVoltage_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_MotionMagicVoltage_Velocity request) Differential control with Motion Magic® average target and velocity difference target using voltage control.- Diff_MotionMagicVoltage_Velocity Parameters:
- AverageRequest: Average MotionMagicVoltage request of the mechanism.
- DifferentialRequest: Differential VelocityVoltage request of the mechanism.
- Specified by:
setControl
in interfaceHasTalonControls
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_MotionMagicVoltage_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_TorqueCurrentFOC_Position request) Differential control with torque current average target and position difference target.- Diff_TorqueCurrentFOC_Position Parameters:
- AverageRequest: Average TorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential PositionTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_TorqueCurrentFOC_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_PositionTorqueCurrentFOC_Position request) Differential control with position average target and position difference target using torque current control.- Diff_PositionTorqueCurrentFOC_Position Parameters:
- AverageRequest: Average PositionTorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential PositionTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_PositionTorqueCurrentFOC_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_VelocityTorqueCurrentFOC_Position request) Differential control with velocity average target and position difference target using torque current control.- Diff_VelocityTorqueCurrentFOC_Position Parameters:
- AverageRequest: Average VelocityTorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential PositionTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VelocityTorqueCurrentFOC_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_MotionMagicTorqueCurrentFOC_Position request) Differential control with Motion Magic® average target and position difference target using torque current control.- Diff_MotionMagicTorqueCurrentFOC_Position Parameters:
- AverageRequest: Average MotionMagicTorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential PositionTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_MotionMagicTorqueCurrentFOC_Position Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_TorqueCurrentFOC_Velocity request) Differential control with torque current average target and velocity difference target.- Diff_TorqueCurrentFOC_Velocity Parameters:
- AverageRequest: Average TorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential VelocityTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_TorqueCurrentFOC_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_PositionTorqueCurrentFOC_Velocity request) Differential control with position average target and velocity difference target using torque current control.- Diff_PositionTorqueCurrentFOC_Velocity Parameters:
- AverageRequest: Average PositionTorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential VelocityTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_PositionTorqueCurrentFOC_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_VelocityTorqueCurrentFOC_Velocity request) Differential control with velocity average target and velocity difference target using torque current control.- Diff_VelocityTorqueCurrentFOC_Velocity Parameters:
- AverageRequest: Average VelocityTorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential VelocityTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_VelocityTorqueCurrentFOC_Velocity Parameters:
-
setControl
public StatusCode setControl(com.ctre.phoenix6.controls.compound.Diff_MotionMagicTorqueCurrentFOC_Velocity request) Differential control with Motion Magic® average target and velocity difference target using torque current control.- Diff_MotionMagicTorqueCurrentFOC_Velocity Parameters:
- AverageRequest: Average MotionMagicTorqueCurrentFOC request of the mechanism.
- DifferentialRequest: Differential VelocityTorqueCurrentFOC request of the mechanism.
- Specified by:
setControl
in interfaceSupportsFOC
- Parameters:
request
- Control object to request of the device- Returns:
- Code response of the request
- Diff_MotionMagicTorqueCurrentFOC_Velocity Parameters:
-
setControl
Control device with generic control request object.User must make sure the specified object is castable to a valid control request, otherwise this function will fail at run-time and return the NotSupported StatusCode
- Specified by:
setControl
in interfaceHasTalonControls
- Specified by:
setControl
in interfaceSupportsFOC
- Specified by:
setControl
in interfaceSupportsMusic
- Parameters:
request
- Control object to request of the device- Returns:
- Status Code of the request, 0 is OK
-
setPosition
Sets the mechanism position of the device in mechanism rotations.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
setPosition
in interfaceHasTalonSignals
- Parameters:
newValue
- Value to set to. Units are in rotations.- Returns:
- StatusCode of the set command
-
setPosition
Sets the mechanism position of the device in mechanism rotations.- Specified by:
setPosition
in interfaceHasTalonSignals
- Parameters:
newValue
- Value to set to. Units are in rotations.timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
setPosition
Sets the mechanism position of the device in mechanism rotations.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
setPosition
in interfaceHasTalonSignals
- Parameters:
newValue
- Value to set to. Units are in rotations.- Returns:
- StatusCode of the set command
-
setPosition
Sets the mechanism position of the device in mechanism rotations.- Specified by:
setPosition
in interfaceHasTalonSignals
- Parameters:
newValue
- Value to set to. Units are in rotations.timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFaults
Clear the sticky faults in the device.This typically has no impact on the device functionality. Instead, it just clears telemetry faults that are accessible via API and Tuner Self-Test.
This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFaults
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFaults
Clear the sticky faults in the device.This typically has no impact on the device functionality. Instead, it just clears telemetry faults that are accessible via API and Tuner Self-Test.
- Specified by:
clearStickyFaults
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_Hardware
Clear sticky fault: Hardware fault occurredThis will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_Hardware
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_Hardware
Clear sticky fault: Hardware fault occurred- Specified by:
clearStickyFault_Hardware
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_ProcTemp
Clear sticky fault: Processor temperature exceeded limitThis will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_ProcTemp
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_ProcTemp
Clear sticky fault: Processor temperature exceeded limit- Specified by:
clearStickyFault_ProcTemp
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_DeviceTemp
Clear sticky fault: Device temperature exceeded limitThis will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_DeviceTemp
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_DeviceTemp
Clear sticky fault: Device temperature exceeded limit- Specified by:
clearStickyFault_DeviceTemp
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_Undervoltage
Clear sticky fault: Device supply voltage dropped to near brownout levelsThis will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_Undervoltage
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_Undervoltage
Clear sticky fault: Device supply voltage dropped to near brownout levels- Specified by:
clearStickyFault_Undervoltage
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_BootDuringEnable
Clear sticky fault: Device boot while detecting the enable signalThis will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_BootDuringEnable
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_BootDuringEnable
Clear sticky fault: Device boot while detecting the enable signal- Specified by:
clearStickyFault_BootDuringEnable
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_UnlicensedFeatureInUse
Clear sticky fault: An unlicensed feature is in use, device may not behave as expected.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_UnlicensedFeatureInUse
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_UnlicensedFeatureInUse
Clear sticky fault: An unlicensed feature is in use, device may not behave as expected.- Specified by:
clearStickyFault_UnlicensedFeatureInUse
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_BridgeBrownout
Clear sticky fault: Bridge was disabled most likely due to supply voltage dropping too low.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_BridgeBrownout
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_BridgeBrownout
Clear sticky fault: Bridge was disabled most likely due to supply voltage dropping too low.- Specified by:
clearStickyFault_BridgeBrownout
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_RemoteSensorReset
Clear sticky fault: The remote sensor has reset.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_RemoteSensorReset
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_RemoteSensorReset
Clear sticky fault: The remote sensor has reset.- Specified by:
clearStickyFault_RemoteSensorReset
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_MissingDifferentialFX
Clear sticky fault: The remote Talon used for differential control is not present on CAN Bus.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_MissingDifferentialFX
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_MissingDifferentialFX
Clear sticky fault: The remote Talon used for differential control is not present on CAN Bus.- Specified by:
clearStickyFault_MissingDifferentialFX
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_RemoteSensorPosOverflow
Clear sticky fault: The remote sensor position has overflowed. Because of the nature of remote sensors, it is possible for the remote sensor position to overflow beyond what is supported by the status signal frame. However, this is rare and cannot occur over the course of an FRC match under normal use.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_RemoteSensorPosOverflow
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_RemoteSensorPosOverflow
Clear sticky fault: The remote sensor position has overflowed. Because of the nature of remote sensors, it is possible for the remote sensor position to overflow beyond what is supported by the status signal frame. However, this is rare and cannot occur over the course of an FRC match under normal use.- Specified by:
clearStickyFault_RemoteSensorPosOverflow
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_OverSupplyV
Clear sticky fault: Supply Voltage has exceeded the maximum voltage rating of device.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_OverSupplyV
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_OverSupplyV
Clear sticky fault: Supply Voltage has exceeded the maximum voltage rating of device.- Specified by:
clearStickyFault_OverSupplyV
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_UnstableSupplyV
Clear sticky fault: Supply Voltage is unstable. Ensure you are using a battery and current limited power supply.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_UnstableSupplyV
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_UnstableSupplyV
Clear sticky fault: Supply Voltage is unstable. Ensure you are using a battery and current limited power supply.- Specified by:
clearStickyFault_UnstableSupplyV
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_ReverseHardLimit
Clear sticky fault: Reverse limit switch has been asserted. Output is set to neutral.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_ReverseHardLimit
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_ReverseHardLimit
Clear sticky fault: Reverse limit switch has been asserted. Output is set to neutral.- Specified by:
clearStickyFault_ReverseHardLimit
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_ForwardHardLimit
Clear sticky fault: Forward limit switch has been asserted. Output is set to neutral.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_ForwardHardLimit
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_ForwardHardLimit
Clear sticky fault: Forward limit switch has been asserted. Output is set to neutral.- Specified by:
clearStickyFault_ForwardHardLimit
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_ReverseSoftLimit
Clear sticky fault: Reverse soft limit has been asserted. Output is set to neutral.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_ReverseSoftLimit
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_ReverseSoftLimit
Clear sticky fault: Reverse soft limit has been asserted. Output is set to neutral.- Specified by:
clearStickyFault_ReverseSoftLimit
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_ForwardSoftLimit
Clear sticky fault: Forward soft limit has been asserted. Output is set to neutral.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_ForwardSoftLimit
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_ForwardSoftLimit
Clear sticky fault: Forward soft limit has been asserted. Output is set to neutral.- Specified by:
clearStickyFault_ForwardSoftLimit
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_MissingSoftLimitRemote
Clear sticky fault: The remote soft limit device is not present on CAN Bus.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_MissingSoftLimitRemote
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_MissingSoftLimitRemote
Clear sticky fault: The remote soft limit device is not present on CAN Bus.- Specified by:
clearStickyFault_MissingSoftLimitRemote
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_MissingHardLimitRemote
Clear sticky fault: The remote limit switch device is not present on CAN Bus.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_MissingHardLimitRemote
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_MissingHardLimitRemote
Clear sticky fault: The remote limit switch device is not present on CAN Bus.- Specified by:
clearStickyFault_MissingHardLimitRemote
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_RemoteSensorDataInvalid
Clear sticky fault: The remote sensor's data is no longer trusted. This can happen if the remote sensor disappears from the CAN bus or if the remote sensor indicates its data is no longer valid, such as when a CANcoder's magnet strength falls into the "red" range.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_RemoteSensorDataInvalid
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_RemoteSensorDataInvalid
Clear sticky fault: The remote sensor's data is no longer trusted. This can happen if the remote sensor disappears from the CAN bus or if the remote sensor indicates its data is no longer valid, such as when a CANcoder's magnet strength falls into the "red" range.- Specified by:
clearStickyFault_RemoteSensorDataInvalid
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_FusedSensorOutOfSync
Clear sticky fault: The remote sensor used for fusion has fallen out of sync to the local sensor. A re-synchronization has occurred, which may cause a discontinuity. This typically happens if there is significant slop in the mechanism, or if the RotorToSensorRatio configuration parameter is incorrect.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_FusedSensorOutOfSync
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_FusedSensorOutOfSync
Clear sticky fault: The remote sensor used for fusion has fallen out of sync to the local sensor. A re-synchronization has occurred, which may cause a discontinuity. This typically happens if there is significant slop in the mechanism, or if the RotorToSensorRatio configuration parameter is incorrect.- Specified by:
clearStickyFault_FusedSensorOutOfSync
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_StatorCurrLimit
Clear sticky fault: Stator current limit occured.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_StatorCurrLimit
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_StatorCurrLimit
Clear sticky fault: Stator current limit occured.- Specified by:
clearStickyFault_StatorCurrLimit
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_SupplyCurrLimit
Clear sticky fault: Supply current limit occured.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_SupplyCurrLimit
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_SupplyCurrLimit
Clear sticky fault: Supply current limit occured.- Specified by:
clearStickyFault_SupplyCurrLimit
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_UsingFusedCANcoderWhileUnlicensed
Clear sticky fault: Using Fused CANcoder feature while unlicensed. Device has fallen back to remote CANcoder.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_UsingFusedCANcoderWhileUnlicensed
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_UsingFusedCANcoderWhileUnlicensed
Clear sticky fault: Using Fused CANcoder feature while unlicensed. Device has fallen back to remote CANcoder.- Specified by:
clearStickyFault_UsingFusedCANcoderWhileUnlicensed
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-
clearStickyFault_StaticBrakeDisabled
Clear sticky fault: Static brake was momentarily disabled due to excessive braking current while disabled.This will wait up to 0.100 seconds (100ms) by default.
- Specified by:
clearStickyFault_StaticBrakeDisabled
in interfaceHasTalonSignals
- Returns:
- StatusCode of the set command
-
clearStickyFault_StaticBrakeDisabled
Clear sticky fault: Static brake was momentarily disabled due to excessive braking current while disabled.- Specified by:
clearStickyFault_StaticBrakeDisabled
in interfaceHasTalonSignals
- Parameters:
timeoutSeconds
- Maximum time to wait up to in seconds.- Returns:
- StatusCode of the set command
-