IN, IN_OUT, OUT paramters

Hi all during my S5 S7 conversions I was going throught the threads and curious about the discussions on the S5 declarations in and out that are used in the FB with load and transfer regardless of the parameter type. Now during compilation of those blocks I did not have any warnings or errors in the S7 converter howeverthe declarations are exactly defined in the Step 7 as they are inS5. Now this sounds scary but I have over500 FC's with this issue, (as per example below)so before I would go and change them all from IN orOUT to IN_OUT I wanted to make sure that this is the right way.I found also that generating a source file from thoseblocks and modifying thesource file and recompiling would be the moststraight forward method and of course updating the calls to those blocks later by doing a block consistancy check.

Thanks

FUNCTION "TRIGGER" : VOID
TITLE =
AUTHOR : _97092
NAME : TRIGGER
VERSION : 0.0

VAR_INPUT
UHR : WORD ;// UHR
ZEIT : INT ;// ZEIT
DB_S : WORD ;// DB-S
END_VAR
VAR_OUTPUT
LIFE : WORD ;// LIFE
END_VAR
VAR_TEMP
conv_akku1 : DWORD ;
conv_index : WORD ;
RS5 : INT ;
END_VAR
BEGIN
NETWORK
TITLE =START-TRIGGER FOR DATATRANS.TO CP(FX181)

L "ACT_CYCL_TIME";
L 10;
/I ;
T #RS5;

O "F30.1 H1-BUS ANZW SEND"; // send-job ist active
O "F29.7 H1-BUS";
R "F29.4 H1-BUS"; // reset trigger
BEC ;
//; // --------------------------------
O "F28.1 H1-BUS"; // trigger after connection is o.k.
O "F29.2 H1-BUS"; // trigger if interface overload
O "F29.3 H1-BUS"; // trigger from extern
O "F30.3 H1-BUS ANZW SEND"; // send-job ready with fault
JC M001;
//; // --------------------------------
L 0;
L #ZEIT;
>I ; // 0 > parametered time
JC M002;
L #RS5; // cycletime counting L RS 5 shadi
SLW 8;
SRW 8;
ENT ;
L #UHR;
+I ;
T #UHR;
<=I ; // parametered time <= run-time
JC M001;
//; // ********************************
M002: R "F29.4 H1-BUS"; // NO TRIGGER :
BEU ;
//; // ********************************
M001: L 0; // TRIGGER :
T #UHR; // reset timer
AN "F29.4 H1-BUS";
S "F29.4 H1-BUS";
JC M003;
BEU ; // --------------------------------
M003: L #DB_S; // in case of positive edge at
T MW 240; // F 29.4
L 0;
L MB 240;
==I ;
JC M004;
L 1;
<>I ;
BEC ;

T #conv_akku1;
L MB 241;
T #conv_index;
TAK ;
L #conv_akku1;
OPN DB [#conv_index];
// *** Warning in Line 22696 Note new block numbering.
JU M005;
M004: NOP 0;

T #conv_akku1;
L MB 241;
T #conv_index;
TAK ;
L #conv_akku1;
OPN DB [#conv_index];
M005: L #LIFE;
L 1;
+I ;
L 0;
<I ; // life-counter < 0 (overflow)
JC M006; // then reset to 0
TAK ; // else increment 1
M006: T #LIFE;
//; // ********************************
// end

END_FUNCTION

Hi

Goign through your code I see no reason why you would want to change IN or OUTs to IN_OUT. Atleast in this function there is no such requirement. Basically you need to convert IN_OUT those IN values which may change during the function execution and this change needs to reflect in the subsequent logic. Normally such logics are more when the signals are coming from HMI or other external operator interfaces (justas example..there maybe many situation where such signals are required,

Krish