nobleo_socketcan_bridge
- Software
- Middleware
- Driver or SDK
A ROS2 bridge that exposes CAN frames from a SocketCAN device as ROS2 topics, re-implemented from ROS1's socketcan_bridge.
Made by Nobleo Technology.
Source on GitHub: github.com/nobleo/nobleo_socketcan_bridge (opens in a new tab). Facts read at commit b380dd4 (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 b380dd4 (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
What it does
- Publishes frames received on a SocketCAN device to an rx topic.
- Sends messages received on a tx topic out to the SocketCAN device.
- Does not loop back sent frames to the same node.
- Runs as a standalone node, with no lifecycle management.
- Can also be loaded as a dynamically loadable component.
Written by Robotheca from the project's README (opens in a new tab) at commit b380dd4.
Getting started
- Difficulty
- Intermediate
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Maintained: a commit in the last 12 months
- Newest commit
- 9 Feb 2026 on main
- Latest release
- None published on GitHub
Checked on GitHub on 16 Oct 2026.
Links
Robots that can run 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.