An ADC converts an analogue signal at an input pin to a digital value. The analogue signal are quantified to a maximum number of different levels defined by the resolution of the ADC. The Accuracy of the ADC is important for the overall functionality. mmt.qualifiedName="ADC" atpObject Defines the action that is going to be performed when a limit is reached. - Clipping: Logical value is limited to minimal or maximal range of the value range. E.g. The max. resolution of an ADC is at 5V represented 0xFF; in case off clipping a voltage of 6V is also represented as 0xFF; - Undefined: Exceeding the resolution results in an undefined representation of the logical value. - Default: Exceeding the resolution results in a predefined default value. The default value might be a value, which report the status to the application e.g. as an error condition. - Other: A predefined function occur in order to prevent a undefined logical value. A typical application is a "Soft-Clipping" in a logarithmic form at the limit of the resolutions in audio applications. The according methods have to be specified in the signal description. mmt.qualifiedName="ADC.behaviourAtLimit";pureMM.maxOccurs="1";pureMM.minOccurs="1" An ADC converts an analogue signal at an input pin to a digital value. The analogue signal are quantified to a maximum number of different levels defined by the resolution of the ADC. The Accuracy of the ADC is important for the overall functionality. mmt.qualifiedName="ADC" atpObject mmt.qualifiedName="ARLimit" atpObject mmt.qualifiedName="ARLimit.value";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.roleElement="false";xml.roleWrapperElement="false";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="ARLimit" atpObject mmt.qualifiedName="ARLimit.intervalType";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="ARLimit" atpObject Implicit base class of all classes in metamodel. mmt.qualifiedName="ARObject" atpObject checksum calculated from the * attributes * aggregations and aggregated non-identifiables * references mmt.qualifiedName="ARObject.checksum";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true";xml.name="S" the timestamp of the creation or modification of an instance, its attributes, references or aggregated non-identifiables. mmt.qualifiedName="ARObject.timestamp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true";xml.name="T" AUTOSAR package, allowing to create top level packages to structure the contained ARElements. ARPackages are open sets, which means that in a file based description system, multiple files can be used to partially describe the contents of a package. This is an extended version of MSR's SW-SYSTEM. mmt.qualifiedName="ARPackage" atpObject Elements that are part of this package mmt.qualifiedName="element.ARPackage";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Contained sub packages. mmt.qualifiedName="subPackage.ARPackage";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable AUTOSAR package, allowing to create top level packages to structure the contained ARElements. ARPackages are open sets, which means that in a file based description system, multiple files can be used to partially describe the contents of a package. This is an extended version of MSR's SW-SYSTEM. mmt.qualifiedName="ARPackage" atpObject Root element of an AUTOSAR description, also the root element in corresponding XML documents. mmt.qualifiedName="AUTOSAR";xml.globalElement="true" atpObject mmt.qualifiedName="AUTOSAR.adminData";pureMM.maxOccurs="1";pureMM.minOccurs="0" Top level packages of a description. mmt.qualifiedName="topLevelPackage.AUTOSAR";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Root element of an AUTOSAR description, also the root element in corresponding XML documents. mmt.qualifiedName="AUTOSAR";xml.globalElement="true" atpObject Root element of an AUTOSAR description, also the root element in corresponding XML documents. mmt.qualifiedName="AUTOSAR";xml.globalElement="true" atpObject Maximum allowable deviation mmt.qualifiedName="AbsoluteTolerance" atpObject Maximum allowable deviation in duration (in seconds) mmt.qualifiedName="AbsoluteTolerance.absolute";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum allowable deviation mmt.qualifiedName="AbsoluteTolerance" atpObject Each frame in FlexRay is identified by its slot id and communication cycle. A description is provided by the usage of AbsolutelyScheduledTiming. In the static segment a frame can be sent multiple times within one communication cycle. For describing this case multiple AbsolutelyScheduledTimings have to be used. The main use case would be that a frame is sent twice within one communication cycle. mmt.qualifiedName="AbsolutelyScheduledTiming" atpObject The communication cycle where the frame is sent. mmt.qualifiedName="communicationCycle.AbsolutelyScheduledTiming";pureMM.maxOccurs="1";pureMM.minOccurs="1" In the static part the SlotID defines the slot in which the frame is transmitted. The SlotID also determines, in combination with FlexrayCluster::numberOfStaticSlots, whether the frame is sent in static or dynamic segment. In the dynamic part, the slot id is equivalent to a priority. Lower dynamic slot ids are all sent until the end of the dynamic segment. Higher numbers, which were ignored that time, have to wait one cycle and then must try again. minValue: 1 maxValue: 2047 mmt.qualifiedName="AbsolutelyScheduledTiming.slotID";pureMM.maxOccurs="1";pureMM.minOccurs="1" Each frame in FlexRay is identified by its slot id and communication cycle. A description is provided by the usage of AbsolutelyScheduledTiming. In the static segment a frame can be sent multiple times within one communication cycle. For describing this case multiple AbsolutelyScheduledTimings have to be used. The main use case would be that a frame is sent twice within one communication cycle. mmt.qualifiedName="AbsolutelyScheduledTiming" atpObject HW Element Actuator definition. mmt.qualifiedName="ActuatorHW" atpObject Defines the way the actuator is seen after power on. On Bi-Stable or Multistable actuators the software has to know the status of this device after reset or Power On. Each actuator has a control input that determines its behaviour mmt.qualifiedName="ActuatorHW.defaultPositionType";pureMM.maxOccurs="1";pureMM.minOccurs="0" If there is a specific default value is available. E.g. Valve status = off; mmt.qualifiedName="ActuatorHW.defaultPositionValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the most typical electrical behaviour of the system. This information is necessary for the ECU generation process and for tools which check for later interaction of the different component. (avoid resonance's, planning of the ECU power management). mmt.qualifiedName="ActuatorHW.electricalType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Number of activation cycles the actuator is designed for. mmt.qualifiedName="ActuatorHW.endurance";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the way the movement is controlled by AUTOSAR. Positional feedback can be provided by the actuator by the conglomeration of the requisite actuator and sensor primitives. mmt.qualifiedName="ActuatorHW.movement";pureMM.maxOccurs="1";pureMM.minOccurs="0" HW Element Actuator definition. mmt.qualifiedName="ActuatorHW" atpObject <adminData> can be used to set administrative information for an element. This administration information is to be treated as metadata such as revision id or state of the file. There are basically four kinds of metadata * The language and/or used laguages. * Revision information covering e.g. revision number, state, release date, changes. Note that this information can be given in general as well as related to a particular company. * Document metadata specific for a company * Formatting controls that can affect layouts for example. * Revision information for the element. mmt.qualifiedName="AdminData" atpObject This attribute specifies the master language of the document or the document fragment. The master language is the one in which the document is maintained and from which the other languages are derived from. mmt.qualifiedName="AdminData.language";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" Use <usedLanguages> to enter all other languages, in addition to the document language, which are used an a document or a section of a document. mmt.qualifiedName="AdminData.usedLanguages";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Use <docRevision> , to generate information on the corresponding document version. mmt.qualifiedName="AdminData.docRevision";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="50";xml.typeElement="false";xml.typeWrapperElement="false" <sdg> (Special Data Group) is a backdoor used to handle elements that has not yet been defined in a DTD. The <sdg> is a containder for one or several <sd> that defines new elements and carries the information. Special Data should only be used moderately since all elements should be defined in the dtd. Thereby should SDG be considered as a temporary sollution when elements are missing. If a <sdgCaption> element is created along with a <shortName> it is possible to reference the <sdg> structure via a <xref>. mmt.qualifiedName="AdminData.sdg";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="60";xml.typeElement="false";xml.typeWrapperElement="false" <adminData> can be used to set administrative information for an element. This administration information is to be treated as metadata such as revision id or state of the file. There are basically four kinds of metadata * The language and/or used laguages. * Revision information covering e.g. revision number, state, release date, changes. Note that this information can be given in general as well as related to a particular company. * Document metadata specific for a company * Formatting controls that can affect layouts for example. * Revision information for the element. mmt.qualifiedName="AdminData" atpObject No filtering is performed so that the message always passes. mmt.qualifiedName="Always" atpObject These are the common attributes for both, the ADC and the DAC. mmt.qualifiedName="AnalogueIO" atpObject There is a number of different conversion error in an ADC or DAC like non-linearity and absolute error. The accuracy is defined as the total error and it can be expressed as a deviation from its nominal value by e.g. 0.5, 1.0, 1.5 or 2.0 LSB. mmt.qualifiedName="AnalogueIO.accuracy";pureMM.maxOccurs="1";pureMM.minOccurs="1" ADC: The conversion time is the definition how long it takes for an ADC to convert an analogue signal to a digital value. DAC: The conversion time is the definition how long it takes for a DAC to convert a digital value to an analogue signal. mmt.qualifiedName="AnalogueIO.conversionTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" The analogue comparator of an ADC must be connected to a voltage reference. An external voltage is usually connected to one low and one high voltage reference input pin. For an internal DAC it is normally only one voltage reference input. The low voltage reference input is internally connected to the analogue ground. mmt.qualifiedName="externalReferenceVoltage.AnalogueIO";pureMM.maxOccurs="1";pureMM.minOccurs="0" An ADC or DAC can operate in continuous, single or sequential mode. In the continuous mode the conversion is automatically repeated after a completion. In single shot only one conversion is performed. For the sequential mode can a predefined number of different analogue channels be converted. mmt.qualifiedName="AnalogueIO.mode";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the design of a simple multiplexer used by an ADC. Example A 2:8-multiplexer has 2 input channels and 8 registers. M is the second value. mmt.qualifiedName="AnalogueIO.multiplexedM";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the design of a simple multiplexer used by an ADC. Example A 2:8-multiplexer has 2 input channels and 8 registers. N is the first value. mmt.qualifiedName="AnalogueIO.multiplexedN";pureMM.maxOccurs="1";pureMM.minOccurs="0" For an Analogue to Digital Converter the resolution defines the number of different voltage levels, which are converted to a digital value. For example, an ADC with 10-bits resolution have the ability to convert an analogue value into 1024 different digital values. Unit: Bits mmt.qualifiedName="AnalogueIO.resolution";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of Bits used to store the digital value. mmt.qualifiedName="AnalogueIO.width";pureMM.maxOccurs="1";pureMM.minOccurs="1" This is a plain annotation which does not have further formal data. mmt.qualifiedName="Annotation" atpObject This is a user-defined error that is associated with an element of an AUTOSAR interface. It is specific for the particular functionality or service provided by the AUTOSAR software component. mmt.qualifiedName="ApplicationError" atpObject The RTE generator is forced to assign this value to the corresponding error symbol. Note that for error codes certain ranges are predefined (see RTE specification). mmt.qualifiedName="ApplicationError.errorCode";pureMM.maxOccurs="1";pureMM.minOccurs="1" This is a user-defined error that is associated with an element of an AUTOSAR interface. It is specific for the particular functionality or service provided by the AUTOSAR software component. mmt.qualifiedName="ApplicationError" atpObject In client server communication, the server may return any value within the application error range. mmt.qualifiedName="ApplicationErrorMapping" atpObject Reference to the SystemSignal with the ApplicationError. mmt.qualifiedName="ApplicationErrorMapping.systemSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" In client server communication, the server may return any value within the application error range. mmt.qualifiedName="ApplicationErrorMapping" atpObject The ApplicationSoftwareComponentType is used to represent the application software. mmt.qualifiedName="ApplicationSoftwareComponentType" atpObject,atpType mmt.qualifiedName="ArCalprmRef" atpObject This represents the referred arCalprm. mmt.qualifiedName="ArCalprmRef.arCalprm";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="ArCalprmRef" atpObject mmt.qualifiedName="ArCalprmRef_CalprmElementPrototype" atpObject,instanceRef mmt.qualifiedName="ArCalprmRef_CalprmElementPrototype.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ArCalprmRef_CalprmElementPrototype.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ArCalprmRef_CalprmElementPrototype.calprmElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="ArCalprmRef_CalprmElementPrototype" atpObject,instanceRef An argument of an operation, much like a data element, but also carries direction information and is associated with a particular operation. mmt.qualifiedName="ArgumentPrototype" atpObject,atpPrototype This attribute controls the direction of the ArgumentPrototype according to the DirectionKind. mmt.qualifiedName="ArgumentPrototype.direction";pureMM.maxOccurs="1";pureMM.minOccurs="1" An argument of an operation, much like a data element, but also carries direction information and is associated with a particular operation. mmt.qualifiedName="ArgumentPrototype" atpObject,atpPrototype mmt.qualifiedName="ArrayElement" atpObject,atpPrototype The maximum number of elements that the array can contain. mmt.qualifiedName="ArrayElement.maxNumberOfElements";pureMM.maxOccurs="1";pureMM.minOccurs="1" atpMaxMultiplicity mmt.qualifiedName="ArrayElement" atpObject,atpPrototype A constant array, which refers to its elements by index. mmt.qualifiedName="ArraySpecification" atpObject,atpPrototype Elements of array. mmt.qualifiedName="element.ArraySpecification";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A constant array, which refers to its elements by index. mmt.qualifiedName="ArraySpecification" atpObject,atpPrototype mmt.qualifiedName="ArrayType" atpObject,atpType This represents a formal representation of the ArrayElement within ArrayType. mmt.qualifiedName="ArrayType.element";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="ArrayType" atpObject,atpType AssemblyConnectorPrototypes are exclusively used to connect ComponentPrototypes in the context of a CompositionType. mmt.qualifiedName="AssemblyConnectorPrototype" atpObject,atpStructureElement Instance of providing port. mmt.qualifiedName="provider.AssemblyConnectorPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" Instance of requiring port. mmt.qualifiedName="requester.AssemblyConnectorPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" AssemblyConnectorPrototypes are exclusively used to connect ComponentPrototypes in the context of a CompositionType. mmt.qualifiedName="AssemblyConnectorPrototype" atpObject,atpStructureElement mmt.qualifiedName="AssemblyConnectorPrototype_provider" atpObject,instanceRef mmt.qualifiedName="AssemblyConnectorPrototype_provider.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="AssemblyConnectorPrototype_provider.pPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="AssemblyConnectorPrototype_provider" atpObject,instanceRef mmt.qualifiedName="AssemblyConnectorPrototype_requester" atpObject,instanceRef mmt.qualifiedName="AssemblyConnectorPrototype_requester.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="AssemblyConnectorPrototype_requester.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="AssemblyConnectorPrototype_requester" atpObject,instanceRef An AssemblyHWConnection is established between at least two HWPorts provided by different HWElements. The AssemblyHWConnection can only be established between HWPorts on the same hierarchical level. To connect accross hierarchical levels use the DelegationHWConnection. mmt.qualifiedName="AssemblyHWConnection" atpObject References to HWPorts connected by this AssemblyHWConnection. mmt.qualifiedName="AssemblyHWConnection.hwPort";pureMM.maxOccurs="-1";pureMM.minOccurs="2" An AssemblyHWConnection is established between at least two HWPorts provided by different HWElements. The AssemblyHWConnection can only be established between HWPorts on the same hierarchical level. To connect accross hierarchical levels use the DelegationHWConnection. mmt.qualifiedName="AssemblyHWConnection" atpObject Schedule entry for an Assign Frame Id master request. mmt.qualifiedName="AssignFrameIdTiming" atpObject The frame whose identifier is set by this assignment. mmt.qualifiedName="AssignFrameIdTiming.assignedFrameTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="1" Schedule entry for an Assign Frame Id master request. mmt.qualifiedName="AssignFrameIdTiming" atpObject Schedule entry for an Assign NAD master request. mmt.qualifiedName="AssignNadTiming" atpObject The newly assigned NAD value (valid range 1..126) mmt.qualifiedName="AssignNadTiming.newNad";pureMM.maxOccurs="1";pureMM.minOccurs="1" Schedule entry for an Assign NAD master request. mmt.qualifiedName="AssignNadTiming" atpObject A LIN specific extension of the common RelativelyScheduledTiming The extension describes the LIN specific assignment frames. mmt.qualifiedName="AssignmentTimingType" atpObject The LIN slaves controller who is target of this assignment. mmt.qualifiedName="AssignmentTimingType.assignedController";pureMM.maxOccurs="1";pureMM.minOccurs="1" An asynchronous server call-point is used for asynchronous invocation of an operation prototype. It is associated with AsynchronousServerCallReturnsEvent, this RTEEvent notifies the completion of the required operation or a timeout, this event can be waited for or it can lead to the invocation of a runnable. IMPORTANT: a server-call-point cannot be used concurrently. Once the client runnable has made the invocation, the server-call-point cannot be used until the call returns (or an error occurs!) at which point the server call-point becomes available again... mmt.qualifiedName="AsynchronousServerCallPoint" atpObject This event is raised when an asynchronous server call is finished. mmt.qualifiedName="AsynchronousServerCallReturnsEvent" atpObject The referenced server call point mmt.qualifiedName="event.eventSource";pureMM.maxOccurs="1";pureMM.minOccurs="1" This event is raised when an asynchronous server call is finished. mmt.qualifiedName="AsynchronousServerCallReturnsEvent" atpObject mmt.qualifiedName="BaseType" atpObject This is the absolute size of the basetype. In this case the BaseType is of fixed lenght. mmt.qualifiedName="BaseTypeAbsSize" atpObject Describes the length of the data type specified in the container in bits. mmt.qualifiedName="BaseTypeAbsSize.baseTypeSize";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This is the absolute size of the basetype. In this case the BaseType is of fixed lenght. mmt.qualifiedName="BaseTypeAbsSize" atpObject This BaseType is defined directly (as opposite to a derived BaseType) mmt.qualifiedName="BaseTypeDirectDefinition" atpObject This specifies, how an object of the current BaseType is encode eg. in an ECU in a message sequence. mmt.qualifiedName="BaseTypeDirectDefinition.baseTypeEncoding";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="90" describes the alignment of the memory object in bits. E.g. "1" specifies, that the object in question is aligned to a byte while "32" specifies that it is aligned four byte. mmt.qualifiedName="BaseTypeDirectDefinition.memAlignment";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="100" This element specifies the byte order of the parent element. The byte order is defined with the attribute TYPE. Possible values are: * MOST-SIGNIFICANT-BYTE-FIRST * MOST-SIGNIFICANT-BYTE-LAST mmt.qualifiedName="BaseTypeDirectDefinition.byteOrder";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="110" This BaseType is defined directly (as opposite to a derived BaseType) mmt.qualifiedName="BaseTypeDirectDefinition" atpObject This BaseType is defined by referring to anotherone. This indirect definition allows to create alias base types. mmt.qualifiedName="BaseTypeIndirectDefinition" atpObject This is the baseType on which the indirectly defined base type is derived. mmt.qualifiedName="BaseTypeIndirectDefinition.baseType";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="130" This BaseType is defined by referring to anotherone. This indirect definition allows to create alias base types. mmt.qualifiedName="BaseTypeIndirectDefinition" atpObject This is the maximum size of a BaseType in case of a dynamic BaseType. mmt.qualifiedName="BaseTypeMaxSize" atpObject Describes the maximum length of the BaseType in bits mmt.qualifiedName="BaseTypeMaxSize.maxBaseTypeSize";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" This is the maximum size of a BaseType in case of a dynamic BaseType. mmt.qualifiedName="BaseTypeMaxSize" atpObject Boolean constant expression. mmt.qualifiedName="BooleanLiteral" atpObject,atpPrototype The Boolean value. mmt.qualifiedName="BooleanLiteral.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Boolean constant expression. mmt.qualifiedName="BooleanLiteral" atpObject,atpPrototype Configuration parameter type for Boolean. allowed values are true and false. mmt.qualifiedName="BooleanParamDef";xml.sequenceOffset="0" atpObject Default value of the boolean configuration parameter. mmt.qualifiedName="BooleanParamDef.defaultValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" Configuration parameter type for Boolean. allowed values are true and false. mmt.qualifiedName="BooleanParamDef";xml.sequenceOffset="0" atpObject This datatype represents a set containing the logical value true and false mmt.qualifiedName="BooleanType" atpObject,atpType Representing a configuration value of definition type BooleanParamDef mmt.qualifiedName="BooleanValue" atpObject Stores the value of the Boolean parameter. mmt.qualifiedName="BooleanValue.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Representing a configuration value of definition type BooleanParamDef mmt.qualifiedName="BooleanValue" atpObject Time information for ECU and PU startup. mmt.qualifiedName="BootTime" atpObject Time it takes to come from a completely powered down state to the HWInit state in seconds. mmt.qualifiedName="BootTime.coldStartTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Time it takes from the reset initiation to the HWInit state in seconds. mmt.qualifiedName="BootTime.resetTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Time information for ECU and PU startup. mmt.qualifiedName="BootTime" atpObject This element is the same as function here as in a HTML document i.e. it forces a line break. mmt.qualifiedName="Br" atpObject Specifies the behavior of a BSW module or a BSW cluster w.r.t. the code entities visible by the BSW Scheduler. It is possible to have several different BswBehaviors referring to the same BswModuleDescription. mmt.qualifiedName="BswBehavior" atpObject A code entity for which the behavior is described mmt.qualifiedName="BswBehavior.entity";pureMM.maxOccurs="-1";pureMM.minOccurs="1" An event required by this module behavior. mmt.qualifiedName="BswBehavior.event";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This specifies an ExclusiveArea for this BswBehavior. The exclusiveArea is local to the module or module cluster. mmt.qualifiedName="BswBehavior.exclusiveArea";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The module specification fulfilled by this behavior. mmt.qualifiedName="BswBehavior.module";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the behavior of a BSW module or a BSW cluster w.r.t. the code entities visible by the BSW Scheduler. It is possible to have several different BswBehaviors referring to the same BswModuleDescription. mmt.qualifiedName="BswBehavior" atpObject A cyclically recurring BSW event. The cyclic activity has to be implemented by the BSW Scheduler. mmt.qualifiedName="BswCyclicEvent" atpObject Requirement for the cycle time (in seconds) by which this event is triggered. mmt.qualifiedName="BswCyclicEvent.cycleTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" A cyclically recurring BSW event. The cyclic activity has to be implemented by the BSW Scheduler. mmt.qualifiedName="BswCyclicEvent" atpObject Defines an event which is used to trigger a schedulable entity of this BSW module or cluster. The event is local to the BSW module or cluster. The short name of the class instance is intended as an input to configure the required API of the BSW Scheduler. mmt.qualifiedName="BswEvent" atpObject This entity is started by the event. mmt.qualifiedName="BswEvent.startsOnEvent";pureMM.maxOccurs="1";pureMM.minOccurs="1" Contains the implementation specific information in addition to the generic specification (BswModuleDescription and BswBehavior). It is possible to have several different BswImplementations referring to the same BswBehavior. mmt.qualifiedName="BswImplementation" atpObject Major version number of AUTOSAR specification on which this implementation is based on. mmt.qualifiedName="BswImplementation.arMajorVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minor version number of AUTOSAR specification on which this implementation is based on. mmt.qualifiedName="BswImplementation.arMinorVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Patch level version number of AUTOSAR specification on which this implementation is based on. mmt.qualifiedName="BswImplementation.arPatchVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" The behavior of this implementation. mmt.qualifiedName="BswImplementation.behavior";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the module configuration that contains preconfigured (i.e. fixed) configuration parameters. mmt.qualifiedName="BswImplementation.preconfiguredConfiguration";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the recommended configuration for this module. mmt.qualifiedName="BswImplementation.recommendedConfiguration";pureMM.maxOccurs="1";pureMM.minOccurs="0" Hardware resource required by this BswImplementation mmt.qualifiedName="BswImplementation.requiredHW";pureMM.maxOccurs="-1";pureMM.minOccurs="0" In driver modules which can be instantiated several times on a single ECU, BSW00347 requires that the name of APIs is extended by the VendorId and a vendor specific name. This parameter is used to specify the vendor specific name. In total, the implementation specific name is generated as follows: <ModuleName>_<VendorId>_ <VendorApiInfix><Api name from SWS>. E.g. assuming that the VendorId of the implementor is 123 and the implementer chose a VendorApiInfix of "v11r456" a api name Can_Write defined in the SWS will translate to Can_123_v11r456Write. This attribute is mandatory for all modules with upper multiplicity > 1. It shall not be used for modules with upper multiplicity =1. mmt.qualifiedName="BswImplementation.vendorApiInfix";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Vendor Specific ModuleDef used in this BSW module description. mmt.qualifiedName="BswImplementation.vendorSpecificModuleDef";pureMM.maxOccurs="1";pureMM.minOccurs="1" Contains the implementation specific information in addition to the generic specification (BswModuleDescription and BswBehavior). It is possible to have several different BswImplementations referring to the same BswBehavior. mmt.qualifiedName="BswImplementation" atpObject BSW module entity, which is designed to be triggered by an interrupt. mmt.qualifiedName="BswInterruptEntity" atpObject Category of the interrupt mmt.qualifiedName="BswInterruptEntity.interruptCategory";pureMM.maxOccurs="1";pureMM.minOccurs="1" Allows a textual documentation of the intended interrupt source. mmt.qualifiedName="BswInterruptEntity.interruptSource";pureMM.maxOccurs="1";pureMM.minOccurs="1" BSW module entity, which is designed to be triggered by an interrupt. mmt.qualifiedName="BswInterruptEntity" atpObject This class collects the dependencies of a BSW module or cluster on a certain other BSW module in an abstract way. mmt.qualifiedName="BswModuleDependency" atpObject Indicates a callback expected to be called from another module and implemented by this module. mmt.qualifiedName="BswModuleDependency.expectedCallback";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Indicates an entry into another modules which is required by this module. mmt.qualifiedName="BswModuleDependency.requiredEntry";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A single item (example: Nv block) for which the quality of a service is defined. mmt.qualifiedName="BswModuleDependency.serviceItem";pureMM.maxOccurs="-1";pureMM.minOccurs="0" AUTOSAR identifier of the target module of which the dependencies are defined. mmt.qualifiedName="BswModuleDependency.targetModuleId";pureMM.maxOccurs="1";pureMM.minOccurs="1" This class collects the dependencies of a BSW module or cluster on a certain other BSW module in an abstract way. mmt.qualifiedName="BswModuleDependency" atpObject Root element for the description of a single BSW module or BSW cluster. In case it describes a BSW module, the short name of this element equals the name of the BSW module. mmt.qualifiedName="BswModuleDescription" atpObject,atpStructureElement Describes the dependency to another BSW module. mmt.qualifiedName="BswModuleDescription.bswModuleDependency";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Refers to the BSW Module Identifier defined by the AUTOSAR standard. mmt.qualifiedName="BswModuleDescription.moduleId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies a callback, which will be called from this module if required by another module. mmt.qualifiedName="BswModuleDescription.outgoingCallback";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specifies an entry provided by this module which can be called by other modules. This includes "main" functions and interrupt routines, but not callbacks (because the signature of a callback is defined by the calller). mmt.qualifiedName="BswModuleDescription.providedEntry";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Root element for the description of a single BSW module or BSW cluster. In case it describes a BSW module, the short name of this element equals the name of the BSW module. mmt.qualifiedName="BswModuleDescription" atpObject,atpStructureElement Specifies the smallest code fragment which can be described for a BSW module or cluster within AUTOSAR. mmt.qualifiedName="BswModuleEntity" atpObject The module entity can activate this event. mmt.qualifiedName="BswModuleEntity.activationPoint";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The entry of another (or the same) BSW module which is called by this entry (usually via C function call). This information allows to set up a model of call chains. mmt.qualifiedName="BswModuleEntity.calledEntry";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The BswModuleEntity can enter/leave the referenced exclusive area through explicit API calls. mmt.qualifiedName="BswModuleEntity.canEnterExclusiveArea";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The module entity can cancel the activation of the event (this only makes sense, if the event has a non-zero delay time). mmt.qualifiedName="BswModuleEntity.cancellationPoint";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The entry which is implemented by this module entity. mmt.qualifiedName="BswModuleEntity.implementedEntry";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the smallest code fragment which can be described for a BSW module or cluster within AUTOSAR. mmt.qualifiedName="BswModuleEntity" atpObject This class represents a single API entry (C-function prototype) into the BSW module or cluster. The name of the C-function is equal to the short name of this element with one exception: In case of multiple instances of a module on the same CPU, special rules for "infixes" apply, see description of class BswImplementation. mmt.qualifiedName="BswModuleEntry" atpObject the type of call associated with this service mmt.qualifiedName="BswModuleEntry.callType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the excution context which is required (in case of entries into this module) or guaranteed (in case of entries called from this module) for this service. mmt.qualifiedName="BswModuleEntry.executionContext";pureMM.maxOccurs="1";pureMM.minOccurs="1" true: This calls a synchronous service, i.e. the service is completed when the call returns. false: The service (on semantical level) may not be complete when the call returns. mmt.qualifiedName="BswModuleEntry.isSynchronous";pureMM.maxOccurs="1";pureMM.minOccurs="1" Refers to the service identifier of the Standardized Interfaces of AUTOSAR basic software. mmt.qualifiedName="BswModuleEntry.serviceId";pureMM.maxOccurs="1";pureMM.minOccurs="1" This class represents a single API entry (C-function prototype) into the BSW module or cluster. The name of the C-function is equal to the short name of this element with one exception: In case of multiple instances of a module on the same CPU, special rules for "infixes" apply, see description of class BswImplementation. mmt.qualifiedName="BswModuleEntry" atpObject BSW module entity, which is designed for control by the BSW Scheduler. It implements a so-called "main" function. mmt.qualifiedName="BswSchedulableEntity" atpObject A BSW event, which can happen sporadically. The event is activated/cancelled by explicit calls from the module to the BSW Scheduler. There a two purposes for such an event: - cause a context switch, e.g. from an ISR context into a task context - implement a time delay mmt.qualifiedName="BswSporadicEvent" atpObject Requirement for the delay time (in seconds) after which this event is triggered. The delay is counted from the activation of this event by a BswModuleEntitiy until the actual triggering of another BswModuleEntity associated by the event. mmt.qualifiedName="BswSporadicEvent.delayTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" A BSW event, which can happen sporadically. The event is activated/cancelled by explicit calls from the module to the BSW Scheduler. There a two purposes for such an event: - cause a context switch, e.g. from an ISR context into a task context - implement a time delay mmt.qualifiedName="BswSporadicEvent" atpObject Description of a buffer. It is used to describe input and output buffers. Buffers can also be configurable direction. mmt.qualifiedName="Buffer" atpObject The amount of buffers with the attributes size and type. mmt.qualifiedName="Buffer.number";pureMM.maxOccurs="1";pureMM.minOccurs="0" The size of the Buffer. Unit: Byte mmt.qualifiedName="Buffer.size";pureMM.maxOccurs="1";pureMM.minOccurs="1" Either input, output or configurable buffer. mmt.qualifiedName="Buffer.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" Description of a buffer. It is used to describe input and output buffers. Buffers can also be configurable direction. mmt.qualifiedName="Buffer" atpObject In order to avoid signal reflection and oscillation of the Technical Signal represen-tation the impedance on communication lines have to be defined and matched at the signal destination and the signal source. Some examples: A High-speed CAN network with a twisted pair cable works optimal with an overall impedance of 60 Ohms represented by a 120 Ohm resistor in the ECU at the begin-ning of the network and 120 Ohm in the ECU at the end of a linear network topology. For Low-speed CAN networks in many cases termination resistors of 820 Ohm each are distributed on several ECUs to get good balance between system scalability and signal integrity in real networks without a fixed network topology. The lower bandwidth can tolerate some impedance mismatch. For LIN networks recessive termination is used: The inactive bus signal level is defined by resistors tied to a defined voltage level. An important attribute for communication lines is the presence of a termination resistor and the value of this resistor. mmt.qualifiedName="BusTermination" atpObject Switchable termination describes a technology were the termination resistors can be switched or changed by extra hardware and therefore is under control of software. Main scope of a switchable termination is to adopt the termination of an individual ECU to the network topology of a specific car, e. g modules for extra car options can use this method to be incorporated in a wide range of different car types. The active termination is described by the values for each termination value. E.g. 120, 820, 12k. No termination is represented by values greater than 100 k. The attributes value and switchable are exclusive to each other. mmt.qualifiedName="BusTermination.activeSwitchable";pureMM.maxOccurs="1";pureMM.minOccurs="0" To improve the signal integrity on communication busses with a differential electrical signal representation on the physical layer, common mode chokes are used. They suppress common mode DC noise on CAN, FlexRay and Ethernet networks. Depending on the network topology common mode chokes of an ECU have to be taken in to account when adding ECUs to a network during design phase. Typically chokes are used on CAN, FlexRay, LVDS. mmt.qualifiedName="BusTermination.choke";pureMM.maxOccurs="1";pureMM.minOccurs="0" To improve the EMC behaviour of communication busses common dedicated EMC Filters are used. They suppress frequencies outside the range, which is needed for the communication of the specific bus E.g. some small capacitors in parallel to ground, resistors and inductivities in series are added to the bus lines in order to prevent the higher harmonics stimulated by the communication on the network The information about the termination is used with in the system configuration process, where the placement of an ECU within a car architecture is generated. mmt.qualifiedName="BusTermination.emcFilter";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describe a technology were the termination is split in to individual resistors with a capacitive coupling to ground. This technology improves the signal quality. mmt.qualifiedName="BusTermination.split";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describe the nominal Value of the termination resistor at the ECU as seen from the communication network. mmt.qualifiedName="BusTermination.value";pureMM.maxOccurs="1";pureMM.minOccurs="0" In order to avoid signal reflection and oscillation of the Technical Signal represen-tation the impedance on communication lines have to be defined and matched at the signal destination and the signal source. Some examples: A High-speed CAN network with a twisted pair cable works optimal with an overall impedance of 60 Ohms represented by a 120 Ohm resistor in the ECU at the begin-ning of the network and 120 Ohm in the ECU at the end of a linear network topology. For Low-speed CAN networks in many cases termination resistors of 820 Ohm each are distributed on several ECUs to get good balance between system scalability and signal integrity in real networks without a fixed network topology. The lower bandwidth can tolerate some impedance mismatch. For LIN networks recessive termination is used: The inactive bus signal level is defined by resistors tied to a defined voltage level. An important attribute for communication lines is the presence of a termination resistor and the value of this resistor. mmt.qualifiedName="BusTermination" atpObject This element specifies the byte order of the parent element. The byte order is defined with the attribute TYPE. Possible values are: * MOST-SIGNIFICANT-BYTE-FIRST * MOST-SIGNIFICANT-BYTE-LAST mmt.qualifiedName="ByteOrder" atpObject This represents the actual setting of the byte order. mmt.qualifiedName="ByteOrder.content";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.roleElement="false";xml.roleWrapperElement="false";xml.typeElement="false";xml.typeWrapperElement="false" This element specifies the byte order of the parent element. The byte order is defined with the attribute TYPE. Possible values are: * MOST-SIGNIFICANT-BYTE-FIRST * MOST-SIGNIFICANT-BYTE-LAST mmt.qualifiedName="ByteOrder" atpObject The CCU is a special kind of a timer, which has the capability of counting and comparing external signals. The timer is equipped with some extra registers and comparators in order to measure time or frequency. mmt.qualifiedName="CCU" atpObject A Capture and Compare peripheral can be configured to operate either in capture or compare mode. mmt.qualifiedName="CCU.mode";pureMM.maxOccurs="1";pureMM.minOccurs="1" The CCU is a special kind of a timer, which has the capability of counting and comparing external signals. The timer is equipped with some extra registers and comparators in order to measure time or frequency. mmt.qualifiedName="CCU" atpObject Annotation to a port used for calibration regarding a certain CalprmElement. mmt.qualifiedName="CalibrationPortAnnotation" atpObject The instance of calprm element annotated. mmt.qualifiedName="CalibrationPortAnnotation.calprmElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" Annotation to a port used for calibration regarding a certain CalprmElement. mmt.qualifiedName="CalibrationPortAnnotation" atpObject mmt.qualifiedName="CalprmAccess" atpObject mmt.qualifiedName="calprmAccess.CalprmAccess";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="CalprmAccess" atpObject mmt.qualifiedName="CalprmAccess_CalprmElementPrototype" atpObject,instanceRef mmt.qualifiedName="CalprmAccess_CalprmElementPrototype.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="CalprmAccess_CalprmElementPrototype.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.context This represents the corresponding calprmElementPrototype. mmt.qualifiedName="CalprmAccess_CalprmElementPrototype.calprmElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="CalprmAccess_CalprmElementPrototype" atpObject,instanceRef mmt.qualifiedName="CalprmComponentType" atpObject,atpType In the context of a component there is no typed re-use of CalprmElementPrototype entities mmt.qualifiedName="CalprmElementPrototype" atpObject,atpPrototype mmt.qualifiedName="CalprmInterface" atpObject,atpType This represents a calibration parameter owned by the CalprmInterface. mmt.qualifiedName="CalprmInterface.calprmElement";pureMM.maxOccurs="-1";pureMM.minOccurs="0" mmt.qualifiedName="CalprmInterface" atpObject,atpType CAN specific attributes mmt.qualifiedName="CanCluster";xml.namePlural="CAN-BUSES" atpObject It determines if bus load reduction for the respective NM channel is active or not. True: active False: inactive mmt.qualifiedName="CanCluster.nmBusLoadReductionActive";pureMM.maxOccurs="1";pureMM.minOccurs="1" switch for enabling busload reduction support. mmt.qualifiedName="CanCluster.nmBusLoadReductionEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the immediate NM PDU cycle time in seconds which is used for nmImmediateNmTransmissions NM PDU transmissions. This parameter is only valid if CanNmImmediateNmTransmissions is greater one. mmt.qualifiedName="CanCluster.nmImmediateNmCycleTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the number of immediate NM PDUs which shall be transmitted. If the value is zero no immediate NM PDUs are transmitted. The cycle time of immeditate NM PDUs is defined by nmImmediateNmCycleTime. mmt.qualifiedName="CanCluster.nmImmediateNmTransmissions";pureMM.maxOccurs="1";pureMM.minOccurs="0" Enables the asynchronous transmission of a CanNm PDU upon bus-communication request in Prepare-Bus-Sleep mode. mmt.qualifiedName="CanCluster.nmImmediateRestartEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" This attribute can be used together with the nmUpperCanId attribute to define a range of CanIds. Can Frames which will arrive in the given Id Range will be handled as Nm Pdus. This range definition is redundant to the attribute "rxIdentifierRange" of "CanFrameTriggering". For backward compatibility reasons this redundancy shall be preserved and both shall be defined. mmt.qualifiedName="CanCluster.nmLowerCanId";pureMM.maxOccurs="1";pureMM.minOccurs="0" Period of a CanNm message in seconds. It determines the periodic rate in the periodic transmission mode with bus load reduction and is the basis for transmit scheduling in the periodic transmission mode without bus load reduction. mmt.qualifiedName="CanCluster.nmMsgCycleTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Timeout for Remote Sleep Indication in seconds. It defines the time how long it shall take to recognize that all other nodes are ready to sleep. mmt.qualifiedName="CanCluster.nmRemoteSleepIndicationTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" It defines how long the NM shall stay in the Repeat Message State (in seconds) mmt.qualifiedName="CanCluster.nmRepeatMessageStateTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Network Timeout for NM-Messages. It denotes the time (in seconds) how long the NM shall stay in the Network Mode before transition into Prepare Bus-Sleep Mode shall take place. It shall be equal for all nodes in the cluster. mmt.qualifiedName="CanCluster.nmTimeoutTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute can be used together with the nmLowerCanId attribute to define a range of CanIds. Can Frames which will arrive in the given Id Range will be handled as Nm Pdus. This range definition is redundant to the attribute "rxIdentifierRange" of "CanFrameTriggering". For backward compatibility reasons this redundancy shall be preserved and both shall be defined. mmt.qualifiedName="CanCluster.nmUpperCanId";pureMM.maxOccurs="1";pureMM.minOccurs="0" Timeout for bus calm down phase. It denotes the time (in seconds) how long the NM shall stay in the Prepare Bus-Sleep Mode before transition into Bus-Sleep Mode shall take place. It shall be equal for all nodes in the cluster. mmt.qualifiedName="CanCluster.nmWaitBusSleepTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" CAN specific attributes mmt.qualifiedName="CanCluster";xml.namePlural="CAN-BUSES" atpObject CAN bus specific communication connector attributes. mmt.qualifiedName="CanCommunicationConnector" atpObject CAN Identifier used to configure the CAN Transceiver for partial network wakeup. mmt.qualifiedName="CanCommunicationConnector.pncWakeupCanId";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines whether pncWakeupCanId and pncWakeupCanIdMask shall be interpreted as extended or standard CAN ID. true: extended Can identifier is used false: standard Can identifier is used mmt.qualifiedName="CanCommunicationConnector.pncWakeupCanIdExtended";pureMM.maxOccurs="1";pureMM.minOccurs="0" Bit mask for CAN Identifier used to configure the CAN Transceiver for partial network wakeup. mmt.qualifiedName="CanCommunicationConnector.pncWakeupCanIdMask";pureMM.maxOccurs="1";pureMM.minOccurs="0" Bit mask for CAN Payload used to configure the CAN Transceiver for partial network wakeup. mmt.qualifiedName="CanCommunicationConnector.pncWakeupDataMask";pureMM.maxOccurs="1";pureMM.minOccurs="0" Data Length of the remote data frame used to configure the CAN Transceiver for partial network wakeup in Bytes. mmt.qualifiedName="CanCommunicationConnector.pncWakeupDlc";pureMM.maxOccurs="1";pureMM.minOccurs="0" CAN bus specific communication connector attributes. mmt.qualifiedName="CanCommunicationConnector" atpObject CAN bus specific communication port attributes. mmt.qualifiedName="CanCommunicationController" atpObject CAN Bit Timing configuration mmt.qualifiedName="canControllerAttributes.CanCommunicationController";pureMM.maxOccurs="1";pureMM.minOccurs="1" Node specific time offset in the periodic transmission node. It determines the start delay of the transmission. Specified in seconds. mmt.qualifiedName="CanCommunicationController.nmMsgCycleOffset";pureMM.maxOccurs="1";pureMM.minOccurs="0" Node specific bus cycle time in the periodic transmission mode with bus load reduction. Specified in seconds. mmt.qualifiedName="CanCommunicationController.nmMsgReducedTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Switch for enabling user data support. mmt.qualifiedName="CanCommunicationController.nmUserDataEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" CAN bus specific communication port attributes. mmt.qualifiedName="CanCommunicationController" atpObject This element is used for the specification of the exact CAN Bit Timing configuration parameter values. mmt.qualifiedName="CanControllerConfiguration" atpObject Number of samples. Possible values are 1 or 3. mmt.qualifiedName="CanControllerConfiguration.numberOfSamples";pureMM.maxOccurs="1";pureMM.minOccurs="0" The propagation time segment in quanta. mmt.qualifiedName="CanControllerConfiguration.propagationDelay";pureMM.maxOccurs="1";pureMM.minOccurs="0" The number of quanta in the Synchronization Jump Width, SJW. The (Re-)Synchronization Jump Width (SJW) defines how far a resynchronization may move the Sample Point inside the limits defined by the Phase Buffer Segments to compensate for edge phase errors. mmt.qualifiedName="CanControllerConfiguration.syncJumpWidth";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of quanta before the sampling point. The propagation time segment is factored into the timeSeg1 configuration parameter: timeSeg1 = tPROP_SEG + tPHASE_SEG1 mmt.qualifiedName="CanControllerConfiguration.timeSeg1";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of quanta after the sampling point: timeSeg2 = Phase_Seg2 mmt.qualifiedName="CanControllerConfiguration.timeSeg2";pureMM.maxOccurs="1";pureMM.minOccurs="1" This element is used for the specification of the exact CAN Bit Timing configuration parameter values. mmt.qualifiedName="CanControllerConfiguration" atpObject This element allows the specification of ranges for the CAN Bit Timing configuration parameters. These ranges are taken as requirements and have to be respected by the ECU developer. mmt.qualifiedName="CanControllerConfigurationRequirements" atpObject Maximum number of time quanta in the bit time. mmt.qualifiedName="CanControllerConfigurationRequirements.maxNumberOfTimeQuantaPerBit";pureMM.maxOccurs="1";pureMM.minOccurs="0" The max. value of the sample point as a percentage of the total bit time. mmt.qualifiedName="CanControllerConfigurationRequirements.maxSamplePoint";pureMM.maxOccurs="1";pureMM.minOccurs="0" The max. Synchronization Jump Width value as a percentage of the total bit time. The (Re-)Synchronization Jump Width (SJW) defines how far a resynchronization may move the Sample Point inside the limits defined by the Phase Buffer Segments to compensate for edge phase errors. mmt.qualifiedName="CanControllerConfigurationRequirements.maxSyncJumpWidth";pureMM.maxOccurs="1";pureMM.minOccurs="0" Minimum number of time quanta in the bit time. mmt.qualifiedName="CanControllerConfigurationRequirements.minNumberOfTimeQuantaPerBit";pureMM.maxOccurs="1";pureMM.minOccurs="0" The min. value of the sample point as a percentage of the total bit time. mmt.qualifiedName="CanControllerConfigurationRequirements.minSamplePoint";pureMM.maxOccurs="1";pureMM.minOccurs="0" The min. Synchronization Jump Width value as a percentage of the total bit time. The (Re-)Synchronization Jump Width (SJW) defines how far a resynchronization may move the Sample Point inside the limits defined by the Phase Buffer Segments to compensate for edge phase errors. mmt.qualifiedName="CanControllerConfigurationRequirements.minSyncJumpWidth";pureMM.maxOccurs="1";pureMM.minOccurs="0" This element allows the specification of ranges for the CAN Bit Timing configuration parameters. These ranges are taken as requirements and have to be respected by the ECU developer. mmt.qualifiedName="CanControllerConfigurationRequirements" atpObject CAN specific attributes to the FrameTriggering mmt.qualifiedName="CanFrameTriggering" atpObject The CAN protocol supports two types of frame formats. The standard frame format uses 11-bit identifiers and is defined in the CAN specification 2.0 A. Additionally the extended frame format allows 29-bit identifiers and is defined in the CAN specification 2.0 B. mmt.qualifiedName="CanFrameTriggering.canAddressingMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" To describe a frames identifier on the communication system, usualy with a fixed identifierValue. mmt.qualifiedName="CanFrameTriggering.identifier";pureMM.maxOccurs="1";pureMM.minOccurs="1" Optional definition of a CanId range. mmt.qualifiedName="rxIdentifierRange.CanFrameTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="0" CAN specific attributes to the FrameTriggering mmt.qualifiedName="CanFrameTriggering" atpObject A connection channel represents an internal path for the transmission or reception of a Pdu via CanTp and describes the the sender and the receiver of this particular communication. The CanTp module routes a Pdu through the connection channel mmt.qualifiedName="CanTpConnectionChannel" atpObject Declares which communication addressing mode is supported. mmt.qualifiedName="CanTpConnectionChannel.addressingFormat";pureMM.maxOccurs="1";pureMM.minOccurs="1" The maximum number of N-PDUs the CanTp receiver allows the sender to send, before waiting for an authorization to continue transmission of the following N-PDUs. For further details on this parameter value see ISO 15765-2 specification. Note: For reasons of buffer length, the CAN Transport Layer can adapt the BS value within the limit of this maximum BS mmt.qualifiedName="CanTpConnectionChannel.blockSize";pureMM.maxOccurs="1";pureMM.minOccurs="1" The CAN Transport Layer supports half and full duplex channel modes. mmt.qualifiedName="CanTpConnectionChannel.channelModeType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to an NPdu (Single Frame, First Frame or Consecutive Frame). The Single Frame network protocol data unit (SF N_PDU) shall be sent out by the sending network entity and can be received by one or multiple receiving network entities. The Single Frame (SF N_PDU) shall be sent out to transfer a service data unit that can be transferred via a single service request to the data link layer. This network protocol data unit shall be sent to transfer unsegmented messages. The First Frame network protocol data unit (FF N_PDU) identifies the first network protocol data unit (N_PDU) of a segmented message transmitted by a network sending entity and received by a receiving network entity. The Consecutive Frame network protocol data unit (CF N_PDU) transfers segments (N_Data) of the service data unit message data (<MessageData>). All network protocol data units (N_PDUs) transmitted by the sending entity after the First Frame network protocol data unit (FF N_PDU) shall be encoded as Consecutive Frames network protocol data units (CF N_PDUs). mmt.qualifiedName="CanTpConnectionChannel.dataPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Flow Control NPdu. The Flow Control network protocol data unit (FC N_PDU) is identified by the Flow Control protocol control information (FC N_PCI). The Flow Control network protocol data unit (FC N_PDU) instructs a sending network entity to start, stop or resume transmission of CF N_PDUs. The Flow Control network protocol data unit shall be sent by the receiving network layer entity to the sending network layer entity, when ready to receive more data, after correct reception of: a) First Frame network protocol data unit (FF N_PDU) b) the last Consecutive Frame network protocol data unit (CF N_PDU) of a block of Consecutive Frames (CF N_PDU) if further Consecutive Frame network protocol data unit (CF N_PDU) need(s) to be sent. mmt.qualifiedName="CanTpConnectionChannel.flowControlPdu";pureMM.maxOccurs="1";pureMM.minOccurs="0" This attribute defines the minimum amount of time (separation Time) between two succeeding CFs. Specified in seconds. mmt.qualifiedName="CanTpConnectionChannel.minimumSeparationTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the communication type: true: 1:n communication (Functional) false: 1:1 communication (Physical) mmt.qualifiedName="CanTpConnectionChannel.multicastAddressing";pureMM.maxOccurs="1";pureMM.minOccurs="1" TP address for 1:n connections. mmt.qualifiedName="CanTpConnectionChannel.multicast";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines if the receive frame uses padding or not. true: The N-PDU received uses padding for SF, FC and the last CF. (N-PDU length is always 8 bytes) false: The N-PDU received does not use padding for SF, CF and the last CF. (N-PDU length is dynamic) mmt.qualifiedName="CanTpConnectionChannel.paddingActivation";pureMM.maxOccurs="1";pureMM.minOccurs="1" The source of the TP connection. mmt.qualifiedName="CanTpConnectionChannel.source";pureMM.maxOccurs="1";pureMM.minOccurs="1" Network Target Address type. mmt.qualifiedName="CanTpConnectionChannel.taType";pureMM.maxOccurs="1";pureMM.minOccurs="0" The target of the TP connection. mmt.qualifiedName="CanTpConnectionChannel.target";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Value in second of the N_As timeout. N_As is the time for transmission of a CAN frame (any N_PDU) on the part of the sender. mmt.qualifiedName="CanTpConnectionChannel.timeoutAs";pureMM.maxOccurs="1";pureMM.minOccurs="0" N_Br is the elapsed time (in seconds) between the receiving indication of a FF or CF or the transmit confirmation of a FC, until the transmit request of the next FC. mmt.qualifiedName="CanTpConnectionChannel.timeoutBr";pureMM.maxOccurs="1";pureMM.minOccurs="0" Value in seconds of the N_Bs timeout. N_Bs is the time of transmission until reception of the next Flow Control N_PDU. mmt.qualifiedName="CanTpConnectionChannel.timeoutBs";pureMM.maxOccurs="1";pureMM.minOccurs="0" Value in seconds of the N_Cr timeout. N_Cr is the time until reception of the next Consecutive Frame N_PDU. mmt.qualifiedName="CanTpConnectionChannel.timeoutCr";pureMM.maxOccurs="1";pureMM.minOccurs="0" N_Cs is the time (in seconds) which elapses between the transmit request of a CF N-PDU until the transmit request of the next CF N-PDU. mmt.qualifiedName="CanTpConnectionChannel.timeoutCs";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the IPdu that is segmented by the Transport Protocol. To support the low-level routing of NPdu's the NPdu is a specialization of an IPdu. More details can be found in the NPdu class description. Nevertheless the CanTpConnection must not reference a NPdu with this tpSdu reference. mmt.qualifiedName="CanTpConnectionChannel.tpSdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" A connection channel represents an internal path for the transmission or reception of a Pdu via CanTp and describes the the sender and the receiver of this particular communication. The CanTp module routes a Pdu through the connection channel mmt.qualifiedName="CanTpConnectionChannel" atpObject TP Node (Sender or Receiver) provides the TP Address and the connection to the Topology description. mmt.qualifiedName="CanTpNode" atpObject This parameter indicates how many Flow Control wait N-PDUs can be consecutively transmitted by the receiver. mmt.qualifiedName="CanTpNode.rxWftMax";pureMM.maxOccurs="1";pureMM.minOccurs="0" Value in seconds of the N_Ar timeout. N_Ar is the time for transmission of a CAN frame (any N_PDU) on the receiver side. mmt.qualifiedName="CanTpNode.timeoutAr";pureMM.maxOccurs="1";pureMM.minOccurs="0" TP Node (Sender or Receiver) provides the TP Address and the connection to the Topology description. mmt.qualifiedName="CanTpNode" atpObject Character constant description. mmt.qualifiedName="CharLiteral" atpObject,atpPrototype The character value (a string of length 1). mmt.qualifiedName="CharLiteral.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Character constant description. mmt.qualifiedName="CharLiteral" atpObject,atpPrototype This represents a character belonging to the character-set specified in the encoding. The semantics are built-in into this datatype. mmt.qualifiedName="CharType" atpObject,atpType Specification of character encoding, e.g. ISO-8859-1 mmt.qualifiedName="CharType.encoding";pureMM.maxOccurs="1";pureMM.minOccurs="1" This represents a character belonging to the character-set specified in the encoding. The semantics are built-in into this datatype. mmt.qualifiedName="CharType" atpObject,atpType Used to define configuration containers that provide a choice between several ParamConfContainerDef. But in the actual ECU Configuration Description only one instance from the choice list will be present (depending on the multiplicites given). mmt.qualifiedName="ChoiceContainerDef" atpObject The choices available in a ChoiceContainerDef. mmt.qualifiedName="choice.ChoiceContainerDef";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Used to define configuration containers that provide a choice between several ParamConfContainerDef. But in the actual ECU Configuration Description only one instance from the choice list will be present (depending on the multiplicites given). mmt.qualifiedName="ChoiceContainerDef" atpObject Specify alternative references where in the ECU Configuration description only one of the specified references will actually be used. mmt.qualifiedName="ChoiceReferenceParamDef" atpObject All the possible parameter containers for the reference are specified. mmt.qualifiedName="ChoiceReferenceParamDef.destination";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specify alternative references where in the ECU Configuration description only one of the specified references will actually be used. mmt.qualifiedName="ChoiceReferenceParamDef" atpObject Client specific communication attributes (R-Port and client-server interface). mmt.qualifiedName="ClientComSpec" atpObject Operation these attributes belong to. mmt.qualifiedName="ClientComSpec.operation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Client specific communication attributes (R-Port and client-server interface). mmt.qualifiedName="ClientComSpec" atpObject In case of a server on one ECU with multiple clients on other ECUs, the client server communication shall use different unique COM signals and signal groups for each client to allow the identification of the client associated with each system signal. mmt.qualifiedName="ClientIdMapping" atpObject Reference to the SystemSignal with the ClientID. mmt.qualifiedName="ClientIdMapping.systemSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" In case of a server on one ECU with multiple clients on other ECUs, the client server communication shall use different unique COM signals and signal groups for each client to allow the identification of the client associated with each system signal. mmt.qualifiedName="ClientIdMapping" atpObject The ArrayElement may be a primitive one or a composite one. If the element is primitive, it will be mapped to the "SystemSignal" (multiplicity 1). If the element is composite, there will be no mapping to the "SystemSignal" (multiplicity 0). In this case the "ArrayElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive array element is mapped the indexed array element always needs to be specified. mmt.qualifiedName="ClientServerArrayElementMapping" atpObject This aggregation will be used if the element is composite. mmt.qualifiedName="complexTypeMapping.ClientServerArrayElementMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to an indexed array element in the context of the mappedOperation or in the context of a composite element. mmt.qualifiedName="indexedArrayElement.ClientServerArrayElementMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the system signal used to carry the primitive ArrayElement. mmt.qualifiedName="ClientServerArrayElementMapping.signal";pureMM.maxOccurs="1";pureMM.minOccurs="0" The ArrayElement may be a primitive one or a composite one. If the element is primitive, it will be mapped to the "SystemSignal" (multiplicity 1). If the element is composite, there will be no mapping to the "SystemSignal" (multiplicity 0). In this case the "ArrayElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive array element is mapped the indexed array element always needs to be specified. mmt.qualifiedName="ClientServerArrayElementMapping" atpObject If the compositeType is an Array, the "ArrayTypeMapping" will be used. mmt.qualifiedName="ClientServerArrayTypeMapping" atpObject Each ArrayElement must be mapped on a SystemSignal. mmt.qualifiedName="arrayElementMapping.ClientServerArrayTypeMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" If the compositeType is an Array, the "ArrayTypeMapping" will be used. mmt.qualifiedName="ClientServerArrayTypeMapping" atpObject Two mappings exist for the composite data types: "ArrayTypeMapping" and "RecordTypeMapping". In both, a primitive datatype will be mapped to a system signal. But it is also possible to combine the arrays and the records, so that an "array" could be an element of a "record" and in the same manner a "record" could be an element of an "array". Nesting these data types is also possible. If an element of a composite data type is again a composite one, the "CompositeTypeMapping" element will be used one more time (aggregation between the ArrayElementMapping and CompositeTypeMapping or aggregation between the RecordElementMapping and CompositeTypeMapping). mmt.qualifiedName="ClientServerCompositeTypeMapping" atpObject Reference to an argument in the context of the mappedOperation. Only ClientServerCompositeTypeMapping elements that are directly aggregated by the ClientServerToSignalGroupMapping shall contain this reference. mmt.qualifiedName="ClientServerCompositeTypeMapping.argument";pureMM.maxOccurs="1";pureMM.minOccurs="0" A client/server interface declares a number of operations that can be invoked on a server by a client. mmt.qualifiedName="ClientServerInterface" atpObject,atpType OperationPrototypes owned by this ClientServerInterface. mmt.qualifiedName="operation.interface";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Application errors that are defined as part of this interface. mmt.qualifiedName="possibleError.ClientServerInterface";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A client/server interface declares a number of operations that can be invoked on a server by a client. mmt.qualifiedName="ClientServerInterface" atpObject,atpType Mapping of an argument with a primitive datatype to a signal. mmt.qualifiedName="ClientServerPrimitiveTypeMapping" atpObject Reference to an argument in the context of the mappedOperation. mmt.qualifiedName="ClientServerPrimitiveTypeMapping.argument";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the system signal used to carry the argument mmt.qualifiedName="ClientServerPrimitiveTypeMapping.systemSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" Mapping of an argument with a primitive datatype to a signal. mmt.qualifiedName="ClientServerPrimitiveTypeMapping" atpObject Mapping of a primitive record element to a SystemSignal. If the element is composite, there will be no mapping (multiplicity 0). In this case the "RecordElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive record element is mapped the record element always needs to be specified. mmt.qualifiedName="ClientServerRecordElementMapping" atpObject This aggregation will be used if the element is composite. mmt.qualifiedName="complexTypeMapping.ClientServerRecordElementMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to a RecordElement in the context of the mappedOperation or in the context of a composite element. mmt.qualifiedName="ClientServerRecordElementMapping.recordElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the system signal used to carry the primitive RecordElement. mmt.qualifiedName="ClientServerRecordElementMapping.signal";pureMM.maxOccurs="1";pureMM.minOccurs="0" Mapping of a primitive record element to a SystemSignal. If the element is composite, there will be no mapping (multiplicity 0). In this case the "RecordElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive record element is mapped the record element always needs to be specified. mmt.qualifiedName="ClientServerRecordElementMapping" atpObject If the compositeType is a Record, the "RecordTypeMapping" will be used. mmt.qualifiedName="ClientServerRecordTypeMapping" atpObject Each RecordElement must be mapped on a SystemSignal. mmt.qualifiedName="recordElementMapping.ClientServerRecordTypeMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" If the compositeType is a Record, the "RecordTypeMapping" will be used. mmt.qualifiedName="ClientServerRecordTypeMapping" atpObject Mapping of client server operation arguments to signals of a signal group. Arguments with a primitive datatype will be mapped via the "ClientServerPrimitiveTypeMapping" element. Arguments with composite datatypes will be mapped via the "CompositeTypeMapping" element. mmt.qualifiedName="ClientServerToSignalGroupMapping" atpObject In client server communication, the server may return any value within the application error range. mmt.qualifiedName="applicationError.ClientServerToSignalGroupMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" In case of a server on one ECU with multiple clients on other ECUs, the client server communication shall use different unique COM signals and signal groups for each client to allow the identification of the client associated with each system signal. mmt.qualifiedName="clientID.ClientServerToSignalGroupMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Mapping of arguments with composite datatypes. mmt.qualifiedName="compositeTypeMapping.ClientServerToSignalGroupMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" According to the COM Specification, signal groups without signals are allowed. These have a "signalLength" = 0. In this case there shall be an "update-bit" configured. mmt.qualifiedName="emptySignal.ClientServerToSignalGroupMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the operation whose arguments should be transmitted via the communication bus. Reference to a Operation, which is mapped to a signal group. mmt.qualifiedName="mappedOperation.ClientServerToSignalGroupMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Mapping of an argument with a primitive datatype to a signal. mmt.qualifiedName="primitiveTypeMapping.ClientServerToSignalGroupMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to the signal group which contains the references to request signals used to transport the OUT arguments of the operation or the empty signal if the operation doesn't have OUT arguments. mmt.qualifiedName="ClientServerToSignalGroupMapping.requestGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the signal group which contains the references to response signals used to transport the IN arguments of the operation. mmt.qualifiedName="ClientServerToSignalGroupMapping.responseGroup";pureMM.maxOccurs="1";pureMM.minOccurs="0" The purpose of sequence counters is to map a response to the correct request of a known client. mmt.qualifiedName="sequenceCounter.ClientServerToSignalGroupMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Mapping of client server operation arguments to signals of a signal group. Arguments with a primitive datatype will be mapped via the "ClientServerPrimitiveTypeMapping" element. Arguments with composite datatypes will be mapped via the "CompositeTypeMapping" element. mmt.qualifiedName="ClientServerToSignalGroupMapping" atpObject mmt.qualifiedName="ClientServerToSignalGroupMapping_mappedOperation" atpObject,instanceRef mmt.qualifiedName="ClientServerToSignalGroupMapping_mappedOperation.compositionPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ClientServerToSignalGroupMapping_mappedOperation.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ClientServerToSignalGroupMapping_mappedOperation.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="ClientServerToSignalGroupMapping_mappedOperation.operation";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.target mmt.qualifiedName="ClientServerToSignalGroupMapping_mappedOperation" atpObject,instanceRef The clock delivers the time for the PU and other HW Elements on the ECU. mmt.qualifiedName="Clock" atpObject Defines if the clock is adjustable from software. mmt.qualifiedName="Clock.adjustable";pureMM.maxOccurs="1";pureMM.minOccurs="0" The short-term deviation of the nominal frequency to the real frequency. Jitter is influenced by the circuitry itself, voltage spikes etc. Jitter is critical for communication elements. PLL need/generate jitter for operation. Therefore communication interfaces should operate from an oscillator e.g. quartz directly or use only divider, not a PLL, as clock source. Using PLL for communication interfaces is a very common source for problems in ECU test and integration. mmt.qualifiedName="Clock.clockJitter";pureMM.maxOccurs="1";pureMM.minOccurs="1" The time the clock generation needs to deliver a stable and valid signal. mmt.qualifiedName="Clock.clockStartupTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" The long-term deviation of the nominal frequency to the real frequency. Influenced by manufacturing, layout, temperature, external components and voltage. Tolerances are critical for timer application and time synchronisation. mmt.qualifiedName="Clock.clockTolerance";pureMM.maxOccurs="1";pureMM.minOccurs="1" The frequency range the clock is able to provide. This value depends on what the oscillator is delivering. mmt.qualifiedName="frequency.Clock";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies which oscillator is used to generate the clock. mmt.qualifiedName="Clock.oscillator";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Defines the type of the clock signal. mmt.qualifiedName="Clock.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" The clock delivers the time for the PU and other HW Elements on the ECU. mmt.qualifiedName="Clock" atpObject A generic code descriptor. mmt.qualifiedName="Code" atpObject The type of described code. mmt.qualifiedName="Code.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" The files belonging to this code descriptor. mmt.qualifiedName="Code.xfile";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.typeElement="false" A generic code descriptor. mmt.qualifiedName="Code" atpObject Specifies the abstract needs on the configuration of the Communication Manager for one "user". mmt.qualifiedName="ComMgrUserNeeds" atpObject Maximum communication mode requested by this ComM user mmt.qualifiedName="ComMgrUserNeeds.maxCommMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs on the configuration of the Communication Manager for one "user". mmt.qualifiedName="ComMgrUserNeeds" atpObject The Ecu communication relationship defines which signals, Pdus and frames are actually received and transmitted by this ECU. For each signal, Pdu or Frame that is transmitted or received and used by the Ecu an association between a SignalPort, IPduPort or FramePort with the corresponding Triggering shall be created. A SignalPort shall be created only if the corresponding signal is handled by COM (RTE or Signal Gateway). If a Pdu Gateway ECU only routes the Pdu without being interested in the content only a FramePort and an IPduPort needs to be created. mmt.qualifiedName="CommConnectorPort" atpObject communication Direction of the Connector Port (input or output Port). mmt.qualifiedName="CommConnectorPort.communicationDirection";pureMM.maxOccurs="1";pureMM.minOccurs="1" Attributes used by Configuration Parameters as well as References. mmt.qualifiedName="CommonConfigurationAttributes" atpObject Specifes whether changes on this parameter have some affection on other parameters. This element is deprecated and will be removed in future versions. mmt.qualifiedName="configurationClassAffection.CommonConfigurationAttributes";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specifies which in which ConfigurationClass this parameter or reference is available for which ConfigurationVariant. mmt.qualifiedName="implementationConfigClass.CommonConfigurationAttributes";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.namePlural="IMPLEMENTATION-CONFIG-CLASSES" String specifying if this configuration parameter is an AUTOSAR standardized configuration parameter or if the parameter is hardware- or vendor-specific. mmt.qualifiedName="CommonConfigurationAttributes.origin";pureMM.maxOccurs="1";pureMM.minOccurs="1" The CommonSignalPath describes that two or more SwcToSwcSignals and/or SwcToSwcOperationArguments must take the same way (Signal Path) in the topology. mmt.qualifiedName="CommonSignalPath" atpObject mmt.qualifiedName="operation.CommonSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The SwcToSwcSignals that must take the same way (Signal Path) in the topology. mmt.qualifiedName="signal.CommonSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The CommonSignalPath describes that two or more SwcToSwcSignals and/or SwcToSwcOperationArguments must take the same way (Signal Path) in the topology. mmt.qualifiedName="CommonSignalPath" atpObject The CommunicationCluster is the main element to describe the topological connection of communicating ECUs. A cluster describes the ensemble of ECUs, which are linked by a communication medium of arbitrary topology (bus, star, ring, ...). The nodes within the cluster share the same communication protocol, which may be event-triggered, time-triggered or a combination of both. A CommunicationCluster aggregates one or more physical channels. All physical channels that are aggregated by a communication cluster are synchronized with each other. mmt.qualifiedName="CommunicationCluster" atpObject Maximal supported length in bytes for frames in this cluster. mmt.qualifiedName="CommunicationCluster.maxFrameLength";pureMM.maxOccurs="1";pureMM.minOccurs="0" Enable/disable the node detection functionality. mmt.qualifiedName="CommunicationCluster.nmNodeDetectionEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="1" Enable/disable the source node identifier. mmt.qualifiedName="CommunicationCluster.nmNodeIdEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="1" switch for enabling support for repeat message mmt.qualifiedName="CommunicationCluster.nmRepeatMessageSupport";pureMM.maxOccurs="1";pureMM.minOccurs="1" This relationship defines which channel element belongs to which cluster. A channel must be assigned to exactly one cluster, whereas a cluster may have one or more channels. mmt.qualifiedName="physicalChannel.CommunicationCluster";pureMM.maxOccurs="-1";pureMM.minOccurs="1" atpSplitable The name of the protocol used. mmt.qualifiedName="CommunicationCluster.protocolName";pureMM.maxOccurs="1";pureMM.minOccurs="0" The version of the protocol used. mmt.qualifiedName="CommunicationCluster.protocolVersion";pureMM.maxOccurs="1";pureMM.minOccurs="0" channels speed in bits per second mmt.qualifiedName="CommunicationCluster.speed";pureMM.maxOccurs="1";pureMM.minOccurs="0" The CommunicationCluster is the main element to describe the topological connection of communicating ECUs. A cluster describes the ensemble of ECUs, which are linked by a communication medium of arbitrary topology (bus, star, ring, ...). The nodes within the cluster share the same communication protocol, which may be event-triggered, time-triggered or a combination of both. A CommunicationCluster aggregates one or more physical channels. All physical channels that are aggregated by a communication cluster are synchronized with each other. mmt.qualifiedName="CommunicationCluster" atpObject The connection between the referencing ECU and the referenced channel via the referenced controller. Connectors are used to describe the bus interfaces of the ECUs and to specify the sending/receiving behavior. Each CommunicationConnector has a reference to exactly one communicationController. The communicationController can be referenced by several CommunicationConnector elements. This is important for the FlexRay Bus. FlexRay communicates via two physical channels. But only one controller in an ECU is responsible for both channels. Thus, two connectors (for channel A and for channel B) must reference to the same controller. The relationship of CommunicationConnector and PhysicalChannel in the scope of one EcuInstance is always 1:1. The existence of two or more CommunicationConnectors aggregated at the same EcuInstance that reference the same PhysicalChannel is prohibited. mmt.qualifiedName="CommunicationConnector" atpObject Reference to the channel to which the ECU is connected. mmt.qualifiedName="CommunicationConnector.channel";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the communication controller. The CommunicationConnector and referenced CommunicationController must be aggregated by the same ECUInstance. mmt.qualifiedName="CommunicationConnector.commController";pureMM.maxOccurs="1";pureMM.minOccurs="1" An ECUs reception or send ports. mmt.qualifiedName="ecuCommPortInstance.CommunicationConnector";pureMM.maxOccurs="-1";pureMM.minOccurs="0" An ECUs NM address on the referenced channel. mmt.qualifiedName="CommunicationConnector.nmAddress";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines if this EcuInstance shall implement the PncGateway functionality on this CommunicationConnector and its respective PhysicalChannel. Several EcuInstances on the same PhysicalChannel can have the PncGateway functionality enabled, but only one of them shall have the pncGatewayType "active". mmt.qualifiedName="CommunicationConnector.pncGatewayType";pureMM.maxOccurs="1";pureMM.minOccurs="0" The connection between the referencing ECU and the referenced channel via the referenced controller. Connectors are used to describe the bus interfaces of the ECUs and to specify the sending/receiving behavior. Each CommunicationConnector has a reference to exactly one communicationController. The communicationController can be referenced by several CommunicationConnector elements. This is important for the FlexRay Bus. FlexRay communicates via two physical channels. But only one controller in an ECU is responsible for both channels. Thus, two connectors (for channel A and for channel B) must reference to the same controller. The relationship of CommunicationConnector and PhysicalChannel in the scope of one EcuInstance is always 1:1. The existence of two or more CommunicationConnectors aggregated at the same EcuInstance that reference the same PhysicalChannel is prohibited. mmt.qualifiedName="CommunicationConnector" atpObject The communication controller is a dedicated hardware device by means of which hosts are sending frames to and receiving frames from the communication medium. mmt.qualifiedName="CommunicationController" atpObject May the ECU be woken up by this CAN Controller? TRUE: wake up is possible FALSE: wake up is not supported Note: This flag may only be set to TRUE if the feature is supported by both hardware and basic software. mmt.qualifiedName="CommunicationController.wakeUpByControllerSupported";pureMM.maxOccurs="1";pureMM.minOccurs="1" The communication controller is a dedicated hardware device by means of which hosts are sending frames to and receiving frames from the communication medium. mmt.qualifiedName="CommunicationController" atpObject CommunicationControllerMapping specifies the CommunicationPeripheral hardware (defined in the ECU Resource Template) to realize the specified CommunicationController in a physical topology. mmt.qualifiedName="CommunicationControllerMapping" atpObject Reference to the CommunicationController in the System Template mmt.qualifiedName="CommunicationControllerMapping.communicationController";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="CommunicationControllerMapping.communicationPeripheral";pureMM.maxOccurs="1";pureMM.minOccurs="1" CommunicationControllerMapping specifies the CommunicationPeripheral hardware (defined in the ECU Resource Template) to realize the specified CommunicationController in a physical topology. mmt.qualifiedName="CommunicationControllerMapping" atpObject Describes the amount and the size of the communication filters. These can be used as acceptance or rejection filters. mmt.qualifiedName="CommunicationFilter" atpObject How many acceptance filters are availabe. mmt.qualifiedName="CommunicationFilter.filterCount";pureMM.maxOccurs="1";pureMM.minOccurs="1" Which bit-size do the filters have. mmt.qualifiedName="CommunicationFilter.filterWidth";pureMM.maxOccurs="1";pureMM.minOccurs="1" Is it possible to provide wildcard identifires allowing to specify ranges for filtering. mmt.qualifiedName="CommunicationFilter.wildCards";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the amount and the size of the communication filters. These can be used as acceptance or rejection filters. mmt.qualifiedName="CommunicationFilter" atpObject mmt.qualifiedName="CommunicationHWPort" atpObject Describes the physical medium the bus is working on. In most cases it is not relevant for the SW to know about it. mmt.qualifiedName="physicalLayer.CommunicationHWPort";pureMM.maxOccurs="1";pureMM.minOccurs="0" The Communication speed can be provided either as a fixed value if it can not be changed by software. Or there can be a range in which software can configure the communication speed. Also a list of possible speed values can be provided from which the software can choose. If the communication speed is not fixed with one value the System Constraint Description has the freedom to choose from the given range or list of communication speed. In the end only HW Ports with the same communication speed can be connected to a bus system. mmt.qualifiedName="speed.CommunicationHWPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="CommunicationHWPort" atpObject Peripheral representing communication devices. mmt.qualifiedName="CommunicationPeripheral" atpObject If the Communication Peripheral supports filtering of frames here the amount and quality of filters is described. mmt.qualifiedName="acceptanceFilter.CommunicationPeripheral";pureMM.maxOccurs="1";pureMM.minOccurs="0" The implemented architecture mmt.qualifiedName="CommunicationPeripheral.architecture";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the clock description. This is used to calculate possible transmission rates. mmt.qualifiedName="CommunicationPeripheral.clock";pureMM.maxOccurs="1";pureMM.minOccurs="0" Under certain conditions that are likely to appear in automotive applications, the transmission of information between communication endpoints might be unsafe because of particular sources of interference . It is possible to detect the presence of interference by means of error-detection codes (EDC) and at least partly overcome the problem by means of error-correction codes (ECC). Error detection is a method that allows some communication errors to be detected. For this purpose the introduction of redundancy is required such that the information transmitted consists of more bits than the source of information. The extra bits are required for EDC and ECC. mmt.qualifiedName="errorDetection.CommunicationPeripheral";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the actual ommunication HW Port of this peripheral. mmt.qualifiedName="hwPort.CommunicationPeripheral";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The Element Monitor specifies if the device supports listen only. In this mode the device is passive on the bus and no acknowledgement or other responds are transmitted. mmt.qualifiedName="CommunicationPeripheral.monitor";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes which protocols are supported by this hardware. mmt.qualifiedName="protocol.CommunicationPeripheral";pureMM.maxOccurs="-1";pureMM.minOccurs="1" If the Communication Peripheral supports filtering of frames here the amount and quality of filters is described. mmt.qualifiedName="rejectionFilter.CommunicationPeripheral";pureMM.maxOccurs="1";pureMM.minOccurs="0" Is a timestamp for received frames available. mmt.qualifiedName="CommunicationPeripheral.timestampAvailable";pureMM.maxOccurs="1";pureMM.minOccurs="0" Peripheral representing communication devices. mmt.qualifiedName="CommunicationPeripheral" atpObject Describes the physical medium the bus is working on. In most cases it is not relevant for the SW to know about it, only for compatibility checking. mmt.qualifiedName="CommunicationPhysicalMedium" atpObject Specifies how many data lines (ground not included) are used for the physical layer. Some bus systems can be implemented with e.g. 1, 2 or 4 data lines. mmt.qualifiedName="CommunicationPhysicalMedium.physicalMediumDataLines";pureMM.maxOccurs="1";pureMM.minOccurs="0" The element protocol name defines the exact standardised protocol name. Examples are: - ISO 11519 for low-speed CAN - IEEE 802.11g for W-LAN (54 Mbit/s at 2,5 GHz) - IEEE-1394a for Firewire-400 mmt.qualifiedName="CommunicationPhysicalMedium.physicalMediumStandard";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the actual medium used for transmission. mmt.qualifiedName="CommunicationPhysicalMedium.physicalMediumType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the physical medium the bus is working on. In most cases it is not relevant for the SW to know about it, only for compatibility checking. mmt.qualifiedName="CommunicationPhysicalMedium" atpObject The name and version of the communication protocol. mmt.qualifiedName="CommunicationProtocol" atpObject This is the version number of the implementation of the protocol layer, e.g. - 2.0a, 2.0b for CAN. - 1.3, 2.0 for LIN. - 2.0 for USB. mmt.qualifiedName="CommunicationProtocol.version";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The name and version of the communication protocol. mmt.qualifiedName="CommunicationProtocol" atpObject Abstract element to describe communication speed. This can be either a fixed value, a range or a list of allowed communication speed. mmt.qualifiedName="CommunicationSpeed" atpObject The element defines the tolerance allowed for the interface. (E.g. K-Line or LIN +/- 2 % at 9.6 Kbd) mmt.qualifiedName="CommunicationSpeed.tolerance";pureMM.maxOccurs="1";pureMM.minOccurs="0" Fixed value for the communication speed. mmt.qualifiedName="CommunicationSpeedFixed" atpObject Unit: bits per second mmt.qualifiedName="CommunicationSpeedFixed.fixSpeed";pureMM.maxOccurs="1";pureMM.minOccurs="1" Fixed value for the communication speed. mmt.qualifiedName="CommunicationSpeedFixed" atpObject List of possible communication speed. mmt.qualifiedName="CommunicationSpeedList" atpObject Unit: bits per second mmt.qualifiedName="CommunicationSpeedList.speed";pureMM.maxOccurs="-1";pureMM.minOccurs="1" List of possible communication speed. mmt.qualifiedName="CommunicationSpeedList" atpObject Range of communication speed. mmt.qualifiedName="CommunicationSpeedRange" atpObject Unit: bits per second mmt.qualifiedName="CommunicationSpeedRange.maxSpeed";pureMM.maxOccurs="1";pureMM.minOccurs="1" Unit: bits per second mmt.qualifiedName="CommunicationSpeedRange.minSpeed";pureMM.maxOccurs="1";pureMM.minOccurs="1" Range of communication speed. mmt.qualifiedName="CommunicationSpeedRange" atpObject The Communication Transceiver has to transfer and receive the data through the physical link and is the implementation of the OSI layer 1. Communication Transceivers have additional links to the controller/PU to support wake-up feature, enabling/disabling and error indication. mmt.qualifiedName="CommunicationTransceiver" atpObject Some transceivers have already acceptance filters implemented in hardware. This can be specified here. mmt.qualifiedName="acceptanceFilter.CommunicationTransceiver";pureMM.maxOccurs="1";pureMM.minOccurs="0" Distinguish between different implementations. mmt.qualifiedName="CommunicationTransceiver.architecture";pureMM.maxOccurs="1";pureMM.minOccurs="0" Some transceivers have already rejection filters implemented in hardware. This can be specified here. mmt.qualifiedName="rejectionFilter.CommunicationTransceiver";pureMM.maxOccurs="1";pureMM.minOccurs="0" Description how this network node is terminated. mmt.qualifiedName="termination.CommunicationTransceiver";pureMM.maxOccurs="1";pureMM.minOccurs="0" The Communication Transceiver has to transfer and receive the data through the physical link and is the implementation of the OSI layer 1. Communication Transceivers have additional links to the controller/PU to support wake-up feature, enabling/disabling and error indication. mmt.qualifiedName="CommunicationTransceiver" atpObject Use <companyRevisionInfo> , to generate information on document version within the respective company. mmt.qualifiedName="CompanyRevisionInfo";xml.sequenceOffset="30" atpObject mmt.qualifiedName="CompanySpecificInfo" atpObject Specifies the compiler attributes. In case of source code this specifies requirements how the compiler shall be invoked. In case of object code this documents the used compiler settings. mmt.qualifiedName="Compiler" atpObject Compiler name (like gcc). mmt.qualifiedName="Compiler.name";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the compiler options. mmt.qualifiedName="Compiler.options";pureMM.maxOccurs="1";pureMM.minOccurs="1" Vendor of compiler. mmt.qualifiedName="Compiler.vendor";pureMM.maxOccurs="1";pureMM.minOccurs="1" Exact version of compiler executable. mmt.qualifiedName="Compiler.version";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the compiler attributes. In case of source code this specifies requirements how the compiler shall be invoked. In case of object code this documents the used compiler settings. mmt.qualifiedName="Compiler" atpObject The ComplexDeviceDriver Component is a special AtomicSoftwareComponent that has direct access to hardware on an ECUand which is therefore linked to a specific ECU or specific hardware. The ComplexDeviceDriver ComponentType introduces the possibility to link from the software representation to its hardware description provided by the ECU Resource Template. mmt.qualifiedName="ComplexDeviceDriverComponentType" atpObject,atpType Reference from the ComplexDeviceDriverComponentType to the Basic Software Module Description describing the BSW part of the Complex Device Driver Component. mmt.qualifiedName="ComplexDeviceDriverComponentType.bswModuleDescription";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference from the ComplexDeviceDriverComponentType to the description of the used HWElements. mmt.qualifiedName="ComplexDeviceDriverComponentType.hardwareElement";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The ComplexDeviceDriver Component is a special AtomicSoftwareComponent that has direct access to hardware on an ECUand which is therefore linked to a specific ECU or specific hardware. The ComplexDeviceDriver ComponentType introduces the possibility to link from the software representation to its hardware description provided by the ECU Resource Template. mmt.qualifiedName="ComplexDeviceDriverComponentType" atpObject,atpType Constraint that forces the mapping of all referenced SW component instances to the same ECU mmt.qualifiedName="ComponentClustering" atpObject Reference to the components that have to be mapped together. mmt.qualifiedName="clusteredComponent.ComponentClustering";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Constraint that forces the mapping of all referenced SW component instances to the same ECU mmt.qualifiedName="ComponentClustering" atpObject mmt.qualifiedName="ComponentClustering_clusteredComponent" atpObject,instanceRef mmt.qualifiedName="ComponentClustering_clusteredComponent.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ComponentClustering_clusteredComponent.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ComponentClustering_clusteredComponent.clusteredComponent";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="ComponentClustering_clusteredComponent" atpObject,instanceRef Role of a software component within a composition. mmt.qualifiedName="ComponentPrototype" atpObject,atpPrototype Type of the instance. mmt.qualifiedName="ComponentPrototype.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType Role of a software component within a composition. mmt.qualifiedName="ComponentPrototype" atpObject,atpPrototype Constraint that forces the two referenced SW components (called A and B in the following) not to be mapped to the same ECU. If a SW component (e.g. A) is a composition, none of the atomic SW components making up the A composition must be mapped together with any of the atomic SW components making up the B composition. Furthermore, A and B must be disjoint. mmt.qualifiedName="ComponentSeparation" atpObject The two components that have to be mapped to different ECUs mmt.qualifiedName="separatedComponent.ComponentSeparation";pureMM.maxOccurs="2";pureMM.minOccurs="2" Constraint that forces the two referenced SW components (called A and B in the following) not to be mapped to the same ECU. If a SW component (e.g. A) is a composition, none of the atomic SW components making up the A composition must be mapped together with any of the atomic SW components making up the B composition. Furthermore, A and B must be disjoint. mmt.qualifiedName="ComponentSeparation" atpObject mmt.qualifiedName="ComponentSeparation_separatedComponent" atpObject,instanceRef mmt.qualifiedName="ComponentSeparation_separatedComponent.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ComponentSeparation_separatedComponent.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ComponentSeparation_separatedComponent.separatedComponent";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="ComponentSeparation_separatedComponent" atpObject,instanceRef Base class for AUTOSAR software components. mmt.qualifiedName="ComponentType" atpObject,atpType The ports through which this component can communicate. mmt.qualifiedName="port.component";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A portGroup being part of this component. mmt.qualifiedName="ComponentType.portGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A CompositionType aggregates ComponentPrototypes (that in turn are typed by ComponentTypes) as well as ConnectorPrototypes for primarily connecting ComponentPrototypes among each others and towards the surface of the CompositionType. By this means hierarchical structures of software-components can be created. mmt.qualifiedName="CompositionType" atpObject,atpType The instantiated components that are part of this composition. mmt.qualifiedName="component.CompositionType";pureMM.maxOccurs="-1";pureMM.minOccurs="1" ConnectorPrototypes have the principal ability to establish a connection among PortPrototypes. They can have many roles in the context of a CompositionType. Details are refined by subclasses. mmt.qualifiedName="connector.composition";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A CompositionType aggregates ComponentPrototypes (that in turn are typed by ComponentTypes) as well as ConnectorPrototypes for primarily connecting ComponentPrototypes among each others and towards the surface of the CompositionType. By this means hierarchical structures of software-components can be created. mmt.qualifiedName="CompositionType" atpObject,atpType mmt.qualifiedName="Compu" atpObject This property can be used to specify an output value for a conversion formula, if the value to be converted lies outside the plausibility limit. Although this is possible for all conversion formulae, it is especially valid for variables with tabular conversion formulae. mmt.qualifiedName="Compu.compuDefaultValue";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" mmt.qualifiedName="Compu" atpObject mmt.qualifiedName="CompuConst" atpObject mmt.qualifiedName="CompuConst" atpObject mmt.qualifiedName="CompuConstFormulaContent" atpObject Value calculated via a system constant. This element is included in every case, where parameters should be generated from numerical values during compile time (not runtime!). Thus for example, the influence of the cylinder number on conversion formulae, can be introduced in a repeatable manner. mmt.qualifiedName="CompuConstFormulaContent.vf";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" mmt.qualifiedName="CompuConstFormulaContent" atpObject mmt.qualifiedName="CompuConstNumericContent" atpObject Use <v> to enter a numerical value. mmt.qualifiedName="CompuConstNumericContent.v";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="50" mmt.qualifiedName="CompuConstNumericContent" atpObject mmt.qualifiedName="CompuConstTextContent" atpObject <vt> represents one particular textual value of the calibration item. mmt.qualifiedName="CompuConstTextContent.vt";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="70" mmt.qualifiedName="CompuConstTextContent" atpObject This class represents a calculation formula as a simple arithmetical expression. string f(x): function to calculate the physical value from the binary, control unit internal value. The interpretation proceeds from left to right for operations of the same operation preferences. Operator preferences, such as power before product/quotient before sum/difference before shift left before shift right before logical AND before logical OR are taken into account. Brackets are allowed and should be used in order to exclude interpretation doubt. For more details refer to ASAM Harmonized Data Objects v1.1 Chapter 9.3.11. Note that this element is a mixed string since a future variant mechanism might use placeholdes to represent references to other objects of the metamodel. As of August 2007 within ASAM there are slightly different syntaxes. One from ASAM-HDO (GenericMath) and the one from SwDataDependency: The difference is mainly between available functions and operators. Nevertheless we use the same class for now. numeric_expression ::= ( "-"expression ) | ( expression ( "+" | "-" | "*" | "/" | "^") expression ) expression ::= ( number | variable | numeric_expression | ( "(" expression ")" ) | sinus_statement | cosinus_statement | sqrt_statement ) | expression {white-space} sinus_statement ::= "sin" "(" expression ")" cosinus_statement ::= "cos" "(" expression ")" sqrt_statement ::= "sqrt" "(" expression ")" number ::= integer_literal | float_literal variable ::= Any valid Object in question integer_literal ::= ( "1..9" { "0..9" } ) | ( "0" "x" "0..9a..f" { "0..9a..f" } ) float_literal ::= ( decimal_digits "." decimal_digits exponent_part ) | ( "." decimal_digits exponent_part ) | ( decimal_digits exponent_part ) decimal_digits ::= "0..9" { "0..9" } exponent_part ::= "e" "+" | "-" decimal_digits white-space ::= tabulator | blank | newline | carriage_return | {tabulator | blank | newline | carriage_return } tabulator ::= \t blank ::= " " newline ::= \n carriage_return ::= \c mmt.qualifiedName="CompuGenericMath" atpMixedString,atpObject Placeholder to describe an indicator of a language level for the mathematics e.g. INFORMAL, ASAMHDO. May be refined by particular usecases. mmt.qualifiedName="CompuGenericMath.level";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" This class represents a calculation formula as a simple arithmetical expression. string f(x): function to calculate the physical value from the binary, control unit internal value. The interpretation proceeds from left to right for operations of the same operation preferences. Operator preferences, such as power before product/quotient before sum/difference before shift left before shift right before logical AND before logical OR are taken into account. Brackets are allowed and should be used in order to exclude interpretation doubt. For more details refer to ASAM Harmonized Data Objects v1.1 Chapter 9.3.11. Note that this element is a mixed string since a future variant mechanism might use placeholdes to represent references to other objects of the metamodel. As of August 2007 within ASAM there are slightly different syntaxes. One from ASAM-HDO (GenericMath) and the one from SwDataDependency: The difference is mainly between available functions and operators. Nevertheless we use the same class for now. numeric_expression ::= ( "-"expression ) | ( expression ( "+" | "-" | "*" | "/" | "^") expression ) expression ::= ( number | variable | numeric_expression | ( "(" expression ")" ) | sinus_statement | cosinus_statement | sqrt_statement ) | expression {white-space} sinus_statement ::= "sin" "(" expression ")" cosinus_statement ::= "cos" "(" expression ")" sqrt_statement ::= "sqrt" "(" expression ")" number ::= integer_literal | float_literal variable ::= Any valid Object in question integer_literal ::= ( "1..9" { "0..9" } ) | ( "0" "x" "0..9a..f" { "0..9a..f" } ) float_literal ::= ( decimal_digits "." decimal_digits exponent_part ) | ( "." decimal_digits exponent_part ) | ( decimal_digits exponent_part ) decimal_digits ::= "0..9" { "0..9" } exponent_part ::= "e" "+" | "-" decimal_digits white-space ::= tabulator | blank | newline | carriage_return | {tabulator | blank | newline | carriage_return } tabulator ::= \t blank ::= " " newline ::= \n carriage_return ::= \c mmt.qualifiedName="CompuGenericMath" atpMixedString,atpObject mmt.qualifiedName="CompuMethod" atpObject This property specifies, how the physical value shall be displayed e.g. in documents or measurement and calibration tools. mmt.qualifiedName="CompuMethod.displayFormat";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This is the physical unit of the Physical values for which the CompuMethod applies. mmt.qualifiedName="CompuMethod.unit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This speifies the computation from internal values to physical values. mmt.qualifiedName="CompuMethod.compuInternalToPhys";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" This represents the computation from physical values to the internal values. mmt.qualifiedName="CompuMethod.compuPhysToInternal";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" mmt.qualifiedName="CompuMethod" atpObject mmt.qualifiedName="CompuNominatorDenominator" atpMixed,atpObject Value calculated via a system constant. This element is included in every case, where parameters should be generated from numerical values during compile time (not runtime!). Thus for example, the influence of the cylinder number on conversion formulae, can be introduced in a repeatable manner. mmt.qualifiedName="CompuNominatorDenominator.vf";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" Use <v> to enter a numerical value. mmt.qualifiedName="CompuNominatorDenominator.v";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" mmt.qualifiedName="CompuNominatorDenominator" atpMixed,atpObject mmt.qualifiedName="CompuProgCode" atpObject mmt.qualifiedName="CompuProgCode.progCode";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="60" mmt.qualifiedName="CompuProgCode" atpObject mmt.qualifiedName="CompuRationalCoeffs" atpObject This is the enumerator of the rational expression. mmt.qualifiedName="CompuRationalCoeffs.compuNumerator";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" This is the denominator of the expression. mmt.qualifiedName="CompuRationalCoeffs.compuDenominator";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" mmt.qualifiedName="CompuRationalCoeffs" atpObject mmt.qualifiedName="CompuScale" atpObject This element specifies a short name for the particular scale. The name can for example be used to derive a programming language identifier. mmt.qualifiedName="CompuScale.shortLabel";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" The symbol, if provided, is used by code generators to get a C identifier for the CompuScale. The name will be used as is for the code generation, therefore it needs to be unique within the generation context. mmt.qualifiedName="CompuScale.symbol";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="25" <desc> represents a general but brief description of the object in question. mmt.qualifiedName="CompuScale.desc";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element specifies the lower limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="CompuScale.lowerLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This element specifies the upper limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="CompuScale.upperLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" mmt.qualifiedName="CompuScale" atpObject mmt.qualifiedName="CompuScaleConstantContents" atpObject This represnts the fact that the scale is a constant. The use case is mainly a non interplolated scale. It is a simplification of the fact that a constant scale can also be expressed as Rational Function of oder 0. mmt.qualifiedName="CompuScaleConstantContents.compuConst";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="90" mmt.qualifiedName="CompuScaleConstantContents" atpObject mmt.qualifiedName="CompuScaleGenericMath" atpObject mmt.qualifiedName="CompuScaleRationalFormula" atpObject This specifies the coefficients of the rational fomula. mmt.qualifiedName="CompuScaleRationalFormula.compuRationalCoeffs";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="110" mmt.qualifiedName="CompuScaleRationalFormula" atpObject mmt.qualifiedName="CompuScales" atpObject This represents one scale within the compu method. mmt.qualifiedName="CompuScales.compuScale";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="CompuScales" atpObject Abstract class used to define the similarities of all ECU Configuration Parameter types defined as subclasses. mmt.qualifiedName="ConfigParameter" atpObject Specifies that this parameter's value is used, together with the aggregating container, to derive a symbolic name definition. E.g.: #define "container_shortName" "this parameter's value". mmt.qualifiedName="ConfigParameter.symbolicNameValue";pureMM.maxOccurs="1";pureMM.minOccurs="1" Abstract class to be used as common parent for all reference values in the ECU Configuration Description. mmt.qualifiedName="ConfigReferenceValue" atpObject Reference to the definition of this ConfigReferenceValue subclasses in the ECU Configuration Parameter Definition. mmt.qualifiedName="ConfigReferenceValue.definition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="-10" Specifies in the "VendorSpecificModuleDefinition" whether changes on this parameter do affect other parameters in a later configuration step. This element is deprecated and will be removed in future versions. mmt.qualifiedName="ConfigurationClassAffection" atpObject Optional reference to parameters or references which are affected by the ConfigurationClassAffection. mmt.qualifiedName="ConfigurationClassAffection.affected";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specifies which affect do changes in this parameter have on other parameters. This attribute is deprecated and will be removed in future versions. mmt.qualifiedName="ConfigurationClassAffection.affectionKind";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies in the "VendorSpecificModuleDefinition" whether changes on this parameter do affect other parameters in a later configuration step. This element is deprecated and will be removed in future versions. mmt.qualifiedName="ConfigurationClassAffection" atpObject Instead of defining this constant inline, another constant is referenced. mmt.qualifiedName="ConstantReference" atpObject,atpPrototype The referenced constant. mmt.qualifiedName="ConstantReference.constant";pureMM.maxOccurs="1";pureMM.minOccurs="1" Instead of defining this constant inline, another constant is referenced. mmt.qualifiedName="ConstantReference" atpObject,atpPrototype Specification of a constant that can be part of a package, i.e. it can be defined stand-alone. mmt.qualifiedName="ConstantSpecification" atpObject Specification of an expression leading to a value of a given datatype. mmt.qualifiedName="value.ConstantSpecification";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specification of a constant that can be part of a package, i.e. it can be defined stand-alone. mmt.qualifiedName="ConstantSpecification" atpObject Represents a Container definition in the ECU Configuration Description. mmt.qualifiedName="Container" atpObject Reference to the definition of this Container in the ECU Configuration Parameter Definition. mmt.qualifiedName="Container.definition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="-10" atpSplitable Aggregates all ECU Configuration Values within this Container. mmt.qualifiedName="parameterValue.Container";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Aggregates all References with this container. mmt.qualifiedName="referenceValue.Container";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Aggregates all sub-containers within this container. mmt.qualifiedName="subContainer.Container";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Represents a Container definition in the ECU Configuration Description. mmt.qualifiedName="Container" atpObject Base class used to gather common attributes of configuration container definitions. mmt.qualifiedName="ContainerDef" atpObject Specifies if the number of instances of this container may be changed post-build time. This parameter may only be set to true if all of the following conditions hold: - the container's upperMultiplicity > lowerMultiplicity - all parameters within the container and subContainers are post-build time changeable. If any of the aggregated parameters is either pre-compile time or link time this attribute is ignored and may be omitted. mmt.qualifiedName="ContainerDef.postBuildChangeable";pureMM.maxOccurs="1";pureMM.minOccurs="1" The communication cycle where the frame is send is described by the attribute "cycleCounter". mmt.qualifiedName="CycleCounter" atpObject The communication cycle where the frame described by this timing is sent. If a timing is given in this way the referencing cluster must specify the NUMBER-OF-CYCLES as upper bound and point of total repetition. This value is incremented at the beginning of each new cycle, ranging from 0 to 63, and is reset to 0 after a sequence of 64 cycles. mmt.qualifiedName="CycleCounter.CycleCounter";pureMM.maxOccurs="1";pureMM.minOccurs="1" The communication cycle where the frame is send is described by the attribute "cycleCounter". mmt.qualifiedName="CycleCounter" atpObject The communication cycle where the frame is send is described by the attributes baseCycle and cycleRepetition. mmt.qualifiedName="CycleRepetition" atpObject The first communication cycle where the frame is sent. This value is incremented at the beginning of each new cycle, ranging from 0 to 63, and is reset to 0 after a sequence of 64 cycles. mmt.qualifiedName="CycleRepetition.BaseCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of communication cycles (after the first cycle) whenever the frame described by this timing is sent again. mmt.qualifiedName="CycleRepetition.CycleRepetition";pureMM.maxOccurs="1";pureMM.minOccurs="1" The communication cycle where the frame is send is described by the attributes baseCycle and cycleRepetition. mmt.qualifiedName="CycleRepetition" atpObject Specification of a cyclic sending behavior. mmt.qualifiedName="CyclicTiming" atpObject Number of repetitions the pdu is sent from the moment the stop condition has been met mmt.qualifiedName="CyclicTiming.finalRepetitions";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specification of the repeating cycle. mmt.qualifiedName="repeatingTime.CyclicTiming";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specification of the time that is needed before the pdu can be sent the first time. mmt.qualifiedName="startingTime.CyclicTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specification of a cyclic sending behavior. mmt.qualifiedName="CyclicTiming" atpObject The processing unit writes a digital value to a register of the DAC and the value is converted to an analogue value at a given pin. mmt.qualifiedName="DAC" atpObject mmt.qualifiedName="DataConstr" atpObject This is one particular rule within the data constraints, mmt.qualifiedName="DataConstr.dataConstrRule";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="30";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="DataConstr" atpObject mmt.qualifiedName="DataConstrRule" atpObject Describes the limitiations applicapble on the physical domain (as opposed to the internal domain). mmt.qualifiedName="DataConstrRule.physConstrs";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Describes the limitiations applicapble on the internal domain (as opposed to the physical domain). mmt.qualifiedName="DataConstrRule.internalConstrs";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" mmt.qualifiedName="DataConstrRule" atpObject A data element of a sender-receiver interface, supporting signal like communication patterns. mmt.qualifiedName="DataElementPrototype" atpObject,atpPrototype Qualifies whether the content of the data element is queued. If it is queued, then the data element has "event" semantics, i.e. data elements are stored in a queue and all data elements are processed in "first in first out" order. If it is not queued, then the "last is best" semantics applies. Please note: Depending on the read access cycle to the data element some values might not be processed by the receiver. mmt.qualifiedName="DataElementPrototype.isQueued";pureMM.maxOccurs="1";pureMM.minOccurs="1" A data element of a sender-receiver interface, supporting signal like communication patterns. mmt.qualifiedName="DataElementPrototype" atpObject,atpPrototype Base class for prototypical roles of a datatype. mmt.qualifiedName="DataPrototype" atpObject,atpPrototype This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="DataPrototype.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="DataPrototype.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType mmt.qualifiedName="DataPrototypeRef" atpObject This represents the referred dataPrototype. mmt.qualifiedName="DataPrototypeRef.dataPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="DataPrototypeRef" atpObject mmt.qualifiedName="DataPrototypeRef_DataPrototype" atpObject,instanceRef mmt.qualifiedName="DataPrototypeRef_DataPrototype.compositionComponentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataPrototypeRef_DataPrototype.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="DataPrototypeRef_DataPrototype.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="DataPrototypeRef_DataPrototype.dataPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.target mmt.qualifiedName="DataPrototypeRef_DataPrototype" atpObject,instanceRef The presence of a DataReadAccess implies that a RunnableEntity needs access to a DataElementPrototype in an RPortPrototype. The RunnableEntity will not modify the contents of the data but only read the information. The RunnableEntity expects that the contents of this data does NOT change during the entire duration of its execution. mmt.qualifiedName="DataReadAccess" atpObject The data element that is going to be read by this runnable. mmt.qualifiedName="dataElement.DataReadAccess";pureMM.maxOccurs="1";pureMM.minOccurs="1" The presence of a DataReadAccess implies that a RunnableEntity needs access to a DataElementPrototype in an RPortPrototype. The RunnableEntity will not modify the contents of the data but only read the information. The RunnableEntity expects that the contents of this data does NOT change during the entire duration of its execution. mmt.qualifiedName="DataReadAccess" atpObject mmt.qualifiedName="DataReadAccess_dataElement" atpObject,instanceRef mmt.qualifiedName="DataReadAccess_dataElement.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataReadAccess_dataElement.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DataReadAccess_dataElement" atpObject,instanceRef This event is raised by the RTE when the Com layer detects and notifies an error concerning the reception of the referenced data element. mmt.qualifiedName="DataReceiveErrorEvent" atpObject Data element referenced by event mmt.qualifiedName="data.event";pureMM.maxOccurs="1";pureMM.minOccurs="1" This event is raised by the RTE when the Com layer detects and notifies an error concerning the reception of the referenced data element. mmt.qualifiedName="DataReceiveErrorEvent" atpObject mmt.qualifiedName="DataReceiveErrorEvent_data" atpObject,instanceRef mmt.qualifiedName="DataReceiveErrorEvent_data.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataReceiveErrorEvent_data.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DataReceiveErrorEvent_data" atpObject,instanceRef A DataReceivePoint allows a RunnableEntity to explicitly query for received information, thereby blocking write access to the same information only for a very brief period. mmt.qualifiedName="DataReceivePoint" atpObject The data element to be explicitly read. mmt.qualifiedName="dataElement.DataReceivePoint";pureMM.maxOccurs="1";pureMM.minOccurs="1" A DataReceivePoint allows a RunnableEntity to explicitly query for received information, thereby blocking write access to the same information only for a very brief period. mmt.qualifiedName="DataReceivePoint" atpObject mmt.qualifiedName="DataReceivePoint_dataElement" atpObject,instanceRef mmt.qualifiedName="DataReceivePoint_dataElement.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataReceivePoint_dataElement.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DataReceivePoint_dataElement" atpObject,instanceRef The event is raised when the referenced data elements are received. mmt.qualifiedName="DataReceivedEvent" atpObject Data element referenced by event mmt.qualifiedName="data.event";pureMM.maxOccurs="1";pureMM.minOccurs="1" The event is raised when the referenced data elements are received. mmt.qualifiedName="DataReceivedEvent" atpObject mmt.qualifiedName="DataReceivedEvent_data" atpObject,instanceRef mmt.qualifiedName="DataReceivedEvent_data.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataReceivedEvent_data.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DataReceivedEvent_data" atpObject,instanceRef The event is raised when the referenced data elements have been sent or an error occurs. mmt.qualifiedName="DataSendCompletedEvent" atpObject Data send point that triggers the event. mmt.qualifiedName="event.eventSource";pureMM.maxOccurs="1";pureMM.minOccurs="1" The event is raised when the referenced data elements have been sent or an error occurs. mmt.qualifiedName="DataSendCompletedEvent" atpObject A DataSendPoint specifies that a RunnableEntity explicitly sends a certain DataElementPrototype. mmt.qualifiedName="DataSendPoint" atpObject The data element that is sent by this runnable. mmt.qualifiedName="dataElement.DataSendPoint";pureMM.maxOccurs="1";pureMM.minOccurs="1" A DataSendPoint specifies that a RunnableEntity explicitly sends a certain DataElementPrototype. mmt.qualifiedName="DataSendPoint" atpObject mmt.qualifiedName="DataSendPoint_dataElement" atpObject,instanceRef mmt.qualifiedName="DataSendPoint_dataElement.pPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataSendPoint_dataElement.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DataSendPoint_dataElement" atpObject,instanceRef A LIN specific extension of the common RelativelyScheduledTiming. The extension maps the LIN specific free data frames into SystemTemplate. The base type keeps scheduling for those free data frames applicable. mmt.qualifiedName="DataTiming" atpObject mmt.qualifiedName="FreeFormat.DataTiming";pureMM.maxOccurs="1";pureMM.minOccurs="1" A LIN specific extension of the common RelativelyScheduledTiming. The extension maps the LIN specific free data frames into SystemTemplate. The base type keeps scheduling for those free data frames applicable. mmt.qualifiedName="DataTiming" atpObject The presence of a DataWriteAccess means that the RunnableEntity will potentially modify the DataElementPrototype in the PPortPrototype. The RunnableEntity has free access to the DataElementPrototype while it is running. The RunnableEntity has the responsibility to make sure that the DataElementPrototype is in a consistent state when it returns. When using DataWriteAccess the new values of the DataElementPrototype is not made available via the communication infrastructure before the RunnableEntity returns (exits the "Running" state). mmt.qualifiedName="DataWriteAccess" atpObject The data element that is going to be written to by this runnable. mmt.qualifiedName="dataElement.DataWriteAccess";pureMM.maxOccurs="1";pureMM.minOccurs="1" The presence of a DataWriteAccess means that the RunnableEntity will potentially modify the DataElementPrototype in the PPortPrototype. The RunnableEntity has free access to the DataElementPrototype while it is running. The RunnableEntity has the responsibility to make sure that the DataElementPrototype is in a consistent state when it returns. When using DataWriteAccess the new values of the DataElementPrototype is not made available via the communication infrastructure before the RunnableEntity returns (exits the "Running" state). mmt.qualifiedName="DataWriteAccess" atpObject mmt.qualifiedName="DataWriteAccess_dataElement" atpObject,instanceRef mmt.qualifiedName="DataWriteAccess_dataElement.pPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DataWriteAccess_dataElement.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DataWriteAccess_dataElement" atpObject,instanceRef Represents the I-PDU's handled by Dcm. mmt.qualifiedName="DcmIPdu" atpObject The default value consists of a number of elements. Each element is one byte long and the number of elements is specified by SduLength. mmt.qualifiedName="DefaultValueElement" atpObject The integer value of a freely defined data byte. mmt.qualifiedName="DefaultValueElement.elementByteValue";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute specifies the byte position of the element within the default value mmt.qualifiedName="DefaultValueElement.elementPosition";pureMM.maxOccurs="1";pureMM.minOccurs="1" The default value consists of a number of elements. Each element is one byte long and the number of elements is specified by SduLength. mmt.qualifiedName="DefaultValueElement" atpObject Annotation to a "delegated port" to specify the Signal Fan In or Signal Fan Out inside the Composition Type. mmt.qualifiedName="DelegatedPortAnnotation" atpObject Specify the Signal Fan In or Signal Fan Out inside the Composition Type mmt.qualifiedName="DelegatedPortAnnotation.signalFan";pureMM.maxOccurs="1";pureMM.minOccurs="1" Annotation to a "delegated port" to specify the Signal Fan In or Signal Fan Out inside the Composition Type. mmt.qualifiedName="DelegatedPortAnnotation" atpObject A delegation connector delegates one inner PortPrototype (a port of a component that is used inside the composition) to a outer PortPrototype of compatible type that belongs directly to the composition (a port that is owned by the composition). mmt.qualifiedName="DelegationConnectorPrototype" atpObject,atpStructureElement Connects these ports. The role (inner, outer) of those ports is derived from the context (port of composition or port of inner component). The port that belongs to the ComponentPrototype in the composition mmt.qualifiedName="innerPort.DelegationConnectorPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" The port that is located on the outside of the CompositionType mmt.qualifiedName="DelegationConnectorPrototype.outerPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" A delegation connector delegates one inner PortPrototype (a port of a component that is used inside the composition) to a outer PortPrototype of compatible type that belongs directly to the composition (a port that is owned by the composition). mmt.qualifiedName="DelegationConnectorPrototype" atpObject,atpStructureElement mmt.qualifiedName="DelegationConnectorPrototype_innerPort" atpObject,instanceRef mmt.qualifiedName="DelegationConnectorPrototype_innerPort.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="DelegationConnectorPrototype_innerPort.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="DelegationConnectorPrototype_innerPort" atpObject,instanceRef Is used to connect HWPorts of a HWContainer with HWPorts of the contained HWElements. mmt.qualifiedName="DelegationHWConnection" atpObject Reference to the HWPort of the connected inner HWElement. A single HWPort can only be referenced by exactly one DelegationHWConnection. mmt.qualifiedName="DelegationHWConnection.innerPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the HWPort of the connected outer HWElement. A single HWPort can only be referenced by exactly one DelegationHWConnection. mmt.qualifiedName="DelegationHWConnection.outerPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Is used to connect HWPorts of a HWContainer with HWPorts of the contained HWElements. mmt.qualifiedName="DelegationHWConnection" atpObject General dependency, typically on the existence of another artifact. mmt.qualifiedName="Dependency" atpObject Specification during for which process step(s) this dependency is required. mmt.qualifiedName="Dependency.usage";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Dependency on the existence of a certain file. mmt.qualifiedName="DependencyOnFile" atpObject The specified file needs to exist. mmt.qualifiedName="DependencyOnFile.xfile";pureMM.maxOccurs="1";pureMM.minOccurs="1" Dependency on the existence of a certain file. mmt.qualifiedName="DependencyOnFile" atpObject A specific file dependency: without the library that implementation cannot be used (compiled, linked, executed, ...). mmt.qualifiedName="DependencyOnLibrary" atpObject Maximum version compatible with implementation. If not set, there is limitation on the upper version. mmt.qualifiedName="DependencyOnLibrary.maxVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum version compatible with implementation. mmt.qualifiedName="DependencyOnLibrary.minVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" A specific file dependency: without the library that implementation cannot be used (compiled, linked, executed, ...). mmt.qualifiedName="DependencyOnLibrary" atpObject Derived value is of type Boolean mmt.qualifiedName="DerivedBooleanParamDef" atpObject Derived value is an Enumeration. mmt.qualifiedName="DerivedEnumerationParamDef" atpObject Derived value is of type Float mmt.qualifiedName="DerivedFloatParamDef" atpObject Derived value is of type Integer. mmt.qualifiedName="DerivedIntegerParamDef" atpObject Allows to define configuration items that are calculated based on the value of * other parameters values * elements (attributes /classes) defined in other AUTOSAR templates such as System template and SW component template. A calculation definition is given which defines how Configuration Editors and Generators can calculate the value from other values when needed to display/use the configuration item. The actual value is stored in the "value" attribute of the derived parameter. mmt.qualifiedName="DerivedParamType";xml.sequenceOffset="40" atpObject Definition of the formula used to calculate the value of the configuration element. mmt.qualifiedName="DerivedParamType.calculationFormula";pureMM.maxOccurs="1";pureMM.minOccurs="1" Definition of the languag used to specify the formula in attribute calculationFormula. Currentlfy, only informal definition of the formula is supported. mmt.qualifiedName="DerivedParamType.calculationLanguage";pureMM.maxOccurs="1";pureMM.minOccurs="1" Derived value is of type String. mmt.qualifiedName="DerivedStringParamDef" atpObject Specifies the abstract needs on the configuration of the Diagnostic Communication Manager for one "user". Details are an expert task for AUTOSAR Release 4.0. mmt.qualifiedName="DiagnosticCommunicationNeeds" atpObject Specifies the abstract needs on the configuration of the Diagnostic Event Manager for one diagnostic event. Its name can be regarded as a symbol identifying the diagnostic event from the viewpoint of the component or module which owns this class. mmt.qualifiedName="DiagnosticEventNeeds" atpObject Digital Input/Output peripherals provide the capability to send/receive data in a digital manner. Each digital input has an electrical range. When the voltage is less than a specified level, the input is represents logical low '0'. On the opposite when the voltage is higher than a specified value the input represents logical high '1'. A digital I/O can usually be programmed to be either an input or output. It can also be programmed to logically invert the input or output. The maximum frequency of a digital input or output is related to how fast the PU can read or write to the digital I/O register. It's very common for a digital I/O to have different functionality. One example is when a timer has an external clock signal associated with a digital I/O. In this case the maximum frequency is defined by the performance of the timer counter and can be found in the electrical characteristic of the peripheral datasheet. mmt.qualifiedName="DigitalIO" atpObject A general digital input can be enabled to trigger an interrupt on a falling, rising or both edges of an input signal. A clock, compare or count input on a timer can be programmed to increase, decrease or store the timer value if a change on the input pin has occurred. The condition for this change can be programmed to trigger an event in the same manner as for a digital input. mmt.qualifiedName="DigitalIO.edgeDetection";pureMM.maxOccurs="1";pureMM.minOccurs="1" Digital Input/Output peripherals provide the capability to send/receive data in a digital manner. Each digital input has an electrical range. When the voltage is less than a specified level, the input is represents logical low '0'. On the opposite when the voltage is higher than a specified value the input represents logical high '1'. A digital I/O can usually be programmed to be either an input or output. It can also be programmed to logically invert the input or output. The maximum frequency of a digital input or output is related to how fast the PU can read or write to the digital I/O register. It's very common for a digital I/O to have different functionality. One example is when a timer has an external clock signal associated with a digital I/O. In this case the maximum frequency is defined by the performance of the timer counter and can be found in the electrical characteristic of the peripheral datasheet. mmt.qualifiedName="DigitalIO" atpObject mmt.qualifiedName="DiscreteECUElectronics" atpObject The Display HW element derives from HW Sensor Actuator and can be connected to a PU via a serial or parallel interface. For the parallel mode the display can be connected to the data bus and address bus of a PU or to a peripheral. The most common serial interface for displays are: - I2C - SPI The most common physical interface for high resolution displays are the LVDS interface (Low Voltage Differential Signalling). This interface has three different lines for colours (RGB) and additional lines for control signals. mmt.qualifiedName="DisplayHW" atpObject Defines whether the display has a background lighting. This eases the readability of the displays during bad daylight conditions. mmt.qualifiedName="DisplayHW.backlight";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the visibility of the display. mmt.qualifiedName="DisplayHW.brightness";pureMM.maxOccurs="1";pureMM.minOccurs="1" If the display can present numerical, alpha-numerical, semi-graphical or graphical objects. mmt.qualifiedName="DisplayHW.btypeOfCharacters";pureMM.maxOccurs="1";pureMM.minOccurs="1" If the display has an in-built character generator. mmt.qualifiedName="DisplayHW.characterGenerator";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines which character set that can be handled by the display. There is a number of standardised character sets like ISO-8859-1 or Unicode. mmt.qualifiedName="DisplayHW.characterSet";pureMM.maxOccurs="1";pureMM.minOccurs="0" If the display can show objects in monochrome, grey scale or in colour. mmt.qualifiedName="DisplayHW.colour";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the ratio of the display resolution in horizontal versus vertical direction (e.g. 16 to 9). mmt.qualifiedName="DisplayHW.resolutionRation";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the number of the smallest graphical elements which can be displayed in horizontal direction. mmt.qualifiedName="DisplayHW.resolutionX";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the number of the smallest graphical elements which can be displayed in vertical direction. mmt.qualifiedName="DisplayHW.resolutionY";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines how long it takes for the display to show a changed element at -20 degree C. mmt.qualifiedName="DisplayHW.responseTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the angle range where the display can be observed. mmt.qualifiedName="DisplayHW.viewingAngle";pureMM.maxOccurs="1";pureMM.minOccurs="1" The Display HW element derives from HW Sensor Actuator and can be connected to a PU via a serial or parallel interface. For the parallel mode the display can be connected to the data bus and address bus of a PU or to a peripheral. The most common serial interface for displays are: - I2C - SPI The most common physical interface for high resolution displays are the LVDS interface (Low Voltage Differential Signalling). This interface has three different lines for colours (RGB) and additional lines for control signals. mmt.qualifiedName="DisplayHW" atpObject mmt.qualifiedName="DisplayName" atpMixedString,atpObject Use <docRevision> , to generate information on the corresponding document version. mmt.qualifiedName="DocRevision";xml.sequenceOffset="20" atpObject Use revisionLabel, to enter the version number of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. Therefore it is still kept as String. mmt.qualifiedName="DocRevision.revisionLabel";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" Use revisionLabelP1, to enter the version number of the ** of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. This element is used, if the document or document section is the result of a merge process in which two branches are merged in to one new revision. mmt.qualifiedName="DocRevision.revisionLabelP1";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Use revisionLabelP1, to enter the version number of the ** of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. This element is used, if the document or document section is the result of a merge process in which two branches are merged in to one new revision. mmt.qualifiedName="DocRevision.revisionLabelP2";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" <state> represents the current state of the current file according to the configuration management plan. mmt.qualifiedName="DocRevision.state";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" This element contains the name of the person who initiated the document revision. If the initiator cannot be referenced as <teamMember> in the current document his name can be given in this element. mmt.qualifiedName="DocRevision.issuedBy";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This specifies the time, when the object in question was released mmt.qualifiedName="DocRevision.date";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="80" Use <modification> to record what has changed in a document in comparison to its predecessor. mmt.qualifiedName="DocRevision.modification";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="100";xml.typeElement="false";xml.typeWrapperElement="false" Use <docRevision> , to generate information on the corresponding document version. mmt.qualifiedName="DocRevision";xml.sequenceOffset="20" atpObject This class represents a documentation block.It represents a sequence of paragraphs. Main intention is to provide References to external objects which are not processed by AUTOSAR-tooling. mmt.qualifiedName="DocumentationBlock" atpMixed,atpObject Use <p> to create a paragraph for continuous texts. mmt.qualifiedName="DocumentationBlock.p";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="50" This class represents a documentation block.It represents a sequence of paragraphs. Main intention is to provide References to external objects which are not processed by AUTOSAR-tooling. mmt.qualifiedName="DocumentationBlock" atpMixed,atpObject Dynamic part of a multiplexed I-Pdu. Reserved space which is used to transport varying SignalIPdus at the same position, controlled by the corresponding selectorFieldCode. mmt.qualifiedName="DynamicPart" atpObject Com IPdu alternatives that are transmitted in the Dynamic Part of the MultiplexedIPdu. mmt.qualifiedName="dynamicPartAlternative.DynamicPart";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Dynamic part of a multiplexed I-Pdu. Reserved space which is used to transport varying SignalIPdus at the same position, controlled by the corresponding selectorFieldCode. mmt.qualifiedName="DynamicPart" atpObject One of the Com IPdu alternatives that are transmitted in the Dynamic Part of the MultiplexedIPdu. The selectorFieldCode specifies which Com IPdu is contained in the DynamicPart within a certain transmission of a multiplexed PDU. mmt.qualifiedName="DynamicPartAlternative" atpObject Reference to a Com IPdu which is routed to the IPduM module and is combined to a multiplexedPdu. mmt.qualifiedName="DynamicPartAlternative.iPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Dynamic part that shall be used to initialize this multiplexed IPdu. Constraint: Only one "DynamicPartAlternative" in a "DynamicPart" shall be the initialDynamicPart. mmt.qualifiedName="DynamicPartAlternative.initialDynamicPart";pureMM.maxOccurs="1";pureMM.minOccurs="1" The selector field is part of a multiplexed IPdu. It consists of contiguous bits. The value of the selector field selects the layout of the dynamic part of the IPdu. mmt.qualifiedName="DynamicPartAlternative.selectorFieldCode";pureMM.maxOccurs="1";pureMM.minOccurs="1" One of the Com IPdu alternatives that are transmitted in the Dynamic Part of the MultiplexedIPdu. The selectorFieldCode specifies which Com IPdu is contained in the DynamicPart within a certain transmission of a multiplexed PDU. mmt.qualifiedName="DynamicPartAlternative" atpObject The ECU provides information about an ECU and its internal hardware elements. The described hardware elements are related to some extent to basic software configuration and the AUTOSAR generation process. mmt.qualifiedName="ECU" atpObject,atpType Reference to the software component describing the ECU Abstraction software module for this ECU. mmt.qualifiedName="ECU.ecuAbstraction";pureMM.maxOccurs="1";pureMM.minOccurs="0" The ECU provides information about an ECU and its internal hardware elements. The described hardware elements are related to some extent to basic software configuration and the AUTOSAR generation process. mmt.qualifiedName="ECU" atpObject,atpType A specialization of a Communication HW Port that is availabe for the inter ECU communication. mmt.qualifiedName="ECUCommunicationPort" atpObject The abstract class ECU Electronics HW Element contains all elements and attributes common for all kind of ECU Electronics. mmt.qualifiedName="ECUElectronics" atpObject Defines if the ECU Electronic can be enabled and disabled. mmt.qualifiedName="ECUElectronics.canBeDisabled";pureMM.maxOccurs="1";pureMM.minOccurs="1" ECUMapping allows to assign an ECU hardware type (defined in the ECU Resource Template) to an ECUInstance used in a physical topology. mmt.qualifiedName="ECUMapping" atpObject The ECUMapping contains the mapping of all CommunicationControllers of the ECU. mmt.qualifiedName="commControllerMapping.ECUMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Reference to the EcuInstance in the System Template mmt.qualifiedName="ECUMapping.ecuInstance";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Ecu description in the ECU Resource Template mmt.qualifiedName="ECUMapping.ecu";pureMM.maxOccurs="1";pureMM.minOccurs="1" The ECUMapping contains the mapping of all HW Ports of the ECU. mmt.qualifiedName="portMapping.ECUMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" ECUMapping allows to assign an ECU hardware type (defined in the ECU Resource Template) to an ECUInstance used in a physical topology. mmt.qualifiedName="ECUMapping" atpObject mmt.qualifiedName="ECUPrototype" atpObject,atpPrototype mmt.qualifiedName="ECUPrototype.ECU";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType mmt.qualifiedName="ECUPrototype" atpObject,atpPrototype This is an emphasized text. As a compromise it contains some rendering oriented attributes such as color and font. mmt.qualifiedName="EType" atpMixedString,atpObject The ECUAbstraction is a special AtomicSoftwareComponent that sits between a component that wants to access ECUperiphery and the Microcontroller Abstraction. The EcuAbstractionComponentType introduces the possibility to link from the software representation to its hardware description provided by the ECU Resource Template. mmt.qualifiedName="EcuAbstractionComponentType" atpObject,atpType Reference from the EcuAbstractionComponentType to the Basic Software Module Description describing the BSW part of the ECU Abstraction Component. mmt.qualifiedName="EcuAbstractionComponentType.bswModuleDescription";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference from the EcuAbstractionComponentType to the description of the used HWElements. mmt.qualifiedName="EcuAbstractionComponentType.hardwareElement";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The ECUAbstraction is a special AtomicSoftwareComponent that sits between a component that wants to access ECUperiphery and the Microcontroller Abstraction. The EcuAbstractionComponentType introduces the possibility to link from the software representation to its hardware description provided by the ECU Resource Template. mmt.qualifiedName="EcuAbstractionComponentType" atpObject,atpType This represents the anchor point of the ECU configuration description. mmt.qualifiedName="EcuConfiguration" atpObject Represents the extract of the System Configuration that is relevant for the ECU configured with that ECU Configuration Description. mmt.qualifiedName="EcuConfiguration.ecuExtract";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the EcuSwComposition which holds the AUTOSAR Service Software Components. mmt.qualifiedName="EcuConfiguration.ecuSwComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1" References to the configuration of individual software modules that are present on this ECU. mmt.qualifiedName="EcuConfiguration.module";pureMM.maxOccurs="-1";pureMM.minOccurs="1" This represents the anchor point of the ECU configuration description. mmt.qualifiedName="EcuConfiguration" atpObject ECUInstances are used to define the ECUs used in the topology. The type of the ECU is defined by a reference to an ECU specified with the ECU resource description. mmt.qualifiedName="EcuInstance" atpObject With this reference it is possible to identify which IPduGroups are applicable for which CommunicationConnector/ ECU. mmt.qualifiedName="EcuInstance.associatedIPduGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0" With this reference it is possible to identify which PduR IPdu Groups are applicable for which CommunicationConnector/ ECU. mmt.qualifiedName="EcuInstance.associatedPdurIPduGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This ID is returned by a call to Com_GetConfigurationId() mmt.qualifiedName="EcuInstance.comConfigurationId";pureMM.maxOccurs="1";pureMM.minOccurs="0" The COM scheduling time is used in order to be able to calculate the worst case bus timing. The processing period shall be specified AUTOSAR conform in seconds. mmt.qualifiedName="EcuInstance.comProcessingPeriod";pureMM.maxOccurs="1";pureMM.minOccurs="0" Optional signal Routing processing period of the COM scheduling in order to be able to calculate the worst case bus timing. Only applicable if a different processing period for Tx and Routing shall be respected. If not present the "comProcessingPeriod" attribute shall be used for Tx and Gateway operation. The processing period shall be specified AUTOSAR conform in seconds. mmt.qualifiedName="EcuInstance.comProcessingPeriodGw";pureMM.maxOccurs="1";pureMM.minOccurs="0" Optional Rx processing period of the COM scheduling in order to be able to calculate the worst case bus timing. Only applicable if a different processing period for Tx and Rx shall be respected. If not present the "comProcessingPeriod" attribute shall be used for Tx and Rx operation. The processing period shall be specified AUTOSAR conform in seconds. mmt.qualifiedName="EcuInstance.comProcessingPeriodRx";pureMM.maxOccurs="1";pureMM.minOccurs="0" CommunicationControllers of the ECU. mmt.qualifiedName="commController.EcuInstance";pureMM.maxOccurs="-1";pureMM.minOccurs="1" All channels controlled by a single controller. mmt.qualifiedName="connector.EcuInstance";pureMM.maxOccurs="-1";pureMM.minOccurs="0" An ECU specific ID for responses of diagnostic routines. mmt.qualifiedName="EcuInstance.diagnosticAddress";pureMM.maxOccurs="1";pureMM.minOccurs="0" unique PDURconfiguration identifier mmt.qualifiedName="EcuInstance.pduRConfigurationId";pureMM.maxOccurs="1";pureMM.minOccurs="0" An ECU specific ID for responses of diagnostic routines. mmt.qualifiedName="EcuInstance.responseAddress";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specifies whether the ECU instance may be put to a "low power mode" TRUE: sleep mode is supported FALSE: sleep mode is not supported Note: This flag may only be set to TRUE if the feature is supported by both hardware and basic software. mmt.qualifiedName="EcuInstance.sleepModeSupported";pureMM.maxOccurs="1";pureMM.minOccurs="1" Driver support for wakeup over Bus. mmt.qualifiedName="EcuInstance.wakeUpOverBusSupported";pureMM.maxOccurs="1";pureMM.minOccurs="1" ECUInstances are used to define the ECUs used in the topology. The type of the ECU is defined by a reference to an ECU specified with the ECU resource description. mmt.qualifiedName="EcuInstance" atpObject This represents the anchor point of an ECU Configuration Parameter Definition within the AUTOSAR templates structure. mmt.qualifiedName="EcuParameterDefinition" atpObject References to the module definitions of individual software modules. mmt.qualifiedName="EcuParameterDefinition.module";pureMM.maxOccurs="-1";pureMM.minOccurs="1" This represents the anchor point of an ECU Configuration Parameter Definition within the AUTOSAR templates structure. mmt.qualifiedName="EcuParameterDefinition" atpObject Resource estimations for RTE and BSW of a single ECU instance. mmt.qualifiedName="EcuResourceEstimation" atpObject Estimation for the resource consumption of the basic software. mmt.qualifiedName="bswResourceEstimation.EcuResourceEstimation";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the ECU this estimation is done for. mmt.qualifiedName="EcuResourceEstimation.ecuInstance";pureMM.maxOccurs="1";pureMM.minOccurs="1" Estimation for the resource consumption of the run time environment. mmt.qualifiedName="rteResourceEstimation.EcuResourceEstimation";pureMM.maxOccurs="1";pureMM.minOccurs="0" References to SwCompToEcuMappings that have been taken into account for the resource estimations. This way it is possible to define dfferent EcuResourceEstimations with different mappings, e.g. before and after mapping an additional SW component. mmt.qualifiedName="EcuResourceEstimation.swCompToEcuMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Resource estimations for RTE and BSW of a single ECU instance. mmt.qualifiedName="EcuResourceEstimation" atpObject Specifies the abstract needs on the configuration of the ECU State Manager for one "user". This class currently contains no attributes. Its name can be regarded as a symbol identifying the user from the viewpoint of the component or module which owns this class. mmt.qualifiedName="EcuStateMgrUserNeeds" atpObject EcuSwComposition contains the complete Software Composition in an ECU, consisting both of application software components and service components. mmt.qualifiedName="EcuSwComposition" atpObject,atpStructureElement Service components used within one EcuSwComposition mmt.qualifiedName="component.EcuSwComposition";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The connectors used for connecting Service ports with the AtomicSoftwareComponents' service ports. mmt.qualifiedName="connector.EcuSwComposition";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Represents the extract of the System Configuration which the referencing EcuSwComposition applies to, in particular the softwareComposition. As EcuSwComposition is only valid in the context of a given EcuConfiguration, this association needs to have the same target as the ecuExtract association from EcuConfiguration. mmt.qualifiedName="EcuSwComposition.ecuExtract";pureMM.maxOccurs="1";pureMM.minOccurs="1" EcuSwComposition contains the complete Software Composition in an ECU, consisting both of application software components and service components. mmt.qualifiedName="EcuSwComposition" atpObject,atpStructureElement Specifies electrical ranges for different applications within the ECU Resource Template. mmt.qualifiedName="ElectricalRange" atpObject Maximum Current Unit: A mmt.qualifiedName="ElectricalRange.maxCurrent";pureMM.maxOccurs="1";pureMM.minOccurs="0" Maximum voltage Unit: V mmt.qualifiedName="ElectricalRange.maxVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum Current Unit: A mmt.qualifiedName="ElectricalRange.minCurrent";pureMM.maxOccurs="1";pureMM.minOccurs="0" Minimum voltage Unit: V mmt.qualifiedName="ElectricalRange.minVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="1" Typical Current Unit: A mmt.qualifiedName="ElectricalRange.typicalCurrent";pureMM.maxOccurs="1";pureMM.minOccurs="0" Typical voltage Unit: V mmt.qualifiedName="ElectricalRange.typicalVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specifies electrical ranges for different applications within the ECU Resource Template. mmt.qualifiedName="ElectricalRange" atpObject According to the COM Specification, signal groups without signals are allowed. These have a "signalLength" = 0. In this case there shall be an "update-bit" configured. mmt.qualifiedName="EmptySignalMapping" atpObject Reference to a SystemSignal with "signalLength" = 0 and an UpdateBit. mmt.qualifiedName="EmptySignalMapping.systemSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" According to the COM Specification, signal groups without signals are allowed. These have a "signalLength" = 0. In this case there shall be an "update-bit" configured. mmt.qualifiedName="EmptySignalMapping" atpObject This meta-class contains information about end-to-end protection. The set of applicable attributes depends on the actual value of the category attribute of EndToEndProtection. mmt.qualifiedName="EndToEndDescription" atpObject The category represents the identification of the concrete E2E profile. The applicable values are specified in a semantic constraint and determine the applicable attributes of EndToEndDescription. mmt.qualifiedName="EndToEndDescription.category";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="-100" This represents a unique numerical identifier. Note: ID is used for protection against masquerading. The details concerning the maximum number of values (this information is specific for each E2E profile) applicable for this attribute are controlled by a semantic constraint that depends on the category of the EndToEndProtection. mmt.qualifiedName="EndToEndDescription.dataId";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="-90" There are three inclusion modes how the implicit two-byte Data ID is included in the one-byte CRC: * dataIDMode = 0: Two bytes are included in the CRC (double ID configuration) This is used in variant 1A. * dataIDMode = 1: One of the two bytes byte is included, alternating high and low byte, depending on parity of the counter (alternating ID configuration). For even counter low byte is included; For odd counters the high byte is included. This is used in variant 1B. * dataIDMode = 2: Only low byte is included, high byte is never used. This is applicable if the IDs in a particular system are 8 bits. mmt.qualifiedName="EndToEndDescription.dataIdMode";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-85" This attribute represents the length of the Array representation of the Signal Group/DataElementPrototype including CRC and Counter in bits. mmt.qualifiedName="EndToEndDescription.dataLength";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-80" Initial maximum allowed gap between two counter values of two consecutively received valid Data, i.e. how many subsequent lost data is accepted. For example, if the receiver gets Data with counter 1 and MaxDeltaCounterInit is 1, then at the next reception the receiver can accept Counters with values 2 and 3, but not 4. Note that if the receiver does not receive new Data at a consecutive read, then the receiver increments the tolerance by 1. mmt.qualifiedName="EndToEndDescription.maxDeltaCounterInit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-70" Bit offset of CRC from the beginning of the Array representation of the Signal Group/DataElementPrototype (MSB order, bit numbering: bit 0 is the least important). The offset shall be a multiplicity of 8 and it should be 0 whenever possible. For example, offset 8 means that the CRC will take the byte 1, i.e. bits 8..15. If crcOffset is not present the value is defined by the selected profile. mmt.qualifiedName="EndToEndDescription.crcOffset";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-60" Bit offset of Counter from the beginning of the Array representation of the Signal Group/DataElementPrototype (MSB order, bit numbering: bit 0 is the least important). The offset shall be a multiplicity of 4 and it should be 8 whenever possible. For example, offset 8 means that the counter will take the low nibble of the byte 1, i.e. bits 8 .. 11. If counterOffset is not present the value is defined by the selected profile. mmt.qualifiedName="EndToEndDescription.counterOffset";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-50" This meta-class contains information about end-to-end protection. The set of applicable attributes depends on the actual value of the category attribute of EndToEndProtection. mmt.qualifiedName="EndToEndDescription" atpObject This meta-class represents the ability to describe a particular end to end protection. mmt.qualifiedName="EndToEndProtection" atpObject This represents the particular EndToEndDescription. mmt.qualifiedName="EndToEndProtection.endToEndProfile";pureMM.maxOccurs="1";pureMM.minOccurs="1" atpSplitable Defines to which DataElementPrototypes in the roles of one sender and one or more receivers this EndToEndprotection shall apply. In case several senders are defined to transport the data there may exist several EndToEndProtectionDataElementPrototype elements. mmt.qualifiedName="EndToEndProtection.endToEndProtectionDataElementPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Defines to which ISignalIPdu - ISignal pair this EndToEndProtection shall apply. In case several ISignals are used to transport the data (e.g. fan-out in the RTE) there may exist several EndToEndProtectionISignalIPdu definitions. mmt.qualifiedName="EndToEndProtection.endToEndProtectionISignalIPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable This meta-class represents the ability to describe a particular end to end protection. mmt.qualifiedName="EndToEndProtection" atpObject It is possible to protect the data exchanged between software components. For this purpose, for each communication to be protected, the user defines a separate EndToEndProtection (specifying a set of protection settings) and refers to a dataElement in the role of sender and to one or many dataElements in the role of receiver. For details, see End to End Library. mmt.qualifiedName="EndToEndProtectionDataElementPrototype" atpObject This represnets the receiver. Note that 1:n communication is supported for this use case. Can be optional if an ecu extract is provided and no receiver is part of the extract. This represnets the receiver. Note that 1:n communication is supported for this use case. mmt.qualifiedName="EndToEndProtectionDataElementPrototype.receiver";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This represents the sender. Can be optional if an ecu extract is provided and the sender is part of the extract. mmt.qualifiedName="EndToEndProtectionDataElementPrototype.sender";pureMM.maxOccurs="1";pureMM.minOccurs="0" It is possible to protect the data exchanged between software components. For this purpose, for each communication to be protected, the user defines a separate EndToEndProtection (specifying a set of protection settings) and refers to a dataElement in the role of sender and to one or many dataElements in the role of receiver. For details, see End to End Library. mmt.qualifiedName="EndToEndProtectionDataElementPrototype" atpObject mmt.qualifiedName="EndToEndProtectionDataElementPrototype_dataElement" atpObject,instanceRef mmt.qualifiedName="EndToEndProtectionDataElementPrototype_dataElement.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="EndToEndProtectionDataElementPrototype_dataElement.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="EndToEndProtectionDataElementPrototype_dataElement.targetDataPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="EndToEndProtectionDataElementPrototype_dataElement" atpObject,instanceRef It is possible to protect the inter-ECU data exchange of safety-related ISignal (refering to a SystemSignalGroup) at the level of COM IPdus using protection mechanisms provided by E2E Library. For each ISignal to be protected, a separate E2EProtectionISignalIPdu element must be created within the EndToEndProtectionSet. The E2EProtectionISignalIPdu element refers to the ISignal that is to be protected and to the ISignalIPdu that transmits the protected ISignal. The information how the referenced ISignal shall be protected (through which E2E Profile and with which E2E settings) is defined in the EndToEndDescription element. mmt.qualifiedName="EndToEndProtectionISignalIPdu" atpObject This attribute defines the beginning offset (in bits) of the Array representation of the Signal Group (including CRC, counter and application signal group) in the IPdu. This attribute is mandatory and the dataOffset shall always be defined. mmt.qualifiedName="EndToEndProtectionISignalIPdu.dataOffset";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the ISignal (representing a signal group) that is to be protected. mmt.qualifiedName="EndToEndProtectionISignalIPdu.iSignalGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the SignalPdu that transmits the protected ISignal (group). mmt.qualifiedName="EndToEndProtectionISignalIPdu.iSignalIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" It is possible to protect the inter-ECU data exchange of safety-related ISignal (refering to a SystemSignalGroup) at the level of COM IPdus using protection mechanisms provided by E2E Library. For each ISignal to be protected, a separate E2EProtectionISignalIPdu element must be created within the EndToEndProtectionSet. The E2EProtectionISignalIPdu element refers to the ISignal that is to be protected and to the ISignalIPdu that transmits the protected ISignal. The information how the referenced ISignal shall be protected (through which E2E Profile and with which E2E settings) is defined in the EndToEndDescription element. mmt.qualifiedName="EndToEndProtectionISignalIPdu" atpObject This represents a container for collection EndToEndProtectionInformation. mmt.qualifiedName="EndToEndProtectionSet" atpObject This is one particular EndToEndProtection. mmt.qualifiedName="EndToEndProtectionSet.endToEndProtection";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable This represents a container for collection EndToEndProtectionInformation. mmt.qualifiedName="EndToEndProtectionSet" atpObject Configuration parameter type for enumeration literals definition. mmt.qualifiedName="EnumerationLiteralDef" atpObject Configuration parameter type for Enumeration. mmt.qualifiedName="EnumerationParamDef";xml.sequenceOffset="0" atpObject Default value of the enumeration configuration parameter. This string nees to be one of the literals specified for this enumeration. mmt.qualifiedName="EnumerationParamDef.defaultValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" Aggregation on the literals used to define this enumeration parameter. mmt.qualifiedName="literal.EnumerationParamDef";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Configuration parameter type for Enumeration. mmt.qualifiedName="EnumerationParamDef";xml.sequenceOffset="0" atpObject Representing a configuration value of definition type EnumerationParamDef mmt.qualifiedName="EnumerationValue" atpObject Stores the chosen literal. mmt.qualifiedName="EnumerationValue.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Representing a configuration value of definition type EnumerationParamDef mmt.qualifiedName="EnumerationValue" atpObject Provides information on what extra bits are used for error detection and correction. mmt.qualifiedName="ErrorDetectionCorrection" atpObject How many error bits can be corrected. Unit: Bit mmt.qualifiedName="ErrorDetectionCorrection.correctedBits";pureMM.maxOccurs="1";pureMM.minOccurs="1" How many bit errors can be reconginsed. Unit: Bit mmt.qualifiedName="ErrorDetectionCorrection.detectedBits";pureMM.maxOccurs="1";pureMM.minOccurs="1" How many extra bits are used for ensuring error detection and correction. Unit: Bit mmt.qualifiedName="ErrorDetectionCorrection.extraBits";pureMM.maxOccurs="1";pureMM.minOccurs="1" Provides information on what extra bits are used for error detection and correction. mmt.qualifiedName="ErrorDetectionCorrection" atpObject Specification of a event driven sending behavior. The PDU is sent n (numberOfRepeat + 1) times separated by the repetitionPeriod. If numberOfRepeats = 0, then the Pdu is sent just once. mmt.qualifiedName="EventControlledTiming" atpObject Defines the number of repetitions for the Direct/N-Times transmission mode and the event driven part of Mixed transmission mode. mmt.qualifiedName="EventControlledTiming.numberOfRepeats";pureMM.maxOccurs="1";pureMM.minOccurs="1" If the EventControlledTiming is aggregated by the IPduTiming the repetitionPeriod specifies the time in seconds that elapses before the pdu can be sent the next time (Minimum repeat gap between two pdus). If the EventControlledTiming is aggregated by the SignalTriggering the repetitionPeriod specifies the time in seconds that elapses before the signal can be sent the next time (Minimum repeat gap between two signals). mmt.qualifiedName="repetitionPeriod.EventControlledTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specification of a event driven sending behavior. The PDU is sent n (numberOfRepeat + 1) times separated by the repetitionPeriod. If numberOfRepeats = 0, then the Pdu is sent just once. mmt.qualifiedName="EventControlledTiming" atpObject Prevents an executable entity running in the area from being preempted. mmt.qualifiedName="ExclusiveArea" atpObject Base class for several means how to describe the ExecutionTime of software. The required context information is provided through this class. mmt.qualifiedName="ExecutionTime" atpObject Provides information on a ECUPrototype based on one ECU type. mmt.qualifiedName="ecu.ExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the ExclusiveArea this execution time is provided for. mmt.qualifiedName="ExecutionTime.exclusiveArea";pureMM.maxOccurs="1";pureMM.minOccurs="0" If this dependency is specified, the execution time of the library code is included in the execution time data for the runnable. mmt.qualifiedName="ExecutionTime.externalLibrary";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Provides information on the HardwareConfiguration used to specify this ExecutionTime. mmt.qualifiedName="hardwareConfiguration.ExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Provides information on the MemorySectionLocation which is involved in the ExecutionTime description. mmt.qualifiedName="memorySectionLocation.ExecutionTime";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to the runnable this execution time is provided for. mmt.qualifiedName="ExecutionTime.runnable";pureMM.maxOccurs="1";pureMM.minOccurs="0" Provides information on the detailed SoftwareContext used to provide the ExecutionTime description. mmt.qualifiedName="softwareContext.ExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Base class for several means how to describe the ExecutionTime of software. The required context information is provided through this class. mmt.qualifiedName="ExecutionTime" atpObject FlexRay specific attributes to the CommunicationConnector mmt.qualifiedName="FlexRayCommunicationConnector" atpObject Referenced channel used by the node to send a wakeup pattern. (pWakeupChannel) mmt.qualifiedName="FlexRayCommunicationConnector.wakeUpChannel";pureMM.maxOccurs="1";pureMM.minOccurs="1" FlexRay specific attributes to the CommunicationConnector mmt.qualifiedName="FlexRayCommunicationConnector" atpObject A connection within a channel identifies the sender and the receiver of this particular communication. The FlexRayTp module routes a Pdu through this connection. mmt.qualifiedName="FlexRayTpConnection" atpObject Reference to the IPdu that is segmented by the Transport Protocol. The source address of the transmitted NPdu is determined by the configured source CommunicationConnector. The target address of the transmitted NPdu is determined by the configured target CommunicationConnector. To support the low-level routing of NPdu's the NPdu is a specialization of an IPdu. More details can be found in the NPdu class description. Nevertheless the FlexRayTpConnection must not reference a NPdu with this tpSdu reference. mmt.qualifiedName="FlexRayTpConnection.directTpSdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Flow Control NPdu. The Flow Control network protocol data unit (FC N_PDU) is identified by the Flow Control protocol control information (FC N_PCI). The Flow Control network protocol data unit (FC N_PDU) instructs a sending network entity to start, stop or resume transmission of CF N_PDUs. The Flow Control network protocol data unit shall be sent by the receiving network layer entity to the sending network layer entity, when ready to receive more data, after correct reception of: a) First Frame network protocol data unit (FF N_PDU) b) the last Consecutive Frame network protocol data unit (CF N_PDU) of a block of Consecutive Frames (CF N_PDU) if further Consecutive Frame network protocol data unit (CF N_PDU) need(s) to be sent. mmt.qualifiedName="FlexRayTpConnection.flowControlPdu";pureMM.maxOccurs="1";pureMM.minOccurs="0" TP address for 1:n connections. mmt.qualifiedName="FlexRayTpConnection.multicast";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the IPdu that is segmented by the Transport Protocol. If support of both sending and receiving is used, this association references the IPdu used for the additional second direction. The source address of the transmitted NPdu is determined by the configured target CommunicationConnector. The target address of the transmitted NPdu is determined by the configured source CommunicationConnector. To support the low-level routing of NPdu's the NPdu is a specialization of an IPdu. More details can be found in the NPdu class description. Nevertheless the FlexRayTpConnection must not reference a NPdu with this tpSdu reference. mmt.qualifiedName="FlexRayTpConnection.reversedTpSdu";pureMM.maxOccurs="1";pureMM.minOccurs="0" The source of the TP connection. mmt.qualifiedName="FlexRayTpConnection.source";pureMM.maxOccurs="1";pureMM.minOccurs="1" The target of the TP connection. mmt.qualifiedName="FlexRayTpConnection.target";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Reference to an NPdu (Single Frame, First Frame or Consecutive Frame). The Single Frame network protocol data unit (SF N_PDU) shall be sent out by the sending network entity and can be received by one or multiple receiving network entities. The Single Frame (SF N_PDU) shall be sent out to transfer a service data unit that can be transferred via a single service request to the data link layer. This network protocol data unit shall be sent to transfer unsegmented messages. The First Frame network protocol data unit (FF N_PDU) identifies the first network protocol data unit (N_PDU) of a segmented message transmitted by a network sending entity and received by a receiving network entity. The Consecutive Frame network protocol data unit (CF N_PDU) transfers segments (N_Data) of the service data unit message data (&lt;MessageData&gt;). All network protocol data units (N_PDUs) transmitted by the sending entity after the First Frame network protocol data unit (FF N_PDU) shall be encoded as Consecutive Frames network protocol data units (CF N_PDUs). mmt.qualifiedName="FlexRayTpConnection.transmitPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A connection within a channel identifies the sender and the receiver of this particular communication. The FlexRayTp module routes a Pdu through this connection. mmt.qualifiedName="FlexRayTpConnection" atpObject FlexRay specific attributes to the physicalCluster mmt.qualifiedName="FlexrayCluster" atpObject The offset of the action point in networks mmt.qualifiedName="FlexrayCluster.actionPointOffset";pureMM.maxOccurs="1";pureMM.minOccurs="1" Nominal bit time (= 1 / fx:SPEED). gdBit = cSamplesPerBit * gdSampleClockPeriod. Unit: seconds (gdBit) mmt.qualifiedName="FlexrayCluster.bit";pureMM.maxOccurs="1";pureMM.minOccurs="1" Bus Guardian Inter Slot Gap (ISG) part that follows a guarded schedule element. Unit macroticks mmt.qualifiedName="FlexrayCluster.busGuardianEnablePart";pureMM.maxOccurs="1";pureMM.minOccurs="0" Upper limit of the Collision Avoidance Symbol (CAS) acceptance window. Unit:bitDuration mmt.qualifiedName="FlexrayCluster.casRxLowMax";pureMM.maxOccurs="1";pureMM.minOccurs="1" Lower limit of the Collision Avoidance Symbol (CAS) acceptance window. Unit:bitDuration mmt.qualifiedName="FlexrayCluster.casRxLowMin";pureMM.maxOccurs="1";pureMM.minOccurs="1" The maximum number of times that a node in this cluster is permitted to attempt to start the cluster by initiating schedule synchronization mmt.qualifiedName="FlexrayCluster.coldStartAttempts";pureMM.maxOccurs="1";pureMM.minOccurs="1" Length of the cycle. Unit: seconds mmt.qualifiedName="FlexrayCluster.cycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum cycle counter value in a given cluster. Remark: Set to 63 for FlexRay Protocol 2.1 Rev. A compliance. mmt.qualifiedName="FlexrayCluster.cycleCountMax";pureMM.maxOccurs="1";pureMM.minOccurs="0" The duration of the dynamic slot idle phase in minislots. mmt.qualifiedName="FlexrayCluster.dynamicSlotIdlePhase";pureMM.maxOccurs="1";pureMM.minOccurs="1" Duration for which the bitstrobing is paused after transmission [gdBit]. mmt.qualifiedName="FlexrayCluster.ignoreAfterTx";pureMM.maxOccurs="1";pureMM.minOccurs="0" Upper limit for the start up and wake up listen timeout in the presence of noise. Expressed as a multiple of the cluster constant pdListenTimeout. Unit microticks mmt.qualifiedName="FlexrayCluster.listenNoise";pureMM.maxOccurs="1";pureMM.minOccurs="1" number of macroticks which describe the distance between the static slot boundary and the closed macrotick boundary of the secondary time reference point using the initial configured macrotick length mmt.qualifiedName="FlexrayCluster.macroInitialOffset";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of macroticks in a communication cycle mmt.qualifiedName="FlexrayCluster.macroPerCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Duration of the cluster wide nominal macrotick, expressed in seconds mmt.qualifiedName="FlexrayCluster.macrotickDuration";pureMM.maxOccurs="1";pureMM.minOccurs="1" The maximum error that a node may have after initialization. Unit: seconds mmt.qualifiedName="FlexrayCluster.maxInitialisationError";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum propagation delay of a Cluster (in seconds). mmt.qualifiedName="FlexrayCluster.maxPropagationDelay";pureMM.maxOccurs="1";pureMM.minOccurs="1" Threshold concerning vClockCorrectionFailedCounter. Defines the number of consecutive even/odd Cycle pairs with missing clock correction terms that will cause the protocol to transition from the POC:normal active or POC:normal passive state into the POC:halt state. mmt.qualifiedName="FlexrayCluster.maxWithoutClockCorrectionFatal";pureMM.maxOccurs="1";pureMM.minOccurs="1" Threshold concerning vClockCorrectionFailedCounter. Defines the number of consecutive even/odd Cycle pairs with missing clock correction terms that will cause the protocol to transition from the POC:normal active state to the POC:normal passive state. mmt.qualifiedName="FlexrayCluster.maxWithoutClockCorrectionPassive";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum propagation delay of a Cluster (in seconds). mmt.qualifiedName="FlexrayCluster.minPropagationDelay";pureMM.maxOccurs="1";pureMM.minOccurs="1" The Offset of the action point within a minislot. Unit: macroticks mmt.qualifiedName="FlexrayCluster.minislotActionPointOffset";pureMM.maxOccurs="1";pureMM.minOccurs="1" The duration of a minislot (dynamic segment). Unit: macroticks. mmt.qualifiedName="FlexrayCluster.minislotDuration";pureMM.maxOccurs="1";pureMM.minOccurs="1" The duration of the network idle time in macroticks mmt.qualifiedName="FlexrayCluster.networkIdleTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Length of the Network Management vector on a cluster. Unit: Bytes mmt.qualifiedName="FlexrayCluster.networkManagementVectorLength";pureMM.maxOccurs="1";pureMM.minOccurs="0" Number of FlexRay Communication Cycles needed to transmit the Nm Data PDUs of all FlexRay Nm Ecus of this FlexRayNmCluster. mmt.qualifiedName="FlexrayCluster.nmDataCycle";pureMM.maxOccurs="1";pureMM.minOccurs="0" Numbers of repetitions in the ready sleep state before NM switches to bus sleep mode. On a value of "1", the NM-State Machine will leave the Ready Sleep State after one NM Repetition Cycle with no "keep awake" votes. mmt.qualifiedName="FlexrayCluster.nmReadySleepCount";pureMM.maxOccurs="1";pureMM.minOccurs="0" Timeout for Remote Sleep Indication in seconds. It defines the time how long it shall take to recognize that all other nodes are ready to sleep. mmt.qualifiedName="FlexrayCluster.nmRemoteSleepIndicationTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Timeout for Repeat Message State in seconds. Defines the time how long the NM shall stay in the Repeat Message State. mmt.qualifiedName="FlexrayCluster.nmRepeatMessageTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Number of FlexRay Communication Cycles used to repeat the transmission of the Nm vote PDUs of all FlexRay NmEcus of this FlexRayNmCluster. This value must be an integral multiple of nmVotingCycle. mmt.qualifiedName="FlexrayCluster.nmRepetitionCycle";pureMM.maxOccurs="1";pureMM.minOccurs="0" Number of FlexRay CommunicationCycles needed to transmit the Nm vote of Pdus of all FlexRay NmEcus of this FlexRayNmCluster. mmt.qualifiedName="FlexrayCluster.nmVotingCycle";pureMM.maxOccurs="1";pureMM.minOccurs="0" Total number of cycles until a temporal transmission pattern is repeated. The CycleCounter of an AbsolutelyScheduledTiming is evaluated against this parameter. mmt.qualifiedName="FlexrayCluster.numberOfCycles";pureMM.maxOccurs="1";pureMM.minOccurs="1" number of Minislots in the dynamic segment. mmt.qualifiedName="FlexrayCluster.numberOfMinislots";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of static slots in the static segment. mmt.qualifiedName="FlexrayCluster.numberOfStaticSlots";pureMM.maxOccurs="1";pureMM.minOccurs="1" Cluster global magnitude of the maximum permissible offset correction value Unit: seconds (gOffsetCorrectionMax) mmt.qualifiedName="FlexrayCluster.offsetCorrectionMax";pureMM.maxOccurs="1";pureMM.minOccurs="0" Start of the offset correction phase within the Network Idle Time (NIT), expressed as the number of macroticks from the start of cycle. Unit: macroticks mmt.qualifiedName="FlexrayCluster.offsetCorrectionStart";pureMM.maxOccurs="1";pureMM.minOccurs="1" Globally configured payload length of a static frame. Unit: 16-bit WORDS. mmt.qualifiedName="FlexrayCluster.payloadLengthStatic";pureMM.maxOccurs="1";pureMM.minOccurs="1" Sample clock period. Unit: seconds mmt.qualifiedName="FlexrayCluster.sampleClockPeriod";pureMM.maxOccurs="1";pureMM.minOccurs="0" The duration of a slot in the static segment. Unit: macroticks mmt.qualifiedName="FlexrayCluster.staticSlotDuration";pureMM.maxOccurs="1";pureMM.minOccurs="1" The duration of the symbol window. Unit: macroticks mmt.qualifiedName="FlexrayCluster.symbolWindow";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of macroticks the action point offset is from the beginning of the symbol window [Macroticks]. mmt.qualifiedName="FlexrayCluster.symbolWindowActionPointOffset";pureMM.maxOccurs="1";pureMM.minOccurs="0" Maximum number of distinct syncframe identifiers present in a given cluster. This parameter maps to FlexRay Protocol 2.1 Rev. A parameter gSyncNodeMax. mmt.qualifiedName="FlexrayCluster.syncFrameIDCountMax";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of bits in the Transmission Start Sequence [gdBits]. mmt.qualifiedName="FlexrayCluster.transmissionStartSequenceDuration";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of bits used by the node to test the duration of the 'idle' or HIGH phase of a received wakeup. Unit:bitDuration Remarks: This parameter maps to FlexRay Protocol 2.1 Rev. A parameter gdWakeupSymbolRxIdle. mmt.qualifiedName="FlexrayCluster.wakeupRxIdle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of bits used by the node to test the duration of the LOW phase of a received wakeup. Unit:bitDuration Remarks: This parameter maps to FlexRay Protocol 2.1 Rev. A parameter gdWakeupSymbolRxLow. mmt.qualifiedName="FlexrayCluster.wakeupRxLow";pureMM.maxOccurs="1";pureMM.minOccurs="1" The size of the window used to detect wakeups [gdBit]. Remarks: This parameter maps to FlexRay Protocol 2.1 Rev. A parameter gdWakeupSymbolRxWindow. mmt.qualifiedName="FlexrayCluster.wakeupRxWindow";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of bits used by the node to transmit the LOW phase of awakeup symbol and the HIGH and LOW phases of a WUDOP. Unit:bitDuration. Remarks: This parameter maps to FlexRay Protocol 2.1 Rev. A parameter gdWakeupSymbolTxLow. mmt.qualifiedName="FlexrayCluster.wakeupTxActive";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of bits used by the node to transmit the 'idle' part of a wakeup symbol. Unit: gDbit. Remarks: This parameter maps to FlexRay Protocol 2.1 Rev. A parameter gdWakeupSymbolTxIdle. mmt.qualifiedName="FlexrayCluster.wakeupTxIdle";pureMM.maxOccurs="1";pureMM.minOccurs="1" FlexRay specific attributes to the physicalCluster mmt.qualifiedName="FlexrayCluster" atpObject FlexRay bus specific communication port attributes. mmt.qualifiedName="FlexrayCommunicationController" atpObject Expanded range of measured clock deviation allowed for startup frames during integration. Unit:microtick mmt.qualifiedName="FlexrayCommunicationController.acceptedStartupRange";pureMM.maxOccurs="1";pureMM.minOccurs="1" Boolean flag that controls the transition to the POC:halt state due to a clock synchronization errors. If set to true, the Communication Controller is allowed to transition to POC:halt. If set to false, the Communication Controller will not transition to the POC:halt state but will enter or remain in the normal POC (passive State). mmt.qualifiedName="FlexrayCommunicationController.allowHaltDueToClock";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of consecutive even/odd cycle pairs that must have valid clock correction terms before the Communication Controller will be allowed to transition from the POC:normal passive state to POC:normal active state. If set to 0, the Communication Controller is not allowed to transition from POC:norm mmt.qualifiedName="FlexrayCommunicationController.allowPassiveToActive";pureMM.maxOccurs="1";pureMM.minOccurs="1" The cluster drift damping factor used in clock synchronization rate correction in microticks mmt.qualifiedName="FlexrayCommunicationController.clusterDriftDamping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Value used by the receiver to calculate the difference between primary time reference point and secondary time reference point. Unit: Microticks (pDecodingCorrection) mmt.qualifiedName="FlexrayCommunicationController.decodingCorrection";pureMM.maxOccurs="1";pureMM.minOccurs="1" Value used to compensate for reception delays on channel A Unit: Microticks This optional parameter shall only be filled out if channel A is used. mmt.qualifiedName="FlexrayCommunicationController.delayCompensationA";pureMM.maxOccurs="1";pureMM.minOccurs="0" Value used to compensate for reception delays on channel B. Unit: Microticks This optional parameter shall only be filled out if channel B is used. mmt.qualifiedName="FlexrayCommunicationController.delayCompensationB";pureMM.maxOccurs="1";pureMM.minOccurs="0" Boolean flag that configures the Bus Guardian Schedule Monitoring Service to expect transmissions within the dynamic segment. mmt.qualifiedName="FlexrayCommunicationController.dynamicSegmentEnable";pureMM.maxOccurs="1";pureMM.minOccurs="1" Fixed amount added or subtracted to the calculated offset correction term to facilitate external offset correction, expressed in node-local microticks. mmt.qualifiedName="FlexrayCommunicationController.externOffsetCorrection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Fixed amount added or subtracted to the calculated rate correction term to facilitate external rate correction, expressed in node-local microticks. mmt.qualifiedName="FlexrayCommunicationController.externRateCorrection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Flag indicating whether the node is externally synchronized (operating as Time Gateway Sink in an TT-E Time Triggered External Sync cluster) or locally synchronized. mmt.qualifiedName="FlexrayCommunicationController.externalSync";pureMM.maxOccurs="1";pureMM.minOccurs="0" Flag indicating whether a Time Gateway Sink node will switch to local clock operation when synchronization with the Time Gateway Source node is lost (pFallBackInternal = true) or will instead go to POC:ready (pFallBackInternal = false). mmt.qualifiedName="FlexrayCommunicationController.fallBackInternal";pureMM.maxOccurs="1";pureMM.minOccurs="0" One First In First Out (FIFO) queued receive structure, defining the admittance criteria to the FIFO. mmt.qualifiedName="flexrayFifo.FlexrayCommunicationController";pureMM.maxOccurs="-1";pureMM.minOccurs="0" ID of the slot used to transmit the startup frame, sync frame, or designated single slot frame. mmt.qualifiedName="FlexrayCommunicationController.keySlotID";pureMM.maxOccurs="1";pureMM.minOccurs="1" Flag indicating whether or not the node shall enter key slot only mode following startup. mmt.qualifiedName="FlexrayCommunicationController.keySlotOnlyEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="1" Flag indicating whether the Key Slot is used to transmit a startup frame. mmt.qualifiedName="FlexrayCommunicationController.keySlotUsedForStartUp";pureMM.maxOccurs="1";pureMM.minOccurs="1" Flag indicating whether the Key Slot is used to transmit a sync frame. mmt.qualifiedName="FlexrayCommunicationController.keySlotUsedForSync";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of the last minislot in which a transmission can start in the dynamic segment for the respective node mmt.qualifiedName="FlexrayCommunicationController.latestTX";pureMM.maxOccurs="1";pureMM.minOccurs="1" Upper limit for the start up listen timeout and wake up listen timeout. Unit: Microticks mmt.qualifiedName="FlexrayCommunicationController.listenTimeout";pureMM.maxOccurs="1";pureMM.minOccurs="1" Integer number of macroticks between the static slot boundary and the closest macrotick boundary of the secondary time reference point based on the nominal macrotick duration. (pMacroInitialOffset) This optional parameter shall only be filled out if channel A is used. mmt.qualifiedName="FlexrayCommunicationController.macroInitialOffsetA";pureMM.maxOccurs="1";pureMM.minOccurs="0" Integer number of macroticks between the static slot boundary and the closest macrotick boundary of the secondary time reference point based on the nominal macrotick duration. (pMacroInitialOffset) This optional parameter shall only be filled out if channel B is used. mmt.qualifiedName="FlexrayCommunicationController.macroInitialOffsetB";pureMM.maxOccurs="1";pureMM.minOccurs="0" Maximum payload length for the dynamic channel of a frame in 16 bit WORDS. mmt.qualifiedName="FlexrayCommunicationController.maximumDynamicPayloadLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of microticks between the closest macrotick boundary described by gMacroInitialOffset and the secondary time reference point. The parameter depends on pDelayCompensationA and therefore it has to be set independently for each channel. This optional parameter shall only be filled out if channel A is used. mmt.qualifiedName="FlexrayCommunicationController.microInitialOffsetA";pureMM.maxOccurs="1";pureMM.minOccurs="0" Number of microticks between the closest macrotick boundary described by gMacroInitialOffset and the secondary time reference point. The parameter depends on pDelayCompensationB and therefore it has to be set independently for each channel. This optional parameter shall only be filled out if channel B is used. mmt.qualifiedName="FlexrayCommunicationController.microInitialOffsetB";pureMM.maxOccurs="1";pureMM.minOccurs="0" The nominal number of microticks in a communication cycle mmt.qualifiedName="FlexrayCommunicationController.microPerCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of microticks per nominal macrotick that all implementations must support. mmt.qualifiedName="FlexrayCommunicationController.microPerMacroNom";pureMM.maxOccurs="1";pureMM.minOccurs="1" Duration of a microtick. This attribute can be derived from samplePerMicrotick and gdSampleClockPeriod. Unit: seconds mmt.qualifiedName="FlexrayCommunicationController.microtickDuration";pureMM.maxOccurs="1";pureMM.minOccurs="0" Enables control bit vector support. mmt.qualifiedName="FlexrayCommunicationController.nmControlBitVectorEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" Enables the Request Repeat Message Request support. Only valid if nmNodeIdEnabled is set to true. mmt.qualifiedName="FlexrayCommunicationController.nmNodeDetectionEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" Switch for enabling SourceNodeIdentifier support. mmt.qualifiedName="FlexrayCommunicationController.nmSourceNodeIdentifierEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" Switch for enabling user data support. mmt.qualifiedName="FlexrayCommunicationController.nmUserDataEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" Flag indicating when the update of the Network Management Vector in the CHI shall take place. If set to false, the update shall take place after the NIT. If set to true, the update shall take place after the end of the static segment. mmt.qualifiedName="FlexrayCommunicationController.nmVectorEarlyUpdate";pureMM.maxOccurs="1";pureMM.minOccurs="0" Magnitude of the maximum permissible offset correction value. Unit:microtick (pOffsetCorrectionOut) mmt.qualifiedName="FlexrayCommunicationController.offsetCorrectionOut";pureMM.maxOccurs="1";pureMM.minOccurs="1" Magnitude of the maximum permissible rate correction value and the maximum drift offset between two nodes operating with unsynchronized clocks for one communication cycle. Unit:Microticks (pRateCorrectionOut) Remarks: This parameter maps to FlexRay Protocol 2.1 Rev. A parameter pdMaxDrift. mmt.qualifiedName="FlexrayCommunicationController.rateCorrectionOut";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of samples per microtick mmt.qualifiedName="FlexrayCommunicationController.samplesPerMicrotick";pureMM.maxOccurs="1";pureMM.minOccurs="1" ID of the second Key slot, in which a second startup frame shall be sent in TT-L Time Triggered Local Master Sync or TT-E Time Triggered External Sync mode. If this parameter is set to zero the node does not have a second key slot. mmt.qualifiedName="FlexrayCommunicationController.secondKeySlotId";pureMM.maxOccurs="1";pureMM.minOccurs="0" Indicates that the node is a startup node (startup frame configured; connected to gChannels) mmt.qualifiedName="FlexrayCommunicationController.startUpNode";pureMM.maxOccurs="1";pureMM.minOccurs="1" The number of the static slot in which a sync frame shall be sent, if a sync frame shall be sent mmt.qualifiedName="FlexrayCommunicationController.syncSlot";pureMM.maxOccurs="1";pureMM.minOccurs="0" Flag indicating whether node operates as a startup node in a TT-E Time Triggered External Sync or TT-L Time Triggered Local Master Sync cluster. mmt.qualifiedName="FlexrayCommunicationController.twoKeySlotMode";pureMM.maxOccurs="1";pureMM.minOccurs="0" Number of repetitions of the Tx-wakeup symbol to be sent during the CC_WakeupSend state of this Node in the cluster mmt.qualifiedName="FlexrayCommunicationController.wakeUpPattern";pureMM.maxOccurs="1";pureMM.minOccurs="1" FlexRay bus specific communication port attributes. mmt.qualifiedName="FlexrayCommunicationController" atpObject One First In First Out (FIFO) queued receive structure, defining the admittance criteria to the FIFO, and mandating the ability to admit messages into the FIFO based on Message Id filtering criteria. mmt.qualifiedName="FlexrayFifoConfiguration" atpObject Boolean configuration which determines whether or not frames received in the dynamic segment that don't contain a message ID will be admitted into the FIFO. mmt.qualifiedName="FlexrayFifoConfiguration.admitWithoutMessageId";pureMM.maxOccurs="1";pureMM.minOccurs="1" FIFO cycle counter acceptance criteria. mmt.qualifiedName="FlexrayFifoConfiguration.baseCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Fifo channel admittance criteria. mmt.qualifiedName="FlexrayFifoConfiguration.channel";pureMM.maxOccurs="2";pureMM.minOccurs="0" FIFO cycle counter acceptance criteria. mmt.qualifiedName="FlexrayFifoConfiguration.cycleRepetition";pureMM.maxOccurs="1";pureMM.minOccurs="1" Fifo Depth. mmt.qualifiedName="FlexrayFifoConfiguration.fifoDepth";pureMM.maxOccurs="1";pureMM.minOccurs="1" FIFO Frame Id range acceptance criteria. mmt.qualifiedName="fifoRange.FlexrayFifoConfiguration";pureMM.maxOccurs="-1";pureMM.minOccurs="2" FIFO message identifier acceptance criteria (Mask filter). mmt.qualifiedName="FlexrayFifoConfiguration.msgIdMask";pureMM.maxOccurs="1";pureMM.minOccurs="1" FIFO message identifier acceptance criteria (Match filter). mmt.qualifiedName="FlexrayFifoConfiguration.msgIdMatch";pureMM.maxOccurs="1";pureMM.minOccurs="1" One First In First Out (FIFO) queued receive structure, defining the admittance criteria to the FIFO, and mandating the ability to admit messages into the FIFO based on Message Id filtering criteria. mmt.qualifiedName="FlexrayFifoConfiguration" atpObject FIFO Frame Id range acceptance criteria. mmt.qualifiedName="FlexrayFifoRange" atpObject Max Range. mmt.qualifiedName="FlexrayFifoRange.rangeMax";pureMM.maxOccurs="1";pureMM.minOccurs="1" Min Range. mmt.qualifiedName="FlexrayFifoRange.rangeMin";pureMM.maxOccurs="1";pureMM.minOccurs="1" FIFO Frame Id range acceptance criteria. mmt.qualifiedName="FlexrayFifoRange" atpObject FlexRay specific attributes to the FrameTriggering mmt.qualifiedName="FlexrayFrameTriggering" atpObject Specification of a sending behaviour where the exact time for the frames transmission is guaranteed. mmt.qualifiedName="absolutelyScheduledTiming.FlexrayFrameTriggering";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Switching the Payload Preamble bit. mmt.qualifiedName="FlexrayFrameTriggering.payloadPreambleIndicator";pureMM.maxOccurs="1";pureMM.minOccurs="1" FlexRay specific attributes to the FrameTriggering mmt.qualifiedName="FlexrayFrameTriggering" atpObject A connection identifies the sender and the receiver of this particular communication. The FlexRayIsoTp module routes a Pdu through this connection. In a System Description the references to the PduPools are mandatory. In an ECU Extract these references can be optional: On unicast connections these references are always mandatory. On multicast the txPduPool is mandatory on the sender side. The rxPduPool is mandatory on the receiver side. On Gateway ECUs both references are mandatory. mmt.qualifiedName="FlexrayIsoTpConnection" atpObject Specifies whether the connection requires a bandwidth limitation or not. mmt.qualifiedName="FlexrayIsoTpConnection.bandwidthLimitation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the IPdu that is segmented by the Transport Protocol. To support the low-level routing of NPdu's the NPdu is a specialization of an IPdu. More details can be found in the NPdu class description. Nevertheless the FlexrayIsoTpConnection must not reference a NPdu with this tpSdu reference. mmt.qualifiedName="FlexrayIsoTpConnection.directTpSdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" TP address for 1:n connections. mmt.qualifiedName="FlexrayIsoTpConnection.multicast";pureMM.maxOccurs="1";pureMM.minOccurs="0" The target of the TP connection. mmt.qualifiedName="FlexrayIsoTpConnection.receiver";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Reference to the IPdu that is segmented by the Transport Protocol. If support of both sending and receiving is used, this association references the IPdu used for the additional second direction. To support the low-level routing of NPdu's the NPdu is a specialization of an IPdu. More details can be found in the NPdu class description. Nevertheless the FlexrayIsoTpConnection must not reference a NPdu with this tpSdu reference. mmt.qualifiedName="FlexrayIsoTpConnection.reversedTpSdu";pureMM.maxOccurs="1";pureMM.minOccurs="0" A connection has a reference to a set of NPdus (FrTpRxPduPool) which are defined for receiving data via this particular connection. mmt.qualifiedName="FlexrayIsoTpConnection.rxPduPool";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the connection control. mmt.qualifiedName="FlexrayIsoTpConnection.tpConnectionControl";pureMM.maxOccurs="1";pureMM.minOccurs="1" The source of the TP connection. mmt.qualifiedName="FlexrayIsoTpConnection.transmitter";pureMM.maxOccurs="1";pureMM.minOccurs="1" A connection has a reference to a set of NPdus (FrTpTxPduPool) which are defined for sending data via this particular connection. mmt.qualifiedName="FlexrayIsoTpConnection.txPduPool";pureMM.maxOccurs="1";pureMM.minOccurs="0" A connection identifies the sender and the receiver of this particular communication. The FlexRayIsoTp module routes a Pdu through this connection. In a System Description the references to the PduPools are mandatory. In an ECU Extract these references can be optional: On unicast connections these references are always mandatory. On multicast the txPduPool is mandatory on the sender side. The rxPduPool is mandatory on the receiver side. On Gateway ECUs both references are mandatory. mmt.qualifiedName="FlexrayIsoTpConnection" atpObject Configuration parameters to control a FlexRay TP connection. mmt.qualifiedName="FlexrayIsoTpConnectionControl" atpObject This parameter defines the type of acknowledgement which is used for the specific channel. For FlexrayIsoTp only noAck and ackWithRt shall be used. mmt.qualifiedName="FlexrayIsoTpConnectionControl.ackType";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to send a frame when a TIMEOUT AR occurs (depending on whether retry is configured). mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxAr";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to send a frame when a TIMEOUT AS occurs (depending on whether retry is configured) mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxAs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter is only relevant when having retry activated. It limits the maximal buffer size the FrTp can choose in order to limit the amount of Tx buffer that will be requested at the sender side in a segmented transfer. mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxBufferSize";pureMM.maxOccurs="1";pureMM.minOccurs="0" This attribute defines the maximum number of FlowControl N-PDUs with FlowState "WAIT". mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxFcWait";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to send a frame when the FrIf returns an error mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxFrIf";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter limits the number of N-Pdus the sender is allowed to transmit within a FlexRay cycle. mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxNumberOfNpduPerCycle";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of retries (if retry is configured for the particular channel). mmt.qualifiedName="FlexrayIsoTpConnectionControl.maxRetries";pureMM.maxOccurs="1";pureMM.minOccurs="0" Exponent to calculate the minimum number of "Separation Cycles" the sender has to wait for the next transmission of an FrTp N-Pdu. mmt.qualifiedName="FlexrayIsoTpConnectionControl.separationCycleExponent";pureMM.maxOccurs="1";pureMM.minOccurs="0" Time (in seconds) until transmission of the next FlowControl N-PDU. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeBr";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the time of waiting for the next try to get a Tx or Rx buffer. This parameter is equivalent to the temporal distance between two FC.WT N-Pdus in case the buffer request returns busy. Specified in seconds. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeBuffer";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the time of waiting for the next try to send. Specified in seconds. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeFrIf";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter states the timeout between the PDU transmit request of the Transport Layer to the FlexRay Interface and the corresponding confirmation of the FlexRay Interface on the receiver side (for FC or AF). Specified in seconds. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeoutAr";pureMM.maxOccurs="1";pureMM.minOccurs="0" This attribute states the timeout between the PDU transmit request for the first PDU of the group used in the current connection of the Transport Layer to the FlexRay Interface and the corresponding confirmation of the FlexRay Interface (when having sent the last PDU of the group used in this connection) on the sender side (SF-x, FF-x, CF or FC (in case of Transmit Cancellation)). Specified in seconds. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeoutAs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the timeout in seconds for waiting for an FC or AF on the sender side in a 1:1 connection. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeoutBs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the timeout value in seconds for waiting for a CF or FF-x (in case of retry) after receiving the last CF or after sending an FC or AF on the receiver side. Specified in seconds. mmt.qualifiedName="FlexrayIsoTpConnectionControl.timeoutCr";pureMM.maxOccurs="1";pureMM.minOccurs="0" Configuration parameters to control a FlexRay TP connection. mmt.qualifiedName="FlexrayIsoTpConnectionControl" atpObject ECU specific TP configuration parameters. Each TpEcu element has a reference to exactly one ECUInstance in the topology. mmt.qualifiedName="FlexrayIsoTpEcu" atpObject The period between successive calls to the Main Function of the AUTOSAR TP. Specified in seconds. mmt.qualifiedName="FlexrayIsoTpEcu.cycleTimeMainFunction";pureMM.maxOccurs="1";pureMM.minOccurs="0" Connection to the ECUInstance in the Topology. mmt.qualifiedName="FlexrayIsoTpEcu.ecuInstance";pureMM.maxOccurs="1";pureMM.minOccurs="1" The full duplex mechanisms is enabled if this attribute is set to true. Otherwise half duplex is enabled. mmt.qualifiedName="FlexrayIsoTpEcu.fullDuplexEnabled";pureMM.maxOccurs="1";pureMM.minOccurs="1" ECU specific TP configuration parameters. Each TpEcu element has a reference to exactly one ECUInstance in the topology. mmt.qualifiedName="FlexrayIsoTpEcu" atpObject TP Node (Sender or Receiver) provides the TP Address and the connection to the Topology description. mmt.qualifiedName="FlexrayIsoTpNode" atpObject FlexrayTpPduPool is a set of N-PDUs which are defined for FrTp sending or receiving purpose. mmt.qualifiedName="FlexrayIsoTpPduPool" atpObject Reference to NPdus that are part of the PduPool. mmt.qualifiedName="FlexrayIsoTpPduPool.nPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="1" FlexrayTpPduPool is a set of N-PDUs which are defined for FrTp sending or receiving purpose. mmt.qualifiedName="FlexrayIsoTpPduPool" atpObject FlexRay specific attributes to the physicalChannel mmt.qualifiedName="FlexrayPhysicalChannel" atpObject Name of the channel (Channel A or Channel B). mmt.qualifiedName="FlexrayPhysicalChannel.channelName";pureMM.maxOccurs="1";pureMM.minOccurs="1" Optional configuration of FlexRay TP Pdu Pools (shall only be used for Flexray ISO TP configuration). mmt.qualifiedName="pduPool.FlexrayPhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Optional configuration of FlexRay ISO TP Connection Controls (shall only be used for Flexray ISO TP configuration). mmt.qualifiedName="tpConnectionControl.FlexrayPhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Optional collection of TP Ecus with ECU specific Flexray ISO Tp configuration parameters. mmt.qualifiedName="tpEcus.FlexrayPhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" FlexRay specific attributes to the physicalChannel mmt.qualifiedName="FlexrayPhysicalChannel" atpObject A channel is a group of connections sharing several properties. The FlexRay Transport Layer supports several channels. These channels can work concurrently, thus each of them requires its own state machine and management data structures and its own PDU-IDs. mmt.qualifiedName="FlexrayTpChannel" atpObject Type of Acknowledgement. mmt.qualifiedName="FlexrayTpChannel.ackType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Adressing Type of this connection: true: Two Bytes false: One Byte mmt.qualifiedName="FlexrayTpChannel.extendedAddressing";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Flow Control NPdu. The Flow Control network protocol data unit (FC N_PDU) is identified by the Flow Control protocol control information (FC N_PCI). The Flow Control network protocol data unit (FC N_PDU) instructs a sending network entity to start, stop or resume transmission of CF N_PDUs. The Flow Control network protocol data unit shall be sent by the receiving network layer entity to the sending network layer entity, when ready to receive more data, after correct reception of: mmt.qualifiedName="FlexrayTpChannel.flowControlPdu";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to send a frame when a TIMEOUT AR occurs (depending on whether retry is configured). mmt.qualifiedName="FlexrayTpChannel.maxAr";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to send a frame when a TIMEOUT AS occurs (depending on whether retry is configured). mmt.qualifiedName="FlexrayTpChannel.maxAs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter is only relevant when having retry activated. It limits the maximal block size the FrTp can choose in order to limit the amount of Tx buffer that will be requested at the sender side in a segmented transfer. mmt.qualifiedName="FlexrayTpChannel.maxBs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to get a buffer (Transmit / Receive), depending of the return value of PduR_FrTpProvideTxBuffer / PduR_FrTpProvideRxBuffer and on whether retry is configured. mmt.qualifiedName="FlexrayTpChannel.maxBufferRequest";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of trying to send a frame when the FrIf returns an error. mmt.qualifiedName="FlexrayTpChannel.maxFrIf";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the maximum number of retries (if retry is configured for the particular channel). mmt.qualifiedName="FlexrayTpChannel.maxRetries";pureMM.maxOccurs="1";pureMM.minOccurs="0" This specifies the maximum message length for the particular channel. mmt.qualifiedName="FlexrayTpChannel.maximumMessageLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute defines the minimum amount of time (separation Time) between two succeeding CFs. Specified in seconds. mmt.qualifiedName="FlexrayTpChannel.minimumSeparationTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute defines whether segmentation within a 1:n connection is allowed or not. mmt.qualifiedName="FlexrayTpChannel.multicastSegmentation";pureMM.maxOccurs="1";pureMM.minOccurs="1" A FlexRayTpChannel contains a pool of NPdus. mmt.qualifiedName="pduPool.FlexrayTpChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This parameter defines the time in seconds between receiving the last CF of a block or an FF-x (or SF-x) and sending out an FC or AF. mmt.qualifiedName="FlexrayTpChannel.timeBr";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the time in seconds of waiting for the next try (if retry is activated) to get a Tx or Rx buffer. mmt.qualifiedName="FlexrayTpChannel.timeBuffer";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the time in seconds between the sending of two consecutive frames or between a consecutive frame and a flow control (for Transmit Cancellation) or between reception of an flow control or Acknowledgement Frame and sending of the next consecutive frame or a flow control (for Transmit Cancellation). mmt.qualifiedName="FlexrayTpChannel.timeCs";pureMM.maxOccurs="1";pureMM.minOccurs="1" This parameter defines the time in seconds of waiting for the next try (if retry is activated) to send via FrIf_Transmit. Specified in seconds. mmt.qualifiedName="FlexrayTpChannel.timeFrIf";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter states the timeout in seconds between the PDU transmit request of the Transport Layer to the FlexRay Interface and the corresponding confirmation of the FlexRay Interface on the receiver side (for FC or AF). mmt.qualifiedName="FlexrayTpChannel.timeoutAr";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter states the timeout in seconds between the PDU transmit request for the first PDU of the group used in the current connection of the Transport Layer to the FlexRay Interface and the corresponding confirmation of the FlexRay Interface (when having sent the last PDU of the group used in this connection) on the sender side (SF-x, FF-x, CF). mmt.qualifiedName="FlexrayTpChannel.timeoutAs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the timeout in seconds for waiting for an FC or AF on the sender side in a 1:1 connection. mmt.qualifiedName="FlexrayTpChannel.timeoutBs";pureMM.maxOccurs="1";pureMM.minOccurs="0" This parameter defines the timeout value in seconds for waiting for a CF or FF-x (in case of retry) after receiving the last CF or after sending an FC or AF on the receiver side. mmt.qualifiedName="FlexrayTpChannel.timeoutCr";pureMM.maxOccurs="1";pureMM.minOccurs="0" Group of connections that can be used in this channel. mmt.qualifiedName="tpConnection.FlexrayTpChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="1" This attribute states whether Transmit Cancellation is supported on this channel. mmt.qualifiedName="FlexrayTpChannel.transmitCancellation";pureMM.maxOccurs="1";pureMM.minOccurs="1" A channel is a group of connections sharing several properties. The FlexRay Transport Layer supports several channels. These channels can work concurrently, thus each of them requires its own state machine and management data structures and its own PDU-IDs. mmt.qualifiedName="FlexrayTpChannel" atpObject TP Node (Sender or Receiver) provides the TP Address and the connection to the Topology description. mmt.qualifiedName="FlexrayTpNode" atpObject Configuration parameter type for Float. mmt.qualifiedName="FloatParamDef";xml.sequenceOffset="0" atpObject Default value of the float configuration parameter. mmt.qualifiedName="FloatParamDef.defaultValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" max value allowed for the parameter defined. mmt.qualifiedName="FloatParamDef.max";pureMM.maxOccurs="1";pureMM.minOccurs="0" min value allowed for the parameter defined. mmt.qualifiedName="FloatParamDef.min";pureMM.maxOccurs="1";pureMM.minOccurs="0" Configuration parameter type for Float. mmt.qualifiedName="FloatParamDef";xml.sequenceOffset="0" atpObject Representing a configuration value of definition type FloatParamDef mmt.qualifiedName="FloatValue" atpObject Stores the value of the Float parameter. mmt.qualifiedName="FloatValue.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Representing a configuration value of definition type FloatParamDef mmt.qualifiedName="FloatValue" atpObject The ForbiddenSignalPath describes the physical channels which an element must not take in the topology. Such a signal path can be a constraint for the communication matrix, because such a path has an effect on the frame generation and the frame path. mmt.qualifiedName="ForbiddenSignalPath" atpObject Reference to the operation arguments of one operation which must not take the predefined way in the topology. mmt.qualifiedName="operation.ForbiddenSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The SwcToSwcSignal must not be transmitted on one of these physical channels. mmt.qualifiedName="ForbiddenSignalPath.physicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The data element which must not take the predefined way in the topology. mmt.qualifiedName="signal.ForbiddenSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The ForbiddenSignalPath describes the physical channels which an element must not take in the topology. Such a signal path can be a constraint for the communication matrix, because such a path has an effect on the frame generation and the frame path. mmt.qualifiedName="ForbiddenSignalPath" atpObject Specify a reference to an XML description of an entity desribed in another AUTOSAR template. mmt.qualifiedName="ForeignReferenceParamDef" atpObject The type in the AUTOSAR Metamodel to which' instance this reference is allowed to point to. mmt.qualifiedName="ForeignReferenceParamDef.destinationType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specify a reference to an XML description of an entity desribed in another AUTOSAR template. mmt.qualifiedName="ForeignReferenceParamDef" atpObject Data frame which is sent over a communication medium. This element describes the pure Layout of a frame sent on a channel. mmt.qualifiedName="Frame" atpObject The used length (in bytes) of the referencing frame. Should not be confused with a static byte length reserved for each frame by some platforms (e.g. FlexRay). mmt.qualifiedName="Frame.frameLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" A frames layout as a sequence of Pdus. mmt.qualifiedName="pduToFrameMapping.Frame";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Data frame which is sent over a communication medium. This element describes the pure Layout of a frame sent on a channel. mmt.qualifiedName="Frame" atpObject The entire source frame is mapped as it is onto the target frame (what in general is only possible inside of a common platform). In this case source and target frame should be the identical object. Each pair consists in a SOURCE and a TARGET referencing to a FrameTriggering. The Frame Mapping is not supported by the Autosar BSW. The existence is optional and has been incorporated into the System Template mainly for compatibility in order to allow interchange between FIBEX and AUTOSAR descriptions. mmt.qualifiedName="FrameMapping" atpObject Source destination of the referencing mapping. mmt.qualifiedName="FrameMapping.sourceFrame";pureMM.maxOccurs="1";pureMM.minOccurs="1" Target destination of the referencing mapping. mmt.qualifiedName="FrameMapping.targetFrame";pureMM.maxOccurs="1";pureMM.minOccurs="1" The entire source frame is mapped as it is onto the target frame (what in general is only possible inside of a common platform). In this case source and target frame should be the identical object. Each pair consists in a SOURCE and a TARGET referencing to a FrameTriggering. The Frame Mapping is not supported by the Autosar BSW. The existence is optional and has been incorporated into the System Template mainly for compatibility in order to allow interchange between FIBEX and AUTOSAR descriptions. mmt.qualifiedName="FrameMapping" atpObject Connectors reception or send port on the referenced channel referenced by a FrameTriggering. mmt.qualifiedName="FramePort" atpObject The FrameTriggering describes the instance of a frame sent on a channel and defines the manner of triggering (timing information) and identification of a frame on the channel, on which it is sent. For the same frame, if Frame Triggerings exist on more than one channel of the same cluster the fan-out/in is handled by the Bus interface. mmt.qualifiedName="FrameTriggering" atpObject This reference allows to specify explicitly which Frame is received/sent by the connected ECU on the connected channel. This reference shall be provided to every FramePort on every ECU in the System which sends and/or receives the Frame. mmt.qualifiedName="FrameTriggering.framePort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" One frame can be triggered on different channels. If a frame has no frame triggering, it won&rsquo;t be sent at all. A frame triggering has assigned exactly one frame, which it triggers. mmt.qualifiedName="FrameTriggering.frame";pureMM.maxOccurs="1";pureMM.minOccurs="1" This reference provides the relationship to the IPduTriggerings that are implemented by the FrameTriggering. The reference is optional since no IPduTriggering can be defined for NmPdus. mmt.qualifiedName="FrameTriggering.iPduTriggering";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Representing freely defined data. mmt.qualifiedName="FreeFormat" atpObject The integer Value of a freely defined data byte. mmt.qualifiedName="FreeFormat.ByteValue";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Representing freely defined data. mmt.qualifiedName="FreeFormat" atpObject Class describing minimum, maximum and typical frequencies. mmt.qualifiedName="FrequencyRange" atpObject Maximum frequency. Unit: Herz mmt.qualifiedName="FrequencyRange.maxFrequency";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum frequency. Unit: Herz mmt.qualifiedName="FrequencyRange.minFrequency";pureMM.maxOccurs="1";pureMM.minOccurs="1" Typical frequency. Unit: Herz mmt.qualifiedName="FrequencyRange.typicalFrequency";pureMM.maxOccurs="1";pureMM.minOccurs="0" Class describing minimum, maximum and typical frequencies. mmt.qualifiedName="FrequencyRange" atpObject Use <ft> , to create a footnote. mmt.qualifiedName="Ft" atpMixedString,atpObject Specifies the abstract needs on the configuration of the Function Inhibition Manager for one Function Identifier (FID). This class currently contains no attributes. Its name can be regarded as a symbol identifying the FID from the viewpoint of the component or module which owns this class. mmt.qualifiedName="FunctionInhibitionNeeds" atpObject Configuration parameter type for Function Names like those used to specify callback functions. mmt.qualifiedName="FunctionNameDef" atpObject Representing a configuration value of definition type FunctionNameDef mmt.qualifiedName="FunctionNameValue" atpObject A gateway is an ECU that is connected to two or more clusters (channels, but not redundant), and performs a frame, Pdu or signal mapping between them. mmt.qualifiedName="Gateway" atpObject mmt.qualifiedName="Gateway.ecu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Frame Gateway: The entire source frame is mapped as it is onto the target frame (what in general is only possible inside of a common platform). In this case source and target frame should be the identical object. mmt.qualifiedName="frameMapping.Gateway";pureMM.maxOccurs="-1";pureMM.minOccurs="0" IPdu Gateway: Arranges those IPdus that are transferred by the gateway from one channel to the other in pairs and defines the mapping between them. mmt.qualifiedName="iPduMapping.Gateway";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Signal Gateway: Arranges those signals that are transferred by the gateway from one channel to the other in pairs and defines the mapping between them. mmt.qualifiedName="signalMapping.Gateway";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A gateway is an ECU that is connected to two or more clusters (channels, but not redundant), and performs a frame, Pdu or signal mapping between them. mmt.qualifiedName="Gateway" atpObject This class represents textual comments (called annotations) which relate to the object in which it is aggregated. These are intended for use during the development process, to transfer information from one stage of the development process to the next one. The approach is similar to the "yellow pads ..." This abstract class can be specialized in order to add some further formal properties. mmt.qualifiedName="GeneralAnnotation" atpObject label is used as a long designator (similar to longName) for objects which cannot be referenced. mmt.qualifiedName="GeneralAnnotation.label";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" This element identifies the origin of the annotation. It is an arbitrary string since it can be an individual's name as well as the name of a tool or even the name of a process step. mmt.qualifiedName="GeneralAnnotation.annotationOrigin";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" This is the text of the annotation. mmt.qualifiedName="GeneralAnnotation.annotationText";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" Common attributes shared by all timer peripherals mmt.qualifiedName="GeneralPurposeTimer" atpObject The clock input to a timer can have different sources like the internal system clock or an external clock. If the clock is pre-scaled this information should be entered in the table. mmt.qualifiedName="GeneralPurposeTimer.clockSource";pureMM.maxOccurs="1";pureMM.minOccurs="0" Some timers have the possibility to detect signals from a quadrature rotating switch. There are two outputs signal from such a switch; the signals are 90 degrees phase shifted from each other. The rotation of the switch can then automatically be detected by a special function in a timer. mmt.qualifiedName="GeneralPurposeTimer.phaseDetection";pureMM.maxOccurs="1";pureMM.minOccurs="1" For a timer the resolution defines the data width of the counter. Unit: Bits mmt.qualifiedName="GeneralPurposeTimer.resolution";pureMM.maxOccurs="1";pureMM.minOccurs="1" The threshold is the definition of a counter value. When the counter has reached this value some action is performed, e.g. an interrupt can be generated. mmt.qualifiedName="GeneralPurposeTimer.thresholdValue";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Abstract class to specify the ability to connect HWPorts. mmt.qualifiedName="HWConnection" atpObject A set of connections between HWPins of the connected HWPorts. mmt.qualifiedName="connectedPin.HWConnection";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A HW Container is a group of HW Elements on the same hierarchical level and is an abstraction of composite HW Elements. The HW Container is a specialisation of a HW Element and therefore the HW Container has all elements of a HW Element. The values of elements of the HW Elements grouped in a HW Container may differ from the values of the elements of the HW Container. mmt.qualifiedName="HWContainer" atpObject The General HW Element specifies definitions valid for all specific HW Elements. mmt.qualifiedName="HWElement" atpObject For the placement of a HW Element within a car the temperature has to be considered the HW Element has been designed for. mmt.qualifiedName="hwElementTemperature.HWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" All the HWPorts this HWElement exposes. This also includes delegation HWPorts of HWContainers. mmt.qualifiedName="port.HWElement";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The Signal Transformation defines the conversion of the signal attached to a HW Port (direction In) and a signal attached to a HW Port (direction Out). mmt.qualifiedName="signalTransformation.HWElement";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The Standby Current is the current in state OFF. For HW Elements the Standby Current consists of the current needed by the logic to stay in the state OFF and the leakage current of the HW Element. For big HW Elements the leakage current can be up to several 100 microA. Standby Current is used to determine which elements are necessary to be switch off, when the car itself is in a standby mode. This can be done automatically or by the user. The value for the Standby Current can be entered for each HW Element and HW Container respectively. The user has to take care about these values and decides about the entries necessary for the calculation of the complete standby current. On the other side the sum for all HW Elements grouped in a HW Container may have a bigger value than the value for the HW Container itself. In this case the values for the HW Elements represent the worst case for each HW Element. Unit: Ampere (A) mmt.qualifiedName="HWElement.standbyCurrent";pureMM.maxOccurs="1";pureMM.minOccurs="0" The ECU Resource Template provides the element Supports Safety storing the information about the supported safety mechanism. In the current version of the ECU Resource Template the element Supports Safety is optional. A HW Element uses this element if it provides a safety mechanism otherwise this element is missing in the description of the HW Element. mmt.qualifiedName="supportsSafety.HWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" The ECU Resource Template provides the element SupportsSecurity storing the information about the supported security mechanism. In the current version of the ECU Resource Template the element SupportsSecurity is optional. A HW Element uses this element if it provides a security mechanism otherwise this element is missing in the description of the HW Element. mmt.qualifiedName="supportsSecurity.HWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" Abstract class to enable the collection of HW Elements. mmt.qualifiedName="HWElementContainer" atpObject The connections gathered within the HWElementContainer. mmt.qualifiedName="connection.HWElementContainer";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The HW Elements contained in the HW Element Container. mmt.qualifiedName="containedElement.HWElementContainer";pureMM.maxOccurs="-1";pureMM.minOccurs="1" A HWPin is an elementary electrical interface of the HWElement. The HWPins of a HWPort can be clustered if there are some HWPins with the same behaviour. mmt.qualifiedName="HWPin" atpObject The general element HW Port is necessary to connect HW Elements and contains common elements for all different kind of HW Ports. HW Ports are required to be uniquely identifiable within the scope of a HW Element. This means to identify a specific HW Port it is necessary to prefix the HW Port name by the name of the HW Element (e.g."PU1/ADCPort3"). mmt.qualifiedName="HWPort" atpObject The direction of a HW Port defines signal flow in the point of view of the HW Element the HW Port belongs to. The following attributes are allowed: mmt.qualifiedName="HWPort.direction";pureMM.maxOccurs="1";pureMM.minOccurs="1" These are the pins the HWPort assembles. If the HWPort does not have HWPins (because the HWPort is inside a micro) the set is empty. mmt.qualifiedName="pin.HWPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The general element HW Port is necessary to connect HW Elements and contains common elements for all different kind of HW Ports. HW Ports are required to be uniquely identifiable within the scope of a HW Element. This means to identify a specific HW Port it is necessary to prefix the HW Port name by the name of the HW Element (e.g."PU1/ADCPort3"). mmt.qualifiedName="HWPort" atpObject HWPortMapping specifies the ECUCommunicationPort hardware (defined in the ECU Resource Template) to realize the specified CommunicationConnector in a physical topology. mmt.qualifiedName="HWPortMapping" atpObject Reference to the CommunicationConnector in the System Template mmt.qualifiedName="HWPortMapping.communicationConnector";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Peripheral in the ECU Resource Template mmt.qualifiedName="HWPortMapping.ecuCommunicationPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" HWPortMapping specifies the ECUCommunicationPort hardware (defined in the ECU Resource Template) to realize the specified CommunicationConnector in a physical topology. mmt.qualifiedName="HWPortMapping" atpObject Describes in which mode the hardware is operating while providing the ExecutionTime. mmt.qualifiedName="HardwareConfiguration" atpObject Specifies additional information on the HardwareConfiguration. mmt.qualifiedName="HardwareConfiguration.additionalInformation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies in which mode the processor is operating. mmt.qualifiedName="HardwareConfiguration.processorMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the speed the processor is operating. mmt.qualifiedName="HardwareConfiguration.processorSpeed";pureMM.maxOccurs="1";pureMM.minOccurs="1" Describes in which mode the hardware is operating while providing the ExecutionTime. mmt.qualifiedName="HardwareConfiguration" atpObject Describes the heap memory usage of a SW-Component. mmt.qualifiedName="HeapUsage" atpObject Reference to the ECU description this implementation is provided for. mmt.qualifiedName="HeapUsage.ecu";pureMM.maxOccurs="1";pureMM.minOccurs="0" Contains information about the hardware context this heap usage is describing. mmt.qualifiedName="hardwareConfiguration.HeapUsage";pureMM.maxOccurs="1";pureMM.minOccurs="0" Contains details about the software context this heap usage is provided for. mmt.qualifiedName="softwareContext.HeapUsage";pureMM.maxOccurs="1";pureMM.minOccurs="0" The IPdu (Interaction Layer Protocol Data Unit) element is used to sum up the IPdus of AUTOSAR COM, DCM and IPduM. These Pdus are routed by the PduR. In the AUTOSAR Layered Archtecture the NPdu is not a spezialisation of an IPdu. The NPdu is located under the IPdu to support the low-level routing of NPdu's. More details can be found in the NPdu class description. mmt.qualifiedName="IPdu" atpObject The size of the IPDU in bits. mmt.qualifiedName="IPdu.length";pureMM.maxOccurs="1";pureMM.minOccurs="1" AUTOSAR COM fills not 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. mmt.qualifiedName="IPdu.unusedBitPattern";pureMM.maxOccurs="1";pureMM.minOccurs="0" The AUTOSAR COM Layer is able to start and to stop sending and receiving configurable groups of I-Pdus during runtime. An I-Pdu group contains either Com I-Pdus or I-Pdu groups. When an I-Pdu group containing one or more other I-Pdu groups is started the contained I-Pdu groups shall also be started. When an I-Pdu group containing one or more other I-Pdu groups is stopped the contained I-Pdu groups shall also be stopped. Only a two level hierarchy of I-Pdu groups is allowed. An I-Pdu group that is part of an I-Pdu group must not contain I-Pdu groups. In the COM SRS document it is stated that "every IPdu must belong to exactly 1 I-Pdu group." This is true from a dedicated ECUs point of view, however in the system description handling a number of ECUs several IPdu Groups may reference to the same SignalIPdu. mmt.qualifiedName="IPduGroup" atpObject This attribute determines in which direction IPdus that are contained in this IPduGroup will be transmitted (communication direction can be either Send or Receive). mmt.qualifiedName="IPduGroup.communicationDirection";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute defines the use-case for this IPduGroup (e.g. diagnostic, debugging etc.). For example, in a diagnostic mode all IPdus - which are not involved in diagnostic - are disabled. The use cases are not limited to a fixed enumeration and can be specified as a string. mmt.qualifiedName="IPduGroup.communicationMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" An I-PDU group can be included in other I-Pdu groups. mmt.qualifiedName="IPduGroup.containedIPduGroups";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to a set of SignalIPdus, which are contained in the I-Pdu Group. mmt.qualifiedName="IPduGroup.iPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The AUTOSAR COM Layer is able to start and to stop sending and receiving configurable groups of I-Pdus during runtime. An I-Pdu group contains either Com I-Pdus or I-Pdu groups. When an I-Pdu group containing one or more other I-Pdu groups is started the contained I-Pdu groups shall also be started. When an I-Pdu group containing one or more other I-Pdu groups is stopped the contained I-Pdu groups shall also be stopped. Only a two level hierarchy of I-Pdu groups is allowed. An I-Pdu group that is part of an I-Pdu group must not contain I-Pdu groups. In the COM SRS document it is stated that "every IPdu must belong to exactly 1 I-Pdu group." This is true from a dedicated ECUs point of view, however in the system description handling a number of ECUs several IPdu Groups may reference to the same SignalIPdu. mmt.qualifiedName="IPduGroup" atpObject Arranges those IPdus that are transferred by the gateway from one channel to the other in pairs and defines the mapping between them. mmt.qualifiedName="IPduMapping" atpObject Optionally defines the to be configured Pdu Router TpChunkSize for this routing relation. mmt.qualifiedName="IPduMapping.pdurTpChunkSize";pureMM.maxOccurs="1";pureMM.minOccurs="0" Source destination of the referencing mapping. mmt.qualifiedName="sourceIPdu.IPduMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Target destination of the referencing mapping. mmt.qualifiedName="targetIPdu.IPduMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Arranges those IPdus that are transferred by the gateway from one channel to the other in pairs and defines the mapping between them. mmt.qualifiedName="IPduMapping" atpObject Connectors reception or send port on the referenced channel referenced by an IPduTriggering. mmt.qualifiedName="IPduPort" atpObject AUTOSAR COM provides the possibility to define two different TRANSMISSION MODES for each I-PDU. The Transmission Mode of an I-PDU that is valid at a specific point in time is selected using the values of the signals that are mapped to this I-PDU. For each I-PDU a Transmission Mode Selector is defined. The Transmission Mode Selector is calculated by evaluating the conditions for a subset of signals (class TransmissionModeCondition in the System Template). The Transmission Mode Selector is defined to be true, if at least one Condition evaluates to true and is defined to be false, if all Conditions evaluate to false. mmt.qualifiedName="IPduTiming" atpObject If the COM Transmission Mode is true the timing can be aggregated directly by the IPduTriggering. Additionally a Cyclic Timing can be defined as a Timing Requirement (for Lin, FlexRay). Timing Requirements are aggregated by the IPduTriggering/IPduTiming element. mmt.qualifiedName="cyclicTiming.IPduTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" If the COM Transmission Mode is true the timing can be aggregated directly by the IPduTiming. Additionally an EventControlledTiming can be defined as a Timing Requirement (for Lin, FlexRay). Timing Requirements are aggregated by the IPduTriggering/IPduTiming element. mmt.qualifiedName="eventControlledTiming.IPduTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" Minimum Delay in seconds between successive transmissions of this I-PDU, independent of the Transmission Mode. mmt.qualifiedName="IPduTiming.minimumDelay";pureMM.maxOccurs="1";pureMM.minOccurs="0" A RequestControlled Timing can be defined as a Timing Requirement. Timing Requirements are aggregated by the IPduTriggering/IPduTiming element. mmt.qualifiedName="requestControlledTiming.IPduTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" AUTOSAR COM allows configuring statically two different transmission modes for each I-PDU (True and False). The Transmission Mode Selector evaluates the conditions for a subset of signals and decides the transmission mode. It is possible to switch between the transmission modes during runtime. In case only the TRUE transmission mode is used there is no need for the "TransmissionModeDeclaration" and its sub-structure. mmt.qualifiedName="transmissionModeDeclaration.IPduTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" AUTOSAR COM provides the possibility to define two different TRANSMISSION MODES for each I-PDU. The Transmission Mode of an I-PDU that is valid at a specific point in time is selected using the values of the signals that are mapped to this I-PDU. For each I-PDU a Transmission Mode Selector is defined. The Transmission Mode Selector is calculated by evaluating the conditions for a subset of signals (class TransmissionModeCondition in the System Template). The Transmission Mode Selector is defined to be true, if at least one Condition evaluates to true and is defined to be false, if all Conditions evaluate to false. mmt.qualifiedName="IPduTiming" atpObject The IPduTriggering describes on which channel the IPdu is transmitted. Depending on its relation to entities such channels and clusters it can be unambiguously deduced whether a fan-out is handled by the Pdu router or the Bus Interface. If the fan-out is specified between different clusters it shall be handled by the Pdu Router. If the fan-out is specified between different channels of the same cluster it shall be handled by the Bus Interface. mmt.qualifiedName="IPduTriggering" atpObject This relationship specifies explicitly which IPdus are received/sent by the connected ECU on the connected channel. This reference shall be provided to every IPduPort on every ECU in the System which sends and/or receives the IPdu. mmt.qualifiedName="IPduTriggering.iPduPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to the Pdu for which the IPdu triggering is defined. One IPdu can be triggered on different channels. The Pdu routing by the PduR is only allowed for IPdus and not for NmPdus and UserDefinedPdus. Nevertheless is the reference to the Pdu element necessary since the PduTriggering element is also used to specify the sending and receiving connections to EcuPorts. mmt.qualifiedName="IPduTriggering.iPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" This reference provides the relationship to the ISignalTriggerings that are implemented by the IPduTriggering. The reference is optional since no ISignalTriggering can be defined for DCM and Multiplexed Pdus. mmt.qualifiedName="IPduTriggering.iSignalTriggering";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Describes timing requirements on an I-PDU, handled by the bus interface, (Flexray or LIN). For CAN the timing information must be equal to the timing specification on a signal IPdu. mmt.qualifiedName="timingRequirement.IPduTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="0" The IPduTriggering describes on which channel the IPdu is transmitted. Depending on its relation to entities such channels and clusters it can be unambiguously deduced whether a fan-out is handled by the Pdu router or the Bus Interface. If the fan-out is specified between different clusters it shall be handled by the Pdu Router. If the fan-out is specified between different channels of the same cluster it shall be handled by the Bus Interface. mmt.qualifiedName="IPduTriggering" atpObject Signal of the Interaction Layer. The RTE supports a "signal fan-out" where the same System Signal is sent in different SignalIPdus to multiple receivers. The System Signal is unique per System. To support the RTE "signal fan-out" each SignalIPdu contains ISignals. If the same System Signal is to be mapped into several SignalIPdus there is one ISignal needed for each ISignalToIPduMapping. ISignals describe the Interface between the Precompile configured RTE and the potentially Postbuild configured Com Stack (see ECUC Parameter Mapping). In the case of the SystemSignalGroup an ISignal must be created for the SystemSignalGroup and for each SystemSignal contained in the SystemSignalGroup. If a mapping for the SystemSignalGroup is defined, only the UpdateIndicationBitPosition is relevant, and the startPosition shall be ignored. mmt.qualifiedName="ISignal" atpObject Reference to the System Signal that is supposed to be transmitted in the ISignal. mmt.qualifiedName="ISignal.systemSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" Signal of the Interaction Layer. The RTE supports a "signal fan-out" where the same System Signal is sent in different SignalIPdus to multiple receivers. The System Signal is unique per System. To support the RTE "signal fan-out" each SignalIPdu contains ISignals. If the same System Signal is to be mapped into several SignalIPdus there is one ISignal needed for each ISignalToIPduMapping. ISignals describe the Interface between the Precompile configured RTE and the potentially Postbuild configured Com Stack (see ECUC Parameter Mapping). In the case of the SystemSignalGroup an ISignal must be created for the SystemSignalGroup and for each SystemSignal contained in the SystemSignalGroup. If a mapping for the SystemSignalGroup is defined, only the UpdateIndicationBitPosition is relevant, and the startPosition shall be ignored. mmt.qualifiedName="ISignal" atpObject An ISignalToIPduMapping describes the mapping of ISignals to ISignalIPdus and defines the position of the ISignal within an ISignalIPdu. This element does NOT describe signal or IPdu fan-out but is used to describe the COM Signal Gateway fan-out. In case the ISignal/ISignalGroup is not part of the Signal Gateway the ISignal/ISignalGroup can only be mapped into one ISignalIPdu. In case the ISignal/ISignalGroup is part of the Signal Gateway several ISignalToIPduMappings of the same ISignal are supported. mmt.qualifiedName="ISignalToIPduMapping" atpObject This parameter defines the order of the bytes of the signal and the packing into the SignalIPdu. The byte ordering "Little Endian" (MostSignificantByteLast) and "Big Endian" (MostSignificantByteFirst) can be selected. The value of this attribute impacts the absolute position of the signal into the SignalIPdu (see the startPosition attribute description). mmt.qualifiedName="ISignalToIPduMapping.packingByteOrder";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to a ISignal that is mapped into the SignalIPdu. Several ISignalToPduMappings to the same ISignal are only relevant when the ECU handles the signal gateway. mmt.qualifiedName="ISignalToIPduMapping.signal";pureMM.maxOccurs="1";pureMM.minOccurs="1" 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 packingByteOrder attribute). Bits within the IPdu are counted as follows (see the OSEK COM v3.0.3 specification) : Bit 0 corresponds to Byte 0 Bit 0 Bit 1 corresponds to Byte 0 Bit 1 ..... Bit 8 corresponds to Byte 1 Bit 0 etc. 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. Note also that the absolute position of the signal in the SignalIPdu is then determined by the definition of the packingByteOrder attribute of the signal. If a mapping for the SystemSignalGroup is defined, only the UpdateIndicationBitPosition is relevant, and the startPosition shall be ignored. mmt.qualifiedName="ISignalToIPduMapping.startPosition";pureMM.maxOccurs="1";pureMM.minOccurs="0" The triggered, triggeredOnChange, triggeredWithoutRepetition and triggeredOnChangeWithoutRepetition transferProperty causes immediate transmission of the IPdu, except if transmission mode Periodic or transmission mode NONE is defined for the IPdu. The Pending transfer property does not cause transmission of an IPdu. The immediate transmission of the IPdu is caused even if only one Signal of an IPdu has the transferProperty triggered, triggeredWithoutRepetition, triggeredOnChange, triggeredOnChangeWithoutRepetition and all other Signals have the transferProperty pending. Also for ISignals which refer to GroupSignals of a SystemSignalGroup this attribute is relevant and shall be evaluated: - If none of the ISignals belonging to the GroupSignals of a SystemSignalGroup have a transferProperty defined the transferProperty of the ISignal referring to the SystemSignalGroup is considered. - If at least one of the ISignals belonging to the GroupSignals of a SystemSignalGroup has a transferProperty defined all ISignals belonging to the GroupSignals of a SystemSignalGroup shall have a transferProperty defined as well. All of the transferProperties of the ISignals belonging to the GroupSignals of a SystemSignalGroup are considered. mmt.qualifiedName="ISignalToIPduMapping.transferProperty";pureMM.maxOccurs="1";pureMM.minOccurs="1" The UpdateIndicationBit indicates to the receivers that the signal (or the signal group) was updated by the sender. Length is always one bit. The UpdateIndicationBitPosition attribute describes the position of the update bit within the SignalIPdu. The updateIndicationBitPosition is determined by the definition of the packingByteOrder attribute. If Big Endian is specified, the updateIndicationBitPosition indicates the bit position of the most significant bit in the ISignalIPdu. If Little Endian is specified, the updateIndicationBitPosition indicates the bit position of the least significant bit in the ISignalIPdu. mmt.qualifiedName="ISignalToIPduMapping.updateIndicationBitPosition";pureMM.maxOccurs="1";pureMM.minOccurs="0" An ISignalToIPduMapping describes the mapping of ISignals to ISignalIPdus and defines the position of the ISignal within an ISignalIPdu. This element does NOT describe signal or IPdu fan-out but is used to describe the COM Signal Gateway fan-out. In case the ISignal/ISignalGroup is not part of the Signal Gateway the ISignal/ISignalGroup can only be mapped into one ISignalIPdu. In case the ISignal/ISignalGroup is part of the Signal Gateway several ISignalToIPduMappings of the same ISignal are supported. mmt.qualifiedName="ISignalToIPduMapping" atpObject A ISignalTriggering defines the manner of triggering of a ISignal on the channel, on which it is sent. ISignalTriggering should only be used for defining timing constraints. Com does not know of signals related to a specific cluster or channel. mmt.qualifiedName="ISignalTriggering" atpObject Specification of a cyclic sending behavior. mmt.qualifiedName="cyclicTiming.ISignalTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specification of a event driven sending behavior. mmt.qualifiedName="eventControlledTiming.ISignalTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="0" This relationship allows to specify explicitly which ISignals are received/sent by the connected ECU on the connected channel. This reference shall be provided to every SignalPort on every ECU in the System which sends and/or receives the Signal. mmt.qualifiedName="ISignalTriggering.iSignalPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to the ISignal for which the ISignalTriggering is defined. mmt.qualifiedName="ISignalTriggering.signal";pureMM.maxOccurs="1";pureMM.minOccurs="1" A ISignalTriggering defines the manner of triggering of a ISignal on the channel, on which it is sent. ISignalTriggering should only be used for defining timing constraints. Com does not know of signals related to a specific cluster or channel. mmt.qualifiedName="ISignalTriggering" atpObject Instances of this class can be referred to by their identifier (while adhering to namespace borders). mmt.qualifiedName="Identifiable" atpObject Use <shortName> to generate a short name for the context element, which enables it to be ** . mmt.qualifiedName="Identifiable.shortName";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.enforceMinMultiplicity="true";xml.sequenceOffset="-100" Use <longName> to create a comprehensive name for the context element. mmt.qualifiedName="Identifiable.longName";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-90" <desc> represents a general but brief description of the object in question. mmt.qualifiedName="Identifiable.desc";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-60" This element assigns a category to the parent element. The category can be used by a semantic checker in post-processes to ensure that the parent object is defined correctly i.e. has the right number of elements for example. mmt.qualifiedName="Identifiable.category";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-50" <adminData> can be used to set administrative information for an element. This administration information is to be treated as metadata such as revision id or state of the file. There are basically four kinds of metadata * The language and/or used laguages. * Revision information covering e.g. revision number, state, release date, changes. Note that this information can be given in general as well as related to a particular company. * Document metadata specific for a company * Formatting controls that can affect layouts for example. * Revision information for the element. mmt.qualifiedName="Identifiable.adminData";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-40" This represents more information about how the object in question is built or is used. Therefore it is a DocumentationBlock. In this AUTOSAR Version it is intended to refer to external objexts which are not processed by AUTOSAR-tools. mmt.qualifiedName="Identifiable.introduction";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="-30" Instances of this class can be referred to by their identifier (while adhering to namespace borders). mmt.qualifiedName="Identifiable" atpObject The purpose of this attribute is to provide a globally unique identifier for an instance of a metaclass. The values of this attribute should be globally unique strings prefixed by the type of identifier. For example, to include a DCE UUID as defined by The Open Group, the UUID would be preceded by "DCE:". The values of this attribute may be used to support merging of different AUTOSAR models. The form of the UUID (Universally Unique Identifier) is taken from a standard defined by the Open Group (was Open Software Foundation). This standard is widely used, including by Microsoft for COM (GUIDs) and by many companies for DCE, which is based on CORBA. The method for generating these 128-bit IDs is published in the standard and the effectiveness and uniqueness of the IDs is not in practice disputed. If the id namespace is omitted, DCE is assumed. An example is "DCE:2fac1234-31f8-11b4-a222-08002b34c003". mmt.qualifiedName="Identifiable.uuid";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" Use <ie> to create an index that is to appear in the index directory. mmt.qualifiedName="Ie" atpMixedString,atpObject Description of an implementation a single software component or module. mmt.qualifiedName="Implementation" atpObject Specifies the provided implementation code. mmt.qualifiedName="codeDescriptor.Implementation";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Optional: code generator used. mmt.qualifiedName="Implementation.codeGenerator";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specifies the compiler for which this implementation has been released mmt.qualifiedName="compiler.Implementation";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specifies details on dependent software, modules or libraries. mmt.qualifiedName="implementationDependency.Implementation";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.namePlural="IMPLEMENTATION-DEPENDENCIES" Specifies the linker for which this implementation has been released. mmt.qualifiedName="linker.Implementation";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The processor the implementation is compatible with. mmt.qualifiedName="Implementation.processor";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Programming language the implementation was created in. mmt.qualifiedName="Implementation.programmingLanguage";pureMM.maxOccurs="1";pureMM.minOccurs="1" All static and dynamic resources for each implementation are described within the ResourceConsumption class. mmt.qualifiedName="resourceConsumption.Implementation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Major version number of this implementation. The numbering is vendor specific. mmt.qualifiedName="Implementation.swMajorVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minor version number of this implementation. The numbering is vendor specific. mmt.qualifiedName="Implementation.swMinorVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Patch version number of this implementation. The numbering is vendor specific. mmt.qualifiedName="Implementation.swPatchVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Vendor ID of this Implementation according to the AUTOSAR vendor list mmt.qualifiedName="Implementation.vendorId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Description of an implementation a single software component or module. mmt.qualifiedName="Implementation" atpObject Specifies which ConfigurationClass this parameter has in the individual ConfigurationVariants. mmt.qualifiedName="ImplementationConfigClass" atpObject Specifies the ConfigurationClass for the given ConfigurationVariant. mmt.qualifiedName="ImplementationConfigClass.configClass";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the ConfigurationVariant the ConfigurationClass is specified for. mmt.qualifiedName="ImplementationConfigClass.configVariant";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies which ConfigurationClass this parameter has in the individual ConfigurationVariants. mmt.qualifiedName="ImplementationConfigClass" atpObject mmt.qualifiedName="IndexedArrayElement" atpObject,indexedRef Reference to an element in an array. mmt.qualifiedName="IndexedArrayElement.arrayElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" Position of an element in an array. mmt.qualifiedName="IndexedArrayElement.index";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="IndexedArrayElement" atpObject,indexedRef This represents the ablity to assign an initial value to a calibration parameter. mmt.qualifiedName="InitValueAssignment" atpObject This is the init value. mmt.qualifiedName="InitValueAssignment.initValue";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.SequenceOffset="20" This is the parameter for which the initial value applies. mmt.qualifiedName="InitValueAssignment.parameter";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.SequenceOffset="10" Specify a reference to an XML description of an entity desribed in another AUTOSAR template using the INSTANCE REFERENCE semantics. mmt.qualifiedName="InstanceReferenceParamDef" atpObject The context in the AUTOSAR Metamodel to which' this reference is allowed to point to. mmt.qualifiedName="InstanceReferenceParamDef.destinationContext";pureMM.maxOccurs="1";pureMM.minOccurs="1" The type in the AUTOSAR Metamodel to which' instance this reference is allowed to point to. mmt.qualifiedName="InstanceReferenceParamDef.destinationType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specify a reference to an XML description of an entity desribed in another AUTOSAR template using the INSTANCE REFERENCE semantics. mmt.qualifiedName="InstanceReferenceParamDef" atpObject InstanceReference representation in the ECU Configuration. mmt.qualifiedName="InstanceReferenceValue" atpObject InstanceReference representation in the ECU Configuration. mmt.qualifiedName="value.InstanceReferenceValue";pureMM.maxOccurs="1";pureMM.minOccurs="1" InstanceReference representation in the ECU Configuration. mmt.qualifiedName="InstanceReferenceValue" atpObject mmt.qualifiedName="InstanceReferenceValue_value" atpObject,instanceRef mmt.qualifiedName="InstanceReferenceValue_value.context";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="InstanceReferenceValue_value.value";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="InstanceReferenceValue_value" atpObject,instanceRef Constant integer value. mmt.qualifiedName="IntegerLiteral" atpObject,atpPrototype The value. mmt.qualifiedName="IntegerLiteral.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Constant integer value. mmt.qualifiedName="IntegerLiteral" atpObject,atpPrototype Configuration parameter type for Integer. mmt.qualifiedName="IntegerParamDef";xml.sequenceOffset="0" atpObject Default value of the integer configuration parameter. mmt.qualifiedName="IntegerParamDef.defaultValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" max value allowed for the parameter defined. mmt.qualifiedName="IntegerParamDef.max";pureMM.maxOccurs="1";pureMM.minOccurs="0" min value allowed for the parameter defined. mmt.qualifiedName="IntegerParamDef.min";pureMM.maxOccurs="1";pureMM.minOccurs="0" Configuration parameter type for Integer. mmt.qualifiedName="IntegerParamDef";xml.sequenceOffset="0" atpObject This data-type are the integers in the interval defined by the Range. mmt.qualifiedName="IntegerType" atpObject,atpType Representing a configuration value of definition type IntegerParamDef mmt.qualifiedName="IntegerValue" atpObject Stores the value of the Integer parameter. mmt.qualifiedName="IntegerValue.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Representing a configuration value of definition type IntegerParamDef mmt.qualifiedName="IntegerValue" atpObject Implement state message semantics for establishing communication among runnables of the same component. mmt.qualifiedName="InterRunnableVariable" atpObject,atpPrototype Communication among RunnableEntities resembles the approaches taken for the communication among software components. The explicit communication corresponds to DataReceivePoint/DataSendPoint. The implicit communication resembles DataReadAccess/DataWriteAccess mmt.qualifiedName="InterRunnableVariable.communicationApproach";pureMM.maxOccurs="1";pureMM.minOccurs="1" This represents the initial value of the InterRunnabelVariable. mmt.qualifiedName="InterRunnableVariable.initValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" Implement state message semantics for establishing communication among runnables of the same component. mmt.qualifiedName="InterRunnableVariable" atpObject,atpPrototype The internal behavior of an atomic software component describes the RTE relevant aspects of a component, i.e. the runnable entities and the events they respond to. mmt.qualifiedName="InternalBehavior" atpObject The component this behavior is defined for. mmt.qualifiedName="InternalBehavior.component";pureMM.maxOccurs="1";pureMM.minOccurs="1" This is a RTEEvent specified for the particular InternalBehavior. mmt.qualifiedName="event.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This specifies an ExclusiveArea for this InternalBehavior. The exclusiveArea is local to a software-component. mmt.qualifiedName="exclusiveArea.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This represents the initial value for the owned parameter. mmt.qualifiedName="InternalBehavior.initValue";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Implement state message semantics for establishing communication among RunnabelEntities of the same software-component. mmt.qualifiedName="interRunnableVariable.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" the perInstanceCalprm is aggregated in the internal behavior, since it is read only. Therefore not protection mechanisms are necessary regardless which runnable performs the access mmt.qualifiedName="perInstanceCalprm.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Defines a per-instance memory object needed by this software component. mmt.qualifiedName="perInstanceMemory.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Options for generating the signature of port-related calls from a runnable to the RTE and vice versa. mmt.qualifiedName="portAPIOption.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This is a RunnableEntity specified for the particular InternalBehavior. mmt.qualifiedName="runnable.behavior";pureMM.maxOccurs="-1";pureMM.minOccurs="1" the requirements on an AUTOSAR Service defined by this InternalBehavior mmt.qualifiedName="InternalBehavior.serviceNeeds";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Defines parameter(s) or characteristic value(s) shared between ComponentPrototypes of the same ComponentType. mmt.qualifiedName="sharedCalprm.InternalBehavior";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Indicate whether the corresponding software-component can be multiply instantiated on one ECU. In this case the attribute will result in an appropriate component API on programming language level (with or without instance handle). mmt.qualifiedName="InternalBehavior.supportsMultipleInstantiation";pureMM.maxOccurs="1";pureMM.minOccurs="1" The internal behavior of an atomic software component describes the RTE relevant aspects of a component, i.e. the runnable entities and the events they respond to. mmt.qualifiedName="InternalBehavior" atpObject mmt.qualifiedName="InternalConstrs" atpObject This element specifies the lower limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="InternalConstrs.lowerLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This element specifies the upper limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="InternalConstrs.upperLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This is one particular scale in which contributes to the data constraints. mmt.qualifiedName="InternalConstrs.scaleConstr";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" This element specifies the maximum slope that may be used in maps and curves. mmt.qualifiedName="InternalConstrs.maxGradient";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" Maximum difference that is permitted between two consecutive values if the constraint is applied to an axis. mmt.qualifiedName="InternalConstrs.maxDiff";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This element specifies the monotony characteristics of the current internal or physical limits. The following table shows the monotony characteristics which are to be filled through the corresponding values. If the element has no contents or if it is omitted, "no-monotony" is the default content. mmt.qualifiedName="InternalConstrs.monotony";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" mmt.qualifiedName="InternalConstrs" atpObject This port represents the drain of an interrupt request, i.e. the HWElement (in the majority of cases this will be a ProcessingUnit) to which this HWPort is attached is capable of accepting interrupt requests. mmt.qualifiedName="InterruptConsumeHWPort" atpObject Defines which hardware resource activate the interrupt. Typically any peripheral HW Element can activate an interrupt. E.g. CAN, SCI, SPI, Timer, ADC. Even simple digital I/O can activate an interrupt. Some microC have in this context dedicatated pins which act only as activation for interrupt. The connection from the according HW Element is made by the HW Port. mmt.qualifiedName="InterruptConsumeHWPort.activationSource";pureMM.maxOccurs="1";pureMM.minOccurs="0" Interrupt Latency: time passed from the occurrence of the interrupt request until the interrupt service routine is entered - HW: Register organisation; operations are necessary for context save. - SW: As SW can control the enabling/disabling of the interrupt SW determines a great part of the according time. - System: several constraints define the min/max times allowed for software to enable / disable interrupts. mmt.qualifiedName="InterruptConsumeHWPort.latency";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines if interrupts can be selected to be processed by the interrupt controller. mmt.qualifiedName="InterruptConsumeHWPort.maskable";pureMM.maxOccurs="1";pureMM.minOccurs="1" Some processing units offer different interrupt levels. It describes the priority in which the incoming interrupts are handled. mmt.qualifiedName="InterruptConsumeHWPort.priority";pureMM.maxOccurs="1";pureMM.minOccurs="1" This port represents the drain of an interrupt request, i.e. the HWElement (in the majority of cases this will be a ProcessingUnit) to which this HWPort is attached is capable of accepting interrupt requests. mmt.qualifiedName="InterruptConsumeHWPort" atpObject This port represents the source of an interrupt request, i.e. the HWElement to which this port is attached is capable of raising interrupt requests. mmt.qualifiedName="InterruptProduceHWPort" atpObject The IoHwAbstractionPort Annotation will only be used from a sensor- or an actuator component while interacting with the IoHwAbstraction layer mmt.qualifiedName="IoHwAbstractionServerAnnotation" atpObject In case of a SET operation, the age will be interpreted as Delay while in a GET operation (input) it specifies the Lifetime of the signal within the IoHwAbstraction Layer mmt.qualifiedName="IoHwAbstractionServerAnnotation.Age";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the corresponding ArgumentPrototype. The IoHwAbstractionServerAnnotation can be applied either to sender-receiver or to client-server communication. This association only applies in the latter case mmt.qualifiedName="IoHwAbstractionServerAnnotation.argumentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specifies the maximum value of the Range the ECU-Signal is supposed to have mmt.qualifiedName="IoHwAbstractionServerAnnotation.BswRangeMax";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the maximum value of the Range the ECU-Signal is supposed to have. mmt.qualifiedName="IoHwAbstractionServerAnnotation.BswRangeMin";pureMM.maxOccurs="1";pureMM.minOccurs="1" This value is determined by an appropriate combination of the range, the unit as well as the data-elements type, i.e. (BswRangeMax-BswRangeMin) / (2^datatypelength - 1) mmt.qualifiedName="IoHwAbstractionServerAnnotation.BswResolution";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the corresponding DataElementPrototype. The IoHwAbstractionServerAnnotation can be applied either to sender-receiver or to client-server communication. This association only applies in the former case mmt.qualifiedName="IoHwAbstractionServerAnnotation.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0" This is only applicable in SET operations. If it is enabled, the IoHwAbstraction layer will monitor the result of the operation and issue an diagnostic signal. This means especially, that an additional client-server port has to be created. Tools can use this information to cross-check whether for each data-element in a SET operation with FailureMonitoring enabled an additional port is created The referenced port monitors a failure in the to be monitored data-element of the IoHwAbstraction layer. The referenced port has to be another port of the same Actuator or Sensor Component. mmt.qualifiedName="IoHwAbstractionServerAnnotation.failureMonitoring";pureMM.maxOccurs="1";pureMM.minOccurs="0" This attribute is used to indicate what kind of filtering/debouncing has been put to the signal in the IoHwAbstraction layer. rawData means that no modification of the signal has been applied.This is the default value debounceData means that the signal is a mean value waitTimeData means that the signal is delivered by a GET operation after a certain amount of time mmt.qualifiedName="IoHwAbstractionServerAnnotation.FilteringDebouncing";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute indicates to the connected SensorActuatorSoftwareComponentType whether the DataElementPrototype can be used to generate pulse test sequences using the IoHwAbstraction layer mmt.qualifiedName="IoHwAbstractionServerAnnotation.PulseTest";pureMM.maxOccurs="1";pureMM.minOccurs="1" Calrifies whether a report RunnableEntity is supported, mmt.qualifiedName="supportsReportRunnable.IoHwAbstractionServerAnnotation";pureMM.maxOccurs="1";pureMM.minOccurs="0" Clarifies whether a wake-up RunnableEntity is supported. mmt.qualifiedName="supportsWakeUpRunnable.IoHwAbstractionServerAnnotation";pureMM.maxOccurs="1";pureMM.minOccurs="0" These are either electrical units like Volts (V) or time units like milliseconds (ms). The unit is set according to the ECU Input signal class which is either analogue or modulation mmt.qualifiedName="IoHwAbstractionServerAnnotation.Unit";pureMM.maxOccurs="1";pureMM.minOccurs="1" The IoHwAbstractionPort Annotation will only be used from a sensor- or an actuator component while interacting with the IoHwAbstraction layer mmt.qualifiedName="IoHwAbstractionServerAnnotation" atpObject ParagraphInOneParticularLanguage This is the text for a paragraph in one particular language. The language is denoted in the attribute l. mmt.qualifiedName="L1" atpMixedString,atpObject mmt.qualifiedName="L1.l";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" ParagraphInOneParticularLanguage This is the text for a paragraph in one particular language. The language is denoted in the attribute l. mmt.qualifiedName="L1" atpMixedString,atpObject MixedContentForPlainText in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L10" atpMixedString,atpObject mmt.qualifiedName="L10.l";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MixedContentForPlainText in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L10" atpMixedString,atpObject MixedContentForOverviewParagraph in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L2" atpMixedString,atpObject mmt.qualifiedName="L2.l";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MixedContentForOverviewParagraph in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L2" atpMixedString,atpObject MixedContentForUnitNames in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L3" atpMixedString,atpObject mmt.qualifiedName="L3.l";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MixedContentForUnitNames in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L3" atpMixedString,atpObject MixedContentForLongNames in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L4" atpMixedString,atpObject mmt.qualifiedName="L4.l";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MixedContentForLongNames in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L4" atpMixedString,atpObject MixedContentForVerbatim in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L5" atpMixedString,atpObject mmt.qualifiedName="L5.l";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MixedContentForVerbatim in one particular language. The language is dentoted in the attribute l. mmt.qualifiedName="L5" atpMixedString,atpObject mmt.qualifiedName="Limit" atpMixedString,atpObject This specifies the type of the interval. If the attribute is missing the interval shall be considered as "CLOSED". mmt.qualifiedName="Limit.intervalType";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="Limit" atpMixedString,atpObject LIN specific attributes mmt.qualifiedName="LinCluster" atpObject,atpStructureElement Schedule tables organize the Timings of the frames for LIN. mmt.qualifiedName="scheduleTable.LinCluster";pureMM.maxOccurs="-1";pureMM.minOccurs="0" LIN specific attributes mmt.qualifiedName="LinCluster" atpObject,atpStructureElement Each slave node shall publish a one bit signal, named response_error, to the master node in one of its transmitted unconditional frames. The response_error signal shall be set whenever a frame (except for event triggered frame responses) that is transmitted or received by the slave node contains an error in the frame response. The response_error signal shall be cleared when the unconditional frame containing the response_error signal is successfully transmitted. mmt.qualifiedName="LinErrorResponse" atpObject Reference to an unconditional frame that transmits the response error. The referenced LinFrameTriggering shall contain a reference to an unconditionalFrame. mmt.qualifiedName="LinErrorResponse.frameTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the position of the ResponseError bit in the frame. Each slave node shall publish one response error in one of its transmitted unconditional frames. mmt.qualifiedName="LinErrorResponse.responseErrorPosition";pureMM.maxOccurs="1";pureMM.minOccurs="1" Each slave node shall publish a one bit signal, named response_error, to the master node in one of its transmitted unconditional frames. The response_error signal shall be set whenever a frame (except for event triggered frame responses) that is transmitted or received by the slave node contains an error in the frame response. The response_error signal shall be cleared when the unconditional frame containing the response_error signal is successfully transmitted. mmt.qualifiedName="LinErrorResponse" atpObject Lin specific attributes to the FrameTriggering mmt.qualifiedName="LinFrameTriggering" atpObject Type of checksum that the frame is using. mmt.qualifiedName="LinFrameTriggering.checksumType";pureMM.maxOccurs="1";pureMM.minOccurs="1" To describe a frames identifier on the communication system, usualy with a fixed identifierValue. mmt.qualifiedName="LinFrameTriggering.identifier";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specification of a sending behaviour where the transmission order is predefined. mmt.qualifiedName="relativelyScheduledTiming.LinFrameTriggering";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Lin specific attributes to the FrameTriggering mmt.qualifiedName="LinFrameTriggering" atpObject Describing the properties of the refering ecu as a LIN master. mmt.qualifiedName="LinMaster" atpObject Time base is mandatory for the master. It is not used for slaves. LIN 2.0 Spec states: "The time_base value specifies the used time base in the master node to generate the maximum allowed frame transfer time." The time base shall be specified AUTOSAR conform in seconds. mmt.qualifiedName="LinMaster.timeBase";pureMM.maxOccurs="1";pureMM.minOccurs="0" timeBaseJitter is a mandatory attribute for the master and not used for slaves. LIN 2.0 Spec states: "The jitter value specifies the differences between the maximum and minimum delay from time base start point to the frame header sending start point (falling edge of BREAK signal)." The jitter shall be specified AUTOSAR conform in seconds. mmt.qualifiedName="LinMaster.timeBaseJitter";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describing the properties of the refering ecu as a LIN master. mmt.qualifiedName="LinMaster" atpObject The master task (in the master node) transmits frame headers based on a schedule table. The schedule table specifies the identifiers for each header and the interval between the start of a frame and the start of the following frame. mmt.qualifiedName="LinScheduleTable" atpObject Priority of the schedule table. The priority is used in the schedule table manager. The RUN_ONCE run mode schedules shall not have equal priority. Priority 0 is reserved for the NULL_SCHEDULE. Priority 255 is reserved for the RUN_CONTINUOUS run mode. mmt.qualifiedName="LinScheduleTable.priority";pureMM.maxOccurs="1";pureMM.minOccurs="1" The schedule table can be executed in two different modes. mmt.qualifiedName="LinScheduleTable.runMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" The master task (in the master node) transmits frame headers based on a schedule table. The schedule table specifies the identifiers for each header and the interval between the start of a frame and the start of the following frame. mmt.qualifiedName="LinScheduleTable" atpObject Describing the properties of the refering ecu as a LIN slave. mmt.qualifiedName="LinSlave" atpObject To distinguish LIN slaves that are used twice or more within the same cluster. mmt.qualifiedName="LinSlave.configuredNad";pureMM.maxOccurs="1";pureMM.minOccurs="1" Each slave node shall publish one response error in one of its transmitted unconditional frames. mmt.qualifiedName="linErrorResponse.LinSlave";pureMM.maxOccurs="1";pureMM.minOccurs="1" Version specifier for a communication protocol. mmt.qualifiedName="LinSlave.protocolVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" Describing the properties of the refering ecu as a LIN slave. mmt.qualifiedName="LinSlave" atpObject A LinTP channel represents an internal path for the transmission or reception of a Pdu via LinTp and describes the the sender and the receiver of this particular communication. The LinTp module routes a Pdu through the connection channel mmt.qualifiedName="LinTpChannel" atpObject Reference to an NPdu (Single Frame, First Frame or Consecutive Frame). The Single Frame network protocol data unit (SF N_PDU) shall be sent out by the sending network entity and can be received by one or multiple receiving network entities. The Single Frame (SF N_PDU) shall be sent out to transfer a service data unit that can be transferred via a single service request to the data link layer. This network protocol data unit shall be sent to transfer unsegmented messages. The First Frame network protocol data unit (FF N_PDU) identifies the first network protocol data unit (N_PDU) of a segmented message transmitted by a network sending entity and received by a receiving network entity. The Consecutive Frame network protocol data unit (CF N_PDU) transfers segments (N_Data) of the service data unit message data (<MessageData>). All network protocol data units (N_PDUs) transmitted by the sending entity after the First Frame network protocol data unit (FF N_PDU) shall be encoded as Consecutive Frames network protocol data units (CF N_PDUs). mmt.qualifiedName="LinTpChannel.dataPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Configures if TP Frames of not requested LIN-Slaves are dropped or not. mmt.qualifiedName="LinTpChannel.dropNotRequestedNad";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the Flow Control NPdu. The Flow Control network protocol data unit (FC N_PDU) is identified by the Flow Control protocol control information (FC N_PCI). The Flow Control network protocol data unit (FC N_PDU) instructs a sending network entity to start, stop or resume transmission of CF N_PDUs. The Flow Control network protocol data unit shall be sent by the receiving network layer entity to the sending network layer entity, when ready to receive more data, after correct reception of: a) First Frame network protocol data unit (FF N_PDU) b) the last Consecutive Frame network protocol data unit (CF N_PDU) of a block of Consecutive Frames (CF N_PDU) if further Consecutive Frame network protocol data unit (CF N_PDU) need(s) to be sent. mmt.qualifiedName="LinTpChannel.flowControl";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the IPdu that is segmented by the Transport Protocol. To support the low-level routing of NPdu's the NPdu is a specialization of an IPdu. More details can be found in the NPdu class description. Nevertheless the LinTpChannel must not reference a NPdu with this linTpNSdu reference. mmt.qualifiedName="LinTpChannel.linTpNSdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" TP address for 1:n connections. mmt.qualifiedName="LinTpChannel.multicast";pureMM.maxOccurs="1";pureMM.minOccurs="0" The source of the TP connection. mmt.qualifiedName="LinTpChannel.source";pureMM.maxOccurs="1";pureMM.minOccurs="1" The target of the TP connection. mmt.qualifiedName="LinTpChannel.target";pureMM.maxOccurs="-1";pureMM.minOccurs="1" A LinTP channel represents an internal path for the transmission or reception of a Pdu via LinTp and describes the the sender and the receiver of this particular communication. The LinTp module routes a Pdu through the connection channel mmt.qualifiedName="LinTpChannel" atpObject TP Node (Sender or Receiver) provides the TP Address and the connection to the Topology description. mmt.qualifiedName="LinTpNode" atpObject Specifies the linker attributes used to decribe how the linker shall be invoked. mmt.qualifiedName="Linker" atpObject Linker name. mmt.qualifiedName="Linker.name";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the linker options. mmt.qualifiedName="Linker.options";pureMM.maxOccurs="1";pureMM.minOccurs="1" Vendor of linker. mmt.qualifiedName="Linker.vendor";pureMM.maxOccurs="1";pureMM.minOccurs="1" Exact version of linker executable. mmt.qualifiedName="Linker.version";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the linker attributes used to decribe how the linker shall be invoked. mmt.qualifiedName="Linker" atpObject Configuration parameter type for Linker Symbol Names like those used to specify memory locations of variables and constants. mmt.qualifiedName="LinkerSymbolDef" atpObject Representing a configuration value of definition type LinkerSymbolDef mmt.qualifiedName="LinkerSymbolValue" atpObject This is the specialization for local parameters. mmt.qualifiedName="LocalParameterInitValueAssignment" atpObject A MPU provides means where the memory access within a defined program flow of a PU is controlled. In case of a failure an exception routine e.g. interrupt is activated. A MPU is implemented as an independent hardware block in a device separate to the processing unit. A MPU does not perform any data manipulation, only in case of an error a change in the processor control flow is forced. The number of individual checked memory ranges is limited to the registers available for specifying the memory ranges. One individual memory range is in the following referenced as MPU Channel. In most cases the MPU consists of a set of registers, which do range checking of the addresses asserted by the program on the address bus as well as the access type to the according address. The checking of the address ranges is also coupled to the address range of the program, which runs under the control of the MPU. The MPU also can be coupled with one of the different processing elements of a device like the PU itself, a DMA or a Coprocessor. In order to have a broad usage of a MPU a specification of filter values is often allowed, so very user specific selection methods are possible. Typical use case for a MPU: A 3rd party software routine is allowed only to access a defined memory-area. Any access outside the defined memory area will be denied and control will be transferred to the supervising operating system. A error handling routine will be started. mmt.qualifiedName="MPU" atpObject Defines the number of individual MPU channels are available. mmt.qualifiedName="MPU.channelCount";pureMM.maxOccurs="1";pureMM.minOccurs="1" Describes which Memory Mapped HW Ports are obserable by this MPU. The actual configuration will be done by SW. mmt.qualifiedName="MPU.protectedMemoryHWPort";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Defines the interrupts this MPU can raise to indicate the violation of memory access. mmt.qualifiedName="raisedInterrupt.MPU";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A MPU provides means where the memory access within a defined program flow of a PU is controlled. In case of a failure an exception routine e.g. interrupt is activated. A MPU is implemented as an independent hardware block in a device separate to the processing unit. A MPU does not perform any data manipulation, only in case of an error a change in the processor control flow is forced. The number of individual checked memory ranges is limited to the registers available for specifying the memory ranges. One individual memory range is in the following referenced as MPU Channel. In most cases the MPU consists of a set of registers, which do range checking of the addresses asserted by the program on the address bus as well as the access type to the according address. The checking of the address ranges is also coupled to the address range of the program, which runs under the control of the MPU. The MPU also can be coupled with one of the different processing elements of a device like the PU itself, a DMA or a Coprocessor. In order to have a broad usage of a MPU a specification of filter values is often allowed, so very user specific selection methods are possible. Typical use case for a MPU: A 3rd party software routine is allowed only to access a defined memory-area. Any access outside the defined memory area will be denied and control will be transferred to the supervising operating system. A error handling routine will be started. mmt.qualifiedName="MPU" atpObject Pass messages where the masked value has changed. (new_value&mask) !=(old_value&mask) new_value: current value of the message old_value: last value of the message (initialised with the initial value of the message, updated with new_value if the new message value is not filtered out) mmt.qualifiedName="MaskedNewDiffersMaskedOld" atpObject mask for old and new value mmt.qualifiedName="MaskedNewDiffersMaskedOld.mask";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pass messages where the masked value has changed. (new_value&mask) !=(old_value&mask) new_value: current value of the message old_value: last value of the message (initialised with the initial value of the message, updated with new_value if the new message value is not filtered out) mmt.qualifiedName="MaskedNewDiffersMaskedOld" atpObject Pass messages whose masked value is not equal to a specific value x (new_value&mask) != x new_value: current value of the message mmt.qualifiedName="MaskedNewDiffersX" atpObject mask for the new Value mmt.qualifiedName="MaskedNewDiffersX.mask";pureMM.maxOccurs="1";pureMM.minOccurs="1" Value to compare with mmt.qualifiedName="MaskedNewDiffersX.x";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pass messages whose masked value is not equal to a specific value x (new_value&mask) != x new_value: current value of the message mmt.qualifiedName="MaskedNewDiffersX" atpObject Pass messages whose masked value is equal to a specific value x (new_value&mask) == x new_value: current value of the message mmt.qualifiedName="MaskedNewEqualsX" atpObject mask for the new Value mmt.qualifiedName="MaskedNewEqualsX.mask";pureMM.maxOccurs="1";pureMM.minOccurs="1" Value to compare with mmt.qualifiedName="MaskedNewEqualsX.x";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pass messages whose masked value is equal to a specific value x (new_value&mask) == x new_value: current value of the message mmt.qualifiedName="MaskedNewEqualsX" atpObject Specifies the ExecutionTime which has been gathered using measurement means. mmt.qualifiedName="MeasuredExecutionTime" atpObject Average MeasuredExecutionTime. mmt.qualifiedName="MeasuredExecutionTime.averageExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum MeasuredExecutionTime. mmt.qualifiedName="MeasuredExecutionTime.maximalExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minumum MeasuredExecutionTime. mmt.qualifiedName="MeasuredExecutionTime.minimalExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the ExecutionTime which has been gathered using measurement means. mmt.qualifiedName="MeasuredExecutionTime" atpObject The heap usage has been measured. mmt.qualifiedName="MeasuredHeapUsage" atpObject The average heap usage measured. mmt.qualifiedName="MeasuredHeapUsage.averageMemoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" The maximum heap usage measured. mmt.qualifiedName="MeasuredHeapUsage.maximumMemoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" The minimum heap usage measured. mmt.qualifiedName="MeasuredHeapUsage.minimumMemoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="0" Description of the test pattern used to aquire the measured values. mmt.qualifiedName="MeasuredHeapUsage.testPattern";pureMM.maxOccurs="1";pureMM.minOccurs="0" The heap usage has been measured. mmt.qualifiedName="MeasuredHeapUsage" atpObject The stack usage has been measured. mmt.qualifiedName="MeasuredStackUsage" atpObject The average stack usage measured. mmt.qualifiedName="MeasuredStackUsage.averageMemoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" The maximum stack usage measured. mmt.qualifiedName="MeasuredStackUsage.maximumMemoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" The minimum stack usage measured. mmt.qualifiedName="MeasuredStackUsage.minimumMemoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="0" Description of the test pattern used to aquire the measured values. mmt.qualifiedName="MeasuredStackUsage.testPattern";pureMM.maxOccurs="1";pureMM.minOccurs="0" The stack usage has been measured. mmt.qualifiedName="MeasuredStackUsage" atpObject Describes the different possible kinds of access to the memory and the time these access takes. mmt.qualifiedName="MemoryAccess" atpObject The element access type describes the different possible kinds of access to the memory. mmt.qualifiedName="MemoryAccess.accessType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Access time is the timing characteristic for each access type. Access time at the Memory Mapped HW Port is only theoretical. The actual Access time is given in the Memory Mapped HW Connection. mmt.qualifiedName="time.MemoryAccess";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the different possible kinds of access to the memory and the time these access takes. mmt.qualifiedName="MemoryAccess" atpObject This connection is used to connect Memory HWPort on the same hierarchical level (inside one HW Container). mmt.qualifiedName="MemoryMappedAssemblyHWConnection" atpObject Defines the base address of the memory within the ECU template. The same base address might be defined multiple times according to the access type and the architecture. A base address is uniquely bound to a defined memory segment. mmt.qualifiedName="MemoryMappedAssemblyHWConnection.baseAddress";pureMM.maxOccurs="1";pureMM.minOccurs="0" When a PU stores data in a memory the ordering of the bytes can be done in two different ways. This storing scheme is normally fixed in the PU when more than one byte is stored in the memory. When the least significant byte is stored at the lowest address this architecture is called "mostSignificantByteLast" (aka little endian) and when the most significant byte is stored at the lowest address this is called "mostSignificantByteFirst" (aka big endian). Some CPU architectures like ARM and PowerPC can be configured to handle both little and big endian. This is called bi-endian. ByteOrder is very important when you communicate between different PUs or ECUs. mmt.qualifiedName="MemoryMappedAssemblyHWConnection.byteOrder";pureMM.maxOccurs="1";pureMM.minOccurs="0" A memory segment may be cacheable. This has to be defined in the description of the segment connection. mmt.qualifiedName="MemoryMappedAssemblyHWConnection.cachable";pureMM.maxOccurs="1";pureMM.minOccurs="0" Access time is the timing characteristic for each access type. Access time at the Memory Mapped HW Port is only theoretical. The actual Access time is given in the Memory Mapped HW Connection. mmt.qualifiedName="hwConnectionAccess.MemoryMappedAssemblyHWConnection";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The segment usage is defined in the linker memory map. Usually it is fixed within an operation mode but different operations modes have different memory usage. The element segment usage contains the following attributes. - Data: The attribute data is used for all kind of data: constant, variable, calibration, system initialisation, system configuration, etc. - Code: The attribute code is used for the program code itself. - Stack: Memory usable for a system or software stack is in some cases only available on limited number of segments within a PU. - Boot: The boot memory is used to store program and data for the start up or test of an ECU. Within the boot program the basic ECU initialisation is performed. Furthermore some system maintenance programs, like the set-up for flash programming or loading of data via communication interface, can be part of the boot program. Boot memory is in general not a subject of AUTOSAR SW. -- Boot sector: Boot sector is the location in memory, preferable Flash or ROM, where the boot program is stored. The location of the boot sector might be dependant on the PU architecture as reset and interrupt vectors must be accessible during boot. The boot sector should be separated from other user accessible Flash or implemented as ROM. In Flash the boot sector should have the appropriate array size, some few kilobyte and provide protection mechanism against unintended erasure or system manipulation. A system may have different boot sectors, one accessible only for testing the PU during the manufacturing and configuration of the PU, in factory test mode or some initial program mode, and a user boot mode. -- Mapping of boot sector: Mapping of the boot sector is useful to enhance the boot sequence and the release of the used resources during the boot phase at the later user mode, e.g. the use of reset vector and interrupt vector can be improved. mmt.qualifiedName="MemoryMappedAssemblyHWConnection.segmentUsage";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This connection is used to connect Memory HWPort on the same hierarchical level (inside one HW Container). mmt.qualifiedName="MemoryMappedAssemblyHWConnection" atpObject This connection is used to delegate a Memory HW Port to the outside of a HW Container. Typically this will used internally of a micro-controller. mmt.qualifiedName="MemoryMappedDelegationHWConnection" atpObject mmt.qualifiedName="MemoryMappedHWPort" atpObject The element defines the number of bits that can be transferred from the PU to the memory device or vice versa. The width of data bus are important characteristics. All technical characteristics of the memory are covered by the access time. Unit: Bit mmt.qualifiedName="MemoryMappedHWPort.dataInterfaceWidth";pureMM.maxOccurs="1";pureMM.minOccurs="1" the type of port mmt.qualifiedName="MemoryMappedHWPort.hwPortType";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="MemoryMappedHWPort" atpObject The MemorySection provides description of the Memory Sections used in the Implementation. mmt.qualifiedName="MemorySection" atpObject The alignment (typically 1, 2, 4,...) mmt.qualifiedName="MemorySection.alignment";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute introduces the ability to specify further intended properties of this MemorySection. The following value is standardized (to be used for code sections only): * INLINE - The code section is declared with the compiler abstraction macro INLINE. The expansion of INLINE depends on the compiler specific implementation of the macro. Depending on this, the code section either corresponds to an actual section in memory or is put into the section of the caller. See AUTOSAR_SWS_CompilerAbstraction for more details. mmt.qualifiedName="MemorySection.option";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This is the name of the section in the Implementation. mmt.qualifiedName="MemorySection.sectionName";pureMM.maxOccurs="1";pureMM.minOccurs="1" Memory section type of the described MemorySection. mmt.qualifiedName="MemorySection.sectionType";pureMM.maxOccurs="1";pureMM.minOccurs="1" The size in bytes of the section. mmt.qualifiedName="MemorySection.size";pureMM.maxOccurs="1";pureMM.minOccurs="1" This assocation indicates all objects (e.g. calibration parameters, data element prototypes) being assigned to this SwAddrMethod shall be placed in this memory Section. mmt.qualifiedName="MemorySection.swAddrMethod";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The MemorySection provides description of the Memory Sections used in the Implementation. mmt.qualifiedName="MemorySection" atpObject Specifes in which hardware ProvidedMemorySegment the softwareMemorySection is located. mmt.qualifiedName="MemorySectionLocation" atpObject Reference to the hardware ProvidedMemorySegment. mmt.qualifiedName="MemorySectionLocation.providedMemory";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the MemorySection which is mapped on a certain hardware memory segment. mmt.qualifiedName="MemorySectionLocation.softwareMemorySection";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifes in which hardware ProvidedMemorySegment the softwareMemorySection is located. mmt.qualifiedName="MemorySectionLocation" atpObject MixedContentForParagraph This mainly represents the text model of a full blown paragraph within a documentation. mmt.qualifiedName="MixedContent1" atpMixedString,atpObject Use <xfile> , to reference an external file. mmt.qualifiedName="MixedContent1.xfile";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="140" MultiLanguageParagraph This is the content model of a multilinugal paragraph in a documentation. mmt.qualifiedName="MlData1" atpObject mmt.qualifiedName="MlData1.helpEntry";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="MlData1.keepWithPrevious";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" MultiLanguageParagraph This is the content model of a multilinugal paragraph in a documentation. mmt.qualifiedName="MlData1" atpObject MultiLanguagePlainText mmt.qualifiedName="MlData10" atpObject MultiLanguageOverviewParagraph This is the content of a multilingual paragraph in an overview item. mmt.qualifiedName="MlData2" atpObject MultiLanguageUnitNames mmt.qualifiedName="MlData3" atpObject MultiLanguageUnitNameVerbatim mmt.qualifiedName="MlData3p" atpObject mmt.qualifiedName="MlData3p.xml:space";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MultiLanguageUnitNameVerbatim mmt.qualifiedName="MlData3p" atpObject MultilanguageLongName mmt.qualifiedName="MlData4" atpObject MultiLanguageVerbatim mmt.qualifiedName="MlData5" atpObject mmt.qualifiedName="MlData5.allowBreak";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="MlData5.float";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="MlData5.helpEntry";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="MlData5.keepWithPrevious";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="MlData5.pgwide";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="MlData5.xml:space";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" MultiLanguageVerbatim mmt.qualifiedName="MlData5" atpObject MultilanguageDataModelForParagraph mmt.qualifiedName="MlDataModel1" atpObject mmt.qualifiedName="MlDataModel1.l1";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" MultilanguageDataModelForPlainText mmt.qualifiedName="MlDataModel10" atpObject mmt.qualifiedName="MlDataModel10.l10";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" MultilanguageDataModelForOverviewParagraph mmt.qualifiedName="MlDataModel2" atpObject mmt.qualifiedName="MlDataModel2.l2";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" MultilanguageDataModelForUnitNames mmt.qualifiedName="MlDataModel3" atpObject mmt.qualifiedName="MlDataModel3.l3";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" MultilanguageDataModelForLongNames mmt.qualifiedName="MlDataModel4" atpObject mmt.qualifiedName="MlDataModel4.l4";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" MultilanguageDataModelForVerbatim mmt.qualifiedName="MlDataModel5" atpObject mmt.qualifiedName="MlDataModel5.l5";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="MlGraphic" atpObject mmt.qualifiedName="MlGraphic.L";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="MlGraphic" atpObject Declaration of one Mode. The name and semantics of a special mode is not defined in the metamodel. mmt.qualifiedName="ModeDeclaration" atpObject,atpStructureElement A collection of Mode Declarations. mmt.qualifiedName="ModeDeclarationGroup" atpObject,atpType The initial mode of the ModeDeclarationGroup. This mode is active before any mode switches occured. mmt.qualifiedName="ModeDeclarationGroup.initialMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" The ModeDeclarations collected in this ModeDeclarationGroup. mmt.qualifiedName="modeDeclaration.ModeDeclarationGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="1" A collection of Mode Declarations. mmt.qualifiedName="ModeDeclarationGroup" atpObject,atpType The ModeDeclarationGroupPrototype specifies the set of Modes (ModeDeclarationGroup) that is supported by a ComponentType. mmt.qualifiedName="ModeDeclarationGroupPrototype" atpObject,atpPrototype The "collection of ModeDeclarations" ( = ModeDeclarationGroup) supported by a component mmt.qualifiedName="ModeDeclarationGroupPrototype.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType The ModeDeclarationGroupPrototype specifies the set of Modes (ModeDeclarationGroup) that is supported by a ComponentType. mmt.qualifiedName="ModeDeclarationGroupPrototype" atpObject,atpPrototype Collection of references to the Modes that disable the RTEEvent mmt.qualifiedName="ModeDisablingDependency" atpObject Reference to the Modes that disable the Runnable Entity. mmt.qualifiedName="dependentOnMode.ModeDisablingDependency";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Collection of references to the Modes that disable the RTEEvent mmt.qualifiedName="ModeDisablingDependency" atpObject mmt.qualifiedName="ModeDisablingDependency_dependentOnMode" atpObject,instanceRef mmt.qualifiedName="ModeDisablingDependency_dependentOnMode.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ModeDisablingDependency_dependentOnMode.modeDeclarationGroupPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ModeDisablingDependency_dependentOnMode.modeDeclaration";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="ModeDisablingDependency_dependentOnMode" atpObject,instanceRef Communication attributes for both sender /server port (P-Port and sender-receiver interface). mmt.qualifiedName="ModeSwitchComSpec" atpObject Mode Declaration Group (of the same Port Interface) to which these communication attributes apply. mmt.qualifiedName="ModeSwitchComSpec.modeGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1" This represents the ModeSwitchedAckrequest owned by the ModeSwitchComSoec. mmt.qualifiedName="modeSwitchedAck.ModeSwitchComSpec";pureMM.maxOccurs="1";pureMM.minOccurs="0" Length of call queue on the server side. The queue is implemented by the RTE. The value must be greater or equal to 0. Setting the value of queueLength to 0 implies non-queued communication. mmt.qualifiedName="ModeSwitchComSpec.queueLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" Communication attributes for both sender /server port (P-Port and sender-receiver interface). mmt.qualifiedName="ModeSwitchComSpec" atpObject This event is listening to mode changes coming from the StateManager. mmt.qualifiedName="ModeSwitchEvent" atpObject Specifies if the event is activated on entering or exiting the referenced Mode. mmt.qualifiedName="ModeSwitchEvent.activation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the Mode that initiates the Mode Switch Event. mmt.qualifiedName="mode.ModeSwitchEvent";pureMM.maxOccurs="1";pureMM.minOccurs="1" This event is listening to mode changes coming from the StateManager. mmt.qualifiedName="ModeSwitchEvent" atpObject mmt.qualifiedName="ModeSwitchEvent_mode" atpObject,instanceRef mmt.qualifiedName="ModeSwitchEvent_mode.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ModeSwitchEvent_mode.modeDeclarationGroupPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ModeSwitchEvent_mode.modeDeclaration";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="ModeSwitchEvent_mode" atpObject,instanceRef A ModeSwitchPoint is required by a RunnableEntity owned a Mode Manager. Its semantics implies the ability to initiate a mode switch. mmt.qualifiedName="ModeSwitchPoint" atpObject The mode group that is received by this runnable. mmt.qualifiedName="modeGroup.ModeSwitchPoint";pureMM.maxOccurs="1";pureMM.minOccurs="1" A ModeSwitchPoint is required by a RunnableEntity owned a Mode Manager. Its semantics implies the ability to initiate a mode switch. mmt.qualifiedName="ModeSwitchPoint" atpObject mmt.qualifiedName="ModeSwitchPoint_modeGroup" atpObject,instanceRef mmt.qualifiedName="ModeSwitchPoint_modeGroup.pPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ModeSwitchPoint_modeGroup.modeDeclarationGroupPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="ModeSwitchPoint_modeGroup" atpObject,instanceRef The event is raised when the referenced mode have been received or an error occurs. mmt.qualifiedName="ModeSwitchedAckEvent" atpObject Mode switch point that triggers the event. mmt.qualifiedName="event.eventSource";pureMM.maxOccurs="1";pureMM.minOccurs="1" The event is raised when the referenced mode have been received or an error occurs. mmt.qualifiedName="ModeSwitchedAckEvent" atpObject Requests acknowledgements that a mode switch has been proceeded successfully mmt.qualifiedName="ModeSwitchedAckRequest" atpObject Number of seconds before an error is reported or in case of allowed redundancy, the value is sent again. mmt.qualifiedName="ModeSwitchedAckRequest.timeout";pureMM.maxOccurs="1";pureMM.minOccurs="1" Requests acknowledgements that a mode switch has been proceeded successfully mmt.qualifiedName="ModeSwitchedAckRequest" atpObject Use <modification> to record what has changed in a document in comparison to its predecessor. mmt.qualifiedName="Modification" atpObject <change> is used to enter a modification text for a <modification> element. The element has the same contents and features as a normal Pararagraf element <p>. mmt.qualifiedName="Modification.change";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" Use <reason> to cite the reason for changes to the document version. mmt.qualifiedName="Modification.reason";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Use <modification> to record what has changed in a document in comparison to its predecessor. mmt.qualifiedName="Modification" atpObject Head of the configuration of one Module. A Module can be a BSW module as well as the RTE and ECU Infrastructure. As part of tthe BSW module description, the ModuleConfiguration has two different roles: The recommendedConfiguration contains parameter values recommended by the BSW module vendor. The preconfiguredConfiguration contains values for those parameters which are fixed by the implementation and cannot be changed. These two ModuleConfigurations are used when the base ModuleConfiguration (as part of the base ECU configuration) is created to fill parameters with initial values. mmt.qualifiedName="ModuleConfiguration" atpObject Reference to the definition of this ModuleConfiguration. Typically, this is a vendor specific module configuration. mmt.qualifiedName="ModuleConfiguration.definition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="-10" Specifies the ConfigurationVariant used for this ModuleConfiguration. mmt.qualifiedName="ModuleConfiguration.implementationConfigVariant";pureMM.maxOccurs="1";pureMM.minOccurs="1" Referencing the BSW module description, which this ModuleConfiguration is configuring. This is optional because the ModuleConfiguration is also used to configure the ECU infrastructure (memory map) or Application SW-Cs. mmt.qualifiedName="ModuleConfiguration.moduleDescription";pureMM.maxOccurs="1";pureMM.minOccurs="0" Aggregates all containers that belong to this module configuration. mmt.qualifiedName="container.ModuleConfiguration";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.sequenceOffset="10" atpSplitable Head of the configuration of one Module. A Module can be a BSW module as well as the RTE and ECU Infrastructure. As part of tthe BSW module description, the ModuleConfiguration has two different roles: The recommendedConfiguration contains parameter values recommended by the BSW module vendor. The preconfiguredConfiguration contains values for those parameters which are fixed by the implementation and cannot be changed. These two ModuleConfigurations are used when the base ModuleConfiguration (as part of the base ECU configuration) is created to fill parameters with initial values. mmt.qualifiedName="ModuleConfiguration" atpObject Used as the top-level element for configuration definition for Software Modules, including BSW and RTE as well as ECU Infrastructure. mmt.qualifiedName="ModuleDef" atpObject Optional reference from the Vendor Specific Module Definition to the Standardized Module Definition it refines. mmt.qualifiedName="ModuleDef.refinedModuleDef";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specifies which ConfigurationVariants are supported by this software module. mmt.qualifiedName="ModuleDef.supportedConfigVariant";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Aggregates the top-level container definitions of this specific module definition. mmt.qualifiedName="container.ModuleDef";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.sequenceOffset="11" Used as the top-level element for configuration definition for Software Modules, including BSW and RTE as well as ECU Infrastructure. mmt.qualifiedName="ModuleDef" atpObject A MultiplexedPdu (i.e. NOT a COM I-PDU) contains a DynamicPart, an optional StaticPart and a selectorField. In case of multiplexing this IPdu is routed between the Pdu Multiplexer and the Interface Layer. A multiplexer is used to define variable parts within an IPdu that may carry different signals. The receivers of such a IPdu can determine which signalPdus are transmitted by evaluating the selector field, which carries a unique selector code for each sub-part. mmt.qualifiedName="MultiplexedIPdu" atpObject According to the value of the selector field some parts of the IPdu have a different layout. mmt.qualifiedName="dynamicPart.MultiplexedIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute defines the order of the bytes of the selectorField and the packing into the MultiplexedIPdu. The byte ordering "Little Endian" (MostSignificantByteLast) and "Big Endian" (MostSignificantByteFirst) can be selected. A mix between Little Endian and Big Endian within a MultiplexedIPdu (staticPart, dynamicPart, selectorField) is not allowed. mmt.qualifiedName="MultiplexedIPdu.selectorFieldByteOrder";pureMM.maxOccurs="1";pureMM.minOccurs="1" The size in bits of the selector field shall be configurable in a range of one bit and eight bits. mmt.qualifiedName="MultiplexedIPdu.selectorFieldLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" This parameter is necessary to describe the position of the selector field within the IPdu. Note that the absolute position of the selectorField in the MultiplexedIPdu is determined by the definition of the selectorFieldByteOrder attribute of the Multiplexed Pdu. If Big Endian is specified, the start position indicates the bit position of the most significant bit in the IPdu. If Little Endian is specified, the start position indicates the bit position of the least significant bit in the IPdu. mmt.qualifiedName="MultiplexedIPdu.selectorFieldStartPosition";pureMM.maxOccurs="1";pureMM.minOccurs="1" The static part of the multiplexed IPdu is the same regardless of the selector field. The static part is optional. mmt.qualifiedName="staticPart.MultiplexedIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="0" IPduM can be configured to send a transmission request for the new multiplexed I-PDU to the PDU-Router because of the trigger conditions/ modes that are described in the TriggerMode enumeration. mmt.qualifiedName="MultiplexedIPdu.triggerMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" A MultiplexedPdu (i.e. NOT a COM I-PDU) contains a DynamicPart, an optional StaticPart and a selectorField. In case of multiplexing this IPdu is routed between the Pdu Multiplexer and the Interface Layer. A multiplexer is used to define variable parts within an IPdu that may carry different signals. The receivers of such a IPdu can determine which signalPdus are transmitted by evaluating the selector field, which carries a unique selector code for each sub-part. mmt.qualifiedName="MultiplexedIPdu" atpObject The StaticPart and the DynamicPart have common properties. Both can be separated in multiple segments within the multiplexed PDU. mmt.qualifiedName="MultiplexedPart" atpObject The StaticPart and the DynamicPart can be separated in multiple segments within the multiplexed PDU. Therefore the StaticPart and the DynamicPart can contain multiple SegmentPositions. mmt.qualifiedName="segmentPosition.MultiplexedPart";pureMM.maxOccurs="-1";pureMM.minOccurs="1" This is a PDU of the Transport Layer. The main purpose of the TP Layer is to segment and reassemble I-PDUs. In case of a Pdu Gateway when the source and the target network are of the same kind (e.g. Can-to-Can routing) it is possible to optimize the routing. The incoming NPdu can be directly forwarded to the PduR and then be sent on the outbound bus without any (resource consuming) TP module involvement. To support this use case the NPdu is located under the IPdu. But in the AUTOSAR Layered Architecture the NPdu is not a specialization of an IPdu. mmt.qualifiedName="NPdu" atpObject The filter removes all messages. mmt.qualifiedName="Never" atpObject Pass a message if its value is outside a predefined boundary. (min > new_value) OR (new_value > max) mmt.qualifiedName="NewIsOutside" atpObject Value to specify the upper boundary mmt.qualifiedName="NewIsOutside.max";pureMM.maxOccurs="1";pureMM.minOccurs="1" Value to specify the lower boundary mmt.qualifiedName="NewIsOutside.min";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pass a message if its value is outside a predefined boundary. (min > new_value) OR (new_value > max) mmt.qualifiedName="NewIsOutside" atpObject Pass a message if its value is within a predefined boundary. min <= new_value <= max mmt.qualifiedName="NewIsWithin" atpObject Value to specify the upper boundary mmt.qualifiedName="NewIsWithin.max";pureMM.maxOccurs="1";pureMM.minOccurs="1" Value to specify the lower boundary mmt.qualifiedName="NewIsWithin.min";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pass a message if its value is within a predefined boundary. min <= new_value <= max mmt.qualifiedName="NewIsWithin" atpObject Network Management I-Pdu mmt.qualifiedName="NmPdu" atpObject This optional aggregation is used to describe NmUserData that is transmitted in the NmPdu. mmt.qualifiedName="iSignalToIPduMapping.NmPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The size of the NmPDU in bits. mmt.qualifiedName="NmPdu.length";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the position of the control bit vector within the NM PDU (Bitpositon). mmt.qualifiedName="NmPdu.nmCbvPosition";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the bitposition of the source node identifier within the NM PDU. mmt.qualifiedName="NmPdu.nmNidPosition";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the length in Bytes of the user data contained in the NM PDU. mmt.qualifiedName="NmPdu.nmUserDataLength";pureMM.maxOccurs="1";pureMM.minOccurs="0" Network Management I-Pdu mmt.qualifiedName="NmPdu" atpObject Specifies the abstract needs on the configuration of a single Nv block. mmt.qualifiedName="NvBlockNeeds" atpObject number of data sets to be provided by the NVRAM manager for this block mmt.qualifiedName="NvBlockNeeds.nDataSets";pureMM.maxOccurs="1";pureMM.minOccurs="1" true: data of this block are write protected for normal operation (but protection can be disabled) false: no restriction mmt.qualifiedName="NvBlockNeeds.readonly";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reliability against data loss on the non-volatile medium. mmt.qualifiedName="NvBlockNeeds.reliability";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines whether an Nv block shall be treated resistant to configuration changes (true) or not (false). For details how to handle initialization in the latter case, refer to the NVRAM specification. mmt.qualifiedName="NvBlockNeeds.resistantToChangedSw";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines whether the associated RAM mirror block shall be implictly restored during startup by the basic SW or not. Only relevant if a RAM mirror block (PerInstanceMemory) is associated with this port. mmt.qualifiedName="NvBlockNeeds.restoreAtStart";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines write protection after first write: true: This block is prevented from being changed/erased or being replaced with the default ROM data after first initialization by the SWC. false: No such restriction. mmt.qualifiedName="NvBlockNeeds.writeOnlyOnce";pureMM.maxOccurs="1";pureMM.minOccurs="1" Provides the amount of updates to this block from the application point of view. It has to be provided in "number of write access per year". mmt.qualifiedName="NvBlockNeeds.writingFrequency";pureMM.maxOccurs="1";pureMM.minOccurs="1" Requires the priority of writing this block in case of concurrent requests to write other blocks. mmt.qualifiedName="NvBlockNeeds.writingPriority";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs on the configuration of a single Nv block. mmt.qualifiedName="NvBlockNeeds" atpObject Specifies the abstract needs of a compoment or module on the configuration of OBD Service 08 (request control of on-board system) in relation to a particular test-Identifier (TID) supported by this component or module. mmt.qualifiedName="ObdControlServiceNeeds" atpObject Test Identifier (TID) according to ISO 15031-5. mmt.qualifiedName="ObdControlServiceNeeds.testId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs of a compoment or module on the configuration of OBD Service 08 (request control of on-board system) in relation to a particular test-Identifier (TID) supported by this component or module. mmt.qualifiedName="ObdControlServiceNeeds" atpObject Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a given InfoType (OBD Service 09), which is supported by this component or module. mmt.qualifiedName="ObdInfoServiceNeeds" atpObject Length of date (in bytes) provided for this InfoType. mmt.qualifiedName="ObdInfoServiceNeeds.dataLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" The InfoType according to ISO 15031-5 mmt.qualifiedName="ObdInfoServiceNeeds.infoType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a given InfoType (OBD Service 09), which is supported by this component or module. mmt.qualifiedName="ObdInfoServiceNeeds" atpObject Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a particular on-board monitoring test supported by this component or module. (OBD Service 06). mmt.qualifiedName="ObdMonitorServiceNeeds" atpObject On-board monitor ID according to ISO 15031-5. mmt.qualifiedName="ObdMonitorServiceNeeds.onBoardMonitorId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Test Identifier (TID) according to ISO 15031-5. mmt.qualifiedName="ObdMonitorServiceNeeds.testId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Unit and scaling ID according to ISO 15031-5. mmt.qualifiedName="ObdMonitorServiceNeeds.unitAndScalingId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a particular on-board monitoring test supported by this component or module. (OBD Service 06). mmt.qualifiedName="ObdMonitorServiceNeeds" atpObject Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a particular PID (parameter identifier), which is supported by this component or module. mmt.qualifiedName="ObdPidServiceNeeds" atpObject Length of data (in bytes) provided for this particular PID. mmt.qualifiedName="ObdPidServiceNeeds.dataLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" Standardized parameter identifier (PID) according to the OBD standard specified in attribute "standard". mmt.qualifiedName="ObdPidServiceNeeds.parameterId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Annotates the standard according to which the PID is given, e.g. "ISO15031-5" or "SAE J1979 Rev May 2007". mmt.qualifiedName="ObdPidServiceNeeds.standard";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a particular PID (parameter identifier), which is supported by this component or module. mmt.qualifiedName="ObdPidServiceNeeds" atpObject Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a particular "ratio monitoring", which is supported by this component or module. mmt.qualifiedName="ObdRatioServiceNeeds" atpObject Defines how the DEM is connected to the component or module to perform the IUMPR service. mmt.qualifiedName="ObdRatioServiceNeeds.connectionType";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines the IUMPR Group of the SAE standard. Note that possible values are not predefined by an enumeration meta-type in oder to make the meta-model independent of the details of the SAE standard. Possible values are currently (AUTOSAR R3.1): CAT1 CAT2 OXS1 OXS2 EGR SAIR EVAP SECOXS1 SECOXS2 NMHCCAT NOXCAT NOXADSORB PMFILTER EGSENSOR BOOSTPRS NOGROUP NONE. mmt.qualifiedName="ObdRatioServiceNeeds.iumprGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1" The rate based monitored Diagnosic Event. mmt.qualifiedName="ObdRatioServiceNeeds.rateBasedMonitoredEvent";pureMM.maxOccurs="1";pureMM.minOccurs="1" Function Inhibition Identifier used for the rate based monitor. This is an optional attribute. mmt.qualifiedName="ObdRatioServiceNeeds.usedFid";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specifies the abstract needs of a compoment or module on the configuration of OBD Services in relation to a particular "ratio monitoring", which is supported by this component or module. mmt.qualifiedName="ObdRatioServiceNeeds" atpObject Pass a message once every N message occurrences. Algorithm: occurrence % period == offset Start: occurrence = 0. Each time the message is received or transmitted, occurrence is incremented by 1 after filtering. Length of occurrence is 8 bit (minimum). mmt.qualifiedName="OneEveryN" atpObject specifies the initial number of messages to occur before the first message is passed mmt.qualifiedName="OneEveryN.offset";pureMM.maxOccurs="1";pureMM.minOccurs="1" specifies number of messages to occur before the message is passed again mmt.qualifiedName="OneEveryN.period";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pass a message once every N message occurrences. Algorithm: occurrence % period == offset Start: occurrence = 0. Each time the message is received or transmitted, occurrence is incremented by 1 after filtering. Length of occurrence is 8 bit (minimum). mmt.qualifiedName="OneEveryN" atpObject An opaque literal. mmt.qualifiedName="OpaqueLiteral" atpObject,atpPrototype The string encodes an array of bytes in the following syntax "ae:05:fe" mmt.qualifiedName="OpaqueLiteral.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" An opaque literal. mmt.qualifiedName="OpaqueLiteral" atpObject,atpPrototype This Datatype represents an array of exactly numberOfBits bits. It is called "opaque" because this array of bits should be transported "as is" by the AUTOSAR RTE. mmt.qualifiedName="OpaqueType" atpObject,atpType The number of bits that are used to make up the opaque type. mmt.qualifiedName="OpaqueType.numberOfBits";pureMM.maxOccurs="1";pureMM.minOccurs="1" This Datatype represents an array of exactly numberOfBits bits. It is called "opaque" because this array of bits should be transported "as is" by the AUTOSAR RTE. mmt.qualifiedName="OpaqueType" atpObject,atpType The OperationInvokedEvent references the OperationPrototype invoked by the client. mmt.qualifiedName="OperationInvokedEvent" atpObject The operation to be executed as the consequence of the event. mmt.qualifiedName="operation.event";pureMM.maxOccurs="1";pureMM.minOccurs="1" The OperationInvokedEvent references the OperationPrototype invoked by the client. mmt.qualifiedName="OperationInvokedEvent" atpObject mmt.qualifiedName="OperationInvokedEvent_operation" atpObject,instanceRef mmt.qualifiedName="OperationInvokedEvent_operation.pPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="OperationInvokedEvent_operation.operationPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="OperationInvokedEvent_operation" atpObject,instanceRef An operation declared within the scope of a client/server interface. mmt.qualifiedName="OperationPrototype" atpObject,atpStructureElement ArgumentPrototypes owned by this OperationPrototype. mmt.qualifiedName="argument.OperationPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Possible errors that may by raised by referring operation. mmt.qualifiedName="OperationPrototype.possibleError";pureMM.maxOccurs="-1";pureMM.minOccurs="0" An operation declared within the scope of a client/server interface. mmt.qualifiedName="OperationPrototype" atpObject,atpStructureElement The basic source for time in the ECU. Based on the oscillator the PU clock is generated, but also the communication and other peripherals need timing information (ADC, PWM, timer). mmt.qualifiedName="Oscillator" atpObject Defines if the oscillator is adjustable from software. mmt.qualifiedName="Oscillator.adjustible";pureMM.maxOccurs="1";pureMM.minOccurs="0" An internal, very inaccurate RC-oscillator, which provide the PU with a clock source when the external oscillator is not available. mmt.qualifiedName="backupOscillator.Oscillator";pureMM.maxOccurs="1";pureMM.minOccurs="0" The frequency range the oscillator is able to provide. mmt.qualifiedName="oscillatorFrequencyRange.Oscillator";pureMM.maxOccurs="1";pureMM.minOccurs="1" The short-term deviation of the nominal frequency to the real frequency. Jitter is influenced by the circuitry itself, voltage spikes etc. Jitter is critical for communication elements. mmt.qualifiedName="Oscillator.oscillatorJitter";pureMM.maxOccurs="1";pureMM.minOccurs="0" Crystals and other oscillating elements have more than one resonant frequencies, which are usually odd harmonics to the basic, fundamental frequencies. For Automotive a basic requirement should be to use only fundamental mode only. Using overtone modes there is a risk, that the oscillator circuitry starts at the fundamental mode after a error in the start up routine. In order to reach an overtone mode the frequency of the fundamental mode, or lower overtones has to be passed during start up. There is a risk that the oscillator locks to this, lower frequency. Therefore Fundamental modes oscillatorts are not so critical for this issue. Fundamental quartz/crystals can reach up to 40 MHz today, above this frequency all quartz/crystals are running in the 3rd, 5th or higher overtone mode. mmt.qualifiedName="Oscillator.oscillatorMode";pureMM.maxOccurs="1";pureMM.minOccurs="0" The time the oscillator needs to deliver a stable and valid signal. mmt.qualifiedName="Oscillator.oscillatorStartupTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" The long-term deviation of the nominal frequency to the real frequency. Influenced by manufacturing, layout, temperature, external components and voltage. Tolerances are critical for timer application and time synchronisation. mmt.qualifiedName="Oscillator.oscillatorTolerance";pureMM.maxOccurs="1";pureMM.minOccurs="0" The basic source for time in the ECU. Based on the oscillator the PU clock is generated, but also the communication and other peripherals need timing information (ADC, PWM, timer). mmt.qualifiedName="Oscillator" atpObject Component port providing a certain port interface. mmt.qualifiedName="PPortPrototype" atpObject,atpPrototype Provided communication attributes per interface element (data element or operation). mmt.qualifiedName="providedComSpec.PPortPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The interface that this port provides. mmt.qualifiedName="pPort.providedInterface";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType Component port providing a certain port interface. mmt.qualifiedName="PPortPrototype" atpObject,atpPrototype Pulse Width Demodulation is the inverse method of PWM. Here the processing unit is trying to gather information about a signal. A PWD can detect rising and falling edges and call the software in order to calculate the pulse width. When a PWD have more than one input signal the frequency and phase between the signals can be obtained. mmt.qualifiedName="PWD" atpObject A Pulse Width Demodulation peripheral can be configured to decode a two phase or a three phase input signals. mmt.qualifiedName="PWD.mode";pureMM.maxOccurs="1";pureMM.minOccurs="1" Some timers have the possibility to detect signals from a quadrature rotating switch. There are two outputs signal from such a switch; the signals are 90 degrees phase shifted from each other. The rotation of the switch can then automatically be detected by a special function in a timer. mmt.qualifiedName="PWD.phaseDetection";pureMM.maxOccurs="1";pureMM.minOccurs="1" Pulse Width Demodulation is the inverse method of PWM. Here the processing unit is trying to gather information about a signal. A PWD can detect rising and falling edges and call the software in order to calculate the pulse width. When a PWD have more than one input signal the frequency and phase between the signals can be obtained. mmt.qualifiedName="PWD" atpObject Pulse Width Modulation refers to a method of carrying information on a train of pulses, the information being encoded in the width of the pulses. The frequency is normally not changed. It's only relationship between the high and low level of the signal which are changed. A PWM interface is usually a part of a processing unit. It provides the capability to communicate with another system with an easy protocol. mmt.qualifiedName="PWM" atpObject The period between successive calls to Com_MainFunctionRx in seconds. This parameter may be used by the COM generator to transform the values of the reception related timing configuration parameters of the COM module to internal implementation specific counter or tick values. The COM module's internal timing handling is implementation specific. The COM module (generator) may rely on the fact that Com_MainFunctionRx is scheduled according to the value configured here. mmt.qualifiedName="ParamConfContainerDef" atpObject Specifies whether this container is used to define multiple configuration sets. Only one container in the whole ModuleDef shall have this enabled. mmt.qualifiedName="ParamConfContainerDef.multipleConfigurationContainer";pureMM.maxOccurs="1";pureMM.minOccurs="1" The parameters defined within the ParamConfContainerDef. mmt.qualifiedName="parameter.ParamConfContainerDef";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The references defined within the ParamConfContainerDef. mmt.qualifiedName="reference.ParamConfContainerDef";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The containers defined within the ParamConfContainerDef. mmt.qualifiedName="subContainer.ParamConfContainerDef";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The period between successive calls to Com_MainFunctionRx in seconds. This parameter may be used by the COM generator to transform the values of the reception related timing configuration parameters of the COM module to internal implementation specific counter or tick values. The COM module's internal timing handling is implementation specific. The COM module (generator) may rely on the fact that Com_MainFunctionRx is scheduled according to the value configured here. mmt.qualifiedName="ParamConfContainerDef" atpObject Common class used to express multiplicities in the definition of configuration parameters, references and containers. If not stated otherwise the default multiplicity is exactly one mandatory occurrence of the specified element. mmt.qualifiedName="ParamConfMultiplicity" atpObject The lower multiplicity of the specified element. 0: optional 1: at least one occurence n: at least n occurrences mmt.qualifiedName="ParamConfMultiplicity.lowerMultiplicity";pureMM.maxOccurs="1";pureMM.minOccurs="1" The upper multiplicity of the specified element. 1: at most one occurrence m: at most m occurrences *: arbitrary number of occurrences mmt.qualifiedName="ParamConfMultiplicity.upperMultiplicity";pureMM.maxOccurs="1";pureMM.minOccurs="1" This meta-class represents the ability to provide an initial value for a calibration parameter. mmt.qualifiedName="ParameterProvideComSpec" atpObject This meta-class represents the ability to define an initial value for a calibration parameter. mmt.qualifiedName="ParameterRequireComSpec" atpObject Common class to all types of configuration values mmt.qualifiedName="ParameterValue" atpObject Reference to the definition of this ParameterValue subclasses in the ECU Configuration Parameter Definition. mmt.qualifiedName="ParameterValue.definition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="-10" Default Value which will be distributed if no I-Pdu has been received since last sending. mmt.qualifiedName="PduMappingDefaultValue" atpObject The default value consists of a number of elements. Each default value element is represented by the element and the position in an array. mmt.qualifiedName="defaultValueElement.PduMappingDefaultValue";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Default Value which will be distributed if no I-Pdu has been received since last sending. mmt.qualifiedName="PduMappingDefaultValue" atpObject A PduToFrameMapping defines the composition of Pdus in each frame. Depending on its relation to entities such channels and clusters it can be unambiguously deduced whether a fan-out is handled by the Pdu router or the Bus Interface. mmt.qualifiedName="PduToFrameMapping" atpObject This attribute defines the order of the bytes of the Pdu and the packing into the Frame. The byte ordering "Little Endian" (MostSignificantByteLast) and "Big Endian" (MostSignificantByteFirst) can be selected. A mix between Little Endian and Big Endian within a Frame is not allowed (all PduToFrameMappings within a Frame must have the same packingByteOrder). mmt.qualifiedName="PduToFrameMapping.packingByteOrder";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to a I-Pdu, N-Pdu or NmPdu that is transmitted in the Frame. mmt.qualifiedName="PduToFrameMapping.pdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" This parameter is necessary to describe the byteposition of a Pdu within a Frame. Note that the absolute position of the Pdu in the Frame is determined by the definition of the packingByteOrder attribute. If Big Endian is specified, the start position indicates the bit position of the most significant bit in the Frame. If Little Endian is specified, the start position indicates the bit position of the least significant bit in the Frame. mmt.qualifiedName="PduToFrameMapping.startPosition";pureMM.maxOccurs="1";pureMM.minOccurs="1" Indication to the receivers that the corresponding I-Pdu was updated by the sender. This attribute describes the position of the update bit in the frame that aggregates this PDUToFrameMapping. Length is always one bit. The updateIndicationBitPosition is determined by the definition of the packingByteOrder attribute. If Big Endian is specified, the updateIndicationBitPosition indicates the bit position of the most significant bit in the Frame. If Little Endian is specified, the updateIndicationBitPosition indicates the bit position of the least significant bit in the Frame. mmt.qualifiedName="PduToFrameMapping.updateIndicationBitPosition";pureMM.maxOccurs="1";pureMM.minOccurs="0" A PduToFrameMapping defines the composition of Pdus in each frame. Depending on its relation to entities such channels and clusters it can be unambiguously deduced whether a fan-out is handled by the Pdu router or the Bus Interface. mmt.qualifiedName="PduToFrameMapping" atpObject The AUTOSAR PduR will enable and disable the sending of configurable groups of IPdus during runtime according to the AUTOSAR PduR specification. mmt.qualifiedName="PdurIPduGroup" atpObject This attribute defines the use-case for this PduRIPduGroup. For example, in a diagnostic mode all IPdus - which are not involved in diagnostic - are disabled. The use cases are not limited to a fixed enumeration and can be specified as a string. mmt.qualifiedName="PdurIPduGroup.communicationMode";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to a set of IPdus, which are contained in the PduR I-Pdu Group. If an IPdu is routed by the PduR to different destinations (PduR fan-out) than an PduTriggering for each destination is created in the System Template. To enable/disable a specific destination the PdurIPduGroup refers to the PduTriggering. mmt.qualifiedName="PdurIPduGroup.iPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The AUTOSAR PduR will enable and disable the sending of configurable groups of IPdus during runtime according to the AUTOSAR PduR specification. mmt.qualifiedName="PdurIPduGroup" atpObject Defines a memory-block that needs to be available for each instance of the SW-component. This is typically only useful if supportsMultipleInstantiation is TRUE of if the component defines NVRAM access via permanent blocks. mmt.qualifiedName="PerInstanceMemory" atpObject The "C"-type mmt.qualifiedName="PerInstanceMemory.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" A definition of the type mmt.qualifiedName="PerInstanceMemory.typeDefinition";pureMM.maxOccurs="1";pureMM.minOccurs="1" Defines a memory-block that needs to be available for each instance of the SW-component. This is typically only useful if supportsMultipleInstantiation is TRUE of if the component defines NVRAM access via permanent blocks. mmt.qualifiedName="PerInstanceMemory" atpObject Resources needed by the allocation of PerInstanceMemory for each SWC instance. Note that these resources are not covered by an ObjectFileSection, because they are supposed to be allocated by the RTE. mmt.qualifiedName="PerInstanceMemorySize" atpObject Required alignment (1,2,4,...) of the referenced PerInstanceMemory mmt.qualifiedName="PerInstanceMemorySize.alignment";pureMM.maxOccurs="1";pureMM.minOccurs="1" This represents that PerInstanceMemory to which the PerInstanceMemorySize refers to. mmt.qualifiedName="PerInstanceMemorySize.perInstanceMemory";pureMM.maxOccurs="1";pureMM.minOccurs="1" Size (in bytes) of the reference perInstanceMemory mmt.qualifiedName="PerInstanceMemorySize.size";pureMM.maxOccurs="1";pureMM.minOccurs="1" Resources needed by the allocation of PerInstanceMemory for each SWC instance. Note that these resources are not covered by an ObjectFileSection, because they are supposed to be allocated by the RTE. mmt.qualifiedName="PerInstanceMemorySize" atpObject General Element for all peripherals. mmt.qualifiedName="Peripheral" atpObject Defines if the peripheral can be logically enabled or disabled. mmt.qualifiedName="Peripheral.canBeDisabled";pureMM.maxOccurs="1";pureMM.minOccurs="0" General Element for all peripherals. mmt.qualifiedName="Peripheral" atpObject This port is directed from the peripheral to the ecu electronics and communication. mmt.qualifiedName="PeripheralHWPort" atpObject Defines the number of elements that can be stored in an input or output buffer. A capture timer can for example have several registers to store the timer value when an external event has occurred. mmt.qualifiedName="buffer.PeripheralHWPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" An input or output can sometimes be programmed to invert the level of a signal. mmt.qualifiedName="PeripheralHWPort.inversion";pureMM.maxOccurs="1";pureMM.minOccurs="0" The peripheral device has the feature to issue a Power On event to the ECU. Example: Some CAN bus transceivers have a dedicated low power voltage regulator and a feature, which allows to turn on the main voltage regulator of the ECU by detecting a bus activity. Example: A wired-or connection of a termination KL30 and KL15 can fulfil this requirement. mmt.qualifiedName="PeripheralHWPort.powerOnCapability";pureMM.maxOccurs="1";pureMM.minOccurs="0" The peripheral device has the feature to issue a wake-up event to the processing unit. Example: HW Port with Key-Wake-Up on a PU is still active while the PU is in stop mode and only partially supplied with power. The Key-Wake-Up reacts on any changes at the input of the HW Port with the activation of the power supply, the activation of the clock system and later the resuming of the software, which has to process the input of the HW Port. mmt.qualifiedName="PeripheralHWPort.wakeUpCapability";pureMM.maxOccurs="1";pureMM.minOccurs="0" This port is directed from the peripheral to the ecu electronics and communication. mmt.qualifiedName="PeripheralHWPort" atpObject The PermissibleSignalPath describes the way a data element shall take in the topology. The path is described by ordered references to PhysicalChannels. If more than one PermissibleSignalPath is defined for the same signal/operation attributes, any of them can be chosen. Such a signal path can be a constraint for the communication matrix . This path describes that one data element should take path A (e.g. 1. Can channel, 2. Lin channel) and not path B (1. Can channel, FlexRay channel A). This has an effect on the frame generation and the frame path. mmt.qualifiedName="PermissibleSignalPath" atpObject The arguments of an operation that can take the predefined way in the topology. mmt.qualifiedName="operation.PermissibleSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The SwcToSwcSignal can be transmitted on one of these physical channels. mmt.qualifiedName="PermissibleSignalPath.physicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The data element which can take the predefined way in the topology. mmt.qualifiedName="signal.PermissibleSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The PermissibleSignalPath describes the way a data element shall take in the topology. The path is described by ordered references to PhysicalChannels. If more than one PermissibleSignalPath is defined for the same signal/operation attributes, any of them can be chosen. Such a signal path can be a constraint for the communication matrix . This path describes that one data element should take path A (e.g. 1. Can channel, 2. Lin channel) and not path B (1. Can channel, FlexRay channel A). This has an effect on the frame generation and the frame path. mmt.qualifiedName="PermissibleSignalPath" atpObject mmt.qualifiedName="PhysConstrs" atpObject This element specifies the lower limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="PhysConstrs.lowerLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This element specifies the upper limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="PhysConstrs.upperLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This is one particular scale in which contributes to the data constraints. mmt.qualifiedName="PhysConstrs.scaleConstr";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" This element specifies the maximum slope that may be used in maps and curves. mmt.qualifiedName="PhysConstrs.maxGradient";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" Maximum difference that is permitted between two consecutive values if the constraint is applied to an axis. mmt.qualifiedName="PhysConstrs.maxDiff";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This specifies the monotony constraints on the data object. Note that this applies only to curves and maps. mmt.qualifiedName="PhysConstrs.monotony";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" Use <unit> to enter the unit of a parameter. mmt.qualifiedName="PhysConstrs.unit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" mmt.qualifiedName="PhysConstrs" atpObject A physical channel is the transmission medium that is used to send and receive information between two communicating ECUs. Each CommunicationCluster has at least one physical channel. Bus systems like CAN and LIN only have exactly one PhysicalChannel. A FlexRay cluster may have more than one PhysicalChannels that may be used in parallel for redundant communication. An ECU is part of a cluster if it contains at least one controller that is connected to at least one channel of the cluster. mmt.qualifiedName="PhysicalChannel" atpObject One frame triggering is defined for exactly one channel. Channels may have assigned an arbitrary number of frame triggerings. mmt.qualifiedName="frameTriggerings.PhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable One I-Pdu triggering is defined for exactly one channel. Channels may have assigned an arbitrary number of I-Pdu triggerings. mmt.qualifiedName="iPduTriggering.PhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable One ISignalTriggering is defined for exactly one channel. Channels may have assigned an arbitrary number of ISignaltriggerings. mmt.qualifiedName="iSignalTriggering.PhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" atpSplitable Collection of TpAddresses. mmt.qualifiedName="tpAddress.PhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Optional configuration of Tranport Protocol channels. mmt.qualifiedName="tpChannel.PhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Senders and receivers of TP messages. mmt.qualifiedName="tpNode.PhysicalChannel";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A physical channel is the transmission medium that is used to send and receive information between two communicating ECUs. Each CommunicationCluster has at least one physical channel. Bus systems like CAN and LIN only have exactly one PhysicalChannel. A FlexRay cluster may have more than one PhysicalChannels that may be used in parallel for redundant communication. An ECU is part of a cluster if it contains at least one controller that is connected to at least one channel of the cluster. mmt.qualifiedName="PhysicalChannel" atpObject This class represents a physical dimension. If the physical dimension of two units is identical a conversion between them is possible. The conversion between units is related to the definition of the physical dimension. mmt.qualifiedName="PhysicalDimension" atpObject The exponent of the physical dimension "length" mmt.qualifiedName="PhysicalDimension.lengthExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" The exponent of the physical dimension "mass" mmt.qualifiedName="PhysicalDimension.massExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" The exponent of the physical dimension "time" mmt.qualifiedName="PhysicalDimension.timeExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" the exponent of the physical dimension "electric current" mmt.qualifiedName="PhysicalDimension.currentExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" The exponent of the physical dimension "temperature" mmt.qualifiedName="PhysicalDimension.temperatureExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" The exponent of the physical dimension "quantity of substance" mmt.qualifiedName="PhysicalDimension.molarAmountExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" The exponent of the physical dimension "luminous intensity" mmt.qualifiedName="PhysicalDimension.luminousIntensityExp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" This class represents a physical dimension. If the physical dimension of two units is identical a conversion between them is possible. The conversion between units is related to the definition of the physical dimension. mmt.qualifiedName="PhysicalDimension" atpObject Is used to connect the HWPins of the HWPorts that are referenced by the HWConnection. mmt.qualifiedName="PinHWConnection" atpObject Reference to the connected pin. When the PinHWConnection is used in the context of a DelegationHWConnection there might be only ONE pin known (typically this is a pin of the OUTER-PORT), so only one pin has to be specified. mmt.qualifiedName="PinHWConnection.connectedPin";pureMM.maxOccurs="2";pureMM.minOccurs="1" Is used to connect the HWPins of the HWPorts that are referenced by the HWConnection. mmt.qualifiedName="PinHWConnection" atpObject Describes a mapping between one or several Virtual Function Clusters onto Partial Network Clusters. A Virtual Function Cluster is realized by a PortGroup. A Partial Network Cluster is realized by one or more IPduGroups. mmt.qualifiedName="PncMapping" atpObject IPduGroup participating in a Partial Network Cluster. This reference is optional in case an ecu extract has only indirect pnc access, i.e. ecu is not directly conntected to a network which supports partial network. mmt.qualifiedName="PncMapping.pncGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Identifer of the Partial Network Cluster. mmt.qualifiedName="PncMapping.pncIdentifier";pureMM.maxOccurs="1";pureMM.minOccurs="1" Virtual Function Cluster to be mapped onto a Partial Network Cluster. This reference is optional in case that the System Description doesn't use a complete Software Component Description (VFB View). This supports the inclusion of legacy systems. mmt.qualifiedName="vfc.PncMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to collection of FrameTriggerings that are used for the wakeup of this PNC (Application Frames or Nm Frames can be used). This reference is optional in case an ecu extract has only indirect pnc access, i.e. ecu is not directly conntected to a network which supports partial network. mmt.qualifiedName="PncMapping.wakeupFrame";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Describes a mapping between one or several Virtual Function Clusters onto Partial Network Clusters. A Virtual Function Cluster is realized by a PortGroup. A Partial Network Cluster is realized by one or more IPduGroups. mmt.qualifiedName="PncMapping" atpObject mmt.qualifiedName="PncMapping_vfc" atpObject,instanceRef mmt.qualifiedName="PncMapping_vfc.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="PncMapping_vfc.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="PncMapping_vfc.vfc";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="PncMapping_vfc" atpObject,instanceRef Options how to generate the signatures of calls for an AtomicSoftwareComponentType in order to communicate over a PortPrototype (for calls into a RunnableEntity as well as for calls from a RunnableEntity to the PortPrototype). mmt.qualifiedName="PortAPIOption" atpObject If set to true, the software-component is able to use the API reference for deriving a pointer to an object. mmt.qualifiedName="PortAPIOption.enableTakeAddress";pureMM.maxOccurs="1";pureMM.minOccurs="1" true: Specifies an "indirect API" to be generated for the associated port, which means that the SWC is able to access the actions on a port via a pointer to an object representing a port. This allows e.g. iterating over ports in a loop. This option has no effect for PPorts of client/server interfaces. mmt.qualifiedName="PortAPIOption.indirectAPI";pureMM.maxOccurs="1";pureMM.minOccurs="1" A "port defined argument values" is passed to a runnable dealing with the operations provided by a given port. Restricted to PPorts of a client/server interface. mmt.qualifiedName="portArgValue.PortAPIOption";pureMM.maxOccurs="-1";pureMM.minOccurs="0" the option is valid for generated functions related to communication over this port mmt.qualifiedName="PortAPIOption.port";pureMM.maxOccurs="1";pureMM.minOccurs="1" Options how to generate the signatures of calls for an AtomicSoftwareComponentType in order to communicate over a PortPrototype (for calls into a RunnableEntity as well as for calls from a RunnableEntity to the PortPrototype). mmt.qualifiedName="PortAPIOption" atpObject Group of ports which share a common functionality, e.g. need specific network resources. This information shall be available on the VFB level in order to delegate it properly via compositions. When propagated into the ECU extract, this information is used as input for the configuration of Services like the Communication Manager. A PortGroup is defined locally in a component (which can be a composition) and refers to the "outer" ports belonging to the group as well as to the "inner" groups which propagate this group into the components which are part of a composition. A PortGroup within an atomic SWC cannot be linked to inner groups. mmt.qualifiedName="PortGroup" atpObject,atpStructureElement Links a PortGroup in a composition to another PortGroup, that is defined in a component which is part of this CompositionType. mmt.qualifiedName="innerGroup.PortGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Outer port of this component which belongs to the group. A port can belong to several groups or to no group at all. mmt.qualifiedName="PortGroup.outerPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Group of ports which share a common functionality, e.g. need specific network resources. This information shall be available on the VFB level in order to delegate it properly via compositions. When propagated into the ECU extract, this information is used as input for the configuration of Services like the Communication Manager. A PortGroup is defined locally in a component (which can be a composition) and refers to the "outer" ports belonging to the group as well as to the "inner" groups which propagate this group into the components which are part of a composition. A PortGroup within an atomic SWC cannot be linked to inner groups. mmt.qualifiedName="PortGroup" atpObject,atpStructureElement mmt.qualifiedName="PortGroup_innerGroup" atpObject,instanceRef mmt.qualifiedName="PortGroup_innerGroup.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="PortGroup_innerGroup.portGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="PortGroup_innerGroup" atpObject,instanceRef Abstract base class for an interface that is either provided or required by a port of a software component. mmt.qualifiedName="PortInterface" atpObject,atpType This flag is set, if the PortInterface is to be used for communication between an ApplicationSoftwareComponentType and a ServiceComponentType (namely an AUTOSAR Service, ECU abstraction or Complex Driver) located on the same ECU. Otherwise the flag is not set. mmt.qualifiedName="PortInterface.isService";pureMM.maxOccurs="1";pureMM.minOccurs="1" Base class for the ports of an AUTOSAR software component. mmt.qualifiedName="PortPrototype" atpObject,atpPrototype Annotations on this CalibrationPort. mmt.qualifiedName="calibrationPortAnnotation.PortPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Annotations on this delegated port. mmt.qualifiedName="delegatedPortAnnotation.PortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0" Annotations on this IoHwAbstraction port. mmt.qualifiedName="ioHwAbstractionServerAnnotation.PortPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Collection of annotations of this ports sender/receiver communication. mmt.qualifiedName="senderReceiverAnnotation.PortPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Power Driver HW Element describes a group of electronic devices, which perform signal transformations with hardware devices. The main focus of the ECU Resource Template is the logical description of these elements, necessary for the system generation and relevant for the SW development. mmt.qualifiedName="PowerDriverHWElement" atpObject The device limits the maximum current conduction. The limit has to be specified. If this element does not occur the HW Element does not provide current limitation. Unit: Ampere mmt.qualifiedName="PowerDriverHWElement.currentLimitation";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="PowerDriverHWElement.defaultResetBehaviuor";pureMM.maxOccurs="1";pureMM.minOccurs="0" Which kind of notification to the PU is available. mmt.qualifiedName="notification.PowerDriverHWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" The resistance in ON state can be used together with the current through this element to determine the static thermal power dissipation of the element itself and the ECU completely by summing up each element with power dissipation. As the heating up of an power element follows with an exponential delay, the ratio of on and off times is later needed in the system generation process. This information can give the first hint on critical issues of thermal design, but does not replace a complete static and dynamic verification of the thermal layout. Unit: Ohm mmt.qualifiedName="PowerDriverHWElement.onStateResistance";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the general type of the element. Type is a most common naming for an element. Several sets of types exist. Type is mandatory for the usage of the ECU Resource Template. mmt.qualifiedName="PowerDriverHWElement.powerDriverType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Which kind of protection is available. mmt.qualifiedName="protection.PowerDriverHWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describe the way the element is reactivated after a self protection sequence was entered mmt.qualifiedName="PowerDriverHWElement.resetOnFaultBehaviour";pureMM.maxOccurs="1";pureMM.minOccurs="0" Power Driver HW Element describes a group of electronic devices, which perform signal transformations with hardware devices. The main focus of the ECU Resource Template is the logical description of these elements, necessary for the system generation and relevant for the SW development. mmt.qualifiedName="PowerDriverHWElement" atpObject Define the option of a Power Driver that the output of a Power Driver can be superposed by a PWM signal asserted by a HW Element e.g. a microprocessor. In most cases, the PWM signal is connected by a separate wire, even when the general control information are transmitted by a bus. mmt.qualifiedName="PowerDriverHWPort" atpObject It defines the upper limit at which the device can fulfil the PWM capability. EMC and power dissipation are increasing almost exponential with the PWM frequency. Choosing PWM frequencies be aware that some effects can cause secondary effects, which can create a audible noise for the user, e.g. a PWM dimmed lamp can be noticed by the driver. Unit: Hz mmt.qualifiedName="PowerDriverHWPort.pwmMaxFrequency";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the characteristic, that a Power Driver has to be off at least a minimum time in order to assure the function. Unit: s mmt.qualifiedName="PowerDriverHWPort.pwmMinOffTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the characteristic, that a Power Driver has to be on at least a minimum time in order to assure the function. Unit: s mmt.qualifiedName="PowerDriverHWPort.pwmMinOnTime";pureMM.maxOccurs="1";pureMM.minOccurs="0" Define the option of a Power Driver that the output of a Power Driver can be superposed by a PWM signal asserted by a HW Element e.g. a microprocessor. In most cases, the PWM signal is connected by a separate wire, even when the general control information are transmitted by a bus. mmt.qualifiedName="PowerDriverHWPort" atpObject Describe the status which cause a notification to the controlling devices of an ECU, e.g. to the PU. mmt.qualifiedName="PowerDriverNotification" atpObject If a notification is issued, in which Interrupt will it result. mmt.qualifiedName="PowerDriverNotification.issuedInterruptSource";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a loss of ground situation. The device was forced off, in order to avoid damages by excessive currents. mmt.qualifiedName="PowerDriverNotification.lossOfGround";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a too high current. mmt.qualifiedName="PowerDriverNotification.maxCurrent";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a too high supply voltage. mmt.qualifiedName="PowerDriverNotification.maxVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a too low curent. mmt.qualifiedName="PowerDriverNotification.minCurrent";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a too low supply voltage. mmt.qualifiedName="PowerDriverNotification.minVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected open loads. This situation is reported to the controlling portion of an ECU, e.g. to the PU. mmt.qualifiedName="PowerDriverNotification.openLoad";pureMM.maxOccurs="1";pureMM.minOccurs="0" The maximum allowed temperature was detected in the device. A protecting hardware has forced the device off. mmt.qualifiedName="PowerDriverNotification.overTemperature";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device was forced off, in order to avoid damages by excessive currents. mmt.qualifiedName="PowerDriverNotification.shortLoad";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a short to battery situation. The device was forced off, in order to avoid damages by excessive currents. mmt.qualifiedName="PowerDriverNotification.shortToBatt";pureMM.maxOccurs="1";pureMM.minOccurs="0" The device detected a short to ground situation. The device was forced off, in order to avoid damages by excessive currents. mmt.qualifiedName="PowerDriverNotification.shortToGround";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describe the status which cause a notification to the controlling devices of an ECU, e.g. to the PU. mmt.qualifiedName="PowerDriverNotification" atpObject The Power Driver HW Element / ASIC turns off by internal means in order to protect the device against severe damages. mmt.qualifiedName="PowerDriverProtection" atpObject Is protected against loss of ground. mmt.qualifiedName="PowerDriverProtection.lossOfGroundProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Maximal current limits are exceeded. mmt.qualifiedName="PowerDriverProtection.maxCurrentProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Maximal voltage limits are exceeded. mmt.qualifiedName="PowerDriverProtection.maxVoltageProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Minimal current limits are exceeded. mmt.qualifiedName="PowerDriverProtection.minCurrentProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Minimal voltage limits are exceeded. mmt.qualifiedName="PowerDriverProtection.minVoltageProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Is protected against over-temperature. mmt.qualifiedName="PowerDriverProtection.overTemperatureProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" Is protected against reverse battery voltage. mmt.qualifiedName="PowerDriverProtection.reverseBatteryProtection";pureMM.maxOccurs="1";pureMM.minOccurs="0" The Power Driver HW Element / ASIC turns off by internal means in order to protect the device against severe damages. mmt.qualifiedName="PowerDriverProtection" atpObject mmt.qualifiedName="PowerSupplyCurrentNotification" atpObject mmt.qualifiedName="PowerSupplyCurrentNotification.hysteresis";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="PowerSupplyCurrentNotification.interrupt";pureMM.maxOccurs="-1";pureMM.minOccurs="0" mmt.qualifiedName="PowerSupplyCurrentNotification.level";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="PowerSupplyCurrentNotification" atpObject The Power Supply HW Element provides information about the power source of the ECU. There can be multiple power supplies within one ECU. mmt.qualifiedName="PowerSupplyHWElement" atpObject Define the capability assigned to the output of the Power Supply HW Element to maintain the output voltage stable for a certain time after the undervoltage status information is asserted. In the ECU Resource Template the Backup Capacity is described as time. The time is dependent from the current consumed by the HW Elements connected to the according output, the SW-functions controlling the ECU hardware and the implementation of the Power Supply HW Element itself. The time has to be calculated from the available capacitors or measured in the application. Example: For the energy storage for airbag applications capacitors stores energy for the airbag ignition for several seconds even the battery is completely disconnected. Example: A combined step up/step down DC/DC converter can deliver a stable 5V volt output even when the input has already dropped to 3V. The undervoltage status is already set at a Vbatt level of 6V. Unit: Ah mmt.qualifiedName="PowerSupplyHWElement.backupCapacity";pureMM.maxOccurs="1";pureMM.minOccurs="0" This value defines the nominal output voltage, which is supplied as default after a reset occured. This attribute is only applicable at power supplies with a programmable output voltage. mmt.qualifiedName="PowerSupplyHWElement.defaultVoltageOnReset";pureMM.maxOccurs="1";pureMM.minOccurs="0" The maximum voltage that can be supplied. mmt.qualifiedName="PowerSupplyHWElement.maxVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="1" The minimum voltage that can be supplied. mmt.qualifiedName="PowerSupplyHWElement.minVoltage";pureMM.maxOccurs="1";pureMM.minOccurs="1" Status information that the on-chip temperature on the Power Supply Hardware Element exceed the maximal, defined limit. mmt.qualifiedName="PowerSupplyHWElement.notificationOverTemperature";pureMM.maxOccurs="1";pureMM.minOccurs="0" The power on reset is generated depending on the output voltage. Valid operation of the ECU and the connected HW Elements are only possible if the output voltage is stable and within the specified output voltage range. Therefore most of the Power Supply HW Elements contain a circuitry, which generate a output signal which indicates an instable or unspecified voltage at the output. Some Power Supply HW Elements offer the possibility to adjust the reset thresholds. mmt.qualifiedName="PowerSupplyHWElement.notificationReset";pureMM.maxOccurs="1";pureMM.minOccurs="0" Status information that the output current exceeds the maximal, defined limit at the output of the Power Supply HW Element. A short circuit indication is a special form of the overcurrent status information. mmt.qualifiedName="overCurrentNotification.PowerSupplyHWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" Notification that the source voltage is too high for the power Supply HW Element to handle. mmt.qualifiedName="overVoltageNotification.PowerSupplyHWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" The reset signal at the power-on reset is delayed by the Power Supply HW Element in order to enable the different ECU HW Elements to enter a stable and defined operation state when the reset signal is released. Unit: s mmt.qualifiedName="PowerSupplyHWElement.resetDelay";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describe the way the element is reactivated after a self protection sequence was entered mmt.qualifiedName="PowerSupplyHWElement.resetOnFaultBehaviour";pureMM.maxOccurs="1";pureMM.minOccurs="0" Status information that at the input of the Power Supply HW Element has dropped to a critical value. This can be used to switch off functions, which caused that voltage drop or start a power down function like storing important data to NV memory. mmt.qualifiedName="underVoltageNotification.PowerSupplyHWElement";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the feature of the power supply to turn on the output voltage by an external event. In some cases this feature is coupled with other ECU internal HW elements e.g. transceivers and is the main feature used by the car specific power management. Different to other HW elements with this feature the power supply is the receiver of the signal, as more ECU function is only possible if the power supply is activated. Example: Philips CAN Transceivers have an output called INH, which allow together with some Voltage regulators with wake up capability to wake up the ECU at the presence of a CAN bus telegram. Example: The Wake up Capability is connected to the terminal KL15 (ignition), the ECU is waked up at the presence of KL15. mmt.qualifiedName="PowerSupplyHWElement.wakeupCapability";pureMM.maxOccurs="1";pureMM.minOccurs="0" The Power Supply HW Element provides information about the power source of the ECU. There can be multiple power supplies within one ECU. mmt.qualifiedName="PowerSupplyHWElement" atpObject The Power Supply HW Port is used to model the power distribution within the ECU. If the direction is "in" the port is used to describe the power consumption of an HW Element. If the direction is "out" the port is used to describe a power source. The HW Connection between these two HW Ports can only be established between the Power Supply HW Port of the HW Element with direction "out" and a Power Supply HW Port of the Power Supply HW Element with direction "in". mmt.qualifiedName="PowerSupplyHWPort" atpObject Defines if the Power Supply HW Port can be switched off and therefore the supplied HW Element is switched off as well. This feature allows to describe which parts of an ECU are able be disconnected from their power supply based on software interaction. If the Power Supply HW Port has the direction 'in' the supplied HW Element can be switched off. If the Power Supply HW Port has the direction 'out' the power supply can be switched off and therefore all supplied HW Elements are switched off as well (This is used to describe groups of HW Elements that can only be switched off together). When however the whole ECU is disconnected from power the switchable power supply is of course not valid anymore. mmt.qualifiedName="PowerSupplyHWPort.canBeSwitchedOff";pureMM.maxOccurs="1";pureMM.minOccurs="0" For power source: provided electrical specification. For power consumer: required electrical specification. mmt.qualifiedName="supplied.PowerSupplyHWPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" The Power Supply HW Port is used to model the power distribution within the ECU. If the direction is "in" the port is used to describe the power consumption of an HW Element. If the direction is "out" the port is used to describe a power source. The HW Connection between these two HW Ports can only be established between the Power Supply HW Port of the HW Element with direction "out" and a Power Supply HW Port of the Power Supply HW Element with direction "in". mmt.qualifiedName="PowerSupplyHWPort" atpObject mmt.qualifiedName="PowerSupplyVoltageNotification" atpObject mmt.qualifiedName="PowerSupplyVoltageNotification.hystereses";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="PowerSupplyVoltageNotification.interrupt";pureMM.maxOccurs="-1";pureMM.minOccurs="0" mmt.qualifiedName="PowerSupplyVoltageNotification.level";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="PowerSupplyVoltageNotification" atpObject A primitive datatype consists of a set of allowed values. mmt.qualifiedName="PrimitiveType" atpObject,atpType This represents the swDataDefProps of the PrimitiveType. mmt.qualifiedName="PrimitiveType.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0" A ProcessingUnit describes the plain processor core. The identifier provides the actual type name of the processing unit. mmt.qualifiedName="ProcessingUnit" atpObject The addressing modes describe the options to access the data from the memory. mmt.qualifiedName="ProcessingUnit.addressingModes";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The kind of architecture mmt.qualifiedName="ProcessingUnit.architectureKind";pureMM.maxOccurs="1";pureMM.minOccurs="0" The name of the architecture (e.g. ARM, MIPS, PowerPC). mmt.qualifiedName="ProcessingUnit.architectureName";pureMM.maxOccurs="1";pureMM.minOccurs="0" The architecture type take influence to the performance index of a PU, but are not necessarily a main topic of software development, as some of the aspects are transparent to the user as the are handled with in the compiler. The last two types are slightly different as they require a detailed planning during system design, how the data must be prepared in order to use the features of an SIMD or MIMD very efficiently. Application like video processing use in general this features by their data format, as every pixel information is formed by the three basic colours and intensity, thus each pixel is represented by four different values, which have to be processed simultaneously. mmt.qualifiedName="ProcessingUnit.architectureType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Provide information about the boot time of the PU. mmt.qualifiedName="bootTime.ProcessingUnit";pureMM.maxOccurs="1";pureMM.minOccurs="0" Direct Memory Access is a mechanism for off-loading a PU and having transfer directly between memory and peripherals without involving the PU. In most common PU the DMA mechanism is implemented with a specialised cell (DMA unit) that transfers data between a peripheral device and memory, independent of the processor. The DMA controller becomes the bus master and directs the reads or writes between itself and memory. A typical DMA transfer can be described in three steps: 1. The PU sets up the DMA transfer by supplying the identity of the periphery module, the operation to perform on that device, the memory address that is the source or the destination of the data to be transferred, and the number of bytes to transfer. 2. The DMA starts the operation on the periphery device and arbitrates for the bus. When the data is available, from the periphery device or memory, it transfers the data. The DMA unit supplies the memory address and initiates the next transfer. With this technique, a DMA unit can complete an entire transfer, which may be Kbytes of data, without bothering the PU. Many DMA units contain some memory to allow them to deal flexibly with delays either in transfer or those incurred while waiting to become bus master. 3. Once the DMA transfer is complete, the DMA unit interrupts the processor, which can then determine by interrogating the DMA unit or examining memory whether the entire operation completed successfully. During an active DMA transfer the PU cannot access the involved resources concurrently. mmt.qualifiedName="ProcessingUnit.dmaChannelCount";pureMM.maxOccurs="1";pureMM.minOccurs="0" Name of the technology used to implement this PU. mmt.qualifiedName="ProcessingUnit.implementationTechnology";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines how many interrupts are allowed to be activated at one time. This entry is mainly defined by the size of the according stack as the data saving mechanism during interrupts and the data passing mechanism during function calls use the stack. mmt.qualifiedName="ProcessingUnit.maxInterruptNestingLevels";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the Memory Protection Unit, if available. mmt.qualifiedName="mpu.ProcessingUnit";pureMM.maxOccurs="1";pureMM.minOccurs="0" The natural data size prvides information which data manipulations are optimized on this PU. The natural data size is typically the Data Register size. The PU is optimised for this data size. Typical natural data size is one of following (in bits): 8, 16, 32, 64, other (12, 20, 80) mmt.qualifiedName="ProcessingUnit.naturalDataSize";pureMM.maxOccurs="1";pureMM.minOccurs="1" The attribute describes the typical length of the opcodes. In CISC machines the opcode size is variable due to the opcode itself. In RISC machines the opcode is by definition limited to a defined size. Type definition is used if the PU has more than one opcode set is incorporated. E.g. at the ARM architecture there is the ARM opcode set (size of 32 bit) and the Thumb opcode set (size of 16 bit). Code compression is a technology where the opcodes are stored in a compressed form and are automatically decompressed before execution. mmt.qualifiedName="ProcessingUnit.opcodeSize";pureMM.maxOccurs="1";pureMM.minOccurs="0" The clock source for the PU. mmt.qualifiedName="puClock.ProcessingUnit";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes the register model of the PU. For each register type availabe one 'Regsiter' element is used to give the number available. mmt.qualifiedName="registerModel.ProcessingUnit";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The following attributes are opcodes, which are not supported by all PUs. The support of this opcodes has an influence on the performance of the PU. - Bit-manipulation - Multiplication - Division - Multiply Accumulate - Floating-point Support In the future further opcodes may be possible. The special opcodes take important influence to the performance index of a PU, but are not main topic of the software development, as far as high level programming languages are used, due to the fact that these are covered by compiler settings, compiler strategies and software libraries where the direct usage or a SW emulation is available for almost any general use case. For some of these opcodes the main advantage is available only at the level of assembler programming or compiler optimization. mmt.qualifiedName="ProcessingUnit.specialOpcodes";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This element provides a list of all supported data types and its according data sizes of the described PU. mmt.qualifiedName="supportedDataType.ProcessingUnit";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A ProcessingUnit describes the plain processor core. The identifier provides the actual type name of the processing unit. mmt.qualifiedName="ProcessingUnit" atpObject mmt.qualifiedName="ProgCode" atpObject Describes one volatile memory segment. mmt.qualifiedName="ProvidedMemorySegment" atpObject Some memory architectures are organised for bigger natural data size than accessed by the PU. In this case memory might not be used completely and some memory locations are left blank due to misalignment. The overall memory size is not used by code or data. Misalignment may be recovered by special mechanisms provided by hardware or software. In this case the access time will be increased. Certain PU architectures do not allow misalignment in code or data generally. Unit: Byte mmt.qualifiedName="ProvidedMemorySegment.alignment";pureMM.maxOccurs="1";pureMM.minOccurs="0" The error detection and error correction facilities provided by the memory segment itself. mmt.qualifiedName="architecturalQuality.ProvidedMemorySegment";pureMM.maxOccurs="1";pureMM.minOccurs="0" As memory holds the executable program as well as the according data, memory needs a level of quality and reliability according to the purpose of the ECU. In most applications today memory is the biggest homogeneous hardware block; therefore quality and reliability of memory have the biggest impact on ECU performance and availability. With the introduction of non-volatile memory and the use of huge DRAM memories the aspect of quality and reliability gains more importance. Despite all Zero-defect programs of the semiconductor suppliers a defect rate in the range of 1 to 5 ppm must be considered as given even for critical applications. Separate quality data for Endurance and Data retention can be available also. The biggest value for ppm rates is used as a quality factor. Unit: ppm mmt.qualifiedName="ProvidedMemorySegment.manufacturingQuality";pureMM.maxOccurs="1";pureMM.minOccurs="0" A value that determines the amount of bytes within the memory segment. An ECU for AUTOSAR always contains at least one memory segment. Within a single ECU different memory types and access types can be used simultaneously. An ECU may consist of different parts that carry one or more memories. Segment size is defined in the terms of Bytes. The overall amount of memory is the sum of all available memory segments. For different types of memory only the sum of the same type gives a useful overall sum. Unit: Byte mmt.qualifiedName="ProvidedMemorySegment.segmentSize";pureMM.maxOccurs="1";pureMM.minOccurs="1" Separate memories are required for safety-relevant functions and redundancy requirements. mmt.qualifiedName="ProvidedMemorySegment.separate";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes one volatile memory segment. mmt.qualifiedName="ProvidedMemorySegment" atpObject Describes one non-volatile memory segment. mmt.qualifiedName="ProvidedNVMemorySegment" atpObject Program and erase cycles are a stress to the memory cell, therefore endurance is characterised by the number of erase/program cycles the memory can survive exceeding the prescribed failure rate. Unit: No of cycles. mmt.qualifiedName="ProvidedNVMemorySegment.dataEndurance";pureMM.maxOccurs="1";pureMM.minOccurs="0" Data retention time is the time between programming a sample of non-volatile memory and the observation of a prescribed failure rate when verifying the programmed pattern. The time is dependent on the chosen technology for the integrated memory cell. Unit: Years mmt.qualifiedName="ProvidedNVMemorySegment.dataRetention";pureMM.maxOccurs="1";pureMM.minOccurs="0" Additional to verify, all data are read back with a different set-up of the threshold of the sense amplifier of the programmed cell. With this method besides the logical correctness, the sufficient amount of electrical charges, which represents the stored data is checked. Furthermore the content of the memory and the correctness and the quality of the programming tools can be verified. Performing the margin read allow the prediction of the data retention. The feature of margin read is a characteristic of a memory, which is not available at all devices. Margin read is available for flash technology only. mmt.qualifiedName="ProvidedNVMemorySegment.marginReadAvailable";pureMM.maxOccurs="1";pureMM.minOccurs="0" For an erasable memory it's usually the same size of the segment as for the segment size which can be erased at a time. If the size of an erasable segment is different shall the size of the erasable segment be entered in the table. Unit: Byte mmt.qualifiedName="ProvidedNVMemorySegment.segmentSizeErase";pureMM.maxOccurs="1";pureMM.minOccurs="0" Some memory types have not the same segment size as in the case when data is written to the memory. For example, a specific flash memory you must write 128 bytes once even if the segment size is 16 kBytes. Unit: Byte mmt.qualifiedName="ProvidedNVMemorySegment.segmentSizeWrite";pureMM.maxOccurs="1";pureMM.minOccurs="0" Describes one non-volatile memory segment. mmt.qualifiedName="ProvidedNVMemorySegment" atpObject Common elements for PWM, PWD and CCU. mmt.qualifiedName="PulseWidthPeripheral" atpObject Defines the data width of the counter. Unit: Bits mmt.qualifiedName="PulseWidthPeripheral.resolution";pureMM.maxOccurs="1";pureMM.minOccurs="1" Communication attributes specific to queued receiving. mmt.qualifiedName="QueuedReceiverComSpec" atpObject Length of queue for received events. mmt.qualifiedName="QueuedReceiverComSpec.queueLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" Communication attributes specific to queued receiving. mmt.qualifiedName="QueuedReceiverComSpec" atpObject Communication attributes specific to distribution of events (P-Port, sender-receiver interface and data element carries an "event"). mmt.qualifiedName="QueuedSenderComSpec" atpObject Component port requiring a certain port interface. mmt.qualifiedName="RPortPrototype" atpObject,atpPrototype Required communication attributes, one for each interface element. mmt.qualifiedName="requiredComSpec.RPortPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The interface that this port requires, i.e. the port depends on another port providing the specified interface. mmt.qualifiedName="rPort.requiredInterface";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType Component port requiring a certain port interface. mmt.qualifiedName="RPortPrototype" atpObject,atpPrototype Abstract base class for all RTE-related events mmt.qualifiedName="RTEEvent" atpObject Provides the means to describe the Modes this RTEEvent can be disabled by. mmt.qualifiedName="modeDependency.RTEEvent";pureMM.maxOccurs="1";pureMM.minOccurs="0" Runnable starts when event occurs mmt.qualifiedName="RTEEvent.startOnEvent";pureMM.maxOccurs="1";pureMM.minOccurs="0" Abstract class for specifying a range from lower limit to upper limit. mmt.qualifiedName="Range" atpObject This element specifies the lower limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="Range.lowerLimit";pureMM.maxOccurs="1";pureMM.minOccurs="1" This element specifies the upper limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="Range.upperLimit";pureMM.maxOccurs="1";pureMM.minOccurs="1" Constant description for real values. mmt.qualifiedName="RealLiteral" atpObject,atpPrototype The numeric value itself. mmt.qualifiedName="RealLiteral.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Constant description for real values. mmt.qualifiedName="RealLiteral" atpObject,atpPrototype This represents a range of reals that can be represented by either the IEEE 754 "Single Precision" (encoding is "Single") or IEEE 754 "Double Precision" (encoding is "Double") arithmetic. Note that these standards include representations for +infinity, -infinity, QNaN and SNaN. When defining a RealType, one must indicate whether these special values are allowed or not. mmt.qualifiedName="RealType" atpObject,atpType Denotes whether this data type permits for "not a number" being represented by the type mmt.qualifiedName="RealType.allowNaN";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.name="ALLOW-NAN" Denotes the precision of the RealType mmt.qualifiedName="RealType.encoding";pureMM.maxOccurs="1";pureMM.minOccurs="1" This represents a range of reals that can be represented by either the IEEE 754 "Single Precision" (encoding is "Single") or IEEE 754 "Double Precision" (encoding is "Double") arithmetic. Note that these standards include representations for +infinity, -infinity, QNaN and SNaN. When defining a RealType, one must indicate whether these special values are allowed or not. mmt.qualifiedName="RealType" atpObject,atpType Annotation of a receiver port, specifying properties of data elements that don't affect communication or generation of the RTE. The given attributes are requirements on the required data. mmt.qualifiedName="ReceiverAnnotation" atpObject The maximum allowed age of the signal since it was originally read by a sensor. This is a requirement specified on the receiver side. mmt.qualifiedName="ReceiverAnnotation.signalAge";pureMM.maxOccurs="1";pureMM.minOccurs="1" Annotation of a receiver port, specifying properties of data elements that don't affect communication or generation of the RTE. The given attributes are requirements on the required data. mmt.qualifiedName="ReceiverAnnotation" atpObject Receiver specific communication attributes (R-Port and sender-receiver interface). mmt.qualifiedName="ReceiverComSpec" atpObject Data element these attributes belong to. mmt.qualifiedName="ReceiverComSpec.dataElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" The DataFilter associated with this ReceiverComSpec. mmt.qualifiedName="filter.ReceiverComSpec";pureMM.maxOccurs="1";pureMM.minOccurs="0" This indicates whether the corresponding dataElement shall be transmitted using end-to-end protection. mmt.qualifiedName="ReceiverComSpec.usesEndToEndProtection";pureMM.maxOccurs="1";pureMM.minOccurs="1" An element in a record. mmt.qualifiedName="RecordElement" atpObject,atpPrototype mmt.qualifiedName="RecordElementRef" atpObject mmt.qualifiedName="RecordElementRef.recordElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="RecordElementRef" atpObject mmt.qualifiedName="RecordElementRef_RecordElement" atpObject,instanceRef mmt.qualifiedName="RecordElementRef_RecordElement.compositionComponentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="RecordElementRef_RecordElement.componentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="RecordElementRef_RecordElement.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="RecordElementRef_RecordElement.dataElementPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.context mmt.qualifiedName="RecordElementRef_RecordElement.recordElement";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="50" instanceRef.target mmt.qualifiedName="RecordElementRef_RecordElement" atpObject,instanceRef mmt.qualifiedName="RecordSpecification" atpObject,atpPrototype Elements of the record. mmt.qualifiedName="element.RecordSpecification";pureMM.maxOccurs="-1";pureMM.minOccurs="0" mmt.qualifiedName="RecordSpecification" atpObject,atpPrototype mmt.qualifiedName="RecordType" atpObject,atpType This represents the collection of RecordElements that make up the RecordType. mmt.qualifiedName="element.RecordType";pureMM.maxOccurs="-1";pureMM.minOccurs="1" mmt.qualifiedName="RecordType" atpObject,atpType Specify references within the ECU Configuration Description between parameter containers. mmt.qualifiedName="ReferenceParamDef" atpObject Exactly one reference to an parameter container is allowed as destination. mmt.qualifiedName="ReferenceParamDef.destination";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specify references within the ECU Configuration Description between parameter containers. mmt.qualifiedName="ReferenceParamDef" atpObject Used to represent a configuration value that has a parameter definition of type ConfigReference (used for all of its specializations excluding InstanceReferenceParamDef). mmt.qualifiedName="ReferenceValue" atpObject Specifes the destination of the reference. mmt.qualifiedName="ReferenceValue.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Used to represent a configuration value that has a parameter definition of type ConfigReference (used for all of its specializations excluding InstanceReferenceParamDef). mmt.qualifiedName="ReferenceValue" atpObject The user available registers are a part of the programming model that consists of: Memory organisation and segmentation, Data types, Registers, Instruction format, Operand selection, Interrupts and exceptions. Basically the register model contains the registers that are interest to the applications programmer; these registers can be grouped into three basic categories: - General registers: These general-purpose registers are used primarily to contain operands for arithmetic and logical operations. - Segment registers: These special-purpose registers permit software designers to choose either a flat or segmented model of memory organisation. These registers determine, at any given time, which segments of memory are currently addressable. - Status and instruction registers: These special-purpose registers are used to record and alter certain aspects of the processor state. The register model is only valuable data for low level programming, e.g assembler programming. The register model, along with the available OP codes takes influence on the performance of the PU. The most general impact of the register model to software is number of registers which have to be handled during interrupts or function calls. mmt.qualifiedName="Register" atpObject Describes how many registers are available of the specified type. mmt.qualifiedName="Register.count";pureMM.maxOccurs="1";pureMM.minOccurs="1" Describes the kind of register. mmt.qualifiedName="Register.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" The user available registers are a part of the programming model that consists of: Memory organisation and segmentation, Data types, Registers, Instruction format, Operand selection, Interrupts and exceptions. Basically the register model contains the registers that are interest to the applications programmer; these registers can be grouped into three basic categories: - General registers: These general-purpose registers are used primarily to contain operands for arithmetic and logical operations. - Segment registers: These special-purpose registers permit software designers to choose either a flat or segmented model of memory organisation. These registers determine, at any given time, which segments of memory are currently addressable. - Status and instruction registers: These special-purpose registers are used to record and alter certain aspects of the processor state. The register model is only valuable data for low level programming, e.g assembler programming. The register model, along with the available OP codes takes influence on the performance of the PU. The most general impact of the register model to software is number of registers which have to be handled during interrupts or function calls. mmt.qualifiedName="Register" atpObject Maximum allowable deviation mmt.qualifiedName="RelativeTolerance" atpObject Maximum allowable deviation in percent mmt.qualifiedName="RelativeTolerance.relative";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum allowable deviation mmt.qualifiedName="RelativeTolerance" atpObject Specification of a sending behavior where the transmission order is predefined, e.g. used on LIN buses mmt.qualifiedName="RelativelyScheduledTiming" atpObject Relative delay between this frame and the start of the successor frame in the schedule table in seconds. mmt.qualifiedName="RelativelyScheduledTiming.delay";pureMM.maxOccurs="1";pureMM.minOccurs="1" Relative position of the frame described by this timing in the schedule table mmt.qualifiedName="RelativelyScheduledTiming.positionInTable";pureMM.maxOccurs="1";pureMM.minOccurs="1" The master task transmits frame headers based on a schedule table. The master application may use different schedule tables and select among them. mmt.qualifiedName="RelativelyScheduledTiming.scheduleTable";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specification of a sending behavior where the transmission order is predefined, e.g. used on LIN buses mmt.qualifiedName="RelativelyScheduledTiming" atpObject <remark> is used for comments e.g. on the specific calibration state. The remark can be a regular paragraph or a preformatted text. mmt.qualifiedName="Remark" atpMixed,atpObject Use <p> to create a paragraph for continuous texts. mmt.qualifiedName="Remark.p";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" <verbatim> is a paragraph in which white-space (in particular blanks and line feeds) is obeyed. This enables basic preformatting to be carried out, which can even be displayed on simple devices. Behavior is the same as PRE in HTML . mmt.qualifiedName="Remark.verbatim";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" <remark> is used for comments e.g. on the specific calibration state. The remark can be a regular paragraph or a preformatted text. mmt.qualifiedName="Remark" atpMixed,atpObject This feature is used for input signals only. Each time the level of the associated data-element changes a dedicated GET operation has to be invoked by the sensor software component, i.e. an appropriate runnable has to be started. mmt.qualifiedName="ReportFeature" atpObject Specification of a request driven sending behavior. Semantics of this communication mechanism is that basic software stores values but does not send it out until a frame requesting the information is received. mmt.qualifiedName="RequestControlledTiming" atpObject Number of repetitions the frame is sent for a single request mmt.qualifiedName="RequestControlledTiming.finalRepetitions";pureMM.maxOccurs="1";pureMM.minOccurs="0" Specification of the time that is needed before the frame can be sent after the requests arrival mmt.qualifiedName="responseTime.RequestControlledTiming";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specification of a request driven sending behavior. Semantics of this communication mechanism is that basic software stores values but does not send it out until a frame requesting the information is received. mmt.qualifiedName="RequestControlledTiming" atpObject Description of consumed resources by one implementation of a software. mmt.qualifiedName="ResourceConsumption" atpObject Collection of the execution time descriptions for the runnable entities of this implementation. mmt.qualifiedName="executionTime.ResourceConsumption";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Collection of the heap memory allocated by this implementation. mmt.qualifiedName="heapUsage.ResourceConsumption";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Provides additional information to the sections of the object-file containing the implementation of the SW-Component mmt.qualifiedName="objectFileSection.ResourceConsumption";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Collection of the stack memory usage for each runnable entity of this implementation. mmt.qualifiedName="stackUsage.ResourceConsumption";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Description of consumed resources by one implementation of a software. mmt.qualifiedName="ResourceConsumption" atpObject This class specifies an assignment of a role to a particular P-Port. This port must contain a service which is inside of the component and called by outside entity in order to handle a particular issue (e.g. a communication event). This is often named as callback. mmt.qualifiedName="RoleBasedPPortAssignment" atpObject Port which provides the software component to be connected to an AUTOSAR Service. mmt.qualifiedName="RoleBasedPPortAssignment.pPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" This is the role of the assigned Port in the given context. The value must be a name of a PortInterface as standardized in the Software Specification of the related AUTOSAR Service. mmt.qualifiedName="RoleBasedPPortAssignment.role";pureMM.maxOccurs="1";pureMM.minOccurs="1" This class specifies an assignment of a role to a particular P-Port. This port must contain a service which is inside of the component and called by outside entity in order to handle a particular issue (e.g. a communication event). This is often named as callback. mmt.qualifiedName="RoleBasedPPortAssignment" atpObject This class specifies an assignment of a role to a particular R-Port. This port must contain a service which is outside of the component and called by the component in order to handle a particular issue (e.g. a communication event). mmt.qualifiedName="RoleBasedRPortAssignment" atpObject Port which requires the software component to be connected to an AUTOSAR Service. mmt.qualifiedName="RoleBasedRPortAssignment.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" This is the role the assigned Port in given context. The value must be a name of a PortInterface as standardized in Software Specification of the related AUTOSAR Service. mmt.qualifiedName="RoleBasedRPortAssignment.role";pureMM.maxOccurs="1";pureMM.minOccurs="1" This class specifies an assignment of a role to a particular R-Port. This port must contain a service which is outside of the component and called by the component in order to handle a particular issue (e.g. a communication event). mmt.qualifiedName="RoleBasedRPortAssignment" atpObject Rough estimation of the heap usage. mmt.qualifiedName="RoughEstimateHeapUsage" atpObject Rough estimate of the heap usage. mmt.qualifiedName="RoughEstimateHeapUsage.memoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" Rough estimation of the heap usage. mmt.qualifiedName="RoughEstimateHeapUsage" atpObject Provides a description of a rough estimate on the ExecutionTime. mmt.qualifiedName="RoughEstimateOfExecutionTime" atpObject Provides description on the rough estimate of the ExecutionTime. mmt.qualifiedName="RoughEstimateOfExecutionTime.description";pureMM.maxOccurs="1";pureMM.minOccurs="1" Provides a description of a rough estimate on the ExecutionTime. mmt.qualifiedName="RoughEstimateOfExecutionTime" atpObject Rough estimation of the stack usage. mmt.qualifiedName="RoughEstimateStackUsage" atpObject Rough estimate of the stack usage. mmt.qualifiedName="RoughEstimateStackUsage.memoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" Rough estimation of the stack usage. mmt.qualifiedName="RoughEstimateStackUsage" atpObject The runnable entities are the smallest code-fragments that are provided by the component and are executed in the RTE. Runnables are for instance set up to respond to data reception or operation invocation on a server. mmt.qualifiedName="RunnableEntity" atpObject Optional reference to the corresponding BswModuleEntity in case the RunnableEntity is implemented as part of a BSW module (in the case of an AUTOSAR Service, a Complex Device Driver or an ECU Abstraction). It can be used by a tool to find relevant information on the behavior, e.g. whether the bswEntity shall be running in interrupt context. mmt.qualifiedName="RunnableEntity.bswEntity";pureMM.maxOccurs="1";pureMM.minOccurs="0" The presence of a calprmAccess implies that a RunnableEntity needs read only access to a CalprmElementPrototype which may either be local or within a PortPrototype. mmt.qualifiedName="RunnableEntity.calprmAccess";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Normally, this is FALSE. When this is TRUE, it is allowed that this runnable entity is invoked concurrently (even for one instance of the SW-C), which implies that it is the responsibility of the implementation of the runnable to take care of this form of concurrency. mmt.qualifiedName="RunnableEntity.canBeInvokedConcurrently";pureMM.maxOccurs="1";pureMM.minOccurs="1" This means that the runnable can enter/leave the referenced exclusive area through explicit API calls. mmt.qualifiedName="RunnableEntity.canEnterExclusiveArea";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Runnable has read access to data element mmt.qualifiedName="dataReadAccess.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Data receive points of this runnable. mmt.qualifiedName="dataReceivePoint.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The runnable has data send point. mmt.qualifiedName="dataSendPoint.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Runnable has write access to data element mmt.qualifiedName="dataWriteAccess.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specifies the time in seconds which two starts of a RunnableEntity are guaranteed to be separated. mmt.qualifiedName="RunnableEntity.minimumStartInterval";pureMM.maxOccurs="1";pureMM.minOccurs="1" The runnable has a mode switch point. mmt.qualifiedName="modeSwitchPoint.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This implements the ability to access a per-instance calibration parameter. mmt.qualifiedName="RunnableEntity.perInstanceCalprmAccess";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Inter-runnable variables that are read by this Runnable. mmt.qualifiedName="RunnableEntity.readVariable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The runnable entity runs inside the referenced exclusive area mmt.qualifiedName="RunnableEntity.runsInsideExclusiveArea";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The runnable has server call point. mmt.qualifiedName="serverCallPoint.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This represents the ability to access a shared calibration parameter. mmt.qualifiedName="RunnableEntity.sharedCalprmAccess";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The symbol describing this runnable's entry point. This is considered the API of the runnable and is required during the RTE contract phase. mmt.qualifiedName="RunnableEntity.symbol";pureMM.maxOccurs="1";pureMM.minOccurs="1" The runnable has wait point. mmt.qualifiedName="waitPoint.runnable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Inter-runnable variables that are written by Runnable. mmt.qualifiedName="RunnableEntity.writtenVariable";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The runnable entities are the smallest code-fragments that are provided by the component and are executed in the RTE. Runnables are for instance set up to respond to data reception or operation invocation on a server. mmt.qualifiedName="RunnableEntity" atpObject Optional definition of a CanId range to reduce the effort of specifying every possible FrameTriggering within the defined Id range during reception. All frames received within a range are mapped to the same Pdu that is passed to a upper layer module (e.g. Nm, CDD, PduR). This range is redundant to the attributes "nmLowerCanId" and "nmUpperCanId" of "CanCluster". For backward compatibility reasons this redundancy shall be preserved and both shall be defined. mmt.qualifiedName="RxIdentifierRange" atpObject This attribute can be used together with the upperCanId attribute to define a range of CanIds. mmt.qualifiedName="RxIdentifierRange.lowerCanId";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute can be used together with the lowerCanId attribute to define a range of CanIds. mmt.qualifiedName="RxIdentifierRange.upperCanId";pureMM.maxOccurs="1";pureMM.minOccurs="1" Optional definition of a CanId range to reduce the effort of specifying every possible FrameTriggering within the defined Id range during reception. All frames received within a range are mapped to the same Pdu that is passed to a upper layer module (e.g. Nm, CDD, PduR). This range is redundant to the attributes "nmLowerCanId" and "nmUpperCanId" of "CanCluster". For backward compatibility reasons this redundancy shall be preserved and both shall be defined. mmt.qualifiedName="RxIdentifierRange" atpObject mmt.qualifiedName="ScaleConstr" atpObject This element specifies a short name for the scaleConstr. This can for example be used to create more specific messages of a constraint checker. The constraints cannot be associated in the metamodel, therefore shortLabel is somehow a substitute for shortName. mmt.qualifiedName="ScaleConstr.shortLabel";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" <desc> represents a general but brief description of the object in question. mmt.qualifiedName="ScaleConstr.desc";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element specifies the lower limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="ScaleConstr.lowerLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This element specifies the upper limit of a closed, half-open or open interval. It can also be set to infinity by setting the attribute INTERVAL-TYPE to INFINITE. No value has to be set in the case of an infinite interval. mmt.qualifiedName="ScaleConstr.upperLimit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" mmt.qualifiedName="ScaleConstr" atpObject Specifies if the values defined by the scales are considered to be valid. If the attribute is missing then the default value is "VALID". mmt.qualifiedName="ScaleConstr.validity";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="ScaleConstr" atpObject mmt.qualifiedName="ScaleConstrs" atpObject mmt.qualifiedName="ScaleConstrs.scaleConstr";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="ScaleConstrs" atpObject This class is a "Special Data" element. By using this element it is possible to extend the model with arbirtrary information. In this case the "role" is specified using gid. mmt.qualifiedName="Sd" atpMixedString,atpObject This attributes specifies an identifier. Gid comes from the SGML-Term "Generic Identifier" which is the element name in XML. The role of this attribute is the same as the name of an XML - element. mmt.qualifiedName="Sd.gid";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" This class is a "Special Data" element. By using this element it is possible to extend the model with arbirtrary information. In this case the "role" is specified using gid. mmt.qualifiedName="Sd" atpMixedString,atpObject Sdg is a generic model which can be used to keep arbitrary information which is not explicitly modeled in the metamodel. Sdg can have various contets as defined by sdgContentsType. Special Data should only be used moderately since all elements should be defined in the metamodel. Thereby SDG should be considered as a temporary solution when no explicit model is available. If an sdgCaption is available, it is possible to establish a reference to the sdg structure. mmt.qualifiedName="Sdg" atpObject this aggregation allows to assign the properties of Identifiable to the sdg. By this, a shortName etc. can be assigned to the Sdg. mmt.qualifiedName="Sdg.sdgCaption";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This association allows to reuse an already exisiting caption. mmt.qualifiedName="Sdg.sdgCaptionRef";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.name="SDG-CAPTION-REF";xml.sequenceOffset="25" Sdg is a generic model which can be used to keep arbitrary information which is not explicitly modeled in the metamodel. Sdg can have various contets as defined by sdgContentsType. Special Data should only be used moderately since all elements should be defined in the metamodel. Thereby SDG should be considered as a temporary solution when no explicit model is available. If an sdgCaption is available, it is possible to establish a reference to the sdg structure. mmt.qualifiedName="Sdg" atpObject This attributes specifies an identifier. Gid comes from the SGML-Term "Generic Identifier" which is the element name in XML. The role of this attribute is the same as the name of an XML - element. mmt.qualifiedName="Sdg.gid";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" Sdg is a generic model which can be used to keep arbitrary information which is not explicitly modeled in the metamodel. Sdg can have various contets as defined by sdgContentsType. Special Data should only be used moderately since all elements should be defined in the metamodel. Thereby SDG should be considered as a temporary solution when no explicit model is available. If an sdgCaption is available, it is possible to establish a reference to the sdg structure. mmt.qualifiedName="Sdg" atpObject mmt.qualifiedName="SdgCaption" atpObject mmt.qualifiedName="SdgContents" atpMixed,atpObject This allows to refer to any identifiable object from within an Sdg. mmt.qualifiedName="SdgContents.sdx";pureMM.maxOccurs="1";pureMM.minOccurs="0" This is one particular special data element. mmt.qualifiedName="SdgContents.sd";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This aggregation allows to create an arbitrary structuring of Sdg. mmt.qualifiedName="SdgContents.sdg";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" mmt.qualifiedName="SdgContents" atpMixed,atpObject This is a class which allows to refer to any identifiable object. It could be modeled as an association to Identifiable. But for compatibility reasons to ASAM it is left as it is. mmt.qualifiedName="Sdx" atpMixedString,atpObject This attributes specifies an identifier. Gid comes from the SGML-Term "Generic Identifier" which is the element name in XML. The role of this attribute is the same as the name of an XML - element. mmt.qualifiedName="Sdx.gid";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" This specifies the class of the referenced object. mmt.qualifiedName="Sdx.idClass";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" This is a class which allows to refer to any identifiable object. It could be modeled as an association to Identifiable. But for compatibility reasons to ASAM it is left as it is. mmt.qualifiedName="Sdx" atpMixedString,atpObject The StaticPart and the DynamicPart can be separated in multiple segments within the multiplexed PDU. The ISignalIPdus are copied bit by bit into the MultiplexedIPdu. If the space of the first segment is 5 bits large than the first 5 bits of the ISignalIPdu are copied into this first segment and so on. mmt.qualifiedName="SegmentPosition" atpObject This attribute defines the order of the bytes of the segment and the packing into the MultiplexedIPdu. The byte ordering "Little Endian" (MostSignificantByteLast) and "Big Endian" (MostSignificantByteFirst) can be selected. A mix between Little Endian and Big Endian within a MultiplexedIPdu (staticPart, dynamicPart, selectorField) is not allowed. mmt.qualifiedName="SegmentPosition.segmentByteOrder";pureMM.maxOccurs="1";pureMM.minOccurs="1" Data Length of the segment in bits. mmt.qualifiedName="SegmentPosition.segmentLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" Segments bit position relatively to the beginning of a multiplexed IPdu. Note that the absolute position of the segment in the MultiplexedIPdu is determined by the definition of the segmentByteOrder attribute of the SegmentPosition. If Big Endian is specified, the start position indicates the bit position of the most significant bit in the IPdu. If Little Endian is specified, the start position indicates the bit position of the least significant bit in the IPdu. mmt.qualifiedName="SegmentPosition.segmentPosition";pureMM.maxOccurs="1";pureMM.minOccurs="1" The StaticPart and the DynamicPart can be separated in multiple segments within the multiplexed PDU. The ISignalIPdus are copied bit by bit into the MultiplexedIPdu. If the space of the first segment is 5 bits large than the first 5 bits of the ISignalIPdu are copied into this first segment and so on. mmt.qualifiedName="SegmentPosition" atpObject Annotation of a sender port, specifying properties of data elements that don't affect communication or generation of the RTE. mmt.qualifiedName="SenderAnnotation" atpObject Communication attributes for a sender port (P-Port and sender-receiver interface). mmt.qualifiedName="SenderComSpec" atpObject Data element these quality of service attributes apply to. mmt.qualifiedName="SenderComSpec.dataElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" Requested transmission acknowledgement for data element. mmt.qualifiedName="transmissionAcknowledge.SenderComSpec";pureMM.maxOccurs="1";pureMM.minOccurs="0" This indicates whether the corresponding dataElement shall be transmitted using end-to-end protection. mmt.qualifiedName="SenderComSpec.usesEndToEndProtection";pureMM.maxOccurs="1";pureMM.minOccurs="1" The ArrayElement may be a primitive one or a composite one. If the element is primitive, it will be mapped to the "SystemSignal" (multiplicity 1). If the element is composite, there will be no mapping to the "SystemSignal" (multiplicity 0). In this case the "ArrayElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive array element is mapped the indexed element always needs to be specified. mmt.qualifiedName="SenderRecArrayElementMapping" atpObject This aggregation will be used if the element is composite. mmt.qualifiedName="complexTypeMapping.SenderRecArrayElementMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to an indexed array element in the context of the dataElement or in the context of a composite element. mmt.qualifiedName="indexedArrayElement.SenderRecArrayElementMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the system signal used to carry the primitive ArrayElement. mmt.qualifiedName="SenderRecArrayElementMapping.signal";pureMM.maxOccurs="1";pureMM.minOccurs="0" The ArrayElement may be a primitive one or a composite one. If the element is primitive, it will be mapped to the "SystemSignal" (multiplicity 1). If the element is composite, there will be no mapping to the "SystemSignal" (multiplicity 0). In this case the "ArrayElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive array element is mapped the indexed element always needs to be specified. mmt.qualifiedName="SenderRecArrayElementMapping" atpObject If the compositeType is an Array, the "ArrayTypeMapping" will be used. mmt.qualifiedName="SenderRecArrayTypeMapping" atpObject Each ArrayElement must be mapped on a SystemSignal. mmt.qualifiedName="arrayElementMapping.SenderRecArrayTypeMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" If the compositeType is an Array, the "ArrayTypeMapping" will be used. mmt.qualifiedName="SenderRecArrayTypeMapping" atpObject Mapping of a primitive record element to a SystemSignal. If the element is composite, there will be no mapping (multiplicity 0). In this case the "RecordElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive record element is mapped the record element always needs to be specified. mmt.qualifiedName="SenderRecRecordElementMapping" atpObject This aggregation will be used if the element is composite. mmt.qualifiedName="complexTypeMapping.SenderRecRecordElementMapping";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to a RecordElement in the context of the dataElement or in the context of a composite element. mmt.qualifiedName="SenderRecRecordElementMapping.recordElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the system signal used to carry the primitive RecordElement. mmt.qualifiedName="SenderRecRecordElementMapping.signal";pureMM.maxOccurs="1";pureMM.minOccurs="0" Mapping of a primitive record element to a SystemSignal. If the element is composite, there will be no mapping (multiplicity 0). In this case the "RecordElementMapping" Element will aggregate the "TypeMapping" Element. In that way also the composite datatypes can be mapped to SystemSignals. Regardless whether composite or primitive record element is mapped the record element always needs to be specified. mmt.qualifiedName="SenderRecRecordElementMapping" atpObject If the compositeType is a Record, the "RecordTypeMapping" will be used. mmt.qualifiedName="SenderRecRecordTypeMapping" atpObject Each RecordElement must be mapped on a SystemSignal. mmt.qualifiedName="recordElementMapping.SenderRecRecordTypeMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" If the compositeType is a Record, the "RecordTypeMapping" will be used. mmt.qualifiedName="SenderRecRecordTypeMapping" atpObject Annotation of the data elements in a port that realizes a sender/receiver interface. mmt.qualifiedName="SenderReceiverAnnotation" atpObject Flag whether this data element was not measured directly but instead was calculated from possibly several other measured or calculated values. mmt.qualifiedName="SenderReceiverAnnotation.computed";pureMM.maxOccurs="1";pureMM.minOccurs="1" The instance of data element annotated. mmt.qualifiedName="SenderReceiverAnnotation.dataElement";pureMM.maxOccurs="1";pureMM.minOccurs="1" This min or max has not to be mismatched with the min- and max for data-value in a CompuMethod. For example, this annotation shows when the result of the calculation performed in a RunnableEntity owned by one AtomicSoftwareComponentType is transmitted to another AtomicSoftwareComponentType whose RunnableEntity will use this value as a limit, e.g. the max.power which can be used by that software-component, or the current min. slip. mmt.qualifiedName="SenderReceiverAnnotation.limitKind";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute indicates how the data is processed according to the PorcessingKind. mmt.qualifiedName="SenderReceiverAnnotation.processingKind";pureMM.maxOccurs="1";pureMM.minOccurs="1" A sender/receiver interface declares a number of data elements to be sent and received. mmt.qualifiedName="SenderReceiverInterface" atpObject,atpType The dataelements of this sender/receiver interface. mmt.qualifiedName="dataElement.interface";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Modes which may be communicated via this interface. mmt.qualifiedName="modeGroup.interface";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A sender/receiver interface declares a number of data elements to be sent and received. mmt.qualifiedName="SenderReceiverInterface" atpObject,atpType Mapping of a sender receiver communication data element with a composite datatype to a signal group. mmt.qualifiedName="SenderReceiverToSignalGroupMapping" atpObject Reference to the data element, which ought to be sent over the Communication bus. Reference to a data element with a composite datatype which is mapped to a signal group. mmt.qualifiedName="dataElement.SenderReceiverToSignalGroupMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the signal group, which contain all primitive datatypes of the composite type mmt.qualifiedName="SenderReceiverToSignalGroupMapping.signalGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="typeMapping.SenderReceiverToSignalGroupMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Mapping of a sender receiver communication data element with a composite datatype to a signal group. mmt.qualifiedName="SenderReceiverToSignalGroupMapping" atpObject mmt.qualifiedName="SenderReceiverToSignalGroupMapping_dataElement" atpObject,instanceRef mmt.qualifiedName="SenderReceiverToSignalGroupMapping_dataElement.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SenderReceiverToSignalGroupMapping_dataElement.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SenderReceiverToSignalGroupMapping_dataElement.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="SenderReceiverToSignalGroupMapping_dataElement.dataElement";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.target mmt.qualifiedName="SenderReceiverToSignalGroupMapping_dataElement" atpObject,instanceRef Mapping of a sender receiver communication data element with a primitive datatype to a signal. If the data element has to be transmitted to several receivers there is still exactly one mapping defined. In case of 1:n communication the DataElementPrototype in the ProvidePort of the ComponentPrototype is still mapped to only one SystemSignal. mmt.qualifiedName="SenderReceiverToSignalMapping" atpObject Reference to the data element, which ought to be sent over the Communication bus. This DataElement is described in the Software Component Template. mmt.qualifiedName="dataElement.SenderReceiverToSignalMapping";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the system signal used to carry the data element. mmt.qualifiedName="SenderReceiverToSignalMapping.signal";pureMM.maxOccurs="1";pureMM.minOccurs="1" Mapping of a sender receiver communication data element with a primitive datatype to a signal. If the data element has to be transmitted to several receivers there is still exactly one mapping defined. In case of 1:n communication the DataElementPrototype in the ProvidePort of the ComponentPrototype is still mapped to only one SystemSignal. mmt.qualifiedName="SenderReceiverToSignalMapping" atpObject mmt.qualifiedName="SenderReceiverToSignalMapping_dataElement" atpObject,instanceRef mmt.qualifiedName="SenderReceiverToSignalMapping_dataElement.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SenderReceiverToSignalMapping_dataElement.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SenderReceiverToSignalMapping_dataElement.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="SenderReceiverToSignalMapping_dataElement.dataElement";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.target mmt.qualifiedName="SenderReceiverToSignalMapping_dataElement" atpObject,instanceRef The common attributes for sensors and actuators. The sensor and actuators can be connected via a Peripheral HW Port, a Communication HW Port or a Power Driver HW Port. mmt.qualifiedName="SensorActuatorHW" atpObject Defines the error in the representation of the Technical Signal in the data format This applies only if the Technical Signal is encoded before it is transferred to the ECU Electronics (e.g. via Communication Transceiver HW Port). mmt.qualifiedName="SensorActuatorHW.accuracy";pureMM.maxOccurs="1";pureMM.minOccurs="1" The time the sensor/actuator must be accessed for correct information. It is possible to give a minimum, a maximum and a typical cycle time. mmt.qualifiedName="cycleTime.SensorActuatorHW";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the granularity of the representation of the Technical Signal in the data format. This applies only if the Technical Signal is encoded before it is transferred to the ECU Electronics (e.g. via Communication Transceiver HW Port). mmt.qualifiedName="SensorActuatorHW.resolution";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the general type of the sensor/actuator type is a most common naming for a sensor/actuator and is an open list and is not restricted to the following items. Several sets of types exist. Type is mandatory for the usage of the template - Sensor: Temperature, Pressure, Distance, Hall - Actuator: DC Motor, Valve, Relay, Display mmt.qualifiedName="SensorActuatorHW.type";pureMM.maxOccurs="1";pureMM.minOccurs="1" The SensorActuatorSoftwareComponentType introduces the possibility to link from the software representation of a sensor/actuator to its hardware description provided by the ECU Resource Template. mmt.qualifiedName="SensorActuatorSoftwareComponentType" atpObject,atpType Reference from the Sensor Actuator Software Component Type to the description of the actual hardware. mmt.qualifiedName="SensorActuatorSoftwareComponentType.sensorActuator";pureMM.maxOccurs="1";pureMM.minOccurs="1" The SensorActuatorSoftwareComponentType introduces the possibility to link from the software representation of a sensor/actuator to its hardware description provided by the ECU Resource Template. mmt.qualifiedName="SensorActuatorSoftwareComponentType" atpObject,atpType HW Element Sensor definition. mmt.qualifiedName="SensorHW" atpObject Defines the quality of the data received from a sensor. Depending on this information later processing on the signal has to be done in HW or SW. mmt.qualifiedName="SensorHW.signalQuality";pureMM.maxOccurs="1";pureMM.minOccurs="1" HW Element Sensor definition. mmt.qualifiedName="SensorHW" atpObject The SeparateSignalPath describes that two SwcToSwcSignals and/or SwcToSwcOperationArguments must not take the same way (Signal Path) in the topology (e.g. Redundancy). mmt.qualifiedName="SeparateSignalPath" atpObject The SwcToSwcOperationArguments that must not take the same way (Signal Path) in the topology. mmt.qualifiedName="operation.SeparateSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The SwcToSwcSignals that must not take the same way (Signal Path) in the topology. mmt.qualifiedName="signal.SeparateSignalPath";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The SeparateSignalPath describes that two SwcToSwcSignals and/or SwcToSwcOperationArguments must not take the same way (Signal Path) in the topology (e.g. Redundancy). mmt.qualifiedName="SeparateSignalPath" atpObject The purpose of sequence counters is to map a response to the correct request of a known client. mmt.qualifiedName="SequenceCounterMapping" atpObject Reference to the SystemSignal with the SequenceCounter. mmt.qualifiedName="SequenceCounterMapping.systemSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" The purpose of sequence counters is to map a response to the correct request of a known client. mmt.qualifiedName="SequenceCounterMapping" atpObject When a runnable has a serverCallPoint, it has the possibility to invoke any of the operations of a specific rport of the component. mmt.qualifiedName="ServerCallPoint" atpObject The operation that is called by this runnable. mmt.qualifiedName="operation.ServerCallPoint";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.roleWrapperElement="true" Time in seconds before the server call times out and returns with an error message. It depends on the call type (synchronous or asynchronous) how this is reported. mmt.qualifiedName="ServerCallPoint.timeout";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="ServerCallPoint_operation" atpObject,instanceRef mmt.qualifiedName="ServerCallPoint_operation.rPortPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ServerCallPoint_operation.operationPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="ServerCallPoint_operation" atpObject,instanceRef Communication attributes for a server port (P-Port and client-server interface). mmt.qualifiedName="ServerComSpec" atpObject Operation these communication attributes apply to. mmt.qualifiedName="ServerComSpec.operation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Length of call queue on the server side. The queue is implemented by the RTE. mmt.qualifiedName="ServerComSpec.queueLength";pureMM.maxOccurs="1";pureMM.minOccurs="1" Communication attributes for a server port (P-Port and client-server interface). mmt.qualifiedName="ServerComSpec" atpObject Each service in an ECU is represented by exactly one ServiceComponentPrototype. Instances of this class are only to be created in ECU Configuration phase for the specific purpose of the service configuration. mmt.qualifiedName="ServiceComponentPrototype" atpObject,atpPrototype This represents the ServiceComponentType used to type the ServiceComponentPrototype. mmt.qualifiedName="ServiceComponentPrototype.serviceComponent";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType Each service in an ECU is represented by exactly one ServiceComponentPrototype. Instances of this class are only to be created in ECU Configuration phase for the specific purpose of the service configuration. mmt.qualifiedName="ServiceComponentPrototype" atpObject,atpPrototype ServiceComponentType is used for configuring services for a given ECU. Instances of this class are only to be created in ECU Configuration phase for the specific purpose of the service configuration. mmt.qualifiedName="ServiceComponentType" atpObject,atpType Reference from the ServiceComponentType to the Basic Software Module Description describing the BSW part of the Service Component. mmt.qualifiedName="ServiceComponentType.bswModuleDescription";pureMM.maxOccurs="-1";pureMM.minOccurs="0" ServiceComponentType is used for configuring services for a given ECU. Instances of this class are only to be created in ECU Configuration phase for the specific purpose of the service configuration. mmt.qualifiedName="ServiceComponentType" atpObject,atpType A ServiceConnectorPrototype connects a PortPrototype owned by an ComponentPrototype with the service PortPrototype owned by the ServiceComponentPrototype. A ServiceConnectorPrototype is only added to the model in ECU Configuration phase for the specific purpose of configuring services within an EcuSwComposition. mmt.qualifiedName="ServiceConnectorPrototype" atpObject,atpStructureElement Service port to be connected on application component side mmt.qualifiedName="applicationPort.ServiceConnectorPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" Service port to be connected on service component side mmt.qualifiedName="servicePort.ServiceConnectorPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1" A ServiceConnectorPrototype connects a PortPrototype owned by an ComponentPrototype with the service PortPrototype owned by the ServiceComponentPrototype. A ServiceConnectorPrototype is only added to the model in ECU Configuration phase for the specific purpose of configuring services within an EcuSwComposition. mmt.qualifiedName="ServiceConnectorPrototype" atpObject,atpStructureElement mmt.qualifiedName="ServiceConnectorPrototype_applicationPort" atpObject,instanceRef mmt.qualifiedName="ServiceConnectorPrototype_applicationPort.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ServiceConnectorPrototype_applicationPort.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="ServiceConnectorPrototype_applicationPort.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="ServiceConnectorPrototype_applicationPort" atpObject,instanceRef mmt.qualifiedName="ServiceConnectorPrototype_servicePort" atpObject,instanceRef mmt.qualifiedName="ServiceConnectorPrototype_servicePort.serviceComponentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="ServiceConnectorPrototype_servicePort.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" instanceRef.target mmt.qualifiedName="ServiceConnectorPrototype_servicePort" atpObject,instanceRef This expresses the abstract needs that a Software Component or Basic Software Module has on the configuration of an AUTOSAR Service to which it will be connected. "Abstract needs" means, that the model abstracts from the Configuration Paramaters of the underlying Basic Software. mmt.qualifiedName="ServiceNeeds" atpObject Represents the I-PDU's handled by Com. The SignalIPdu 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. mmt.qualifiedName="SignalIPdu" atpObject Timing specification for Com IPdus (Transmission Modes). mmt.qualifiedName="iPduTimingSpecification.SignalIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Definition of SignalToIPduMappings included in the SignalIPdu. mmt.qualifiedName="signalToPduMapping.SignalIPdu";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Represents the I-PDU's handled by Com. The SignalIPdu 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. mmt.qualifiedName="SignalIPdu" atpObject Arranges those signals that are transferred by the gateway from one channel to the other in pairs and defines the mapping between them. Each pair consists in a source and a target referencing to a ISignalTriggering. mmt.qualifiedName="SignalMapping" atpObject Source destination of the referencing mapping. mmt.qualifiedName="SignalMapping.sourceSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" Target destination of the referencing mapping. mmt.qualifiedName="SignalMapping.targetSignal";pureMM.maxOccurs="1";pureMM.minOccurs="1" Arranges those signals that are transferred by the gateway from one channel to the other in pairs and defines the mapping between them. Each pair consists in a source and a target referencing to a ISignalTriggering. mmt.qualifiedName="SignalMapping" atpObject Connectors reception or send port on the referenced channel referenced by an ISignalTriggering. If different timeouts or DataFilters for ISignals need to be specified several ISignalPorts may be created. mmt.qualifiedName="SignalPort" atpObject Optional specification of a signal COM filter at the receiver side in case that the System Description doesn't use a complete Software Component Description (VFB View). This supports the inclusion of legacy system signals. If a full DataMapping exist for the SystemSignal this information may be available from a configured ReceiverComSpec. In this case the ReceiverComSpec overrides this optional specification. mmt.qualifiedName="dataFilter.SignalPort";pureMM.maxOccurs="1";pureMM.minOccurs="0" Optional timeout value in seconds for the reception of the ISignal. In case the System Description doesn't use a complete Software Component Description (VFB View). This supports the inclusion of legacy system signals. If a full DataMapping exist for the SystemSignal this information may be available from a configured ReceiverComSpec, in this case the timeout value in ReceiverComSpec override this optional timeout specification. mmt.qualifiedName="SignalPort.timeout";pureMM.maxOccurs="1";pureMM.minOccurs="0" Connectors reception or send port on the referenced channel referenced by an ISignalTriggering. If different timeouts or DataFilters for ISignals need to be specified several ISignalPorts may be created. mmt.qualifiedName="SignalPort" atpObject The Signal Transformation defines the conversion of the signal attached to a HW Port (direction In) and a signal attached to a HW Port (direction Out). mmt.qualifiedName="SignalTransformation" atpObject The input port the signal transformation is refering to. mmt.qualifiedName="SignalTransformation.inputHwPort";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The output port the signal transformation is refering to. mmt.qualifiedName="SignalTransformation.outputHwPort";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The Signal Transformation defines the conversion of the signal attached to a HW Port (direction In) and a signal attached to a HW Port (direction Out). mmt.qualifiedName="SignalTransformation" atpObject Specifies the ExecutionTime which has been gathered using simulation means. mmt.qualifiedName="SimulatedExecutionTime" atpObject Average SimulatedExecutionTime. mmt.qualifiedName="SimulatedExecutionTime.averageExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum SimulatedExecutionTime. mmt.qualifiedName="SimulatedExecutionTime.maximalExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum SimulatedExecutionTime. mmt.qualifiedName="SimulatedExecutionTime.minimalExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the ExecutionTime which has been gathered using simulation means. mmt.qualifiedName="SimulatedExecutionTime" atpObject SingleLanguageParagraph This is the content model of a single language paragraph in a documentation. mmt.qualifiedName="SlData1" atpMixedString,atpObject SingleLanguagePlainText mmt.qualifiedName="SlData10" atpMixedString,atpObject SingleLanguageOverviewParagraph This is the model for a single language paragraph in an overview item. mmt.qualifiedName="SlData2" atpMixedString,atpObject SingleLanguageUnitName mmt.qualifiedName="SlData3" atpMixedString,atpObject SingleLanguageUnitNameVerbatim mmt.qualifiedName="SlData3p" atpMixedString,atpObject mmt.qualifiedName="SlData3p.xml:space";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" SingleLanguageUnitNameVerbatim mmt.qualifiedName="SlData3p" atpMixedString,atpObject SingleLanguageLongName mmt.qualifiedName="SlData4" atpMixedString,atpObject SingleLanguageVerbatim mmt.qualifiedName="SlData5" atpMixedString,atpObject mmt.qualifiedName="SlData5.allowBreak";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="SlData5.float";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="SlData5.helpEntry";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="SlData5.keepWithPrevious";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="SlData5.pgwide";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" mmt.qualifiedName="SlData5.xml:space";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" SingleLanguageVerbatim mmt.qualifiedName="SlData5" atpMixedString,atpObject The Top-level software composition, containing all software components in the System in a hierarchical structure. The contained ComponentPrototypes are fully specified by their ComponentTypes (including PortPrototypes, PortInterfaces, DataElementPrototypes, InternalBehavior etc.), and their ports are interconnected using ConnectorPrototypes. mmt.qualifiedName="SoftwareComposition" atpObject,atpPrototype We assume that there is exactly one top-level composition that includes all Component instances of the system mmt.qualifiedName="SoftwareComposition.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1" isOfType The Top-level software composition, containing all software components in the System in a hierarchical structure. The contained ComponentPrototypes are fully specified by their ComponentTypes (including PortPrototypes, PortInterfaces, DataElementPrototypes, InternalBehavior etc.), and their ports are interconnected using ConnectorPrototypes. mmt.qualifiedName="SoftwareComposition" atpObject,atpPrototype Specifes the context the software is whose ExecutionTime is provided. mmt.qualifiedName="SoftwareContext" atpObject Specifies the input vector which is used to provide the ExecutionTime. mmt.qualifiedName="SoftwareContext.input";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the state the software is in when the ExecutionTime is provided. mmt.qualifiedName="SoftwareContext.state";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifes the context the software is whose ExecutionTime is provided. mmt.qualifiedName="SoftwareContext" atpObject Source destination of the referencing mapping. mmt.qualifiedName="SourceIPduRef" atpObject If no I-Pdu has been received a default value will be distributed. mmt.qualifiedName="defaultValue.SourceIPduRef";pureMM.maxOccurs="1";pureMM.minOccurs="0" IPdu Reference mmt.qualifiedName="SourceIPduRef.sourceIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Source destination of the referencing mapping. mmt.qualifiedName="SourceIPduRef" atpObject Describes the stack memory usage of a software. mmt.qualifiedName="StackUsage" atpObject Reference to the ECU description this implementation is provided for. mmt.qualifiedName="StackUsage.ecu";pureMM.maxOccurs="1";pureMM.minOccurs="0" Contains information about the hardware context this stack usage is describing. mmt.qualifiedName="hardwareConfiguration.StackUsage";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to the runnable this stack usage is provided for. mmt.qualifiedName="StackUsage.runnable";pureMM.maxOccurs="1";pureMM.minOccurs="0" Contains details about the software context this stack usage is provided for. mmt.qualifiedName="softwareContext.StackUsage";pureMM.maxOccurs="1";pureMM.minOccurs="0" Some parts/signals of the I-PDU may be the same regardless of the selector field. Such a part is called static part. The static part is optional. mmt.qualifiedName="StaticPart" atpObject Reference to a Com IPdu which is routed to the IPduM module and is combined to a multiplexedPdu. mmt.qualifiedName="StaticPart.iPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Some parts/signals of the I-PDU may be the same regardless of the selector field. Such a part is called static part. The static part is optional. mmt.qualifiedName="StaticPart" atpObject Use <std> to reference external standards within a paragraph element. mmt.qualifiedName="Std" atpObject A constant string. mmt.qualifiedName="StringLiteral" atpObject,atpPrototype The string itself. mmt.qualifiedName="StringLiteral.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" A constant string. mmt.qualifiedName="StringLiteral" atpObject,atpPrototype Configuration parameter type for String. mmt.qualifiedName="StringParamDef";xml.sequenceOffset="0" atpObject Default value of the string configuration parameter. mmt.qualifiedName="StringParamDef.defaultValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" Configuration parameter type for String. mmt.qualifiedName="StringParamDef";xml.sequenceOffset="0" atpObject This represents a string of characters out of the character-set specified by the given encoding. The maxNumberOfChars is the maximal number of characters which can be stored within the String. The actual number of bytes that is required to represent the string can be calculated out of maxNumberOfChars and the encoding: bytes required to represent the string = maxNumberOfChars * (max bytes per character using the given encoding) + 1 (terminating null) mmt.qualifiedName="StringType" atpObject,atpType Specification of character encoding, e. g. ISO-8859-1. mmt.qualifiedName="StringType.encoding";pureMM.maxOccurs="1";pureMM.minOccurs="1" The maxNumberOfChars is the maximum number of characters that can be stored in the string. mmt.qualifiedName="StringType.maxNumberOfChars";pureMM.maxOccurs="1";pureMM.minOccurs="1" This represents a string of characters out of the character-set specified by the given encoding. The maxNumberOfChars is the maximal number of characters which can be stored within the String. The actual number of bytes that is required to represent the string can be calculated out of maxNumberOfChars and the encoding: bytes required to represent the string = maxNumberOfChars * (max bytes per character using the given encoding) + 1 (terminating null) mmt.qualifiedName="StringType" atpObject,atpType Representing a configuration value of definition type StringParamDef mmt.qualifiedName="StringValue" atpObject Stores the value of the String parameter. mmt.qualifiedName="StringValue.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" Representing a configuration value of definition type StringParamDef mmt.qualifiedName="StringValue" atpObject A LIN specific extension of the common FRAME to enable the usual frame handling of a placeholder frame that is substituted at runtime. Substitution frame must not declare signal instances nor multiplexers. mmt.qualifiedName="SubstitutionFrame" atpObject,atpStructureElement,atpType Collecting the frames that are substituted by the refering one. This reference is ordered. The order is used to describe the priority (Configuration parameter LinIfFramePriority). The first listed Substitution Frame has the highest priority. mmt.qualifiedName="SubstitutionFrame.substitutedFrame";pureMM.maxOccurs="-1";pureMM.minOccurs="1" The type of substitution. Substitution frames can either be used for event triggered or for sporadic frames. mmt.qualifiedName="SubstitutionFrame.substitutionType";pureMM.maxOccurs="1";pureMM.minOccurs="1" A LIN specific extension of the common FRAME to enable the usual frame handling of a placeholder frame that is substituted at runtime. Substitution frame must not declare signal instances nor multiplexers. mmt.qualifiedName="SubstitutionFrame" atpObject,atpStructureElement,atpType Specifies the abstract needs on the configuration of the Watchdog Manager for one specific Supervised Entity (SE). mmt.qualifiedName="SupervisedEntityNeeds" atpObject true/false: supervision activation status of SE shall be enabled/disabled at start mmt.qualifiedName="SupervisedEntityNeeds.activateAtStart";pureMM.maxOccurs="1";pureMM.minOccurs="1" true: SWC shall be allowed to deactivate supervision of this SE false: not mmt.qualifiedName="SupervisedEntityNeeds.enableDeactivation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Expected cycle time of alive trigger of this SE (in seconds) mmt.qualifiedName="SupervisedEntityNeeds.expectedAliveCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Maximum cycle time of alive trigger of this SE (in seconds) mmt.qualifiedName="SupervisedEntityNeeds.maxAliveCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum cycle time of alive trigger of this SE (in seconds) mmt.qualifiedName="SupervisedEntityNeeds.minAliveCycle";pureMM.maxOccurs="1";pureMM.minOccurs="1" Number of consecutive failed alive cycles for this SE which shall be tolerated until the supervision status of the SE is set to EXPIRED (see WdgM documentation for details). Note that this has to be recalculated w.r.t. the WdgMs own cycle time for ECU configuration. mmt.qualifiedName="SupervisedEntityNeeds.toleratedFailedCycles";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies the abstract needs on the configuration of the Watchdog Manager for one specific Supervised Entity (SE). mmt.qualifiedName="SupervisedEntityNeeds" atpObject This element provides a list of all supported data types and its according data sizes of the described PU. Examples: Boolean (1, 8 bit), Bit String / Bit Field (x bit), Character (8, 16 bit), Signed / unsigned integer (8, 16, 24, 32, 48, 64 bit), Single / double float (56, 64 bit), Fixed point (24 bit), Fractional, Packed (two values handled in one register) mmt.qualifiedName="SupportedDataType" atpObject The size of the data type. Unit: Bit mmt.qualifiedName="SupportedDataType.supportedDataSize";pureMM.maxOccurs="-1";pureMM.minOccurs="1" This element provides a list of all supported data types and its according data sizes of the described PU. Examples: Boolean (1, 8 bit), Bit String / Bit Field (x bit), Character (8, 16 bit), Signed / unsigned integer (8, 16, 24, 32, 48, 64 bit), Single / double float (56, 64 bit), Fixed point (24 bit), Fractional, Packed (two values handled in one register) mmt.qualifiedName="SupportedDataType" atpObject In the current version of the ECU Resource Template the element SupportsSafety is optional. A HW Element uses this element if it provides a safety mechanism, otherwise this element is missing in the description of the HW Element. mmt.qualifiedName="SupportsSafety" atpObject The ECU Resource Template provides the element SupportsSecurity storing the information about the supported security mechanism. In the current version of the ECU Resource Template the element SupportsSecurity is optional. A HW Element uses this element if it provides a security mechanism otherwise this element is missing in the description of the HW Element. mmt.qualifiedName="SupportsSecurity" atpObject Describes how variables or parameters are addressed in the ECU. It contains a description of the addressing process and a reference to the concerned CPU memory segment. mmt.qualifiedName="SwAddrMethod" atpObject The existence of SwArraysize turns the containing element into a multidimensional object. It is then possible to create arrays of variables, parameters etc. SwArraysize should not be used to imitate stereotypes such as curves or maps since these structures are modeled as separate elements, refer to SwCalprmAxisSet for an SwCalprm. Apart from that any array can be created. mmt.qualifiedName="SwArraysize" atpMixed,atpObject Value calculated via a system constant. This element is included in every case, where parameters should be generated from numerical values during compile time (not runtime!). Thus for example, the influence of the cylinder number on conversion formulae, can be introduced in a repeatable manner. mmt.qualifiedName="SwArraysize.vf";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" Use <v> to enter a numerical value. mmt.qualifiedName="SwArraysize.v";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" The existence of SwArraysize turns the containing element into a multidimensional object. It is then possible to create arrays of variables, parameters etc. SwArraysize should not be used to imitate stereotypes such as curves or maps since these structures are modeled as separate elements, refer to SwCalprmAxisSet for an SwCalprm. Apart from that any array can be created. mmt.qualifiedName="SwArraysize" atpMixed,atpObject This element defines an axis for the base points calculated in the ECU. The ECU is equipped with a fixed calculation algorithm. Parameters for the algorithm can be stored in the data component of the ECU. mmt.qualifiedName="SwAxisGeneric" atpObject Associated axis calculation strategy. mmt.qualifiedName="SwAxisGeneric.swAxisType";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" Specific parameter of a generic axis. mmt.qualifiedName="SwAxisGeneric.swGenericAxisParam";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" This element defines an axis for the base points calculated in the ECU. The ECU is equipped with a fixed calculation algorithm. Parameters for the algorithm can be stored in the data component of the ECU. mmt.qualifiedName="SwAxisGeneric" atpObject An SwAxisGrouped is an axis which is shared between multiple calibration parameters. mmt.qualifiedName="SwAxisGrouped" atpObject An SwAxisGrouped is an axis which is shared between multiple calibration parameters. mmt.qualifiedName="SwAxisGrouped" atpObject This element describes an axis integrated into a parameter (field etc.). The integration makes this individual to each parameter. The so-called grouped axis represents the counterpart to this. It is conceived as an independent parameter (see class SwAxisGrouped). The attributes swVariableRefs, compuMethod and unit can exist in parallel, although physically speaking, only one is practical. This parallelism introduces flexibility into the development process, as axes can be described purely physically, without a conversion formula being available. The following priority exists: * swVariableRefs * compuMethod * unit mmt.qualifiedName="SwAxisIndividual" atpObject Refers to an input variable of the axis. It is possible to specify more than one variable. Here the following is valid: * The variable with the highest priority must be given first. It is used in the generation of the code and is also displayed first in the application system. * All variables referenced must be of the same physical nature. This is usually detected in that the conversion formulae affected refer back to the same SI-units. * This multiple referencing allows a base point distribution for more than one input variable to be used. One example of this are the temperature curves, which can depend both on the induction air temperature and the engine temperature. These variables can be displayed simultaneously by MCD systems (adjustment systems), enabling operating points to be shown in the curves. mmt.qualifiedName="SwAxisIndividual.swVariableRef";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="false";xml.roleWrapperElement="true";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" This is the compuMethod which is expected for the axis. It is used in early stages if the particular input-value is not yet available. mmt.qualifiedName="SwAxisIndividual.compuMethod";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Use <unit> to enter the unit of a parameter. mmt.qualifiedName="SwAxisIndividual.unit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" Maximum number of base points contained in the axis of a map or curve. mmt.qualifiedName="SwAxisIndividual.swMaxAxisPoints";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This element specifies the minimum number of base points on the current axis of a map or curve. mmt.qualifiedName="SwAxisIndividual.swMinAxisPoints";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" Refers to constraints, e.g. for plausibility checks. mmt.qualifiedName="SwAxisIndividual.dataConstr";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" This element defines an axis for the base points calculated in the ECU. The ECU is equipped with a fixed calculation algorithm. Parameters for the algorithm can be stored in the data component of the ECU. The following is valid: * The algorithm to be used is specified as <swAxisType> in the data dictionary ** (reservation of keyword and specification of parameters). Thus when forming an axis, the algorithm is given through the appropriate reference ( <swAxisTypeRef> ). * The number of base points to be calculated is defined in <SW-NUMER-OF-AXIS-POINTS>. This element exists to enable the number of axis points to be stored explicitly, although it could also be described as <swGenericAxisParam> . * The calculated base points can be stored on a physical level in the element <swValuesPhys> , which means that it is not necessary for the required calculation algorithm to be implemented in every MCD system. * The calculated base points can be stored on a standardized level in the element <swValuesCoded> , which means that it is not necessary for the required calculation algorithm to be implemented in every MCD system. mmt.qualifiedName="SwAxisIndividual.swAxisGeneric";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" This element describes an axis integrated into a parameter (field etc.). The integration makes this individual to each parameter. The so-called grouped axis represents the counterpart to this. It is conceived as an independent parameter (see class SwAxisGrouped). The attributes swVariableRefs, compuMethod and unit can exist in parallel, although physically speaking, only one is practical. This parallelism introduces flexibility into the development process, as axes can be described purely physically, without a conversion formula being available. The following priority exists: * swVariableRefs * compuMethod * unit mmt.qualifiedName="SwAxisIndividual" atpObject Stands for a specific axis calculation strategy. No formal specification is given, due to the fact that it is possible to use arbitrary algorithms for calculating axis-points. Instead, the algorithm is described verbally but the parameters are specified formally with respect to their names and constraints. As a result, SwAxisType mainly reserves appropriate keywords. mmt.qualifiedName="SwAxisType" atpObject Parameters for this calcultaion algorithm. mmt.qualifiedName="SwAxisType.swGenericAxisParamType";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="30";xml.typeElement="false";xml.typeWrapperElement="false" Stands for a specific axis calculation strategy. No formal specification is given, due to the fact that it is possible to use arbitrary algorithms for calculating axis-points. Instead, the algorithm is described verbally but the parameters are specified formally with respect to their names and constraints. As a result, SwAxisType mainly reserves appropriate keywords. mmt.qualifiedName="SwAxisType" atpObject mmt.qualifiedName="SwBaseType" atpObject Description of the structure of a bit variable: Comprises of the bitPosition in a memory object (e.g. swHostVariable, which stands parallel to swBitRepresentation) and the numberOfBits . In this way, interrelated memory areas can be described. Non-related memory areas are not supported. mmt.qualifiedName="SwBitRepresentation" atpObject If the "bit data object" is hosted witin another data object (e.g. if the memory can be accessed via byte as well as bit adress), this attribute specifies the position of the data object. The count starts at zero (0). mmt.qualifiedName="SwBitRepresentation.bitPosition";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" Number of bits allocated by a "bit data object" within its host data object. mmt.qualifiedName="SwBitRepresentation.numberOfBits";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Description of the structure of a bit variable: Comprises of the bitPosition in a memory object (e.g. swHostVariable, which stands parallel to swBitRepresentation) and the numberOfBits . In this way, interrelated memory areas can be described. Non-related memory areas are not supported. mmt.qualifiedName="SwBitRepresentation" atpObject This element specifies an individual input parameter axis (abscissa). mmt.qualifiedName="SwCalprmAxis" atpObject Describes the index referring to the axis currently described, for which the contents is specified. mmt.qualifiedName="SwCalprmAxis.swAxisIndex";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This property specifies the category of a particular axis. mmt.qualifiedName="SwCalprmAxis.category";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Describes the applicability of parameters and variables. mmt.qualifiedName="SwCalprmAxis.swCalibrationAccess";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" This property specifies how the axis values shall be displayed e.g. in documents or in measurement and calibration tools. mmt.qualifiedName="SwCalprmAxis.displayFormat";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="100" The SwBaseType to be used for the axis. mmt.qualifiedName="SwCalprmAxis.baseType";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="110" This element specifies an individual input parameter axis (abscissa). mmt.qualifiedName="SwCalprmAxis" atpObject Container for the properties of a grouped axis. mmt.qualifiedName="SwCalprmAxisCommonAxis" atpObject The grouped axis contained. mmt.qualifiedName="SwCalprmAxisCommonAxis.swAxisGrouped";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="80" Container for the properties of a grouped axis. mmt.qualifiedName="SwCalprmAxisCommonAxis" atpObject Container for the properties of an individual axis. mmt.qualifiedName="SwCalprmAxisIndividualAxis" atpObject The grouped axis contained. mmt.qualifiedName="SwCalprmAxisIndividualAxis.swAxisIndividual";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="60" Container for the properties of an individual axis. mmt.qualifiedName="SwCalprmAxisIndividualAxis" atpObject This element specifies the input parameter axes (abscissas) of parameters (and variables, if these are used adaptively). mmt.qualifiedName="SwCalprmAxisSet" atpObject One axis belonging to this SwCalprmAxisSet mmt.qualifiedName="SwCalprmAxisSet.swCalprmAxis";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" This element specifies the input parameter axes (abscissas) of parameters (and variables, if these are used adaptively). mmt.qualifiedName="SwCalprmAxisSet" atpObject This element describes the implementation details of a class attribute which manifests itself as a calibration parameter. mmt.qualifiedName="SwCalprmImpl" atpObject This element describes the prototype declaration of a class attribute, which is used as a calibration parameter. mmt.qualifiedName="SwCalprmImpl.swCalprmPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwCalprmImpl.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element describes the implementation details of a class attribute which manifests itself as a calibration parameter. mmt.qualifiedName="SwCalprmImpl" atpObject This element describes the prototype declaration of a class attribute, which is used as a calibration parameter. mmt.qualifiedName="SwCalprmPrototype" atpObject This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwCalprmPrototype.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element describes the prototype declaration of a class attribute, which is used as a calibration parameter. mmt.qualifiedName="SwCalprmPrototype" atpObject Parent class for several kinds of references to a calibration parameter. mmt.qualifiedName="SwCalprmRefProxy" atpObject This element is used to record textual descriptions of axis values and is contained in ASAP1.4, for reasons of backward compatibility. In new systems, the application should be implemented via conversion formulae. mmt.qualifiedName="SwCalprmValueAxisLabels" atpObject Defines the object-oriented class-attributes containing the prototypes: <swVariablePrototypes> which denote attributes within the classes that are variables, <swCalprmPrototypes> which denote attributes within the classes that are calibration parameters , <SW-SERVICE-PROTOTYPES> which denote attributes within the classes that are services and <swClassPrototypes> which denote attributes within the classes that are class instances themselves. mmt.qualifiedName="SwClassAttr" atpObject This element describes the prototype declaration of a class attribute, which appears in the form of a variable. mmt.qualifiedName="SwClassAttr.swVariablePrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" This element describes the prototype declaration of a class attribute, which is used as a calibration parameter. mmt.qualifiedName="SwClassAttr.swCalprmPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="30";xml.typeElement="false";xml.typeWrapperElement="false" Defines the object-oriented class-attributes containing the prototypes: <swVariablePrototypes> which denote attributes within the classes that are variables, <swCalprmPrototypes> which denote attributes within the classes that are calibration parameters , <SW-SERVICE-PROTOTYPES> which denote attributes within the classes that are services and <swClassPrototypes> which denote attributes within the classes that are class instances themselves. mmt.qualifiedName="SwClassAttr" atpObject Defines the object-oriented class-attributes: SW-VARIABLE-IMPLS which implement attributes that are variables, SW-CALPRM-IMPLS which implement attributes that are calibration parameters and SW-CLASS-IMPLS which implement attributes that are class instances themselves. mmt.qualifiedName="SwClassAttrImpl" atpObject This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwClassAttrImpl.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This element describes the implementation details of a class attribute which manifests itself as a variable. mmt.qualifiedName="SwClassAttrImpl.swVariableImpl";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" This element describes the implementation details of a class attribute which manifests itself as a calibration parameter. mmt.qualifiedName="SwClassAttrImpl.swCalprmImpl";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="60";xml.typeElement="false";xml.typeWrapperElement="false" Defines the object-oriented class-attributes: SW-VARIABLE-IMPLS which implement attributes that are variables, SW-CALPRM-IMPLS which implement attributes that are calibration parameters and SW-CLASS-IMPLS which implement attributes that are class instances themselves. mmt.qualifiedName="SwClassAttrImpl" atpObject <swClassAttrInstanceImpl> is used to create an instance from a model (Models are defined with SW-CLASS) where some specifications shall be changed / overwritten. This implementation will then be a instance specific implementation (Classes are usually only implemented under <swClassImpls>). mmt.qualifiedName="SwClassAttrInstanceImpl" atpObject This element describes the implementation details of a class attribute which manifests itself as a variable. mmt.qualifiedName="SwClassAttrInstanceImpl.swVariableImpl";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" This element describes the implementation details of a class attribute which manifests itself as a calibration parameter. mmt.qualifiedName="SwClassAttrInstanceImpl.swCalprmImpl";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="30";xml.typeElement="false";xml.typeWrapperElement="false" This element describes the implementation details of a class attribute which manifests itself as a class. mmt.qualifiedName="SwClassAttrInstanceImpl.swClassImpl";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" <swClassAttrInstanceImpl> is used to create an instance from a model (Models are defined with SW-CLASS) where some specifications shall be changed / overwritten. This implementation will then be a instance specific implementation (Classes are usually only implemented under <swClassImpls>). mmt.qualifiedName="SwClassAttrInstanceImpl" atpObject This element describes the implementation details of a class attribute which manifests itself as a class. mmt.qualifiedName="SwClassImpl" atpObject This element describes the prototype declaration of a class attribute, which appears in the form of a class. mmt.qualifiedName="SwClassImpl.swClassPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwClassImpl.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element describes the implementation details of a class attribute which manifests itself as a class. mmt.qualifiedName="SwClassImpl" atpObject Defines the particular instantiation of a referenced <swClass> . mmt.qualifiedName="SwClassInstance" atpObject This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwClassInstance.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" <swClassAttrInstanceImpl> is used to create an instance from a model (Models are defined with SW-CLASS) where some specifications shall be changed / overwritten. This implementation will then be a instance specific implementation (Classes are usually only implemented under <swClassImpls>). mmt.qualifiedName="SwClassInstance.swClassAttrInstanceImpl";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" Defines the particular instantiation of a referenced <swClass> . mmt.qualifiedName="SwClassInstance" atpObject This element describes the prototype declaration of a class attribute, which appears in the form of a class. mmt.qualifiedName="SwClassPrototype" atpObject SwCodeSyntax objects fix the representation of data objects, e.g. variables and parameters, in the program source file. These code syntax objects are defined centrally in SwCodeSyntaxes and are connected to data objects by means of SwCodeSyntaxRef. The principle role of this element is the declaration of keywords (in the subelement ShortName) for the code generation procedure. The process itself is given a verbal description (in SwCodeSyntaxDesc) rather than a formal one. This approach was adopted as the number of possible code syntax schematics is relatively small. A complete formal description would create unnecessary work. mmt.qualifiedName="SwCodeSyntax" atpObject mmt.qualifiedName="SwCompToEcuMapping_component" atpObject,instanceRef mmt.qualifiedName="SwCompToEcuMapping_component.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SwCompToEcuMapping_component.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SwCompToEcuMapping_component.targetComponentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="SwCompToEcuMapping_component" atpObject,instanceRef mmt.qualifiedName="SwCompToImplMapping_component" atpObject,instanceRef mmt.qualifiedName="SwCompToImplMapping_component.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SwCompToImplMapping_component.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SwCompToImplMapping_component.targetComponentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="SwCompToImplMapping_component" atpObject,instanceRef These variables can be used to display the value of a variable on the value axis of a calibration parameter (characteristic), that is currently displayed in the MCD-System. The purpose is to compare the appropriate result from the calibration parameter in question, with a value being calculated or taken from a sensor (the comparison variable). The sole purpose of this comparison-variable is to serve the calibration process. Screen representation of comparison variable Vs | | | | | | V _|______________|______________ | /----|------ | /-----/ | | / | |/ | |--------------|-------------- tx tmot tx: current temperature V: current speed as shown in the MCD system for comparison: this is the SwComparisonVariable Vs: speed characteristic over temperature tmot: motor temperature mmt.qualifiedName="SwComparisonVariables" atpObject These variables can be used to display the value of a variable on the value axis of a calibration parameter (characteristic), that is currently displayed in the MCD-System. The purpose is to compare the appropriate result from the calibration parameter in question, with a value being calculated or taken from a sensor (the comparison variable). The sole purpose of this comparison-variable is to serve the calibration process. Screen representation of comparison variable Vs | | | | | | V _|______________|______________ | /----|------ | /-----/ | | / | |/ | |--------------|-------------- tx tmot tx: current temperature V: current speed as shown in the MCD system for comparison: this is the SwComparisonVariable Vs: speed characteristic over temperature tmot: motor temperature mmt.qualifiedName="SwComparisonVariables" atpObject Parameters or variables can reference plausibility checks. The assignment of data to <swConstrObjects> makes the reverse direction possible. In this way for example plausibility libraries stored in external files can be latched beneath the previous element <SW-DATA-CONSTRS> -element. mmt.qualifiedName="SwConstrObjects" atpMixed,atpObject This class is a collection of properties relevant for data objects under various aspects. One could consider this class as a "pattern of inheritance by aggregation". The properties can be applied to all objects of all classes in which SwDataDefProps is agrregated. Note that not all of the attributes or associated elements are useful all of the time. Hence, the process definition (e.g. expressed with an OCL or a Document Control Instance) MSR-DCI has the task of implementing limitations. SwDataDefProps covers various aspects: * Structure of the data element, is it a single value, a curve, or a map, but also the recordLayouts which specify, how such elements are mapped/converted to the DataTypes in the programming language (or in Autosar). This is mainly expressed by properties like swRecordLayout and swCalprmAxisSet * Implementation policy, mainly expressed by swImplPolicy, swVariableAccessImplPolicy, swAddrMethod * Access policy for the MDC system, mainly expressed by swCalibrationAccess * Semantics of the data element, mainly expressed by compuMethod and/or unit, dataConstr * Code generation policy provided by swCodeSyntax mmt.qualifiedName="SwDataDefProps" atpObject This aggregation allows to add annotations (yellow pads ...) related to the current data object. mmt.qualifiedName="SwDataDefProps.annotation";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" Addressing method related to this data object. mmt.qualifiedName="SwDataDefProps.swAddrMethod";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Base type associated with the value axis of this data object. mmt.qualifiedName="SwDataDefProps.baseType";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" Description of the binary representaion in case of a bit variable. mmt.qualifiedName="SwDataDefProps.swBitRepresentation";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" Specifies the read or write access by MCD tools for this data object. mmt.qualifiedName="SwDataDefProps.swCalibrationAccess";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" Specifies the size in case the data object is an VAL_BLK. It is there for compatibility reasons, where value blocks were introduced as a kind of an array. mmt.qualifiedName="SwDataDefProps.swValueBlockSize";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" This specifies the properties of the axes in case of a curve or map etc. This is mainly applicable to calibration parameters. mmt.qualifiedName="SwDataDefProps.swCalprmAxisSet";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" the specific properties if the data object is a text object. mmt.qualifiedName="SwDataDefProps.swTextProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="120" Coding policy for this data object expressed as a reference to a Code syntax to be applied. mmt.qualifiedName="SwDataDefProps.swCodeSyntax";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="160" Computation method associated with the semantics of this data object. mmt.qualifiedName="SwDataDefProps.compuMethod";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="180" Data constraint for this data object. mmt.qualifiedName="SwDataDefProps.dataConstr";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="190" If the data object is virtual - that means it is not directly in the ecu, then this property describes how the "virtual variable" can be computed from the real ones. mmt.qualifiedName="SwDataDefProps.swDataDependency";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="200" This property describes how a number is to be rendered e.g. in documents or in a measurement and calibration system. mmt.qualifiedName="SwDataDefProps.displayFormat";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="210" Optional value to express invalidity of the actual data element. If given, the owning component has the API to set this data element invalid, otherwise it does not. mmt.qualifiedName="SwDataDefProps.invalidValue";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="215" Contains a reference to a variable, which serves as a host-variable for a bit variable. Only applicable to bit objects. mmt.qualifiedName="SwDataDefProps.swHostVariable";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="220" Implementation policy for this data object. mmt.qualifiedName="SwDataDefProps.swImplPolicy";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="230" Specifies that the containing data object is a pointer to another data object. mmt.qualifiedName="SwDataDefProps.swPointer";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="280" Record layout for this data object. mmt.qualifiedName="SwDataDefProps.swRecordLayout";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="290" Physical unit associated with the semantics of this data object. This attribute applies, if no compuMethod is specified. If buth units (this as well as via compuMethod is specified,the units ust be the same. mmt.qualifiedName="SwDataDefProps.unit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="350" In case of a swImplPolicy set to "message" the access policy can be refined here. mmt.qualifiedName="SwDataDefProps.swVariableAccessImplPolicy";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="390" This class is a collection of properties relevant for data objects under various aspects. One could consider this class as a "pattern of inheritance by aggregation". The properties can be applied to all objects of all classes in which SwDataDefProps is agrregated. Note that not all of the attributes or associated elements are useful all of the time. Hence, the process definition (e.g. expressed with an OCL or a Document Control Instance) MSR-DCI has the task of implementing limitations. SwDataDefProps covers various aspects: * Structure of the data element, is it a single value, a curve, or a map, but also the recordLayouts which specify, how such elements are mapped/converted to the DataTypes in the programming language (or in Autosar). This is mainly expressed by properties like swRecordLayout and swCalprmAxisSet * Implementation policy, mainly expressed by swImplPolicy, swVariableAccessImplPolicy, swAddrMethod * Access policy for the MDC system, mainly expressed by swCalibrationAccess * Semantics of the data element, mainly expressed by compuMethod and/or unit, dataConstr * Code generation policy provided by swCodeSyntax mmt.qualifiedName="SwDataDefProps" atpObject This element describes the interdependencies of data objects, e.g. variables and parameters. It can be used for example to treat virtual parameters. mmt.qualifiedName="SwDataDependency" atpObject This element describes the formula with which the dependencies between the participating objects are defined. mmt.qualifiedName="SwDataDependency.swDataDependencyFormula";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Specifies the arguments used in the data dependency. Note that this is 0..1 since the aggregated class is a container (atpMixed). mmt.qualifiedName="SwDataDependency.swDataDependencyArgs";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This element describes the interdependencies of data objects, e.g. variables and parameters. It can be used for example to treat virtual parameters. mmt.qualifiedName="SwDataDependency" atpObject This element specifies the elements used in a SwDataDependency. mmt.qualifiedName="SwDataDependencyArgs" atpMixed,atpObject This element specifies the elements used in a SwDataDependency. mmt.qualifiedName="SwDataDependencyArgs" atpMixed,atpObject This element describes a specific parameter of a generic axis. The name of the parameter is defined through a reference to a parameter type defined on a corresponding axis type. mmt.qualifiedName="SwGenericAxisParam" atpObject Parameter type defined on a corresponding axis type. References can only be made to axis parameters types which are defined within the referenced axis type. mmt.qualifiedName="SwGenericAxisParam.swGenericAxisParamType";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" This element describes a specific parameter of a generic axis. The name of the parameter is defined through a reference to a parameter type defined on a corresponding axis type. mmt.qualifiedName="SwGenericAxisParam" atpObject This element describes a generic axis parameter type, namely: * Plausibility checks can be specified via dataConstr. * Textual description (desc), as a formal description is not of any use, due to the large variety of possibilities. * If this parameter contains structures, these can be simulated through the recursive use of swGenericAxisParamTypes. mmt.qualifiedName="SwGenericAxisParamType" atpObject Contains the value for the generic axis parameter. mmt.qualifiedName="SwGenericAxisParamValue" atpMixed,atpObject Value calculated via a system constant. This element is included in every case, where parameters should be generated from numerical values during compile time (not runtime!). Thus for example, the influence of the cylinder number on conversion formulae, can be introduced in a repeatable manner. mmt.qualifiedName="SwGenericAxisParamValue.vf";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" Use <v> to enter a numerical value. mmt.qualifiedName="SwGenericAxisParamValue.v";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="50" Contains the value for the generic axis parameter. mmt.qualifiedName="SwGenericAxisParamValue" atpMixed,atpObject This element indicates, that the data object (which is specified by the containing element) is a reference to another data object. The properties of the referred data object are described in the swDataDefProps contained by the SwPointer . mmt.qualifiedName="SwPointer" atpObject The properties of the data object, to which the pointer points. mmt.qualifiedName="SwPointer.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element indicates, that the data object (which is specified by the containing element) is a reference to another data object. The properties of the referred data object are described in the swDataDefProps contained by the SwPointer . mmt.qualifiedName="SwPointer" atpObject Defines how the data objects (variables, calibration parameters etc.) are to be stored in the ECU memory. As an example, this definition specifies the sequence of axis points in the ECU memory. Iterations through axis values are stored within the subelements swRecordLayoutGroup . These subelements might be stored nested to support multidimensional data objects. mmt.qualifiedName="SwRecordLayout" atpObject Set up for the record layout of axis values. mmt.qualifiedName="SwRecordLayout.swRecordLayoutGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="false";xml.sequenceOffset="20";xml.typeElement="false";xml.typeWrapperElement="false" Defines how the data objects (variables, calibration parameters etc.) are to be stored in the ECU memory. As an example, this definition specifies the sequence of axis points in the ECU memory. Iterations through axis values are stored within the subelements swRecordLayoutGroup . These subelements might be stored nested to support multidimensional data objects. mmt.qualifiedName="SwRecordLayout" atpObject Specifies how a record layout is set up. Using SwRecordLayoutGroup it recursively models iterations through axis values. The subelement swRecordLayoutGroupContentType may reference other SwRecordLayouts, SwRecordLayoutVs and SwRecordLayoutGroups for the modeled record layout. mmt.qualifiedName="SwRecordLayoutGroup" atpObject The contents of this element specifies the axis number within a record layout group. mmt.qualifiedName="SwRecordLayoutGroup.swRecordLayoutGroupAxis";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element attributes a symbolic name to the iterator of the superimposed record layout group. This can be referenced as a loop index beneath superimposed or subsequent SwRecordLayoutV elements. mmt.qualifiedName="SwRecordLayoutGroup.swRecordLayoutGroupIndex";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This element specifies the iterator index for the point in the axis from which a record layout group is commenced. Negative values are also possible, i.e. the value -4 counts from the fourth value from the end. mmt.qualifiedName="SwRecordLayoutGroup.swRecordLayoutGroupFrom";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This element specifies the iterator index for a point in the axis up to which iteration for a record layout group takes place. Negative values are also possible, i.e. the value -4 counts up to the fourth value from the end. mmt.qualifiedName="SwRecordLayoutGroup.swRecordLayoutGroupTo";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="70" This element specifies the step width for the iterator index, which is used for a record layout group . mmt.qualifiedName="SwRecordLayoutGroup.swRecordLayoutGroupStep";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" This element is used to denote the component to which the group in question applies. Thus, the record layout supports structured objects. This secures independence from the sequence of components, because they can be referred to via name. mmt.qualifiedName="SwRecordLayoutGroup.swRecordLayoutComponent";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" Specifies how a record layout is set up. Using SwRecordLayoutGroup it recursively models iterations through axis values. The subelement swRecordLayoutGroupContentType may reference other SwRecordLayouts, SwRecordLayoutVs and SwRecordLayoutGroups for the modeled record layout. mmt.qualifiedName="SwRecordLayoutGroup" atpObject This is the contents of a RecordLaoyut which is inserted for every iteration. Note that since this is atpMixed, multiple properties can be inserted for each iteration. mmt.qualifiedName="SwRecordLayoutGroupContent" atpMixed,atpObject this association allows to support reusable "sub"-record layouts. In particluar, the contents of the referenced record layout must be used here. So semantically it would be equivalent to replace the particluar association with the swRecordLayoutGroups of the referred SwRecordLayout. mmt.qualifiedName="SwRecordLayoutGroupContent.swRecordLayout";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="110" Particular Value specification for this record layout group. mmt.qualifiedName="SwRecordLayoutGroupContent.swRecordLayoutV";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="120" This aggregation provides support for nested iterations. For example if a map is to be handled, then we might have two nested SwRecordLayoutGroups, one for the x-axis and one for the y-axis. The inner iteration runs faster. mmt.qualifiedName="SwRecordLayoutGroupContent.swRecordLayoutGroup";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="130" This is the contents of a RecordLaoyut which is inserted for every iteration. Note that since this is atpMixed, multiple properties can be inserted for each iteration. mmt.qualifiedName="SwRecordLayoutGroupContent" atpMixed,atpObject This element specifies which values are stored for the current SwRecordLayoutGroup. If no baseType is present, the SwBaseType referenced initially in the father element SwRecordLayoutGroup is valid. The specification of swRecordLayoutVAxis gives the axis of the values to be stored in accordance with the current record layout SwRecordLayoutGroup. In swRecordLayoutVProp you are able to specify the type of values that are to be stored, e.g. number or value. Under swRecordLayoutVIndex, the symbolic values of the axes can be given, for which the value given under swRecordLayoutVProp is iterated. These symbolic values relate to the values given in swRecordLayoutGroupIndex. mmt.qualifiedName="SwRecordLayoutV" atpObject SwBaseType to be used for the values within this SwRecordLayoutV. mmt.qualifiedName="SwRecordLayoutV.baseType";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This attribute specifies the axis from which the value properties are used. mmt.qualifiedName="SwRecordLayoutV.swRecordLayoutVAxis";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" The contents of this attribute describes the type of values to be stored in the record. mmt.qualifiedName="SwRecordLayoutV.swRecordLayoutVProp";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" The symbolic value for iteration, or the symbolic values separated by white-spaces, refer to the symbolic values given in swRecordLayoutGroupIndex . The iterators are processed from left to right, in such a manner that they symbolize the loop index from the outside to the inside. An error has occurred if a parameter references a record layout which contains an swRecordLayoutVIndex with more components than the number of parameter axes. mmt.qualifiedName="SwRecordLayoutV.swRecordLayoutVIndex";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This attribute specifies the filler character for the current record layout, in the form of hex digits. The element present parallel to this in swRecordLayoutVProp must therefore have the contents FILL. mmt.qualifiedName="SwRecordLayoutV.swRecordLayoutVFixValue";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="80" tbd: I (bernhard Weichel) ar not sure if this association is superfluous ... mmt.qualifiedName="SwRecordLayoutV.swRecordLayout";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" This element specifies which values are stored for the current SwRecordLayoutGroup. If no baseType is present, the SwBaseType referenced initially in the father element SwRecordLayoutGroup is valid. The specification of swRecordLayoutVAxis gives the axis of the values to be stored in accordance with the current record layout SwRecordLayoutGroup. In swRecordLayoutVProp you are able to specify the type of values that are to be stored, e.g. number or value. Under swRecordLayoutVIndex, the symbolic values of the axes can be given, for which the value given under swRecordLayoutVProp is iterated. These symbolic values relate to the values given in swRecordLayoutGroupIndex. mmt.qualifiedName="SwRecordLayoutV" atpObject This element describes plausibility rules that go beyond the individual data object. E.g. the overrun shut-off engine speed must not be higher than the maximum engine speed. This plausibility rule is defined in exactly the same way as the contexts and dependencies of virtual characteristic variables and variables. mmt.qualifiedName="SwRelatedConstrs" atpObject This element denotes a variable which servers as a semaphore for a particular resource which is specified in the surrounding data object, e.g. SwDataDefProps. mmt.qualifiedName="SwSemaphore" atpObject This element denotes a variable which servers as a semaphore for a particular resource which is specified in the surrounding data object, e.g. SwDataDefProps. mmt.qualifiedName="SwSemaphore" atpObject Describes a procedure call in the software. Depending on the usage, the description can contain properties of the function call (signature) and of its implementation as well. mmt.qualifiedName="SwService" atpObject The return type belonging to this SwService. mmt.qualifiedName="SwService.swServiceReturn";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" An argument belonging to this SwService. mmt.qualifiedName="SwService.swServiceArg";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="30";xml.typeElement="false";xml.typeWrapperElement="false" Interface elements accessed by this SwService. mmt.qualifiedName="SwService.swServiceAccessedElementSet";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="80";xml.typeElement="false";xml.typeWrapperElement="false" The properties assigned to this SwService. mmt.qualifiedName="SwService.swServiceProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="90" Describes a procedure call in the software. Depending on the usage, the description can contain properties of the function call (signature) and of its implementation as well. mmt.qualifiedName="SwService" atpObject This element is similar to <SW-INTERFACE-ACCESSED-ELEMENT-SET> but applies to <SW-SERVICE> . To some extent it is now possible to epress the access to interface elements * within a software component represented by ( <swFeature> ), which is the mainly a functional view * within a process represented by <SW-SERVICE>, which is more the dynamic view. These processes are part of compontents (represented by ownership and imports, which makes it possible to retrieve the functional view from the dynamic view (but ** vice versa). mmt.qualifiedName="SwServiceAccessedElementSet" atpObject Specifies the properties of a data object exchanged during the call of an SwService, e.g. an argument or a return value. mmt.qualifiedName="SwServiceArg" atpObject The existence of <swArraysize> turns the parent element into a multidimensional object. It is then possible to create arrays of variables, parameters etc. <swArraysize> should ** to imitate stereotypes such as curves or maps since these structures are stored in the DTD itself as own elements, refer to <swCalprmAxisSet> for a <swCalprm>. Apart from that any array can be created. mmt.qualifiedName="SwServiceArg.swArraysize";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" Data properties of this SwServiceArg. mmt.qualifiedName="SwServiceArg.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" Specifies the properties of a data object exchanged during the call of an SwService, e.g. an argument or a return value. mmt.qualifiedName="SwServiceArg" atpObject tbd mmt.qualifiedName="SwServiceImpl" atpObject Describes certain properties of the service implementation. mmt.qualifiedName="SwServiceProps" atpObject Reentrance enables or prohibits the service to be invoked again, before the service has finished and delivered a result. If the attribute is missing, then reentrance is prohibited. mmt.qualifiedName="SwServiceProps.swServiceReentrance";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" Enables the specification of an implementation strategy. In this way, the direction of the implementation to come, can be specified in advance in an earlier phase. mmt.qualifiedName="SwServiceProps.swImplPolicy";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" Describes certain properties of the service implementation. mmt.qualifiedName="SwServiceProps" atpObject mmt.qualifiedName="SwServicePrototype" atpObject The properties specific for a textual calibration parameter / variable. mmt.qualifiedName="SwTextProps" atpObject Specifies the maximum text size in characters. Note the the size in bytes depends on the encoding in the corresponding baseType. mmt.qualifiedName="SwTextProps.swMaxTextSize";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" Filler character for text parameter to pad up to the maximum length <SwMaxTextSize>. The filler character for texts which are shorter than the maximum permitted text length. The value will be interpreted according to the encoding specified in the associated base type of the data object., e.g. 0x30 (hex) represents the ASCII character zero as filler character and 0 (dez) represents an end of string as filler character. mmt.qualifiedName="SwTextProps.swFillCharacter";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" The properties specific for a textual calibration parameter / variable. mmt.qualifiedName="SwTextProps" atpObject This element describes the implementation details of a class attribute which manifests itself as a variable. mmt.qualifiedName="SwVariableImpl" atpObject This element describes the prototype declaration of a class attribute, which appears in the form of a variable. mmt.qualifiedName="SwVariableImpl.swVariablePrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="20" This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwVariableImpl.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element describes the implementation details of a class attribute which manifests itself as a variable. mmt.qualifiedName="SwVariableImpl" atpObject This element describes the prototype declaration of a class attribute, which appears in the form of a variable. mmt.qualifiedName="SwVariablePrototype" atpObject This element describes all of the distinguishing characteristics of a data object (variable or parameter). <swDataDefProps> is used in every case, where characteristics of data objects must be given. It is inevitable that not all of the inputs are useful all of the time. Hence, the process definition or the DCI has the task of implementing limitations. The <swDataDefProps> describe the characteristics of all axes: * The characteristics of the argument axes (abscissas) are described in <swCalprmAxisSet> . * The characteristics of the value axis are described directly in <swDataDefProps> . mmt.qualifiedName="SwVariablePrototype.swDataDefProps";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This element describes the prototype declaration of a class attribute, which appears in the form of a variable. mmt.qualifiedName="SwVariablePrototype" atpObject This class establishes a reference to a variable. It is mainly introduced by the reverse engineering tool. mmt.qualifiedName="SwVariableRef" atpObject This class establishes a reference to a variable. It is mainly introduced by the reverse engineering tool. mmt.qualifiedName="SwVariableRef" atpObject Specialization of the ComMgrUserNeeds for the case it is owned by a SoftwareComponentType. mmt.qualifiedName="SwcComMgrUserNeeds" atpObject This is the provided service to be called by the Com Manager to handle a particular communication channel of the Com Manager. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification ot Com Manager" (e.g. something like "modeRequester") mmt.qualifiedName="SwcComMgrUserNeeds.callbackPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This is the expected service to be called by the software component to handle a particular Com Manger event. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification ot Com Manager" (e.g. something like "modeRequester") mmt.qualifiedName="SwcComMgrUserNeeds.serviceCallPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specialization of the ComMgrUserNeeds for the case it is owned by a SoftwareComponentType. mmt.qualifiedName="SwcComMgrUserNeeds" atpObject Specialization of the DiagnosticCommunicationNeeds for the case it is owned by a SoftwareComponentType. mmt.qualifiedName="SwcDiagnosticCommunicationNeeds" atpObject This is the provided service to be called by the Diagnostic Communication Manager to handle a particular Diagnostic Communication.. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification ot Diagnostic Communication Manager" (e.g. something like "CallBakReqTreatment"). mmt.qualifiedName="SwcDiagnosticCommunicationNeeds.callbackPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This is the expected service to be called by the software component to handle a particular Diagnostic Communkication. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification ot Diagnostic Communication Manager" (e.g. something like "DcmService") mmt.qualifiedName="SwcDiagnosticCommunicationNeeds.serviceCallPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specialization of the DiagnosticCommunicationNeeds for the case it is owned by a SoftwareComponentType. mmt.qualifiedName="SwcDiagnosticCommunicationNeeds" atpObject Specialization of the DiagnosticEventNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this diagnostic event. Note that there may be further ports to communicate with the DEM Service (e.g. setting the operation cycle type) which are not included in this mapping because they are independent of the diagnostic event. mmt.qualifiedName="SwcDiagnosticEventNeeds" atpObject This aggregation specifies the expected service to be called by the Diagnostic Event Manager. The value of the role attribute in the aggregated class must be be a name of a PortInterface as standardized in "Specification of Diagnostics Event Manager", for example CallbackInitMonitorForEvent. mmt.qualifiedName="SwcDiagnosticEventNeeds.callbackPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This is the expected service to be called by the software component to handle a particular diagnostic event. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification of Diagnostics Event Manager", for example "DiagnosticMonitor". mmt.qualifiedName="SwcDiagnosticEventNeeds.serviceCallPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specialization of the DiagnosticEventNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this diagnostic event. Note that there may be further ports to communicate with the DEM Service (e.g. setting the operation cycle type) which are not included in this mapping because they are independent of the diagnostic event. mmt.qualifiedName="SwcDiagnosticEventNeeds" atpObject Specialization of the EcuStateMgrUserNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all the ports which are used by this component to put requests for this "user". Note that there are further ports which a component can use to obtain various information from the ECU State Manager. These ports are not included in the mapping because they will be implemented as pure function calls which can be called independently of being a certain"user". Note that the AUTOSAR ECU State Manager does not support callbacks to services provided by users of ECU State Manger, therefore there is not property "callbackPort". mmt.qualifiedName="SwcEcuStateMgrUserNeeds" atpObject This is the expected service to be called by the software component to handle a particular User of the Ecu State Manager.. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification ot ECU State Manager". Examples are "CurrentMode", "ShutdownTarget", "BootTarget" , "ApplicationMode", "StateRequest". mmt.qualifiedName="SwcEcuStateMgrUserNeeds.serviceCallPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specialization of the EcuStateMgrUserNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all the ports which are used by this component to put requests for this "user". Note that there are further ports which a component can use to obtain various information from the ECU State Manager. These ports are not included in the mapping because they will be implemented as pure function calls which can be called independently of being a certain"user". Note that the AUTOSAR ECU State Manager does not support callbacks to services provided by users of ECU State Manger, therefore there is not property "callbackPort". mmt.qualifiedName="SwcEcuStateMgrUserNeeds" atpObject Specialization of the FunctionInhibitionNeeds for the case it is owned by a SoftwareComponentType. Note that the Function Inhibit Manger does not provide callbacks to services provided by software components. Therefoer there is no property "callbackPort". mmt.qualifiedName="SwcFunctionInhibitionNeeds" atpObject This is the expected service to be called by the software component to handle a particular inhibition of a particular function. This inhibition is controlled by the FunctionInhibitManager. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification ot Function Inhibition Manager". e-g- "FunctionInhibition". mmt.qualifiedName="SwcFunctionInhibitionNeeds.serviceCallPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specialization of the FunctionInhibitionNeeds for the case it is owned by a SoftwareComponentType. Note that the Function Inhibit Manger does not provide callbacks to services provided by software components. Therefoer there is no property "callbackPort". mmt.qualifiedName="SwcFunctionInhibitionNeeds" atpObject mmt.qualifiedName="SwcImplementation" atpObject The internal behavior implemented by this Implementation. mmt.qualifiedName="SwcImplementation.behavior";pureMM.maxOccurs="1";pureMM.minOccurs="1" Allows a definition of the size of the per-instance memory for this implementation. mmt.qualifiedName="perInstanceMemorySize.SwcImplementation";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Identify a specific RTE vendor. This information is potentially important at the time of integrating (in particular: linking) the application code with the RTE. The semantics is that (if the association exists) the corresponding code has been created to fit to the vendor-mode RTE provided by this specific vendor. Attempting to integrate the code with another RTE generated in vendor mode is in general not possible. mmt.qualifiedName="SwcImplementation.requiredRTEVendor";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="SwcImplementation" atpObject Specialization of NvBlockNeeds for the case it is owned by a SoftwareComponentType. It specifies all mappings to elements of the SoftwareComponentType concerning a single Nv block. Note that the mapping is the same for all instances of a SoftwareComponentType (because the code depends on it). Note that the block size is not specified here because - it can be derived from the associated PerInstanceMemory size (implementatiion specific) in case of implicit storage/restauration of the block - if can be derived from the array size passed via the correponding operations of the Service Interface in case of explicit storage/restauration of the block mmt.qualifiedName="SwcNvBlockNeeds" atpObject This is the provided service to be called by the NvRam Manager to handle a particular NvBlock. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification of NVRAM Manager" (e.g. something like "NvMNotify") mmt.qualifiedName="SwcNvBlockNeeds.callBackPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Defines the ROM default for an Nv block. This data can be also calibratable. mmt.qualifiedName="SwcNvBlockNeeds.defaultBlock";pureMM.maxOccurs="1";pureMM.minOccurs="0" Defines the RAM mirror in case of a permanant Nv block. mmt.qualifiedName="SwcNvBlockNeeds.mirrorBlock";pureMM.maxOccurs="1";pureMM.minOccurs="0" This is the expected service to be called by the software component to handle a particular NvBlock. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification of NVRAM Manager" (e.g. something like "NvMAdministration" , "NvMService") mmt.qualifiedName="SwcNvBlockNeeds.serviceCallPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specialization of NvBlockNeeds for the case it is owned by a SoftwareComponentType. It specifies all mappings to elements of the SoftwareComponentType concerning a single Nv block. Note that the mapping is the same for all instances of a SoftwareComponentType (because the code depends on it). Note that the block size is not specified here because - it can be derived from the associated PerInstanceMemory size (implementatiion specific) in case of implicit storage/restauration of the block - if can be derived from the array size passed via the correponding operations of the Service Interface in case of explicit storage/restauration of the block mmt.qualifiedName="SwcNvBlockNeeds" atpObject Specialization of the ObdControlServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular TID. mmt.qualifiedName="SwcObdControlServiceNeeds" atpObject Port which must be used for reading the test result data provided by trhe Software Component. mmt.qualifiedName="SwcObdControlServiceNeeds.callbackPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specialization of the ObdControlServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular TID. mmt.qualifiedName="SwcObdControlServiceNeeds" atpObject Specialization of the ObdInfoServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular InfoType. mmt.qualifiedName="SwcObdInfoServiceNeeds" atpObject Port which must be used for reading this InfoType. mmt.qualifiedName="SwcObdInfoServiceNeeds.callbackPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specialization of the ObdInfoServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular InfoType. mmt.qualifiedName="SwcObdInfoServiceNeeds" atpObject Specialization of the ObdMonitorServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular ratio monitoring. mmt.qualifiedName="SwcObdMonitorServiceNeeds" atpObject Port which must be used for reading the TID data provided by trhe Software Component. mmt.qualifiedName="SwcObdMonitorServiceNeeds.callbackPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specialization of the ObdMonitorServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular ratio monitoring. mmt.qualifiedName="SwcObdMonitorServiceNeeds" atpObject Specialization of the ObdPidServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular PID. mmt.qualifiedName="SwcObdPidServiceNeeds" atpObject This aggregation specifies the expected port to be called by the Diagnostic Event Manager or Diagnosticc Communication Manager in order to read the PID value. mmt.qualifiedName="SwcObdPidServiceNeeds.callbackPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specialization of the ObdPidServiceNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this particular PID. mmt.qualifiedName="SwcObdPidServiceNeeds" atpObject Specialization of the ObdRatioServicetNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this element. mmt.qualifiedName="SwcObdRatioServiceNeeds" atpObject Via calls from this port the Software Component is expected to handle a particular ratio monitoring. mmt.qualifiedName="SwcObdRatioServiceNeeds.serviceCallPort";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specialization of the ObdRatioServicetNeeds for the case it is owned by a SoftwareComponentType. It allows to navigate to all ports associated with this element. mmt.qualifiedName="SwcObdRatioServiceNeeds" atpObject Specialization of SupervisedEntityNeeds for the case it is owned by a SoftwareComponentType. mmt.qualifiedName="SwcSupervisedEntityNeeds" atpObject This is the expected service to be called by the software component to handle a supervised entity by the watchdoc. The value of the role attribute in the aggregated class must be a name of a PortInterface as standardized in "Specification of Watchdog Manager" (e.g. something like "WdgMService") mmt.qualifiedName="SwcSupervisedEntityNeeds.serviceCallPort";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Specialization of SupervisedEntityNeeds for the case it is owned by a SoftwareComponentType. mmt.qualifiedName="SwcSupervisedEntityNeeds" atpObject Map software components to a specific ECU Instance. mmt.qualifiedName="SwcToEcuMapping" atpObject References to the software component instances that are mapped to the referenced ECUInstance. If the component prototype referenced is a composition, this indicates that all atomic software components within the composition are mapped to the ECU. If there is aditionally a mapping of some ComponentPrototype INSIDE the Composition to another ECU Instance the inner mapping overrides the outer mapping. mmt.qualifiedName="component.SwcToEcuMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="1" EcuInstance is a reference to an ECU Instance description mmt.qualifiedName="SwcToEcuMapping.ecuInstance";pureMM.maxOccurs="1";pureMM.minOccurs="1" Map software components to a specific ECU Instance. mmt.qualifiedName="SwcToEcuMapping" atpObject The System Constraint Description has to describe dedicated and exclusive mapping of SW-Cs to one or more ECUs. Dedicated mapping means that the SW-C can only be mapped to the ECUs it is dedicated to. Exclusive Mapping means that the SW-C cannot be mapped to the ECUs it is excluded from. mmt.qualifiedName="SwcToEcuMappingConstraint" atpObject Reference to ComponentPrototypes for which the dedicated or exclusive mapping is defined. mmt.qualifiedName="component.SwcToEcuMappingConstraint";pureMM.maxOccurs="-1";pureMM.minOccurs="1" If the dedicated mapping is described, the ComponentPrototypes can only be mapped to these referenced ECUInstances. If the exclusive mapping is described, the ComponentPrototypes cannot be mapped to these referenced ECUInstances. mmt.qualifiedName="SwcToEcuMappingConstraint.ecuInstance";pureMM.maxOccurs="-1";pureMM.minOccurs="0" This attribute determines if dedicated or exclusive mapping is used. mmt.qualifiedName="SwcToEcuMappingConstraint.swcToEcuMappingConstraintType";pureMM.maxOccurs="1";pureMM.minOccurs="1" The System Constraint Description has to describe dedicated and exclusive mapping of SW-Cs to one or more ECUs. Dedicated mapping means that the SW-C can only be mapped to the ECUs it is dedicated to. Exclusive Mapping means that the SW-C cannot be mapped to the ECUs it is excluded from. mmt.qualifiedName="SwcToEcuMappingConstraint" atpObject mmt.qualifiedName="SwcToEcuMappingConstraint_component" atpObject,instanceRef mmt.qualifiedName="SwcToEcuMappingConstraint_component.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SwcToEcuMappingConstraint_component.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SwcToEcuMappingConstraint_component.targetComponentPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.target mmt.qualifiedName="SwcToEcuMappingConstraint_component" atpObject,instanceRef Map instances of an AtomicSoftwareComponentType to a specific Implementation. mmt.qualifiedName="SwcToImplMapping" atpObject Reference to a specific Implementation description. Implementation to be used by the specified SW component instance. This allows to achieve more precise estimates for the resource consumption that results from mapping the instance of an atomic SW component onto an ECU. mmt.qualifiedName="SwcToImplMapping.componentImplementation";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the software component instances that are being mapped to the specified Implementation. The targeted ComponentPrototype needs be of the AtomicSoftwareComponentType being implemented by the referenced Implementation. mmt.qualifiedName="component.SwcToImplMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Map instances of an AtomicSoftwareComponentType to a specific Implementation. mmt.qualifiedName="SwcToImplMapping" atpObject The SwcToSwcOperationArguments describes the information (client server operation arguments, plus the operation identification, if required) that are exchanged between two SW Components from exactly one client to one server, or from one server back to one client. The direction attribute defines which direction is described. If direction == IN, all arguments sent from the client to the server are described by the SwcToSwcOperationArguments, in direction == OUT, it's the arguments sent back from server to client. mmt.qualifiedName="SwcToSwcOperationArguments" atpObject direction addressed by this SwcToSwcClientServerOperation element. mmt.qualifiedName="SwcToSwcOperationArguments.direction";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to the operation at the client and at the server side whose arguments are described by SwcToSwcOperationArguments. The two ports referenced must be connected by a connector in the software component description. mmt.qualifiedName="operation.SwcToSwcOperationArguments";pureMM.maxOccurs="2";pureMM.minOccurs="2" The SwcToSwcOperationArguments describes the information (client server operation arguments, plus the operation identification, if required) that are exchanged between two SW Components from exactly one client to one server, or from one server back to one client. The direction attribute defines which direction is described. If direction == IN, all arguments sent from the client to the server are described by the SwcToSwcOperationArguments, in direction == OUT, it's the arguments sent back from server to client. mmt.qualifiedName="SwcToSwcOperationArguments" atpObject mmt.qualifiedName="SwcToSwcOperationArguments_operation" atpObject,instanceRef mmt.qualifiedName="SwcToSwcOperationArguments_operation.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SwcToSwcOperationArguments_operation.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SwcToSwcOperationArguments_operation.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="SwcToSwcOperationArguments_operation.operationPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.target mmt.qualifiedName="SwcToSwcOperationArguments_operation" atpObject,instanceRef The SwcToSwcSignal describes the information (data element) that is exchanged between two SW Components. On the SWC Level it is possible that a SW Component sends one data element from one P-Port to two different SW Components (1:n Communication). The SwcToSwcSignal describes exactly the information which is exchanged between one P-Port of a SW Component and one R-Port of another SW Component. mmt.qualifiedName="SwcToSwcSignal" atpObject Reference to a data element on the PPort and to the same data element on the RPort. Reference to a data element on the PPort and to the same data element on the RPort. Reference to a data element on the PPort and to the same data element on the RPort. mmt.qualifiedName="dataElement.SwcToSwcSignal";pureMM.maxOccurs="2";pureMM.minOccurs="2" The SwcToSwcSignal describes the information (data element) that is exchanged between two SW Components. On the SWC Level it is possible that a SW Component sends one data element from one P-Port to two different SW Components (1:n Communication). The SwcToSwcSignal describes exactly the information which is exchanged between one P-Port of a SW Component and one R-Port of another SW Component. mmt.qualifiedName="SwcToSwcSignal" atpObject mmt.qualifiedName="SwcToSwcSignal_dataElement" atpObject,instanceRef mmt.qualifiedName="SwcToSwcSignal_dataElement.softwareComposition";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" instanceRef.context mmt.qualifiedName="SwcToSwcSignal_dataElement.componentPrototype";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" instanceRef.context mmt.qualifiedName="SwcToSwcSignal_dataElement.portPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="30" instanceRef.context mmt.qualifiedName="SwcToSwcSignal_dataElement.dataElementPrototype";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="40" instanceRef.target mmt.qualifiedName="SwcToSwcSignal_dataElement" atpObject,instanceRef This specialization of a ReferenceParamDef specifies that the implementation of the reference is done using a symbolic name defined by the referenced Container's shortName. mmt.qualifiedName="SymbolicNameReferenceParamDef" atpObject This means that the runnable will block for a response from the server. mmt.qualifiedName="SynchronousServerCallPoint" atpObject The top level element of the System Description. The System description defines five major elements: Topology, Software, Communication, Mapping and Mapping Constraints. The System element directly aggregates the elements describing the Software, Mapping and Mapping Constraints; it contains a reference to an ASAM FIBEX description specifying Communication and Topology. mmt.qualifiedName="System" atpObject,atpStructureElement Version number of the Ecu Extract. mmt.qualifiedName="System.ecuExtractVersion";pureMM.maxOccurs="1";pureMM.minOccurs="0" Reference to ASAM FIBEX elements specifying Communication and Topology. All Fibex Elements used within a System Description shall be referenced from the System Element. mmt.qualifiedName="System.fibexElement";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Aggregation of all mapping aspects (mapping of SW components to ECUs, mapping of data elements to signals, and mapping constraints). mmt.qualifiedName="mapping.System";pureMM.maxOccurs="1";pureMM.minOccurs="1" Length of the partial networking request release information vector. mmt.qualifiedName="System.pncVectorLength";pureMM.maxOccurs="1";pureMM.minOccurs="0" Absolute offset (with respect to the Frame) of the partial networking request release information vector. mmt.qualifiedName="System.pncVectorOffset";pureMM.maxOccurs="1";pureMM.minOccurs="0" Aggregation of the top-level software composition, containing all software components in the System in a hierarchical structure. mmt.qualifiedName="softwareComposition.System";pureMM.maxOccurs="1";pureMM.minOccurs="1" Version number of the System Description. mmt.qualifiedName="System.systemVersion";pureMM.maxOccurs="1";pureMM.minOccurs="1" The top level element of the System Description. The System description defines five major elements: Topology, Software, Communication, Mapping and Mapping Constraints. The System element directly aggregates the elements describing the Software, Mapping and Mapping Constraints; it contains a reference to an ASAM FIBEX description specifying Communication and Topology. mmt.qualifiedName="System" atpObject,atpStructureElement The system mapping aggregates all mapping aspects (mapping of SW components to ECUs, mapping of data elements to signals, and mapping constraints). mmt.qualifiedName="SystemMapping" atpObject The data mappings defined. mmt.qualifiedName="dataMapping.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" mmt.qualifiedName="ecuResourceMapping.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Constraints that limit the mapping freedom for the mapping of SW components to ECUs. mmt.qualifiedName="mappingConstraint.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" mmt.qualifiedName="pncMapping.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Resource estimations for this set of mappings, zero or one per ECU instance. mmt.qualifiedName="resourceEstimation.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Constraints that limit the mapping freedom for the mapping of data elements to signals. mmt.qualifiedName="signalPathConstraint.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The mappings of AtomicSoftwareComponent Instances to Implementations. mmt.qualifiedName="swImplMapping.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The mappings of SW components to ECUs. mmt.qualifiedName="swMapping.SystemMapping";pureMM.maxOccurs="-1";pureMM.minOccurs="0" The system mapping aggregates all mapping aspects (mapping of SW components to ECUs, mapping of data elements to signals, and mapping constraints). mmt.qualifiedName="SystemMapping" atpObject The system signal represents the communication system's view of data exchanged between SW components which reside on different ECUs. The system signals allow to represent this communication in a flattened structure, with exactly one system signal defined for each data element prototype sent and received by connected SW component instances. According to the COM Specification, signal groups without signals are allowed. These have a "signalLength" = 0. In this case there shall be an "update-bit" configured. mmt.qualifiedName="SystemSignal" atpObject Optional reference to a SystemSignal's datatype in case the System Description doesn't use a complete Software Component Description (VFB View). This supports the inclusion of legacy system signals. This reference can be used to configure the "ComSignalDataInvalidValue" and the Data Semantics. If a full DataMapping exist for the SystemSignal this information is additionally available from the mapped DataElement. In this case the referenced datatypes needs to be compatible. mmt.qualifiedName="SystemSignal.dataType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Optional reference to a SystemSignal's initValue in case the System Description doesn't use a complete Software Component Description (VFB View). This supports the inclusion of legacy system signals. This reference can be used to configure the Signal's "InitValue". If a full DataMapping exist for the SystemSignal this information may be available from a configured SenderComSpec and ReceiverComSpec. In this case the initvalues in SenderComSpec and/or ReceiverComSpec override this optional value specification. Further restrictions apply from the RTE specification. mmt.qualifiedName="SystemSignal.initValue";pureMM.maxOccurs="1";pureMM.minOccurs="0" Size of the signal in bits. mmt.qualifiedName="SystemSignal.length";pureMM.maxOccurs="1";pureMM.minOccurs="1" The system signal represents the communication system's view of data exchanged between SW components which reside on different ECUs. The system signals allow to represent this communication in a flattened structure, with exactly one system signal defined for each data element prototype sent and received by connected SW component instances. According to the COM Specification, signal groups without signals are allowed. These have a "signalLength" = 0. In this case there shall be an "update-bit" configured. mmt.qualifiedName="SystemSignal" atpObject 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. mmt.qualifiedName="SystemSignalGroup" atpObject Reference to a set of signals that must always be kept together. mmt.qualifiedName="SystemSignalGroup.systemSignal";pureMM.maxOccurs="-1";pureMM.minOccurs="0" 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. mmt.qualifiedName="SystemSignalGroup" atpObject Target destination of the referencing mapping. mmt.qualifiedName="TargetIPduRef" atpObject If no I-Pdu has been received a default value will be distributed. mmt.qualifiedName="defaultValue.TargetIPduRef";pureMM.maxOccurs="1";pureMM.minOccurs="0" IPdu Reference mmt.qualifiedName="TargetIPduRef.targetIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Target destination of the referencing mapping. mmt.qualifiedName="TargetIPduRef" atpObject General element to describe temperature ranges and need for cooling/heating. mmt.qualifiedName="Temperature" atpObject These attributes describe that there is an active cooling system required for this HW Element. mmt.qualifiedName="Temperature.needsCooling";pureMM.maxOccurs="1";pureMM.minOccurs="0" These attributes describe that there is an active heating system required for this HW Element. mmt.qualifiedName="Temperature.needsHeating";pureMM.maxOccurs="1";pureMM.minOccurs="0" It describes the temperature range (max) in which the HW Element can be operated. Unit: Kelvin (K) mmt.qualifiedName="Temperature.operationMax";pureMM.maxOccurs="1";pureMM.minOccurs="0" It describes the temperature range (min) in which the HW Element can be operated. Unit: Kelvin (K) mmt.qualifiedName="Temperature.operationMin";pureMM.maxOccurs="1";pureMM.minOccurs="0" It describes the temperature range (typical) in which the HW Element can be operated. Unit: Kelvin (K) mmt.qualifiedName="Temperature.operationTypical";pureMM.maxOccurs="1";pureMM.minOccurs="0" The storage temperature defines maximum temperature the device is allowed to be stored. The HW Element is not in an operational state. Unit: Kelvin (K) mmt.qualifiedName="Temperature.storageMax";pureMM.maxOccurs="1";pureMM.minOccurs="0" The storage temperature defines minimum temperature the device is allowed to be stored. The HW Element is not in an operational state. Unit: Kelvin (K) mmt.qualifiedName="Temperature.storageMin";pureMM.maxOccurs="1";pureMM.minOccurs="0" General element to describe temperature ranges and need for cooling/heating. mmt.qualifiedName="Temperature" atpObject mmt.qualifiedName="TimeRange" atpObject mmt.qualifiedName="TimeRange.max";pureMM.maxOccurs="1";pureMM.minOccurs="1" mmt.qualifiedName="TimeRange.min";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="TimeRange.typical";pureMM.maxOccurs="1";pureMM.minOccurs="0" mmt.qualifiedName="TimeRange" atpObject The timeRange can be specified with the value attribute. Optionally a tolerance can be defined. mmt.qualifiedName="TimeRangeType" atpObject mmt.qualifiedName="tolerance.TimeRangeType";pureMM.maxOccurs="1";pureMM.minOccurs="0" Average value of a date (in seconds) mmt.qualifiedName="TimeRangeType.value";pureMM.maxOccurs="1";pureMM.minOccurs="1" The timeRange can be specified with the value attribute. Optionally a tolerance can be defined. mmt.qualifiedName="TimeRangeType" atpObject The simplest form is an array of directly coupled D-flip flops, which build up a shift register, with separate output from each stage, thus forming a time-register. A clock signal at the input increments the value of the register. Some cases uses some logic in combination of the shift register in order to form a special adopted representation of the information or to fulfil special requirements. mmt.qualifiedName="Timer" atpObject Defines if the peripheral can automatically be reset during operation. mmt.qualifiedName="Timer.canBeReInit";pureMM.maxOccurs="1";pureMM.minOccurs="0" The direction defines if the counter of a timer counts up, down or if it can be selected. mmt.qualifiedName="Timer.countDirection";pureMM.maxOccurs="1";pureMM.minOccurs="0" single: The timer is counted from a defined start value to a defined end value and then stopped. continuous: The timer is counted from a defined start value to a defined end value and then restarted with the start value. free: The timer is counted always to the available maximum value of the timer structure, then a wrap around occurs and the timer starts again from the HW defined startpoint; e.g. a 16 bit Timer counts from 0(hex)....0FFFF(hex), then after the overflow again from 0(hex)....0FFFF(hex). mmt.qualifiedName="Timer.mode";pureMM.maxOccurs="1";pureMM.minOccurs="1" The simplest form is an array of directly coupled D-flip flops, which build up a shift register, with separate output from each stage, thus forming a time-register. A clock signal at the input increments the value of the register. Some cases uses some logic in combination of the shift register in order to form a special adopted representation of the information or to fulfil special requirements. mmt.qualifiedName="Timer" atpObject TimingEvent references the runnable that need to be started in response to the TimingEvent mmt.qualifiedName="TimingEvent" atpObject Period of timing event in seconds. mmt.qualifiedName="TimingEvent.period";pureMM.maxOccurs="1";pureMM.minOccurs="1" TimingEvent references the runnable that need to be started in response to the TimingEvent mmt.qualifiedName="TimingEvent" atpObject An ECUs TP address on the referenced channel. This represents the diagnostic Address. mmt.qualifiedName="TpAddress" atpObject An ECUs TP address on the referenced channel. This represents the diagnostic Address. mmt.qualifiedName="TpAddress.tpAddress";pureMM.maxOccurs="1";pureMM.minOccurs="1" An ECUs TP address on the referenced channel. This represents the diagnostic Address. mmt.qualifiedName="TpAddress" atpObject TP Node (Sender or Receiver) provides the TP Address and the connection to the Topology description. mmt.qualifiedName="TpNode" atpObject Asscociation to one or more physical connectors (max number of connectors for FlexRay: 2). In a System Description this reference is mandatory. In an ECU Extract this reference is optional (references to ECUs that are not part of the ECU Extract shall be avoided). mmt.qualifiedName="TpNode.connector";pureMM.maxOccurs="-1";pureMM.minOccurs="0" Reference to the TP Address that is used by the TpNode. This reference is optional in case that the multicast TP Address is used (reference from TpConnection). mmt.qualifiedName="TpNode.tpAddress";pureMM.maxOccurs="1";pureMM.minOccurs="0" Requests transmission acknowledgement that data has been sent successfully. Success/failure is reported via a SendPoint of a Runnable. mmt.qualifiedName="TransmissionAcknowledgementRequest" atpObject Number of seconds before an error is reported or in case of allowed redundancy, the value is sent again. mmt.qualifiedName="TransmissionAcknowledgementRequest.timeout";pureMM.maxOccurs="1";pureMM.minOccurs="1" Requests transmission acknowledgement that data has been sent successfully. Success/failure is reported via a SendPoint of a Runnable. mmt.qualifiedName="TransmissionAcknowledgementRequest" atpObject Possibility to attach a condition to each signal within an I-PDU. If at least one condition evaluates to true, TRANSMISSION MODE True shall be used for this I-Pdu. In all other cases, the TRANSMISSION MODE FALSE shall be used. mmt.qualifiedName="TransmissionModeCondition" atpObject Possibilities to define conditions mmt.qualifiedName="dataFilter.TransmissionModeCondition";pureMM.maxOccurs="1";pureMM.minOccurs="1" Reference to a signal to which a condition is attached. mmt.qualifiedName="TransmissionModeCondition.signalInIPdu";pureMM.maxOccurs="1";pureMM.minOccurs="1" Possibility to attach a condition to each signal within an I-PDU. If at least one condition evaluates to true, TRANSMISSION MODE True shall be used for this I-Pdu. In all other cases, the TRANSMISSION MODE FALSE shall be used. mmt.qualifiedName="TransmissionModeCondition" atpObject AUTOSAR COM provides the possibility to define two different TRANSMISSION MODES (True and False) for each I-PDU. In case only the TRUE transmission mode is used there is no need for the "TransmissionModeDeclaration" and its sub-structure. mmt.qualifiedName="TransmissionModeDeclaration" atpObject The Transmission Mode Selector evaluates the conditions for a subset of signals and decides which transmission mode should be used. mmt.qualifiedName="transmissionModeCondition.TransmissionModeDeclaration";pureMM.maxOccurs="-1";pureMM.minOccurs="1" Timing Specification if the COM Transmission Mode is false. The Transmission Mode Selector is defined to be false, if all Conditions evaluate to false. mmt.qualifiedName="transmissionModeFalseTiming.TransmissionModeDeclaration";pureMM.maxOccurs="1";pureMM.minOccurs="0" AUTOSAR COM provides the possibility to define two different TRANSMISSION MODES (True and False) for each I-PDU. In case only the TRUE transmission mode is used there is no need for the "TransmissionModeDeclaration" and its sub-structure. mmt.qualifiedName="TransmissionModeDeclaration" atpObject If the COM Transmission Mode is false the timing is aggregated by the TransmissionModeIFalseTiming element. If the COM Transmission Mode is true the timing is aggregated by the SignalIPdu/IPduTiming element. COM supports the following Transmission Modes: Periodic (Cyclic Timing) Direct /n-times (EventControlledTiming) Mixed (Cyclic and EventControlledTiming are assigned) None (no timing is assigned) mmt.qualifiedName="TransmissionModeFalseTiming" atpObject Periodic Transmission Mode. mmt.qualifiedName="cyclicTiming.TransmissionModeFalseTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" Direct Transmission Mode. mmt.qualifiedName="eventControlledTiming.TransmissionModeFalseTiming";pureMM.maxOccurs="1";pureMM.minOccurs="0" If the COM Transmission Mode is false the timing is aggregated by the TransmissionModeIFalseTiming element. If the COM Transmission Mode is true the timing is aggregated by the SignalIPdu/IPduTiming element. COM supports the following Transmission Modes: Periodic (Cyclic Timing) Direct /n-times (EventControlledTiming) Mixed (Cyclic and EventControlledTiming are assigned) None (no timing is assigned) mmt.qualifiedName="TransmissionModeFalseTiming" atpObject Use <tt> to format technical terms within the paragraph element. mmt.qualifiedName="Tt" atpMixedString,atpObject Schedule entry for an Unassign Frame Id master request where the protected identifier is assigned the value 0x40. This will disable reception/transmission of a previously dynamically assigned frame identifier. mmt.qualifiedName="UnassignFrameIdTiming" atpObject The frame whose identifier is reset by this assignment. mmt.qualifiedName="UnassignFrameIdTiming.unassignedFrameTriggering";pureMM.maxOccurs="1";pureMM.minOccurs="1" Schedule entry for an Unassign Frame Id master request where the protected identifier is assigned the value 0x40. This will disable reception/transmission of a previously dynamically assigned frame identifier. mmt.qualifiedName="UnassignFrameIdTiming" atpObject This is a physical measurement unit. All units that might be defined should stem from SI units. In order to convert one unit into another factor and offset are defined. For the calculation from SI-unit to the defined unit the factor (factorSiToUnit ) and the offset (offsetSiToUnit ) are applied: unit = siUnit * factorSiToUnit + offsetSiToUnit For the calculation from a unit to SI-unit the reciprocal of the factor (factorSiToUnit ) and the negation of the offset (offsetSiToUnit ) are applied: siUnit = (unit - offsetSiToUnit) / factorSiToUnit mmt.qualifiedName="Unit" atpObject mmt.qualifiedName="Unit.displayName";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" this is the factor for the convesion from and to siUnits. mmt.qualifiedName="Unit.factorSiToUnit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" this is the offset for the convesion from and to siUnits. mmt.qualifiedName="Unit.offsetSiToUnit";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="40" This association represents the physical dimension to which the unit belongs to. Note that only values with units of the same physical dimensions might be converted. mmt.qualifiedName="Unit.physicalDimension";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" This is a physical measurement unit. All units that might be defined should stem from SI units. In order to convert one unit into another factor and offset are defined. For the calculation from SI-unit to the defined unit the factor (factorSiToUnit ) and the offset (offsetSiToUnit ) are applied: unit = siUnit * factorSiToUnit + offsetSiToUnit For the calculation from a unit to SI-unit the reciprocal of the factor (factorSiToUnit ) and the negation of the offset (offsetSiToUnit ) are applied: siUnit = (unit - offsetSiToUnit) / factorSiToUnit mmt.qualifiedName="Unit" atpObject mmt.qualifiedName="UnitGroup" atpObject Use <unit> to enter the unit of a parameter. mmt.qualifiedName="UnitGroup.unit";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.sequenceOffset="20" mmt.qualifiedName="UnitGroup" atpObject mmt.qualifiedName="UnitSpec" atpObject mmt.qualifiedName="UnitSpec.unitGroup";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="40";xml.typeElement="false";xml.typeWrapperElement="false" Use <unit> to enter the unit of a parameter. mmt.qualifiedName="UnitSpec.unit";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="50";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="UnitSpec.physicalDimension";pureMM.maxOccurs="-1";pureMM.minOccurs="0";xml.roleElement="true";xml.roleWrapperElement="true";xml.sequenceOffset="60";xml.typeElement="false";xml.typeWrapperElement="false" mmt.qualifiedName="UnitSpec" atpObject Communication attributes specific to unqueued receiving. mmt.qualifiedName="UnqueuedReceiverComSpec" atpObject Specify the amount of time (in seconds) after which the software component (via the RTE) needs to be notified if the corresponding data item have not been received according to the specified timing description. mmt.qualifiedName="UnqueuedReceiverComSpec.aliveTimeout";pureMM.maxOccurs="1";pureMM.minOccurs="1" Specifies strategy of handling the reception of invalidValue. mmt.qualifiedName="UnqueuedReceiverComSpec.handleInvalid";pureMM.maxOccurs="1";pureMM.minOccurs="1" This attribute specifies whether for the corresponding DataElementPrototype the "never received" flag is available. If yes, the RTE is supposed to assume that initially the DataElementPrototype has not been received before. After the first reception of the corresponding DataElementPrototype the flag is cleared. If the value of this attribute is set to TRUE the flag is required. If set to FALSE, the RTE shall not support the "never received" functionality for the corresponding DataElementPrototype. mmt.qualifiedName="UnqueuedReceiverComSpec.handleNeverReceived";pureMM.maxOccurs="1";pureMM.minOccurs="1" Initial value to be used in case the sending component is not yet initialized. If the sender also specifies an init value the receiver's value will be used. mmt.qualifiedName="UnqueuedReceiverComSpec.initValue";pureMM.maxOccurs="1";pureMM.minOccurs="1" Time allowed for resynchronization of data values after current data is lost, e.g. after an ECU reset. mmt.qualifiedName="UnqueuedReceiverComSpec.resyncTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Communication attributes specific to unqueued receiving. mmt.qualifiedName="UnqueuedReceiverComSpec" atpObject Communication attributes specific to distribution of data (P-Port, sender-receiver interface and data element carries "data" opposed to carrying an "event"). mmt.qualifiedName="UnqueuedSenderComSpec" atpObject Flag whether the component can actively invalidate data. mmt.qualifiedName="UnqueuedSenderComSpec.canInvalidate";pureMM.maxOccurs="1";pureMM.minOccurs="1" Init value to be sent if sender component is not yet fully initialized, but receiver needs data already. mmt.qualifiedName="UnqueuedSenderComSpec.initValue";pureMM.maxOccurs="1";pureMM.minOccurs="1" Communication attributes specific to distribution of data (P-Port, sender-receiver interface and data element carries "data" opposed to carrying an "event"). mmt.qualifiedName="UnqueuedSenderComSpec" atpObject This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. mmt.qualifiedName="Url" atpObject This is the url itself mmt.qualifiedName="Url.value";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.roleElement="false";xml.roleWrapperElement="false";xml.typeElement="false";xml.typeWrapperElement="false" This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. mmt.qualifiedName="Url" atpObject this denotes the mime type of the resource located by the url. mmt.qualifiedName="Url.mimeType";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.attribute="true" This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. mmt.qualifiedName="Url" atpObject UserDefinedIPdu allows to describe PDU-based communication over Complex Communication Drivers. If a new BSW module is added above the PduR (e.g. a Diagnostic Service ) then this IPdu element shall be used to describe the communication. mmt.qualifiedName="UserDefinedIPdu" atpObject This attribute defines the CDD that transmits or receives the UserDefinedPdu. If several CDDs are defined this attribute is used to distinguish between them. mmt.qualifiedName="UserDefinedIPdu.cddType";pureMM.maxOccurs="1";pureMM.minOccurs="0" UserDefinedIPdu allows to describe PDU-based communication over Complex Communication Drivers. If a new BSW module is added above the PduR (e.g. a Diagnostic Service ) then this IPdu element shall be used to describe the communication. mmt.qualifiedName="UserDefinedIPdu" atpObject UserDefinedPdu allows to describe PDU-based communication over Complex Communication Drivers. If a new BSW module is added above the BusIf (e.g. a new Nm module or XCP) then this Pdu element shall be used to describe the communication. mmt.qualifiedName="UserDefinedPdu" atpObject This attribute defines the CDD that transmits or receives the UserDefinedIPdu. If several CDDs are defined this attribute is used to distinguish between them. mmt.qualifiedName="UserDefinedPdu.cddType";pureMM.maxOccurs="1";pureMM.minOccurs="0" UserDefinedPdu allows to describe PDU-based communication over Complex Communication Drivers. If a new BSW module is added above the BusIf (e.g. a new Nm module or XCP) then this Pdu element shall be used to describe the communication. mmt.qualifiedName="UserDefinedPdu" atpObject Use <v> to enter a numerical value. mmt.qualifiedName="V" atpMixedString,atpObject Value calculated via a system constant. This element is included in every case, where parameters should be generated from numerical values during compile time (not runtime!). Thus for example, the influence of the cylinder number on conversion formulae, can be introduced in a repeatable manner. mmt.qualifiedName="Vf" atpMixedString,atpObject <vt> represents one particular textual value of the calibration item. mmt.qualifiedName="Vt" atpMixedString,atpObject mmt.qualifiedName="Vt.xml:space";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.attribute="true" <vt> represents one particular textual value of the calibration item. mmt.qualifiedName="Vt" atpMixedString,atpObject This defines a wait-point for which the runnable can wait. mmt.qualifiedName="WaitPoint" atpObject Time in seconds before the waitpoint times out and the blocking wait call returns with an error indicating the timeout. mmt.qualifiedName="WaitPoint.timeout";pureMM.maxOccurs="1";pureMM.minOccurs="1" Events this wait point is waiting for. mmt.qualifiedName="WaitPoint.trigger";pureMM.maxOccurs="1";pureMM.minOccurs="1" This defines a wait-point for which the runnable can wait. mmt.qualifiedName="WaitPoint" atpObject This attribut indicates wheter the software component reading this value provides dedicated runnables to handle a wake-up call by the IoHwAbstraction layer. mmt.qualifiedName="WakeUp" atpObject A form of interval timer, which is used to detect a possible malfunction of the processing unit. The timer is started as a countdown and has to be triggered within a specific time. Either the trigger only has to occur before the count-down runs out, or the trigger has to occur within a specific window before the timeout, therefore a trigger too early will also set off the watchdog. If the trigger is not correctly performed the watchdog will set off and will initiate an interrupt or perform a reset of the whole processing unit or ECU. The watchdog can be implemented in software or hardware and if the implementation is in hardware it can be integrated into the processing unit or connected externally. Depending on the complexity of the watchdog the interfacing is either a serial communication or some discrete I/O lines. Also the trigger itself can be just some digital peak or can be some calculated request-response mechanism. The actual handling of the watchdog has to be covered by some specific driver software. The watchdog will use at least an interrupt of the processing unit and also some peripheral connections for the control and set-up. To enable different operating modes of the processing unit and the ECU it is important to specify if the watchdog can be disabled (e.g. during flash programming). mmt.qualifiedName="WatchDog" atpObject The clock input to a timer can have different sources like the internal system clock or an external clock. If the clock is pre-scaled this information should be entered in the table. mmt.qualifiedName="WatchDog.clockSource";pureMM.maxOccurs="1";pureMM.minOccurs="0" A Watchdog can be running in different modes. In normal mode must the watchdog be kicked within a certain maximum time. In the windowed mode there is also a lower limit of the time when the watchdog has to be kicked. In debug mode is the watchdog disabled. Sometimes it's also required that the watchdog can be disabled and enabled during software download. To ensure that this mode is not entered in normal operation there is often some kind of security procedure to enter the mode. mmt.qualifiedName="WatchDog.mode";pureMM.maxOccurs="1";pureMM.minOccurs="1" The threshold is the definition of a counter value. When the counter has reached this value some action is performed, e.g. an interrupt can be generated. mmt.qualifiedName="WatchDog.thresholdValue";pureMM.maxOccurs="-1";pureMM.minOccurs="0" A form of interval timer, which is used to detect a possible malfunction of the processing unit. The timer is started as a countdown and has to be triggered within a specific time. Either the trigger only has to occur before the count-down runs out, or the trigger has to occur within a specific window before the timeout, therefore a trigger too early will also set off the watchdog. If the trigger is not correctly performed the watchdog will set off and will initiate an interrupt or perform a reset of the whole processing unit or ECU. The watchdog can be implemented in software or hardware and if the implementation is in hardware it can be integrated into the processing unit or connected externally. Depending on the complexity of the watchdog the interfacing is either a serial communication or some discrete I/O lines. Also the trigger itself can be just some digital peak or can be some calculated request-response mechanism. The actual handling of the watchdog has to be covered by some specific driver software. The watchdog will use at least an interrupt of the processing unit and also some peripheral connections for the control and set-up. To enable different operating modes of the processing unit and the ECU it is important to specify if the watchdog can be disabled (e.g. during flash programming). mmt.qualifiedName="WatchDog" atpObject WorstCaseExecutionTime provides an analytic method for specifying the minimum and maximum execution time. mmt.qualifiedName="WorstCaseExecutionTime" atpObject Maximum WorstCaseExecutionTime. mmt.qualifiedName="WorstCaseExecutionTime.maximalExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" Minimum WorstCaseExecutionTime. mmt.qualifiedName="WorstCaseExecutionTime.minimalExecutionTime";pureMM.maxOccurs="1";pureMM.minOccurs="1" WorstCaseExecutionTime provides an analytic method for specifying the minimum and maximum execution time. mmt.qualifiedName="WorstCaseExecutionTime" atpObject Provides a formal worst case heap usage. mmt.qualifiedName="WorstCaseHeapUsage" atpObject Worst case heap consumption. mmt.qualifiedName="WorstCaseHeapUsage.memoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" Provides a formal worst case heap usage. mmt.qualifiedName="WorstCaseHeapUsage" atpObject Provides a formal worst case stack usage. mmt.qualifiedName="WorstCaseStackUsage" atpObject Worst case stack consumption. mmt.qualifiedName="WorstCaseStackUsage.memoryConsumption";pureMM.maxOccurs="1";pureMM.minOccurs="1" Provides a formal worst case stack usage. mmt.qualifiedName="WorstCaseStackUsage" atpObject Use <xdoc> , to reference an external document. mmt.qualifiedName="Xdoc" atpObject Use <xfile> , to reference an external file. mmt.qualifiedName="Xfile" atpObject mmt.qualifiedName="Xfile.shortName";pureMM.maxOccurs="1";pureMM.minOccurs="1";xml.sequenceOffset="10" Use <longName1> to create a comprehensive name for the context element mmt.qualifiedName="Xfile.longName1";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="20" This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. mmt.qualifiedName="Xfile.url";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element describes the tool which was used to generate the corresponding <xfile> . Kept as a string. mmt.qualifiedName="Xfile.tool";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" This element describes the tool version which was used to generate the corresponding <xfile> . Kept as a string. mmt.qualifiedName="Xfile.toolVersion";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" Use <xfile> , to reference an external file. mmt.qualifiedName="Xfile" atpObject This meta class represents the ability to refer to an external file in a standalone context. Note that Xfile does the same but embedded in a documentation block paragraph. This meta class maintains backward compatibility of xml schema wrt. to Code.xfile and Dependency.xfile. mmt.qualifiedName="XfileSo" atpObject This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. mmt.qualifiedName="XfileSo.url";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="30" This element describes the tool which was used to generate the corresponding <xfile> . Kept as a string. mmt.qualifiedName="XfileSo.tool";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="50" This element describes the tool version which was used to generate the corresponding <xfile> . Kept as a string. mmt.qualifiedName="XfileSo.toolVersion";pureMM.maxOccurs="1";pureMM.minOccurs="0";xml.sequenceOffset="60" This meta class represents the ability to refer to an external file in a standalone context. Note that Xfile does the same but embedded in a documentation block paragraph. This meta class maintains backward compatibility of xml schema wrt. to Code.xfile and Dependency.xfile. mmt.qualifiedName="XfileSo" atpObject Use <xref> , to generate cross-references within the document. mmt.qualifiedName="Xref" atpMixedString,atpObject This element specifies a reference target which can be scattered throughout the text. mmt.qualifiedName="XrefTarget" atpObject