[RBE]

Unfortunately it appears I spoke too soon. Making the recommended change to the .ini file (and setting the timeout to 5000ms) results in the following RoboDK log output:

Disconnected
Stopped
Starting robot driver: C:/RoboDK/api/robot/apiur.exe
Starting...
CONNECT 192.168.0.1 30002 6
MoveJ with Joints: Yes
MoveL with Joints: Yes
MoveL as: movel(...)
Controller Version: 1
Communication Timeout (ms): 5000
Disconnected
Available local IP addresses (IPv4):
132.181.60.62
192.168.0.10
Server stablished at: 192.168.0.10:30002
Warning: Using older controller compatibility (IO not supported)
Connected to 192.168.0.1:30002. Sending program :/progrobodk_basic.script...
Updating computer IP on program: 192.168.0.10
Updating computer port on program: 30002
Program sent.
Waiting...

Note that I can ping the controller, and explore its file system from within RoboDk using FileZilla, but I am unable to connect to the robot. Any other suggestions as to what may be causing the issue?

Update: I have pushed the latest version of PolyScope (1.8.25319) onto the controller, but this has not improved the situation. I have used FileZilla to search for the 'progrobodk_basic.script' file on the controller after RoboDK said it had been sent, but can find no evidence of the file on the controller.