Specification of COM Based Transformer

AUTOSAR CP Release 4.4.0

Specification of COM Based

Document Title Transformer
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 662

Document Status Final

Part of AUTOSAR Standard Classic Platform
Part of Standard Release 4.4.0

Document Change History

Date Release Changed by Description
AUTOSAR
2018-10-31 4.4.0 Release • Updated buffer handling
Management • Removed include file structure

AUTOSAR • Updated handling of gaps in the

2017-12-08 4.3.1 Release array representation of a signal
Management group.
• Clarification on parameter passing.
• Updated include file structure figure.
AUTOSAR • Clarification on postBuild
2016-11-30 4.3.0 Release configuration in chapter 10.
Management • Added support for unqueued
communication when no data is
available in [SWS_ComXf_00035].
AUTOSAR • Exclude support for external trigger
2015-07-31 4.2.2 Release communica-
Management tion [SWS_ComXf_00032]
AUTOSAR
2014-10-31 4.2.1 Release • Initial Release
Management

1 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Disclaimer

This work (specification and/or software implementation) and the material contained in
it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the
companies that have contributed to it shall not be liable for any use of the work.
The material contained in this work is protected by copyright and other types of intel-
lectual property rights. The commercial exploitation of the material contained in this
work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the work
may be utilized or reproduced, in any form or by any means, without permission in
writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.

2 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Table of Contents
1 Introduction and functional overview 5

2 Acronyms and Abbreviations 6

3 Related documentation 7
3.1 Input documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Related standards and norms . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 Related specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Constraints and assumptions 9
4.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Applicability to car domains . . . . . . . . . . . . . . . . . . . . . . . . 9
5 Dependencies to other modules 10
5.1 File structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1.1 Code file structure . . . . . . . . . . . . . . . . . . . . . . . . 10
6 Requirements Tracing 11

7 Functional specification 12
7.1 Specification of the COM Based Transformer . . . . . . . . . . . . . . 15
7.2 Error classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2.1 Development Errors . . . . . . . . . . . . . . . . . . . . . . . 18
7.2.2 Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2.3 Transient Faults . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.2.4 Production Errors . . . . . . . . . . . . . . . . . . . . . . . . 19
7.2.5 Extended Production Errors . . . . . . . . . . . . . . . . . . . 19
8 API specification 20
8.1 Imported types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2 Type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.3 Function definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.3.1 ComXf_<transformerId> . . . . . . . . . . . . . . . . . . . . . 20
8.3.2 ComXf_Inv_<transformerId> . . . . . . . . . . . . . . . . . . 22
8.3.3 ComXf_Init . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.3.4 ComXf_DeInit . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.3.5 ComXf_GetVersionInfo . . . . . . . . . . . . . . . . . . . . . 24
8.4 Callback notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.5 Scheduled functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.6 Expected interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
9 Sequence diagrams 25

10 Configuration specification 26

A Referenced Meta Classes 27

3 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

B Used ECU Configuration 34

C History of Constraints and Specification Items 58

C.1 Constraint History of this Document according to AUTOSAR R4.2.1 . . 58
C.2 Constraint History of this Document according to AUTOSAR R4.2.2 . . 58
C.2.1 Added Traceables in 4.2.2 . . . . . . . . . . . . . . . . . . . . 58
C.2.2 Changed Traceables in 4.2.2 . . . . . . . . . . . . . . . . . . 58
C.2.3 Deleted Traceables in 4.2.2 . . . . . . . . . . . . . . . . . . . 58
C.3 Constraint History of this Document according to AUTOSAR R4.3.0 . . 58
C.3.1 Added Traceables in 4.3.0 . . . . . . . . . . . . . . . . . . . . 58
C.3.2 Changed Traceables in 4.3.0 . . . . . . . . . . . . . . . . . . 58
C.3.3 Deleted Traceables in 4.3.0 . . . . . . . . . . . . . . . . . . . 59
C.4 Constraint History of this Document according to AUTOSAR R4.3.1 . . 59
C.4.1 Added Traceables in 4.3.1 . . . . . . . . . . . . . . . . . . . . 59
C.4.2 Changed Traceables in 4.3.1 . . . . . . . . . . . . . . . . . . 59
C.4.3 Deleted Traceables in 4.3.1 . . . . . . . . . . . . . . . . . . . 59
C.5 Constraint History of this Document according to AUTOSAR R4.4.0 . . 59
C.5.1 Added Traceables in 4.4.0 . . . . . . . . . . . . . . . . . . . . 59
C.5.2 Changed Traceables in 4.4.0 . . . . . . . . . . . . . . . . . . 59
C.5.3 Deleted Traceables in 4.4.0 . . . . . . . . . . . . . . . . . . . 59

4 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

1 Introduction and functional overview

The transformer feature provides functionality to chain arbitrary transformers when
sending and receiving data in the RTE. The COM Based Transformer provides this
functionality when the target bus system uses a fixed communication matrix with
packed data representations.

5 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

2 Acronyms and Abbreviations

No specific terms have been introduced additionally to those already defined in [1].

6 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

3 Related documentation

3.1 Input documents

References
[1] Glossary
AUTOSAR_TR_Glossary
[2] General Specification on Transformers
AUTOSAR_ASWS_TransformerGeneral
[3] Specification of RTE Software
AUTOSAR_SWS_RTE
[4] Specification of Communication
AUTOSAR_SWS_COM
[5] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral
[6] Requirements on Transformer
AUTOSAR_SRS_Transformer
[7] System Template
AUTOSAR_TPS_SystemTemplate
[8] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral

7 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

3.2 Related standards and norms

Not applicable.

3.3 Related specification

AUTOSAR provides a General Specification on Transformers [2], which is also valid for
COM Based Transformer.
Thus, the specification ASWS Transformer General shall be considered as additional
and required specification for COM Based Transformer.

8 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

4 Constraints and assumptions

4.1 Limitations
For the COM Based Transformer all general transformer limitations (see [2]) apply.
Additionally the following restrictions apply for the COM Based Transformer:
[SWS_ComXf_00017] d The COM Based Transformer does not support Client-Server
communication. c(SRS_Xfrm_00201)
[SWS_ComXf_00032] d The COM Based Transformer does not support external trig-
ger communication. c(SRS_Xfrm_00201)
[SWS_ComXf_00018] d The COM Based Transformer only supports composite data
types (i.e. Signal Groups from COM). c(SRS_Xfrm_00201)
[SWS_ComXf_00019] d The COM Based Transformer only supports fix sized data
types. c(SRS_Xfrm_00201)
[SWS_ComXf_00022] d The COM Based Transformer only supports signal groups
which are byte aligned. c(SRS_Xfrm_00201)
[SWS_ComXf_00023] d The COM Based Transformer shall support signal group
where all group signals are mapped successively (possibly with gaps where posi-
tions in the signal group layout have no corresponding signal defined) to the IPdu.
c(SRS_Xfrm_00201)

4.2 Applicability to car domains

The COM Based Transformer can be used for all domain applications when a fixed
communication matrix is used.

9 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

5 Dependencies to other modules

The AUTOSAR RTE [3] has to exist to execute the COM Based Transformer.
The AUTOSAR COM configuration [4] of the data handled by the COM Based Trans-
former has to exists in order to allow the configuration of the COM Based Transformer.

5.1 File structure

5.1.1 Code file structure

The source code file structure is defined in the [2].

10 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

6 Requirements Tracing
The following table references the features specified in [5] and [6] and links to the
fulfillments of these.
Feature Description Satisfied by
[SRS_BSW_00159] All modules of the [SWS_ComXf_00025]
AUTOSAR Basic Software
shall support a tool based
configuration
[SRS_BSW_00337] Classification of [SWS_ComXf_00028]
development errors
[SRS_BSW_00404] BSW Modules shall support [SWS_ComXf_00030]
post-build configuration
[SRS_BSW_00407] Each BSW module shall [SWS_ComXf_00024] [SWS_ComXf_00026]
provide a function to read [SWS_ComXf_00027]
out the version information
of a dedicated module
implementation
[SRS_BSW_00411] All AUTOSAR Basic [SWS_ComXf_00024] [SWS_ComXf_00026]
Software Modules shall [SWS_ComXf_00027]
apply a naming rule for
enabling/disabling the
existence of the API
[SRS_BSW_00441] Naming convention for type, [SWS_ComXf_00030]
macro and function
[SRS_Xfrm_00009] A fixed set of transformer [SWS_ComXf_00003]
classes shall exist
[SRS_Xfrm_00011] A transformer shall belong [SWS_ComXf_00003] [SWS_ComXf_00006]
to a specific transformer
class
[SRS_Xfrm_00201] The COM Based [SWS_ComXf_00004] [SWS_ComXf_00005]
Transformer shall define the [SWS_ComXf_00007] [SWS_ComXf_00008]
serialization of atomic and [SWS_ComXf_00009] [SWS_ComXf_00010]
structured data elements [SWS_ComXf_00011] [SWS_ComXf_00012]
into linear arrays based on [SWS_ComXf_00013] [SWS_ComXf_00015]
a fixed data mapping [SWS_ComXf_00016] [SWS_ComXf_00017]
[SWS_ComXf_00018] [SWS_ComXf_00019]
[SWS_ComXf_00020] [SWS_ComXf_00021]
[SWS_ComXf_00022] [SWS_ComXf_00023]
[SWS_ComXf_00032] [SWS_ComXf_00035]
[SWS_ComXf_00036]
[SRS_Xfrm_00202] The COM Based [SWS_ComXf_00005] [SWS_ComXf_00020]
Transformer shall take its [SWS_ComXf_00025] [SWS_ComXf_00031]
configuration from the COM [SWS_ComXf_00033] [SWS_ComXf_00034]
module [SWS_ComXf_00036]

