5 Replies Latest reply on Oct 12, 2016 3:42 PM by gregor

    "CurrentTime" tag

    Akhil

      Hello Everyone,

       

      I have created a "currentTime" tag in the primary of the collective, the tag was created on secondary as well(as expected) but now the tag is getting updated only on Secondary server and is stale on the primary, all the others tags seem to be working fine.

      Any suggestions to resolve the issue?

       

      Thanks,

      Akhil

        • Re: "CurrentTime" tag
          dwang

          Hello Akhil,

           

          What is the data source (or data generating application) of this currentTime tag?

          Depending on where the data source is (which machine) and what application is used to generate the data different methods are required to ensure that its data is sent through to both PI Data Archive collective members.

           

          For example if you are using Asset Analytics or any PI Application that support for pibufss then the n-way buffer mechanism can be used to fan the data to both members.

          If you are using PI Performance equation Scheduler then another instance on the primary PI Data Archive will be required to have the data be updating on both Collective members as PI PE is tied to the PI Data Archive instance which its service is running on.  

            • Re: "CurrentTime" tag
              Akhil

              Hello David,

               

              Thanks for your response!

              I have created a simple PE tag where I specified the Ex Desc attribute to '*' and set the Point source to 'C'.

              This tag now seems to be showing correct value(current time) in the Secondary server but the tag in primary server shows "Point Created" value.

              We already have the PI PE scheduler service running on both primary and secondary servers.

              Appreciate your help.

               

              Thanks,

              Akhil

                • Re: "CurrentTime" tag
                  dwang

                  Hello Akhil,

                   

                  Thanks for the update.

                  Can you check the remainder of the PI Tag configuration for this PE Tag and make sure that it matches with the PE interface configurations on your primary. So PI Tag point source matches PE scheduler Point source, Location 1 for the PI Tag matches with the PE interface ID, PI Tag location 4 matches with a valid scan class on the PE interface (if it is periodic scan).  

                  Are the PE scheduler configurations different on the primary and secondary? Please check by identifying what is different on the primary PI Data Archive Performance Equation interface and then make the update to it. Restart the Performance Equation interface to have the change be accepted.

                  On a PI Data Archive the PE configuration file is located in <installation drive letter>\%piserver%\BIN default: pipeschd.bat

                  You can load the Performance equation interface (its .bat file) into the interface configuration utility (ICU) to check the PE interface configurations otherwise read the configuration .bat file in an text editor.

                   

                  Hope this helps to assist in getting your value to update on both Collective nodes.