Re: [foxboro] OMI - operator message interface

I've developed a sort of a queue for my batch projects for operator messages
related to trips and interlocks.  There are three strings on the exception
block that are three trips.  If there are more than three trips, when one is
cleared, it is replaced by a fourth, fifth, etc.  Only drawback is that the
operator cannot see > 3 until the first three are cleared.

Jim

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Jerry Hidahl
Sent: Wednesday, April 28, 2004 12:26 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] OMI - operator message interface





We have a FoxBatch system with eight kettles. Each kettle might have four
sequences running, depending on what's happening. We don't use OMI for
operator messaging. We use string variables to display all the messages.
Each kettle has a dedicated message string variable in a DEP block that is
only used for data storage(no sequence).. Acknowledgement, if needed is
handled with a boolean variable for each kettle. Plant standard subroutines
handle all the messaging. The advantage is that all the messages can be
displayed on the operators normal graphic operating display. One weakness
in our messaging system is we can only show one message at a time, and
there's no queue.

Jerry Hidahl

 
 
_______________________________________________________________________
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: