Learn more about Real-Time Workshop Embedded Coder

Nonvirtual Subsystem Modular Function Code Limitations

The nonvirtual subsystem option Function with separate data has the following limitations:

• The Function with separate data option is available only in ERT-based Simulink models (requires a Real-Time Workshop Embedded Coder license).

• The nonvirtual subsystem to which the option is applied cannot have multiple sample times or continuous sample times; that is, the subsystem must be single-rate with a discrete sample time.

• The nonvirtual subsystem cannot contain continuous states.

• The nonvirtual subsystem cannot output function call signals.

• The nonvirtual subsystem cannot contain noninlined S-functions.

• The generated files for the nonvirtual subsystem will reference model-wide header files, such as model.h and model_private.h.

• The Function with separate data option is incompatible with the GRT compatible call interface option, located on the Real-Time Workshop/Interface pane of the Configuration Parameters dialog box. Selecting both will generate an error.

• The Function with separate data option is incompatible with the Generate reusable code option (Real-Time Workshop/Interface pane). Selecting both will generate an error.

• Although the model_initialize function generated for a model containing a nonvirtual subsystem that uses the Function with separate data option may have a firstTime argument, the argument is not used. Thus, you cannot call model_initialize at a time greater than start time, for example, to reset block states. To suppress inclusion of the firstTime flag in the model_initialize function definition, set the model configuration parameter IncludeERTFirstTime to off.

Examples of Modular Function Code for Nonvirtual Subsystems

Controlling Generation of Function Prototypes

© 1984-2009- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS