Actions after diagnostic message
Each diagnostic message leads to the following actions:
• In S7 or DPV1 mode, diagnoses are reported as diagnostic interrupts.
• After a diagnostic message this is
– entered in the diagnostic frame as diagnostic interrupt block (always only one interrupt)
– stored in the diagnostic buer of the CPU
– entered in the channel related diagnostics
• The MT or ERR LED lights up on the IM 152-1PN interface module.
• The OB82 is called. If there is no OB82, the CPU goes to STOP operating state.
• Acknowledgment of the diagnostic interrupt (after which new interrupt is possible)
Causes of Error and Troubleshooting
The causes of errors and remedial measures of the diagnostic messages are described in the
section "Diagnostics of the IM 152-1PN (Page 193)".
7.12.3 Evaluating interrupts of the ET 200iSP by the CPU with PROFINET
Introduction
The interface module triggers interrupts for specic errors. The interrupt evaluation varies
depending on the CPU used.
Evaluate interrupts using the CPU
Requirements: You have congured the ET 200iSP with the engineering tool STEP 7; i.e.
interrupts are only supported if you integrate the ET 200iSP as follows:
• IO device
• S7 DP device
• DPV1 device
In case of an interrupt, interrupt OBs run automatically in the CPU (see programming manual
System software for S7-300/S7-400, program draft (
http://
support.automation.siemens.com/WW/view/en/1136533)).
Triggering of a diagnostic interrupt
With an incoming or outgoing event (wire break, for example) the module triggers a diagnostic
interrupt upon "Release: Diagnostic Interrupt".
The CPU interrupts the processing of the user program and processes the diagnostics block
OB82. The event that led to the triggering of the interrupt is entered in the start information of
the OB82.
Commissioning and Diagnostics
7.12 Diagnostics with STEP 7 with PROFINET
ET 200iSP
Operating Instructions, 11/2022, A5E00247483-AK 191
To Next Page
Loading...
Need help?
General
