Copy configuration files from robot to simulation

We have a UR10 at one of our costumer’s locations that is net gapped.

I wanted to make some changes to the program running on the cobot, but I’m having trouble copying the configuration files from the cobot to URSim. Every time I try to do that and restart the simulation, I get an error message titled “Installation loading”, with the error “Not an installation file”.
The configuration files etc. were copied from the cobot’s pendant using the urmagic_configuration_files.

Is there any way in which I can copy the configuration from our remote and unaccessable cobot to the simulation?

Thanks,
Uri

Configuration files =/= Installation files. :slight_smile:

The configuration files you’re retrieving are the calibration files for that robot. Those cannot/should not be used on other robots, and neither in the sim.
The installation file you’re looking for is retrieved along with the programs with the urmagic backup programs and is named “xxxxx.installation”. :slight_smile:

Hi, Thanks for the correction.

I tried copying the “default.installation” file I got from the robot using the urmagic_backup_programs.sh file, but still got the same result - I’m still getting an error + "Not an installation file” message.

Is there another way of doing this?

You can access the robot’s internal storage by ftp. Should be possible, if you’ve got network access.

But I don’t believe that will solve your issue. If you’re running the same PolyScope in URSim as the physical robot, and you’re not able to open an installation file, I’d believe something else is wrong. Maybe do a fresh install of URSim.

Does the PolyScope version matter? I am not sure they match, between the actual robot and the URSim.
In case the version does matter, can I change the PolyScope version on the simulation?

I’m not entirely sure, but you might get issues if going from a very low version to the newest version. Only thing I know is that you will have issues loading installations files from e-series to CB-series.

You can just install another virtual machine with the correct version.