ROS index logo ROS Index
  1. Home
  2. Repos
 
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
jazzy

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
kilted

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
rolling

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro ardent showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro bouncy showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro crystal showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro eloquent showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro dashing showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro galactic showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro foxy showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
iron

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro lunar showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro jade showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro indigo showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro hydro showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro kinetic showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro melodic showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING

No version for distro noetic showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

nobleo_socketcan_bridge repository

nobleo_socketcan_bridge

ROS Distro
humble

Repository Summary

Checkout URI https://github.com/nobleo/nobleo_socketcan_bridge.git
VCS Type git
VCS Version main
Last Updated 2025-10-07
Dev Status MAINTAINED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
nobleo_socketcan_bridge 1.0.3

README

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

CONTRIBUTING