Re: [foxboro] Annunciator Keyboard LEDs
- From: "Boulay, Russ" <Russ.Boulay@xxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 21 Jan 2004 16:41:19 -0500
When you first implement the commgrp.cfg file, during the first reboots to
implement the groups, you may get an
"unable to retrieve backup table" or something similiar.
You will get this message if the backup workstation is unable at the time
the local station looks to it's backup to retrieve files.
If the backup station is down, then it can't retrieve the alarms from the
backup station.
So the order of reboot can affect this message.
Usually a good practice is to reboot the first station, wait until it's up ,
then reboot the next and so on.
***Also, for common alarm group to work correctly, one should ensure that
the AAtab and AApan files are identical for the members of a particular
group, and the workstations normally receive the same process alarms.
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx On Behalf Of "Jaime Claramunt
> R. (Inforsa)" <jclaramunt@xxxxxxxxxxxxxxx>
> Sent: Wednesday, January 21, 2004 1:02 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Annunciator Keyboard LEDs
>
> About this cmmgrp.cfg .... " 'still havn't found what I'm looking for..."
> The alarms backup is not working. I have a message :unable to load
> table...
> or something like this..
>
> But..., common group for alarm ack and horn silence work fine for
> annunciators, though.
>
> I realize my cmmgrp.cfg files are the same for the same group but not the
> same between them in the node.
>
> Is it mandatory to have exactly the same file everywhere ? or it's enough
> to
> define inbetween groups ?
> How can I solve the backuo problem for reboots or redefinig annunciators ?
>
> regards
> Jaime
>
>
>
> -----Mensaje original-----
> De: Boulay, Russ [mailto:Russ.Boulay@xxxxxxxxxxxx]
> Enviado el: Viernes, 16 de Enero de 2004 09:50
> Para: 'foxboro@xxxxxxxxxxxxx'
> Asunto: Re: [foxboro] Annunciator Keyboard LEDs
>
>
> In /usr/fox/alarms there is a file named commgrp.cfg (common alarm
> group)
> This file is initially built when you run a utility called CAGinit....in
> the
> same directory.
>
> CAGinit will gather all workstation letterbugs on the system, and
> construct
> the commgrp.cfg file.
> Listing all workstations in the first column.
> The user must then edit this file, providing group names, backup stations
> etc.
> Once file is the way you want it, you must copy the file to all affected
> workstations and reboot.
> From then on, and acknowledgement from one workstation wil acknowledge all
> members of the same group.
>
>
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx On Behalf Of oswald gomez
> > <oswaldgomez@xxxxxxxx>
> > Sent: Friday, January 16, 2004 7:33 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: [foxboro] Annunciator Keyboard LEDs
> >
> > hi guys,
> >
> > I've got a question, hope you can help me.
> >
> > I've got three stations (2WP and 1AW). I also have three annunciators,
> one
> > for each station.
> >
> > I know there are two files: XXXXATAB and the other one XXXXAPAN for the
> > configuration of keys, displays and panels.
> >
> > Is there any file I can edit to configure the way I acknowledge the
> > alarmas. I mean I've noticed that I have to press the red (the one with
> > the little red trumpet on it) button more than once whenever an alarm
> gets
> > off.
> >
> > Where's that file?
> >
> > thanks a lot
> >
> >
> >
> >
> > ---------------------------------
> >
> > Antivirus #8226; Filtros antispam #8226; 6 MB gratis
> > ?Todavia no tienes un correo inteligente?
> >
> >
> >
> > _______________________________________________________________________
> > 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
> >
>
> -- No attachments (even text) are allowed --
> -- Type: application/ms-tnef
>
>
>
>
> _______________________________________________________________________
> 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
>
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
_______________________________________________________________________
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:
