Evaluating The Interrupts Of The Et 200S - Siemens Simatic ET 200S Operating Instructions Manual

Distributed i/o system
Hide thumbs Also See for Simatic ET 200S:
Table of Contents

Advertisement

Alarm, error and system messages
8.2 Alarm, error and system messages on PROFINET IO
Causes of faults and corrective measures
The causes of faults and corrective measures for the diagnosis messages are described in
this manual in the chapter entitled "Channel diagnostics" under "Interrupt, cause and system
messages to the PROFIBUS DP".
8.2.3

Evaluating the interrupts of the ET 200S

Introduction
Interrupts are triggered by the IO device when certain errors occur. The Interrupt evaluation
occurs dependent on the IO controller used.
Evaluating interrupts with IO controller
The ET 200S supports the following interrupts
• Diagnostic interrupts
• Process interrupts
• Insert/remove module interrupts
In case of an interrupt, interrupt OBs are automatically executed in the CPU of the IO
controller (see information on program design in the
programming manual).
You can obtain information on the cause of the error and the error type using the OB number
and the start information.
You can obtain detailed information on the error event in the error OB with SFB 54 RALRM
(read supplementary interrupt information).
Triggering of a diagnostic interrupt
When an incoming or outgoing event (e. g. wire break) is registered , the module triggers a
diagnostic interrupt: if "Enable: Diagnostic interrupt" is set.
The CPU interrupts the processing of the user program and processes the OB 82
diagnostics block. The event that caused the interrupt to be triggered is entered in the start
information of OB 82.
Triggering of a process interrupt
The CPU interrupts processing of the user program and processes the OB 40 diagnostics
module. The event that caused the interrupt to be triggered is entered in the start information
of OB 40.
Triggering of an insert/remove-module interrupt
The CPU interrupts processing of the user program and processes OB 83 diagnostic block.
The event that caused the interrupt to be triggered is entered in the start information of
OB 83.
8-54
System Software for S7-300/ S7-400
Operating Instructions, 12/2005, A5E00515771-03
ET 200S

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents