Integration Of Simocode Pro In Simatic S7 With Om Simocode Es - Siemens SIMOCODE pro Function Manual

Communication
2.1 PROFIBUS communication
2.1.6.3

Integration of SIMOCODE pro in SIMATIC S7 with OM SIMOCODE ES

Diagnostic interrupt/hardware interrupt
The diagnostics data concerning diagnosis alarms and process interrupts is transmitted and
evaluated during the integration of SIMOCODE pro as an S7 slave.
DP masters operated in DP mode "DPV1" (e.g. all later SIMATIC S7-300/400 DP master systems)
Behavior and sequence in STEP7:
Behavior and sequence in STEP7A diagnosis interrupt (OB 82) is triggered in the CPU every
time a new device fault is diagnosed, whereas a hardware interrupt (OB 40) is triggered
every time a new process fault / warning / status information is diagnosed. If OB 82 or OB 40
has not been programmed, the CPU switches to "STOP" mode.
Interrupts from a DPV1 slave, received with STEP7:
The interrupt is read directly in OB 82 or OB 40 with SFB 54 "RALRM."
The data range addressed with SFB 54 by means of the "AINFO" parameter contains the
interrupt information described in Section "Structure of the slave diagnostics (Page 19)". The
first byte which is read corresponds to byte 28.
You will find further information on SFB 54 in the STEP7 online help.
DP masters operated in DP mode "S7-compatible"
(e.g. all early SIMATIC S7-300/400 DP master systems)
Behavior and sequence in STEP7:
Behavior and sequence in STEP7A diagnosis interrupt (OB 82) is triggered in the CPU every
time a new device fault is diagnosed, whereas a hardware interrupt (OB 40) is triggered
every time a new process fault / warning / status information is diagnosed. If OB 82 or OB 40
has not been programmed, the CPU switches to "STOP" mode.
You will find information about the device fault in the start information of OB 82 in the
"OB82_MDL_DEFECT" variable. The start information of OB 40 contains the
"OB40_POINT_ADDR" variable, which in turn contains the data of the hardware interrupt
that is described in bytes 32 to 35 (see Section "Structure of the slave diagnostics
(Page 19)"). Reading the entire diagnosis can then be initiated, for example, from OB 40,
while the complete diagnostic record 92 is being read in the cyclic user program with the
SFC 52 "RD_REC", for example.
You will find further information on SFB 59 in the STEP7 online help.
36
SIMOCODE pro - Communication
Function Manual, 11/2018, A5E40508495002A/RS-AC/003