Re: [foxboro] Maintaining Foxview displays on mixed Windows and Unix consoles

Thanks, Ed, that is very helpful, but as usual with me answers always
bring up more questions!

1.  We use external horns so we should be ok with silencing, but how
about acknowledging?  I assume that gets handled by the block, but will
the message get sent to the station without the common alarm group
working?  I assume it will but I don't know for sure.  And is there any
workaround for "Clear Alarm" not working?

2.  Alarm history won't hurt us, so that's ok.

3.  We do have some fairly involved Bourne shell scripts, so that could
be the biggest problem, especially since a Unix wiz contractor wrote
them and they will have to be modified by a less than wizardly plant
engineer!  Does anyone have any pointers on converting to Korn shell
scripts?

4.  Why does Invensys "upgrade" without transferring all the
functionality?  I can understand having to rewrite scripts, upgrades
always have some of that kind of pain, but totally losing an important
function like Common Alarm Groups? =20

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Ed.Zychowski@xxxxxxxxxxxxxx
Sent: Wednesday, November 07, 2007 8:16 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Maintaining Foxview displays on mixed Windows and
Unix consoles

Virgil,
We currently run in a mixed environment and although we haven't yet=20
converted our unix "propagation" scripts to windows, a couple of things
we=20
learned late that should be considered are
1. Horn silencing via annunciator keyboards in a common alarm group=20
doesn't work across the ATS
2. Getting alarm history with the alarm display doesn't work across the=20
ATS (so if your historian is on the nodebus AW you can't get alarm
history=20
on the XP machine or vice versa)
3. Fonts on the windows machines are not the same as the ones on the
UNIX=20
machines so the displays will not look exactly the same
There are of course other differences (printer assignments, ability to
run=20
remote scripts, nutcracker uses the korn shell only so depending on the=20
shell your unix scripts were written in they will need to be modified,=20
etc) but these caught me by surprise.





"Loudermilk, Virgil:" <Virgil.Loudermilk@xxxxxxxxxxxxxxxxxx>=20
Sent by: foxboro-bounce@xxxxxxxxxxxxx
11/07/2007 06:22 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
[foxboro] Maintaining Foxview displays on mixed Windows and Unix
consoles






We are thinking of replacing our oldest Unix consoles with new Windows
ones, so that each operator will have 3 Unix and 1 Windows console.  We
have a nice Unix script to propagate displays to all stations.  Will it
be possible to revise it to include the Windows ones, or will we have to
manually convert to g and back to fdf for the Windows boxes?
=20
And are there any other things we will have to change to accommodate
these new Windows boxes?  We are on IA 7.1.1.
=20
Thanks,
Virgil
=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:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20



=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:             http://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:             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: