I have an Analysis setup that compares the current value to a value 1 minute ago. I can see the values of the triggers changing, but an Event Frame is not created, therefore my Notification is also not being generated.
Could you please right click on the event frame analyis and check preview results? Would like to know if trigger condition is TRUE during the time period selected.
Why not 'PI Test Point' <> TagVal('PI Test Point','*-1m')? Not sure what is hiding behind the second attribute.
And what does the Analysis preview return as results? That often gives more insights into why an analysis is not returning the results as expected.
It seems as though the Event Frame has triggered
Roger: I have tried 'PI Test Point' <> TagVal('PI Test Point','*-1m'), which does seem to set the Event Frame, but the problems is that the Notification does not go out.
Also, it seems as though the Notification does go out, but only the first time. If I stop and start the Event Frame Analysis, it will work the first time only
Thank you for your help
Could you please check if first event frame is closed?
Also check if Notification email is set to send email during start and end of the event frame or only during start. Would suggest you to check the time period where event frame is generated in preview results and try to backfill to test after deleting existing event frames.
I set it up to end an email at the end of the event frame, but have not gotten any. Upon checking the Event Frames, the End Time is posted, but it seems to post only when a new Event Frame is started.
Can you share the entire configuration of your Notification?
Have you had a look in the Notification logs? Have you tried setting Trace on the Notification logger? See this blog post for more information: https://pisquare.osisoft.com/message/113683-re-notifications-dont-trigger-when-events-are-too-close-one-another?commentI…
Is the Event Frame annotated?
I think I found a solution. The reason the Notification was not being sent out was because the end trigger was not being fired (Thanks Lal Babu Shaik for putting me on that path). I'm not entirely sure why the EndTrigger did not fire, but to resolve this I just set the EndTrigger to 1 so that it closes immediately, which is what I wanted in the first place.
Thank you everyone for your help
You can remove end trigger from the event frame so that if start trigger evaulates to false it will close the event frame automatically once it is generated. Also request you to check the scheduling option. If it is set to event-triggered then would request you to check how frequency data is updated for "PI Test Point". Preview results and archive data for this tag should provide answer why end trigger does not fire in your case.
Yes, you are correct on both counts. Not having an end trigger did not work for me because the analysis was triggered by a change in the PI Test Point, but this only occurred when I manually changed it. When I did this, the previous EventFrame did not close. I could have set the scheduling to be periodic, but the "real" attribute that I will be using when I implement this will change at most once or twice a month
Retrieving data ...