ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
It looks like the CAN device driver has problems while sending out messages. The ros_canopen driver sends updates in burst writes, so the queue just might have run full.
Which CAN driver do you use? For the mainline kernel driver it might help to set the TX queuelen to a higher value: sudo ip link set <network> txqueuelen 15", it defaults to 10. If this does not help, can you please provide a candump? (e.g. via gist.github.com).
I have just filed an issue for the queue overrun: https://github.com/ros-industrial/ros_canopen/issues/102
2 | No.2 Revision |
It looks like the CAN device driver has problems while sending out messages. The ros_canopen driver sends updates in burst writes, so the queue just might have run full.
Which CAN driver do you use?
For the mainline kernel driver it might help to set the TX queuelen to a higher value: value with
sudo ip link set <network> txqueuelen 15", 15 # it defaults to 10.
If this does not help, can you please provide a candump? (e.g. via gist.github.com).
I have just filed an issue for the queue overrun: https://github.com/ros-industrial/ros_canopen/issues/102
3 | No.3 Revision |
It looks like the CAN device driver has problems while sending out messages. The ros_canopen driver sends updates in burst writes, so the queue just might have run full.
Which CAN driver do you use?
For the mainline kernel driver it might help to set the TX queuelen to a higher value with
with:
sudo ip link set <network> txqueuelen 15 # it defaults to 10.
10.
If this does not help, can you please provide a candump? (e.g. via gist.github.com).
I have just filed an issue for the queue overrun: https://github.com/ros-industrial/ros_canopen/issues/102