Felix Exner (fexner)

Regarding this thread: Using the Robotiq_Gripper URCap and connecting to Port 63352 (at least that was the case for me, maybe 65332 was a typo @firesurfer?) currently seems the best...

@rrapi thanks for sharing this with us! This seems like a very inconvenient workaround, but as I stated earlier: I experienced occasional multiple starts in the past as well, but...

The problem actually goes a bit deeper than that... If the driver gets started before the UR-controller is actually booted, things get bad as some subsystems are restarted again. As...

In my opinion this seems like a workaround for some use cases, but not a proper solution. You are right, that the problem is twofold: - We need to make...

As a lot of this has to be fixed inside the client library, I've created a new issue there (https://github.com/UniversalRobots/Universal_Robots_Client_Library/issues/94) describing the points that would have to be addressed in...

I can follow your argumentation and the relevant information is probably available in the used interfaces. I'll mark this as "enhancement", so I see that as a feature request. I...

You will need a driver for your gripper, this is nothing the ur_robot_driver will do for you. If you take a look at the [`ros_control` documentation](http://wiki.ros.org/ros_control) there usually is a...

Yes, that definitely sounds like an interesting question. We've never tested that, so if you gain any knowledge on that it would be nice if you could share that here...

@MiroslavKohut So you got the driver running on WSL2? Thank you for posting your experience here, this is a great addition!

Another issue is that the publishers publishing one message per joint (e.g. the temperatures) don't publish all messages due to a configured queue size of one. ``` $ rostopic echo...