[foxboro] RE : Hard-coding the block inhibit parameters
- From: "Doucet, Terrence" <tdoucet@xxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 26 Jun 2007 11:11:27 -0400
I hope that I am not being redundant with any of this information. The first
item to configure when you want the alarm is the Option parameter. Each type
of alarm has its own parameter name. As an example, we use the AIN High/Low
Option (HLOP) then you have
0 = No alarming
1 = High and Low absolure
2 = High Abs only
3 = Low abs only
So if you only want low alarming then configure a 3 in this parameter and you
never need to worry about high alarms.
Once you have your alarm configured then you should connect the .INHSTA
parameter to the INPUTS parameter of a MCIN (no IO) block. Then you can use the
AIN default display - ALARMS - overlay to toggle the inhibits that you desire.
Now go to the default display for the MCIN and you can view the hex pattern in
the INPUTS: box. For example if you inhibit the High and Low Absolute alarms
your will see 00030000 displayed.
To set only the high and the low inhibit your would set the hex pattern 0x0003
into the AIN.INHALM. Use a program or a script with omsetimp to write this hex
value.
Toggling the AIN.INHIB to a TRUE will inhibit all the configured alarms in
your block. Setting AIN.INHIB to a FALSE will release the AIN block to inhibit
only those specified by the hex pattern of the INHALM. Obviously, with INHIB =
FLASE and INHALM = 0 all configured alarm annunciation is enabled.
Terry
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat
_______________________________________________________________________
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
- Follow-Ups:
- Re: [foxboro] RE : Hard-coding the block inhibit parameters
- From: Joseph M. Riccardi
- References:
- Re: [foxboro] Hard-coding the block inhibit parameters
- From: Armour, Alan
Other related posts:
- » [foxboro] Hard-coding the block inhibit parameters
- » [foxboro] RE : Hard-coding the block inhibit parameters
- Re: [foxboro] RE : Hard-coding the block inhibit parameters
- From: Joseph M. Riccardi
- Re: [foxboro] Hard-coding the block inhibit parameters
- From: Armour, Alan