Alarm state keeps occurring even after ACK in Runtime

Applies To:

PAC Display Professional
PAC Display Basic

Versions Affected:

Problem was discovered in version: R8.2m
Resolution is included beginning in version: B8.2n, Build date November 30, 2009 and later
Problem is fixed in version: R9.0a

Resolved In Version:

Problem is fixed in version: R9.0a

Symptoms:

For a Summary Alarm Type graphic at Runtime, an acknowledged alarm point in an alarm condition incorrectly triggers another alarm notification if the value of the alarm point changes and is still within the same alarm level. This occurs if in Configuratior, the alarm point is Setup By (in the Setup tab) Current Value, and the states (LoLo, Hi, etc.) are configured to use Tag values (in the Value tab).

For example: Suppose an alarm is set up to use a tag for the Lo value. The SetLoAlarm tag is used to set the Lo value to 10.

At Runtime, when the alarm point has a value of 15, it is in the Normal state. If the value changes to 9, the alarm point is in the Lo state, enters in an alarm condition, and causes a message to appear in the alarm window. After acknowledging the alarm point, the message color changes to the acknowledged color (typically green), with ACK State level appearing in the State column. If the alarm point value changes to 8, the alarm point message incorrectly reappears as an alarm that needs to be acknowledged again, even though it is still in the same acknowledged alarm condition. Because it had been Acknowledged in the Lo state, and is still in the Lo state, the alarm point should not appear as an alarm that needs to be acknowledged again. If a sound had been configured for the alarm point, it will also sound again.

This does not affect Detailed or History Alarm Type graphics.

Questions?

Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
Email: support@opto22.com

DISCLAIMER

This Opto 22 Knowledge Base ('OptoKB') article is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this OptoKB article is not intended to constitute application, design, software, or other professional engineering advice or services. Opto 22 may modify the OptoKB articles at any time. Before making any decision or taking any action which might affect your equipment, you should consult a qualified professional.

OPTO 22 DOES NOT WARRANT THE COMPLETENESS, TIMELINESS, OR ACCURACY OF THE DATA CONTAINED IN THIS OPTOKB ARTICLE AND MAY MAKE CHANGES THERETO AT ANY TIME AT ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS 'AS IS.' IN NO EVENT SHALL OPTO 22 BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT, OR DAMAGE, EVEN IF OPTO 22 HAS BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

OPTO 22 DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED WITH RESPECT TO THE INFORMATION (INCLUDING HARDWARE, SOFTWARE, AND/OR FIRMWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTIBILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not sanction the exclusion of implied warranties: thus, this disclaimer may not apply to you.