Connecting to Universal Robot

asked 2022-09-27 03:45:43 -0500

LucB
42 ●7 ●12 ●17

updated 2022-10-20 08:50:38 -0500

I try to connect to my UR3e via ROS 2. For this i installed ROS 2 Foxy. To connect to my UR, I installed the Universal Robot package

Now i have some issues, when i finally want to connect to the Robot. I installed the "externalcontrol-1.0.5.urcap" file on the teach pendant. The Pendant is running with the polyscope version 5.12.4. When i start

ros2 launch ur_bringup ur_control.launch.py ur_type:=ur3e robot_ip:=192.168.1.102 use_fake_hardware:=true launch_rviz:=true

i get following error:

[ERROR] [1664263597.180336063] [UR_Client_Library]: Failed to connect to robot on IP 192.168.1.102. Please check that the robot is booted and reachable on 192.168.1.102. Retrying in 10 seconds

Afterwards I start the URCap file on the Panel. There i get the following error

The connection to the remote PC at 192.168.1.110:50002 could not be established. Reason: connection time out

The connection to the remote PC at 192.168.1.110:50002 could not be established. Reason: No route to host (Host unreachable)

The connection to the remote PC at 192.168.1.110:50002 could not be established. Reason: Connection refused (Connection refused)

My ROS2 is running in VMware on Ubuntu 20.04. In my VM, I set up a additional network adapter. The already existing one is set to NAT. The new one is set to network bridge, where i chose the Realtek PCIe Gbe Family Controller which should be my Ethernet socket, where my LAN cable from the UR is connected to. The second Adapter has a static IP address: 192.168.1.110.

Pinging the UR from the virtual machine is possible:

64 bytes from 192.168.1.102: icmp_seq=1 ttl=128 time=1.56 ms

A Ping is possible if both network adapters are activated or just any of them.

Does any of you have a idea where the problem is and how to solve this?.

edit retag flag offensive close merge delete

add a comment

Comments

Could you please quote the relevant parts from that discussion so your answer here is stand-alone?

UR has made their fora only accessible to people with an account in the past (and then changed it back), which if it would happen again would make your link inaccessible. By copy-pasting the relevant parts here, we avoid that problem.

gvdhoorn ( 2022-10-05 03:09:35 -0500 )edit

Here we go

[ur_ros2_control_node-1] [FATAL] [1664881747.865636229] [URPositionHardwareInterface]: Variable 'speed_slider_mask' is currently controlled by another RTDE client. The input recipe can't be used as configured

There seems to be something else running on the robot using the RTDE input fields. Do you have a fieldbus activated? We had a section for that in the ROS1 driver’s README that seems not to have made it to the ROS2 driver.

This could also be caused by another URCap installed on the robot.

Let me add that we are currently working on replacing the requirement on RTDE inputs for most things, but we won’t be able to ditch the RTDE inputs completely in the near future.

LucB ( 2022-10-05 03:57:14 -0500 )edit

So what was the specific cause in your case?

gvdhoorn ( 2022-10-05 05:21:09 -0500 )edit

I hast to disable the EtherNet/IP like explained in the ROS1 driver‘s README.

LucB ( 2022-10-05 12:21:38 -0500 )edit

You mean EtherNet/IP, correct?

gvdhoorn ( 2022-10-05 12:27:34 -0500 )edit

ah, yes. changed that.

LucB ( 2022-10-05 12:29:29 -0500 )edit

add a comment

Connecting to Universal Robot

1 Answer

Comments

Question Tools

Stats

Related questions

Connecting to Universal Robot edit

1 Answer

Comments

Question Tools

Stats

Related questions

Connecting to Universal Robot