Diagnostics Of Dp Cpus Operating As Dp Slave - Siemens SIMATIC S7-300 Hardware And Installation Manual

Testing functions, Diagnostics and Fault Elimination
Event
Bus failure interrupt
(short-circuit,
connector unplugged)
DP slave: RUN →
STOP
DP slave: STOP →
RUN
Evaluation in the user program
The table below shows how you can, for example, evaluate RUN to STOP
transitions of the DP slave in the DP master.
Table 10-9
Diagnostic addresses: (Example)
Master diagnostic address =1023
Slave diagnostic address =1022
The CPU calls OB 82 with the following
information:
•
OB 82_MDL_ADDR:=1022
•
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.
10.6.2

Diagnostics of DP CPUs operating as DP Slave

Reading Slave Diagnostic Data
The slave diagnostic data is compliant with EN 50170, Volume 2, PROFIBUS.
Depending on the DP master, diagnostic data for all DP slaves conforming to
standard can be read with STEP 7 .
10-14
•
Call of OB 86 with the message Station failure (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 Module error
(incoming event; diagnostic address of the DP slave assigned
to the DP master; Variable OB82_MDL_STOP=1)
•
Call of OB82 with the message Module OK
(outgoing event; diagnostic address of the DP-Slave assigned
to the DP master; Variable OB82_MDL_STOP=0)
Evaluating RUN to STOP transitions of the DP slave in the DP master
In the DP Master
S7-300 Programmable Controller Hardware and Installation
What happens in the DP Slave?
In the DP Slave (CPU 31x-2DP)
Diagnostic addresses: (Example)
Slave diagnostic address =422
Master diagnostic address = irrelevant
← CPU: RUN -> STOP
The CPU generates a DP slave diagnostics
message frame
A5E00105492-01