configuration of hardware interrupt block

Hello,

In the program of our filler I find a hw interrupt block OB40, so I check the HW configuration of the DI module and I find the attached picture with enabling ''process Alarm" and enabling positive edge of input 0-1.

In this DI module we have only 2 connected input E0.2 and E1.4.

I want to understand how and when OB40 is called? on postive edge of E0.2 or E1.4 ?

PISCEAN 2010

Please refer What is a hardware interrupt and how do they work in the S7-300 system? FAQ which may help you.

 Thank you for your reply, I read this link before and I read many topics talking about hardware interrupt, but I don't understand how it works regarding my previous attachment?

Your DI module6ES7321-7BH00-0AB0 is interrupt capable that is you can set up interrupts to be triggered on rising or falling edges of inputs. I couldn't find the exact module on my TIA15.1 and I found its cousin the -7BH01 which seems to have the same features.

Edit: In your picture the "Hardware Interrupt" option is selected and below it rising edge is selected for channel 0-1 and  no other interrupts. I have to have a second look at it!

Here's an extract:

"Program each channel group separately. The parameters can be changed at any time (in
RUN mode in the user program)."

Kal.A

Here's an extract:

"Program each channel group separately. The parameters can be changed at any time (in
RUN mode in the user program)."

 Thank you for your help, 

I don't find my needs in this attachment, sorry I want simply knowing how inputs I0.2 and I1.4 trigger OB40 regarding the configuration in first attachment?

Here's one more attachment.

The parameters of the module can be changed in runtime, i.e. in your user program. That is done by writing the relevant record with the modified parameters to the module. So if you look closely in your program you should find SFC57 (if not may be SFC55) and you should also find code that changes the channel parameters.

The information is scattered across several manuals and you will need to dig-in further.

It's got me interested enough that I intend to look deeper into it later. If you need a quicker answer I would read more in the manual as it looks like the only way to address the module is to write records to it using some SFC of which their seem to be a few that may do the job.