Closed karl-exwzd closed 2 years ago
Sorry for the inconvenience. What is the version of Cobotta?
@ToshitakaSuzuki The controller software version is 2.5.1. I had another robot with the controller version 2.8.0 and I could use that one as intended.
Thank you for pointing this out, I will attempt to update the controller software on the first robot.
Did you guys solve this issue? I am also getting this error when I try to launch MoveIt!. What kind of connection does controller software have here? Is it the one which we can see in the pendant? Mine is 2.7.2. What did you do?
@bmunkhtulga First, I would upgrade the robot controller to at least 2.8.0. That would probably solve your issue. As you say, it's the version you see in the pendant.
Do not forget to enable the b-Cap slave extension on the Cobotta, although you'll be reminded of that if you don't have it in RemoteTP.
Thank you very much for your reply. I solved my issue by upgrading the robot controller from 2.7 to 2.16. I never thought of the controller version being the problem.
I would like to control a standard Cobotta robot from ROS Noetic. So far I've been successful in integrating it, but now I face an issue without a clear way to fix it.
When connecting to the robot, launching the bringup file, by executing the following
I get the following error:
There are no error logs on the robot side (checked with RemoteTP) and no further information as to what goes wrong.
I have dug into the source and found that the
ExecManualResetPreparation
does not go though. There is also a note for the fuction that calls it:ExecClearError
saying: Do NOT call on b-CAP Slave, however the tutorial on how to control a Cobotta robot is all about how to enable the b-Cap Slave extension (which I did) to control the robot via ROS. When trying without the extension the robot says that b-Cap Slave must be enabled for it the be controlled this way.From reading other issues, perhaps it is related to some settings/mode I forgot to change/enable in RemoteTP, but I cannot figure out what it could be.
I do not understand what parameter is incorrect or how to proceed from this point. The communication between ROS and the robot is up, but the error is not helpful... I feel like this is the last challenge before I can move the robot from ROS.