Create a "ros-humble-ros1-bridge" package that can be used directly within Ubuntu 22.02 (Jammy) ROS2 Humble. Both amd64 and arm64 architectures are supported.

• Note1: It takes approximately 10 minutes on my PC, equipped with a 6-core CPU (12 logical cores) and 24GB of memory.

• Note2: It takes about 1 GB of memory per logical CPU core to compile the ROS1 bridge. So, if your system has only 4 GB of memory but 100 logical CPU cores, it will still use only 4 logical cores for the compilation. Now, why does it take so much memory to compile? Well, you can blame the overuse of C++ templates...

  git clone https://github.com/TommyChangUMD/ros-humble-ros1-bridge-builder.git
  cd ros-humble-ros1-bridge-builder

  # By default, ros-tutorals support will be built: (bridging the ros-humble-example-interfaces package)
  docker build . -t ros-humble-ros1-bridge-builder

• Note1: Since building a docker image just needs docker, you could do this step on any system that has docker installed -- it doesn't have to on a Ubuntu 22.04 (Jammy) and it doesn't need ROS2 neither.

• Note2: The builder image can be created on an amd64 machine (e.g., Intel and AMD CPUs) or an arm64 machine (e.g., Raspberry Pi 4B and Nvidia Jetson Orin). Docker will automatically select the correct platform variant based on the host's architecture.

Alternative builds:

  # **[OPTIONAL]** If you don't want to build ros-tutorals support:
  docker build . --build-arg ADD_ros_tutorials=0 -t ros-humble-ros1-bridge-builder

  # **[OPTIONAL]** If you want to build grid-map support:  (bridging the ros-humble-grid-map package)
  docker build . --build-arg ADD_grid_map=1 -t ros-humble-ros1-bridge-builder

  # **[OPTIONAL]** If you want to build an example custom message:
  docker build . --build-arg ADD_example_custom_msgs=1 -t ros-humble-ros1-bridge-builder

• Note1: Don't forget to install the necessary ros-humble-grid-map packages on your ROS2 Humble if you choose to build the bridge with the grid-map support added.

• Note2: For the custom message example, there is no pre-build package for ROS2 Humble so you will need to compile it from the source. For details, see Checking example custom message in the Troubleshoot section.

    cd ~/
    apt update; apt upgrade
    apt -y install ros-humble-desktop
    docker run --rm ros-humble-ros1-bridge-builder | tar xvzf -

• Note1: It's important that you have ros-humble-desktop installed on your ROS2 Humble system because we want to match it with the builder image as closely as possible. So, if you haven't done so already, do:

    apt -y install ros-humble-desktop

Otherwise you may get an error about missing ibexample_interfaces__rosidl_typesupport_cpp.so. See issue TommyChangUMD#10

• Note1: There is no compilation at this point, the docker run command simply spits out a pre-compiled tarball for either amd64 or arm64 architecture, depending on the architecture of the machine you used to created the builder image.

• Note2: The assumption is that this tarball contains configurations and libraries matching your ROS2 Humble system very closely, although not identical.

• Note3: We don't really need the builder image anymore, to delete it, do:

    docker rmi ros-humble-ros1-bridge-builder

  rocker --x11 --user --privileged \
         --volume /dev/shm /dev/shm --network=host -- ros:noetic-ros-base-focal \
         'bash -c "sudo apt update; sudo apt install -y ros-noetic-rospy-tutorials tilix; tilix"'

Tha docker image used above, ros:noetic-ros-base-focal, is multi-platform. It runs on amd64 (eg., Intel and AMD CPUs) or arm64 architecture (eg., Raspberry PI 4B and Nvidia Jetson Orin). Docker will automatically select the correct platform variant based on the host's architecture.

You may need to install rocker first:

  sudo apt install python3-rocker

• Note1: It's important to share the host's network and the /dev/shm/ directory with the container.
• Note2: You can add the --home rocker option if you want your home directory to be shared with the docker container. Be careful though, as the host's ~/.bashrc will be executed inside the container.
• Note3: You can also use ROS1 Melodic. Just replace ros:noetic-ros-base-focal with ros:melodic-ros-base-bionic and also replace ros-noetic-rospy-tutorials with ros-melodic-rospy-tutorials.

  source /opt/ros/noetic/setup.bash
  roscore

  source /opt/ros/humble/setup.bash
  source ~/ros-humble-ros1-bridge/install/local_setup.bash
  ros2 run ros1_bridge dynamic_bridge
  # or try (See Note2):
  ros2 run ros1_bridge dynamic_bridge --bridge-all-topics

• Note: We need to source local_setup.bash and NOT setup.bash because the bridge was compiled in a docker container that may have different underlay locations. Besides, we don't need to source these underlays in the host system again.

• Note2: https://github.com/ros2/ros1_bridge states that: "For efficiency reasons, topics will only be bridged when matching publisher-subscriber pairs are active for a topic on either side of the bridge. As a result using ros2 topic echo <topic-name> doesn't work but fails with an error message Could not determine the type for the passed topic if no other subscribers are present since the dynamic bridge hasn't bridged the topic yet. As a workaround the topic type can be specified explicitly ros2 topic echo <topic-name> <topic-type> which triggers the bridging of the topic since the echo command represents the necessary subscriber. On the ROS 1 side rostopic echo doesn't have an option to specify the topic type explicitly. Therefore it can't be used with the dynamic bridge if no other subscribers are present. As an alternative you can use the --bridge-all-2to1-topics option to bridge all ROS 2 topics to ROS 1 so that tools such as rostopic echo, rostopic list and rqt will see the topics even if there are no matching ROS 1 subscribers. Run ros2 run ros1_bridge dynamic_bridge -- --help for more options."

    $ ros2 run ros1_bridge dynamic_bridge --help
    Usage:
     -h, --help: This message.
     --show-introspection: Print output of introspection of both sides of the bridge.
     --print-pairs: Print a list of the supported ROS 2 <=> ROS 1 conversion pairs.
     --bridge-all-topics: Bridge all topics in both directions, whether or not there is a matching subscriber.
     --bridge-all-1to2-topics: Bridge all ROS 1 topics to ROS 2, whether or not there is a matching subscriber.
     --bridge-all-2to1-topics: Bridge all ROS 2 topics to ROS 1, whether or not there is a matching subscriber.

  source /opt/ros/noetic/setup.bash
  rosrun rospy_tutorials talker

  source /opt/ros/humble/setup.bash
  ros2 run demo_nodes_cpp listener

