Matt, Not sure if this is an option for you, but you can create a display that have only the specific Block you want to acknowledge and then add a code to the display (dmcmd) to ACK the Block every time the display is called. Then you just need to add the display in your Annunciator keyboard. Then the Annunc Key will work as an Pushbutton. Remember to add a code to auto-close the display after ACK the block. I did not try that, but in theory I guess it works. Regards, Ricardo P. Abech Chief Software Architect LimeWare Company, Inc. [USA phone]: (408) 786 5140 [phone]: +55 51 3388 8270 [mobile]: +55 51 8192 9723 [email]: abech@xxxxxxxxxxxxxxxxxxx [http://]: www.limewarecompany.com -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex P (IPS) Sent: Tuesday, November 18, 2008 4:53 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] External Pushbutton for acknowledge Matt, Re: Is there a simple way to use a physical input from an external pushbutton to acknowledge a specific alarm? To actually acknowledge the alarm, you have to reset (drive to FALSE) the parameter UNACK of the target block. This requires a one-shot set to the UNACK parameter. The only ways to generate a reset of the UNACK parameter on a physical contact change are: 1) Use an IND block to monitor the contact (WAITUNTIL) and the reset UNACK (:C:B.P := FALSE) 2) Use a script to monitor the contact and reset the UNACK - very inefficient. 3) Write a program to do it - double heaps of uck! Hope this helps. Regards, Alex Johnson Invensys Process Systems 10900 Equity Drive Houston, TX 77041 713 329 8472 (desk) 713 329 1600 (operator) 713 329 1944 (SSC Fax) 713 329 1700 (Central Fax) alex.johnson@xxxxxxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Kinsinger, Matthew R Sent: Tuesday, November 18, 2008 11:32 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] External Pushbutton for acknowledge Is there a simple way to use a physical input from an external pushbutton to acknowledge a specific alarm? I know a script could do it, or even a simple sequence block, but for one pushbutton and one block I was hoping to avoid those two routes. Any help is appreciated. Matt Kinsinger Process Control Engineer PPG Barberton _______________________________________________________________________ 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 and any associated files are intended solely for the individual or entity to whom they are addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Further, this e-mail and any associated files may be confidential and further may be legally privileged. This email is from the Invensys Process Systems business unit of Invensys plc which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Process Systems business group, please click here http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77 . If you have received this e-mail in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Thank you for your co-operation. You may contact our Helpdesk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx 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 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