800xA Alarm Tone Problem cropped up after loading feature pack 3 to version 5.1
We have a problem with the alarm tones on our 800xA system. At our plant, we only configured Priority 1 alarms to produce an audible alarm tone. We were running with version 5.1, and the alarm tones were operating fine. THEN --- We loaded Feature Pack 3 to the 5.1 and then the problem appeared as follows; If there is a Priority 1 alarm that is unacknowledged (currently active or not) then, any alarms (priority 2 or 3) that come in after that will produce another Priority 1 alarm tone, this will continue until the P1 is acknowledged. Once you acknowledge the Priority 1 alarm, and a P2 or P3 come in, they do not produce a P1 alarm tone, however again if another P1 alarm comes in and is not acknowledged, the problem pops back. The alarm template and audible alarm configuration appears to be configured correctly, in fact we do not even have anything configured for P2 or P3. Never had, because all we wanted was the P1 alarm tones.
Audible alarms are more complex than you think.
There has been changes made over time and what you describe after loading FP3 sounds like the intention with the audible alarm feature.
At each "change" to an alarm list the highest prioritized alarm sound will play. A new silent P2 or P3 alarm will re-trigger the P1 sound if that alarm is still unacknowledged.