diff --git a/lbr_demos/doc/lbr_demos.rst b/lbr_demos/doc/lbr_demos.rst index 7194d431..8a8b431f 100644 --- a/lbr_demos/doc/lbr_demos.rst +++ b/lbr_demos/doc/lbr_demos.rst @@ -29,7 +29,7 @@ MoveIt .. toctree:: :titlesonly: - lbr_moveit_py <../lbr_moveit/doc/lbr_moveit.rst> + lbr_moveit <../lbr_moveit/doc/lbr_moveit.rst> lbr_moveit_cpp <../lbr_moveit_cpp/doc/lbr_moveit_cpp.rst> Integration diff --git a/lbr_demos/lbr_moveit/doc/lbr_moveit.rst b/lbr_demos/lbr_moveit/doc/lbr_moveit.rst index a00c49b5..21726f24 100644 --- a/lbr_demos/lbr_moveit/doc/lbr_moveit.rst +++ b/lbr_demos/lbr_moveit/doc/lbr_moveit.rst @@ -11,8 +11,8 @@ lbr_moveit MoveIt Servo ------------ -Simulation -~~~~~~~~~~ +MoveIt Servo - Simulation +~~~~~~~~~~~~~~~~~~~~~~~~~ #. Run the mock setup: .. code-block:: bash @@ -20,6 +20,15 @@ Simulation ros2 launch lbr_bringup mock.launch.py \ model:=iiwa7 # [iiwa7, iiwa14, med7, med14] + .. hint:: + + For a physics-based simulation, also try Gazebo (remember to set ``mode:=gazebo`` for the next steps): + + .. code-block:: bash + + ros2 launch lbr_bringup gazebo.launch.py \ + model:=iiwa7 # [iiwa7, iiwa14, med7, med14] + #. Run MoveIt Servo: .. code-block:: bash @@ -38,10 +47,10 @@ You can now experiment with - Modifying the MoveIt Servo parameters in `moveit_servo.yaml `_:octicon:`link-external`. E.g. the ``robot_link_command_frame`` to change the commanding frame. - Connect a joystick or game controller. -- Or changing the veloctiy scales for this keyboard driver in `forward_keyboard.yaml `_:octicon:`linkt-external`. +- Or changing the veloctiy scales for this keyboard driver in `forward_keyboard.yaml `_:octicon:`link-external`. -Hardware -~~~~~~~~ +MoveIt Servo - Hardware +~~~~~~~~~~~~~~~~~~~~~~~ #. Client side configurations: #. Configure the ``client_command_mode`` to ``position`` in `lbr_system_parameters.yaml `_:octicon:`link-external` @@ -60,7 +69,7 @@ Hardware - ``FRI control mode``: ``POSITION_CONTROL`` or ``JOINT_IMPEDANCE_CONTROL`` - ``FRI client command mode``: ``POSITION`` -#. Proceed with steps 1, 2 and 3 from `Simulation`_ but with ``ros2 launch lbr_bringup hardware.launch.py`` in step 1. +#. Proceed with steps 1, 2 and 3 from `MoveIt Servo - Simulation`_ but with ``ros2 launch lbr_bringup hardware.launch.py`` in step 1. MoveIt via RViz --------------- @@ -71,8 +80,8 @@ MoveIt via RViz To run MoveIt via RViz, simply follow: -Simulation -~~~~~~~~~~ +MoveIt via RViz - Simulation +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #. Run the mock setup: .. code-block:: bash @@ -80,6 +89,15 @@ Simulation ros2 launch lbr_bringup mock.launch.py \ model:=iiwa7 # [iiwa7, iiwa14, med7, med14] + .. hint:: + + For a physics-based simulation, also try Gazebo (remember to set ``mode:=gazebo`` for the next steps): + + .. code-block:: bash + + ros2 launch lbr_bringup gazebo.launch.py \ + model:=iiwa7 # [iiwa7, iiwa14, med7, med14] + #. Run MoveIt with RViz: .. code-block:: bash @@ -91,8 +109,8 @@ Simulation #. You can now move the robot via MoveIt in RViz! -Hardware -~~~~~~~~ +MoveIt via RViz - Hardware +~~~~~~~~~~~~~~~~~~~~~~~~~~ #. Client side configurations: #. Configure the ``client_command_mode`` to ``position`` in `lbr_system_parameters.yaml `_:octicon:`link-external` @@ -111,4 +129,4 @@ Hardware - ``FRI control mode``: ``POSITION_CONTROL`` or ``JOINT_IMPEDANCE_CONTROL`` - ``FRI client command mode``: ``POSITION`` -#. Proceed with steps 1 and 2 from `Simulation`_ but with ``ros2 launch lbr_bringup hardware.launch.py`` in step 1. +#. Proceed with steps 1 and 2 from `MoveIt via RViz - Simulation`_ but with ``ros2 launch lbr_bringup hardware.launch.py`` in step 1.