[Documentation] [TitleIndex] [WordIndex

  Show EOL distros: 

ros_canopen: can_msgs | canopen_402 | canopen_chain_node | canopen_master | canopen_motor_node | socketcan_bridge | socketcan_interface

Package Summary

ROS node base implementation for CANopen chains with support for management services and diagnostics

ros_canopen: can_msgs | canopen_402 | canopen_chain_node | canopen_master | canopen_motor_node | socketcan_bridge | socketcan_interface

Package Summary

ROS node base implementation for CANopen chains with support for management services and diagnostics

ros_canopen: can_msgs | canopen_402 | canopen_chain_node | canopen_master | canopen_motor_node | socketcan_bridge | socketcan_interface

Package Summary

Base implementation for CANopen chains node with support for management services and diagnostics

ros_canopen: can_msgs | canopen_402 | canopen_chain_node | canopen_master | canopen_motor_node | socketcan_bridge | socketcan_interface

Package Summary

Base implementation for CANopen chains node with support for management services and diagnostics

ros_canopen: can_msgs | canopen_402 | canopen_chain_node | canopen_master | canopen_motor_node | socketcan_bridge | socketcan_interface

Package Summary

Base implementation for CANopen chains node with support for management services and diagnostics

Overview

This packages contains the ROS interface for socketcan_interface and canopen_master. It can be used as a stand-alone ROS node, but as well as a base class for profile specific ROS interfaces, e.g. canopen_motor_node.

It manages a CANopen bus with one or more nodes, which are configures with CANopen EDS/DCF files. The ROS node runs a control loop with CANopen SYNC interval (or with an alternative update interval if the SYNC protocol is not used).

Configuration

The configuration can be split into different parts. First the bus has to be set-up, these settings are shared for all node. Then all must be configured with their CANopen and ROS interfaces. All parameters must be loaded into the nodes private namespace

CANopen Bus layer

The bus settings consists of a CAN interface (socketcan_interface) and the shared bus settings for canopen_master.

   1 bus:
   2   device: can0 # socketcan network
   3   # loopback: false # socket should loop back messages
   4   # driver_plugin: can::SocketCANInterface
   5   # master_allocator: canopen::SimpleMaster::Allocator
   6 sync:
   7   interval_ms: 10 # set to 0 to disable sync
   8   # update_ms: <interval_ms> #update interval of control loop, must be set explecitly if sync is disabled
   9   overflow: 0 # overflow sync counter at value or do not set it (0, default)
  10 heartbeat: # simple heartbeat producer, optional!
  11   rate: 20 # heartbeat rate
  12   msg: "77f#05" # message to send, cansend format: heartbeat of node 127 with status 5=Started

Node layer

All nodes are listed in the nodes parameter, either as list or a struct, and require a node ID, a name and the path to the EDS/DCF file.

   1 # struct syntax
   2 nodes:
   3   node1:
   4     id: 1
   5     eds_pkg: my_config_package # optionals package  name for relative path
   6     eds_file: "my_config.dcf" # path to EDS/DCF file
   7   node2:
   8     id: 85
   9     name: other_mode # optional name
  10     eds_file: "/path/to/my_config.eds" # absolute name

   1 # list syntax
   2 nodes:
   3   - name: node1
   4     id: 1
   5     eds_pkg: my_config_package # optionals package  name for relative path
   6     eds_file: "my_config.eds" # path to EDS/DCF file
   7   - name: node2
   8     id: 85
   9     eds_file: "/path/to/my_config.dcf" # absolute name

Additional parameters can set either for each node or in a defaults section:

   1 defaults: # optional, all defaults can be overwritten per node
   2   eds_pkg: my_config_package # optional package  name for relative path
   3   eds_file: "my_config.dcf" # path to EDS/DCF file
   4   dcf_overlay: # "ObjectID": "ParameterValue" (both as strings)
   5     "1016sub1" : "0x7F0064" # heartbeat timeout of 100 ms for master at 127
   6     "1017": "100" # heartbeat producer

The dcf_overlay can be used to overwrite specific settings in the EDS/DCF.

ROS layer

Each node (or in the defaults) can be passed a publish parameter with a list of object names. The topic types correspond to the object types, e.g. UNSIGNED16 to std_msgs/UInt16. It is meant for debugging or for simple CANopen interfaces, since it blocks the control loop. Each entry can have an exclamation mark appended that forces the driver to reread the object form the node in each step.

For example:

   1 defaults: # optional, all defaults can be overwritten per node
   2   publish: ["1001"] # list of objects to be published (one topic per node)
   3 nodes:
   4   node1:
   5     # ...
   6     publish: ["1003sub0!"] # list of objects to be published (one topic per node)
   7   node2:
   8     # ...
   9   node3:
  10     # ...

will publish on three topics with the sync/update_rate:

The diagnostic_updater can be passed the diagnostic_period parameter in fractional seconds.

ROS API

canopen_chain_node

Published Topics

/diagnostics (diagnostic_msgs/DiagnosticStatus)

Services

driver/init (std_svrs/Trigger) driver/halt (std_svrs/Trigger) driver/recover (std_svrs/Trigger) driver/shutdown (std_svrs/Trigger) driver/get_object (canopen_chain_node/GetObject) driver/set_object (canopen_chain_node/SetObject)

Parameters

~diagnostic_period (double, default: 1.0) ~bus (struct) ~sync (struct) ~heartbeat (struct) ~defaults (struct) ~nodes (struct/list)

Further topics will be published according to the publish parameters.

C++ API

This package provides a canopen::RosChain class that implements a canopen::LayerStack interface and takes care of the parameter parsing and the life-cycle. It can be customized via its virtual interface, especially with RosChain::nodeAdded


2019-06-22 12:32