From 702628237aaca48aa268d0a74b5bed29f329c660 Mon Sep 17 00:00:00 2001 From: Vladimir Fokow <57260995+VladimirFokow@users.noreply.github.com> Date: Fri, 3 May 2024 08:19:57 +0200 Subject: [PATCH] remove a duplicate hint (#507) (cherry picked from commit a4cccb1cb86e78d49139b9a2f74ca845e1911c70) --- doc/index.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/index.rst b/doc/index.rst index 63f44cf22..e65a10c0f 100644 --- a/doc/index.rst +++ b/doc/index.rst @@ -250,7 +250,6 @@ These are some quick hints, especially for those coming from a ROS1 control back * *ros(1)_control* only allowed three hardware interface types: position, velocity, and effort. *ros2_control* allows you to create any interface type by defining a custom string. For example, you might define a ``position_in_degrees`` or a ``temperature`` interface. The most common (position, velocity, acceleration, effort) are already defined as constants in hardware_interface/types/hardware_interface_type_values.hpp. - * Joint names in tags in the URDF must be compatible with the controller's configuration. * In ros2_control, all parameters for the driver are specified in the URDF. The ros2_control framework uses the **** tag in the URDF. * Joint names in tags in the URDF must be compatible with the controller's configuration.