Hello All,
I would like to know if we can trigger the event engine to run on a specific range of historic tag data.
Say I have an event configured based on the value of Tag A and in realtime the event executes as intended but then a couple of days later it turns out Tag A has bad data (But good Quality) and I go back and change the historical data for Tag A, now can I trigger the event engine to look at the new set of Tag A historical data and generate events based on it ?
Thanks in Advance.
No.
But if you've written your events as one-liners that delegate to project library script functions (and you should, always), you can write your own routine that pulls the history from that range and calls those same functions.
@pturmel thanks for your response, I didn't understand
"But if you've written your events as one-liners that delegate to project library script functions (and you should, always)"
I am only aware of configuring the events on the "Alarm" section of the tags themselves, are you referring to an alternate way of configuring events like a gateway script that runs in the background?
No, I'm saying to write common logic in a project library script and call that function from wherever you need to define the event. So any event script, at the point where you must place it, for that kind, is a one-line call to the project library function. Passing whatever arguments to the function from the origin context that the function will need.
Many identical alarms can share the same function if written to use arguments efficiently. And you can call that function from other places to "re-execute" an alarm script.
Side note: alarm events and other events defined on the tag can only reach the global scripting project's libraries. Make sure you've created such.
Thanks for clearing that up, what impact will it have on performance for a system that has 1000s of tags?
Runs faster--shared code using less memory. Shared code eventually gets jitted into native code, making it even faster.