Felix Exner (fexner)

Thanks for reporting this. We'll have to dig into that a bit...

I've added automatic issue closing. A couple of [exceptions](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/94efc8112b8191e08ec6cbe6de163c74ed3b7f37/.github/workflows/stale.yml#L29) should prevent handling issues with special labels. @stefanscherzinger could you have a look whether you think this list is complete. PRs...

@stefanscherzinger I checked output of the debug run and this seems to work as expected. Could you please have another look on the parameters?

This seems unusual at first. The console_bridge issues should probably be gone with https://github.com/UniversalRobots/Universal_Robots_Client_Library/pull/74 merged. As for the `-D__STDC_FORMAT_MACROS` definition: Why is this necessary?

Thanks @gavanderhoorn From my point of view none of the changes here should then be necessary with the latest versions. @nberliner could you try building the driver without the changes...

Now that we have an open issue clearly covering this: There is a [PR going on](https://github.com/ros-industrial/universal_robot/pull/371) changing a lot in generating the robot descriptions. We plan to merge this in...

@ametrix thanks for explicitly reporting this. We have that on our radar and hopefully will find the time to tackle this soon.

I cannot really reproduce this:  Could you please check the output of `rosrun tf tf_echo tool0 tool0_controller`? Since you are using a simulated robot with (assumably) no configured calibration...

To narrow it down: You could check the reported transformation between `base` and `tool0_controller` on ROS. This should be exactly the same as you see on the TP when selecting...

> High-level initial feedback: don't use `rospy` here. > > I'd make this a stand-alone tool, which still checks the same things, but doesn't use ROS parameters or logging. >...