7HVWLQJ)XQFWLRQV'LDJQRVWLFVDQG)DXOW(OLPLQDWLRQ
S7-300 Automation System, Hardware and Installation: CPU 31xC and CPU 31x
11-14 A5E00105492-03
(YHQWUHFRJQLWLRQ
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 Event recognition by CPUs 31x-2 as the DP master
(YHQW :KDWKDSSHQVLQWKH'3VODYH"
Bus failure interrupt
(short-circuit,
connector unplugged)
• Calls OB86 with the message 6WDWLRQIDLOXUH(incoming
event; diagnostic address of Slot 0 of the DP slave that is
assigned to the DP master)
• with I/O access: Call of OB122 (I/O access error)
DP slave: RUN →
STOP
• Call of OB82 with the message 0RGXOHHUURU
(incoming event; diagnostic address of Slot 2 of the DP slave
that is assigned to the DP master; Variable
OB82_MDL_STOP=1)
DP slave: STOP →
RUN
• Call of OB82 with the message 0RGXOH2.
(outgoing event; diagnostic address of Slot 2 of the DP slave
that is assigned to the DP master; Variable
OB82_MDL_STOP=0)
(YDOXDWLRQLQWKHXVHUSURJUDP
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 Evaluation in the DP master of RUN to STOP transitions by the DP slave
,QWKH'3PDVWHU ,QWKH'3VODYH&38['3
Diagnostic addresses: (Example)
Master diagnostic address =
Slave diagnostic address =
(Slot 0 of slave)
(Diagnostic) address for "Slot 2"=
(Slot 2 of slave)
Diagnostic addresses: (Example)
Slave diagnostic address =
Master diagnostic address = irrelevant
The CPU calls OB82 with the following
information:
• OB82_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
SFC 13 "DPNRM_DG" for reading out DP
slave diagnostic data.
← CPU: RUN -> STOP
The CPU generates a DP slave
diagnostics message frame
To Next Page
Loading...
Need help?
General
