Script Instances lost after reboot of ctrlX CORE

[maurusbien]

Hello everyone,

once I have created an script instances (like shown in this example here: https://developer.community.boschrexroth.com/t5/ctrlX-CORE/How-to-run-Python-scripts-on-the-ctrlX-CO...) it is not existing anymore when i reboot my ctrlX CORE (virtual). Should it be like this? Is there a possibility to save the created script instances permanetly?

Thanks!

[Jochen_Mueller · Accepted solution]

The current situation (RM20.11): After reboot the instances vanish. (like descripted)

If you see the necessarity to change this behauvior please contact me directly. So we can discuss it.

[drschiffler]

Hi,

you can use the "init script" functionallity.

1. Download and unzip the configuration via the web interface
2. Write a python script 'init.py' with content eg. 'print("Hello ctrlX")' and save it in the configuration in the directory "script" (any other dir/filename would also work)
3. Zip the configuration directory (now includes the init.py file) and upload it to the core via web ui
4. Write on the datalyer node "script/cfg/init-script" the payload "{"file": "activeConfiguration/script/init.py","language": "python","parameter": []}" (can be done also via web ui)
5. Reboot
6. Now there is always a python instance called "Base" (prerequisite is the python runtime snap)
7. POST the following payload on "script/instances/Base/cmd/file" to excecute any script you need (via web ui or REST API). Payload eg. '{"name":"activeConfiguration/script/myworker.py","param":[]}'

Notes:

Link to documentation

It seems in the docu linked above is a mistake according to the path for the init script see: activeConfiguration vs. activeSolution