Hello everyone,
wenn I open a URScript file then there is normally a lot of setup code above.
Does anyone know where the installation file of the robot is set or imported?
Thanks for any help!
Best regards,
Tobias
Hello everyone,
wenn I open a URScript file then there is normally a lot of setup code above.
Does anyone know where the installation file of the robot is set or imported?
Thanks for any help!
Best regards,
Tobias
Can you post a file as an example?
A lot of setup code comes from URCaps.
Are you talking about script files (.script) or .URP files?
The default.installation and default.variables files are located in the same folder as your program files (unless you’ve created other folders for them), which is the “home” folder to Polyscope. It’s actually the \programs folder when viewed with a utility such as WinSCP.
If you set your file filter to All Files you can see them:
Here I have my primary programs in the home folder, with several subfolders for less frequently used test and utility programs:
If you want to look at the installation or variables files, they are stored in .zip format - pull them onto a thumb drive, then open them in something like 7-Zip File Manager to decode so that they can be viewed in Notepad. You could probably edit them, but that seems pretty dangerous to me.
Hello everyone,
thank you for the responses.
Unfortunately I am looking for something else.
I got the C207A0 error when connecting the robot via Python with the urx library.
My theory is that there is maybe a differend installation file use.
But I don’t know how to figure that out.
Best regards,
Tobias
When polyscope initially boots up it always loads default.installation. This is how the controller knows that it has some payload, IO is configured, etc. If you don’t load anything else this is the context within which your external python code will run. You can change these settings in the default.installation to make the startup environment more friendly to your external app.
Thank you very much.
Sorry for my late response.
The error was that the time between to execution steps was to short in the python script.
It works now with some wait operators.