
■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ ■
▼
TargetLink Data Types Application Note September 2004
5
▲
■■■■■■■■■■I
▲■
Block-specific Scaling Parameters
After compiled data types have been evaluated and TargetLink types
set accordingly, scaling parameters are retrieved on a block-by-block
basis. This is possible without compiling the model, for both model
and library conversion. However, if a block’s output inherits, for
example, an integer data type, this method will fail to detect it.
Additionally, since Simulink blocks do not have explicit scaling
parameters in Simulink 4, this step is confined to version 5 and later.
This is the second step in the conversion process. Thus, if model
compilation is not possible (for libraries), or if no Fixed-Point license is
available, Simulink scaling parameters will be mapped to TargetLink
scaling parameters during this step.
In Simulink 6, more blocks support block-specific types than in
Simulink 5. The overall number will most likely increase in future
Simulink versions.
The following table shows which Simulink block types support fixed-
point data types. Some blocks additionally support scaling parameters,
i.e., the output can be scaled. Output scaling is also taken into account
during conversion. The Simulink properties which define the fixed-
point settings are listed in the third column.
Block Type Ver. Simulink properties Scaling Remarks
DataStoreMemory 6.0+ DataType
OutDataType
OutScaling
Yes
Gain 5.0+ ParameterDataTypeMode
ParameterDataType
ParameterScalingMode
ParameterScaling
OutDataTypeMode
OutDataType
OutScaling
SaturateOnIntegerOverflow
Yes Both output
and gain can
be typed
Constant 5.0+ OutDataTypeMode
OutDataType
OutScaling
ConRadixGroup
Yes
Komentáře k této Příručce