Connect two UR robots to RoboDK- Printable Version +- RoboDK Forum (//www.sinclairbody.com/forum) +-- Forum: RoboDK (EN) (//www.sinclairbody.com/forum/Forum-RoboDK-EN) +--- Forum: General questions about RoboDK (//www.sinclairbody.com/forum/Forum-General-questions-about-RoboDK) +--- Thread: Connect two UR robots to RoboDK (/Thread-Connect-two-UR-robots-to-RoboDK) |
Connect two UR robots to RoboDK-NMIS-03-28-2023 Hello, I managed to connect RoboDK to a single UR5e robot and run the programme from computer on the physical robot very well. However, it did not work when the second UR5e was connected to RoboDK (there were two Ethernet cables to connect to each robot separately). I thought that the issue is: there were two static IP addresses (say 192.168.0.1 and 192.168.0.2) assigned in the PC to each Ethernet. But when I tried to connect both robots, it seems only one of the IP addresses was working, the other Ethernet has be assigned a new and irrelevant IP address so that it actually was ignored. I am not sure if that is the reason. It would be very helpful if you may let me know if it is feasible to connect and run two robots and if yes how to do that properly . Thank you very much. RE: Connect two UR robots to RoboDK-Alex-03-28-2023 were you able to ping both robots? RE: Connect two UR robots to RoboDK-NMIS-03-29-2023 (03-28-2023, 07:41 PM)Alex Wrote:were you able to ping both robots? Hi Alex, Yes I could ping both robots successfully. The log file of the first robot (IP:192.168.0.2) which can be connected to RoboDK said ''Sending command... Closing previous connection... Available local IP addresses (IPv4): 192.168.0.1 192.168.0.7 10.***.***.*** Server established: 192.168.0.1:30000 Using custom script file Connected to 192.168.0.2:30002. Sending program progrobodk.script... Updating computer IP on program: 192.168.0.1 Updating computer port on program: 30000 Program sent. Waiting... Connected to 192.168.0.2 Ready'' By contrast, the second robot (IP:192.168.0.22) said ''Sending command... Available local IP addresses (IPv4): 192.168.0.1 192.168.0.7 10.***.***.*** Problems opening server at: 192.168.0.1:30000 Disconnected'' It seems the right Ethernet IP 192.168.0.7 which connects to the second robot has been ignored. 如果我f之间的断开连接的以太网电缆irst robot and the laptop, the second robot could connect to RoboDK successfully. The log file said ''Available local IP addresses (IPv4): 192.168.0.7 10.***.***.*** Server established: 192.168.0.7:30000 Using custom script file Connected to 192.168.0.22:30002. Sending program progrobodk.script... Updating computer IP on program: 192.168.0.7 Updating computer port on program: 30000 Program sent. Waiting... Connected to 192.168.0.22 Ready'' RE: Connect two UR robots to RoboDK-Albert-03-29-2023 You should simply change the connection port for the second robot:
RE: Connect two UR robots to RoboDK-NMIS-03-29-2023 (03-29-2023, 09:36 AM)Albert Wrote:You should simply change the connection port for the second robot: Hi Albert, Thank you very much. It works! RE: Connect two UR robots to RoboDK-Albert-03-29-2023 Great! Thank you for your feedback. |