Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

As pointed out in the wiki:

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).

The "node" in canopen_chain_node refers to a ROS node, not CANopen node.

I would like for it to create a canopen node on my ROS-pc with its own object dictionary

At the moment ros_canopen only contains the master implemention. A ROS node that is a CANopen slave node to a CANopen master is an interesting use case. Please open an issue to describe this feature.

As pointed out in the wiki:

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).

The "node" in canopen_chain_node refers to a ROS node, not CANopen node.

I would like for it to create a canopen node on my ROS-pc with its own object dictionary

At the moment ros_canopen only contains the master implemention. implementation. A ROS node that is a CANopen slave node to a CANopen master is an interesting use case. Please open an issue to describe this feature.