Hi, we are working with a UR20 and sending script commands over the Primary Interface over port 30001 to the UR20 simulator for testing purposes. The communication works, because if we send a popup, it is becomes visible in the simulator. However, when trying to update a global variable, the variable is not updated in the simulator installation variables list (also after a restart, the new value is not populated). Note that the variable already exists in the installation variables list in the simulator with the same data type. Any suggestions/explanations?
Can you explain a little more about that? You just put that line in your script that you send and that let you access installation variables over the Primary Interface?
Ah, sneaky Just don’t mark this post as a solution.
So the reason why it was forbidden is that we had few issues of “corrupted” installation variables in customer programs. This was considered mild safety risk as those variables are often used to configure motions.
Corruption was due to programs sent by some URCaps that accidentally had the same variable names as main customer program.
Just don’t mark this post as a solution.