Interrupts, error messages, diagnostics and system alarms
5.2 Interrupts
Interface module IM 155-6 DP HF (6ES7155-6BA01-0CN0)
38 Manual, 10/2018, A5E03916550-AD
Evaluating interrupts of ET 200SP
Introduction
With certain process statuses/errors, the DP slave in each case creates an interrupt block
with the corresponding information in the diagnostics frame (DPV1 interrupt mechanism).
Regardless of this, the diagnostic status of the DP slave is displayed in the identifier-related
diagnostics, in the module status, and in the channel diagnostics.
The ET 200SP distributed I/O system supports the following interrupts:
● Diagnostic interrupts
● Hardware interrupts
● Insert/remove module interrupts
Triggering of a diagnostics interrupt
When an event comes or goes (e.g. wire break on a channel of an I/O module), the module
triggers a diagnostics interrupt if "Enable: diagnostic interrupt" is set.
The CPU interrupts user program execution and processes the diagnostic interrupt OB
(OB 82). The event that triggered the interrupt is entered in the start information of the
diagnostic interrupt OB.
Triggering a hardware interrupt
When a hardware interrupt occurs, the CPU interrupts execution of the user program and
processes the hardware interrupt OB, for example OB 40. The event that triggered the
interrupt is entered in the start information of the hardware interrupt OB.
Note
Diagnostics "Hardware interrupt lost" (from I/O module)
Do not use hardware interrupts for technological purposes (e.g., cyclical generation of
hardware interrupts).
pt load is too high, hardware interrupts can get lost depending on the
number of I/O modules and the communication load.
Triggering an insert/remove module interrupt
When an insert/remove module interrupt occurs, the CPU interrupts execution of the user
program and processes the insert/remove module interrupt OB (OB 83). The event that
triggered the interrupt is entered in the start information of the insert/remove module interrupt
OB.
To Next Page
Loading...
Need help?
General
