MATLAB SIMULINK FIXED POINT 6 Bedienungsanleitung PDF herunterladen (Seite 9)

■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ ■

▼

TargetLink Data Types Application Note September 2004

▲

■■■■■■■■■■I

▲■

■■■■■■■■■■■■■■

■ For vectorized variables, TargetLink LSB and offset values can be

set for each vector element individually, while in Simulink the

associated parameters are scalars which apply to all vector

elements.

■ Saturation on integer overflow in Simulink cannot be specified for

the lower and upper bounds separately, as is possible in

TargetLink.

To resolve these issues, the following approach has been

implemented:

■ During Simulink-to-TargetLink conversion, all data type and scaling

related parameters are saved to the replacing TargetLink block.

This applies only to Simulink 5 and 6.

The saved Simulink scaling parameters are retrieved from the

TargetLink blocks during TargetLink-to-Simulink conversion. In many

cases, there are none, either because the block concerned does not

originate from a conversion (but was directly copied from TargetLink’s

blockset), or because the conversion was done with Simulink 4. If

there are no scaling parameters, no such parameters are written to the

Simulink block, which therefore has Simulink’s default settings for

scaling parameters. If there are any scaling parameters, the conversion

routine checks whether they correspond to the current TargetLink

parameters according to the table above. If they do, they are written

to the replacing Simulink block. This resolves most ambiguity

problems. If they do not, the table below applies.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Keine Kommentare

MATLAB SIMULINK FIXED POINT 6 Bedienungsanleitung Seite 9