Revision history [back]

The ros1_bridge is implemented in C++ and therefore only supports bridging types it knows about at compile time. You can get a list of supported types by invoking: ros2 run ros1_bridge dynamic_bridge --print-pairs.

From the services which are not being bridged many (if not all?) seem to be of a service type defined in the gazebo_msgs package: https://github.com/ros-simulation/gazebo_ros_pkgs/tree/bc4938fe5d08adfc853ad6d94bdde8b02e99dbe0/gazebo_msgs/srv

But gazebo_msgs is not an explicitly declared dependency of the ros1_bridge package: https://github.com/ros2-gbp/ros1_bridge-release/blob/b3a2e9657cd303fff26e219db471b0557600b519/debian/package.xml#L42-L67

As such you will need to build the ros1_bridge from source (with gazebo_msgs being present in the underlying ROS 1 and ROS 2 workspaces): https://github.com/ros2/ros1_bridge#building-the-bridge-from-source