Show EOL distros: 

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

Package Summary

A generic canopen implementation for ROS

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

Package Summary

A generic canopen implementation for ROS

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

Package Summary

A generic canopen implementation for ROS

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

Package Summary

A generic canopen implementation for ROS

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

Package Summary

A generic canopen implementation for ROS

Contents

  1. Overview

Experimental

EXPERIMENTAL: This status indicates that this software is experimental code at best. There are known issues and missing functionality. The APIs are completely unstable and likely to change. Use in production systems is not recommended. All code starts at this level. For more information see the ROS-Industrial software status page.

Overview

The packages provides support for CANopen devices within ROS.

It can be divided into different parts:

  • CAN layer abstraction
  • CANopen master with device/object management
  • Profile-specific support, currently only for 402 profile (drives and motion control)
  • ROS interfaces, motion control through ros_control

ros canopen package structure

Wiki: ros_canopen (last edited 2015-05-18 14:26:10 by MathiasLuedtke)