S5 to S7 Convertion - Hardware Interrupts

Hi all,

I'm currently converting a program for and old S5-115U CPU 994B to S7-1500. The S5 came with the hardware interrupt input module 434-7LA12.

I've already had a read of the manual for that module and found out that it occupies two bytes of inputs and two bytes of outputs.

First output (eg. IB8) gives the actual status of inputs and second byte (eg. IB9) gives the information which input triggered the interrupt.

Configuration of inputs in my project is as follows:

I8.0 / I9.0 - Positive Edge

I8.1 / I9.1 - Positive Edge

I8.2 / I9.2 - Negative Edge

I8.3 / I9.3 - Negative Edge

Inputs I8.4 - I8.7 not used

Please see the fragment of the hardware interrupt program below:

I mean how it is possible to have a byte telling me which input triggered an interrupt?

In my case hardware interrupt is called by input byte IW47.

So far in the OB40 instead instructions L PY9 T IB9 L PY8 T IB8,  I added following

L PIW46

T MW400

L IW46

T MW402

AN    "M401.1"

AN    "M403.2"

JC    M001

CALL  FC 214

A     "M403.2"

S     "M4.5"

JCN   X011

CALL  FC 103

X011: NOP 0

A     "M403.2"

JCN   X012

CALL  FC102

X012: NOP 0

A     "M33.0"

AN    "T42"

AN    "M98.6"

=     "Q39.3"

...

and then M401.0 - M401.7 are inputs which triggered interrupt with positive edge and M403.0 - M403.7 are inputs which triggered interrupt with negative edge.

Is that correct?

I might understand it wrong, but I think you should use the information in the header from ie. OB40. (LADDR and IChannel)

You could use OB40 for Rissing and OB41 for Falling edge

Header in OB:

LADDR HW_IO Hardware identifier of the module that triggers the hardware interrupt

USI WORD Identifier for future extensions (not user-relevant)

IChannel USINT Number of the channel that triggered the hardware interrupt

EventType BYTE Identifier for the event type to which the event that triggered the interrupt belongs (e.g., rising edge)

This identifier can be found in the description of the respective module.

 Thank you SMJE for your answer.

SMJE

(...)

You could use OB40 for Rissing and OB41 for Falling edge

(...)

 The problem is, I probably cannot use two separate OB's for this interrupt routine. Logic in the S5 interrupt block is looking on all inputs that triggers it, both positive and negative edge. And I would like to keep it the same.

SMJE

I might understand it wrong, but I think you should use the information in the header from ie. OB40. (LADDR and IChannel)

(...)

Header in OB:

LADDR HW_IO Hardware identifier of the module that triggers the hardware interrupt

USI WORD Identifier for future extensions (not user-relevant)

IChannel USINT Number of the channel that triggered the hardware interrupt

EventType BYTE Identifier for the event type to which the event that triggered the interrupt belongs (e.g., rising edge)

This identifier can be found in the description of the respective module.

I know what you mean. I found this variable in the header of OB called POINT_ADDR (DWord) and noticed that 3rd byte gives the channel number which triggered an interrupt and 4th byte gives the type - positive or negative.

I actually tested my solution and it gives me what I expect it to do. When an interrupt is triggered by the input configured to positive edge, scanning the peripheral input word/byte shows the status of inputs at the time of trigger and when negative edge input triggers the interrupt, scanning the process image input word/byte gives the status before the interrupt was triggered, so all negative edge inputs which might trigger it, were active.

Just to let know anybody who would be doing similar conversion in the future...

In the header of the OB40 there is a variable called POINT_ADDR (DWord) and this is the one to be used in my case. I was actually wrong about all this PIW and IW status.

My solution below:

New question published by AutoGen_8722787 is split to a separate thread with the subject Need a suitable S7 300 module for S5.

Best regards
Jen_Moderator