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: doc/release_notes.rst
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@ Release Notes: Galactic to Humble
4
4
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5
5
This list summarizes the changes between Galactic (previous) and Humble (current) releases. Bugfixes are not included in this list.
6
6
7
+
<<<<<<< HEAD
7
8
.. note::
8
9
9
10
This list was created in July 2024, earlier changes may not be included.
@@ -63,3 +64,10 @@ steering_controllers_library
63
64
gpio_controllers
64
65
************************
65
66
* The GPIO command controller was added 🎉 (`#1251 <https://github.com/ros-controls/ros2_controllers/pull/1251>`_).
67
+
=======
68
+
This list summarizes important changes between Kilted Kaiju (previous) and Lyrical Luth (current) releases.
69
+
70
+
force_torque_sensor_broadcaster
71
+
*******************************
72
+
* Added support for transforming Wrench messages to a given list of target frames. This is useful when applications need force/torque data in their preferred coordinate frames. (`#2021 <https://github.com/ros-controls/ros2_controllers/pull/2021/files>`__).
73
+
>>>>>>> 3d03572 (Add utility node to transform wrench messages for a list of frames (#2021))
The package also provides a standalone ROS 2 node ``wrench_transformer_node`` that transforms wrench messages from the force_torque_sensor_broadcaster to different target frames using TF2. This allows applications to receive force/torque data in their preferred coordinate frames.
13
+
14
+
See the user documentation for details on configuration and usage.
The package provides a standalone ROS 2 node ``wrench_transformer_node`` that transforms wrench messages published by the ``ForceTorqueSensorBroadcaster`` controller to different target frames using TF2. This is useful when applications need force/torque data in coordinate frames other than the sensor frame.
33
+
34
+
The node subscribes to wrench messages from the broadcaster (either raw or filtered) and publishes transformed versions to separate topics for each target frame.
35
+
36
+
Usage
37
+
^^^^^
38
+
The wrench transformer node can be launched as a standalone executable:
39
+
40
+
.. code-block:: bash
41
+
42
+
ros2 run force_torque_sensor_broadcaster wrench_transformer_node
43
+
44
+
Wrench Transformer Parameters
45
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
46
+
The wrench transformer uses the `generate_parameter_library <https://github.com/PickNikRobotics/generate_parameter_library>`_ to handle its parameters. The parameter `definition file for the wrench transformer <https://github.com/ros-controls/ros2_controllers/blob/{REPOS_FILE_BRANCH}/force_torque_sensor_broadcaster/src/wrench_transformer_parameters.yaml>`_ contains descriptions for all the parameters.
- ``~/wrench`` (raw wrench messages). To subscribe to filtered wrench messages, use topic remapping: ``ros2 run ... --ros-args -r ~/wrench:=<namespace>/wrench_filtered``
57
+
58
+
The node publishes:
59
+
60
+
- ``<namespace>/<target_frame>/wrench`` for each target frame specified in ``target_frames``
61
+
62
+
- If the node is in the root namespace (``/``), the namespace defaults to the node name (e.g., ``/fts_wrench_transformer/<target_frame>/wrench``)
63
+
- If the input topic is remapped to a filtered topic (contains "filtered" in the name), the output topics automatically append ``_filtered`` suffix (e.g., ``<namespace>/<target_frame>/wrench_filtered``)
64
+
- This allows users to distinguish between transformed raw wrench data and transformed filtered wrench data
0 commit comments