![]() |
nobleo_socketcan_bridge package from nobleo_socketcan_bridge reponobleo_socketcan_bridge |
|
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/nobleo/nobleo_socketcan_bridge.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-02-17 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Ramon Wijnands
Authors
- Ramon Wijnands
nobleo_socketcan_bridge
This package provides functionality to expose CAN frames from SocketCAN to ROS2 topics.
Overview
This is a from-scratch re-implementation of socketcan_bridge from ROS1. There is a different ROS2 package ros2_socketcan which is similar to this package. The differences between this package and ros2_socketcan are:
- No loopback, i.e. CAN frames that are send are not received by the same node
- No lifecycle management, just run it
- Less CPU usage
Nodes
The main node (socketcan_bridge
) is also available as dynamically loadable component.
The node socketcan_bridge_ee
is also provided that uses the EventsExecutor
that runs a bit more efficient.
socketcan_bridge
Subscribed Topics
-
~/tx
(can_msgs/Frame) Messages received here will be sent to the SocketCAN device.
Published Topics
-
~/rx
(can_msgs/Frame) Frames received on the SocketCAN device are published on this topic.
Parameters
-
interface
(default=can0
) Name of the SocketCAN device, by default these devices are named can0 and upwards. -
read_timeout
(default=1.0
) Maximum duration in seconds to wait for data on the file descriptor -
reconnect_timeout
(default=5.0
) Sleep duration in seconds before reconnecting to the SocketCAN device
Changelog for package nobleo_socketcan_bridge
1.0.0 (2025-02-12)
- First release
- Contributors: Ramon Wijnands, dkorenkovnl, Rein Appeldoorn, Ferry Schoenmakers, Tim Clephas
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
fmt |
Dependant Packages
Launch files
- test/benchmark.launch.xml
- Copyright (C) 2024 Nobleo Technology B.V. SPDX-License-Identifier: Apache-2.0
-
- rate [default: 5000]
- test/comparison.launch.xml
- Copyright (C) 2024 Nobleo Technology B.V. SPDX-License-Identifier: Apache-2.0
-
- rate [default: 1400]
- node [default: socketcan_bridge]
Messages
Services
Plugins
Recent questions tagged nobleo_socketcan_bridge at Robotics Stack Exchange
![]() |
nobleo_socketcan_bridge package from nobleo_socketcan_bridge reponobleo_socketcan_bridge |
|
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/nobleo/nobleo_socketcan_bridge.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-02-17 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Ramon Wijnands
Authors
- Ramon Wijnands
nobleo_socketcan_bridge
This package provides functionality to expose CAN frames from SocketCAN to ROS2 topics.
Overview
This is a from-scratch re-implementation of socketcan_bridge from ROS1. There is a different ROS2 package ros2_socketcan which is similar to this package. The differences between this package and ros2_socketcan are:
- No loopback, i.e. CAN frames that are send are not received by the same node
- No lifecycle management, just run it
- Less CPU usage
Nodes
The main node (socketcan_bridge
) is also available as dynamically loadable component.
The node socketcan_bridge_ee
is also provided that uses the EventsExecutor
that runs a bit more efficient.
socketcan_bridge
Subscribed Topics
-
~/tx
(can_msgs/Frame) Messages received here will be sent to the SocketCAN device.
Published Topics
-
~/rx
(can_msgs/Frame) Frames received on the SocketCAN device are published on this topic.
Parameters
-
interface
(default=can0
) Name of the SocketCAN device, by default these devices are named can0 and upwards. -
read_timeout
(default=1.0
) Maximum duration in seconds to wait for data on the file descriptor -
reconnect_timeout
(default=5.0
) Sleep duration in seconds before reconnecting to the SocketCAN device
Changelog for package nobleo_socketcan_bridge
1.0.0 (2025-02-12)
- First release
- Contributors: Ramon Wijnands, dkorenkovnl, Rein Appeldoorn, Ferry Schoenmakers, Tim Clephas
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
fmt |
Dependant Packages
Launch files
- test/benchmark.launch.xml
- Copyright (C) 2024 Nobleo Technology B.V. SPDX-License-Identifier: Apache-2.0
-
- rate [default: 5000]
- test/comparison.launch.xml
- Copyright (C) 2024 Nobleo Technology B.V. SPDX-License-Identifier: Apache-2.0
-
- rate [default: 1400]
- node [default: socketcan_bridge]
Messages
Services
Plugins
Recent questions tagged nobleo_socketcan_bridge at Robotics Stack Exchange
![]() |
nobleo_socketcan_bridge package from nobleo_socketcan_bridge reponobleo_socketcan_bridge |
|
Package Summary
Tags | No category tags. |
Version | 1.0.0 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/nobleo/nobleo_socketcan_bridge.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-02-17 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Ramon Wijnands
Authors
- Ramon Wijnands
nobleo_socketcan_bridge
This package provides functionality to expose CAN frames from SocketCAN to ROS2 topics.
Overview
This is a from-scratch re-implementation of socketcan_bridge from ROS1. There is a different ROS2 package ros2_socketcan which is similar to this package. The differences between this package and ros2_socketcan are:
- No loopback, i.e. CAN frames that are send are not received by the same node
- No lifecycle management, just run it
- Less CPU usage
Nodes
The main node (socketcan_bridge
) is also available as dynamically loadable component.
The node socketcan_bridge_ee
is also provided that uses the EventsExecutor
that runs a bit more efficient.
socketcan_bridge
Subscribed Topics
-
~/tx
(can_msgs/Frame) Messages received here will be sent to the SocketCAN device.
Published Topics
-
~/rx
(can_msgs/Frame) Frames received on the SocketCAN device are published on this topic.
Parameters
-
interface
(default=can0
) Name of the SocketCAN device, by default these devices are named can0 and upwards. -
read_timeout
(default=1.0
) Maximum duration in seconds to wait for data on the file descriptor -
reconnect_timeout
(default=5.0
) Sleep duration in seconds before reconnecting to the SocketCAN device
Changelog for package nobleo_socketcan_bridge
1.0.0 (2025-02-12)
- First release
- Contributors: Ramon Wijnands, dkorenkovnl, Rein Appeldoorn, Ferry Schoenmakers, Tim Clephas
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
fmt |
Dependant Packages
Launch files
- test/benchmark.launch.xml
- Copyright (C) 2024 Nobleo Technology B.V. SPDX-License-Identifier: Apache-2.0
-
- rate [default: 5000]
- test/comparison.launch.xml
- Copyright (C) 2024 Nobleo Technology B.V. SPDX-License-Identifier: Apache-2.0
-
- rate [default: 1400]
- node [default: socketcan_bridge]