debugging_complex_programs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
debugging_complex_programs [2018/12/26 10:53] – [First scan] emozolyak | debugging_complex_programs [2018/12/26 11:00] – [Differences between write function for internal registers and external] emozolyak | ||
---|---|---|---|
Line 37: | Line 37: | ||
If the order of execution of the scripts is 1 - 2, then everything will work, because at the current scan start script #2 saw one value, and before its execution another one(which script #1 has changed before), and will correctly work 'by changing the state of the register.' | If the order of execution of the scripts is 1 - 2, then everything will work, because at the current scan start script #2 saw one value, and before its execution another one(which script #1 has changed before), and will correctly work 'by changing the state of the register.' | ||
+ | |||
+ | ===== Running backup on the new device ===== | ||
+ | |||
+ | If you take the new WebHMI with clean internal DS - memory, where some complex project has to be run, usually you need some presets (initial values) for correct operation. You can use a recipe feature and make a list of all registers with initial values, and then just apply this recipe. | ||
+ | |||
+ | 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. | ||
debugging_complex_programs.txt · Last modified: 2022/01/15 20:50 by 127.0.0.1