Felix Exner (fexner)
Felix Exner (fexner)
There are a couple of calls missing from the dashboard server, especially since Versions 3.12/5.6 - [ ] PolyscopeVersion - [ ] setUserRole - [ ] set operational mode (eSeries...
There have been multiple issues (e.g. #233, #307) related to ABI incompatibilities. Especially as we provide controller plugins for the scaled controllers, this might be an issue coming up more...
The robot's primary interface actually reports errors in executed script code via a `ROBOT_MESSAGE` of type `ROBOT_MESSAGE_TYPE_RUNTIME_EXCEPTION`. We can catch those and at least print a warning. This way false...
When an e-Series robot runs in local mode, script code sent through the primary interface is ignored. However, the user doesn't get notified of this. Unfortunately, we cannot read whether...
Since we've changed the launchfile structure quite significantly, we should add that to the migration notes.
In the ROS 1 FAQ we had it [written explicitly](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver?tab=readme-ov-file#i-started-everything-but-i-cannot-control-the-robot) what to do if the robot doesn't move. We should write that down explicitly in the ROS 2 documentation, as...
This seems to be necessary for older compilers (e.g. gcc 8.5 on RHEL8) See e.g. https://build.ros2.org/job/Hbin_rhel_el864__ur_calibration__rhel_8_x86_64__binary/23/console This might be necessary for rolling, as well, but for rolling a lot of...
Currently, we don't publish the tcp pose that is reported from the robot. In ROS1 we used to publish this as `tool0_controller` which proved to be helpful either for debugging...
See [ROS1 driver](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/222d67aad0bfb4f35e7acc32d34b4fb74710c0bd/ur_robot_driver/config/ur10_controllers.yaml#L34). This should make maintenance easier.
Since #716 we process the tolerances set from the action goal. This was done as described in https://github.com/ros-controls/control_msgs/blob/65814d985aa29bed0adfaed5f2ebd8cf26266056/control_msgs/action/FollowJointTrajectory.action#L6-L10 and https://github.com/ros-controls/control_msgs/blob/65814d985aa29bed0adfaed5f2ebd8cf26266056/control_msgs/msg/JointTolerance.msg#L7-L10. However, the `goal_time_tolerance` was always overwritten with the value from...