Restrictions

In CODESYS, it is possible that the execution of an IronPython script implies the execution of another, nested IronPython script. An example of this would be that a script is executed via the Execute Script command and the system.commands interface is used to call the command again with a different script. Likewise, this kind of script could call the command to create a CODESYS Test Manager script which itself contains scripting test actions. We call these scenarios "reentrant script execution".

Although these scenarios generally work, they are limited regarding the message memory and display. Each new script execution deletes all messages from the Scripting message category. In other words, only the messages from the deepest nested script execution are displayed until it is completed. This also applies if the script is executed with a console message logger (noUI).