ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
The ros_canopen
ROS nodes do not support NMT broadcasts. Each ROS node is just responsible for its configured CANopen nodes.
This limitation simplifies the management logic and enables to run multiple ROS nodes on the same bus (SharedMaster
plugin). This way each CANopen node can be configured and managed individually.
If you really need NMT broadcasting you can inherit from RosChain::ChainNode
and customize its behaviour.
However, the NMT message class is not exposed by intention: I don't see a benefit from broadcasting and it might not be safe to broadcast to a CAN bus without knowing the state of the CANopen nodes.
(Maybe I should even consider sending a stop to all configured node before initializing them.)
Feel free to open an issue on github with a more specific request and some explanations on your use case. We could then figure out if some NMT interfaces could be exposed for easier customisation.