Interrupts On The Dp Master; Evaluation Of Run To Stop Transitions In The Dp Master/Dp Slave - Siemens SIMATIC S7-300 Hardware And Installation Manual

Hide thumbs Also See for SIMATIC S7-300:
Table of Contents

Advertisement

Testing functions, Diagnostics and Fault Elimination
Evaluation in the user program
The table below shows you how you can, for example, evaluate RUN-STOP
transitions of the DP master in the DP slave (see also the previous table).
Table 11-12 Evaluation of RUN to STOP transitions in the DP master/DP slave
In the DP master
Diagnostic addresses: (Example)
Master diagnostic address =1023
Slave diagnostic address in the master
system=1022
CPU: RUN " STOP

11.6.2 Interrupts on the DP master

Interrupts on S7/M7 DP masters
If the CPU 31x-2 is used as the DP slave, you can trigger a process interrupt on
the DP master from the user program.
When you call SFC 7 "DP_PRAL", you trigger an OB 40 in the user program on the
DP master. The SFC 7 allows you to forward interrupt information to the DP master
in a double word. This information can then be evaluated in the
OB40_POINT_ADDR variable in the OB 40. The interrupt information can be freely
programmed as required. The System software for S7-300/400 - System and
Standard Functions - Reference Manual contains a detailed description of SFC 7
"DP_PRAL".
11-22
In the DP slave
Diagnostic addresses: (Example)
Slave diagnostic address =422
Master diagnostic address = irrelevant
7KH &38 FDOOV 2%  ZLWK WKH IROORZLQJ
information:
OB 82_MDL_ADDR:=422
OB82_EV_CLASS:=B#16#39 (incoming
event)
OB82_MDL_DEFECT: = Module error
Tip: The CPU diagnostic buffer also
contains this information
S7-300 Programmable Controller Hardware and Installation
A5E00105492-02

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents