You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow joint goals defining trajectory for only some joints.
156
156
157
157
open_loop_control (boolean)
158
-
Use controller in open-loop control mode using ignoring the states provided by hardware interface and using last commands as states in the next control step. This is useful if hardware states are not following commands, i.e., an offset between those (typical for hydraulic manipulators).
158
+
Use controller in open-loop control mode:
159
+
+ The controller ignores the states provided by hardware interface but using last commands as states for starting the trajectory interpolation.
160
+
+ It deactivates the feedback control, see the ``gains`` structure.
159
161
160
-
If this flag is set, the controller tries to read the values from the command interfaces on starting. If they have real numeric values, those will be used instead of state interfaces. Therefore it is important set command interfaces to NaN (std::numeric_limits<double>::quiet_NaN()) or state values when the hardware is started.
162
+
This is useful if hardware states are not following commands, i.e., an offset between those (typical for hydraulic manipulators).
163
+
164
+
.. Note::
165
+
If this flag is set, the controller tries to read the values from the command interfaces on activation.
166
+
If they have real numeric values, those will be used instead of state interfaces.
167
+
Therefore it is important set command interfaces to NaN (i.e., ``std::numeric_limits<double>::quiet_NaN()``) or state values when the hardware is started.
If ``velocity`` is the only command interface for all joints or an ``effort`` command interface is configured, PID controllers are used for every joint. This structure contains the controller gains for every joint with the control law
200
+
Only relevant, if ``open_loop_control`` is not set.
201
+
202
+
If ``velocity`` is the only command interface for all joints or an ``effort`` command interface is configured, PID controllers are used for every joint.
203
+
This structure contains the controller gains for every joint with the control law
0 commit comments