Class TorqueCurrentFOC
- All Implemented Interfaces:
ControlRequest,Cloneable
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.
-
Field Summary
FieldsModifier and TypeFieldDescriptiondoubleDeadband in Amperes.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.booleanSet to true to force forward limiting.booleanSet to true to force reverse limiting.doubleThe maximum absolute motor output that can be applied, which effectively limits the velocity.doubleAmount of motor current in Amperes Units: AbooleanSet to true to coast the rotor when output is zero (or within deadband).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). -
Constructor Summary
ConstructorsConstructorDescriptionTorqueCurrentFOC(double Output) Requires Phoenix Pro; Request a specified motor current (field oriented control).TorqueCurrentFOC(Current Output) Requires Phoenix Pro; Request a specified motor current (field oriented control). -
Method Summary
Modifier and TypeMethodDescriptionclone()Gets information about this control request.Helper method to get this Control Request's Deadband parameter converted to a unit type.getName()Gets the name of this control request.Helper method to get this Control Request's Output parameter converted to a unit type.sendRequest(String network, int deviceHash) toString()withDeadband(double newDeadband) Modifies this Control Request's Deadband parameter and returns itself for method-chaining and easier to use request API.withDeadband(Current newDeadband) Modifies this Control Request's Deadband 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.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.withMaxAbsDutyCycle(double newMaxAbsDutyCycle) Modifies this Control Request's MaxAbsDutyCycle parameter and returns itself for method-chaining and easier to use request API.withOutput(double newOutput) Modifies this Control Request's Output parameter and returns itself for method-chaining and easier to use request API.withOutput(Current newOutput) Modifies this Control Request's Output parameter and returns itself for method-chaining and easier to use request API.withOverrideCoastDurNeutral(boolean newOverrideCoastDurNeutral) Modifies this Control Request's OverrideCoastDurNeutral 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.
-
Field Details
-
Output
Amount of motor current in Amperes- Units: A
-
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.- Units: fractional
-
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.- Units: A
-
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.
-
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
-
TorqueCurrentFOC
Requires Phoenix Pro; 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.
- Parameters:
Output- Amount of motor current in Amperes
-
TorqueCurrentFOC
Requires Phoenix Pro; 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.
- Parameters:
Output- Amount of motor current in Amperes
-
-
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
-
withOutput
Modifies this Control Request's Output parameter and returns itself for method-chaining and easier to use request API.Amount of motor current in Amperes
- Units: A
- Parameters:
newOutput- Parameter to modify- Returns:
- Itself
-
withOutput
Modifies this Control Request's Output parameter and returns itself for method-chaining and easier to use request API.Amount of motor current in Amperes
- Units: A
- Parameters:
newOutput- Parameter to modify- Returns:
- Itself
-
getOutputMeasure
Helper method to get this Control Request's Output parameter converted to a unit type. If not using the Java units library,Outputcan be accessed directly instead.Amount of motor current in Amperes
- Units: A
- Returns:
- Output
-
withMaxAbsDutyCycle
Modifies this Control Request's MaxAbsDutyCycle parameter and returns itself for method-chaining and easier to use request API.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.
- Units: fractional
- Parameters:
newMaxAbsDutyCycle- Parameter to modify- Returns:
- Itself
-
withDeadband
Modifies this Control Request's Deadband parameter and returns itself for method-chaining and easier to use request API.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.
- Units: A
- Parameters:
newDeadband- Parameter to modify- Returns:
- Itself
-
withDeadband
Modifies this Control Request's Deadband parameter and returns itself for method-chaining and easier to use request API.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.
- Units: A
- Parameters:
newDeadband- Parameter to modify- Returns:
- Itself
-
getDeadbandMeasure
Helper method to get this Control Request's Deadband parameter converted to a unit type. If not using the Java units library,Deadbandcan be accessed directly instead.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.
- Units: A
- Returns:
- Deadband
-
withOverrideCoastDurNeutral
Modifies this Control Request's OverrideCoastDurNeutral parameter and returns itself for method-chaining and easier to use request API.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).
- Parameters:
newOverrideCoastDurNeutral- 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
-