diff --git a/conf.py b/conf.py index 58b4c4a4d8..06d52f4dd5 100644 --- a/conf.py +++ b/conf.py @@ -119,7 +119,7 @@ "display_github": True, "github_user": "ros-planning", "github_repo": "moveit2_tutorials", - "github_version": "main/", + "github_version": "humble/", "conf_py_path": "", "source_suffix": ".rst", } diff --git a/doc/examples/realtime_servo/realtime_servo_tutorial.rst b/doc/examples/realtime_servo/realtime_servo_tutorial.rst index 809efe230a..d1579f67de 100644 --- a/doc/examples/realtime_servo/realtime_servo_tutorial.rst +++ b/doc/examples/realtime_servo/realtime_servo_tutorial.rst @@ -19,7 +19,7 @@ Launching a Servo Node ---------------------- MoveIt Servo can be launched as a "node component" or a standalone node. The launch file, moveit_servo/servo_example.launch.py, launches a standalone node by default but also contains a commented component node. Commands are sent via ROS topics. The commands can come from anywhere, such as a joystick, keyboard, or other controller. -This demo was written for an Xbox 1 controller, but can be easily modified to use any controller compatible with the `Joy package `_ by modifying the `joystick_servo_example.cpp file `_ +This demo was written for an Xbox 1 controller, but can be easily modified to use any controller compatible with the `Joy package `_ by modifying the :moveit_codedir:`joystick_servo_example.cpp file `. To run the demo, make sure your controller is plugged in and can be detected by :code:`ros2 run joy joy_node`. Usually this happens automatically after plugging the controller in. Then launch with :: @@ -129,7 +129,7 @@ Requirements for incoming command messages, regardless of input device are: Servo Configs ^^^^^^^^^^^^^ -The `demo config file `_ shows the parameters needed for MoveIt Servo and is well documented. +The :moveit_codedir:`demo config file ` shows the parameters needed for MoveIt Servo and is well documented. Start with the parameters from the demo file, but some must be changed for your specific setup: 1. :code:`robot_link_command_frame`: Update this to be a valid frame in your robot, recommended as the planning frame or EEF frame