See an step 6.3 and 7 in the Dockerfile for an example.

• Note1: Make sure the package name ends with "_msgs".
• Note2: Use the same package name for both ROS1 and ROS2.

Also see the troubleshoot section.

• ref: https://github.com/TommyChangUMD/custom_msgs.git
• ref: https://github.com/ros2/ros1_bridge/blob/master/doc/index.rst

• Run roscore on the Noetic machine as usual.
• On the Humble machine, run the bridge as below (assuming the IP address of the Noetic machine is 192.168.1.208):

  source /opt/ros/humble/setup.bash
  source ~/ros-humble-ros1-bridge/install/local_setup.bash
  ROS_MASTER_URI='http://192.168.1.208:11311' ros2 run ros1_bridge dynamic_bridge
  # Note, change "192.168.1.208" above to the IP address of your Noetic machine.

If you have Noetic and Humble running on two different machines and have already set the ROS_MASTER_URI environment variable, you should check the network to ensure that the Humble machine can reach the Noetic machine via port 11311.

$ nc -v -z 192.168.1.208 11311
# Connection to 192.168.1.208 11311 port [tcp/*] succeeded!

$ ros2 run ros1_bridge dynamic_bridge --print-pairs | grep -i tf2
  - 'tf2_msgs/msg/TF2Error' (ROS 2) <=> 'tf2_msgs/TF2Error' (ROS 1)
  - 'tf2_msgs/msg/TFMessage' (ROS 2) <=> 'tf2_msgs/TFMessage' (ROS 1)
  - 'tf2_msgs/msg/TFMessage' (ROS 2) <=> 'tf/tfMessage' (ROS 1)
  - 'tf2_msgs/srv/FrameGraph' (ROS 2) <=> 'tf2_msgs/FrameGraph' (ROS 1)

• By default, --build-arg ADD_ros_tutorials=1 is implicitly added to the docker build ... command.
• The ROS2 Humble system must have the ros-humble-example-interfaces package installed.

$ sudo apt -y install ros-humble-example-interfaces
$ ros2 run ros1_bridge dynamic_bridge --print-pairs | grep -i addtwoints
  - 'example_interfaces/srv/AddTwoInts' (ROS 2) <=> 'roscpp_tutorials/TwoInts' (ROS 1)
  - 'example_interfaces/srv/AddTwoInts' (ROS 2) <=> 'rospy_tutorials/AddTwoInts' (ROS 1)

• Must have --build-arg ADD_grid_map=1 added to the docker build ... command.
• Note: In addition, the ROS2 Humble system must have the ros-humble-grid-map package installed.

$ sudo apt -y install ros-humble-grid-map
$ ros2 run ros1_bridge dynamic_bridge --print-pairs | grep -i grid_map
  - 'grid_map_msgs/msg/GridMap' (ROS 2) <=> 'grid_map_msgs/GridMap' (ROS 1)
  - 'grid_map_msgs/msg/GridMapInfo' (ROS 2) <=> 'grid_map_msgs/GridMapInfo' (ROS 1)
  - 'grid_map_msgs/srv/GetGridMap' (ROS 2) <=> 'grid_map_msgs/GetGridMap' (ROS 1)
  - 'grid_map_msgs/srv/GetGridMapInfo' (ROS 2) <=> 'grid_map_msgs/GetGridMapInfo' (ROS 1)
  - 'grid_map_msgs/srv/ProcessFile' (ROS 2) <=> 'grid_map_msgs/ProcessFile' (ROS 1)
  - 'grid_map_msgs/srv/SetGridMap' (ROS 2) <=> 'grid_map_msgs/SetGridMap' (ROS 1)

• Thanks to Codaero for the source code for an custom message example.
• Must have --build-arg ADD_example_custom_msgs=1 added to the docker build ... command.

# First, install the ROS2 pacakge from the source
$ git clone https://github.com/TommyChangUMD/custom_msgs.git
$ cd custom_msgs/custom_msgs_ros2
$ source /opt/ros/humble/setup.bash
$ colcon build
$ source install/setup.bash

# Now, run the bridge
$ source ~/ros-humble-ros1-bridge/install/local_setup.bash
$ ros2 run ros1_bridge dynamic_bridge --print-pairs | grep -i PseudoGridMap
  - 'custom_msgs/msg/PseudoGridMap' (ROS 2) <=> 'custom_msgs/PseudoGridMap' (ROS 1)

• https://github.com/ros2/ros1_bridge
• https://github.com/ros2/ros1_bridge/blob/master/doc/index.rst
• https://github.com/smith-doug/ros1_bridge/tree/action_bridge_humble
• https://github.com/mjforan/ros-humble-ros1-bridge
• https://packages.ubuntu.com/jammy/ros-desktop-dev