11 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

7 Functional specification
When a SWC initiates an inter-ECU communication which is configured to be trans-
formed, the SWC hands the data over to the RTE. The RTE executes the configured
transformer chain which contains - if the configuration demands this - the COM Based
Transformer.

Application SWC

1. Rte_Write_a {x,y,z}

2. Data are serialized

based on System Desc.

3. Further Transformers
add information
4. one large
crc x y z hash byte array
RTE
5. One call to Com_SendSignalGroupArray()

Com 6. Com analyzes uint8-array based on

Transmission Mode Selection (TMS)

crc x y z hash Pdu

Transmission Mode Selection

y != 0 , z > 200

Figure 7.1: Overview of COM Based Transformer

- AUTOSAR Confidential -

1 The COM Based

Set date in Insert -> Transformer on the
Header & Footer
sender
Set footer side
in Insert -> Headerserializes
& Footer the data of the SWC and
brings them into a uint8-array representation based on the communication matrix de-
scription. The uint8-array representation is forwarded to the COM module to be placed
inside the respective IPdu. The COM module may analyze (depending on the configu-
ration of the Transmission Mode Selection – TMS) the provided uint8-array and trigger
the respective transmission mode. The IPdu is sent via the communication stack over
the bus to the receiver(s).
The RTE of the receiver side executes the transformer chain in the reverse order. The
COM Based transformer of the receiver deserializes the linear data back into the origi-
nal data structure. These are handed over to the receiving SWC.
From the SWC’s point of view it is totally transparent whether data are transformed or
not.

12 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

length of the uint8-array representation

Signal
Signal Group X Signal B Signal IPdu
A

start position of the uint8-array representation

Signal M CRC SC D D D D Signal IPdu showing

Signal B group signals
A 1 2 3 4

Further Transformer with

M CRC SC D D D D
BufferProperties.headerLength > 0
1 2 3 4 adds header data

Array representation
CRC SC D D D D
enhanced by
1 2 3 4 E2E Transformer

Array representation
CRC SC D D D D
result of
1 2 3 4 COM Based Transformer

Array representation
D D D D
filled by
1 2 3 4 COM Based Transformer

Start of data with DataMapping

- AUTOSAR Confidential -

Figure 7.2: IPdu and signal layout

The handling of the data inside COM’s IPdu buffer and the transformer buffer is shown
in figure 7.2.
The ISignalIPdu is handled by the COM module as ComIPdu and may contain
several parts (signals and signal groups). A signal group in COM is represented by the
ComSignalGroup container.
In the System Template [7] it is possible to define that a signal group shall be handled by
the COM Based Transformer. The usage of the COM Based Transformer for a specific
transformer chain is defined by the reference comBasedSignalGroupTransforma-
tion from the ISignalGroup to DataTransformation (see figure 7.3).

13 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

FibexElement Identifiable
+dataTransformation
ISignal DataTransformation
«atpVariation,atpSplitable»
+ dataTypePolicy: DataTypePolicyEnum 0..1
+ iSignalType: ISignalTypeEnum [0..1]
+ length: Integer
0..1 +comBasedSignalGroupTransformation
0..*
+iSignal

  
   
   «atpVariation,atpSplitable»
+networkRepresentationProps 0..1

«atpVariation» FibexElement
SwDataDefProps ISignalGroup

+physicalProps 0..1

+systemSignalGroup 1
ARElement +systemSignal ARElement
+systemSignal SystemSignal SystemSignalGroup
*
1 + dynamicLength: Boolean
+transformingSystemSignal

0..1

Figure 7.3: System Template Transformed communication

In the Ecu configuration of the COM module such ComSignalGroups have a Com-
SignalGroupArrayAccess=true parameter defined.
If the ComSignalGroupArrayAccess=true then it implicitly defines the length of
the signal group ([SWS_Com_00845] [4]) and the start position inside the ComIPdu
where the signal group starts ([SWS_Com_00844] [4]). Thus there can be several
signals and signal groups defined inside an ISignalIPdu (e.g. ’Signal A’ and ’Signal
B’ are part of the IPdu but are not considered by the COM Based Transformer for the
’Signal Group X’).
The Com APIs Com_SendSignalGroupArray and
Com_ReceiveSignalGroupArray handle the signal group as array represen-
tation based on length of the signal group and the start position inside the ComIPdu.
This array representation contains all signals that belong to the signal group,
regardless whether the application software has a data mapping defined or not.
As an example in figure 7.2 the ’Signal Group X’ consists of the signals ’M’, ’CRC’, ’SC’,
’D1’, ’D2’, ’D3’, and ’D4’. Thus the RTE will interact with COM based on the whole array
representation of this signal group with length of the signal group.
When the RTE interacts with the COM Based Transformer also all the other poten-
tial transformers need to be considered in order to determine which part of the array
representation of the signal group actually is provided to each transformer since each
transformer may add data during sending (or remove data during reception).
E.g. the part of the array representation which holds the ’CRC’ and ’SC’ signals are
handled by the E2E transformer but will not be considered by the COM Based Trans-
former. The ’M’ signal will neither be handled by the E2E transformer nor the COM
Based Transformer. For ’M’ a further transformer is responsible.

14 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

The RTE will provide the data buffer from the ’Start of data with DataMapping defined’
location to the COM Based Transformer.

7.1 Specification of the COM Based Transformer

Serialization describes the way data is represented in protocol data units (PDUs) trans-
ported over a network. For the COM Based Transformer the serialization is defined by
the communication matrix using the System Template [7]. The communication matrix
information is taken over to the Ecu configuration of the COM module.
[SWS_ComXf_00005] d The serialization is based on the Ecu configuration of the
COM module and
• the Software Components PortPrototype,
• the dataElement list defined by the respective SenderReceiverInterface,
• the SenderReceiverToSignalGroupMapping,
• and the ISignalToIPduMapping for the SystemSignalGroup.
c(SRS_Xfrm_00201, SRS_Xfrm_00202)
[SWS_ComXf_00003] d The COM Based transformer shall only be used as
the top-most transformer (first) in a transformer chain. c(SRS_Xfrm_00009,
SRS_Xfrm_00011)
The COM Based transformer serializes structured data into a linear form. Therefore it
can only be used as the first transformer on the sending side and the last transformer
on the receiving side.
[SWS_ComXf_00004] d The COM Based transformer defined in this document shall
be used as a transformer if
• the attribute protocol of the TransformationTechnology is set to COM-
Based
• and the attribute version of the TransformationTechnology is set to
1.0.0
• and the attribute transformerClass of the TransformationTechnology is
set to serializer
c(SRS_Xfrm_00201)
[SWS_ComXf_00015] d The COM Based Transformer shall support all basic data
types that are supported by the COM module in [SWS_Com_00675] except for
UINT8_DYN. c(SRS_Xfrm_00201)
[SWS_ComXf_00016] d The COM Based Transformer shall handle each dataEle-
ment of the SenderReceiverInterface individually. c(SRS_Xfrm_00201)

15 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

[SWS_ComXf_00021] d The COM Based Transformer shall handle each dataEle-

ment of the SenderReceiverInterface like defined for the COM module [4] when
the COM API Com_SendSignal (rep. Com_ReceiveSignal) is called for a shadow
signal. c(SRS_Xfrm_00201)
This defines that the COM Based Transformer performs all actions equally to the COM
module. This does include functionality like endianess conversion and sign extension.
The COM Configuration implicitly defines the length of the signal group
([SWS_Com_00845] [4]) and the start position inside the ComIPdu where the signal
group starts ([SWS_Com_00844] [4]). In order to place the transformed data element
into the data buffer provided by the RTE the COM Based Transformer needs to respect
the offset introduced by the position of the ComGroupSignal inside the ComIPdu (de-
fined by the start position inside the ComIPdu) and the additional offset introduced
by header data which is handled by other transformers called after the COM Based
Transformer.
[SWS_ComXf_00036] d If the signal layout of the signal group array representation
contains gaps, those gaps shall be set during transmission to the value defined by
the ComTxIPduUnusedAreasDefault of the respective ComTxIPdu that this signal
group is mapped to. c(SRS_Xfrm_00201, SRS_Xfrm_00202)
Gaps in the signal group array representation may occur because the layout is not fully
packed and there are bits (or even bytes) that have no signal defined for (see 7.4).

