Re: [foxboro] Alarms On Served Terminals
- From: "Ali Ahmed" <alizahidi@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 03 Mar 2006 09:44:30 +0000
I agree with Duc's suggestions. Here I would like to add one scenario that
using single server and multiple X-terminals will create single point of
failure i.e failure of the server will cause the loss of all DMs/FoxViews on
X-terminals.
Rgds,
Ali Ahmed Zahidi
>From: <duc.do@xxxxxxxxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: <foxboro@xxxxxxxxxxxxx>
>Subject: Re: [foxboro] Alarms On Served Terminals
>Date: Thu, 2 Mar 2006 14:49:58 -0500
>
>Ken,
>
>While we don't have P91 Server for Windows, we do use the remote display
>capability of the Solaris platform (without having to run a special box
>just to remotely distribute the DMs/FVs, imagine that!) and use
>plain-jane Dell XP PCs on the operator console to display the remote DM
>screens via Hummingbird Exceed. The alarm display and response should be
>no different be it on the Solaris or Windows platform.
>
>To answer your questions:
>
> > do you get audible alarming through these terminals
>
>No.
>
> >If you don't get audibles, what do you use for audibles in the
> >control room and how do you silence?
>
>We configure a contact output to drive an external horn through horn.cfg
>(/usr/fox/alarms/horn.cfg). The relevant lines include:
>
>5 Extsys None
>6 Extpri1 C2101A:PLB210112.IFL_12
>7 Extpri2 C2101A:PLB210112.IFL_12
>8 Extpri3 C2101A:PLB210112.IFL_12
>9 Extpri4 C2101A:PLB210112.IFL_12
>10 Extpri5 None
>
>In the PLB ladder, IFL_12 simply drives a contact output like this:
>
> IFL_12 CO_12
>--| |------------------------------------------------------------( )--
> 21AW01 UY
> EXTHORN 12345
>
>So any time a priority 1-4 alarm comes in, the AA system triggers the
>external horn via the horn.cfg. Sys alarms and priority 5 alarms do not
>sound the horn.
>
>The horn is silenced by clicking on the Alarm button on the top menu bar
>in the DM screen, which also brings the CAD display to the front so the
>operator can see the active alarm.
>
>(George Bocancea wrote of the desire to have a "silence horn" key on the
>keyboard, and I would like to have that, too, instead of having to use
>the mouse. It's just not high enough of a priority to do anything about
>it. But if somebody has done this, especially remapping a function key
>to silence the horn for use through an X emulator like Exceed, I'd like
>to steal your work.)
>
>Duc
>
>--=20
>Duc M. Do
>DCS Group, Carrollton Plant
>Dow Corning Corp.
>Carrollton, KY, US
>
>
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>On Behalf Of Ken Heywood
>Sent: Thursday, March 02, 2006 8:33 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: [foxboro] Alarms On Served Terminals
>
>I am following the discussion on alarm acknowledgement without GCIO with
>great interest. I don't see a definitive answer on the 'F12' key.
>Lacking a standard key, I like the 'dmcmd' approach and attach it to a
>key.
>
>There's another question that is raised by this discussion about
>terminals. I have limited experience with terminals; just a few remote
>information displays on PCs not requiring operator functionality.
>Several users mentioned previously about using P91 Server for Windows
>and bunches of XP PCs in the control room instead of more expensive AW
>workstations. Users of terminals, do you get audible alarming through
>these terminals and if you do, how do you silence the horn? If you don't
>get audibles, what do you use for audibles in the control room and how
>do you silence? Horn contact and panel pushbutton? Something else?
>
>Thanks.
>
>
>Best Regards,
>
>Ken Heywood, Marketing/Project Consultant
>Process Control Services, Inc.
>401 Industrial Drive
>Plymouth, MI 48170-1885
>
>'PCS means Providing Customer Satisfaction'
>
>Business Phone: (734) 453-0620
>Facsimile: (734) 453-6008
>Mobile Phone: (508) 241-2040
>Text Message: 5082412040@xxxxxxxxx (160 character limit)
>PCS Web: http://www.pcsmi.com <http://www.pcsmi.com/>=3D20
>
>
>CONFIDENTIALITY NOTICE - The information contained in this transmittal
>is confidential. It is intended for the addressee(s) stated above. If
>you are not an addressee you should not disclose, copy, circulate or in
>any other way use the information contained in this transmission. Such
>unauthorized use may be unlawful. If you received this transmission in
>error, please reply to me immediately so that the error can be corrected
>promptly.
>
>
>
>
>
>
>
>
>_______________________________________________________________________
>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
>
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
_______________________________________________________________________
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:
