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
Copy file name to clipboardExpand all lines: controller_manager/doc/userdoc.rst
+92Lines changed: 92 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,6 +194,98 @@ There are two scripts to interact with controller manager from launch files:
194
194
--controller-ros-args CONTROLLER_ROS_ARGS
195
195
The --ros-args to be passed to the controller node, e.g., for remapping topics. Pass multiple times for every argument.
196
196
197
+
<<<<<<< HEAD
198
+
=======
199
+
When launching ``spawner`` with ROS parameter files that use substitutions (for example, launch ``allow_substs=True``),
200
+
the resolved ``--params-file`` path(s) used by the spawner node are automatically forwarded to each controller along
201
+
with any explicit ``--param-file`` arguments passed to the spawner command.
202
+
203
+
.. note::
204
+
If a single parameter file is used for multiple controllers, the spawner will automatically forward the resolved path(s) to each controller. The following methods are recommended:
The ``spawner`` now supports per controller arguments, while parsing the arguments for multiple controllers using ``--controller`` option. For example, to spawn two controllers with different parameter files and remapping topics, the following command can be used:
240
+
241
+
.. code-block:: console
242
+
243
+
$ ros2 run controller_manager spawner --controller position_trajectory_controller \
--load-only Load the controller but do not configure/activate it
284
+
--inactive Configure the controller but do not switch it
285
+
--controller-ros-args CONTROLLER_ROS_ARGS
286
+
ROS arguments to pass to the controller
287
+
288
+
>>>>>>> a583699 ([Spawner] Allow parsing the parameter files parsed from spawner to controllers (#3136))
197
289
198
290
The parsed controller config file can follow the same conventions as the typical ROS 2 parameter file format. Now, the spawner can handle config files with wildcard entries and also the controller name in the absolute namespace. See the following examples on the config files:
0 commit comments