show the entry list
Migration to PCS 7 -- Product information -- System description
Why in PCS 7/Open OS alarms can not be acknowledged?
Why are the communication connections between PCS 7/90 OS and NETWORK 90 CIU reset periodically when using Rovisys OPC Server V7.4.1?
Which versions of the PCS 7 OS migration products are compatible with which versions of PCS 7?
What steps are necessary to migrate a TI 505 controller to a PCS 7 OS project?
What restrictions are to be kept in mind for PCS 7 OS migration products based on V6.1?
Required Version of 4-mation for PCS 7/APACS+ OS
Why in PCS 7/Open OS alarms can not be acknowledged?
Part number:

Description
In very rare cases, when initiating full OS downloads to a running PCS 7/OPEN OS system with active alarms, it can happen that active alarms in the alarm list cannot be acknowledged after an entire OS-compile in DBA.
In the same manner also false process alarms can be triggered that can also not be acknowledged afterwards.

Proposed workaround
In the case of an actual alarm that is stuck, it is necessary to:
 
No. Description
1 Make the alarm condition inactive.
2 Make the alarm condition active again.
3 Acknowledge the alarm.
Table 01

Then this alarm should work fine.

 Entry ID:61629704   Date:2012-06-21 
I regard this article....as helpfulas not helpful                                 
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour