| canopen |
|
|
meta-ros2-rolling |
| canopen-402 |
0.8.5-1 |
This implements the CANopen device profile for drives and motion control. CiA(r) 402 |
meta-ros1-noetic |
| canopen-402-driver |
|
|
meta-ros2-rolling |
| canopen-base-driver |
|
|
meta-ros2-rolling |
| canopen-chain-node |
0.8.5-1 |
Base implementation for CANopen chains node with support for management services and diagnostics |
meta-ros1-noetic |
| canopen-core |
|
|
meta-ros2-rolling |
| canopen-fake-slaves |
|
|
meta-ros2-rolling |
| canopen-interfaces |
|
|
meta-ros2-rolling |
| canopen-master |
0.8.5-1 |
CiA(r) CANopen 301 master implementation with support for interprocess master synchronisation. |
meta-ros1-noetic |
| canopen-master-driver |
|
|
meta-ros2-rolling |
| canopen-motor-node |
0.8.5-1 |
canopen_chain_node specialization for handling of canopen_402 motor devices. It facilitates interface abstraction with ros_control. |
meta-ros1-noetic |
| canopen-proxy-driver |
|
|
meta-ros2-rolling |
| canopen-ros2-control |
|
|
meta-ros2-rolling |
| canopen-ros2-controllers |
|
|
meta-ros2-rolling |
| canopen-tests |
|
|
meta-ros2-rolling |
| canopen-utils |
|
|
meta-ros2-rolling |
| cob-canopen-motor |
0.7.14-1 |
The package cob_canopen_motor implements a controller-drive component which is connected to a can-bus and works with a canopen-interface. "CanDriveItf" provides a - more or less - generic interface to the controller-drive components. "CanDrvie..." then implements a specific setup, e.g. an ELMO Harmonica Controller in case of the "CanDriveHarmonica". |
meta-ros1-noetic |
| ros-canopen |
0.8.5-1 |
A generic canopen implementation for ROS |
meta-ros1-noetic |