Alarm, error and system messages
9.2 PROFINET IO
ET 200pro distributed I/O system
Operating Instructions, 03/2013, A5E00335544-08
219
9.2.2
Diagnostic messages of the electronic modules
Actions after a diagnostic message
Actions initiated by diagnostic messages:
●
The SF LED of the interface module is lit.
●
There can be more than one diagnostic message at the same time.
●
Diagnostic data are reported as diagnostic interrupts and can be read from data records.
●
Incoming diagnostic messages are saved to the diagnostic buffer of the I/O controller.
●
OB 82 is called. If OB 82 is not available, the I/O controller goes into STOP.
●
Acknowledgment of the diagnostic interrupt to enable new interrupts.
9.2.3
Evaluating interrupts of ET 200pro
Introduction
The I/O device generates interrupts as a reaction to specific error events. Interrupts are
evaluated based on the I/O controller used.
Evaluating interrupts with I/O controllers
The ET 200pro supports the following interrupts
●
Diagnostic interrupts
●
Process interrupts
●
Swapping interrupts
An interrupt automatically initiates execution of interrupt OBs in the CPU of the IO controller
(see
System Software for S7-300/S7-400
Programming Manual, under "Program design".
Information on the cause and class of the error is already available, based on the OB
number and start information.
Detailed information on the error event can be obtained in the error OB using SFB 54
RALRM (read additional interrupt information).
Triggering of a diagnostic interrupt
When an event (e.g. wire break) comes or goes, the module triggers a diagnostic interrupt if
"Enable: diagnostic interrupt" is set.
The CPU interrupts the user program and processes the diagnostics block OB 82. The
interrupt triggering event is logged in the start information of OB 82.
