Special Features of Reproducing Components as AUTOSAR Components

The Edit menu, Reproduce As submenu, offers several possibilities to reproduce ASCET components as AUTOSAR components.

The following list explains in detail what these possibilities do.

• SenderReceiver Interface Require Port

  Note
  Available for block diagram and ESDL modules.

  • If the module contains no receive message, you are informed that no interface was created because no suitable message was found.
  • A SenderReceiver interface named (by default) SRI_Require_<module name> is created.

  • For each receive messages included directly or indirectly in the module, a data element with identical name and model type is created.

    Elements not allowed in a SenderReceiver interface are ignored. Such elements are, e.g., matrix messages or record messages.

  • For each implementation set of the module, an implementation set is created for the SenderReceiver interface. The implementations of the receive messages are copied.

  • For each data set of the module, a data set is created for the SenderReceiver interface. The data of the receive messages are copied.

    Note
    In the ASCET options window, "Modeling\Reproduce As" node, you can customize the names of the generated SenderReceiver interface and of automatically created require ports.

• SenderReceiver Interface Provide Port

  Note
  Available for block diagram and ESDL modules.

  • If the module contains no send or SendReceive message, you are informed that no interface was created because no suitable message was found.
  • A SenderReceiver interface named (by default) SRI_Provide_<module name> is created.

  • For each send or SendReceive message included directly or indirectly in the module, a data element with identical name and model type is created.

    Elements not allowed in a SenderReceiver interface are ignored. Such elements are, e.g., matrix messages or record messages that contain a matrix.

  • For each implementation set of the module, an implementation set is created for the SenderReceiver interface. The implementations of the send and SendReceive messages are copied.

  • For each data set of the module, a data set is created for the SenderReceiver interface. The data of the send and SendReceive messages are copied.

    Note
    In the ASCET options window, "Modeling\Reproduce As" node, you can customize the names of the generated SenderReceiver interface and of automatically created provide ports.

• Calibration Interface

  Note
  Available for block diagram and ESDL modules.

  • If the module contains no imported parameters, no interface is created.
  • A Calibration interface named (by default) Calibration_<module name> is created.

  • For each imported parameter included directly or indirectly in the module, a data element with identical name and model type is created.

    Imported parameters with types not allowed in a Calibration interface are ignored. Such types are, e.g., a matrix, a record that contain a matrix, a characteristic line/map, etc.

  • For each implementation set of the module, an implementation set is created for the Calibration interface. The implementations of the imported parameters are copied.

  • For each data set of the module, a data set is created for the Calibration interface. The data of the imported parameters are copied.

    Note
    In the ASCET options window, "Modeling\Reproduce As" node, you can customize the names of the generated Calibration interface and of automatically created require ports.

• ClientServer Interface

  Note
  Available for block diagram, ESDL, or C code classes specified as service routine or prototype implementation.

  • If the class is not specified as service routine or prototype implementation, no interface is created.
  • A ClientServer interface named (by default) Client_Server_<class name> is created.

  • For each method in the class, an operation is created.

    The operation contains all arguments of the original method. If the return type of the original method is not void, an additional argument (named returnArgument by default) with direction OUT and the return type of the method is created. The return type of the operation is set to Std_Return_Type.

    Methods with argument/return types not allowed in a ClientServer interface are ignored. Such types are, e.g., a matrix argument/return, a record argument/return that contains a matrix, etc.

  • For each implementation set of the class, an implementation set is created for the ClientServer interface. The implementations of the arguments and the return value are copied.

  • In addition, a prototype class named (by default) Client_Server_Prototype_<class name> is created. This class contains one method for each operation (with identical arguments, return, implementation, data).

    Each method of the prototype class is assigned a symbol RTE_<CSI name>_<operation name>.

    Note
    In the ASCET options window, "Modeling\Reproduce As" node, you can customize the names of the generated ClientServer interface, the return arguments of the operations, the prototype class, and automatically created require ports.

• SWC Wrapper

  Note
  Available for block diagram and ESDL modules.

  • A software component named SWC_<module name> is created. The software component contains an instance of the module. The module instance in the SWC uses the same implementation set and data set as the original module instance in its parent project.

  • For each process in the module, a runnable with identical name is added to the software component. Each runnable calls its process.

  • A project named (by default) P_<module name> is created. The ANSI-C target and the newest RTE-AUTOSAR * operating system supported by ASCET are selected. The software component is added to the project.

  • If the module contains at least one receive message, a SenderReceiver interface SRI_Require_<module name> is created. See SenderReceiver Interface Require Port for details.

    The SenderReceiver interface is added to the software component as Rport.

  • If the module contains at least one send message or one SendReceive message, a SenderReceiver interface SRI_Provide_<module name> is created. See SenderReceiver Interface Provide Port for details.

    The SenderReceiver interface is added to the software component as Pport.

  • If the module contains, directly or indirectly, at least one imported parameter, a Calibration interface Calibration_<module name> is created. See Calibration Interface for details.

    The Calibration interface is added to the software component as Rport.

  • For each prototype class or service routine referenced by the original module, a ClientServer interface is created. See ClientServer Interface for details.

    The ClientServer interfaces are added to the SWC as Rports.

  • Automatic parameter mapping is performed.

  • For each SendReceive message in the module, an interrunnable with identical name is created.

  • Automatic message mapping (internal and external) is performed.

    Note
    In the ASCET options window, "Modeling\Reproduce As" node, you can customize the names of the generated SWC, project, AUTOSAR interfaces, Rports and Pports, return arguments of operations in generated ClientServer interfaces, and the prototype class of a generated ClientServer interface.

• SenderReceiver Interface

  Note
  Available only for records.

  • A SenderReceiver interface named (by default) SenderReceiver_<record name> is created.

  • For each element included directly or indirectly in the record, a data element with identical name and model type is created.

    Elements not allowed in a SenderReceiver interface are ignored. Such elements are, e.g., a matrix or a record that contains a matrix.

  • If the record contains only elements not allowed in a SenderReceiver interface, the created SenderReceiver interface is empty.
  • For the first implementation set of the record, an implementation set is created for the SenderReceiver interface. The implementations of the record elements are copied. Other implementation sets are ignored.
  • For the first data set of the record, a data set is created for the SenderReceiver interface. The data of the receive messages are copied. Other data sets are ignored.

• NVData Interface

  Note
  Available only for records.

  • An NVData interface named (by default) NVData_<record name> is created.

  • For each element included directly or indirectly in the record, a data element with identical name and model type is created.

    Elements not allowed in an NVData interface are ignored. Such elements are, e.g., a matrix or a record that contains a matrix.

  • If the record contains only elements not allowed in an NVData interface, the created NVData interface is empty.
  • For the first implementation set of the record, an implementation set is created for the NVData interface. The implementations of the record elements are copied. Other implementation sets are ignored.
  • For the first data set of the record, a data set is created for the NVData interface. The data of the receive messages are copied. Other data sets are ignored.

If implementations and data of imported elements are needed to reproduce a component, a project context is needed to obtain the required information. In that case, the project context is determined as follows:

• The database or workspace is searched for projects that contain the component to be reproduced.
• If one project is found, that project determines the project context.
• If no project is found, the component's default project determiner the project context.
• If several projects are found, a selection window opens. You can select the project you want to determine the project context.

See also

Reproducing Database/Workspace Items

Reproducing a Module as SWC Wrapper

Reproducing a Component