Created Date: July 18,2016

Created by: jvian

I am trying to use the event scheduler to trigger an event based on the "change " of a specific alarm; however, when i use for example Class.realtag->Hi or any other configured alarm for .realtag as the trigger for a "change " event, the scheduler does not trigger anything when the "trigger " is changed during runtime. Are specific alarm tag properties usable in the event scheduler? I can use the Class.realtag->AlrStatus as a trigger, this does work but this changes any time any alarm is activated, not just the specific alarm I am looking for. I can also use a math sheet which is executed when an alarm is on; however it continually executes until the alarm is off, whereas I want logic similar to a "one-shot " when an alarm transitions from off to on or vice-versa.

Hopefully there is a way to do this. Thanks in advance.

Created Date: July 18,2016

Created by: jvian

Yes the database spy works and shows the transition from 0->1->0 etc. as expected. This is what was confusing as I have used tag bits within scheduler before without any issue. For testing I was implementing a counter using an integer tag that would increment on a Class.realtag->Hi = 1 and decrement when the Class.realtag->Hi = 0 . No luck for me even though the tag is transitioning as expected. I use this property in several areas of the program so I know when it triggers. Just cant seem to use it in the scheduler.

Created Date: July 20,2016

Created by: ADC_CommTeam02

Response back from Vendor:

Testing this, issue is stemming from using a tag property in the Trigger field. This field is expecting a tag, not a tag property. It would be better to have another boolean tag receive the value of the Hi limit of their tag, and then use that boolean tag on the scheduler worksheet.

Please let me know if you have any questions or if this solution does not work.

Created Date: July 20,2016

Created by: jvian

So I am expected to create four boolean tags, one for each alarm for each tag I have in question? To me that seems incredibly inefficient and is unacceptable. I have 37 alarmable tags, so I must create 148 additional tags (plus all the needed logic to implement) just to trigger events, what a shame. Right now I am running 900+ tags out of a 1000 tag license so this is not possible, nor is upgrading to 5000 tags. I would hope this is something that can eventually be done, it would make the world of difference for my applications, but for now I may have to rethink my entire approach to alarms/events.

P3K, I thank you for your help, prompt replies and support.