● After a diagnostic message this is
– entered in the diagnostic frame as diagnostic interrupt block (always only one alarm)
– stored in the diagnostics buffer of the CPU
– entered in the channel related diagnostics
● The SF LED on the IM 152 is lit.
● The OB82 is called. If there is no OB82, the CPU goes to STOP operating state.
● Acknowledgement of the diagnostic interrupt (after which new alarm is possible)
Actions after a diagnostic message in DPV0 operation
The error is entered in the diagnostic frame in the channel-related diagnostics:
● The SF LED on the IM 152 is lit.
● Several diagnostic messages are possible at the same time.
Causes of Error and Troubleshooting
The causes of error and the troubleshooting of the diagnostic messages are described in the
Chapter "Channel-related diagnostics (Page 165)".
6.8.4
Evaluating interrupts from the ET 200iSP (S7-DP slave/ DPV1 slave)
Introduction
Certain errors cause the DP slave to trigger an interrupt. Depending on the DP master you are
using, the evaluation of the interrupt follows different procedures.
Evaluating Interrupts with an S7 DP Master or DPV1 Master
Requirements: You have configured the ET 200iSP with STEP 7 (Version 5.3 Service Pack 1
or higher), i.e., interrupts are only supported if you integrate the ET 200iSP as an S7-DP slave
or DPV1 slave.
When interrupts are generated the CPU of the DP master automatically calls the interrupt OBs
(see Programming Manual System software for S7-300/S7-400, program draft (
support.automation.siemens.com/WW/view/en/1136533
Evaluating interrupts with other DP master
If you operate ET 200iSP with a different DP master or as DP standard slave, no interrupts
are generated.
Commissioning and Diagnostics
6.8 Diagnostics with STEP 7
ET 200iSP
Operating Instructions, 11/2017, A5E00247483-07
157