Script instance creation issue

[8run0tti]

Dear ctrlX Community!

We tried to create a new script instance on datalayer, but we experienced the following error:

Anyway the script instance is created successfully, but the PLC starts flashing red.
The method of creation does not matter , the result is similar. (we tried the manual creation in datalayer menu and creation by IL_CreateScriptInstance in PLC program and creation in IDE)
The system image version is 1.20.4.

Could You recommend a solution to this problem?

Thanks in advance!

[CodeShepherd]

Please keep in mind that is always two steps. First create instance, 2nd execute script in that instance.

The mentioned error will always occur when the script running (step 2) in an instance will have programming errors or is not exited properly (see this topic).

Could you share your script you are trying to run?

[8run0tti]

Hi CodeShepherd!

Fortunately, we didn't experience any problems running a scripts on an existing script instance.

The mentioned error appears when we create a new script instance.

[CodeShepherd]

We now could reproduce this behaviour when no ctrlX CORE - Motion app is installed and track it as a bug. The error has no effect to your running system/application.

Thanks for mentioning we will improve this.

[8run0tti]

Unfortunately we experienced the same issue on newest (02.02.4) system image.
Do You have any news from the development team?

Thanks in advance!

[CodeShepherd]

As the behaviour is like intended there were no changes made.

As uncontrolled running axis are a risk for machines and workers when you kill a script all motion objects connected to a script will be stopped on purpose. This is done via creating the error. You will need to use function "exit(0)" or detach the motion objects by hand (in the code) before ending the script.

[8run0tti]

As I mentioned in the first post, this error happends, when we create a new script instance. In this case, the script is not running yet, so what you suggested is not effective.

You can simply reproduce this phenomenon by clicking 'Create' in the script/instances node in the Data Layer menu on WebUI. This only happens, when the Motion app is not installed on the Core.

[CodeShepherd · Accepted solution]

Sorry for misunderstanding. I can confirm the behaviour mentioned and it will be fixed in version 2.04 of the automationcore app.