CRC SC D D D D Signal Group with gaps

1 2 3 4 in signal layout

IPdu unused area IPdu unused area IPdu unused area IPdu Unused
default default default
0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Areas Default

CRC SC D D D Signal IPdu with default

D1 value 01 010101
2 3 4 and group signal values

Figure 7.4: Example of an array representation with gaps

[SWS_ComXf_00020] d The COM Based Transformer shall place the serialized data
element into the data buffer at the bit position according to the configuration of the
ISignalGroup in Com. c(SRS_Xfrm_00201, SRS_Xfrm_00202)
[SWS_ComXf_00013] d To allow migration, the deserialization shall be able to accept
larger array representations and ignore dataElements appended at the end of a previ-
ously known parameter list. c(SRS_Xfrm_00201)
This means: data elements that were not defined in the interface specification used to
generate or parameterize the deserialization code at the end of the serialized data will
be ignored by the deserialization.
- AUTOSAR Confidential -

16 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Class TransformationTechnology
Package M2::AUTOSARTemplates::SystemTemplate::Transformer
Note A TransformationTechnology is a transformer inside a transformer chain.
Tags: xml.namePlural=TRANSFORMATION-TECHNOLOGIES
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mul. Kind Note
bufferProperties BufferProperties 1 aggr Aggregation of the mandatory BufferProperties.
hasInternal Boolean 0..1 attr This attribute defines whether the Transformer has an
State internal state or not.
needsOriginal Boolean 0..1 attr Specifies whether this transformer gets access to the
Data SWC’s original data.
protocol String 1 attr Specifies the protocol that is implemented by this
transformer.
transformation Transformation 0..1 aggr A transformer can be configured with transformer specific
Description Description parameters which are represented by the Transformer
Description.
Stereotypes: atpVariation
Tags: vh.latestBindingTime=postBuild
transformer TransformerClassEnum 1 attr Specifies to which transformer class this transformer
Class belongs.
version String 1 attr Version of the implemented protocol.

Table 7.1: TransformationTechnology

Enumeration TransformerClassEnum
Package M2::AUTOSARTemplates::SystemTemplate::Transformer
Note Specifies the transformer class of a transformer.
Literal Description
custom The transformer is a custom transformer.
Tags: atp.EnumerationValue=0
safety The transformer is a safety transformer.
Tags: atp.EnumerationValue=1
security The transformer is a security transformer.
Tags: atp.EnumerationValue=2
serializer The transformer is a serializing transformer.
Tags: atp.EnumerationValue=3

Table 7.2: TransformerClassEnum

Class BufferProperties
Package M2::AUTOSARTemplates::SystemTemplate::Transformer
Note Configuration of the buffer properties the transformer needs to work.
Base ARObject
Attribute Type Mul. Kind Note
buffer CompuScale 0..1 aggr If the transformer changes the size of the data, the
Computation CompuScale can be used to specify a rule to derive the
size of the output data based on the size of the input data.
5

17 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

4
Class BufferProperties
headerLength Integer 1 attr Defines the length of the header (in bits) this transformer
will add in front of the data.
inPlace Boolean 1 attr If set, the transformer uses the input buffer as output
buffer.
Table 7.3: BufferProperties

Class TransformationDescription (abstract)

Package M2::AUTOSARTemplates::SystemTemplate::Transformer
Note The TransformationDescription is the abstract class that can be used by specific transformers to add
transformer specific properties.
Base ARObject, Describable
Subclasses EndToEndTransformationDescription, SOMEIPTransformationDescription, UserDefinedTransformation
Description
Attribute Type Mul. Kind Note
– – – – –
Table 7.4: TransformationDescription

7.2 Error classification

7.2.1 Development Errors

[SWS_ComXf_00028] Development Errors d The errors shown in table 7.5 are de-
fined as development errors for the COM Based Transformer. c(SRS_BSW_00337)

Type of error Related error code Value

Error code if any other API service, except <MIP>_E_UNINIT 0x01
GetVersionInfo is called before the
transformer module was initialized with Init
or after a call to DeInit
Error code if an invalid configuration set was <MIP>_E_INIT_FAILED 0x02
selected
API service called with wrong parameter <MIP>_E_PARAM 0x03
API service called with invalid pointer <MIP>_E_PARAM_POINTER 0x04

Table 7.5: Development Errors

7.2.2 Runtime Errors

No runtime errors are specified for the COM Based Transformer.

18 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

7.2.3 Transient Faults

No transient faults are specified for the COM Based Transformer.

7.2.4 Production Errors

No production errors are specified for the COM Based Transformer.

7.2.5 Extended Production Errors

No extended production errors are specified for the COM Based Transformer.

19 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

8 API specification

8.1 Imported types

There are no imported types from other modules beyond those specified in [2].
In the Module Interlink Headers file which is imported by the COM Based Transformer,
all ImplementationDataTypes known to the RTE are included. Using this mecha-
nism, the COM Based Transformer knows all data types of data which shall be trans-
formed.

8.2 Type definitions

[SWS_ComXf_00030] d
Name: ComXf_ConfigType
Type: Structure
Element: implementation –
specific
Description: This is the type of the data structure containing the initialization data for the
transformer.
Available ComXf.h
via:

Table 8.1: ComXf_ConfigType

c(SRS_BSW_00404, SRS_BSW_00441)

8.3 Function definitions

The COM Based transformer provides the specific interfaces generally required by [2].
[SWS_ComXf_00006] d The COM Based Transformer shall only provide functions for
transformers where the TransformationTechnology is referenced as the first ref-
erence in the list of ordered references transformerChain from a DataTransfor-
mation to a TransformationTechnology. c(SRS_Xfrm_00011)
That means, only the first transformer in a transformer chain can be a COM Based
Transformer because serializer transformer are in general only allowed to be the first
transformer in a chain.

8.3.1 ComXf_<transformerId>

[SWS_ComXf_00007] d

20 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Service name: ComXf_<transformerId>

Syntax: uint8 ComXf_<transformerId>(
uint8* buffer,
uint32* bufferLength,
<paramtype> dataElement
)
Service ID[hex]: 0x03
Sync/Async: Synchronous
Reentrancy: Reentrant
Parameters (in): dataElement Data element which shall be transformed
Parameters (inout): None
Parameters (out): buffer Buffer allocated by the RTE, where the transformed
data has to be stored by the transformer
bufferLength Used length of the buffer
Return value: uint8 0x00 (E_OK): Serialization successful
0x81 (E_SER_GENERIC_ERROR): A generic error
occurred
Description: This function transforms a Sender/Receiver communication using the se-
rialization of COM Based Transformer. It takes the data element as input
and outputs a uint8 array containing the serialized data.
Available via: ComXf.h

Table 8.2: ComXf_<transformerId>

c(SRS_Xfrm_00201)
where
• type is data type of the data element after all data conversion activities of the
RTE
• paramtype is derived from type according to the parameter passing
rules rules defined by the SRS BSW General [5] (see [SRS_BSW_00484],
[SRS_BSW_00485], and [SRS_BSW_00486]) and SWS BSW General [8] (see
[SWS_BSW_00186] and [SWS_BSW_00187])
• transformerId is the name pattern for the transformer specified be the Gen-
eral Specification on Transformers [2] [SWS_Xfrm_00062].
The function specified in [SWS_ComXf_00007] exists for each transformed
Sender/Receiver communication which uses the COM Based Transformer.
[SWS_ComXf_00008] d The function specified in [SWS_ComXf_00007] shall ex-
ist for the first reference in the list of ordered references transformerChain
from a DataTransformation to a TransformationTechnology if the Data-
Transformation is referenced by an ISignalGroup in the role comBasedSig-
nalGroupTransformation where the ISignalGroup references a SystemSig-
nalGroup which is referenced by SenderReceiverToSignalGroupMapping. c
(SRS_Xfrm_00201)
[SWS_ComXf_00009] d The function specified in [SWS_ComXf_00007] shall serial-
ize complex data elements of Sender/Receiver communication into a linear byte array
representation using the COM Based Transformation. c(SRS_Xfrm_00201)

21 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

8.3.2 ComXf_Inv_<transformerId>

[SWS_ComXf_00010] d
Service name: ComXf_Inv_<transformerId>
Syntax: uint8 ComXf_Inv_<transformerId>(
const uint8* buffer,
uint32 bufferLength,
<type>* dataElement
)
Service ID[hex]: 0x04
Sync/Async: Synchronous
Reentrancy: Reentrant
Parameters (in): buffer Buffer allocated by the RTE, where the still serial-
ized data are stored by the Rte
bufferLength Used length of the buffer
Parameters (inout): None
Parameters (out): dataElement Data element which is the result of the transforma-
tion and contains the deserialized data element
Return value: uint8 0x00 (E_OK): Serialization successful
0x01 (E_NO_DATA): No data available which can be
deserialized
0x81 (E_SER_GENERIC_ERROR): A generic error
occurred
Description: This function deserializes a Sender/Receiver communication using the
deserialization of COM Based Transformer. It takes the uint8 array con-
taining the serialized data as input and outputs the original data element
which will be passed to the Rte.
Available via: ComXf.h

