Non-virtual subsystems in EV3Control_sil_sil_ec

1. Code Mapping [hide]

The following table:

  • provides a mapping from the non-virtual subsystems in the model to functions or reusable functions in the generated code and
  • notes exceptions that caused some non-virtual subsystems to not reuse code even though they were assigned a function packaging setting ('Function packaging' entry on the Subsystem Block Dialog) of 'Auto' or 'Reusable function'.

Subsystem Reuse Setting Reuse Outcome Outcome Diagnostic
<S23> Auto Reusable Function(S23) normal
<S22> Auto Reusable Function(S23) normal
<S13> Auto Inline normal
<S30> Auto Inline normal
<S32> Auto Inline normal
<S31> Auto Inline normal
<S28> Auto Inline normal
<S29> Auto Inline normal
<S19> Auto Inline normal
<S64> Auto Inline normal
<S50> Auto Inline normal
<S56> Auto Inline normal
<S47> Auto Inline normal
<S49> Auto Inline normal
<S65> Auto Inline normal
<S70> Auto Inline normal
<S72> Auto Inline normal
<S74> Auto Inline normal
<S77> Auto Inline normal
<S78> Auto Inline normal
<S80> Auto Inline normal
<S38> Auto Inline normal
<S85> Auto Inline normal
<S86> Auto Inline normal
<S87> Auto Inline normal
<S39> Auto Inline normal
<S91> Auto Inline normal
<S93> Auto Inline normal

2. Code Reuse Exceptions [hide]

The following section provides details on each exception that caused a non-virtual subsystem with a function packaging setting of

  • 'Auto' to become an inlined code segment,
  • 'Auto' to become a non-reusable function without arguments, or
  • 'Reusable 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 exception in model