Differences

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

--- on-demand_registers [2018/11/26 13:14] – 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.
-E.g. temperature requlator may have only 2-3 process related data ( current temperature, setpoint, control output value), but tens of even hundreds of setting registers, like sensor types, calibation data, control profile ( ON-OFF, PWN, analog control, PID coeficients, hysteresys)  etc.
+E.g. temperature requlator may have only 2-3 process related data ( current temperature, setpoint, control output value), but __tens of even hundreds__ of setting registers, like sensor types, calibation data, control profile ( ON-OFF, PWM setup, analog control setup, PID coeficients, hysteresys)  etc.
 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" so that WebHMI skips them when polling external devices.
+To avoid this situation, there is a special attribute for the registers which marks them as "Read on-demand" so that WebHMI skips them when polling external devices thus minimizing scan time.
   Tip: Group all read-on demand registers in one or two 'settings' category then they can be easily accessed and
   viewed via Analytics / Raw values menu.
+ {{::readondemandvideo.gif?direct}}