Using Totalizer tag and a digital source tag with mode of "running" and stop. How can I create a Totlaizer tag accumulating the motors run time with no reset?
In order to have the Totalizer tag not reset, choose the radio button corresponding to "Continue forever (interim results ONLY)" under the "Results" tab in the "Totalizers" plugin in SMT. In order for this option to be available, the "Totalizer Type" must be set to "Summary Calculation" with "Moving" instead of "Block". That setting is on the "Name & Type" tab.
You can use a PE to get the individual run times by using the TimEq(tag,starttime,endtime,value) PE to determine how long the digital tag had a value of Running within a certain period. Something like the following should give you what you are looking for:
To get the full run time, you can use the PE above as the target for the totalizer tag.
Please let me know if this helped out.
I just wanted to add to Harry's suggestion:
If you would like to skip the intermediate PE, you can set up your totalizer to total "Time when TRUE" for "equal to RUNNING." It would look like this if you build the totalizer in the PI SMT Totalizers plugin:
I notice that Melinda did not check Summary of Calculation as mentioned by Paul. Even though I choose Count Events it still allowed me to choose continue forever. What is the difference between the two.
Second I wnat to use this to balance out run time between two pumps/motors. I think that hours should suffice for units. Would this be set by changing the conversion field to 3600? Thanks for quick responses
Block refers to a discrete time period to be evaluated versus a Moving calculation such as a moving average which has a dynamic time period for its calculations. The important thing is having Moving selected instead of block. I instructed to pick "Summary Calculation" because I wanted to be very specific with my instructions, but I had not looked at the "Count Events" options which Melinda suggested. "Count Events" is a better choice as it eliminates the PE.
The "Time when TRUE" will return seconds, so you would need to divide by 3600 to get hours back. Unfortunately, the conversion factor is ignored for totalizers when "Event Count" is selected. There is a work item in place to allow the conversion factor to be used with these types in the future. If you want to convert the results from seconds to hours, you will need to use "Summary Calculation" and the PE I suggested earlier, or just apply the scaling factor to the Event Count Totalizer with a PE.
I created the totalizer point and used PE to do the conversio to hours. Thanks to both.
After further review, the documentation (PI Server Applications User Guide) indicates that the "Time when TRUE" (CalcMode=TimeTrue) is technically not a "counting-type" totalizer even though it is grouped with them in the UI. The conversion factor will actually work since it does not fall under this PLI. Furthermore, I tested to verify and the conversion factor does work, so you can continue with your current setting or implement the conversion factor. I apologize for the confusion.
I created the totalizer yesterday, but it has not updated since then. I have also added a conversion factor of .000277778.
From my understanding I should not need the PE tag
Thanks for your help.
9/6/2013 8:00 RUNNING GT-21 MAIN LUBE OIL PUMP #1
9/6/2013 8:08 4.844 HRS GT -21 #1 LO PUMP RUN TIME CALCULATED BY TOTALIZER / 36009/5/2013 12:00 17,438 GT-21 #1 LUBE OIL PUMP RUN-TIME IN HOURS
Totalizer Point Attributes for: 21MBV11AP101_TOT
Descriptor: GT-21 #1 LUBE OIL PUMP RUN-TIME IN HOURS
archiving = 1
calcmode = TIMETRUE
compdev = 2
compmax = 28800
compmin = 0
compressing = 1
compvalue = RUNNING
conversion = .000277778
dataaccess = o:rw g:r w:r
datagroup = piadmin
dataowner = piadmin
descriptor = GT-21 #1 LUBE OIL PUMP RUN-TIME IN HOURS
excdev = 1
excmax = 600
excmin = 0
function = EVENTEQ
movingcount = 1
offset = +0H
offset2 = +0M
pctgood = 85
period = +1H
period2 = +2M
ptaccess = o:rw g:r w:r
ptgroup = piadmin
ptowner = piadmin
ratesamplemode = NATURAL
reportmode = RAMPING
scan = 1
shutdown = 0
sourcetag = 21MBV11AP101.XG01
span = 100
step = 0
tag = 21MBV11AP101_TOT
totalclosemode = FOREVER
typicalvalue = 50
zero = 0
zerobias = 0
This is a naturally scheduled Totalizer, so it will only update when the tag it is triggering off of is updated. Has the tag 21MBV11AP101.XG01 updated since then? If the tag 21MBV11AP101.XG01 rarely changes state, then you may want to use periodic scheduling instead, which is set up on the "Sampling" tab.
What I am looking to do is be able to monitor run time hours on a pump so that we can decide when to switch pumps over. There must be a vaiety of ways to do this. E.g. subtract current time from time when started. Or create counter while it is running. Using the periodically settings does the counter go to zero every 24 hrs.
No, the counter will never be reset when the "Continue forever (interim results ONLY)" option is checked under "Results". Periodic scheduling will affect when interim results are posted.
Totalizers can be a bit complicated to configure given all the settings and subtleties. For detailed information, I would recommend downloading the PI Server Applications User Guide. Chapter 7 is entirely dedicated to the PI Totalizer Subsystem. The chapter outlines principles of operation and defines all aspects of the point configuration.
Retrieving data ...