CTRE Phoenix 6 C++ 25.0.0-beta-4
|
Follow the motor output of another Talon while ignoring the master's invert setting. More...
#include <ctre/phoenix6/controls/StrictFollower.hpp>
Public Member Functions | |
StrictFollower (int MasterID) | |
Follow the motor output of another Talon while ignoring the master's invert setting. | |
StrictFollower & | WithMasterID (int newMasterID) |
Modifies this Control Request's MasterID parameter and returns itself for method-chaining and easier to use request API. | |
StrictFollower & | WithUpdateFreqHz (units::frequency::hertz_t newUpdateFreqHz) |
Sets the period at which this control will update at. | |
std::string | ToString () const override |
Returns a string representation of the object. | |
std::map< std::string, std::string > | GetControlInfo () const override |
Gets information about this control request. | |
Public Member Functions inherited from ctre::phoenix6::controls::ControlRequest | |
ControlRequest (std::string name) | |
Constructs a new Control Request with the given name. | |
std::string const & | GetName () const |
virtual | ~ControlRequest ()=default |
Public Attributes | |
int | MasterID |
Device ID of the master to follow. | |
units::frequency::hertz_t | UpdateFreqHz {20_Hz} |
The period at which this control will update at. | |
Additional Inherited Members | |
Protected Member Functions inherited from ctre::phoenix6::controls::ControlRequest | |
ControlRequest (ControlRequest const &)=default | |
ControlRequest (ControlRequest &&)=default | |
ControlRequest & | operator= (ControlRequest const &)=default |
ControlRequest & | operator= (ControlRequest &&)=default |
Protected Attributes inherited from ctre::phoenix6::controls::ControlRequest | |
std::string | name |
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.
|
inline |
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.
MasterID | Device ID of the master to follow. |
|
inlineoverridevirtual |
Gets information about this control request.
Implements ctre::phoenix6::controls::ControlRequest.
|
inlineoverridevirtual |
Returns a string representation of the object.
Implements ctre::phoenix6::controls::ControlRequest.
|
inline |
Modifies this Control Request's MasterID parameter and returns itself for method-chaining and easier to use request API.
Device ID of the master to follow.
newMasterID | Parameter to modify |
|
inline |
Sets the period at which this control will update at.
This is designated in Hertz, with a minimum of 20 Hz (every 50 ms) and a maximum of 1000 Hz (every 1 ms).
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.
newUpdateFreqHz | Parameter to modify |
int ctre::phoenix6::controls::StrictFollower::MasterID |
Device ID of the master to follow.
units::frequency::hertz_t ctre::phoenix6::controls::StrictFollower::UpdateFreqHz {20_Hz} |
The period at which this control will update at.
This is designated in Hertz, with a minimum of 20 Hz (every 50 ms) and a maximum of 1000 Hz (every 1 ms).
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.