image thumbnail
from Motion Control Demo by Paul Lambrechts
Model Based Design Demonstration Based on a Motion Control Case Study

DMC_system_demo_subsystems.html
RTW Report - Nonvirtual subsystems in DMC_system_demo Nonvirtual subsystems in DMC_system_demo

Code Mapping

The following table:

  • provides a mapping from the non-virtual subsystems in the model to functions or Reused functions in the generated code and
  • notes exceptions that caused some non-virtual subsystems to not reuse code even though they were assigned a Reuse Setting ('RTW System Code' entry on the Subsystem Block Dialog) of 'Auto' or 'Reused Function'.

SubsystemReuse SettingReuse OutcomeOutcome Diagnostic
<S17>AutoReusable Function(S17)normal
<S18>AutoReusable Function(S17)normal
<S27>AutoFunction(S27)normal
<S16>AutoInlinenormal
<S20>AutoInlinenormal
<S30>AutoInlinenormal
<S29>AutoInlinenormal
<S31>AutoInlinenormal
<S23>AutoInlinenormal


Code Reuse Exceptions

The following section provides details on each exception that caused a non-virtual subsystem with a Reuse Setting of

  • 'Auto' to become an inlined code segment,
  • 'Auto' to become a non-reusable function without arguments, or
  • 'Reused Function' to become a non-reusable function without arguments.
Note: This section does not report graphically identical non-virtual subsystems marked as 'Auto' that were not reused due to differences in their functional properties (such as dimensions, datatypes, work vectors, parameters, etc.). You may identify reasons for non-reuse in such cases by inspecting the differences in the functional attributes of the subsystems in the model or in the inlined generated code.

No reuse exceptions in model

Contact us at files@mathworks.com