Table 8.3: ComXf_Inv_<transformerId>

c(SRS_Xfrm_00201)
where
• type is data type of the data element before all data conversion activities of the
RTE
• transformerId is the name pattern for the transformer specified in
[SWS_Xfrm_00062] ([2]).
The function specified in [SWS_ComXf_00010] exists for each transformed
Sender/Receiver communication which uses the COM Based Transformation.
[SWS_ComXf_00011] d The function specified in [SWS_ComXf_00010] shall ex-
ist for the first reference in the list of ordered references transformerChain
from a DataTransformation to a TransformationTechnology if the Data-
Transformation is referenced by an ISignalGroup in the role comBasedSig-
nalGroupTransformation where the ISignalGroup references a SystemSig-
nalGroup which is referenced by SenderReceiverToSignalGroupMapping. c
(SRS_Xfrm_00201)

22 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

[SWS_ComXf_00035] d If ComXf_Inv_<transformerId> specified in

[SWS_ComXf_00010] is called with buffer equal to NULL_PTR and buffer-
Length equal to 0, then the output buffer buffer shall not be changed and
ComXf_Inv_<transformerId> shall return with E_NO_DATA. c(SRS_Xfrm_00201)
[SWS_ComXf_00012] d The function specified in [SWS_ComXf_00010] shall dese-
rialize a linear byte array to primitive or complex data elements of Sender/Receiver
communication using the COM Based Transformation. c(SRS_Xfrm_00201)

8.3.3 ComXf_Init

[SWS_ComXf_00026] d
Service name: ComXf_Init
Syntax: void ComXf_Init(
const ComXf_ConfigType* config
)
Service ID[hex]: 0x01
Sync/Async: Synchronous
Reentrancy: Reentrant
Parameters (in): config Pointer to the transformer’s configuration data.
Parameters (inout): None
Parameters (out): None
Return value: None
Description: This service initializes the transformer for the further processing.
Available via: ComXf.h

Table 8.4: ComXf_Init

c(SRS_BSW_00407, SRS_BSW_00411)

8.3.4 ComXf_DeInit

[SWS_ComXf_00027] d
Service name: ComXf_DeInit
Syntax: void ComXf_DeInit(
void
)
Service ID[hex]: 0x02
Sync/Async: Synchronous
Reentrancy: Reentrant
Parameters (in): None
Parameters (inout): None
Parameters (out): None
Return value: None
Description: This service deinitializes the transformer.
Available via: ComXf.h

Table 8.5: ComXf_DeInit

23 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

c(SRS_BSW_00407, SRS_BSW_00411)

8.3.5 ComXf_GetVersionInfo

[SWS_ComXf_00024] d
Service name: ComXf_GetVersionInfo
Syntax: void ComXf_GetVersionInfo(
Std_VersionInfoType* VersionInfo
)
Service ID[hex]: 0x00
Sync/Async: Synchronous
Reentrancy: Reentrant
Parameters (in): None
Parameters (inout): None
Parameters (out): VersionInfo Pointer to where to store the version information of
this module.
Return value: None
Description: This service returns the version information of the called transformer
module.
Available via: ComXf.h

Table 8.6: ComXf_GetVersionInfo

c(SRS_BSW_00407, SRS_BSW_00411)

8.4 Callback notifications

COM Based Transformer has no callback notifications.

8.5 Scheduled functions

COM Based Transformer has no scheduled functions.

8.6 Expected interfaces

COM Based Transformer has no expected interfaces.

24 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

9 Sequence diagrams
There are no sequence diagrams applicable to COM Based Transformer.

25 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

10 Configuration specification
[SWS_ComXf_00031] d The COM Based Transformer is configured based on the
COM module configuration [4]. c(SRS_Xfrm_00202)
Still, there is an EcuC necessary to map the implementation of the transformer. The
EcuC defined in [2] shall be used.
[SWS_ComXf_00033] d The vendor specific module definition of the COM Based
Transformer - based on the Xfrm configuration [2] - may be extended by the vendor
to support the close interaction with the Com module [4]. c(SRS_Xfrm_00202)
[SWS_ComXf_00034] d The COM Based Transformer shall be configured to be post-
Build when the configuration of the Com module [4] is postBuild for the respective
ComSignalGroups. c(SRS_Xfrm_00202)
[SWS_ComXf_00025] d The apiServicePrefix of the COM Based Transformer’s
EcuC shall be set to ComXf. c(SRS_BSW_00159, SRS_Xfrm_00202)

26 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

A Referenced Meta Classes

For the sake of completeness, this chapter contains a set of class tables representing
meta-classes mentioned in the context of this document but which are not contained
directly in the scope of describing specific meta-model semantics.
Class DataTransformation
Package M2::AUTOSARTemplates::SystemTemplate::Transformer
Note A DataTransformation represents a transformer chain. It is an ordered list of transformers.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mul. Kind Note
data DataTransformationKind 0..1 attr This attribute controls the kind of DataTransformation to
Transformation Enum be applied.
Kind
executeDespite Boolean 1 attr Specifies whether the transformer chain is executed even
Data if no input data are available.
Unavailability
transformer Transformation 1..* ref This attribute represents the definition of a chain of
Chain (ordered) Technology transformers that are supposed to be executed according
to the order of being referenced from DataTransformation.

Table A.1: DataTransformation

Class EcucModuleDef
Package M2::AUTOSARTemplates::ECUCParameterDefTemplate
Note Used as the top-level element for configuration definition for Software Modules, including BSW and RTE
as well as ECU Infrastructure.
Tags: atp.recommendedPackage=EcucModuleDefs
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpDefinition, CollectableElement, Ecuc
DefinitionElement, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mul. Kind Note
apiServicePrefix CIdentifier 0..1 attr For CDD modules this attribute holds the apiService
Prefix.
The shortName of the module definition of a Complex
Driver is always "Cdd". Therefore for CDD modules the
module apiServicePrefix is described with this attribute.
container EcucContainerDef 1..* aggr Aggregates the top-level container definitions of this
specific module definition.
Stereotypes: atpSplitable
Tags: atp.Splitkey=shortName
xml.sequenceOffset=11
postBuildVariant Boolean 0..1 attr Indicates if a module supports different post-build variants
Support (previously known as post-build selectable configuration
sets). TRUE means yes, FALSE means no.
refinedModule EcucModuleDef 0..1 ref Optional reference from the Vendor Specific Module
Def Definition to the Standardized Module Definition it refines.
In case this EcucModuleDef has the category
STANDARDIZED_MODULE_DEFINITION
this reference shall not be provided. In case this Ecuc
5
5

27 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

4
Class EcucModuleDef
4
ModuleDef has the category
VENDOR_SPECIFIC_MODULE_DEFINITION this
reference is mandatory.
Stereotypes: atpUriDef
supported EcucConfiguration * attr Specifies which ConfigurationVariants are supported by
ConfigVariant VariantEnum this software module.
This attribute is optional if the EcucModuleDef has the
category STANDARDIZED_MODULE_DEFINITION. If
the category attribute of the EcucModuleDef is set to
VENDOR_SPECIFIC_MODULE_DEFINITION then this
attribute is mandatory.

Table A.2: EcucModuleDef

Class ISignalGroup
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note SignalGroup of the Interaction Layer. The RTE supports a "signal fan-out" where the same System
Signal Group is sent in different SignalIPdus to multiple receivers.
An ISignalGroup refers to a set of ISignals that shall always be kept together. A ISignalGroup represents
a COM Signal Group.
Therefore it is recommended to put the ISignalGroup in the same Package as ISignals (see
atp.recommendedPackage)
Tags: atp.recommendedPackage=ISignalGroup
Base ARObject, CollectableElement, FibexElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mul. Kind Note
comBased DataTransformation 0..1 ref Optional reference to a DataTransformation which
SignalGroup represents the transformer chain that is used to transform
Transformation the data that shall be placed inside this ISignalGroup
based on the COMBasedTransformer approach.
Stereotypes: atpSplitable; atpVariation
Tags: atp.Splitkey=comBasedSignalGroup
Transformation, variationPoint.shortLabel
vh.latestBindingTime=codeGenerationTime
iSignal ISignal * ref Reference to a set of ISignals that shall always be kept
together.
systemSignal SystemSignalGroup 1 ref Reference to the SystemSignalGroup that is defined on
Group VFB level and that is supposed to be transmitted in the
ISignalGroup.
transformation TransformationISignal * aggr A transformer chain consists of an ordered list of
ISignalProps Props transformers. The ISignalGroup specific configuration
properties for each transformer are defined in the
TransformationISignalProps class. The transformer
configuration properties that are common for all ISignal
Groups are described in the TransformationTechnology
class.
Table A.3: ISignalGroup

