Technical data

Table Of Contents
Organization Blocks
System Software for S7-300/400 System and Standard Functions - Volume 1/2
1-46
A5E00709327-01
If you want to program OB86 dependent on the possible error codes, we
recommend that you organize the local variables as follows:
Variable Type
OB86_EV_CLASS BYTE
OB86_FLT_ID BYTE
OB86_PRIORITY BYTE
OB86_OB_NUMBR BYTE
OB86_RESERVED_1 BYTE
OB86_RESERVED_2 BYTE
OB86_MDL_ADDR WORD
OB86_Z23 DWORD
OB86_DATE_TIME DATE_AND_TIME
The following table show the event started OB86:
OB86_EV_CLASS OB86_FLT_ID Meaning
B#16#39 B#16#C1 Expansion rack failure
OB86_MDL_ADDR: Logical base address of the IM
OB86_Z23: Contains one bit for each possible expansion rack:
Each expansion rack that caused a call of OB86 is reported as
having failed (the respective bits are set). Expansion racks that
previously failed are no longer shown.
- Bit 0: always 0
- Bit 1: 1st expansion rack
- :
- Bit 21: 21st expansion rack
- Bit 22 to 29: always 0
- Bit 30: Failure of at least one expansion rack in the
SIMATIC S5 area
- Bit 31: always 0
B#16#38 B#16#C1 Expansion rack operational again
OB86_MDL_ADDR as for OB86_FLT_ID=B#16#C1. The
expansion racks that are operational again are reported in
OB86_Z23 (the respective bits are set).
B#16#38 B#16#C2 Expansion rack operational again (expansion rack failure with
discrepancy between expected and actual configuration)
OB86_MDL_ADDR: Logical base address of the IM
OB86_Z23: Contains one bit for every possible expansion
rack, see OB86_FLT_ID B#16#C1.
Meaning of the set bit: in the affected expansion rack:
- Modules with an incorrect type ID exist
- Configured modules missing
- At least one module is defective.