Re: [foxboro] System Alarms
- From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 9 Jul 2002 12:58:22 -0400
Re: Where can I know the GCLBUG of our IA system? I don't know exactly the
difference between logical names, etc
Each DM/FV on a AW/WP has a logical name. The boot DM/FV's logical name is
the letterbug of the AW/WP. The logical names for all configured DM/FVs are
specified in the file /usr/fox/customer/hi/dmcfg. There is a .man file there
with instructions on how to configure the names.
When WPs could run only one DM/FV, GCLBUG had two definitions. It was both
the letterbug of the WP and the logical name of the DM.
When the 50-Series was released, the two definitions were split. GCLBUG is
now used for the WP letterbug, but DMNAME is used for the logical name of
the DM/FV being used.
For example, you could build a pickable point on a graphic to print the
letterbug and the DM name like so:
dmcmd msglin "Letterbug: $GCLBUG. DM name: $DMNAME"
The message line should show on the base DM/FV:
Letterbug: W1BPW1. DM name: W1BPW1
On a different DM/FV on the same WP, you would get something like:
Letterbug: W1BPW1. DM name: W1BPW2
Does this help?
Regards,
Alex Johnson
Invensys
10707 Haddington
Houston, TX 77063
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx>
Come to the Invensys Showcase: http://www.invensysshowcase.com/
<http://www.invensysshowcase.com/>
-----Original Message-----
From: pharizna@xxxxxxxxxxxxx [SMTP:pharizna@xxxxxxxxxxxxx]
Sent: Tuesday, July 09, 2002 7:17 AM
To: kgrace@xxxxxxxxxxx; foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] System Alarms
Hi Kathy:
One very easy question for you...
For example, if the GCLBUG of our AW is : W1BPB1... which one is the
=
syntax of the "omget" call for this variable?
omget ALMSTATEW1BPB1 or ALMSTATE:W1BPB1 ? Neither work!
Where can I know the GCLBUG of our IA system? I don't know exactly
the =
difference between logical names, etc
Regards
Pedro Hernandez
REPSOL YPF Quimica
13500 Puertollano (C.Real)
SPAIN
-----Mensaje original-----
De: Grace, Kathy [mailto:kgrace@xxxxxxxxxxx]
Enviado el: lunes 8 de julio de 2002 19:43
Para: 'Sebastian Roman '
CC: 'foxboro@xxxxxxxxxxxxx '
Asunto: Re: [foxboro] System Alarms
Here is the information I promised on the ALMSTATE variable.
1. Each workstation has a global called ALMSTATE<GCLBUG>. Do an =3D
'omget'.
This returns a decimal value.
2. Convert it to hex. The bit pattern is as follows:
| | Horn | "ALARM" or | "SYS" or |
| Unused | Mute Status | "Process" | "System" |
| 15 14 13 12 | 11 10 9 8 | 7 6 5 4 | 3 2 1 0 |
Bit 0: Process Alarms: 0 - Normal (Green) / 1 - Alarm (Red)
1: 0 - Acked (Solid) / 1 - Unacked (Flash)
2: 0 - Unused
3: 0 - Unused
4: System Alarms: 0 - Normal (Green) / 1 - Alarm (Red)
5: 0 - Acked (Solid) / 1 - Unacked (Flash)
6: 0 - Unused
7: 0 - Unused
8: Local Horns: 0 - Unmuted / 1 - Muted
9: CAG 1 Horns: 0 - Unmuted / 1 - Muted
10: CAG 2 Horns: 0 - Unmuted / 1 - Muted
11: Unused: 0
12: Unused: 0
13: Unused: 0
14: Unused: 0
15: Unused: 0
-----Original Message-----
From: Grace, Kathy=3D20
Sent: Wednesday, July 03, 2002 11:43 PM
To: 'Sebastian Roman '; 'Foxboro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx '
Cc: 'foxboro@xxxxxxxxxxxxx '
Subject: RE: [foxboro] System Alarms
Hi,
There is a workstation global called ALMSTATE which contains the =3D
encoding
for the "SYS"/"System" button, "ALARM"/"Process" button, and the
horn =
=3D
mute
state. I am out of the office until Monday, but I can send you the
=3D
details
then. It is set by Alarm Alert and read by the Display Manager
and/or
FoxView.
Kathy Grace
-----Original Message-----
From: Sebastian Roman
To: Foxboro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Cc: foxboro@xxxxxxxxxxxxx
Sent: 7/3/02 4:28 PM
Subject: [foxboro] System Alarms
Hi,
I am looking for the signal that active the SYS button, (The system
alarms=3D20
button). Can somebody help me ?
Thanks in advanced,
_________________________________________________________________
=3DDAnase al mayor servicio mundial de correo electr=3DF3nico:=3D20
http://www.hotmail.com/es
=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list:
//www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=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
_______________________________________________________________________
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:
