Chapter 5
Generated Code Architecture
©
National Instruments Corporation
5-15
foo_2_u.foo_1 = U->t_l_1;
foo(&foo_2_u, &foo_2_y, &foo_2_i);
foo_2_1 = foo_2_y.foo_2_1;
iinfo[0] = foo_2_i.iinfo[0];
if( iinfo[0] != 0 ) {
foo_2_i.iinfo[0] = 0; goto EXEC_ERROR;
}
/* ---------------------------- Procedure SuperBlock */
/* {foo.12} */
foo_12_u.foo_1 = foo_2_1;
foo(&foo_12_u, &foo_12_y, &foo_12_i);
Y->foo_12_1 = foo_12_y.foo_2_1;
iinfo[0] = foo_12_i.iinfo[0];
if( iinfo[0] != 0 ) {
foo_12_i.iinfo[0] = 0; goto EXEC_ERROR;
}
if(iinfo[1]) {
SUBSYS_INIT[1] = FALSE;
iinfo[1] = 0;
}
return;
EXEC_ERROR: ERROR_FLAG[1] = iinfo[0];
iinfo[0]=0;
}
Procedure Arguments
All or some of the following arguments need to be passed for each call to
the procedure in the following order.
U, Y, S, and I
These arguments are pointers to structures reflecting the procedure’s
inputs, outputs, states (including nested procedure states) and
informational data (including nested procedure informational data) used
for communication with the user application or simulation engine.
The inputs to the procedure are provided by the argument U, a pointer to
a structure named
_
procedure name_u
. This structure is composed of
mixed data-typed variables reflecting each procedure input signal and type.
The outputs to the procedure are provided by the argument Y, a pointer to
a structure named
_
procedure name_y
. This structure is composed of