Hello All,
Our organization users many totalizers in Pi, however, there is a group of them (daily and shift totalizers) that are randomly resetting to zero and after different amounts of time they will return back to their previous total.
Both totalizers have a source tag which has a normal level of 0 and at the end of the process goes up to ~5000 for 1 minutes.
The daily totalizer is configured as:
Totalizer Type
Count Events
Events where value changes
Block - change from less than to greater than or equal to = 1
Sampling
Whenever a new source tag event occurs (Natural)
Results
Write final results - After a time period elapses
Start schedule at: 0 Hour(s) after midnight
Results every: 24 Hour(s)
Vary w/DST
Write interim results - At source time (ramp)
Archive
Typical value: 50
Zero: 0
Span: 1000
Scan: On
Archiving: On
Step: On
Shutdown: Off
Compressing: Off
Exception Deviation: 0 Eng Units
Min Time: 0 Days. 0 Hours. 0 Minutes, 0 Seconds
Max Time: 0 Days. 12 Hours. 0 Minutes, 0 Seconds
Compression Deviation: Disabled
Options
Use negative source values: unchecked
Source tag is a DCS integrator: unchecked
Source OverRange is ZERO + SPAN: Unchecked
Use Source Tag BAD in place of "Bad Total": Unchecked
Source UnderRange is: No Selection
Conversion Factor: 1
Source = Zero below: 0
Pct good values needed: 0 (was 85 but changed to 0 based on another post I saw. No change in results).
Summary
Totalizer Point Attributes for: PROD_CNT_DAILY
Descriptor: Daily Total Production Count
archiving = 1
calcmode = CHANGEEVENTS
compdev = 1
compmax = 3600
compmin = 0
compressing = 0
compvalue = 1
conversion = 1
datasecurity = piadmin: A(r,w) | piusers: A® | PIWorld: A®
descriptor = Daily Total Production Count
engunits =
eventexpr =
excdev = 0
excmax = 43200
excmin = 0
filterexpr =
function = EVENTLT_GE
movingcount = 2
offset = +0H
offset2 = +0M
options =
pctgood = 0
period = +24H
period2 = +2M
ptsecurity = piadmin: A(r,w) | piadmins: A(r,w) | PIWorld: A®
ratesamplemode = NATURAL
reportmode = RAMPING
scan = 1
shutdown = 0
sourcetag = EVAC_FLOW
span = 1000
step = 1
tag = PROD_CNT_DAILY
totalclosemode = CLOCK
typicalvalue = 50
zero = 0
zerobias = 0
The shift totalizer (12 hours shifts running from 7-7) is configured as:
Totalizer Type
Count Events
Events where value changes
Block - change from less than to greater than or equal to = 1
Sampling
Whenever a new source tag event occurs (Natural)
Results
Write final results - After a time period elapses
Start schedule at: 7 Hour(s) after midnight
Results every: 12 Hour(s)
Vary w/DST
Write interim results - At source time (ramp)
Archive
Typical value: 50
Zero: 0
Span: 1000
Scan: On
Archiving: On
Step: On
Shutdown: Off
Compressing: Off
Exception Deviation: 0 Eng Units
Min Time: 0 Days. 0 Hours. 0 Minutes, 0 Seconds
Max Time: 0 Days. 12 Hours. 0 Minutes, 0 Seconds
Compression Deviation: Disabled
Options
Use negative source values: unchecked
Source tag is a DCS integrator: unchecked
Source OverRange is ZERO + SPAN: Unchecked
Use Source Tag BAD in place of "Bad Total": Unchecked
Source UnderRange is: No Selection
Conversion Factor: 1
Source = Zero below: 0
Pct good values needed: 0 (was 85 but changed to 0 based on another post I saw. No change in results).
Summary
Totalizer Point Attributes for: PROD_CNT_SHIFT
Descriptor: Shift Total Production Count
archiving = 1
calcmode = CHANGEEVENTS
compdev = 1
compmax = 3600
compmin = 0
compressing = 0
compvalue = 1
conversion = 1
datasecurity = piadmin: A(r,w) | piusers: A® | PIWorld: A®
descriptor = Shift Total Production Count
engunits =
eventexpr =
excdev = 0
excmax = 43200
excmin = 0
filterexpr =
function = EVENTLT_GE
movingcount = 2
offset = +7H
offset2 = +0M
options =
pctgood = 0
period = +12H
period2 = +2M
ptsecurity = piadmin: A(r,w) | piadmins: A(r,w) | PIWorld: A®
ratesamplemode = NATURAL
reportmode = RAMPING
scan = 1
shutdown = 0
sourcetag = EVAC_FLOW
span = 1000
step = 1
tag = PROD_CNT_SHIFT
totalclosemode = CLOCK
typicalvalue = 50
zero = 0
I do not have any bad values logged in the archive edit, only 0s when it drops.
Below is a screen capture of the graph of the 3 points.
Yellow = Shift Count
Blue = Daily Count
Green = End Of Cycle Evacuation Flow
This is a 4 hour time span. The start of shift (7am) is on the left and the yellow line can be seen resetting to 0 to start a new shift. I have also noticed that sometimes these totalizers are not resetting to 0 at midnight (daily) or 7 am/pm (shift). This is rare but out of 100 sets of these tags, this is observed on at least 5 daily (not the same everyday).
I have been reading every post I can over the past few weeks to try and figure this out but I cannot find anyone having a similar issue.
I hope this is something silly I am missing.
Thanks in advance,
Phi