Parameter Mapping
In case an ASCET class or module containing imported parameters is used within an AUTOSAR software component, all imported parameters must be mapped to semantically equivalent AUTOSAR elements.
For this purpose, ASCET provides a special editor in the Parameter Mapping view of the software component editor.
In that editor, imported parameters can be mapped to AUTOSAR elements according to the following rules:
Parameters can be mapped as shown in the following table.
mapping
scalar parameters
to scalar elements of calibration interfaces
to scalar elements of complex elements (records) in calibration interfaces
composite parameters
(arrays, matrices)
to composite elements of calibration interfaces
to composite elements of complex elements (records) in calibration interfaces
complex parameters
(records)
to complex elements (records) in calibration interfaces
to complex elements of complex elements (records) in calibration interfaces
A scalar parameter must be mapped to a scalar element of compatible type.
parameter type
AUTOSAR element type
Continuous (cont)
cont / limitInt / wrapInt / sdisc / udisc
Limited Integer (limitInt)
limitInt / wrapInt
Wrap-Around Integer (wrapInt)
wrapInt
Signed Discrete (sdisc)
cont / limitInt / wrapInt / sdisc / udisc
Unsigned Discrete (udisc)
cont / limitInt / wrapInt / sdisc / udisc
Logic (log)
log
Enumeration (enum)
Enumeration of the same type
If you map a scalar parameter to an element of compatible, but non-identical type, a warning WMdl635 is issued during code generation.
If you map a scalar parameter to an element of incompatible type, an error MMdl635 is issued during code generation.
A composite parameter (array, matrix) must be mapped to an array/matrix of identical size, data type and implementation.
Otherwise, the mapping is indicated as invalid, and an error MMdl635 is issued during code generation.
A complex parameter must be mapped to a record of identical type and implementation.
Otherwise, the mapping is indicated as invalid, and an error MMdl635 is issued during code generation.
You can
Export message/parameter mappings
Import message/parameter mappings
See also