The RoboDK driver connections to UR control systems are bidirectional. This means that the driver not only connects to the remote system as a client, but also acts as a server at the same time, waiting for a counter connection from the control system. That counter connection from the UR control system to the RoboDK computer is considered by the latter as an external incoming connection. Such connections are most often blocked by the operating system firewall. If completely disabling the firewall on your system is not acceptable, then use the table below to accept the necessary inbound and outbound connections:
Purpose | Direction | Protocol | Port Number (apiur) | Port Number (DriverUR) |
Secondary Interface | RoboDK → UR | TCP | 30002 | 30002 |
Real-Time Interface (RTDE) | RoboDK → UR | TCP | not used | 30004 |
Reverse Interface | UR → RoboDK | TCP | 30000 | 50001 |
Script Sender | UR → RoboDK | TCP | not used | 50002 |
Trajectory Interface | UR → RoboDK | TCP | not used | 50003 |
Script Command Interface | UR → RoboDK | TCP | not used | 50004 |