Class DynamicMotionMagicDutyCycle
- All Implemented Interfaces:
ControlRequest,Cloneable
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.
-
Field Summary
FieldsModifier and TypeFieldDescriptiondoubleAcceleration for profiling.booleanSet to true to use FOC commutation (requires Phoenix Pro), which increases peak power by ~15% on supported devices (seeSupportsFOC).doubleFeedforward to apply in fractional units between -1 and +1.booleanSet to true to ignore hardware limit switches and the LimitForwardMotion and LimitReverseMotion parameters, instead allowing motion.booleanSet to true to ignore software limits, instead allowing motion.doubleJerk for profiling.booleanSet to true to force forward limiting.booleanSet to true to force reverse limiting.booleanSet to true to static-brake the rotor when output is zero (or within deadband).doublePosition to drive toward in rotations.intSelect which gains are applied by selecting the slot.doubleThe frequency at which this control will update.booleanSet to true to delay applying this control request until a timesync boundary (requires Phoenix Pro and CANivore).doubleCruise velocity for profiling. -
Constructor Summary
ConstructorsConstructorDescriptionDynamicMotionMagicDutyCycle(double Position, double Velocity, double Acceleration) Requires Phoenix Pro and CANivore; Requests Motion Magic® to target a final position using a motion profile.DynamicMotionMagicDutyCycle(Angle Position, AngularVelocity Velocity, AngularAcceleration Acceleration) Requires Phoenix Pro and CANivore; Requests Motion Magic® to target a final position using a motion profile. -
Method Summary
Modifier and TypeMethodDescriptionclone()Helper method to get this Control Request's Acceleration parameter converted to a unit type.Gets information about this control request.Helper method to get this Control Request's Jerk parameter converted to a unit type.getName()Gets the name of this control request.Helper method to get this Control Request's Position parameter converted to a unit type.Helper method to get this Control Request's Velocity parameter converted to a unit type.sendRequest(String network, int deviceHash) toString()withAcceleration(double newAcceleration) Modifies this Control Request's Acceleration parameter and returns itself for method-chaining and easier to use request API.withAcceleration(AngularAcceleration newAcceleration) Modifies this Control Request's Acceleration parameter and returns itself for method-chaining and easier to use request API.withEnableFOC(boolean newEnableFOC) Modifies this Control Request's EnableFOC parameter and returns itself for method-chaining and easier to use request API.withFeedForward(double newFeedForward) Modifies this Control Request's FeedForward parameter and returns itself for method-chaining and easier to use request API.withIgnoreHardwareLimits(boolean newIgnoreHardwareLimits) Modifies this Control Request's IgnoreHardwareLimits parameter and returns itself for method-chaining and easier to use request API.withIgnoreSoftwareLimits(boolean newIgnoreSoftwareLimits) Modifies this Control Request's IgnoreSoftwareLimits parameter and returns itself for method-chaining and easier to use request API.withJerk(double newJerk) Modifies this Control Request's Jerk parameter and returns itself for method-chaining and easier to use request API.withJerk(Velocity<AngularAccelerationUnit> newJerk) Modifies this Control Request's Jerk parameter and returns itself for method-chaining and easier to use request API.withLimitForwardMotion(boolean newLimitForwardMotion) Modifies this Control Request's LimitForwardMotion parameter and returns itself for method-chaining and easier to use request API.withLimitReverseMotion(boolean newLimitReverseMotion) Modifies this Control Request's LimitReverseMotion parameter and returns itself for method-chaining and easier to use request API.withOverrideBrakeDurNeutral(boolean newOverrideBrakeDurNeutral) Modifies this Control Request's OverrideBrakeDurNeutral parameter and returns itself for method-chaining and easier to use request API.withPosition(double newPosition) Modifies this Control Request's Position parameter and returns itself for method-chaining and easier to use request API.withPosition(Angle newPosition) Modifies this Control Request's Position parameter and returns itself for method-chaining and easier to use request API.withSlot(int newSlot) Modifies this Control Request's Slot parameter and returns itself for method-chaining and easier to use request API.withUpdateFreqHz(double newUpdateFreqHz) Sets the frequency at which this control will update.withUpdateFreqHz(Frequency newUpdateFreqHz) Sets the frequency at which this control will update.withUseTimesync(boolean newUseTimesync) Modifies this Control Request's UseTimesync parameter and returns itself for method-chaining and easier to use request API.withVelocity(double newVelocity) Modifies this Control Request's Velocity parameter and returns itself for method-chaining and easier to use request API.withVelocity(AngularVelocity newVelocity) Modifies this Control Request's Velocity parameter and returns itself for method-chaining and easier to use request API.
-
Field Details
-
Position
Position to drive toward in rotations.- Units: rotations
-
Velocity
Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.- Units: rotations per second
-
Acceleration
Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation- Units: rotations per second²
-
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.
- Units: rotations per second³
-
EnableFOC
Set to true to use FOC commutation (requires Phoenix Pro), which increases peak power by ~15% on supported devices (seeSupportsFOC). 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. This is added to the output of the onboard feedforward terms.- Units: fractional
-
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.
-
IgnoreSoftwareLimits
Set to true to ignore software limits, instead allowing motion.This can be useful when calibrating the zero point of a mechanism such as an elevator.
The software limit faults will still report the values of the software limits 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.
-
UpdateFreqHz
The frequency at which this control will update. This is designated in Hertz, with a minimum of 20 Hz (every 50 ms) and a maximum of 1000 Hz (every 1 ms). Some update frequencies are not supported and will be promoted up to the next highest supported frequency.If this field is set to 0 Hz, the control request will be sent immediately as a one-shot frame. This may be useful for advanced applications that require outputs to be synchronized with data acquisition. In this case, we recommend not exceeding 50 ms between control calls.
-
-
Constructor Details
-
DynamicMotionMagicDutyCycle
Requires Phoenix Pro and CANivore; Requests Motion Magic® to target a final position using a motion profile. This dynamic request allows runtime changes to Cruise Velocity, Acceleration, and (optional) Jerk. Users can optionally provide a duty cycle feedforward.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.
- 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
-
DynamicMotionMagicDutyCycle
public DynamicMotionMagicDutyCycle(Angle Position, AngularVelocity Velocity, AngularAcceleration Acceleration) Requires Phoenix Pro and CANivore; Requests Motion Magic® to target a final position using a motion profile. This dynamic request allows runtime changes to Cruise Velocity, Acceleration, and (optional) Jerk. Users can optionally provide a duty cycle feedforward.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.
- 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
-
-
Method Details
-
getName
Description copied from interface:ControlRequestGets the name of this control request.- Specified by:
getNamein interfaceControlRequest- Returns:
- Name of the control request
-
toString
-
sendRequest
- Specified by:
sendRequestin interfaceControlRequest
-
getControlInfo
Gets information about this control request.- Specified by:
getControlInfoin interfaceControlRequest- Returns:
- Map of control parameter names and corresponding applied values
-
withPosition
Modifies this Control Request's Position parameter and returns itself for method-chaining and easier to use request API.Position to drive toward in rotations.
- Units: rotations
- Parameters:
newPosition- Parameter to modify- Returns:
- Itself
-
withPosition
Modifies this Control Request's Position parameter and returns itself for method-chaining and easier to use request API.Position to drive toward in rotations.
- Units: rotations
- Parameters:
newPosition- Parameter to modify- Returns:
- Itself
-
getPositionMeasure
Helper method to get this Control Request's Position parameter converted to a unit type. If not using the Java units library,Positioncan be accessed directly instead.Position to drive toward in rotations.
- Units: rotations
- Returns:
- Position
-
withVelocity
Modifies this Control Request's Velocity parameter and returns itself for method-chaining and easier to use request API.Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Units: rotations per second
- Parameters:
newVelocity- Parameter to modify- Returns:
- Itself
-
withVelocity
Modifies this Control Request's Velocity parameter and returns itself for method-chaining and easier to use request API.Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Units: rotations per second
- Parameters:
newVelocity- Parameter to modify- Returns:
- Itself
-
getVelocityMeasure
Helper method to get this Control Request's Velocity parameter converted to a unit type. If not using the Java units library,Velocitycan be accessed directly instead.Cruise velocity for profiling. The signage does not matter as the device will use the absolute value for profile generation.
- Units: rotations per second
- Returns:
- Velocity
-
withAcceleration
Modifies this Control Request's Acceleration parameter and returns itself for method-chaining and easier to use request API.Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation
- Units: rotations per second²
- Parameters:
newAcceleration- Parameter to modify- Returns:
- Itself
-
withAcceleration
Modifies this Control Request's Acceleration parameter and returns itself for method-chaining and easier to use request API.Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation
- Units: rotations per second²
- Parameters:
newAcceleration- Parameter to modify- Returns:
- Itself
-
getAccelerationMeasure
Helper method to get this Control Request's Acceleration parameter converted to a unit type. If not using the Java units library,Accelerationcan be accessed directly instead.Acceleration for profiling. The signage does not matter as the device will use the absolute value for profile generation
- Units: rotations per second²
- Returns:
- Acceleration
-
withJerk
Modifies this Control Request's Jerk parameter and returns itself for method-chaining and easier to use request API.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.
- Units: rotations per second³
- Parameters:
newJerk- Parameter to modify- Returns:
- Itself
-
withJerk
Modifies this Control Request's Jerk parameter and returns itself for method-chaining and easier to use request API.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.
- Units: rotations per second³
- Parameters:
newJerk- Parameter to modify- Returns:
- Itself
-
getJerkMeasure
Helper method to get this Control Request's Jerk parameter converted to a unit type. If not using the Java units library,Jerkcan be accessed directly instead.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.
- Units: rotations per second³
- Returns:
- Jerk
-
withEnableFOC
Modifies this Control Request's EnableFOC parameter and returns itself for method-chaining and easier to use request API.Set to true to use FOC commutation (requires Phoenix Pro), which increases peak power by ~15% on supported devices (see
SupportsFOC). 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.
- Parameters:
newEnableFOC- Parameter to modify- Returns:
- Itself
-
withFeedForward
Modifies this Control Request's FeedForward parameter and returns itself for method-chaining and easier to use request API.Feedforward to apply in fractional units between -1 and +1. This is added to the output of the onboard feedforward terms.
- Units: fractional
- Parameters:
newFeedForward- Parameter to modify- Returns:
- Itself
-
withSlot
Modifies this Control Request's Slot parameter and returns itself for method-chaining and easier to use request API.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].
- Parameters:
newSlot- Parameter to modify- Returns:
- Itself
-
withOverrideBrakeDurNeutral
Modifies this Control Request's OverrideBrakeDurNeutral parameter and returns itself for method-chaining and easier to use request API.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.
- Parameters:
newOverrideBrakeDurNeutral- Parameter to modify- Returns:
- Itself
-
withLimitForwardMotion
Modifies this Control Request's LimitForwardMotion parameter and returns itself for method-chaining and easier to use request API.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.
- Parameters:
newLimitForwardMotion- Parameter to modify- Returns:
- Itself
-
withLimitReverseMotion
Modifies this Control Request's LimitReverseMotion parameter and returns itself for method-chaining and easier to use request API.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.
- Parameters:
newLimitReverseMotion- Parameter to modify- Returns:
- Itself
-
withIgnoreHardwareLimits
Modifies this Control Request's IgnoreHardwareLimits parameter and returns itself for method-chaining and easier to use request API.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.
- Parameters:
newIgnoreHardwareLimits- Parameter to modify- Returns:
- Itself
-
withIgnoreSoftwareLimits
Modifies this Control Request's IgnoreSoftwareLimits parameter and returns itself for method-chaining and easier to use request API.Set to true to ignore software limits, instead allowing motion.
This can be useful when calibrating the zero point of a mechanism such as an elevator.
The software limit faults will still report the values of the software limits regardless of this parameter.
- Parameters:
newIgnoreSoftwareLimits- Parameter to modify- Returns:
- Itself
-
withUseTimesync
Modifies this Control Request's UseTimesync parameter and returns itself for method-chaining and easier to use request API.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.
- Parameters:
newUseTimesync- Parameter to modify- Returns:
- Itself
-
withUpdateFreqHz
Sets the frequency at which this control will update. This is designated in Hertz, with a minimum of 20 Hz (every 50 ms) and a maximum of 1000 Hz (every 1 ms). Some update frequencies are not supported and will be promoted up to the next highest supported frequency.If this field is set to 0 Hz, the control request will be sent immediately as a one-shot frame. This may be useful for advanced applications that require outputs to be synchronized with data acquisition. In this case, we recommend not exceeding 50 ms between control calls.
- Specified by:
withUpdateFreqHzin interfaceControlRequest- Parameters:
newUpdateFreqHz- Parameter to modify- Returns:
- Itself
-
withUpdateFreqHz
Sets the frequency at which this control will update. This is designated in Hertz, with a minimum of 20 Hz (every 50 ms) and a maximum of 1000 Hz (every 1 ms). Some update frequencies are not supported and will be promoted up to the next highest supported frequency.If this field is set to 0 Hz, the control request will be sent immediately as a one-shot frame. This may be useful for advanced applications that require outputs to be synchronized with data acquisition. In this case, we recommend not exceeding 50 ms between control calls.
- Specified by:
withUpdateFreqHzin interfaceControlRequest- Parameters:
newUpdateFreqHz- Parameter to modify- Returns:
- Itself
-
clone
-