Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Connect to UR5
#41
Hi Albert.

Thanks for your reply. I have full administrator rights on all the computers I have tried. Antivirus has been disabled with no change in the connection status.

The fact that I can connect the PC to a UR5 running a CB3 controller and it connects without issue means its not an issue with the network, port, or the establishment of the server as you indicate - it must be something else specific to the older CB2 controller.
#42
Are you using a recent version of RoboDK?
Did you set the controller variable to 1 as specified here?
https://robodk.com/forum/Thread-Connect-...585#pid585

Do you get any errors or warnings on the robot?
On a command line window (Windows key + Run, then, type cmd), type:
netstat
You should see your computer's IP listed with the port (the port you specified in the connection parameters)
#43
Hi Albert.

I have answered your questions in previous posts:

- latest version of RoboDK
- variable set to 1
- no errors or warnings

Using netstat and TCPView for Windows (part of Windows Sysinternals), I can see connections being negotiated and established with our CB3-based UR5, but with the CB2-based UR5 the connection is never established. Instead, it gets stuck in the listening state. I am currently running SW 1.8.16941, having downgraded from SW 1.8.25319 to see if it was a UR software issue, but the situation remains the same. I am currently trying to determine the software version that originally shipped with the CB2 robot - I believe it was 1.8.16941, but am verifying with our local agent to be sure.
#44
Having downgraded through several software revisions with no change in outcome, the only conclusion I am able to draw is that it is not possible to use RoboDK with a CB2-based UR5. Again, if any readers of this thread have managed to successfully connect to their CB2-based UR5 using RoboDK, please let the rest of us know, as at this stage I am out of ideas.
#45
Let's try to set up the UR driver manually:
  1. Take the file attached and update the IP and port in the first 2 lines (IP of the robot and the communication port you specify in RoboDK).
  2. You can load the attached file on the robot and run it (you'll need to setup a new program to run a script file as shown here).
  3. You may see errors in the log (let me know if this is the case).
If you don't see any errors it means something is blocking the connection (firewall, antivirus or Windows user account control doesn't let you setup a server connection).


Attached Files
.zip   RoboDK_driver.zip (Size: 1.67 KB / Downloads: 8)
  




Users browsing this thread:
1 Guest(s)