1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
/*
* Copyright (C) Cross The Road Electronics. All rights reserved.
* License information can be found in CTRE_LICENSE.txt
* For support and suggestions contact support@ctr-electronics.com or file
* an issue tracker at https://github.com/CrossTheRoadElec/Phoenix-Releases
*/
#pragma once
#include "ctre/phoenix6/controls/ControlRequest.hpp"
#include <units/frequency.h>
#include <units/time.h>
#include <units/angle.h>
#include <units/current.h>
namespace ctre {
namespace phoenix6 {
namespace controls {
/**
* Requires Phoenix Pro;
* 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.
*/
class MotionMagicTorqueCurrentFOC final : public ControlRequest {
ctre::phoenix::StatusCode SendRequest(const char *network, uint32_t deviceHash, std::shared_ptr<ControlRequest> &req) const override;
public:
/**
* \brief Position to drive toward in rotations.
*
* - Units: rotations
*
*/
units::angle::turn_t Position;
/**
* \brief Feedforward to apply in torque current in Amperes. This is added to
* the output of the onboard feedforward terms.
*
* User can use motor's kT to scale Newton-meter to Amperes.
*
* - Units: A
*
*/
units::current::ampere_t FeedForward = 0.0_A;
/**
* \brief 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].
*/
int Slot = 0;
/**
* \brief 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).
*/
bool OverrideCoastDurNeutral = false;
/**
* \brief 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.
*/
bool LimitForwardMotion = false;
/**
* \brief 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.
*/
bool LimitReverseMotion = false;
/**
* \brief 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.
*/
bool IgnoreHardwareLimits = false;
/**
* \brief 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.
*/
bool IgnoreSoftwareLimits = false;
/**
* \brief 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.
*/
bool UseTimesync = false;
/**
* \brief 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.
*/
units::frequency::hertz_t UpdateFreqHz{100_Hz};
/**
* \brief Requires Phoenix Pro;
* Requests Motion Magic® to target a final position using a motion
* profile. Users can optionally provide a torque current feedforward.
*
* \details 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.
*
* \param Position Position to drive toward in rotations.
*/
constexpr MotionMagicTorqueCurrentFOC(units::angle::turn_t Position) : ControlRequest{},
Position{std::move(Position)}
{}
constexpr ~MotionMagicTorqueCurrentFOC() override {}
/**
* \brief Gets the name of this control request.
*
* \returns Name of the control request
*/
constexpr std::string_view GetName() const override
{
return "MotionMagicTorqueCurrentFOC";
}
/**
* \brief 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
*
*
* \param newPosition Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithPosition(units::angle::turn_t newPosition)
{
Position = std::move(newPosition);
return *this;
}
/**
* \brief Modifies this Control Request's FeedForward parameter and returns itself for
* method-chaining and easier to use request API.
*
* Feedforward to apply in torque current in Amperes. This is added to the
* output of the onboard feedforward terms.
*
* User can use motor's kT to scale Newton-meter to Amperes.
*
* - Units: A
*
*
* \param newFeedForward Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithFeedForward(units::current::ampere_t newFeedForward)
{
FeedForward = std::move(newFeedForward);
return *this;
}
/**
* \brief 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].
*
* \param newSlot Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithSlot(int newSlot)
{
Slot = std::move(newSlot);
return *this;
}
/**
* \brief 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).
*
* \param newOverrideCoastDurNeutral Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithOverrideCoastDurNeutral(bool newOverrideCoastDurNeutral)
{
OverrideCoastDurNeutral = std::move(newOverrideCoastDurNeutral);
return *this;
}
/**
* \brief 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.
*
* \param newLimitForwardMotion Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithLimitForwardMotion(bool newLimitForwardMotion)
{
LimitForwardMotion = std::move(newLimitForwardMotion);
return *this;
}
/**
* \brief 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.
*
* \param newLimitReverseMotion Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithLimitReverseMotion(bool newLimitReverseMotion)
{
LimitReverseMotion = std::move(newLimitReverseMotion);
return *this;
}
/**
* \brief 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.
*
* \param newIgnoreHardwareLimits Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithIgnoreHardwareLimits(bool newIgnoreHardwareLimits)
{
IgnoreHardwareLimits = std::move(newIgnoreHardwareLimits);
return *this;
}
/**
* \brief 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.
*
* \param newIgnoreSoftwareLimits Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithIgnoreSoftwareLimits(bool newIgnoreSoftwareLimits)
{
IgnoreSoftwareLimits = std::move(newIgnoreSoftwareLimits);
return *this;
}
/**
* \brief 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.
*
* \param newUseTimesync Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithUseTimesync(bool newUseTimesync)
{
UseTimesync = std::move(newUseTimesync);
return *this;
}
/**
* \brief 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.
*
* \param newUpdateFreqHz Parameter to modify
* \returns Itself
*/
constexpr MotionMagicTorqueCurrentFOC &WithUpdateFreqHz(units::frequency::hertz_t newUpdateFreqHz)
{
UpdateFreqHz = newUpdateFreqHz;
return *this;
}
/**
* \brief Returns a string representation of the object.
*
* \returns a string representation of the object.
*/
std::string ToString() const override;
/**
* \brief Gets information about this control request.
*
* \returns Map of control parameter names and corresponding applied values
*/
std::map<std::string, std::string> GetControlInfo() const override;
};
}
}
}