Felix Exner (fexner)

I'll mark this an enhancement, as this is not necessarily at the top of our priority list.

As the [docs state](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/master/ur_robot_driver/doc/ROS_INTERFACE.md#zero_ftsensor-std_srvstrigger) an e-Series robot has to be in remote_control mode in order to use this service. Do you have n e-Series robot and did you do that?

See https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/master/ur_robot_driver/README.md#remote-control-mode for a short introduction to remote_control mode. There is no such thing as "external control mode". The URCap delivered with this driver simply starts a program node on...

> Resetting/taring the force-torque sensor is not implement in the current version of the driver. This not entirely true. We do offer [a service for taring](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/master/ur_robot_driver/doc/ROS_INTERFACE.md#zero_ftsensor-std_srvstrigger). However, that currently has...

Thank you for reaching out! The parameters shown are not necessarily unusual. It is rather common for UR robots to have very large values for `d` in joint 2 and...

This still requires some work regarding making posts into PRs and job error output possible... Will postpone this for now.

Yes, this is unfortunately still the state. I do have this on my current work plate though, so if nothing severely comes in between I am confident to have something...

Hi, thank you for reporting this. And also, thank you for providing the tutorial. It is not forgotten, time resources are always rare... The problem you described have been reported...

https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/944 should resolve this.

Closing this as the given answer seems to be appropriate.