▲
■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
TargetLink Data Types Application Note September 2004
■
▼
16
■■■■■■■■■■■■■■■▼
TargetLink Stand-Alone Blockset
In TargetLink’s Stand-Alone Blockset, the blocks are basically just
masked Simulink blocks. Thus, their data type behavior generally
corresponds to Simulink. There are some details to note:
■ The TargetLink data type (output.type property) has no impact on
the signal type during MIL simulations. The
Cast output signal to
TargetLink type
feature is not supported.
■ Custom Code blocks behave identically in full-featured and stand-
alone mode (except that signal logging is generally not possible in
stand-alone mode).
■ TargetLink Inport and Outport blocks are always virtual. Their input
signals are simply fed through the output.
• The signal data type behavior of Index Search and Pre Look-up
Interpolation blocks is the same in full-featured and stand-
alone mode, except that in stand-alone mode, the
Cast output
signal to TargetLink type
feature is not supported.
Thus, the signal data type behavior in TargetLink stand-alone
mode does not exactly correspond to the signal data type
behavior in full-featured mode. It also does not correspond to
Simulink’s behavior , either. This might result in invalid models
after the mode has been switched.
Commenti su questo manuale