Re: [foxboro] More Process Summary Reporter Quirks
- From: "Wilson, Brad" <brad.wilson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 22 Oct 2008 09:27:21 -0400
To expand on what Alex said, look at the interaction between INHIB and
INHOPT. When INHIB is toggled, the action is determined by the value of
INHOPT.
INHOPT=0 will result in msgs being suppressed but detection continues.
INHOPT=1 will result in both msgs and detection being suppressed.
I suppose in I/A-speak, when INHIB is true, INHOPT=0 is an inhibited
alarm, and INHOPT=1 is a disabled alarm.
INHOPT=2/3 are the same as 0/1 with the addition that return-to-normal
states are automatically acknowledged for uninhibited alarms.
When INHIB is toggled, it will invoke INHOPT actions for ALL alarms in
the block. Although I've never used the feature, it appears you can
inhibit alarms individually by setting bits of INHALM. It appears the
INHOPT setting applies to any alarm so inhibited. There is no way to,
say, inhibit high meas alarming (suppress msgs only) and disable output
alarming (suppress both msgs and detection) at the same time.
Since INHOPT is noncon/nonset, if you want to have both capabilities in
a block (inhibit sometimes, disable sometimes), I think you'd probably
want to set INHOPT=1 and use INHIB to disable alarming (no detection)
and redirect the alarm group to block msgs only (while still allowing
detection).
Brad Wilson
brad.wilson@xxxxxxxxxxxxxxxx
Invensys Process Systems, Inc
1090 King Georges Post Rd, Suite 204
Edison, NJ 08837
732-661-4012 o
732-874-0087 c
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Tuesday, October 21, 2008 7:41 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] More Process Summary Reporter Quirks
Virgil,
I can't answer all of your questions, you need a PSR expert and I'm not
one. However,...
Re: As far as I know, Foxboro only uses the term Inhibited alarm, not
disabled alarm.
The I/A Series supports both alarm inhibition and alarm disable options.
An inhibited alarm will detect the alarm and set the alarm indication
status bits, but it will not send the message to any configured alarm
destinations.
A disabled alarm will not detect the alarm, will not set the alarm
indication status bits, and will not send a message to the configured
alarm destinations.
The difference between a disabled alarm and an un-configured alarm is
that the disable function is one that can be changed without using the
control configurator. If the alarm has never been configured, you must
use the control configurator to enable it. Whereas, if you configure it
and disable it, you can restore its operation at any time through your
HMI.
Make some sense?
Regards,
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (desk)
713 329 1600 (operator)
713 329 1944 (SSC Fax)
713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxxxxxx
* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual or
entity to whom they are addressed. Please do not copy it or use it for any
purposes, or disclose its contents to any other person. Further, this e-mail
and any associated files may be confidential and further may be legally
privileged. This email is from the Invensys Process Systems business unit of
Invensys plc which is a company registered in England and Wales with its
registered office at Portland House, Bressenden Place, London, SW1E 5BF
(Registered number 166023). For a list of European legal entities within the
Invensys Process Systems business group, please click here
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
If you have received this e-mail in error, you are on notice of its status.
Please notify us immediately by reply e-mail and then delete this message from
your system. Thank you for your co-operation. You may contact our Helpdesk on
+44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail
and any attachments thereto may be subject to the terms of any agreements
between Invensys (and/or its subsidiaries and affiliates) and the recipient
(and/or its subsidiaries and affiliates).
_______________________________________________________________________
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
Other related posts:
