Re: [foxboro] foxboro Digest V8 #14

  • From: "Tom VandeWater" <tjvandew@xxxxxxxxx>
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Tue, 15 Jan 2008 16:18:50 -1000

Rick,
     I may have missed something in this so forgive me if I ask a simple but
possibly head slapping question.  Are the Compound:Block alarms being
directed to your workstation through the Compound or Station group device
mechanism?  In other words: "Do all of the alarms show up in the Current
Alarm Display" on your specific workstation but won't initiate a light?
Tom VandeWater
Control Conversions Inc.
Tesoro PM Manager

On 1/15/08, Rguercio@xxxxxxx <Rguercio@xxxxxxx> wrote:

>
>
> In a message dated 1/15/2008 12:13:19 Central Standard Time,
> foxboro@xxxxxxxxxxxxx writes:
> The  easiest way of detecting duplicate Compound:Block entries in the
> file is  the following:
>
>
>
> Thanks to everybody who has responded to my problem.  There is  still a
> problem, and here is what I have done:
>
> I am very familiar with the loadalmpnl and prtalmpnl commands and use them
> all the time.  They make the panel buttons work and produce the exact file
> contents I would expect.  I am not having trouble with the AApan  file and
> key-pushing functions.  My problem is:  I cannot get  the associated AAtab
> file to
> be recognized (can't get alarms to light ANY  LED's).
>
> Before this last round of help, I had already checked for duplicates in
> the
> ...AAtab file using the Excel route (and thanks everyone for the other
> dup-checking utilities which I will keep in my bag of Foxboro Tricks),
> and  I
> actually started from scratch with FoxPanels configurator and set up
> a  simple
> panel.  Sure enough, the AApan file created made the key-pushes  work, but
> I could
> not get any LED's to light.  I verified that the ...AA...  files I had
> previously created had both the same name and same format as
> those  created by
> FoxPanels, thus eliminating that path.  The only difference  was that
> FoxPanels, of
> course, created the <LBUG>.apc file, whereas I had  never seen that file
> in
> /usr/fox/alarms before.  I thought, "aha, here is  the problem, even
> though
> dozens of other workstations have been working  successfully without it
> for
> years".  Despite all this, the new ...AAtab  file apparently isn't getting
> recognized, as the new annunciator setup would not  report any alarms to
> the LED's.
> Sorry this is so long, but I wanted to  make sure everyone understood the
> situation.  That given, is there any  wisdom to be had?
>
> RGC
> 12803 Josey Creek Ct.
> Cypress, TX 77433
> 713-805-8742  cell
> 281-256-1111 home office/FAX
> 281-256-1333  home
>
>
>
> **************Start the year off right.  Easy ways to stay in shape.
> http://body.aol.com/fitness/winter-exercise?NCID=aolcmp00300000002489
>
>
>
>
> _______________________________________________________________________
> 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: