Thanks Jerry and to everybody else, It was indeed conditional alarming. I've build the way you've mentioned and it works fine. Hans=20 -----Original Message----- From: Jerry Hidahl [mailto:Jerry_Hidahl@xxxxxxxxxxxx]=20 Sent: vrijdag 5 maart 2004 21:44 To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] inhibit of alarming Hans, You want "Conditional Alarming". Configure the nitrogen flow alarms and the mixer run status to inputs for a LOGIC block. Use the LOGIC block to "gate" the alarms from the CINs for the nitrogen flows to a Boolean Alarm block (BLNALM). Turn the state alarm option (SAO parameter) OFF for each of the CINs, and use the BLNALM block for all the alarms. In the LOGIC block, "AND" each of the nitrogen flow alarms with the mixer run state, and set a corresponding boolean output accordingly. Connect the inputs on the BLNALM block to the outputs from the LOGIC block. Consult the Invensys book Integrated Control Block Descriptions (BO193AX) if you need more detail. Jerry Hidahl =20 "Hans Bauwens" <Hans.Bauwens@per To: <foxboro@xxxxxxxxxxxxx> storp.com> cc: Sent by: Subject: [foxboro] inhibit of alarming =20 foxboro-bounce@fr eelists.org =20 =20 03/05/04 08:18 AM Please respond to foxboro =20 =20 Hello all, We are having a mixer which is stopped and started frequently. When the mixer is stopped , we don't want to have alarmering on the CIN blocks which are indicating the nitrogen flows to the seal and the powersupply to it. I have enabled this by connecting the inhibit parameter of the corresponding CIN blocks with the running contact of the mixer. The only problem I am having with using the INHIB parameter , is that there is a message send to the alarm manager when you disable and and enable the inhibit parameter. When the mixer is stopped the inhibit parameter of 3 CIN 's is enabled and 3 messages are send to the alarm manager. When the mixer is started, we have again 3 message send to the alarm manager. Does anybody now of a way to disable this function ? Hans Bauwens Perstorp Oxo Belgium AB _______________________________________________________________________ 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: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 =20 _______________________________________________________________________ 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 =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ 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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave