Internal Access – Message Mapping View
This part of the Message Mapping view is used to map ASCET messages to AUTOSAR interrunnable variables.
Top Bar
information field
Shows whether message mapping is complete (
), incomplete (
), or contains invalid mappings (
). Update
Updates the instances of the SenderReceiver interfaces, records, classes and modules, i.e. imports changes in these components into the SWC
. Auto-Mapping
This button maps all unmapped messages to scalar interrunnable variables or elements of Record interrunnable variables with identical type and names that match the pattern in the combo box.
combo box for auto-mapping pattern
In this combo box, you determine the pattern used for automatic mapping. See Automatic Mapping for details.

Opens the ASCET options window in the Appearance\Editors\Software Component node. In that node, you can adjust the patterns available for automatic mapping.
/ 
Shows (
) or hides (
) the upper table.
Upper Table
This column lists all unmapped messages from the SWC itself and all modules directly or indirectly used in the software component. The messages are displayed as follows:
exported or imported messages
<message>
local messages
self.<module>[.<nested module>...].<message>
input field and
button above the columnYou can enter a text string in the input field and then click
to filter the list of available messages by name. The filter is case-insensitive; it finds all messages whose names contain the text string.
properties filter above the columnOpens the Filter Criteria dialog window, which allows filtering the list by selected properties.
An active type filter is indicated by a green overlay icon on both filter buttons:

An active filter is indicated by a green overlay icon:
Click the button to remove the filter.This column lists all unmapped elements (scalar interrunnable variables, data elements of complex interrunnable variables, data elements of records in SenderReceiver interfaces) that are available for mapping. The elements are displayed as follows:
interrunnable variables
<element>
elements in complex interrunnable variables
<record>[.<nested record>...].<element>
Note
Complex elements of nested records (record A contains record B, which contains record C, etc.) used as interrunnable variables are not listed.
input field,
properties filter and
button above the columnThe same as in the Messages column.
Button
Maps a message selected in the Message column to an interrunnable variable selected in the Variables column.
Mapping field – Lower Table
input field,
properties filter and
button The same as in the Messages column in the upper table.
Messages column
This column lists all messages from the SWC itself and all modules directly or indirectly used in the software component.
icon column
This column contains icons that represent the mapping status.

The message is unmapped.

Mapping is valid: the message is mapped to a suitable interrunnable variable or SenderReceiver interface port.

Mapping is invalid, e.g., because the type of the interrunnable variable or port changed after mapping.
Variables column
This column shows the interrunnable variables or SenderReceiver interface ports mapped to the messages in the Messages column of the Mapped field. The elements are displayed as in the upper Variables column.
If no mapping exists (–––), the Messages column can be used to perform mapping. A double-click in a table cell opens a list of all suitable calibration parameters.
Unsaved changed mappings are indicated by
blue font.
The context menu options of the lower table are also available in the Mapping menu.
See also
