Revision history [back]

If you installed the ros1_bridge from debs (ros-eloquent-ros1-bridge) this behavior is currently expected as the deb does not provide a mapping for tf/tfMessage only for tf2 messages. I'll take advantage of this to point out that tf and tfMessage have been deprecated for 7 years now (since ROS Hydro) so relying on them in ROS 1 is discouraged. See this PR for a request to provide support for it in the deb.

If you built the bridge from source (like in the github issue you link to) with ROS 1 tf package installed and ROS 2 tf2_msgs package installed, bridging should work. You would need to provide the exact steps you used to build the bridge to find out why it's not working.

I am also having a problem with /tf_static not being published on the ROS2 side

Please open separate questions for separate problems so that each answer respond to only one question.

If you installed the ros1_bridge from debs (ros-eloquent-ros1-bridge) this behavior is currently expected as the deb does not provide a mapping for tf/tfMessage only for tf2 messages. I'll take advantage of this to point out that tf and tfMessage have been deprecated for 7 years now (since ROS Hydro) so relying on them in ROS 1 is discouraged. See this PR for a request to provide support for it in the deb.

If you built the bridge from source (like in the github issue you link to) with ROS 1 tf package installed and ROS 2 tf2_msgs package installed, bridging should work. You would need to provide the exact steps you used to build the bridge to find out why it's not working.

I am also having a problem with /tf_static not being published on the ROS2 side

Please open separate questions for separate problems so that each answer respond to only one question.