RTDE timeout issues

I am having troubles with the RTDE record.py program. I am getting a timeout message as seen below:

Does anyone have a solution to this problem?

Thanks,

Check IP address. Are you specifying the robot host with --host in your launch command? Can you ping the robot from the system running record.py?

@roguebuck thanks for the help!

I checked the IP address as seen in the image below:

I also pinged the robot with the command prompt and got the image below:

The robot’s IP address is set to a static address.

I tried filling the hostname variable with both the IP address 192.168.1.17 and the hostname which is ur-20173355688.

Again thanks for the help.

looks like you have a network problem. Your screenshot of the robot says “Not Connected to Network”

Ping results imply the same.

I know this sounds rudimentary but most root causes are very silly in hindsight … Is the robot physically plugged into the network?

Try a ping with the computer plugged directly into the robot to eliminate potential sources of error.

@roguebuck good eye.

Just to let you know the top screenshot was only for an IP address reference. The, “Not connected to network” message goes away when I plug an Ethernet cable from the robot to a laptop.

The set up menu where I checked the IP address, mask and gateway also say it’s connected when I plug in the Ethernet cable.

Do you know if I need to enable the Installation EtherNet/IP Adapter helps?

ok, great. but you still cant ping. so there is still a network misconfiguration.

what is the IP of the laptop?

No, “Ethernet/IP” is a particular fieldbus protocol. You do not need it enabled, but I dont think its relevant here and I dont think it matters in this case.

@roguebuck I got my laptop connected to the robot and ran the record.py file. In a few seconds it generated a csv file with over 19,000 linens of data. The problem was my laptop had firewalls the IT department had to remove.

Thanks for the help.

1 Like

Yup…its usually the silliest things.

FYI - “PING: general failure” is telling us its failing harder than just not getting a ping response. general failure implies the ping never even left the computer.