[BC1]

I would recommend turning off Windows firewall and reboot the robot controller. Let me know if you still have issues and provide a screenshot of the log window. You can also try to delete the this file:
C:\Users\username\AppData\Roaming\RoboDK-Drivers\apikuka.exe.ini
It will be generated automatically next time you try to connect. I would try to increase the timeout if you are not directly connected to the robot.

Changing COM_ROUNDM won't help as this is internally managed by RoboDKsynch.src file.

Hi Albert,

I've attempted all of the suggestions you've made but the problem is still present. I've attached a zip file with screenshots.

The steps I've taken are outlined below:

Removed antivirus software from KRC2 controller
Turned off firewall on the computer running RoboDK
Deleted apikuka.exe.ini
Rebooted KRC2 controller
Verified connection on Kukavarproxy
started RoboDKsync35 on robot(running in auto mode in a continuous loop)
Pinged the controller
changed the timeout setting to a longer duration
Connected RoboDK
Sent the get joints command

Results:
Once I sent the get joints command, RoboDK disconnected and reconnected immediately. Changing the timeout to a longer duration did not appear to affect the disconnect and reconnect time. Kukavarproxy showed the same results as shown in the image from my initial post.