Triggering A Hardware Interrupt; Triggering An Insert/Remove Module Interrupt; Alarms; Diagnostics Alarms - Siemens SIMATIC ET 200AL Manual

Interrupts, error messages, diagnostics and system alarms

5.3 Alarms

5.2.3

Triggering a hardware interrupt

During a hardware interrupt, the CPU interrupts the processing of the user program and
processes the hardware interrupt OB (e.g., 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)
Avoid creating hardware interrupts cyclically.
If the hardware interrupt load is too high, hardware interrupts can get lost depending on the
number of I/O modules and the communication load.
5.2.4

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 OB.
The pull/plug OB (OB 83) is also triggered for all subsequent I/O modules, because the
ET-Connection and/or the power supply is interrupted.
5.3 Alarms
5.3.1

Diagnostics alarms

Actions after a diagnostics alarm
There can be more than one diagnostic alarm at a given time. Actions initiated by
diagnostics alarms:
● The ERROR LED of the interface module flashes.
● Diagnostic data is reported as diagnostics interrupts to the CPU of the IO controller and
can be read via data records.
● Incoming diagnostics alarms are saved to the diagnostics buffer of the I/O controller.
● OB 82 is called. If OB 82 is not available, the I/O controller goes into STOP mode.
You can find more information on this topic in the STEP 7 online help.
30
Interface module IM 157-1 PN (6ES7157-1AB00-0AB0)
Manual, 12/2016, A5E32347036-AD