Re: [foxboro] Talk about old annunciator keyboards on an old UNIX system...
- From: "Joseph M. Riccardi" <Joe@xxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 2 Apr 2012 09:04:05 -0400
Terry,
Thanks for the reminder; I did not even think about the source AW file I
copied from (it's always a shocker how easily we lose sight of the forest
for the trees). This is my next step.
Just curious, why do you say it is an "easy" check for duplicate names?
What tool are you suggesting that makes it easy? I'm pushing for Foxray
here because that is one of its features but not sure what tool is available
in the meantime that would make that chore easy.
Thanks again.
Joseph M. Riccardi
386-441-0250 Office
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Terry Doucet
Sent: Monday, April 02, 2012 8:54 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Talk about old annunciator keyboards on an old UNIX
system...
Joe,
The two AA files .pan and tab are text files so you can easily check them
for duplicate names. If you copied them from another station, then you need
to fix that station (s), too.
Also if you have a common alarm group so that this station gets the active
alarms from its partner station then their AA pan and AA tab files must be
identical.
Terry
> From: Joe@xxxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Talk about old annunciator keyboards on an old UNIX
system...
> Date: Mon, 2 Apr 2012 08:47:53 -0400
>
> Russ,
>
> Thanks for the feedback. I did check for the gcio_task and it was
running.
> I forgot about the /usr/local/local_printer issue. The file did exist
(how
> did gcio_task get started?) so I have deleted it. I then killed and
> restarted the ast and aa_wp50 tasks but still no luck.
>
> Just for the record:
> - In System Management, both devices show "Not Failed" yet they appear
> highlighted in red.
> - When I restarted ast and aa_wp50 tasks (not sure which one) I did get
the
> message "Invalid or duplicate compound/name or panel/key value in alarm
> table". I have seen this before at many sites but I do not believe it
will
> cause the failure.
>
> I am rebooting now and will also try Dirk's suggestion. I should know
> something in a few minutes...
>
> Thanks.
>
> Joseph M. Riccardi
>
> 386-441-0250 Office
> 386-451-7607 Cell
>
> Joe@xxxxxxxxxxxxx
>
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A.
Adams
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
> Behalf Of Boulay, Russ
> Sent: Monday, April 02, 2012 12:37 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Talk about old annunciator keyboards on an old UNIX
> system...
>
> When you do a process listing....is gcio_task actually running?
>
> If not...check for the existence of a local_printer file in /usr/local....
>
> It will prevent gcio from starting...
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
> Behalf Of Joseph M. Riccardi
> Sent: Sunday, April 01, 2012 9:33 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] Talk about old annunciator keyboards on an old UNIX
> system...
>
> Folks,
> Well, maybe no one was talking about them but they were on my mind all
week
> because one of them quit working; no one remembers why or when so. I
> methodically replaced every part (GCIO, annunciator keyboard, cables,
etc.);
> everything except the actual serial card in the UNIX box. After I
replaced
> each part I tried the shortcut to kill and restart one of the annunciator
> keyboard commands (ast -sig and aa_wp50 -sig; or something like that
because
> I do not have my notes with me so working from memory). That never worked
> so I actually rebooted the AW each time. I initially copied the *.tab and
> *.pan files from its neighbor and renamed the file for the appropriate AW
(I
> think the logical name but again working from memory). Nada. Still no
> working annunciator panel.
>
> The System Management page shows Failed or Not Failed depending on which
> part I replaced but always shows the failed color on both the GCIO and the
> annunciator keyboard before, during and after the above exercises in
> futility. And it gives me no options except to Update EEPROM which fails
> each time (I assume because it cannot communicate with either device).
>
> Where did I go wrong?
>
> How can I check the serial card; I do not want to open up the UNIX box
> unless I actually have to? With old UNIX boxes I just believe in the old
> saying - "Let sleeping dogs lie".
>
> Is there something else I need to do if I just copy and rename the *.tab
and
> *.pan files from another working AW. The original files even looked OK.
>
> Yes, I could have replaced a defective part with another defective part.
> Any way to test individual parts?
>
> Any suggestions or help would be deeply appreciated? I keep sneaking a
peek
> of my neighbor's shoulder looking at their annunciator keyboard. They are
> getting suspicious and nervous.
>
> Thanks.
>
> Joseph M. Riccardi
>
> 386-441-0250 Office
> 386-451-7607 Cell
>
> Joe@xxxxxxxxxxxxx
>
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A.
Adams
>
>
>
>
>
>
> _______________________________________________________________________
> 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
>
>
>
> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to which
it
> is addressed. This e-mail is confidential and may well also be legally
> privileged. If you have received it in error, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then
delete
> this message from your system. Please do not copy it or use it for any
> purposes, or disclose its contents to any other person. This email comes
> from a division of the Invensys Group, owned by Invensys plc, which is a
> company registered in England and Wales with its registered office at 3rd
> Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023).
For
> a list of European legal entities within the Invensys Group, please go to
> http://www.invensys.com/en/legal/default.aspx.
>
> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its subsidiaries
and
> affiliates).
>
>
>
>
> _______________________________________________________________________
> 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
>
_______________________________________________________________________
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:
