Event Recognition By Cpus 31X-2 As The Dp Master - Siemens S7-300 Installation Manual

7HVWLQJ IXQFWLRQV DQG 'LDJQRVWLFV
(YHQW UHFRJQLWLRQ
The table below shows how CPU 31x-2 operating as DP master recognizes
operating mode transitions of a CPU operating as DP slave or data exchange
interruptions.
Table 11-8
(YHQW
Bus failure interrupt
(short-circuit,
connector unplugged)
DP slave: RUN →
STOP
DP slave: STOP →
RUN
(YDOXDWLRQ LQ WKH XVHU SURJUDP
The table below shows how you can, for example, evaluate RUN to STOP
transitions of the DP slave in the DP master.
Table 11-9
Diagnostic addresses: (Example)
Master diagnostic address =
Slave diagnostic address =
The CPU calls OB 82 with the following
information:
•
OB 82_MDL_ADDR:=
•
OB82_EV_CLASS:=B#16#39 (incoming
event)
•
OB82_MDL_DEFECT: = Module error
Tip: The CPU diagnostic buffer also
contains this information
In the user program you should also include
SFC13 "DPNRM_DG" for reading out DP
slave diagnostic data.
11-14

Event recognition by CPUs 31x-2 as the DP master

•
Calls OB 86 with the message 1RGH IDLOXUH (coming event;
diagnostic address of the DP slave assigned to the DP
master)
•
with I/O access: Call of OB122 (I/O access error)
•
Call of OB82 with the message 0RGXOH HUURU
(incoming event; diagnostic address of the DP slave assigned
to the DP master; Variable OB82_MDL_STOP=1)
•
Call of OB82 with the message 0RGXOH 2.
(outgoing event; diagnostic address of the DP-Slave assigned
to the DP master; Variable OB82_MDL_STOP=0)
Evaluation in the DP master of RUN to STOP transitions by the DP slave
,Q WKH '3 PDVWHU
S7-300 Automation System, Hardware and Installation: CPU 312IFM - 318-2 DP
:KDW KDSSHQV LQ WKH '3 VODYH"
,Q WKH '3 VODYH &38 ['3
Diagnostic addresses: (Example)
Slave diagnostic address =
Master diagnostic address = irrelevant
← CPU: RUN -> STOP
The CPU generates a DP slave diagnostics
message frame
A5E00203919-01