Re: [foxboro] Common Alarm Group - try run ksh
- From: Pablo Lioi <plioi@xxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 26 Feb 2014 22:03:19 +0000
Thanks Hizamri, I will try it in my system.
Best regards
Pablo
> Date: Sun, 23 Feb 2014 13:48:42 +0800
> From: hizamri@xxxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Common Alarm Group - try run ksh
>
> Dear Pablo
>
> I tried these syntax on our IA 8.8 :
>
> "Silence Horn" "run ksh /usr/fox/alarms/silence.bat" on a menu ( xxx.mnu
> ) file..
>
> I have also tried on a display bar ( xxx.dbr ) file :
>
> dmcmd dbar_button 16 "dmcmd run ksh /usr/fox/alarms/silence.bat" -l
> "Silence Horns"
>
> with the content of silence.bat:
>
> pref -WS7002 amcmd "silence_horns"
> pref -WS7003 amcmd "silence_horns"
> pref -WS7012 amcmd "silence_horns"
> pref -WS7013 amcmd "silence_horns"
>
>
> I think most if not all IA commands default to a D: drive...
>
> Both work silently, without any windows command box annoyance..
>
> Better yet, change the silence.bat extension to silence.ksh to avoid any
> confusion with other dos batch command file...
>
> God knows best..
> Best regards..
> Hizamri
>
> On 2/21/2014 2:48 AM, Pablo Lioi wrote:
>
> Ignacio,
> Thanks! I've already solved the problem - in a way - after finding an
> oldpost of yours in the archive.
>
>
> What I did:
>
>
> ***Sidebar button in Foxview***
>
>
> For each environment, I edited the '.dbr' file and added the following line:
>
>
> dmcmd dbar_button 16 "dmcmd run startp /min
> d:\usr\fox\alarms\silence.bat" -l "Silence Horns"
>
>
> ***Silence Horns button in CAD***
>
>
> run startp /min d:\usr\fox\alarms\silence.bat
>
>
> ***batch file***
>
>
> silence.bat:
>
>
> d:
>
> cd \usr\fox\system32
>
> pref -WS7002 amcmd "silence_horns"
>
> pref -WS7003 amcmd "silence_horns"
>
> pref -WS7012 amcmd "silence_horns"
>
> pref -WS7013 amcmd "silence_horns"
>
>
> This works... but there are a couple of problems:
>
>
> 1 - When I push the sidebar "Silence Horns" button for the first time
> after changing environment, it takes ages for the batch file to silence
> the horns and finish. Operators get nervous and push the button several
> times, resulting in several instances of the batch file running in
> separated command windows. After this, everything works fine.
>
> 2 - The "/min" switch doesn't work when the batch file is called from
> theCAD button, so there's an annoying "flash" when the command window
> opensand closes.
>
>
> Regards,
>
> Pablo
>
>
> >
> >
> >
> >
> >> From: ignacio.queirolo@xxxxxxx
> >> To: foxboro@xxxxxxxxxxxxx
> >> Subject: Re: [foxboro] Common Alarm Group
> >> Date: Thu, 20 Feb 2014 18:00:42 +0000
> >>
> >> Pablo, check the following links:
> >> //www.freelists.org/post/foxboro/foxboro-HyperSnap-6,7
> >> //www.freelists.org/post/foxboro/foxboro-Run-a-bat-Windows-in-a-Foxview-Button,3
> >>
> >> Regards
> >>
> >> -----Mensaje original-----
> >> De: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]En
> >> nombre de Pablo Lioi
> >> Enviado el: miércoles, 12 de febrero de 2014 18:40
> >> Para: foxboro@xxxxxxxxxxxxx
> >> Asunto: Re: [foxboro] Common Alarm Group
> >>
> >> Ok, this is what I did:
> >>
> >>
> >> 1- I created a script in my WS7003 workstation (silence.scp) with the
> >> following text:
> >>
> >>
> >>
> >> #!/bin/sh
> >> pref -WS7013 amcmd "silence_horns"
> >>
> >>
> >>
> >> Note: WS7003 and WS7013 are in DIFFERENT CAG's
> >>
> >>
> >>
> >> 2 - With the horn sounding in WS7013, I run the script from the command
> >> line in WS7003 and verified that the horn is silenced, as expected.
> >>
> >>
> >>
> >> 3 - With ADMC I modified the action of the "Silence horn" button to:
> >>
> >>
> >>
> >> silence_horns
> >>
> >> run /usr/fox/alarms/silence.bat
> >>
> >>
> >>
> >> The first line takes care of the horns in the CAG and the second line
> >> silences the horns of the workstations outside of the CAG.
> >>
> >>
> >>
> >> Note that I had to write a batch file for the "run" command. I tried the
> >> "script /usr/fox/alarms/silence.scp" first, but it didn't work.
> >>
> >>
> >>
> >> This is the text of the silence.bat file:
> >>
> >>
> >>
> >> d:
> >>
> >> cd \usr\fox\alarms
> >>
> >> call \nutc\bin\ncenv.cmd
> >>
> >> \nutc\mksnt\sh.exe silence.scp
> >>
> >>
> >>
> >> With this configuration, pressing the "Silence horns" button in the CAD
> >> silences both the horns in all workstations.
> >>
> >>
> >> PROBLEM: there's an annoying "flash" after pressing the "Silence horns"
> >> button, when the command line window opens and closes.
> >>
> >>
> >>
> >> 4 - There's a "Silence horns" button in the Foxview button bar. I tried to
> >> modify the dbr environment file to launch the script, but failed. The
> >> sintax I tried was:
> >>
> >>
> >>
> >> dmcmd dbar_button 16 "dmcmd run /usr/fox/alarms/silence.bat" -l "Silence
> >> horns"
> >>
> >>
> >>
> >> Is there a better way of calling the script from a CAD button (and a menu
> >> bar button)?
> >>
> >>
> >>
> >> Regards,
> >>
> >> Pablo
> >>
> >>
> >>
> >>> From: Russ.Boulay@xxxxxxxxxxxx
> >>> To: foxboro@xxxxxxxxxxxxx
> >>> Date: Wed, 12 Feb 2014 10:16:20 -0500
> >>> Subject: Re: [foxboro] Common Alarm Group
> >>>
> >>> I believe the second CAG group approach would still clear all alarms in
> >>> both groups.
> >>>
> >>> You need to set a standard for horn silence.....like a button on graphic
> >>> or annun keyboard that will run the pref command to all workstations to
> >>> silence horns.
> >>> Silence 4 workstations
> >>>
> >>> #!/bin/sh
> >>> pref -AMNAME amcmd "silence_horns"
> >>> pref -AMNAME amcmd "silence_horns"
> >>> pref -AMNAME amcmd "silence_horns"
> >>> pref -AMNAME amcmd "silence_horns"
> >>>
> >>> ______________________________________________________________________
> >>> _______________
> >>>
> >>> Russ Boulay | Schneider Electric | Invensys | United States | Support
> >>> Engineering Manager
> >>> Phone: +1 508 446 1769 | Mobile: +1 508 446 1769
> >>> Email: russ.boulay@xxxxxxxxxxxx | Site: www.invensys.com | Address:
> >>> 2000 Crow Canyon Place Suite 170, 94583 San Ramon, California, United
> >>> States
> >>>
> >>> *** Please consider the environment before printing this e-mail
> >>>
> >>> -----Original Message-----
> >>> From: foxboro-bounce@xxxxxxxxxxxxx
> >>> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
> >>> martin.theobald@xxxxxxxxx
> >>> Sent: Wednesday, February 12, 2014 7:00 AM
> >>> To: foxboro@xxxxxxxxxxxxx
> >>> Subject: Re: [foxboro] Common Alarm Group
> >>>
> >>> Pablo,
> >>> Each workstation can be in up to two Common Alarm Groups (CAGs). Use the
> >>> 'CAG NAME2' field in the <commgrp.cfg> file to set up a second overall
> >>> group for all four workstations. Make sure that the change is made on all
> >>> of the workstations to be affected. Each workstation will need to be
> >>> rebooted to make the change effective.
> >>>
> >>> See document B0700AT Workstation Alarm Management for further details.
> >>> The are also a number of FAQ/SOL notes on the GCS site.
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Martin Theobald
> >>>
> >>> -------------------------------------------------
> >>> eControl - Runcorn
> >>> INEOS Chlor Vinyls
> >>>
> >>> M: +44 7767 87 1989
> >>> T: +44 1928 51 2044
> >>> F: +44 1928 51 6653
> >>> -------------------------------------------------
> >>>
> >>>
> >>>
> >>> From: Pablo Lioi <plioi@xxxxxxxxxxx>
> >>> To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>,
> >>> Date: 12/02/2014 14:32
> >>> Subject: [foxboro] Common Alarm Group
> >>> Sent by: foxboro-bounce@xxxxxxxxxxxxx
> >>>
> >>>
> >>>
> >>> Hello all,
> >>> In our control room, we have four I/A 8.4.3 XP operator workstations.
> >>>
> >>> Operators wanted the workstations grouped in pairs for alarm management.
> >>> So I configured two alarm groups, with 2 WS each (say WS1/2 and WS3/4),
> >>> and set the clear alarm option to "Delete alarm throughout the CAG".
> >>> Everything worked as expected.
> >>>
> >>> But there is a problem: operators want the "Silence Horns" function to
> >>> work on both groups at the same time (i.e., pressing the "Silence Horns"
> >>> button in any workstation silences horns in all workstations). For what I
> >>> know, it can't be done...
> >>>
> >>> As an alternative, I could put all the workstations back in the same
> >>> CAG to solve the "Silence Horns" problem, but I would need some trick
> >>> to make the clear and ack alarm function work in pairs (i.e., clearing
> >>> alarms in WS 1 also clears alarms in WS 2 and vice-versa, but doesn't
> >>> affect WS 3 and 4; clearing alarms in WS 3 also clears alarms in WS 4
> >>> and vice-versa, but doesn't affect WS 1 and 2)
> >>>
> >>> As for why would anybody want to group 4 WS that are a few feet apartfrom
> >>> each other in two groups... well, it's one of those Operations things.
> >>>
> >>> Thanks,
> >>>
> >>> Pablo Lioi
> >>>
> >>> TOTAL AUSTRAL S.A.
> >>>
> >>> Tierra del Fuego - Argentina
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ______________________________________________________________________
> >>> _ 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
> >>>
> >>>
> >>> INEOS is a trade mark, the property of INEOS Capital Limited. The "Bubble
> >>> Logo", CERECLOR, DX PLUS, MEFLEX, METHOKLONE, PERKLONE, SOLVE-CARE,
> >>> TRIKLONE and TRISEC are trade marks, the property of INEOS ChlorVinyls
> >>> Limited. CEREPLAS, DIRECT SALT, HYDROSOFT, LINDROX AND WHITEROX are trade
> >>> marks, the property of INEOS Enterprises Limited. BICHLOR, CHLORCOAT, FM
> >>> and PEMcoat are trade marks, the property of INEOS Technologies Limited.
> >>> EVIPOL is a trade mark, the property of INEOS Vinyls UK Limited.
> >>>
> >>>
> >>>
> >>>
> >>> ______________________________________________________________________
> >>> _ 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
> >>> legallyprivileged. 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
> >>> anypurposes, or disclose its contents to any other person. This email
> >>> comesfrom a division of the Invensys Group, owned by Invensys plc, which
> >>> is acompany 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 select the Legal Entities link at invensys.com. Invensys PLC is
> >>> owned by the Schneider-Electric Group.
> >>>
> >>> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> >>> reception@xxxxxxxxxxxx. 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
> >> atyour 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
> >>
> >> AVISO LEGAL: Esta información es privada y confidencial y está dirigida
> >> únicamente a su destinatario. Si usted no es el destinatario original de
> >> este mensaje y por este medio pudo acceder a dicha información por favor
> >> elimine el mensaje. La distribución o copia de este mensaje está
> >> estrictamente prohibida. Esta comunicación es sólo para propósitos de
> >> información y no debe ser considerada como propuesta, aceptación ni como
> >> una declaración de voluntad oficial de YPF S.A. y/o subsidiarias y/o
> >> afiliadas. La transmisión de e-mails no garantiza que el correo
> >> electrónico sea seguro o libre de error. Por consiguiente, no manifestamos
> >> que esta información sea completa o precisa. Toda informaciónestá sujeta a
> >> alterarse sin previo aviso. This information is private and confidential
> >> and intended for the recipient only. If you are not the intended recipient
> >> of this message you are hereby notified that any review, dissemination,
> >> distribution or copying of this message is strictly prohib
> > it
> >> ed. This communication is for information purposes only and shall not be
> >> regarded neither as a proposal, acceptance nor as a statement of will or
> >> official statement from YPF S.A. and/or subsidiaries and/or affiliates.
> >> Email transmission cannot be guaranteed to be secure or error-free.
> >> Therefore, we do not represent that this information is complete or
> >> accurate and it should not be relied upon as such. All information is
> >> subject to change without notice.
> >>
> >>
> >> _______________________________________________________________________
> >> 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:
