Re: [foxboro] TOD alarming

Ted, could also use crontab to run a script setting a CIN, STALM, REALM or
any other alarming block.  This would use less block equivalents, as only
the block being alarmed is updated in the CP.

jim

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of TED PLUMB
Sent: Wednesday, June 09, 2004 4:50 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] TOD alarming

This is very close to the road we're heading down.  We have sucessfully
accomplished this only using two calca blocks instead of and ind block. 
Thanks

>>> RSmith@xxxxxxxxxxxxx 6/9/2004 1:15:07 PM >>>
Are you talking about something like an alarm clock, where an alarm is
generated when the system clock equals some operator entered day/time
value?
If so, while I have not done this, just off the top of my head, it
would
seem that at the least an independent sequence block could be used. 
The
operator entered values could be tied to block inputs and the block
could
compare the input values to the station block date/time values and set
a
boolean output when they are equal. The output could be tied to a CIN
to
generate the alarm.  I'm sure it could be done with a CALC block also
and
possibly even a series REALM blocks and a LOGIC block.

Roger B. Smith
Process Control Engineering
Department of Watershed Management
City of Atlanta
2440 Bolton Rd., NW
Atlanta, GA  30318
404.350.4952

 -----Original Message-----
From:   TED PLUMB [mailto:tplumb@xxxxxxxxxxxxxxx] 
Sent:   Tuesday, June 08, 2004 3:58 PM
To:     foxboro@xxxxxxxxxxxxx 
Subject:        [foxboro] TOD alarming

I'd like to alarm on an operator entered Time Of Day entry.  The time
could be the current day or sometime during the next day.  Has anyone
developed such logic?
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys
Process
Systems (formerly The Foxboro Company). Use the info you obtain here
at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html

 
foxboro mailing list:             http://www.freelists.org/list/foxboro

to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join

to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

 
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys
Process
Systems (formerly The Foxboro Company). Use the info you obtain here
at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html

 
foxboro mailing list:             http://www.freelists.org/list/foxboro

to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join

to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

 
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: