ROS 2 Demo Catalog

Complete Run Your First ROS 2 Bridge before using these commands. All native examples assume that /opt/ros/jazzy/setup.bash has been sourced. Use gui:=true only with WSLg or another desktop display; otherwise use the headless form shown where available.

Demo

Purpose

Extra package

Launch command

TurtleBot3

First visible mobile-robot bridge demo

ros-jazzy-turtlebot3-description

tb3_demo.launch.py

Navigation

Mobile robot navigation topics and actions

None

nav_demo.launch.py

Panda arm

Seven-joint trajectory control

None

arm_demo.launch.py

Attach

Attach/detach a nearby box through ROS services

ros-jazzy-turtlebot3-description

attach_demo.launch.py

Configurable Fleet ROS

One configurable fleet with batched Fleet ROS commands

TurtleBot3 description only for tb3_* models

fleet_demo.launch.py

Multi-manager Fleet ROS

Two manager-scoped fleets plus unexposed NPCs

ros-jazzy-turtlebot3-description

multi_manager_fleet_demo.launch.py

RMF office

RMF patrol and delivery integration

ros-jazzy-pybullet-fleet-rmf plus rmf_demos overlay

RMF quickstart

TurtleBot3

sudo apt install -y ros-jazzy-turtlebot3-description
ros2 launch pybullet_fleet_ros tb3_demo.launch.py \
  model:=burger gui:=true rviz:=false

For headless verification, replace the final arguments with gui:=false rviz:=false. The launch starts one robot named tb3_0.

Panda arm

Start the fixed-base Franka Panda demo. It exposes joint_states and the follow_joint_trajectory action under panda0:

ros2 launch pybullet_fleet_ros arm_demo.launch.py gui:=true rviz:=false

For RViz visualization, install ros-jazzy-rviz2 and omit rviz:=false.

From another terminal, send a seven-joint trajectory and keep the feedback on screen until the action completes:

ros2 action send_goal --feedback \
  /panda0/follow_joint_trajectory control_msgs/action/FollowJointTrajectory \
  "{trajectory: {joint_names: [panda_joint1, panda_joint2, panda_joint3, panda_joint4, panda_joint5, panda_joint6, panda_joint7], points: [{positions: [0.2, -0.5, 0.2, -1.8, 0.0, 1.3, 0.6], time_from_start: {sec: 3}}]}}"

Attach and detach

This demo starts tb3_0 beside three pickable boxes. Attach box_A, move with it attached, then detach it at the destination:

sudo apt install -y ros-jazzy-turtlebot3-description
ros2 launch pybullet_fleet_ros attach_demo.launch.py gui:=true
ros2 service call /tb3_0/toggle_attach std_srvs/srv/SetBool "{data: true}"
ros2 topic pub --once /tb3_0/goal_pose geometry_msgs/msg/PoseStamped \
  "{header: {frame_id: odom}, pose: {position: {x: 2.0, y: -1.0, z: 0.01}, orientation: {w: 1.0}}}"

After the robot reaches the goal, detach the box:

ros2 service call /tb3_0/toggle_attach std_srvs/srv/SetBool "{data: false}"

Configurable Fleet ROS demo

This launch generates a simple single-fleet YAML from its arguments and exposes the global /fleet/* endpoints. It is the quickest way to test a different fleet size or robot model:

ros2 launch pybullet_fleet_ros fleet_demo.launch.py \
  robots:=10 robot_model:=simple_cube gui:=true

From another terminal, verify the state stream and move five robots:

ros2 topic echo /fleet/states --once
ros2 run pybullet_fleet_ros fleet_nav_demo -- \
  --robots 5 --dx 0.5 --dy 0.5 --transport service

Supported robot_model values are simple_cube, mobile_robot, tb3_burger, and tb3_waffle. Install ros-jazzy-turtlebot3-description before using either TurtleBot3 value.

Multi-manager Fleet ROS demo

This fixed, directly editable scene exposes /fleet/delivery_fleet/* and /fleet/inspection_fleet/*; its npc manager is not published continuously. It is the basic reference for manager-scoped endpoints.

sudo apt install -y ros-jazzy-turtlebot3-description
ros2 launch pybullet_fleet_ros multi_manager_fleet_demo.launch.py gui:=true

From another terminal, inspect and command the delivery manager:

ros2 topic echo /fleet/delivery_fleet/states --once
ros2 run pybullet_fleet_ros fleet_nav_demo -- \
  --fleet-namespace /fleet/delivery_fleet \
  --robots 5 --dx 0.5 --dy 0.5 --transport service

To inspect the complete ROS request without the helper client, call the same service directly. This makes each target name and goal visible in the terminal:

ros2 service call /fleet/delivery_fleet/navigate pybullet_fleet_msgs/srv/FleetNavigate \
  "{command_id: demo_grid_shift, source: demos, goals_2d: [
    {name: delivery_robot_0, position: [0.5, 0.5], yaw: 0.0, z: 0.05},
    {name: delivery_robot_1, position: [2.5, 0.5], yaw: 0.0, z: 0.05},
    {name: delivery_robot_2, position: [4.5, 0.5], yaw: 0.0, z: 0.05},
    {name: delivery_robot_3, position: [6.5, 0.5], yaw: 0.0, z: 0.05},
    {name: delivery_robot_4, position: [8.5, 0.5], yaw: 0.0, z: 0.05}
  ], goals_3d: []}"

The same launch works in Docker; see the Docker bridge guide.

For a fixed, directly editable version of this multi-manager scene, copy bridge_fleet_multi_manager_demo.yaml and pass it to bridge_node through config_yaml.

Docker-only model catalog

The model catalog launches every model available in the fully provisioned Docker image, including optional ROS descriptions. It is not an APT preview demo:

cd docker
docker compose run --rm bridge \
  ros2 launch pybullet_fleet_ros model_catalog_demo.launch.py gui:=true