Most errors can be detected in the INFO system in /Errors/Script. Each error is listed with description, the row and column number.
Some script errors can be more "tricky". For example the error can be of semantic origin instead of syntactic, i.e. the script is running, but not exactly the way it should be. The cause of such error can be found using the Pm.Debug method and e.g. "interval bisection". It means that somewhere in the application this method is placed into the script (together with the tuning remark as a first parameter). Then it is possible to check the script completion in the running application and see the "tuning remark" in the INFO systemu in Debug_info. This information can be useful in order to decide whether the error occured in the script before or after the remark.
A frequent error that occures when writing scripts for WEB is incorrect value assignment or reading graphic item properties. In order to read or write the properties correctly it is necessary to use the GetProp and SetProp method. Additional limitations are described in Web Panels chapter.
The Pm.Debug method works also in the web client and the report can be viewed after pressing Shift-Ctrl-Alt-space simultaneously.
Some errors cannot be prevented easily, because they can be, for example, dependant on operator input. For example if the operator enters 0 into a variable that is then used in script for division an error would be encountered. The application does not crash, but the script is terminated. This situation can be prevented by including the On Error command before the script expression that is prone to such errors. By this command it is ensured that the script continues even if the error occured.
Script errors often occur in the onStart event of the graphic item that reads or writes into another panel item based on this event. The cause of such error is the fact that the other item is not initialized at the moment of executing this event. This is the panel item order error that can be avoided by placing such item (that contains the script) above all others (i.e. select the item, right mouseclick and go to menu "Marked items / Move marked items by order in memory / above all items").
The special external tuning program (debugger) can also be used. The usage is described here: How to debug scripts in PROMOTIC application.
The global errors can be written into the "Application.ini" file. This kind of error log can be set in the "Application.ini" file in the [Log] section. The LOG file can then be explored long after the application is running or stopped. The error log is preset to record only the first occurrence of errors of each type.