28 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Class ISignalIPdu
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note Represents the IPdus handled by Com. The ISignalIPdu assembled and disassembled in AUTOSAR
COM consists of one or more signals.
In case no multiplexing is performed this IPdu is routed to/from the Interface Layer.
A maximum of one dynamic length signal per IPdu is allowed.
Tags: atp.recommendedPackage=Pdus
Base ARObject, CollectableElement, FibexElement, IPdu, Identifiable, MultilanguageReferrable, Packageable
Element, Pdu, Referrable
Attribute Type Mul. Kind Note
iPduTiming IPduTiming 0..1 aggr Timing specification for Com IPdus (Transmission
Specification Modes).
This information is mandatory for the sender in a System
Extract. This information may be omitted on receivers in a
System Extract.
atpVariation: The timing of a Pdu can vary.
Stereotypes: atpVariation
Tags: vh.latestBindingTime=postBuild
iSignalToPdu ISignalToIPduMapping * aggr Definition of SignalToIPduMappings included in the Signal
Mapping IPdu.
atpVariation: The content of a PDU can be variable.
Stereotypes: atpVariation
Tags: vh.latestBindingTime=postBuild
pduCounter SignalIPduCounter 0..1 aggr An included Pdu counter is used to ensure that a
sequence of Pdus is maintained.
Stereotypes: atpVariation
Tags: vh.latestBindingTime=preCompileTime
pduReplication SignalIPduReplication 0..1 aggr Pdu Replication is a form of redundancy where the data
content of one ISignalIPdu (source) is transmitted inside a
set of replica ISignalIPdus. These ISignalIPdus (copies)
have different Pdu IDs, identical PduCounters, identical
data content and are transmitted with the same frequency.
Stereotypes: atpVariation
Tags: vh.latestBindingTime=preCompileTime
unusedBit Integer 1 attr AUTOSAR COM and AUTOSAR IPDUM are filling not
Pattern used areas of an IPDU with this bit-pattern. This attribute
is mandatory to avoid undefined behavior. This
byte-pattern will be repeated throughout the IPdu.

Table A.4: ISignalIPdu

Class ISignalToIPduMapping
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note An ISignalToIPduMapping describes the mapping of ISignals to ISignalIPdus and defines the position of
the ISignal within an ISignalIPdu.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mul. Kind Note
5

29 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

4
Class ISignalToIPduMapping
iSignal ISignal 0..1 ref Reference to a ISignal that is mapped into the ISignal
IPdu.
Each ISignal contained in the ISignalGroup shall be
mapped into an IPdu by an own ISignalToIPduMapping.
The references to the ISignal and to the ISignalGroup in
an ISignalToIPduMapping are mutually exclusive.
iSignalGroup ISignalGroup 0..1 ref Reference to an ISignalGroup that is mapped into the
SignalIPdu.
If an ISignalToIPduMapping for an ISignalGroup is
defined, only the UpdateIndicationBitPosition and the
transferProperty is relevant. The startPosition and the
packingByteOrder shall be ignored.
Each ISignal contained in the ISignalGroup shall be
mapped into an IPdu by an own ISignalToIPduMapping.
The references to the ISignal and to the ISignalGroup in
an ISignalToIPduMapping are mutually exclusive.
packingByte ByteOrderEnum 0..1 attr This parameter defines the order of the bytes of the signal
Order and the packing into the SignalIPdu. The byte ordering
"Little Endian" (MostSignificantByteLast), "Big Endian"
(MostSignificantByteFirst) and "Opaque" can be selected.
For opaque data endianness conversion shall be
configured to Opaque.
The value of this attribute impacts the absolute position of
the signal into the SignalIPdu (see the startPosition
attribute description).
For an ISignalGroup the packingByteOrder is irrelevant
and shall be ignored.
startPosition Integer 0..1 attr This parameter is necessary to describe the bitposition of
a signal within an SignalIPdu.
It denotes the least significant bit for "Little Endian" and
the most significant bit for "Big Endian" packed signals
within the IPdu (see the description of the packingByte
Order attribute). In AUTOSAR the bit counting is always
set to "sawtooth" and the bit order is set to "Decreasing".
The bit counting in byte 0 starts with bit 0 (least significant
bit). The most significant bit in byte 0 is bit 7.
Please note that the way the bytes will be actually sent on
the bus does not impact this representation: they will
always be seen by the software as a byte array.
If a mapping for the ISignalGroup is defined, this attribute
is irrelevant and shall be ignored.
transferProperty TransferPropertyEnum 0..1 attr Defines how the referenced ISignal contributes to the
send triggering of the ISignalIPdu.
update Integer 0..1 attr The UpdateIndicationBit indicates to the receivers that the
IndicationBit signal (or the signal group) was updated by the sender.
Position Length is always one bit. The UpdateIndicationBitPosition
attribute describes the position of the update bit within the
SignalIPdu. For Signals of a ISignalGroup this attribute is
irrelevant and shall be ignored.
Note that the exact bit position of the updateIndicationBit
Position is linked to the value of the attribute packingByte
Order because the method of finding the bit position is
different for the values mostSignificantByteFirst and most
SignificantByteLast. This means that if the value of
5
5

30 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

4
Class ISignalToIPduMapping
4
packingByteOrder is changed while the value of update
IndicationBitPosition remains unchanged the exact bit
position of updateIndicationBitPosition within the
enclosing ISignalIPdu still undergoes a change.
This attribute denotes the least significant bit for "Little
Endian" and the most significant bit for "Big Endian"
packed signals within the IPdu (see the description of the
packingByteOrder attribute). In AUTOSAR the bit
counting is always set to "sawtooth" and the bit order is
set to "Decreasing". The bit counting in byte 0 starts with
bit 0 (least significant bit). The most significant bit in byte
0 is bit 7.

Table A.5: ISignalToIPduMapping

Class ImplementationDataType
Package M2::AUTOSARTemplates::CommonStructure::ImplementationDataTypes
Note Describes a reusable data type on the implementation level. This will typically correspond to a typedef in
C-code.
Tags: atp.recommendedPackage=ImplementationDataTypes
Base ARElement, ARObject, AbstractImplementationDataType, AtpBlueprint, AtpBlueprintable, AtpClassifier ,
AtpType, AutosarDataType, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mul. Kind Note
dynamicArray String 0..1 attr Specifies the profile which the array will follow in case this
SizeProfile data type is a variable size array.
isStructWith Boolean 0..1 attr This attribute is only valid if the attribute category is set to
Optional STRUCTURE.
Element
If set to True, this attribute indicates that the
ImplementationDataType has been created with the
intention to define at least one element of the structure as
optional.
Tags: atp.Status=draft
subElement (or- ImplementationData * aggr Specifies an element of an array, struct, or union data
dered) TypeElement type.
The aggregation of ImplementionDataTypeElement is
subject to variability with the purpose to support the
conditional existence of elements inside a Implementation
DataType representing a structure.
Stereotypes: atpVariation
Tags: vh.latestBindingTime=preCompileTime
symbolProps SymbolProps 0..1 aggr This represents the SymbolProps for the Implementation
DataType.
Stereotypes: atpSplitable
Tags: atp.Splitkey=shortName
typeEmitter NameToken 0..1 attr This attribute is used to control which part of the
AUTOSAR toolchain is supposed to trigger data type
definitions.
Table A.6: ImplementationDataType

