adccommunitymod (AutomationDirect) asked a question.
Created Date: September 09,2013
Created By: lhayhurst
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Is there a way to prevent the C-More from sending out nuisance emails on start up or reboot? In other words can the event manager be set to wait for the next state change of monitored bits? For example C0 represents the status of the e-stop circuit. In event manager when C0 is off, c-more emails an e-stop alarm message. When C0 is on, c-more emails an e-stop return to normal message. Every time we reboot or load in a new program all emails associated with active or inactive bits go out. Thanks for your input.
Created Date: September 10,2013
Created by: scott.lawrence
you could flop the logic, possibly using another bit that turns on when C0 turns off.
instead of looking for an off condition, look for an on condition
Created Date: September 10,2013
Created by: lhayhurst
That is what I was afraid of: 28 sites, several hundred alarms per site...
Created Date: September 10,2013
Created by: scott.lawrence
if all of your alarms are sequential, you could just use the value of the word(s) to send email.
Event Manager gives the option of using comparison statements as well as inside/outside range options...
Created Date: September 09,2013
Created by: lhayhurst
Is there a way to prevent the C-More from sending out nuisance emails on start up or reboot?
In other words can the event manager be set to wait for the next state change of monitored bits? For example C0 represents the status of the e-stop circuit. In event manager when C0 is off, c-more emails an e-stop alarm message. When C0 is on, c-more emails an e-stop return to normal message.
Every time we reboot or load in a new program all emails associated with active or inactive bits go out.
Thanks for your input.