Re: [foxboro] Listing all Configured Alarms
- From: "Pauwels, Dirk - RSM" <Dirk.Pauwels@xxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 17 Dec 2004 16:41:15 +0100
We use the getpars as well to list alarms, groups, limits, HLOP and
HHAOPT, PRI etc... Settings via scripts
Rgds,
Dirk Pauwels - DCS coordinator=20
Engineering dept.
Lawter International BVBA
An RSM Company
Ketenislaan 1c - Haven 1520
B-9130 Kallo, Belgium
T. +32.(0)3.570.95.97/ Mob. +32.(0)497.428.300
F. +32.(0)3.570.16.09
E mail: dirk.pauwels@xxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin FitzGerrell
Sent: vrijdag 17 december 2004 0:42
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Listing all Configured Alarms
Notes garbled the info, so I'm resending from webmail.
Quoting "kevin.fitzgerrell@xxxxxxxxxxxx"
<kevin.fitzgerrell@xxxxxxxxxxxx>:
>=20
> Although it doesn't use the iccprt output, it might be worth looking
at
>=20
> Foxboro's HH1068.
>=20
> =20
HH#: HH1068
IA INFO: sja0403
File: Control, Alarms
Release: All
Date: Nov 04, 2004
Subject: Determining Which Alarms Are Configured On Your System, Per
Block
Source: TAC
Here is a procedure that uses the utility program "getpars" to determine
the=20
alarm types that are set on your system for each of the blocks.
"getpars" is very flexible and has several options. Look at the
getpars.man=20
file (in /opt/fox/bin/tools) to see the complete list of options. The
following
is just one example.=20
Log into your system in VT100 and go to the tools directory.
cd /opt/fox/bin/tools
Run the following command:
getpars -U\* -C\* -B\* -mCMPNM:%12s -mTYPE:%6s -mALMOPT:%8x >
alarm.txt
The command options are as follows:
-U\* all cp's
-C\* all compounds
-B\* all blocks
-mCMPMN:%12s prints the compound name as a 12-character
string
-mTYPE:%6s prints the type of block as a 6-characters
string
-mALMOPT:%8x prints the parameter ALMOPT as an 8-digit hex
number
> alarm.txt redirects the output to a file called alarm.txt
The backslashes are required before the asterisks so that the Unix shell
will=20
not evaluate the * as filenames.
Here is an example of the output:
COMPOUND-NAME AC_PIDA (CP-LETTERBUG: CP660F)
BLOCK-NAME CMPNM TYPE ALMOPT
CALC AC_PIDA CALC NA
AIN1 AC_PIDA AIN 0
AIN AC_PIDA AIN 13430080
PIDA AC_PIDA PIDA 0
FBTUNE AC_PIDA FBTUNE NA
AOUT AC_PIDA AOUT 0
LLAG AC_PIDA LLAG NA
DTIME AC_PIDA DTIME NA
DEP AC_PIDA DEP 0
In this example only AC_PIDA:AIN has alarm options set.=20
When the value shows "NA", it means that that parameter does not apply
to=20
that block type.
To determine what is set for this block convert the hex number into
binary.
1 3 4 3 0 0 8 0 (Hex)
0001 0011 0100 0011 0000 0000 1000 0000 (Bin)
Then look up the ALMOPT parameter in B0193AX, Control Block
Descriptions.
Here is the ALMOPT parameter for an AIN block.
B4=3D Out-of-Range Alarm, B7=3DHHALM, B8=3DLLALM, B15=3DHABS, =
B16=3DLABS,=20
B7=3DAlarm Group 1
This is for an AIN. All the other blocks are listed in the document
and,=20
if they have an ALMOPT, parameter, the individual option bits will be
shown.
A general description of the parameter for all block types is given as a
table in B0193AW, Integrated Control Concepts.
HH1068
=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: http://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: 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: