Quantcast
Channel: OSIsoft Users Community
Viewing all articles
Browse latest Browse all 1120

Totalizers - View Interim Results While Totalizing

$
0
0

Hello everyone

 

First off, I'm pretty new to PI.

 

I have a typical application involving Totalizers to generate equipment runtime hours based on a Digital tag being in the Active state.

But, it's a bit more complicated and involves an external database that reads the runtimes and then clears them via PI OLEDB - still pretty typical in my mind.

 

Here's my testing totalizer config:

Totalizer Point Attributes for: RunTime1
Descriptor: 
 
archiving = 0
calcmode = TIMETRUE
compdev = 0
compmax = 28800
compmin = 0
compressing = 0
compvalue = Active
conversion = 1
datasecurity = piadmin: A(r,w) | FTHEngineers: A(r,w) | PIWorld: A®
descriptor = 
engunits = 
eventexpr = 
excdev = 0
excmax = 600
excmin = 0
filterexpr = 
function = EVENTEQ
movingcount = 1
offset = +0H
offset2 = +0M
options = SETABLE 
pctgood = 85
period = +1H
period2 = +2M
ptsecurity = piadmin: A(r,w) | FTHEngineers: A(r,w) | PIWorld: A®
ratesamplemode = NATURAL
reportmode = RAMPING
scan = 1
shutdown = 0
sourcetag = TestBit
span = 100
step = 0
tag = RunTime1
totalclosemode = FOREVER
typicalvalue = 0
zero = 0
zerobias = 0

 

The problem with this is my clients equipment will run for weeks at a time, and the runtimes "hang" until the equipment turns off. The client wants to be able to check the values in real time (see them update in SMT Current Values every minute or so) to make sure they configured the totalizer and source tag correctly.

Another problem with this, the external database will read and clear the values, and days/weeks of totalization could be lost.

 

Is there a way to read the totalized tag while it is running? I was under the impression "interim" results would write successively to archive, but they only do once the source tag is inactive. I've tried scheduled sampling rather than natural, but no go.

 

I've made an alternate solution using PEs:

TimeEq('TestBit','*-1m','*',"Active") + TagVal('RunTimePE')

Where 'RunTimePE' is the point name of the performance equation and then I add the PE to the 1 minute schedule

 

But this seems like something the Totalizer should be able to do and I've heard PEs can bog down the PI system - my client will have 25k or so runtimes to monitor.

In my mind, I should be able to see interim results during the interim - hence the name.

 

Am I missing something?

 

Thanks!

Chad


Viewing all articles
Browse latest Browse all 1120

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>