# Installation variables

**URL:** <https://forum.universal-robots.com/t/installation-variables/18275>\
**Category:** Report a Bug\
**Created:** [December 20, 2021, 2:18pm UTC](https://forum.universal-robots.com/t/installation-variables/18275 "2021-12-20T14:18:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![he1](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@he1](https://forum.universal-robots.com/u/he1)\
**Post date:** [December 20, 2021, 2:18pm UTC](https://forum.universal-robots.com/t/installation-variables/18275/1 "2021-12-20T14:18:45Z")

</div>

Polyscope version 3.13.1.10297

When I copy a saved default.installation and default.variables to the simulator and load the installation the variables are blanked.

Is this expected? How can I load installation variables from a \*.variables file?

---

<div class="post-metadata">

**Author:** ![he1](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@he1](https://forum.universal-robots.com/u/he1)\
**Post date:** [December 20, 2021, 2:25pm UTC](https://forum.universal-robots.com/t/installation-variables/18275/2 "2021-12-20T14:25:32Z")

</div>

It seems that the problem was that I had the simulator running and tried to overwrite the default installation. This did not work.

when I shuted down the simulator, transferred files and started the simulator again the variables were populated as expected.

But how to do this on a live robot ? How can I kill the polyscope java application and keep it from restarting while I transfer the new default installation?

---

<div class="post-metadata">

**Author:** ![bba](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/bba/32/555_2.png) [@bba](https://forum.universal-robots.com/u/bba)\
**Post date:** [December 21, 2021, 7:13pm UTC](https://forum.universal-robots.com/t/installation-variables/18275/3 "2021-12-21T19:13:12Z")

</div>

When you initially copy the installation/variables files rename then to something unique like default1.installation and default1.variables (using SaveAs). Then, after the copy into URsim, open default1.installation and do a saveas on the target URsim instance to ‘default’ installation.
