Siemens SIMATIC PCS 7 CPU 410-5H System Manual page 234

Supplementary information
15.2 Supplementary information on diagnostics of CPU 410-5H as PROFIBUS DP master
Event detection
The following table shows how the CPU 41xH in DP master mode detects operating state
changes on a DP slave or interruptions of the data transfer.
Table 15- 2 Event detection of the CPU 41xH as a DP master
Event
Bus interruption due to short-circuit or
disconnection of the connector
DP slave: RUN → STOP
DP slave: STOP → RUN
Evaluation in the user program
The table below shows you how to evaluate RUN-STOP changes of the DP slave on the DP
master. Also refer to the previous table.
On the DP master
Example of diagnostic addresses:
•
Master diagnostics address=1023
Slave diagnostics address in master
system=1022
The CPU calls OB 82 with the following information, for example:
OB 82_MDL_ADDR:=1022
•
OB82_EV_CLASS:=B#16#39
•
As incoming event
OB82_MDL_DEFECT:=module error
•
The CPU diagnostic buffer also contains this information.
Your user program should also be set up to read the diagnostic
data of the DP slave using SFC 13 "DPNRM_DG".
Use SFB 54 in the DPV1 environment. It outputs the full interrupt
information.
234
What happens in the DP master?
OB 86 is called with the message Station failure as an incoming event; diag-
•
nostics address of the DP slave assigned to the DP master
With I/O access: Call of OB 122, I/O area access error
•
OB 82 is called with the message Module error as incoming event; diagnostic
•
address of the DP slave assigned to the DP master; variable
OB82_MDL_STOP=1
OB 82 is called with the message Module OK as incoming event; diagnostic
•
address of the DP slave assigned to the DP master; variable
OB82_MDL_STOP=0
On the DP slave (CPU 41x)
Example of diagnostic addresses:
•
Slave diagnostics address=422
Master diagnostics address=irrelevant
CPU: RUN → STOP
CPU generates a DP slave diagnostics frame.
CPU 410-5H Process Automation
System Manual, 09/2014, A5E31622160-AB