on-demand_registers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| on-demand_registers [2018/11/26 14:23] – emozolyak | on-demand_registers [2018/11/26 21:25] – akuzmuk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Read-on demand registers ====== | + | ====== Read on demand registers ====== |
| Each remote device, connected to WebHMI always has some settings or setup data which does not have to be read in each WebHMI scan. They are actually accessed by operator only during commisioning or installation. | Each remote device, connected to WebHMI always has some settings or setup data which does not have to be read in each WebHMI scan. They are actually accessed by operator only during commisioning or installation. | ||
| Line 7: | Line 7: | ||
| So when you add many such controllers with all registers to the WebHMI project, it will communicate 90% of time in vain, and only 10% to read important data. | So when you add many such controllers with all registers to the WebHMI project, it will communicate 90% of time in vain, and only 10% to read important data. | ||
| - | To avoid this situation, there is a special attribute for the registers which marks them as "Read on-demand" | + | To avoid this situation, there is a special attribute for the registers which marks them as "Read on-demand" |
| Tip: Group all read-on demand registers in one or two ' | Tip: Group all read-on demand registers in one or two ' | ||
on-demand_registers.txt · Last modified: 2022/01/15 08:12 by 127.0.0.1