Re: you can use the new NASTDB and NASOPT parameter (time related parameters to avoid chattering), but I am almost sure that PID\PIDA\etc... do not support that yet These parameters and others were added in V8.4. This is taken from B0700RT - Table D-3 Process Alarm Enhancements Summary: The following Block Types PID, PIDA, PIDE,PIDX, PIDXE, DPIDA Added support for: * Alarm Reprioritizaiton (PRTYPE) on these alarms: HHA/LLA, HA/LA, HDA/LDA, HOA/LOA * Alarm Message Regeneration (AMRTIN) on these alarms: HHA/LLA, HA/LA, HDA/LDA, HOA/LOA * Nuisance Alarm Suppression (NASOPT, NASTDB) on these alarms: HHA/LLA, HA/LA, HDA/LDA, HOA/LOA Regards, Alex Johnson Invensys Operations Management 10900 Equity Drive Houston, TX 77041 +1 713 329 8472 (desk) +1 713 329 1600 (operator) +1 713 329 1944 (SSC Fax) +1 713 329 1700 (Central Fax) alex.johnson@xxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Corey R Clingo Sent: Friday, May 06, 2011 10:58 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Alarm timer supression on PIDA block "This can be a good Improvement for the I/A actually." +1. We try to attach alarms to the "primary operator interface" blocks, and if a controller exists, the PID(A) is almost always that block. Corey From: Ricardo Abech <abech@xxxxxxxxxxxx> To: foxboro@xxxxxxxxxxxxx Date: 05/06/2011 07:48 AM Subject: Re: [foxboro] Alarm timer supression on PIDA block Sent by: foxboro-bounce@xxxxxxxxxxxxx Hi Luciano, For most block types (AIN, CIN, etc?) you can use the new NASTDB and NASOPT parameter (time related parameters to avoid chattering), but I am almost sure that PID\PIDA\etc... do not support that yet, so you have to stick with the deadband (MEASDB), not very reliable to avoid chattering if the noise or variance is high. Unless you can use the AIN instead of the PID to alarm (not a good idea most of the time, since the PID is normally the block you use in the display). This can be a good Improvement for the I/A actually. Maybe there is something already, but I am not aware of it. Ricardo _______________________________________________________________________ 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 legally privileged. 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 any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company 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 go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail reception@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