on-demand_registers
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
on-demand_registers [2018/11/26 13:06] – created emozolyak | on-demand_registers [2018/11/26 14:25] – emozolyak | ||
---|---|---|---|
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. | ||
- | E.g. temperature requlator may have only 2-3 process related data ( current temperature, | + | E.g. temperature requlator may have only 2-3 process related data ( current temperature, |
- | So when you add many such controlles | + | So when you add many such controllers |
+ | |||
+ | 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 ' | ||
+ | viewed via Analytics / Raw values menu. | ||
+ | |||
+ | | ||
- | To avoid this situation, there a special attribute for the registers which marks them as "Read on-demand" |
on-demand_registers.txt · Last modified: 2022/01/15 08:12 by 127.0.0.1