Script Window

In the script window, scripts and CTRL libraries can be debugged. You can set Breakpoints and execute scripts (see figure below). The buttons of the debugger are described here Buttons.

Figure 1. A red circle indicates a set breakpoint

Figure 2. An arrow symbol shows the code that is executed

You can use the search window to search for scripts, libraries, variables and breakpoints. The search is case insensitive! Without wildcards, for example, "settings" is part of a word and all words containing "settings" are found. With bsettings* = all words that begin with "bsettings" are found.

Note: Note that you need to refresh the table to see the script of a panel or library if you want to debug the script.

Note: If you create an evalScript(). Normally you cannot debug the code lines of the evalScript. However, if you set a breakpoint in the library used in the evalScript, you can debug the library and therefore also the evalScript normally.

Note: With the Start Manager for Debugging and break new Threads option in the WinCC OA console the debugger stops on the first line. It waits and when you press a second time, the debugger is started. If a manager has not yet been started and you press the button, the manager does not yet execute, but waits until you start the CTRL debugger and click Continue.

For Debugging of init scripts:

Break new thread: With the Break new thread the debugger stops on the first line. It waits and when you press a second time, the debugger is started. If a manager has not yet been started and you press the button, the manager does not yet execute, but waits until you start the CTRL debugger and click Continue. The option Start Manager for Debugging and break new Threads option in the WinCC OA console is the same as Break new thread.

Debug Break Stop Thread: Stops the execution of the code since DebugBreak() is set in the code. You have to set DebugBreak() explicitly in the code if you want to use it.

Break Thread on Error: Break Thread on error stops the execution of the code when an error occurs. It stops at the error.

Also Remote UI can be debugged.