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
+4-9Lines changed: 4 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,6 @@ force_torque_sensor_broadcaster
14
14
* Added support for filter chains, allowing users to configure a sequence of filter plugins with their parameters. The force/torque sensor readings are filtered sequentially and published on a separate topic.
15
15
* 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>`__).
16
16
17
-
<<<<<<< HEAD
18
17
imu_sensor_broadcaster
19
18
*******************************
20
19
* IMU sensor broadcaster is now a chainable controller. It supports a calibration by means of a rotation, defined as euler angles, to its target frame. (`#1833 <https://github.com/ros-controls/ros2_controllers/pull/1833/files>`__).
@@ -26,6 +25,10 @@ joint_trajectory_controller
26
25
<https://github.com/ros-controls/ros2_controllers/pull/1191>`__. With this the controller
27
26
"stretches the time" with which it progresses in the trajectory. Scaling can either be set
28
27
manually or it can be synchronized with the hardware. See :ref:`jtc_speed_scaling` for details.
28
+
* Fill in 0 velocities and accelerations into point before trajectories if the state interfaces
29
+
don't contain velocity / acceleration information, but the trajectory does. This way, the segment
30
+
up to the first waypoint will use the same interpolation as the rest of the trajectory. (`#2043
0 commit comments