Re: [foxboro] foxboro Digest V8 #22
- From: Rguercio@xxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Sun, 20 Jan 2008 20:06:09 EST
In a message dated 1/19/2008 22:47:49 Central Standard Time,
foxboro@xxxxxxxxxxxxx writes:
I have a question for all you experts: I am cleaning up a 10-year-old
system with some 30-odd workstations. This is in a refinery with groups
consisting usually of 3 workstations assigned to a refinery unit or group of
related
units. We have consistently configured every block with its alarm group
(4-8), etc. Suppose workstation 3 needs to report to one of its annunciator
keys/LED's the alarms from just one screen from workstation 17, which is one
of
the assigned workstations of that alarm's CP alarm group, and has its points
configured to and reporting to a different set of workstations than the one to
which 3 "belongs". In other words, the respective CPs for workstation 17's
group have had their STATION parameters edited to report the desired screen's
alarms up to just those stations, and I don't want ALL of the CP's alarms
reported to station 3, just one screen's worth (a shared utility but with all
points belonging to a CP dedicated to workstation 17's group). How do I get
only that screen's alarms to report also to workstation 3's annunciator panel
which is configured in its ...AApan to pull up the shared screen? Is there a
way to read another annunciator's key/LED and have it fire a different
annunicator's LED? I know from the command line or with a script that we can
make
a given LED light up (thanks to Andreas Weiss), but it seems a shame to have
to constantly run a script whose sole job is to check for this one LED on one
panel and report it to another, and even then, I'm not sure if it would
blink until acknowledged or not, etc. Any ideas?
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
Other related posts:
