Unable to start UR5 under ROS Melodic

asked 2021-01-04 19:54:53 -0500

Alejandro Velasquez gravatar image

updated 2021-01-06 03:38:56 -0500

gvdhoorn gravatar image

Hello, I am trying to start using the UR5 robot with ROS. Platform: The specific OS that I am using is UBUNTU 18.04, and ROS melodic.

  • ROS_ETC_DIR=/opt/ros/melodic/etc/ros
  • ROS_ROOT=/opt/ros/melodic/share/ros
  • ROS_MASTER_URI=http://localhost:11311
  • ROS_VERSION=1 ROS_PYTHON_VERSION=2
  • ROS_PACKAGE_PATH=/home/avl/ur5_ws/src:/opt/ros/melodic/share
  • ROSLISP_PACKAGE_DIRECTORIES=/home/avl/ur5_ws/devel/share/common-lisp
  • ROS_DISTRO=melodic*

I have been following the instructions from Universal Robots: https://github.com/UniversalRobots/Un...

However I am getting the following error message when I try run the bringup file:

[INFO] [1609809246.480823]: Controller Spawner: Loaded controllers: joint_state_controller, scaled_pos_joint_traj_controller, speed_scaling_state_controller, force_torque_sensor_controller
Traceback (most recent call last):
  File "/opt/ros/melodic/lib/controller_manager/spawner", line 212, in <module>
    if __name__ == '__main__': main()
  File "/opt/ros/melodic/lib/controller_manager/spawner", line 204, in main
    resp = switch_controller(loaded, [], 2, False, 0.0)
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 442, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 532, in call
    raise ServiceException("transport error completing service call: %s"%(str(e)))
rospy.service.ServiceException: transport error completing service call: unable to receive data from sender, check sender's logs for details
================================================================================REQUIRED process [ur_hardware_interface-3] has died!
process has died [pid 3495, exit code -11, cmd /home/avl/ur5_ws/devel/lib/ur_robot_driver/ur_robot_driver_node __name:=ur_hardware_interface __log:=/home/avl/.ros/log/4c31743e-4ef3-11eb-8257-0492260a46a3/ur_hardware_interface-3.log].
log file: /home/avl/.ros/log/4c31743e-4ef3-11eb-8257-0492260a46a3/ur_hardware_interface-3*.log
Initiating shutdown!
================================================================================
[INFO] [1609809246.596238]: Shutting down spawner. Stopping and unloading controllers...
[INFO] [1609809246.597208]: Stopping all controllers...
[WARN] [1609809246.598873]: Controller Spawner error while taking down controllers: unable to connect to service: [Errno 111] Connection refused
[ur_hardware_interface/ur_robot_state_helper-7] killing on exit
[controller_stopper-6] killing on exit
[ros_control_stopped_spawner-5] killing on exit
[ros_control_controller_spawner-4] killing on exit
[ur_hardware_interface-3] killing on exit
[robot_state_publisher-2] killing on exit
[INFO] [1609809246.713667]: Shutting down spawner. Stopping and unloading controllers...
[INFO] [1609809246.716995]: Stopping all controllers...
[WARN] [1609809246.725097]: Controller Spawner error while taking down controllers: unable to connect to service: [Errno 111] Connection refused
[controller_stopper-6] escalating to SIGTERM
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Any thoughts about it?

edit retag flag offensive close merge delete

Comments

The log shows a SEGFAULT, which typically indicates there is a problem with the binary itself, or any of its binary dependencies.

Are you building ros_control (or the controllers) from source?

Can you make sure you don't have any outstanding updates to ROS packages?

gvdhoorn gravatar image gvdhoorn  ( 2021-01-06 03:41:06 -0500 )edit

I ran into the exact same problem today, were you able to fix it already?

JaFeKl gravatar image JaFeKl  ( 2021-01-07 11:27:11 -0500 )edit