SNIP_CLASSIC_ECUCONFIGURATION_SECTION_4_3_3_De_nition_of_PDUs

4.3.3 Definition of PDUs In order to support the synchronization of Handle IDs (see section 4.4.1) two modules need to be able to refer to the same PDU object2. Therefore a generic Pdu container has been defined which does not belong to any module but is defined in the EcuC module. Since the PDU flowing through the COM-Stack does not belong to an individual module, the "virtual" module EcuC has been introduced in the ECU Configuration. This module is used to collect configuration information not associated with any specific standardized module. The EcucPduCollection may contain several "global" Pdu objects as shown in figure 4.5. Each Pdu may be representing an actual PduToFrameMapping3 from the AUTOSAR System Description[9] (the ECU Extract), therefore there is an optional reference to an element in the System Template. The reference is optional because the PDUs which are transported within an ECU only are not necessarily part of the ECU Extract. Especially PDUs handled by the Transport Protocol modules have no representation in the ECU Extract (There is a PDU coming over the bus which is represented by a Pdu object, but when the TP does the conversion and a new Pdu is created which then is forwarded to the upper layer. This created Pdu does not have a reference to a PduToFrameMapping). 2For the aspect of the configuration it does not matter what kind of PDU it is, i.e. I-PDU, L-PDU or N-PDU. 3The element PduToFrameMapping represents the actual PDU in the specific ECU (formerly known as PduInstance) Specification of ECU Configuration R4.0 Rev 3 System Template EcucPduCollection : EcucParamConfContainerDef upperMultiplicity = 1 lowerMultiplicity = 0 Pdu : EcucParamConfContainerDef upperMultiplicity = * lowerMultiplicity = 0 EcuC :EcucModuleDef upperMultiplicity = 1 lowerMultiplicity = 0 (from EcuC) Identifiable «atpPrototype» CoreCommunication::PduToFrameMapping + packingByteOrder: ByteOrderEnum + startPosition: Integer + updateIndicationBitPosition: Integer [0..1] SysTPduToFrameMappingRef : EcucForeignReferenceDef upperMultiplicity = 1 lowerMultiplicity = 0 destinationType = PDU-TO-FRAME-MAPPING PduLength : EcucIntegerParamDef min = 0 max = 4095 PduLengthTypeEnum : EcucEnumerationParamDef PduIdTypeEnum : EcucEnumerationParamDef UINT8 : EcucEnumerationLiteralDef UINT16 : EcucEnumerationLiteralDef UINT32 : EcucEnumerationLiteralDef +literal +literal +literal +literal +literal +reference +parameter +container +subContainer +parameter +parameter Figure 4.5: Generic Pdu Container EcucPduCollection SWS Item [EcuC002_Conf] Container Name EcucPduCollection Description Collection of all Pdu objects flowing through the Com-Stack. Configuration Parameters Name PduIdTypeEnum [EcuC041_Conf] Description The PduIdType is used within the entire AUTOSAR Com Stack except for bus drivers. The size of this global type depends on the maximum number of PDUs used within one software module. If no software module deals with more PDUs that 256, this type can be set to uint8. If at least one software module handles more than 256 PDUs, this type must be set to uint16. See AUTOSAR_SWS_CommunicationStackTypes for more details. Multiplicity