Controlling Tool Output while using a newer version of the Robotiq Gripper URCap is not possible about universal_robots_ros2_driver HOT 7 OPEN

I don't quite understand how this relates to our ROS 2 driver. We use the RTDE protocol to read the robot state, move the arm and set i/os. This did not change.

What exactly do you want to achieve? Why do you need to be able to directly set tool i/os if the robotiq urcap is used?

from universal_robots_ros2_driver.

@RobertWilbrandt

1. Why do I want to set one of the tool outputs while the robotiq urcap is used?

The robotiq 2f-85 only uses one of the outputs as power supply. We use the second one to control an electromagnet mounted at the wrist.
Being able to control the gripper from remote + from the teach panel is very convenient for testing.

2. Apparently setting the output via the urscript instead of RTDE still works with newer versions of the urcap.

As neither UR nor Robotiq want to do anything about this the only way of having this very convenient feature is by changing the way the IOs are controlled in the ROS driver....

from universal_robots_ros2_driver.

I see, that makes sense.

We are aware that using RTDE for IOs can lead to problems when integrating with additional equipment (also e.g. if you try to control the UR IOs from a PLC while controlling the joints through ROS). Enabling IO control through a different interface is on our roadmap, but we don't have a timeline for that yet.

@urrsk do you maybe have some more information on this specific conflict with robotiq?

from universal_robots_ros2_driver.

@firesurfer you have a good point and we are aware about it. In general, we are missing a good way to integrate URCaps with the use of the ROS drivers.
On the short term, regarding the digital and analog outputs, we have talked about expending the script_commands thread in the Universal_Robots_Client_Library/resources/external_control.urscript#L496 to also control the outputs as an alternative to use RTDE.

from universal_robots_ros2_driver.

@urrsk
Could you perhaps elaborate why it should make a difference to control an IO via RTDE or via a urscript? In both cases one would need to accept that one can interfere with the settings from an installed URcap (or it has to be blocked). Unfortunately I did't get any useful answer from the UR support why this specific behavior has been changed (That the robotiq urcap may only control the gripper if the IOs are controlled by the urcap) .

from universal_robots_ros2_driver.

@firesurfer Our current way of managing the Tool Connector have it limitations. The intend with selecting one owner is that they are in control. In the past we have seen cases with other tool manufactures tools have been disturbed by the presence of Robotiqs URCap, even when they were selected as owner of the tool connector. That is what Robotiq have fixed here.
Is it an option to use the UCG-1.8.13.22852 version of the URCap?

from universal_robots_ros2_driver.

@EbbeFuglsang Thanks for the info.

Is it an option to use the UCG-1.8.13.22852 version of the URCap?

Thats what we are currently doing. But given that there were some necessary updates in the past I would like being able to run the newest version of the URCap to avoid bad surprises in the future.
(E.g. at some point the combination of the URCap and a newer Polyscope version lead to the gripper shutting down during startup because of an over current condition)

Also I would argue that from a user point of view: If I select: Controlled by user, than I would like to be able to control it myself ;)

from universal_robots_ros2_driver.