ros1_bridge
- Software
- Middleware
- Tool
A network bridge that passes messages and services between ROS 1 and ROS 2 so nodes from both systems can talk to each other.
Made by ROS 2.
Source on GitHub: github.com/ros2/ros1_bridge (opens in a new tab). Facts read at commit 611755f (opens in a new tab).
Licenses
- Code
- Apache-2.0 (opens in a new tab)
Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit 611755f (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
What it does
- Bridges topics dynamically, starting a bridge only when matching publishers and subscribers exist on either side.
- Also bridges ROS 1 and ROS 2 services; a parameter_bridge variant selects topics and services from a YAML config.
- Ships with support for common ROS interfaces; custom message types require building the bridge from source.
- Supports configuring per-topic Quality of Service settings, such as latching for /tf_static.
- Includes examples: talker/listener, image exchange with rqt_image_view, and an AddTwoInts service bridge.
Written by Robotheca from the project's README (opens in a new tab) at commit 611755f.
Getting started
- Difficulty
- Intermediate
- Hardware it needs, as the project states it
- Building on a memory-constrained system may need limited parallel jobs (MAKEFLAGS=-j1).
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Maintained: a commit in the last 12 months
- Newest commit
- 17 Nov 2025 on master
- Latest release
- None published on GitHub
Checked on GitHub on 16 Oct 2026.
Links
Robots on Robotheca that use it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.