Is there a setting that controls socket access from a script running in Polyscope?
Everything was working correctly for a while, but at some point, opening a socket to access a sensor from a Polyscope script stopped functioning. The same script runs perfectly when executed from a URCap. I suspect I may have inadvertently changed a setting, but I haven’t been able to identify the issue.
On another robot, the script works fine, so the problem doesn’t appear to be with the script itself.
Double check the settings under “Security.” Make sure you aren’t restricting certain ports, and then expand the “Services” tab and just enable all of them. At some point, UR made a Polyscope update that defaults them all to Disabled. Which has screwed me up more than once.
Hello, Eric!
Thank you for the suggestion, I have checked this. All services are active, no restrictions implied. Probably the issue is beyond Polyscope.
Have you disabled Profinet and EthernetIP?
This may sound silly, but have you double-checked that the script hasn’t been modified (accidentally or otherwise)? If it is working on another robot and works fine from a URCap (on the problem robot?), then perhaps the script has accidentally been changed?
