Totalizer End of period Issues

Discussion created by mikeloria on Mar 15, 2011
Latest reply on Mar 17, 2011 by mikeloria

I came accross an issue with using the PI Totalizer. I have several totalizers for an operator screen to show totals and statistics over an 8 hour period. At the end of 8 hours, I need the values to zero out and start over. The totalizers are event driven and run when a new value for a particular point is has a new snapshot value. The issue is that at the end of the period, the totalizer does not zero out until a new value for the event driven point exists. This means that in real-time, the operator sees the toalized values zeroing out at different times and there is no way to tell if the values are from the current shift or the previous shift.


I have brought this to the attention of tech support and they have confirmed this to be the case. They have also reccomended that I go to PEs. I would rather use the totalizers because they have many features over the PEs such as using the snapshot and not the archive. Is there any suggestions to this issue where I can still use the totalizers? I am afraid that if I set the totalizer to period, I will lose events since some of the events are 1 second and less.


Here was the tech support response:


Under TotalCloseMOde clock of the pi applications manual (page 223), the
manual states:

In this example, although the accumulation ends, the actual close of the
accumulation does not occur until the rate point updates. This event can
occur well after the end of the accumulation interval. When the update
event occurs, the calculated result is written to the Archive with
timestamps of the actual totalization interval.

I would recommend using a Performance equation to perform your totals.
You syntax would be along the lines:

if hour('*') <7 then eventcount('sinusoid','t', 't+8h') else if ....


Thak you very much for your help in this matter