1.

14 CPU Redundancy Error OB (OB72)

Note
The CPU redundancy error OB (OB72) exists only with H CPUs.

Description
The operating system of the H CPU calls OB72 when one of the following events occurs:
Loss of CPU redundancy
Reserve-master switchover
Synchronization error
Error in a SYNC module
Updating aborted
Comparison error (for example, RAM, PIQ)
OB72 is executed by all CPUs that are in the RUN or STARTUP mode following a suitable start event.

Local Data of the CPU Redundancy Error OB

The following table contains the temporary (TEMP) variables of the CPU redundancy error OB. The
default names of OB72 have been used as the variable names.

Variable Type Description

OB72_EV_CLASS BYTE Event class and IDs:
B#16#78: outgoing event
B#16#73, B#16#75, B#16#79: incoming event
OB72_FLT_ID BYTE Error code (possible values: B#16#01, B#16#02,
B#16#03, B#16#20, B#16#21, B#16#22, B#16#23,
B#16#31, B#16#33, B#16#34, B#16#40, B#16#41,
B#16#42, B#16#43, B#16#44, B#16#50, B#16#51,
B#16#52, B#16#53, B#16#54, B#16#55, B#16#56,
B#16#C1, B#16#C2)
OB72_PRIORITY BYTE Priority class; can be assigned via STEP 7
(hardware configuration)
OB72_OB_NUMBR BYTE OB number (72)
 Variable Type Description
OB72_RESERVED_1 WORD Only for error code B#16#03:
High byte: ID for the content of OB72_INFO_2
and OB72_INFO_3
- 0: OB72_INFO-2 and OB72_INFO_3 are of
no significance
- B#16#C4: Transition to redundant mode
after troubleshooting mode was carried out
with standby-master switch-over (if
OB72_INFO_3=W#16#0001) or without
standby-master switch-over (if
OB72_INFO_3=W#16#0002).
OB72_INFO_2 is reserved.
- B#16#CD: OB72_INFO_2 and
OB72_INFO_3 contain the actual lock time
for priority classes > 15
Low byte: reserved
OB72_INFO_1 WORD Only for error code B#16#C2:
high byte: identifier for the exceeded monitoring
time:
- 1: Cycle time extension
- 2: I/O dead time
- 4: Communication delay
low byte: current update attempt
OB72_INFO_2 WORD Only for error code B#16#03 and
OB72_RESERVED_1=B#16#CD: high word of the
actual lock time for priority classes > 15 in ms
OB72_INFO_3 WORD Only for error code B#16#03:
OB72_RESERVED_1=B#16#C4:
- W#16#0001: Transition to redundant
operation after troubleshooting mode was
carried out with standby-master
switch-over
- W#16#0002: Transition to redundant
operation after troubleshooting mode was
carried out without standby-master
switch-over
OB72_RESERVED_1=B#16#CD: high word of
the actual lock time for priority classes > 15 in
ms
OB82_DATE_TIME DATE_AND_TIME DATE_AND_TIME at which the OB was called

System Software for S7-300/400 System and Standard Functions Volume 1/2
Reference Manual, 05/2010, A5E02789976-01 47
The following table shows which event caused OB72 to be started.

OB72_EV_CLASS OB72_FLT_ID Start Event of OB72

B#16#73 B#16#01 Loss of redundancy (1 of 2) due to a CPU failure
B#16#73 B#16#02 Loss of redundancy (1 of 2) due to STOP on the reserve triggered by
user
B#16#73 B#16#03 H system (1 of 2) changed to redundant mode
B#16#73 B#16#20 Error in RAM comparison
B#16#73 B#16#21 Error comparing process image output value
B#16#73 B#16#22 Error comparing memory bits, timers, or counters
B#16#73 B#16#23 Different operating system data recognized
B#16#73 B#16#31 Standby-master switchover due to master failure
B#16#73 B#16#33 Standby-master switchover due to system modification during runtime
B#16#73 B#16#34 Standby-master switchover due to sync module connection problem
B#16#73 B#16#40 Synchronization error in user program due to elapsed wait time
B#16#73 B#16#41 Synchronization error in user program due to waiting at different
synchronization
points
B#16#73 B#16#42 Synchronization error in operating system due to waiting at different
synchronization points
B#16#73 B#16#43 Synchronization error in operating system due to elapsed wait time
B#16#73 B#16#44 Synchronization error in operating system due to wrong data
B#16#79 B#16#50 No SYNC module
B#16#79 B#16#51 Modification at SYNC module without Power On
B#16#79/B#16#78 B#16#52 SYNC module removed/inserted
B#16#79 B#16#53 Modification at SYNC module without reset
B#16#79 B#16#54 SYNC module: rack number assigned twice
B#16#79/B#16#78 B#16#55 SYNC module error/eliminated
B#16#79 B#16#56 Illegal rack number set on the SYNC module
B#16#73 B#16#C1 Updating aborted
B#16#73 B#16#C2 Abort of update attempt because a monitoring time was exceeded
during the n-th attempt (1 <= n <= maximum possible number of
update attempts after an abort due to the monitoring time being
exceeded.)