4 Replies Latest reply on Aug 5, 2016 8:08 PM by aljovinj

    downtime event frame every date changed

    aljovinj

      Hello, the event frame template downtime works, but when the downtime lasting more than 24 hours, in PSE you can see that the downtime still running, it is good because you know how long the downtime occurs, but when you try to make an analytics about this process or machine you can have more than a month only in one record or maybe it is not countable, My questions is the event frame could report a record for every single day.

       

      I tried to do this using .net and PI AF SDK using this sentence

       

              Dim list As AFNamedCollectionList(Of AFEventFrame) = AFEventFrame.FindEventFrames(lo_Database, Nothing, "*-3d", 1, 100, AFEventFrameSearchMode.None, "*", lo_Reference, Nothing, Nothing, True)

       

      But  even changed the start time, search mode, max count, I couldn't cath this downtime

      Downtimes 2016-02-29 08:15:05.349 --->158:3:27:01.251     29/02/2016 08:15:05.349 a.m.

        • Re: downtime event frame every date changed
          Dan Fishman

          Yes, you can make an EF for each day.

           

          You should be find your open event frame.  Do you retrieve any results?  Also, I would recommend changing the startIndex from one to zero since the startIndex is zero based and if you are expecting only one EF to match your criteria, than you will never see this!

            • Re: downtime event frame every date changed
              aljovinj

              You totally right, changing index from 1 to 0 I see it, but

               

              56e7b635-7a64-4dff-0000-00000000166dDowntimes 2016-03-01 06:59:07.84701/03/2016 06:59:07 a.m.01/03/2016 07:01:41 a.m.00:02:34.1260071PK4None
              56e7b635-7a64-4dff-0000-00000000164aDowntimes 2016-02-29 10:02:59.97629/02/2016 10:02:59 a.m.29/02/2016 10:26:12 a.m.00:23:12.3129883PK4None
              56e7b635-7a64-4dff-0000-000000001646Downtimes 2016-02-29 08:40:21.76929/02/2016 08:40:21 a.m.29/02/2016 09:01:01 a.m.00:20:39.6999969PK4None
              56e7b635-7a64-4dff-0000-0000000015f1Downtimes 2016-02-29 08:15:05.34929/02/2016 08:15:05 a.m.31/12/9999 11:59:59 p.m.2916036.10:44:53.6509858PK4None
              56e7b635-7a64-4dff-0000-0000000015ebDowntimes 2016-02-29 03:06:36.44029/02/2016 03:06:36 a.m.29/02/2016 03:33:59 a.m.00:27:22.8220062PK4None
              56e7b635-7a64-4dff-0000-0000000015eaDowntimes 2016-02-29 02:56:45.19729/02/2016 02:56:45 a.m.29/02/2016 02:59:27 a.m.00:02:42.2220001PK4None

               

              The downtime 56e7b635-7a64-4dff-0000-0000000015f1 didn't finish 2016-02-19 08:40:21.769 and still counting, maybe I'll backfilling this period to correct this mistake