From 4f9fbe9869c36814004aacdae6c0b8442855c33a Mon Sep 17 00:00:00 2001 From: Valeriy Date: Mon, 12 Feb 2024 19:29:15 -0800 Subject: [PATCH] Yaml format --- .../controller_configuration_tutorial.rst | 50 +++++++++---------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/doc/controller_configuration/controller_configuration_tutorial.rst b/doc/controller_configuration/controller_configuration_tutorial.rst index 587540e89..973170a27 100644 --- a/doc/controller_configuration/controller_configuration_tutorial.rst +++ b/doc/controller_configuration/controller_configuration_tutorial.rst @@ -6,7 +6,7 @@ There are a few paths for integrating a controller that moves robot joints with * Any other controllers managed by `ROS Controller Manager `_ can be used by linking them with an existing MoveIt integration plugin if they support `Follow Joint Trajectory Action `_. * ROS controllers that don't support `Follow Joint Trajectory Action `_ can be bridged with MoveIt by implementing integration interfaces and exporting a plugin, as long as they can be made to fit into the `Controller Handle `_ interface. * Custom controllers that are not managed by `ROS Controller Manager `_, or for which the `MoveIt Controller Handle `_ is a poor fit, can be integrated by writing a custom MoveIt Controller Manager. - +fCon We will look at each of these options in more detail. Stock ROS Controllers @@ -26,51 +26,51 @@ The `ROS Controller Manager `_ loads the .. code-block:: yaml - arm_controller: + arm_controller: type: velocity_controllers/JointTrajectoryController joints: - - shoulder_joint - - upperarm_joint - - forearm_joint + - shoulder_joint + - upperarm_joint + - forearm_joint gains: - shoulder_joint: + shoulder_joint: p: 100 d: 1 i: 1 i_clamp: 1 - upperarm_joint: + upperarm_joint: p: 100 d: 1 i: 1 i_clamp: 1 - forearm_joint: + forearm_joint: p: 100 d: 1 i: 1 i_clamp: 1 gripper_controller: - type: position_controllers/GripperActionController - joint: gripper + type: position_controllers/GripperActionController + joint: gripper The *MoveIt Simple Controller Manager* configured by MSA `as the default `_ will load the *handles* that bridge these controllers with MoveIt by reading the ``simple_moveit_controllers.yaml`` configuration file, for example: .. code-block:: yaml - controller_list: - - name: arm_controller - action_ns: follow_joint_trajectory - type: FollowJointTrajectory - default: True - joints: - - shoulder_joint - - upperarm_joint - - forearm_joint - - name: gripper_controller - action_ns: gripper_cmd - type: GripperCommand - default: True - joints: - - gripper + controller_list: + - name: arm_controller + action_ns: follow_joint_trajectory + type: FollowJointTrajectory + default: True + joints: + - shoulder_joint + - upperarm_joint + - forearm_joint + - name: gripper_controller + action_ns: gripper_cmd + type: GripperCommand + default: True + joints: + - gripper The mapping from ROS controller ``name`` to MoveIt *controller handle* ``type`` is done by using pre-defined *simple integration types*: