ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Universal Robots Driver ROS2 not working

asked 2023-06-27 08:55:37 -0500

ledrag gravatar image

I'm trying to control an UR5 Robot arm using ROS2. To achieve this i've been using the following repo as guideline: https://github.com/UniversalRobots/Un...

I'm running this on Ubuntu 22.04.02 and using ROS2 Humble

When i try to launch the driver i get the following logs:

ros2 launch ur_robot_driver ur_control.launch.py ur_type:=ur5 robot_ip:=10.100.129.39 launch_rviz:=false

[INFO] [launch]: All log files can be found below /home/ur-control/.ros/log/2023-06-27-15-10-38-716282-u22lts-urcontrol-46884
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [dashboard_client-2]: process started with pid [46889]
[INFO] [controller_stopper_node-3]: process started with pid [46891]
[INFO] [ur_ros2_control_node-1]: process started with pid [46887]
[INFO] [robot_state_publisher-4]: process started with pid [46893]
[INFO] [spawner-5]: process started with pid [46895]
[INFO] [spawner-6]: process started with pid [46897]
[INFO] [spawner-7]: process started with pid [46899]
[INFO] [spawner-8]: process started with pid [46901]
[INFO] [spawner-9]: process started with pid [46930]
[INFO] [spawner-10]: process started with pid [46937]
[dashboard_client-2] [INFO] [1687871439.398742580] [UR_Client_Library]: Connected: Universal Robots Dashboard Server
[dashboard_client-2] 
[controller_stopper_node-3] [INFO] [1687871439.398103120] [Controller stopper]: Waiting for switch controller service to come up on controller_manager/switch_controller
[ur_ros2_control_node-1] terminate called after throwing an instance of 'std::runtime_error'
[ur_ros2_control_node-1]   what():  text not specified in the tf_prefix tag
[robot_state_publisher-4] [INFO] [1687871439.427927325] [robot_state_publisher]: got segment base
[robot_state_publisher-4] [INFO] [1687871439.428226479] [robot_state_publisher]: got segment base_link
[robot_state_publisher-4] [INFO] [1687871439.428249023] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-4] [INFO] [1687871439.428257832] [robot_state_publisher]: got segment flange
[robot_state_publisher-4] [INFO] [1687871439.428265292] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-4] [INFO] [1687871439.428272157] [robot_state_publisher]: got segment ft_frame
[robot_state_publisher-4] [INFO] [1687871439.428278847] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-4] [INFO] [1687871439.428285812] [robot_state_publisher]: got segment tool0
[robot_state_publisher-4] [INFO] [1687871439.428292984] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-4] [INFO] [1687871439.428301409] [robot_state_publisher]: got segment world
[robot_state_publisher-4] [INFO] [1687871439.428312288] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-4] [INFO] [1687871439.428322226] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-4] [INFO] [1687871439.428332326] [robot_state_publisher]: got segment wrist_3_link
[ERROR] [ur_ros2_control_node-1]: process has died [pid 46887, exit code -6, cmd '/home/ur-control/workspace/ros_ur_driver/install/ur_robot_driver/lib/ur_robot_driver/ur_ros2_control_node --ros-args --params-file /tmp/launch_params_v5mj3prx --params-file /home/ur-control/workspace/ros_ur_driver/install/ur_robot_driver/share/ur_robot_driver/config/ur5e_update_rate.yaml --params-file /home/ur-control/workspace/ros_ur_driver/install/ur_robot_driver/share/ur_robot_driver/config/ur_controllers.yaml'].
[spawner-10] [INFO] [1687871441.826413906] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1687871441.848227602] [spawner_scaled_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1687871441.886653953] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-9] [INFO] [1687871441.903905257] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1687871441.911055867] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1687871441.920189700] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-10] [INFO] [1687871443.849888060] [spawner_forward_position_controller]: Waiting for '/controller_manager' node to exist
[spawner-5] [INFO] [1687871443.871522619] [spawner_scaled_joint_trajectory_controller]: Waiting for '/controller_manager' node to exist
[spawner-6] [INFO] [1687871443.910050317] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-9] [INFO] [1687871443.926036279] [spawner_force_torque_sensor_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-8] [INFO] [1687871443.934576269] [spawner_speed_scaling_state_broadcaster]: Waiting for '/controller_manager' node to exist
[spawner-7] [INFO] [1687871443.943109006] [spawner_io_and_status_controller]: Waiting for '/controller_manager' node to exist
[spawner-10] [INFO] [1687871445.872573721] [spawner_forward_position_controller]: Waiting for '/controller_manager ...
(more)
edit retag flag offensive close merge delete

Comments

Looks like UniversalRobots/Universal_Robots_ROS2_Driver#718.

As this is an actual problem with the sw, as opposed to some configuration or usage question, I'd recommend diagnosing on the issue tracker instead of here on ROS Answers.

gvdhoorn gravatar image gvdhoorn  ( 2023-06-27 12:30:56 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2023-07-07 08:31:23 -0500

fexner gravatar image

As a follow-up: This has been resolved in the driver. See https://github.com/UniversalRobots/Un...

edit flag offensive delete link more

Question Tools

Stats

Asked: 2023-06-27 08:55:37 -0500

Seen: 353 times

Last updated: Jun 27 '23