ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

I have worked with this particular arm and have faced the same issue. After a lot of digging, I realised that it is not a problem with ROS. You should use a CANalyser to connect to the Schunk MTS tool and check the CAN protocol. Sometimes, it erroneously resets to CAN whereas, it should be CANOpen. Change that back to CANOpen (you might need to change to admin to do that) and that will fix this issue.

I have worked with this particular arm and have faced the same issue. After a lot of digging, I realised that it is not a problem with ROS. You should use a CANalyser to connect to the Schunk MTS tool and check the CAN protocol. Sometimes, it erroneously resets to CAN whereas, it should be CANOpen. Change that back to CANOpen (you might need to change to admin to do that) and that will fix this issue. You can also consider setting the reference values and the joint limits using this tool.

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2