31 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Class PortPrototype (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::Components
Note Base class for the ports of an AUTOSAR software component.
The aggregation of PortPrototypes is subject to variability with the purpose to support the conditional
existence of ports.
Base ARObject, AtpBlueprintable, AtpFeature, AtpPrototype, Identifiable, MultilanguageReferrable, Referrable
Subclasses AbstractProvidedPortPrototype, AbstractRequiredPortPrototype
Attribute Type Mul. Kind Note
clientServer ClientServerAnnotation * aggr Annotation of this PortPrototype with respect to
Annotation client/server communication.
delegatedPort DelegatedPort 0..1 aggr Annotations on this delegated port.
Annotation Annotation
ioHwAbstraction IoHwAbstractionServer * aggr Annotations on this IO Hardware Abstraction port.
Server Annotation
Annotation
modePort ModePortAnnotation * aggr Annotations on this mode port.
Annotation
nvDataPort NvDataPortAnnotation * aggr Annotations on this non voilatile data port.
Annotation
parameterPort ParameterPort * aggr Annotations on this parameter port.
Annotation Annotation
senderReceiver SenderReceiver * aggr Collection of annotations of this ports sender/receiver
Annotation Annotation communication.
triggerPort TriggerPortAnnotation * aggr Annotations on this trigger port.
Annotation
Table A.7: PortPrototype

Class SenderReceiverInterface
Package M2::AUTOSARTemplates::SWComponentTemplate::PortInterface
Note A sender/receiver interface declares a number of data elements to be sent and received.
Tags: atp.recommendedPackage=PortInterfaces
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
DataInterface, Identifiable, MultilanguageReferrable, PackageableElement, PortInterface, Referrable
Attribute Type Mul. Kind Note
dataElement VariableDataPrototype 1..* aggr The data elements of this SenderReceiverInterface.
invalidation InvalidationPolicy * aggr InvalidationPolicy for a particular dataElement
Policy

Table A.8: SenderReceiverInterface

Class SenderReceiverToSignalGroupMapping
Package M2::AUTOSARTemplates::SystemTemplate::DataMapping
Note Mapping of a sender receiver communication data element with a composite datatype to a signal group.
Base ARObject, DataMapping
Attribute Type Mul. Kind Note
dataElement VariableDataPrototype 1 iref Reference to a data element with a composite datatype
which is mapped to a signal group.
signalGroup SystemSignalGroup 1 ref Reference to the signal group, which contain all primitive
datatypes of the composite type
5

32 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

4
Class SenderReceiverToSignalGroupMapping
typeMapping SenderRecComposite 1 aggr The CompositeTypeMapping maps the the Application
TypeMapping ArrayElements and ApplicationRecordElements to
Signals of the SignalGroup.

Table A.9: SenderReceiverToSignalGroupMapping

Class SystemSignalGroup
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note A signal group refers to a set of signals that must always be kept together. A signal group is used to
guarantee the atomic transfer of AUTOSAR composite data types.
The SystemSignalGroup defines a signal grouping on VFB level. On cluster level the Signal grouping is
described by the ISignalGroup element.
Tags: atp.recommendedPackage=SystemSignalGroups
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mul. Kind Note
systemSignal SystemSignal * ref Reference to a set of SystemSignals that must always be
kept together.
transforming SystemSignal 0..1 ref Optional reference to the SystemSignal which shall
SystemSignal contain the transformed (linear) data.

Table A.10: SystemSignalGroup

33 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

B Used ECU Configuration

To ease the readability the relevant parts of the Com module configuration [4] are
duplicated here (for information only).
ComSignalGroup: ComSignalGroupArrayAccess:
EcucParamConfContainerDef +parameter
EcucBooleanParamDef
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1

ComHandleId:
EcucIntegerParamDef

min = 0
max = 65535
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
symbolicNameValue = true

ComGroupSignal: ComBitPosition:
EcucParamConfContainerDef +parameter EcucIntegerParamDef
lowerMultiplicity = 0 min = 0
upperMultiplicity = * max = 4294967295 ComSignalLength:
EcucIntegerParamDef
+subContainer +parameter
max = 4294967295
min = 0
lowerMultiplicity = 0
ComBitSize: upperMultiplicity = 1
EcucIntegerParamDef
+parameter
max = 64
min = 0
lowerMultiplicity = 0
upperMultiplicity = 1

Figure B.1: AR_EcucDef_ComSignalGroupArrayAccess

SWS Item [ECUC_Com_00345]

Container Name ComSignalGroup
Description Contains the configuration parameters of the AUTOSAR COM
module’s signal groups.
Post-Build Variant true
Multiplicity
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Configuration Parameters

Name ComDataInvalidAction [ECUC_Com_00314]

Parent Container ComSignalGroup
Description This parameter defines the action performed upon reception of an
invalid signal. Relating to signal groups the action in case if one of the
included signals is an invalid signal. If Replace is used the
ComSignalInitValue will be used for the replacement.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range NOTIFY
REPLACE Literal for DataInvalidAction

34 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Post-Build Variant false

Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComErrorNotification [ECUC_Com_00499]

Parent Container ComSignalGroup
Description Only valid on sender side: Name of Com_CbkTxErr callback function
to be called. If this parameter is omitted no error notification shall take
place.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComFirstTimeout [ECUC_Com_00183]

Parent Container ComSignalGroup
Description Defines the length of the first deadline monitoring timeout period in
seconds. This timeout is used immediately after start (or restart) of the
deadline monitoring service. The timeout period of the successive
periods is configured by ECUC_Com_00263.
Multiplicity 0..1
Type EcucFloatParamDef
Range [0 .. 3600]

35 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComHandleId [ECUC_Com_00165]

Parent Container ComSignalGroup
Description The numerical value used as the ID.

This ID identifies signals and signal groups in the COM APIs using
Com_SignalIdType or Com_SignalGroupIdType parameter
respectively.
Multiplicity 0..1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name ComInitialValueOnly [ECUC_Com_00811]

Parent Container ComSignalGroup
Description This parameter defines that the respective signal’s initial value shall be
put into the respective PDU but there will not be any update of the
value through the RTE. Thus the Com implementation does not need
to expect any API calls for this signal (group).
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false

36 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Post-Build Variant false

Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComInvalidNotification [ECUC_Com_00315]

Parent Container ComSignalGroup
Description Only valid on receiver side: Name of Com_CbkInv callback function to
be called. Name of the function which notifies the RTE about the
reception of an invalidated signal/ signal group. Only applicable if
ComDataInvalidAction is configured to NOTIFY.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

37 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComNotification [ECUC_Com_00498]

Parent Container ComSignalGroup
Description On sender side: Name of Com_CbkTxAck callback function to be
called. On receiver side: Name of Com_CbkRxAck callback function to
be called.

If this parameter is omitted no notification shall take place.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComRxDataTimeoutAction [ECUC_Com_00412]

Parent Container ComSignalGroup
Description This parameter defines the action performed upon expiration of the
reception deadline monitoring timer.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range NONE no replacement shall take place
REPLACE signals shall be replaced by their
ComSignalInitValue
SUBSTITUTE signals shall be replaced by their
ComTimeoutSubstitutionValue
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –

38 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE

Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComSignalGroupArrayAccess [ECUC_Com_10003]

Parent Container ComSignalGroup
Description Defines whether the uint8-array based access shall be used for this
ComSignalGroup.
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency

Name ComTimeout [ECUC_Com_00263]

Parent Container ComSignalGroup
Description Defines the length of the deadline monitoring timeout period in
seconds. The period for the first timeout period can be configured
separately by ECUC_Com_00183.
Multiplicity 0..1
Type EcucFloatParamDef
Range [0 .. 3600]
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD

39 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Scope / Dependency scope: local

Name ComTimeoutNotification [ECUC_Com_00552]

Parent Container ComSignalGroup
Description On sender side: Name of Com_CbkTxTOut callback function to be
called. On receiver side: Name of Com_CbkRxTOut callback function
to be called.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComTransferProperty [ECUC_Com_00232]

Parent Container ComSignalGroup
Description Defines if a write access to this signal can trigger the transmission of
the corresponding I-PDU. If the I-PDU is triggered, depends also on
the transmission mode of the corresponding I-PDU.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range PENDING A write access to this signal never
triggers the transmission of the
corresponding I-PDU.
TRIGGERED Depending on the transmission mode,
a write access to this signal can trigger
the transmission of the corresponding
I-PDU.
TRIGGERED_ON_CHAN Depending on the transmission mode,
GE a write access to this signal can trigger
the transmission of the corresponding
I-PDU, but only in case the written
value is different to the locally stored
(last sent or initial value) in length or
value.

40 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

TRIGGERED_ON_CHAN Depending on the transmission mode,

GE_WITHOUT_REPETITI a write access to this signal can trigger
ON the transmission of the corresponding
I-PDU just once without a repetition,
but only in case the written value is
different to the locally stored (last sent
or initial value) in length or value.
TRIGGERED_WITHOUT_ Depending on the transmission mode,
REPETITION a write access to this signal can trigger
the transmission of the corresponding
I-PDU just once without a repetition.
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComUpdateBitPosition [ECUC_Com_00257]

Parent Container ComSignalGroup
Description Bit position of update-bit inside I-PDU. If this attribute is omitted then
there is no update-bit. This setting must be consistently on sender and
on receiver side.

Range: 0..63 for CAN and LIN, 0..511 for CAN FD, 0..2031 for FlexRay,
0..4294967295 for TP.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

41 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComSystemTemplateSignalGroupRef [ECUC_Com_00001]

Parent Container ComSignalGroup
Description Reference to the ISignalToIPduMapping that contains a reference to
the ISignalGroup (SystemTemplate) which this ComSignalGroup
represents.
Multiplicity 0..1
Type Foreign reference to I-SIGNAL-TO-I-PDU-MAPPING
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
ComGroupSignal 0..* This container contains the configuration parameters of
group signals. I.e. signals that are included within a
signal group.

SWS Item [ECUC_Com_00520]

Container Name ComGroupSignal
Description This container contains the configuration parameters of group signals.
I.e. signals that are included within a signal group.
Post-Build Variant true
Multiplicity
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Configuration Parameters

Name ComBitPosition [ECUC_Com_00259]

Parent Container ComGroupSignal
Description Starting position within the I-PDU. This parameter refers to the position
in the I-PDU and not in the shadow buffer. If the endianness
conversion is configured to Opaque the parameter ComBitPosition
shall define the bit0 of the first byte like in little endian byte order
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value

42 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Post-Build Variant true

Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComBitSize [ECUC_Com_00158]

Parent Container ComGroupSignal
Description Size in bits, for integer signal types. For ComSignalType UINT8_N and
UINT8_DYN the size shall be configured by ComSignalLength. For
ComSignalTypes FLOAT32 and FLOAT64 the size is already defined
by the signal type and therefore may be omitted.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 64
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComHandleId [ECUC_Com_00165]

Parent Container ComGroupSignal
Description The numerical value used as the ID.

This ID identifies signals and signal groups in the COM APIs using
Com_SignalIdType or Com_SignalGroupIdType parameter
respectively.
Multiplicity 0..1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value

43 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Multiplicity Pre-compile time X All Variants

Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name ComSignalDataInvalidValue [ECUC_Com_00391]

Parent Container ComGroupSignal
Description Defines the data invalid value of the signal.

In case the ComSignalType is UINT8, UINT16, UINT32, UINT64,

SINT8, SINT16, SINT32, SINT64 the string shall be interpreted as
defined in the chapter Integer Type in the AUTOSAR EcuC
specification. In case the ComSignalType is FLOAT32, FLOAT64 the
string shall be interpreted as defined in the chapter Float Type in the
AUTOSAR EcuC specification. In case the ComSignalType is
BOOLEAN the string shall be interpreted as defined in the chapter
Boolean Type in the AUTOSAR EcuC specification. In case the
ComSignal is a UINT8_N, UINT8_DYN the string shall be interpreted
as a decimal representation of the characters separated by blanks, e.g.
"97 98 100" means a string "abd", where the char "a" is in byte 0(lowest
address), "b" is in byte 1, and "d" is in byte 2 and (highest address).
For the ComSignalType UINT8_DYN the dynamic length shall be set to
the number of configured characters. An empty string "" shall be
interpreted as 0-sized dynamic signal.
Multiplicity 0..1
Type EcucStringParamDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local
dependency: In case of UINT8_N the length of
ComSignalDataInvalidValue has to be the same as ComSignalLength.

44 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComSignalEndianness [ECUC_Com_00157]

Parent Container ComGroupSignal
Description Defines the endianness of the signal’s network representation.
Multiplicity 1
Type EcucEnumerationParamDef
Range BIG_ENDIAN
LITTLE_ENDIAN
OPAQUE
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComSignalInitValue [ECUC_Com_00170]

Parent Container ComGroupSignal
Description Initial value for this signal. In case of UINT8_N the default value is a
string of length ComSignalLength with all bytes set to 0x00. In case of
UINT8_DYN the initial size shall be 0.

In case the ComSignalType is UINT8, UINT16, UINT32, UINT64,

SINT8, SINT16, SINT32, SINT64 the string shall be interpreted as
defined in the chapter Integer Type in the AUTOSAR EcuC
specification. In case the ComSignalType is FLOAT32, FLOAT64 the
string shall be interpreted as defined in the chapter Float Type in the
AUTOSAR EcuC specification. In case the ComSignalType is
BOOLEAN the string shall be interpreted as defined in the chapter
Boolean Type in the AUTOSAR EcuC specification. In case the
ComSignal is a UINT8_N, UINT8_DYN the string shall be interpreted
as a decimal representation of the characters separated by blanks, e.g.
"97 98 100" means a string "abd", where the char "a" is in byte 0(lowest
address), "b" is in byte 1, and "d" is in byte 2 and (highest address).
For the ComSignalType UINT8_DYN the dynamic length shall be set to
the number of configured characters. An empty string "" shall be
interpreted as 0-sized dynamic signal.
Multiplicity 0..1
Type EcucStringParamDef
Default Value 0
Regular Expression
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD

45 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE

Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local
dependency: In case of UINT8_N the length of ComSignalInitValue
has to be the same as ComSignalLength.

Name ComSignalLength [ECUC_Com_00437]

Parent Container ComGroupSignal
Description Description: For ComSignalType UINT8_N this parameter specifies the
length n in bytes. For ComSignalType UINT8_DYN it specifies the
maximum length in bytes. For all other types this parameter shall be
ignored.

The supported maximum length is restricted by the used transportation

system. For non TP-PDUs the maximum size of a PDU, and therefore
also of any included signal, is limited by the concrete bus
characteristic. For example, the limit is 8 bytes for CAN and LIN, 64
bytes for CAN FD and 254 for FlexRay.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComSignalType [ECUC_Com_00127]

Parent Container ComGroupSignal
Description The AUTOSAR type of the signal. Whether or not the signal is signed
or unsigned can be found by examining the value of this attribute. This
type could also be used to reserved appropriate storage in AUTOSAR
COM.
Multiplicity 1
Type EcucEnumerationParamDef
Range BOOLEAN
FLOAT32

46 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

FLOAT64
SINT16
SINT32
SINT64
SINT8
UINT16
UINT32
UINT64
UINT8
UINT8_DYN
UINT8_N
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Name ComTimeoutSubstitutionValue [ECUC_Com_10006]

Parent Container ComGroupSignal
Description The signal substitution value will be used in case of a timeout and
ComRxDataTimeoutAction is set to SUBSTITUTE. In case of UINT8_N
the default value is a string of length ComSignalLength with all bytes
set to 0x00.

In case ofUINT8_DYN the initial size shall be 0.

In case the ComSignalType is UINT8, UINT16, UINT32, UINT64,

SINT8, SINT16, SINT32, SINT64 the string shall be interpreted as
defined in the chapter Integer Type in the AUTOSAR EcuC
specification.

In case the ComSignalType is FLOAT32, FLOAT64 the string shall be

interpreted as defined in the chapter Float Type in the AUTOSAR EcuC
specification.

In case the ComSignalType is BOOLEAN the string shall be interpreted

as defined in the chapter Boolean Type in the AUTOSAR EcuC
specification.

In case the ComSignal is a UINT8_N, UINT8_DYN the string shall be

interpreted as a decimal representation of the characters separated by
blanks, e.g. "97 98 100" means a string "abd", where the char "a" is in
byte 0(lowest address), "b" is in byte 1, and "d" is in byte 2 and (highest
address). For the ComSignalType UINT8_DYN the dynamic length
shall be set to the number of configured characters. An empty string ""
shall be interpreted as 0-sized dynamic signal.
Multiplicity 0..1
Type EcucStringParamDef
Default Value

47 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Regular Expression
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComTransferProperty [ECUC_Com_00560]

Parent Container ComGroupSignal
Description Optionally defines whether this group signal shall contribute to the
TRIGGERED_ON_CHANGE transfer property of the signal group. If at
least one group signal of a signal group has the "ComTransferProperty"
configured all other group signals of that signal group shall have the
attribute configured as well.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range PENDING A change of the value of this group
signal shall not be considered in the
evaluation of the signal groups
ComTransferProperty.
TRIGGERED_ON_CHAN A change of the value of this group
GE signal shall be considered in the
evaluation of the signal groups
ComTransferProperty.
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

48 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComSystemTemplateSystemSignalRef [ECUC_Com_00002]

Parent Container ComGroupSignal
Description Reference to the ISignalToIPduMapping that contains a reference to
the ISignal (System Template) which this ComSignal (or
ComGroupSignal) represents.
Multiplicity 0..1
Type Foreign reference to I-SIGNAL-TO-I-PDU-MAPPING
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

Included Containers
Container Name Multiplicity Scope / Dependency
ComFilter 0..1 This container contains the configuration parameters of
the AUTOSAR COM module’s Filters.

Note: On sender side the container is used to specify

the transmission mode conditions.

SWS Item [ECUC_Com_00340]

Container Name ComIPdu
Description Contains the configuration parameters of the AUTOSAR COM
module’s I-PDUs.
Post-Build Variant true
Multiplicity
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Configuration Parameters

Name ComIPduCallout [ECUC_Com_00387]

Parent Container ComIPdu
Description This parameter defines the existence and the name of a callout
function for the corresponding I-PDU. If this parameter is omitted no
I-PDU callout shall take place for the corresponding I-PDU.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression

49 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Post-Build Variant false

Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name ComIPduCancellationSupport [ECUC_Com_00709]

Parent Container ComIPdu
Description Defines for I-PDUs with ComIPduType NORMAL: If the underlying
IF-modul supports cancellation of transmit requests.

Defines for I-PDUs with ComIPduType TP: If the underlying TP-module

supports RX and TX cancellation of ongoing requests.
Multiplicity 0..1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time –
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time –
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU
dependency: This parameter shall not be set to true if
ComCancellationSupport is set to false

Name ComIPduDirection [ECUC_Com_00493]

Parent Container ComIPdu
Description The direction defines if this I-PDU, and therefore the contributing
signals and signal groups, shall be sent or received.
Multiplicity 1
Type EcucEnumerationParamDef
Range RECEIVE
SEND
Post-Build Variant false
Value

50 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Value Configuration Pre-compile time X VARIANT-PRE-COMPILE

Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local
dependency: If configured to Sent also a ComTxIpdu container shall
be included, see ECUC_Com_00496

Name ComIPduHandleId [ECUC_Com_00175]

Parent Container ComIPdu
Description The numerical value used as the ID of this I-PDU. The
ComIPduHandleId is required by the API calls Com_RxIndication,
Com_TpRxIndication, Com_StartOfReception and Com_CopyRxData
to receive I-PDUs from the PduR (ComIP-duDirection: Receive), as
well as the PduId passed to an Rx-I-PDU-callout. For Tx-I-PDUs
(ComIPduDirection: Send), this handle Id is used for the APIs calls
Com_TxConfirmation, Com_TriggerTransmit, Com_TriggerIPDUSend
or Com_TriggerIPDUSendWithMetaData, Com_CopyTxData and
Com_TpTxConfirmation to transmit respectively confirm transmissions
of I-PDUs, as well as the PduId passed to the Tx-I-PDU-callout
configured with ComIPduCallout and/or
ComIPduTriggerTransmitCallout.
Multiplicity 0..1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default Value
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

Name ComIPduSignalProcessing [ECUC_Com_00119]

Parent Container ComIPdu
Description For the definition of the two modes Immediate and Deferred.
Multiplicity 1
Type EcucEnumerationParamDef
Range DEFERRED signal indication / confirmations are
deferred for example to a cyclic task
IMMEDIATE the signal indications / confirmations
are performed in Com_RxIndication/
Com_TxConfirmation

51 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Post-Build Variant true

Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComIPduTriggerTransmitCallout [ECUC_Com_00765]

Parent Container ComIPdu
Description If there is a trigger transmit callout defined for this I-PDU this
parameter contains the name of the callout function.
Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local

Name ComIPduType [ECUC_Com_00761]

Parent Container ComIPdu
Description Defines if this I-PDU is a normal I-PDU that can be sent unfragmented
or if this is a large I-PDU that shall be sent via the Transport Protocol of
the underlying bus.
Multiplicity 1
Type EcucEnumerationParamDef
Range NORMAL sent or received via normal L-PDU
TP sent or received via TP
Post-Build Variant true
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

52 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComIPduGroupRef [ECUC_Com_00206]

Parent Container ComIPdu
Description Reference to the I-PDU groups this I-PDU belongs to.
Multiplicity 0..*
Type Reference to ComIPduGroup
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComIPduSignalGroupRef [ECUC_Com_00519]

Parent Container ComIPdu
Description References to all signal groups contained in this I-Pdu
Multiplicity 0..*
Type Reference to ComSignalGroup
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComIPduSignalRef [ECUC_Com_00518]

Parent Container ComIPdu
Description References to all signals contained in this I-PDU.
Multiplicity 0..*
Type Reference to ComSignal
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value

53 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE

Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComPduIdRef [ECUC_Com_00711]

Parent Container ComIPdu
Description Reference to the "global" Pdu structure to allow harmonization of
handle IDs in the COM-Stack.
Multiplicity 1
Type Reference to Pdu
false
Post-Build Variant
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency

Included Containers
Container Name Multiplicity Scope / Dependency
ComIPduCounter 0..1 This optional container contains the configuration
parameters of PDU Counter.
ComIPduReplication 0..1 This optional container contains the information needed
for each I-PDU replicated.
ComTxIPdu 0..1 This container contains additional transmission related
configuration parameters of the AUTOSAR COM
module’s I-PDUs.

SWS Item [ECUC_Com_00496]

Container Name ComTxIPdu
Description This container contains additional transmission related configuration
parameters of the AUTOSAR COM module’s I-PDUs.
Configuration Parameters

54 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComMetaDataDefault [ECUC_Com_10005]

Parent Container ComTxIPdu
Description In case an I-PDU refers to a globally configured MetaDataType and no
explicit meta data is given for a send request (e.g. by using
Com_TriggerIPDUSendWithMetaData ), the AUTOSAR COM module
uses this configured default meta data for sending. The configured
string shall be interpreted as a decimal representation of the
characters separated by blanks, e.g. "97 98 100" means a string "abd",
where the char "a" is in byte 0(lowest address), "b" is in byte 1, and "d"
is in byte 2 and (highest address).
Multiplicity 0..1
Type EcucStringParamDef
Default Value
Regular Expression
Post-Build Variant false
Multiplicity
Post-Build Variant false
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: ECU
dependency: This parameter shall only be used in case
ComMetaDataSupport is enabled. The length of the default meta data
shall match the globally configured MetaDataLength of this I-PDU.

Name ComMinimumDelayTime [ECUC_Com_00181]

Parent Container ComTxIPdu
Description Defines the Minimum Delay Time (MDT) between successive
transmissions of this I-PDU in seconds. The MDT is independent of the
possible different transmission modes. There is only one minimum
delay time parameter for one I-PDU. The minimum delay timer is not
reset by changing the transmission mode. Hence, it is not allowed to
violate the minimum delay time by transmission mode changes. It is
not possible to monitor the minimum delay time for I-PDUs that are
requested using the Com_TriggerTransmit API.
Multiplicity 0..1
Type EcucFloatParamDef
Range [0 .. 3600]
Default Value
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value

55 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Multiplicity Pre-compile time X VARIANT-PRE-COMPILE

Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

Name ComTxIPduClearUpdateBit [ECUC_Com_00576]

Parent Container ComTxIPdu
Description Defines when the update-bits of signals or signal groups, contained in
this I-PDU, will be cleared.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range Confirmation The update-bits are cleared when the
transmission of the I-PDU was
confirmed. In case of Direct/N-Times
transmission mode the update bits will
be cleared with respect to the
confirmation behaviour of
SWS_Com_00305.
Transmit The update-bits are cleared directly
after the invocation of
PduR_ComTransmit.
TriggerTransmit The update-bits are cleared after the
I-PDU was fetched via
Com_TriggerTransmit.
Post-Build Variant true
Multiplicity
Post-Build Variant true
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

56 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

Name ComTxIPduUnusedAreasDefault [ECUC_Com_00017]

Parent Container ComTxIPdu
Description The AUTOSAR COM module fills not used areas of an I-PDU with this
byte pattern. This attribute is mandatory to avoid undefined behaviour.
This byte-pattern will be repeated throughout the I-PDU before any
init-values or update-bits were set.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Post-Build Variant false
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time X VARIANT-LINK-TIME,
VARIANT-POST-BUILD
Post-build time –
Scope / Dependency scope: local

Included Containers
Container Name Multiplicity Scope / Dependency
ComTxModeFalse 0..1 This container contains the configuration parameters of
the AUTOSAR COM module’s transmission modes in
the case the ComFilter evaluates to false.
ComTxModeTrue 0..1 This container contains the configuration parameters of
the AUTOSAR COM module’s transmission modes in
the case the ComFilter evaluates to true.

57 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

C History of Constraints and Specification Items

C.1 Constraint History of this Document according to AUTOSAR

R4.2.1
Initial document release.

C.2 Constraint History of this Document according to AUTOSAR

R4.2.2

C.2.1 Added Traceables in 4.2.2

[SWS_ComXf_00032]

C.2.2 Changed Traceables in 4.2.2

[SWS_ComXf_00028]

C.2.3 Deleted Traceables in 4.2.2

none

C.3 Constraint History of this Document according to AUTOSAR

R4.3.0

C.3.1 Added Traceables in 4.3.0

[SWS_ComXf_00033] [SWS_ComXf_00034] [SWS_ComXf_00035]

C.3.2 Changed Traceables in 4.3.0

[SWS_ComXf_00001] [SWS_ComXf_00004] [SWS_ComXf_00006]

[SWS_ComXf_00007] [SWS_ComXf_00008] [SWS_ComXf_00010]
[SWS_ComXf_00011]

58 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —
 Specification of COM Based Transformer
AUTOSAR CP Release 4.4.0

C.3.3 Deleted Traceables in 4.3.0

none

C.4 Constraint History of this Document according to AUTOSAR

R4.3.1

C.4.1 Added Traceables in 4.3.1

[SWS_ComXf_00036]

C.4.2 Changed Traceables in 4.3.1

[SWS_ComXf_00007] [SWS_ComXf_00023]

C.4.3 Deleted Traceables in 4.3.1

none

C.5 Constraint History of this Document according to AUTOSAR

R4.4.0

C.5.1 Added Traceables in 4.4.0

none

C.5.2 Changed Traceables in 4.4.0

[SWS_ComXf_00007] [SWS_ComXf_00020]

C.5.3 Deleted Traceables in 4.4.0

[SWS_ComXf_00001] [SWS_ComXf_00014]

59 of 59 Document ID 662: AUTOSAR_SWS_COMBasedTransformer

— AUTOSAR CONFIDENTIAL —