06-28-2019, 05:23 PM
I am using RoboDK version 3.8.3 and had Windows Firewall completely disabled.
After some additional testing, I think I have found the source of the issue. I have been using Pycharm to write Python scripts with the RoboDK API, and I was never able to connect to the robot when running the programs directly from Pycharm, however I was consistently able to connect to it when running those same programs through a command prompt. Thus, the error must have to do with the way the programs are being launched rather than the content of the programs themselves. After this realization, I tried running the programs in a different IDE (this time I used Wing) and the problem was solved; I can now successfully connect to the robot using the same Python programs that were giving me errors and crashing the UR driver earlier.
After some additional testing, I think I have found the source of the issue. I have been using Pycharm to write Python scripts with the RoboDK API, and I was never able to connect to the robot when running the programs directly from Pycharm, however I was consistently able to connect to it when running those same programs through a command prompt. Thus, the error must have to do with the way the programs are being launched rather than the content of the programs themselves. After this realization, I tried running the programs in a different IDE (this time I used Wing) and the problem was solved; I can now successfully connect to the robot using the same Python programs that were giving me errors and crashing the UR driver earlier.