nobleo_socketcan_bridge

Simple wrapper around SocketCAN

• Links
  • Rosindex
  • Repository
  • Bugtracker
• C++ API
  • Class Hierarchy
  • File Hierarchy
  • Full C++ API

• Standard Documents
  • README
  • PACKAGE
  • CHANGELOG
  • LICENSE
• Ros Package Dependencies
  • can_msgs
  • diagnostic_msgs
  • diagnostic_updater
  • rclcpp
  • rclcpp_components

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