Mathias Lüdtke
Mathias Lüdtke
Like https://answers.ros.org/question/380751/why-canopen_motor_node-exit-code-6/
For kinetic: - [ ] fail gracefully if a standard mode does not work - [ ] ~~auto-support all
Currently, the socketcan_bridge nodes to not handle error. There is no inteface to read the state or any way to recover the interface. (via http://answers.ros.org/question/267980/socketcan_bridge_node-error-handling/)
Support for boolean data could be added for SDOs. However, the PDO granularity will be kept at 8, so single bits cannot be mapped for performance reasons. The following should...
Setting class is already used for Motor layer. Using it in 301 and CAN increases flexibility.
* Implement option to turn off homing at init * Provide function to trigger the homing individually: 1. Stop ros_control 2. trigger homing for selected joints in parallel 3. restart...
replaces #30 - [ ] style guide - [ ] logging macros (https://github.com/ros-industrial/ros_canopen/pull/286#discussion_r299508615) - [ ] `make_shared` usage - [ ] layer system documentation
`socketcan_bridge` lacks the [option](https://github.com/ros-industrial/ros_canopen/blob/kinetic-devel/canopen_chain_node/src/ros_chain.cpp#L232) to use a different driver plugin.
As pointed out in #183 PDOs cannot be mapped twice. This patch checks for this case and stops further processing. @JuliusGel: Can you test this fix, please. I don't have...