Re: [foxboro] Suddenly loading the AApan file doesn't work to assign displays to the annunciator keypad

List,

Just thought I'd update you on the resolution.  A good old reboot of
each workstation cured it all, so over reliance on the pref command was
a mistake.

Plus, just for good measure, one of the buttons on an annunciator keypad
(previously spare) was not working.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Loudermilk, Virgil:
Sent: Thursday, August 14, 2008 10:11 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Suddenly loading the AApan file doesn't work to
assign displays to the annunciator keypad

Peter, I did that, and the dump file showed the same displays that I
loaded, so that's what has me so perplexed.  I'm starting to think there
might be some oddity with these new displays, so I think I'll try
displays that are known to work and see if that works. I also thought
maybe we needed to do the clearalarm panel command, but that is the
first thing the AApan file does.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Bruley, Peter T
Sent: Thursday, August 14, 2008 8:54 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Suddenly loading the AApan file doesn't work to
assign displays to the annunciator keypad

Perhaps what you are loading is not actually getting into the panel.

 There is a way to dump the memory of the annuciator panel to get the
configuration that is actually being executed on the station. It is
something like this:

pref -LBUG ascmd printalmpnl

(or it might be "prtalmpnl" I can't remember off hand)

This will create a file in /usr/fox/alarms with a "WPLOGICNAME.prt"
(look for the "prt" extension)

Then have a look at the dump file to see if it matches your
configuration.

Good Luck

Peter



 
 
_______________________________________________________________________
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
 
 
 
_______________________________________________________________________
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
 
 
 
_______________________________________________________________________
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: