,1&20,1*DODUP
287*2,1*DODUP
$FNQRZOHGJPHQW
287*2,1*$/$50/,67
$&.12:/('*('
$/$50/,67
$FNQRZOHGJPHQW
287*2,1*DODUP
+,6725</,67
352&(66&21
752//,67
2SHUDWLRQ
,1&20,1*$/$50/,67
$OOXQDFNQRZOHGJHG
DODUPV
$ODUPVFOHDUHGEHIRUH
DFNQRZOHGJPHQW
$FNQRZOHGJHGDFWLYH
DODUPV
23(5$7,21/,67
$/$50/2*
9LHZVRIWKH
DODUPORJ
ILOWHUHGOLVWV
Alarm log
All alarms, operator information and status changes are saved to the alarm log. You can use
the filters to read specific information from the alarm log.
5.5.5
Overflow of message buffer
Overflow of message buffer
Each component of the overall PCS 7 system can process only a limited number of messages.
If more alarms are generated in a component (for example, an AS) within a particular time
frame than the component can process, some of these alarms will be lost. If this case, the AS
sets an overflow flag and the following event is reported at the PCS 7 OS: "NRMS7 Messages
Lost".
Note
If events that trigger messages change status in very quick succession, this can trigger a
message surge. The overview of the plant status can no longer be sufficiently ensured.
Message concept of PCS 7
5.5 Understanding messages
Service support and diagnostics (V8.0)
60
Service Manual, 03/2012, A5E02779775-02
