Universal_Robots_ROS_Driver icon indicating copy to clipboard operation
Universal_Robots_ROS_Driver copied to clipboard

Universal Robots ROS driver supporting CB3 and e-Series

Results 186 Universal_Robots_ROS_Driver issues
Sort by recently updated
recently updated
newest added

The issue #390 is still an issue in ROS melodic. This means that if you use the pose_based_cartesian_traj_controller or joint_based_cartesian_traj_controller with ROS melodic, the robot will move slightly over time...

bug

# Summary I noticed that by default, many of the moveit config launch files from re-load the robot description. I'm not sure whether this interferes with the calibration offsets loaded...

ToDo

I keep running into rviz crashing after running it for a while to control the robot. The error message shows that there is some clock synchronization issue. Afterwards, I have...

When I connect to URSim (3.12) running UR10 with the ur_robot_driver I continuously get error messages: [ INFO] [1583503125.382218862]: Connection to robot dropped, waiting for new connection. [ INFO] [1583503125.399099714]:...

Currently the README build instructions ask us to clone [fmauch/universal_robot](https://github.com/fmauch/universal_robot), which is a branch in a fork of a fork. I'd like to submit a fix to this repo but...

PR pending

I can't find any code related to the [ROS diagnostic concept](http://wiki.ros.org/diagnostics) Is there any ongoing effort/plan to support this feature? I'd like to - at least - track the operation...

enhancement

Added test of the robot moving slightly over time for both cartesian controllers. This will test the issue #390, however it will fail on melodic, because the issue still exist...

As risen [here](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/issues/418#issuecomment-880348250) it might be a good idea to look at our RT-kernel installation guide, whether it could / should be improved.

documentation

[ERROR] [1631239742.680577697]: Unsuccessful in setting main thread realtime priority. Error code: 1 [ERROR] [1631239742.680666131]: Main thread: Scheduling is NOT SCHED_FIFO!

Solution proposed
close if no update

# Impact Hello! I cannot connect completely to the robot. I followed the required steps in order to connect to the robot. I run the driver on ros, then I...

duplicate
close if no update