5 Replies Latest reply on Apr 16, 2014 7:29 PM by Dan Fishman

    EMDVB Interface Configuration

    jamespr

      Hi guys!

       

      Mora than a question, this topic is a request. It is possible (or maybe it is already available) to create a video that demostrate the uses and configuration of the Template system in the PI EMDBV Interface throught the PI Event Frame Interface Manager? 

       

      Regards,

       

      James

        • Re: EMDVB Interface Configuration
          bbregenzer

          Hi, Jamespr.

          Have you taken a look at this video to see if it fills your needs?

          OSIsoft: How to Create PI EF Events, EF Attributes, and EF Templates (PI EFGen v3.0.0.x)

          https://www.youtube.com/watch?v=UbideDwhawg

          • Re: EMDVB Interface Configuration
            jamespr

            Hi! 

             

            Thanks for the recommendation. Unfortunately the video does not cover the PI EMDVB Template scheme.

            • Re: EMDVB Interface Configuration
              Dan Fishman

              James,

              Since we don't have a video I can attempt to give you a few points.  There is a lot of ground to cover on this :)

               

               

                   Attribute Templates: When the Batch Interface is configured to create Event Frames these become static values that are PI AF attributes of Event Frames with no data reference.  When using the PI Batch Database the property template defines the properties of  a PI Batch.  

              Tag Templates: In  general, tag templates allows for the storage of data in PI tags and should be used for time series information such as multiple values per Event Frame or the ability to trend data.  It makes sense to use a property if there is just one value to be stored per Event Frames using an Attribute/Property Template.

               

              Recipe Templates allow for customization of the Event Frame or PI Batch objects themselves.  For example, we can give the Event Frames or PI Batch objects a custom name, descriptor (AF only), Product (both Batch and AF) and more per the manual.  The index for recipe templates refer to the level in the recipe.  That means level 1 refers to the procedure level and two is the unit procedure level.

               

              In the PI Event Frames Interface Manager, for the triggers, note that each line will act as an or trigger.  I could provide you with a few lines from some sample .ini files I have on my machine if that would be helpful.  Also, you could paste a few lines from the manual into you .ini file, save the file and open the user interface and see what it looks like.

               

              Let us know if you have any specific questions.

               

              Dan

              • Re: EMDVB Interface Configuration
                jamespr

                Hi DFishman,

                 

                Thanks for the clarification. I would like to see the example that you mention. One of the challenges that we are like to address is copy the current anatomy of a report parameter on PI. Which is something similar to:

                 

                A:UnitTank(PhaseName):ParameterName-Report

                 

                Where, 

                A = Area

                UnitTank = Unit 

                PhaseName = DeltaV Phase Name

                ParameterName = DeltaV Parameter Name

                Report = Tag Keyword

                And very similar to the recipe parameters.

                 

                I know it is something that I can configure in the  PI EMDVB Template scheme but I dont really understand how to use the pleaceholder in order to achive the structure. 

                 

                Thanks in advance for your time!

                • Re: EMDVB Interface Configuration
                  Dan Fishman

                  Try this as a guide:

                   

                   
                  [TAG TEMPLATE]
                  TAG[1].NAME=PreFix:[UNIT].[PHASEMODULE].[EVENT].[DESCRIPT]
                  TAG[1].VALUE=[PVAL]
                  TAG[1].DESCRIPTOR=[PHASE].[EVENT]: [DESCRIPT]
                  TAG[1].TYPE=Float
                  TAG[1].UNITALIAS=Phases.[PHASEMODULE].[EVENT].[DESCRIPT]
                  TAG[1].PHASEALIAS=[EVENT].[DESCRIPT]
                  TAG[1].ENGUNITS=[EU]
                  TAG[1].TRIGGER=[EVENT,value="Report"]
                  TAG[1].TRIGGER=[EVENT,value="Recipe Value"]
                  TAG[2].NAME=PreFix:[UNIT].PIEvent.UnitBatch.BatchID
                  TAG[2].VALUE=[BATCHID]
                  TAG[2].DESCRIPTOR=UnitBatch Batch ID
                  TAG[2].TYPE=String
                  TAG[2].UNITALIAS=PIEvent.UnitBatch.BatchID
                  TAG[2].TRIGGER=[EVENT,value="PIEVENT"] [DESCRIPT, value="UNITBATCH"] [PVAL,value="START"]
                  TAG[3].NAME=PreFix:[UNIT].PIEvent.UnitBatch.BatchID
                  TAG[3].VALUE=Inactive
                  TAG[3].DESCRIPTOR=UnitBatch Batch ID
                  TAG[3].TYPE=String
                  TAG[3].UNITALIAS=PIEvent.UnitBatch.BatchID
                  TAG[3].TRIGGER=[EVENT,value="PIEVENT"] [DESCRIPT, value="UNITBATCH"] [PVAL,value="END"]
                   
                  [ATTRIBUTE TEMPLATE]
                  ATTRIBUTE[1].NAME=[DESCRIPT]
                  ATTRIBUTE[1].VALUE=[PVAL]
                  ATTRIBUTE[1].TYPE=String
                  ATTRIBUTE[1].DESCRIPTOR=[EVENT]: [DESCRIPT]
                  ATTRIBUTE[1].ENGUNITS=[EU]
                  ATTRIBUTE[1].TRIGGER=[EVENT, value="Recipe Data"]
                  ATTRIBUTE[2].NAME=[DESCRIPT] TIME
                  ATTRIBUTE[2].VALUE=[TIME]
                  ATTRIBUTE[2].TYPE=String
                  ATTRIBUTE[2].TRIGGER=[DESCRIPT, value="Procedure Started"] [EVENT, value="System Message"]
                  ATTRIBUTE[2].TRIGGER=[DESCRIPT, value="Procedure Finished"] [EVENT, value="System Message"]
                  ATTRIBUTE[3].NAME=[DESCRIPT] TIME
                  ATTRIBUTE[3].VALUE=[TIME]
                  ATTRIBUTE[3].TYPE=String
                  ATTRIBUTE[3].TRIGGER=[DESCRIPT, value="ACTUAL_CHARGE"] [EVENT, value="Report"] [PHASEMODULE, value="CHG_COLOR"]
                  ATTRIBUTE[4].NAME=[DESCRIPT]
                  ATTRIBUTE[4].VALUE=[PVAL] (Time: [TIME]) (User: [USERID])
                  ATTRIBUTE[4].TYPE=String
                  ATTRIBUTE[4].DESCRIPTOR=Prompt Response Info
                  ATTRIBUTE[4].TRIGGER=[EVENT, value="Prompt Response"]
                  ATTRIBUTE[5].NAME=Parsed [DESCRIPT]
                  ATTRIBUTE[5].VALUE=[PVAL] (Time: [TIME]) (User: [USERID, lbe="OperatorName: "])
                  ATTRIBUTE[5].TYPE=String
                  ATTRIBUTE[5].DESCRIPTOR=Prompt Response Info
                  ATTRIBUTE[5].TRIGGER=[EVENT, value="Prompt Response"]
                  2 of 2 people found this helpful