22.07.2013 Views

II - DCE FEL ČVUT v Praze

II - DCE FEL ČVUT v Praze

II - DCE FEL ČVUT v Praze

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SIMATIC S7 Ex Digital Modules<br />

Interrupts<br />

Parameterizing<br />

interrupts<br />

Default setting<br />

Diagnostic<br />

interrupt<br />

Hardware interrupt<br />

Hardware interrupt<br />

lost<br />

2-12<br />

The interrupt characteristics of the SM 321; DI 4 x NAMUR are described in<br />

the following.<br />

In principle, a differentiation is made between the following interrupts:<br />

Diagnostic interrupt<br />

Hardware interrupt<br />

The interrupts are parameterized with STEP 7.<br />

The interrupts are inhibited by way of default.<br />

If enabled, the module triggers a diagnostic interrupt when an fault comes or<br />

goes (e.g. wire break or short to M). Diagnostic functions inhibited by<br />

parameterization cannot trigger an interrupt. The CPU interrupts processing<br />

of the user program or low-priority classes and processes the diagnostic<br />

interrupt module (OB 82).<br />

Depending on the parameterization, the module can trigger a hardware<br />

interrupt for every channel optionally at leading, trailing or both edges of a<br />

signal change. You can determine which of the channels has triggered the<br />

interrupt from the local data of the OB 40 in the user program (refer to<br />

/235/).<br />

Active hardware interrupts trigger interrupt processing (OB 40) in the CPU,<br />

consequently the CPU interrupts processing of the user program or<br />

low-priority classes. If there are no higher priority classes pending<br />

processing, the stored interrupts (of all modules) are processed one after the<br />

other corresponding to the order in which they occurred.<br />

If an event occurred in one channel (edge change), this event is stored in the<br />

hardware interrupt register and a hardware interrupt is triggered. If a further<br />

event occurs on this channel before the hardware interrupt has been<br />

acknowledged by the CPU (OB 40 run) this event will be lost. A diagnostic<br />

interrupt ”hardware interrupt lost” is triggered in this case. The diagnostic<br />

interrupt enable must be active for this purpose.<br />

Further events on this channel are then no longer registered until interrupt<br />

processing is completed for this channel.<br />

I/O Modules with Intrinsically-Safe Signals<br />

C79000-G7076-C152-04

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!