You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to follow this CombinedRobotHW tutorial I discovered, that ros_canopen is not capable of supporting the necessary class loader plugin. Are there any plans on adding this capability?
The big advantage of this would be the possibility to add custom CAN devices or even Serial controlled devices to a robot running on the CANopen stack.
The text was updated successfully, but these errors were encountered:
@bxc237 I luckily have just a passive rotating joint. To solve the upper mentioned issue I added a simple publisher, which publishes the encoder values to the /joint_states topic. This way I now have two different publishers:
CANopen ros_control: [wheel_left, wheel_right]
Custom encoder node: [body_joint]
It seems the robot_state_publisher is handling this setup just fine, so for me it was a good workaround.
@ivan140: If you want to improve your setup even further, add a joint_state_publisher in between. This will reduce the load of robot_state_publisher and all other nodes, which consume /joint_states or /tf. This is especially useful for MoveIt, which runs collisions checks on each update.
Hi,
When trying to follow this CombinedRobotHW tutorial I discovered, that ros_canopen is not capable of supporting the necessary class loader plugin. Are there any plans on adding this capability?
The files in question are:
ros_canopen/canopen_motor_node/include/canopen_motor_node/robot_layer.h
ros_canopen/canopen_motor_node/include/canopen_motor_node/robot_layer.cpp
The big advantage of this would be the possibility to add custom CAN devices or even Serial controlled devices to a robot running on the CANopen stack.
The text was updated successfully, but these errors were encountered: