Accessing ASCET Messages

If your SWCClosed AUTOSAR software component (singular; plural is SWCs) uses one or more modules that contain ASCET messages, or if the SWC itself contains messages, these messages must be mapped to suitable interrunnable variables or ports of SenderReceiver interfaces.

Note

Since ASCET V6.4.6, mapping messages to elements of NVData interfaces is no longer possible.

Existing mappings of messages to elements of NVData interfaces must be converted to NV data mappings; see Mapping Conversion for details.

SWCs that contain messages can be exported only in AMD format V6.4.8 and higher. An AMD format V6.4.7 or lower will result in an export error.

  1. Include the necessary module(s) and SenderReceiver interface(s).
  2. Create the necessary message(s) in the SWC.
  3. Open the Message Mapping view and go to the desired tab.

    The Message Mapping view contains two tabs, Internal Access and External Access. In the former tab, you can map messages to interrunnable variables, in the latter tab, you can map messages to elements of SenderReceiver interfaces.

    The Messages column in the Mapping field lists all messages directly or indirectlyClosed  (i.e., inside included modules) used in the SWC. The Variables column in the Mapping field can be used to map the messages according to the rules given in Message Mapping.

  4. If necessary, open the Mapping menu and select Update to import changes in the modules and SenderReceiver interfaces into the SWC.
  5. If desired, filter the columns.
  6. To use automatic mapping, proceed Closedas follows.

    1. In the combo box, enter or select a pattern for auto-mapping.
    2. Do one of the following:

      • Click the Auto-Mapping button.
      • Open the Mapping menu and select Auto-Mapping.
      • Right-click in the Message Mapping view and select Auto-Mapping from the context menu.

      Messages and interrunnable variables or SenderReceiver interface elements with matching element name and type are mapped. The results are shown in the Mapping field.

      A mapped AUTOSAR element is removed from the Variables column of the upper table.

      In the Internal Access tab, a mapped message is removed from the Messages column of the upper table.

      In the External Access tab, a mapped Receive message is removed from the Messages column of the upper table. Mapped Send or SendReceive messages remain in that column.

      See Automatic Mapping for more information on how auto-mapping works.

  7. To map messages and interrunnable variables or SenderReceiver interface elements manually in the Mapping field, proceed Closedas follows.

    Note

    You cannot use the Mapping field for multiple mappings of the same message.

    1. Double-click in a cell in the Variables column.

      A list with all elements available for mapping opens.

    2. Select an element.

      The mapping is performed. The results are shown in the Mapping field.

      The mapped element is removed from the Variables column of the upper table. A mapped receive message is removed from the Messages column of the upper table.

      Or – as an alternative in the Internal Access tab –

    1. In the Messages column, select an unmapped message.

    2. Right-click the message and select Create Interrunnable from the context menu.

      A new interrunnable variable with the same name, type, and implementation, as the message is created in the SWC, and mapped to the message.

      The mapped message is removed from the Messages column of the upper table.

  8. To map messages and interrunnable variables or SenderReceiver interface elements manually in the upper table (hidden by default), proceed Closedas follows.

    1. If necessary, click to show the upper table.
    2. In the Messages column of the upper table, select a message.
    3. In the Variables column, select an interrunnable variable or SenderReceiver interface element.

      The button becomes available if the selected elements can be mapped.

    4. Click to map the selected elements.

      Or

    5. Drag a message from the Messages column and drop it onto a suitable element in the Variables column.

      The mapping is performed. The results are shown in the Mapping field.

      The mapped element is removed from the Variables column of the upper table. A mapped receive message is removed from the Messages column of the upper table, other messages remain in that column.

  9. If desired, import an existing mapping.
  10. To remove a mapping, proceed Closedas follows.

    1. In the Mapping field, Messages or Variables column, select a mapped element.
    2. Do one of the following:

      • Open the context menu or the Mapping menu and select Remove.
      • Press <Delete>.

      Or

    3. In the Mapping field, double-click a cell in the Variables column and select <None>.

      The mapping is removed. If it was the 1+nth mapping of a Send or SendReceive message, the entire line is removed from the Mapping field.

      The interrunnable variable or SenderReceiver interface element reappears in the upper table.

      If the message is a Receive message, it reappears in the upper table, too.

    Changed mappings are indicated by blue font in the Variables column of the Mapping field.

    The icon column in the Mapping field shows the mapping status: – unmapped / – mapping is valid / – mapping is invalid.

See also Example: Accessing ASCET Messages

See also

Including a Component as a Complex Element

Creating a Message

Example: Accessing ASCET Messages

Message Mapping

Message Mapping View

Mapping Conversion

Filtering the Mapping Views

Importing Mappings

Exporting Mappings