debugging_complex_programs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
debugging_complex_programs [2018/12/26 11:12] – [Running backup on the new device] emozolyak | debugging_complex_programs [2021/08/02 11:01] – [Step over trick] emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
====== Debugging complex scripts ====== | ====== Debugging complex scripts ====== | ||
===== Project initialization ===== | ===== Project initialization ===== | ||
+ | |||
+ | |||
==== Non - volatile registers ==== | ==== Non - volatile registers ==== | ||
Line 29: | Line 33: | ||
Remember that registers such as Dxx, CDxx and other internal registers, except for DSxx, return to the initial state (usually 0) after initializing the project (which happens when editing project elements - scripts, registers, connections, | Remember that registers such as Dxx, CDxx and other internal registers, except for DSxx, return to the initial state (usually 0) after initializing the project (which happens when editing project elements - scripts, registers, connections, | ||
- | ===== Differences between write function for internal | + | ===== Differences between write function for internal/external |
There are some differences in the operation of the SetReg and WriteReg functions with respect to internal registers (Dxx, DSxx). These functions directly change the values of the internal registers inside the scan, and do not delay WriteReg writing to the next scan start. Thus, at the end of the scan, the internal register can have a value different from the one at the scan input. Then, for example, a situation is possible where: | There are some differences in the operation of the SetReg and WriteReg functions with respect to internal registers (Dxx, DSxx). These functions directly change the values of the internal registers inside the scan, and do not delay WriteReg writing to the next scan start. Thus, at the end of the scan, the internal register can have a value different from the one at the scan input. Then, for example, a situation is possible where: | ||
Line 46: | Line 50: | ||
===== Debug messages ===== | ===== 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' | + | 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' |
+ | |||
+ | When there is a lot of records in the communication log, you can filter out unneccerary output from scripts with this [[http:// | ||
+ | |||
+ | 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 " | ||
+ | |||
+ | There are also messaging functions like [[ http:// | ||
+ | |||
+ | ===== Modular principle ===== | ||
+ | |||
+ | It is recommended that you split complex scripts into simpler and more frequently used functions that you can reuse. Dividing tme into simpler parts, arranging them in the right order and grouping helps to control the logic of the system and makes it easier to set up the system. | ||
+ | |||
+ | ===== Proper commenting ===== | ||
+ | Use commenting you will understand next time you or someone will see you code. | ||
+ | <code lua> | ||
+ | ----------------------------------------CALC. DAY ECONOMY -------------------------------------------------- | ||
+ | LimitMonthDayYesterday = GetReg(" | ||
+ | HeatEnergyDay = GetReg(" | ||
+ | WriteReg(" | ||
+ | ------------------------------------------------------------------------------------------------------------ | ||
+ | </ | ||
+ | |||
+ | ===== Step over trick ===== | ||
- | When there is a lot of records | + | When you need to run once your script and inspect its result |
+ | *make extra bit register, like "Debug step over bit" | ||
+ | *change run mode of the script being debugged - execute upon the register' | ||
- | 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. | + | {{ :: |
- | However, in a large system with many interrelated scripts, when there is a lot of debugging data, it becomes inconvenient to look for the necessary data, especially if you need to track a specific chain of execution of several scripts that can not be called at specific moments, not in each scan. | ||
- | In addition, filtering unnecessary information in logs is also useful from the point of view of performance, | ||
- | You can proceed as follows - assign your debugging function, which will be called only if the debug printing of this script is allowed. For example, you can write the ids of the scripts in the ' | ||
debugging_complex_programs.txt · Last modified: 2022/01/15 20:50 by 127.0.0.1