Re: [foxboro] WP51D- Alarm Messages

Dear Mr. Tom,
Thank you for your help. Your advise solved my problem. Actually I missed
assigning the new WP as 'System Monitor WP' in System Definition.
Thanks again.

Rgds,
Ali

----- Original Message -----
From: <tom.vandewater@xxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Monday, July 25, 2005 6:06 AM
Subject: Re: [foxboro] WP51D- Alarm Messages


> Ali,
> We have seen something similar to the problem you describe and
> this is what we learned.  In the ICC when assigning WP's to the Compound
> Alarm Groups it is possible to select "SHOW" from the top menu bar and
> then "Available WP's" from the pulldown menu.  This causes a list of all
> Available WP's, (as defined in SysDef), to appear on the right side of
> the ICC window.  With the compound param GR1DV1 selected you can click
> on any WP from the list and the ICC will enter the selected WP in the
> GR1DV1 field.  If you do not hit the "ENTER" key before selecting
> another parameter or if you select "Done" without hitting "ENTER", the
> WP name you selected will continue to show in the ICC compound parameter
> but it will never work.  By contrast, if you manually type in the WPNAME
> and forget to hit enter before selecting another parameter or hitting
> "DONE" the field will be blanked out.  This is an odd bug/quirk that has
> eaten the lunch of many a knowledgeable ICC user.  My suggestion is
> this:
> 1. Enter ICC on the CP where your compound resides
> 2. Select the Compound you want to alarm from the list on left of the
> ICC window
> 3. Select "Edit Compound Parameters"
> 4. With compound parameters showing select the GR/DV param with the bad
> WP name and delete all text then ((HIT "ENTER"))!!!
> 5. Pick "DONE"
> 6. Select "Edit Compound Parameters" again
> 7. Select the GR/DV param you wish to assign
> 8. Select "SHOW" from top menu
> 9. Pick "Available WP's"
> 10.Select the new WP's Logical Name from the list
> 11.You should see the New WP Logical name in the GR/DV you had selected
> 12. ((HIT "ENTER"))!!!
> 13. ((HIT "DONE"))!!!
> 14. Test to see that the alarm function now works correctly
>
> The System alarms generated by each individual System Monitor are
> directed to a primary and secondary printer as well as System Monitor
> WP's as assigned in System Definition.  Check to insure that your new WP
> is assigned as a "System Monitor WP" in System Definition!
> I think these suggestions will correct your problems.  I would
> appreciate feedback if this works.
>
>
> Cheers,
> Tom VandeWater
> Control Systems Developer/Analyst
> Dow Corning Corporation
> Carrollton, KY   USA
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of ALI AHMED ZAHIDI
> Sent: Monday, July 25, 2005 8:26 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] WP51D- Alarm Messages
>
> =20
> Dear Mr. Alex,=20
>
> The WP logical name in the ICC is correct. The alarms are being received
> on
> other "good WP" but not on the bad WP. The alarm reception problem is
> not
> only with Process Alarms but also with the system alarms. Kindly advise.
>
>
> Rgds,=20
>
> Ali=20
>
>
> >From: "Johnson, Alex P" <alex.johnson@xxxxxxxxxxxxxxxx>
> >Reply-To: foxboro@xxxxxxxxxxxxx
> >To: foxboro@xxxxxxxxxxxxx
> >Subject: Re: [foxboro] WP51D- Alarm Messages
> >Date: Mon, 25 Jul 2005 08:12:34 -0400
> >
> >The most typical problem is that they are not being sent or the WP's
> logical
> >name is misspelled in the alarm group.
> >
> >My free advice is:
> >
> >1) Create a new compound
> >    a) Set ON to 1
> >    b) Put the logical name of the "bad" WP and a "known good" WP in
> GR1DV1
> >and GR1DV2.
> >2) Create a CIN block in the compound and set:
> >    a) IOMOPT=3D2
> >    b) SAO=3D1
> >    c) Fill in the alarm text fields
> >    d) Set MA to 1
> >4) Raise the detail display for the CIN block
> >5) Toggle the IN parameter to generate an alarm
> >
> >You should see it appear in both places.
> >
> >If it shows only on the good and not the "bad" WP, I'd double check the
> WP
> >logical name.
> >
> >
> >Hope this helps.
> >
> >Regards,
> >
> >Alex Johnson
> >Invensys Systems, Inc.
> >10707 Haddington
> >Houston, TX 77063
> >+1 713 722 2859 (voice)
> >+1 713 932 0222 (fax)
> >+1 713 722 2700 (switchboard)
> >alex.johnson@xxxxxxxxxxxxxxxx
> >I hope to see you at the Invensys Process System User Group meeting
> October
> >3-6 in Houston, TX -
> >www.invensys.com/usergroup2005
> >-----Original Message-----
> >From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> >Behalf Of ALI AHMED ZAHIDI
> >Sent: Monday, July 25, 2005 6:49 AM
> >To: foxboro@xxxxxxxxxxxxx
> >Subject: [foxboro] WP51D- Alarm Messages
> >
> >  Dear All, We have recently added a WP51D in our I/A Series System.
> The
> >station was added to nodebus successfully but it is not receiving
> system
> and
> >process alarm messages. Do any one have any idea?   Thanks, Ali Ahmed
> Zahidi
> >Karachi, Pakistan.
> >-----------------------------------------------------------------------
> ----
> -
> >FREE pop-up blocking with the new MSN Toolbar MSN Toolbar[1] Get it
> now!
> >
> >--- Links ---
> >    1 http://g.msn.com/8HMBEN/2752??PS=3D47575
> >
> >
> >_______________________________________________________________________
> >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=3Djoin
> >to unsubscribe:      =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> >
> >
> >
> >
> >_______________________________________________________________________
> >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=3Djoin
> >to unsubscribe:      =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> >
>
>
> ------------------------------------------------------------------------
> ----
> FREE pop-up blocking with the new MSN Toolbar MSN Toolbar[1] Get it now!
>
>
> --- Links ---
>    1 http://g.msn.com/8HMBEN/2755??PS=3D47575
> =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
>
>
 
 
_______________________________________________________________________
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: