Differences

This shows you the differences between two versions of the page.

--- debugging_complex_programs [2018/12/26 11:00] – [Differences between write function for internal registers and external] emozolyak
+++ debugging_complex_programs [2018/12/26 11:21] – [Debug messages] emozolyak
@@ Line 43: / Line 43: @@
 If the project was linked to Level2 account, when restoring its backup on the new WebHMI, check that Level2 integration is switched off, otherwise this WebHMI may interefer another one which use same Level2 account.
+===== Debug messages =====
+It is desirable after the key moments of logic or calculations in scripts to immediately put the functions INFO, ERROR, DEBUG, TRACE, with respectve values at this point, script's name, line number at the beginning, etc. Then these fragments are conveniently searched and analyzed in the communication log.
+When there is a lot of records in the communication log, you can filter out unneccerary output from scripts with this [[http://docs.webhmi.com.ua/useful_programs#debug_printing|method]].
+In the script editor, there is a debugging console, which always prints out the functions INFO, DEBUG, ERROR, TRACE regardless of the system log level settings. If the output changes too quickly to analize, you can slow down the script by changging in execution type to "Execute on register's value change" and link to system time register or another one, slower.
+There are also messaging functins like [[ http://docs.webhmi.com.ua/scripts#writing_to_message_log|AddInfoMessage]], which can be used to write in a separate Messages log. Just take care of using them in logic transition points, otherwise you will get huge number of records generated in every scan from these functions.