|
ODX-Checker rule set documentation |
ASAM ODX 2.0.1 |
| rule name | ASAM_001 [848] |
| severity | warn |
| runtime relevance | false |
| short description | Every LANGUAGE element must contain an ISO 639-2T compliant value. |
| full description | Every LANGUAGE element must contain an ISO 639-2T compliant value. |
| rule name | ASAM_003 [808] |
| severity | error |
| runtime relevance | false |
| short description | Every SHORT-NAME must match the regular expression [a-zA-Z0-9_]+. |
| full description | A SHORT-NAME must only contain digits, letters and underscores '_'. |
| rule name | ASAM_004 [837] |
| severity | error |
| runtime relevance | true |
| short description | A DIAG-COMM must only reference COMPARAMs that reside in a COMPARAM-SPEC of the supported PROTOCOLs. |
| full description | A DIAG-COMM must only reference COMPARAMs that reside in a COMPARAM-SPEC of the supported PROTOCOLs. If PROTOCOL-SNREFS is set, all supported PROTOCOLs are listed there and no PROTOCOL is supported implicitly. If PROTOCOL-SNREFS is not set, then all PROTOCOLs within the current layer hierarchy are supported. |
| rule name | ASAM_005 [808] |
| severity | warn |
| runtime relevance | true |
| short description | SYNTAX within PROG-CODE must match one of the values 'JAVA', 'CLASS' or 'JAR'. |
| full description | SYNTAX within PROG-CODE must match one of the values 'JAVA', 'CLASS' or 'JAR'. |
| rule name | ASAM_006 [808] |
| severity | warn |
| runtime relevance | true |
| short description | If SYNTAX is neither 'JAVA' nor 'CLASS' ENTRYPOINT must be specified, otherwise it must not be set. |
| full description | If SYNTAX is neither 'JAVA' nor 'CLASS' ENTRYPOINT must be specified, otherwise it must not be set. |
| rule name | ASAM_007 [850] |
| severity | error |
| runtime relevance | true |
| short description | MATCHING-REQUEST-PARAM must refer to a byte position that is not outside the corresponding REQUESTs range. |
| full description | REQUEST-BYTE-POS added to BYTE-LENGTH must be less than or equal to the request byte length belonging to the same DIAG-COMM. |
| rule name | ASAM_008 [817] |
| severity | error |
| runtime relevance | true |
| short description | The PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP of a SYSTEM parameter must correspond to the SYSPARAM attribute. |
| full description | BASE-DATA-TYPE at PHYSICAL-TYPE of the referenced DOP of a SYSTEM parameter must be A_BYTEFIELD in case of SYSPARAM=TESTERID or SYSPARAM=USERID and A_UINT32 otherwise. |
| rule name | ASAM_009 [808] |
| severity | error |
| runtime relevance | true |
| short description | Value of BIT-LENGTH must be greater than 0. |
| full description | Value of BIT-LENGTH must be greater than 0. |
| rule name | ASAM_010 [808] |
| severity | error |
| runtime relevance | true |
| short description | Value of BIT-POSITION must be less than 8. |
| full description | Value of BIT-POSITION must be less than 8. |
| rule name | ASAM_011 [808] |
| severity | error |
| runtime relevance | false |
| short description | The attributes DISPLAY-RADIX and PRECISION of PHYSICAL-TYPE must only be set if the BASE-DATA-TYPE is A_UINT32 or respectively A_FLOAT32 or A_FLOAT64. |
| full description | The attributes DISPLAY-RADIX and PRECISION of PHYSICAL-TYPE must only be set if the BASE-DATA-TYPE is A_UINT32 or respectively A_FLOAT32 or A_FLOAT64. |
| rule name | ASAM_012 [808] |
| severity | error |
| runtime relevance | true |
| short description | MIN-LENGTH must be less than or equal to MAX-LENGTH. |
| full description | DIAG-CODED-TYPE/MIN-LENGTH must be less than or equal to DIAG-CODED-TYPE/MAX-LENGTH. |
| rule name | ASAM_014 [808] |
| severity | error |
| runtime relevance | true |
| short description | Ranges of SCALE-CONSTRs within a common INTERNAL-CONSTRS must not overlap. |
| full description | Ranges of SCALE-CONSTRs within a common INTERNAL-CONSTRS must not overlap. |
| rule name | ASAM_015 [808] |
| severity | error |
| runtime relevance | true |
| short description | MIN-NUMBER-OF-ITEMS must be less than or equal to MAX-NUMBER-OF-ITEMS. |
| full description | MIN-NUMBER-OF-ITEMS at END-OF-PDU-FIELD must be lower than or equal to MAX-NUMBER-OF-ITEMS. |
| rule name | ASAM_016 [808] |
| severity | error |
| runtime relevance | true |
| short description | For every CASE LOWER-LIMIT must be less than or equal to UPPER-LIMIT. |
| full description | For every MUX' CASE and DEFAULT-CASE LOWER-LIMIT must be less than or equal to UPPER-LIMIT. |
| rule name | ASAM_017 [808] |
| severity | error |
| runtime relevance | true |
| short description | The DOP referenced by DETERMINE-NUMBER-OF-ITEMS must have PHYSICAL-TYPE/BASE-DATA-TYPE set to A_UINT32. |
| full description | The DOP referenced by a DYNAMIC-LENGTH-FIELD/DETERMINE-NUMBER-OF-ITEMS must have PHYSICAL-TYPE/BASE-DATA-TYPE = A_UINT32. |
| rule name | ASAM_018 [808] |
| severity | error |
| runtime relevance | true |
| short description | Every TROUBLE-CODE must be unique inside of one DTC-DOP. |
| full description | Every TROUBLE-CODE must be unique inside of one DTC-DOP. |
| rule name | ASAM_019 [827] |
| severity | error |
| runtime relevance | true |
| short description | A PARAM, which is referenced by an ENV-DATA-DESC, must refer to a DATA-OBJECT-PROP or DTC-DOP with PHYSICAL-TYPE/BASE-DATA-TYPE set to A_UINT32. |
| full description | A PARAM, which is referenced by an ENV-DATA-DESC, must refer to a DATA-OBJECT-PROP or DTC-DOP with PHYSICAL-TYPE/BASE-DATA-TYPE set to A_UINT32. |
| rule name | ASAM_020 [808] |
| severity | error |
| runtime relevance | true |
| short description | ALL-VALUE must not occur more than once per ENV-DATA-DESC. |
| full description | Only one ENV-DATA with set ALL-VALUE element is allowed per ENV-DATA-DESC. |
| rule name | ASAM_021 [808] |
| severity | error |
| runtime relevance | true |
| short description | All DTC-VALUEs must be unique. |
| full description | Every ENV-DATA/DTC-VALUE must be unique inside one ENV-DATA-DESC. |
| rule name | ASAM_022 [850] |
| severity | error |
| runtime relevance | true |
| short description | The parameter referenced by COMM-RELATION via IN-/OUT-PARAM-IF-SNREF must exist at the referenced DIAG-COMM. |
| full description | The parameter referenced by COMM-RELATION via IN-/OUT-PARAM-IF-SNREF must exist at the DIAG-COMM which is also referenced by COMM-RELATION. If the referenced DIAG-COMM is a DIAG-SERVICE, the IN-PARAM-IF-SNREF must exist in the REQUEST referenced by DIAG-SERVICE and the OUT-PARAM-IF-SNREF must exist in one of the POS-RESPONSEs. If the DIAG-COMM is a SINGLE-ECU-JOB, then the IN-PARAM-IF-SNREF must exist among its INPUT-PARAMS and the OUT-PARAM-IF-SNREF among its OUTPUT-PARAMS. |
| rule name | ASAM_023 [817] |
| severity | warn |
| runtime relevance | true |
| short description | The parameter referenced by MATCHING-PARAMETER via OUT-PARAM-IF-SNREF must exist in all POS-RESPONSEs of the referenced DIAG-COMM and must refer to a DATA-OBJECT-PROP. |
| full description | The parameter referenced by MATCHING-PARAMETER via OUT-PARAM-IF-SNREF must exist in all POS-RESPONSEs of the referenced DIAG-COMM and must refer to a DATA-OBJECT-PROP. |
| rule name | ASAM_024 [808] |
| severity | error |
| runtime relevance | true |
| short description | ODXLINKs in a COMPARAM-SPEC must not use the DOCREF attribute. |
| full description | ODXLINKs in a COMPARAM-SPEC must not use the DOCREF attribute. |
| rule name | ASAM_025 [817] |
| severity | warn |
| runtime relevance | true |
| short description | The parameter referenced by MATCHING-COMPONENT must exist in the referenced DIAG-SERVICE or SINGLE-/MULTIPLE-ECU-JOB. |
| full description | If MATCHING-COMPONENT references a DIAG-SERVICE, the parameter referenced via OUT-PARAM-IF-SNREF must exist in all of its POS-RESPONSEs. If a SINGLE- or MULTIPLE-ECU-JOB is referenced, then the parameter must exist in its OUTPUT-PARAMS. |
| rule name | ASAM_027 [817] |
| severity | error |
| runtime relevance | true |
| short description | The target of a LOGICAL-LINK must be unambiguous. |
| full description | A LOGICAL-LINK that references a BASE-VARIANT which inherits from several PROTOCOLs (directly or indirectly from FUNCTIONAL-GROUPs) must also reference one of these PROTOCOLs or one of these FUNCTIONAL-GROUPs, so its target becomes unambiguous. |
| rule name | ASAM_028 [828] |
| severity | error |
| runtime relevance | true |
| short description | The parameter referenced by IDENT-DESC must exist. |
| full description | If IDENT-DESC references a DIAG-SERVICE the parameter referenced by OUT-PARAM-IF-SNREF must exist in all POS-RESPONSEs and if IDENT-DESC references a SINGLE-ECU-JOB it must exist in its OUTPUT-PARAMs. |
| rule name | ASAM_029 [808] |
| severity | error |
| runtime relevance | true |
| short description | LAYER-REF must only point to BASE- or ECU-VARIANT. |
| full description | Only BASE-VARIANT and ECU-VARIANT are valid targets for LAYER-REF in ECU-MEM-CONNECTOR. |
| rule name | ASAM_030 [808] |
| severity | warn |
| runtime relevance | true |
| short description | DOP-BASE elements defined in a MULTIPLE-ECU-JOB-SPEC must not set the IS-HIGHLOW-BYTE-ORDER attribute. |
| full description | Within a MULTIPLE-ECU-JOB-SPEC the attribute IS-HIGHLOW-BYTE-ORDER must remain unset for all DOP-BASE elements (=DATA-OBJECT-PROPs, all COMPLEX-DOPs, DTC-DOPs). |
| rule name | ASAM_031 [837] |
| severity | error |
| runtime relevance | true |
| short description | ODXLINK must only point to visible elements. |
| full description | ODXLINK must only point to elements that are visible from the current layer through inheritance or import. |
| rule name | ASAM_032 [806] |
| severity | error |
| runtime relevance | true |
| short description | Cyclic references are not allowed. |
| full description | No direct or indirect cycles must arise from the use of ODXLINKs. |
| rule name | ASAM_033 [808] |
| severity | error |
| runtime relevance | true |
| short description | ODXLINK must reference an existing element. |
| full description | ODXLINK must reference an existing element. |
| rule name | ASAM_035 [827] |
| severity | error |
| runtime relevance | false |
| short description | PHYSICAL-DEFAULT-VALUE VALUE must only exist if a DATA-OBJECT-PROP is referenced. |
| full description | PHYSICAL-DEFAULT-VALUE in PARAM of type VALUE must only exist if the referenced DOP-BASE element is a DATA-OBJECT-PROP. |
| rule name | ASAM_036 [808] |
| severity | error |
| runtime relevance | true |
| short description | A SHORT-NAME must not have more than 128 characters. |
| full description | A SHORT-NAME must not have more than 128 characters. |
| rule name | ASAM_038 [808] |
| severity | error |
| runtime relevance | true |
| short description | PHYSICAL-TYPE/BASE-DATA-TYPE of DTC-DOP must be A_UINT32. |
| full description | The BASE-DATA-TYPE of the PHYSICAL-TYPE of a DTC-DOP must always be set to A_UINT32. |
| rule name | ASAM_039 [808] |
| severity | error |
| runtime relevance | true |
| short description | Every DIAG-LAYER (except PROTOCOL and ECU-SHARED-DATA) must inherit from a PROTOCOL. |
| full description | At least one PROTOCOL must exist in the inheritance hierarchy of every DIAG-LAYER. For ECU-SHARED-DATA this rule does not apply. |
| rule name | ASAM_041 [817] |
| severity | error |
| runtime relevance | false |
| short description | REQUEST and RESPONSE must not have more than one PARAM with SEMANTIC=SERVICE-ID each. |
| full description | REQUEST and RESPONSE must not have more than one PARAM which has its SEMANTIC attribute set to SERVICE-ID. |
| rule name | ASAM_042 [808] |
| severity | error |
| runtime relevance | false |
| short description | IS-HIGHLOW-BYTE-ORDER must not be set, if the DIAG-CODED-TYPE is not of type LEADING-LENGTH-INFO-TYPE and BASE-DATA-TYPE is A_BYTEFIELD, A_ASCIISTRING or A_UTF8STRING. |
| full description | IS-HIGHLOW-BYTE-ORDER must not be set, if the BASE-DATA-TYPE of the DIAG-CODED-TYPE is A_BYTEFIELD, A_ASCIISTRING or A_UTF8STRING or else the DIAG-CODED-TYPE must be of type LEADING-LENGTH-INFO-TYPE. |
| rule name | ASAM_043 [808] |
| severity | error |
| runtime relevance | true |
| short description | INTERNAL-CONSTR is only allowed for ordered types. |
| full description | INTERNAL-CONSTR must only be specified if the BASE-DATA-TYPE of the DIAG-CODED-TYPE is an ordered type. Ordered types are A_BYTEFIELD, A_INT32, A_UINT32, A_FLOAT32 and A_FLOAT64. |
| rule name | ASAM_044 [808] |
| severity | error |
| runtime relevance | true |
| short description | The DIAG-CODED-TYPE of the DOP referenced by SWITCH-KEY must be a STANDARD-LENGTH-TYPE. |
| full description | The DIAG-CODED-TYPE of the DATA-OBJECT-PROP referenced by SWITCH-KEY in MUX must be of type STANDARD-LENGTH-TYPE. |
| rule name | ASAM_046 [808] |
| severity | error |
| runtime relevance | true |
| short description | If no CASES are specified in a MUX a DEFAULT-CASE must be given. |
| full description | If no CASES are specified in a MUX then a DEFAULT-CASE must be given. |
| rule name | ASAM_047 [836] |
| severity | error |
| runtime relevance | true |
| short description | COMPARAM-REFs within a common COMPARAM-REFS wrapper must be unique. |
| full description | COMPARAM-REFs within a common COMPARAM-REFS wrapper must not reference the same COMPARAM multiple times. |
| rule name | ASAM_049 [808] |
| severity | error |
| runtime relevance | false |
| short description | A final DIAG-COMM must not be overwritten. |
| full description | A DIAG-COMM which has its IS-FINAL attribute set to true must not be overwritten. |
| rule name | ASAM_050 [808] |
| severity | error |
| runtime relevance | true |
| short description | DIAG-LAYERs must establish only allowed inheritance relationships. |
| full description | DIAG-LAYERs must establish only permitted inheritance relationships. Permitted relationships are: Every DIAG-LAYER type except ECU-SHARED-DATA may inherit from arbitrary number of ECU-SHARED-DATAs. A FUNCTIONAL-GROUP may inherit from an arbitrary number of PROTOCOLs. A BASE-VARIANT may inherit from an arbitrary number of FUNCTIONAL-GROUPs and PROTOCOLs. An ECU-VARIANT may inherit from exactly one BASE-VARIANT. |
| rule name | ASAM_051 [822] |
| severity | error |
| runtime relevance | false |
| short description | Every Bit of a REQUEST must be covered by exactly one PARAM. |
| full description | Every Bit of a REQUEST must be covered by exactly one PARAM. The last byte of the REQUEST must be complete (no half bytes). No gaps may result from bitmasks. Objects with potentially volatile length (strings, bytefields, TABLEs) must either be programmed in a way that their length can be determined at compile time (and is constant) or must be placed at the end of the REQUEST. I.e. it must be guaranteed that in no case a bit of the REQUEST remains unset or is being multiply assigned. |
| rule name | ASAM_052 [808] |
| severity | error |
| runtime relevance | true |
| short description | A COMPU-METHOD of CATEGORY TAB-INTP must have a numerical LOWER-LIMIT and no UPPER-LIMIT in every COMPU-SCALE. |
| full description | A COMPU-METHOD of CATEGORY TAB-INTP must have a numerical LOWER-LIMIT and no UPPER-LIMIT in every COMPU-INTERNAL-TO-PHYS//COMPU-SCALE. |
| rule name | ASAM_053 [808] |
| severity | error |
| runtime relevance | true |
| short description | A COMPU-METHOD of CATEGORY COMPUCODE must have a PROG-CODE in COMPU-INTERNAL-TO-PHYS. |
| full description | A COMPU-METHOD of CATEGORY COMPUCODE must have a PROG-CODE in COMPU-INTERNAL-TO-PHYS. |
| rule name | ASAM_054 [808] |
| severity | error |
| runtime relevance | true |
| short description | A UNIT must be specified completely. |
| full description | If a UNIT specifies one of the elements PHYSICAL-DIMENSION-REF, FACTOR-SI-TO-UNIT and OFFSET-SI-TO-UNIT, then the remaining two must be specified too. |
| rule name | ASAM_055 [808] |
| severity | error |
| runtime relevance | true |
| short description | No DIAG-LAYER must inherit from another DIAG-LAYER and simultaneously import it. |
| full description | No DIAG-LAYER must inherit from another DIAG-LAYER and simultaneously import it. |
| rule name | ASAM_056 [850] |
| severity | error |
| runtime relevance | true |
| short description | SHORT-NAMEs must be unique within their specified NAMESPACES. |
| full description | SHORT-NAMEs must be unique within their specified NAMESPACES. This rule also applies for elements that are imported via ODXLINK in a proxy wrapper. Proxy wrappers are: DIAG-COMM-PROXY, DTC-PROXY, ENV-DATA-PROXY, DIAG-VARIABLE-PROXY and TABLE-ROW. |
| rule name | ASAM_057 [812] |
| severity | error |
| runtime relevance | true |
| short description | Each SCALE-CONSTR must fit into the corresponding INTERNAL-CONSTR. |
| full description | Each range of SCALE-CONSTR must fit into the INTERNAL-CONSTR range. |
| rule name | ASAM_058 [832] |
| severity | error |
| runtime relevance | true |
| short description | The DIAG-COMM, referenced by ACCESS-LEVEL, COMM-RELATION, DIAG-SERVICE or MATCHING-PARAMETER must be visible. |
| full description | ACCESS-LEVEL, COMM-RELATION, DIAG-SERVICE and MATCHING-PARAMETER may only reference a DIAG-COMM which resides in the enclosing layers inheritance hierarchy. |
| rule name | ASAM_059 [808] |
| severity | error |
| runtime relevance | true |
| short description | BASE-DATA-TYPE of DIAG-CODED- and PHYSICAL-TYPE of a DATA-OBJECT-PROP with COMPU-METHOD/CATEGORY=IDENTICAL must be identical. |
| full description | BASE-DATA-TYPE of DIAG-CODED-TYPE and PHYSICAL-TYPE of a DATA-OBJECT-PROP must be identical if COMPU-METHOD/CATEGORY is IDENTICAL. String types are an exception to this rule - they are regarded compatible among each other. |
| rule name | ASAM_060 [808] |
| severity | error |
| runtime relevance | true |
| short description | The BASE-DATA-TYPEs of DIAG-CODED- and PHYSICAL-TYPE must be suitable for the COMPU-METHOD/COMPU-CATEGORY. |
| full description | BASE-DATA-TYPEs of DIAG-CODED-TYPE and PHYSICAL-TYPE must be numeric if COMPU-METHOD/COMPU-CATEGORY is LINEAR, SCALE-LINEAR, TAB-INTP, RAT-FUNC or SCALE-RAT-FUNC. |
| rule name | ASAM_061 [808] |
| severity | error |
| runtime relevance | true |
| short description | PHYSICAL-TYPE/BASE-DATA-TYPE must be A_UNICODE2STRING if COMPU-CATEGORY is TEXTTABLE. |
| full description | PHYSICAL-TYPE/BASE-DATA-TYPE must be A_UNICODE2STRING if COMPU-CATEGORY is TEXTTABLE. |
| rule name | ASAM_062 [808] |
| severity | error |
| runtime relevance | true |
| short description | DIAG-CODED-TYPE/BASE-DATA-TYPE must be A_INT32, A_UINT32, A_UNICODE2STRING, A_ASCIISTRING, A_UTF8STRING or A_BYTEFIELD if COMPU-CATEGORY is TEXTTABLE. |
| full description | DIAG-CODED-TYPE/BASE-DATA-TYPE must be A_INT32, A_UINT32, A_UNICODE2STRING, A_ASCIISTRING, A_UTF8STRING or A_BYTEFIELD if COMPU-CATEGORY is TEXTTABLE. |
| rule name | ASAM_063 [808] |
| severity | warn |
| runtime relevance | false |
| short description | If COMPU-METHOD/CATEGORY is IDENTICAL, then no conversion method must be defined. |
| full description | Neither COMPU-INTERNAL-TO-PHYS nor COMPU-PHYS-TO-INTERNAL must be defined if COMPU-METHOD/CATEGORY is IDENTICAL. |
| rule name | ASAM_064 [808] |
| severity | error |
| runtime relevance | true |
| short description | No more than one COMPU-SCALE is allowed if CATEGORY is LINEAR or RAT-FUNC. |
| full description | No more than one COMPU-SCALE is allowed if CATEGORY is LINEAR or RAT-FUNC. |
| rule name | ASAM_068 [828] |
| severity | error |
| runtime relevance | false |
| short description | OUT-PARAM-IF-SNREF inside an IDENT-DESC must refer to a DATA-OBJECT-PROP. |
| full description | OUT-PARAM-IF-SNREF inside an IDENT-DESC must refer to a DATA-OBJECT-PROP. |
| rule name | ASAM_069 [808] |
| severity | error |
| runtime relevance | false |
| short description | TYPE of all IDENT-VALUES in a common IDENT must be identical. |
| full description | The value of the TYPE attribute of all IDENT-VALUES in a common EXPECRED-IDENT must be identical. |
| rule name | ASAM_070 [832] |
| severity | error |
| runtime relevance | false |
| short description | The TYPE of all IDENT-VALUEs of an IDENT which is referenced by an IDENT-DESC must match the PHYSICAL-TYPE/BASE-DATA-TYPE of the DOP referenced by IN-/OUT-PARAM-IF-SNREF. |
| full description | The datatype which is specified by the TYPE attribute of IDENT-VALUE must match the BASE-DATA-TYPE of the PHYSICAL-TYPE of the DOP belonging to the parameter which is referenced via IN-/OUT-PARAM-IF-SNREF by an IDENT-DESC for all IDENT-VALUEs of an IDENT which is also referenced by the IDENT-DESC (in ECU-MEM-CONNECTOR). In case of DIAG-SERVICE this rule is applied to each POS-RESPONSE of the service. In case of SINGLE-ECU-JOB it is applied to the OUTPUT-PARAM with the given SHORT-NAME. |
| rule name | ASAM_071 [808] |
| severity | error |
| runtime relevance | false |
| short description | The START-ADDRESS of an ADDRDEF-PHYS-SEGMENT must be less or equal to END-ADDRESS. |
| full description | The START-ADDRESS of an ADDRDEF-PHYS-SEGMENT must be less or equal to END-ADDRESS. |
| rule name | ASAM_072 [808] |
| severity | error |
| runtime relevance | false |
| short description | SOURCE-START-ADDRESS in CHECKSUM must be less or equal to SOURCE-END-ADDRESS. |
| full description | SOURCE-START-ADDRESS in CHECKSUM must be less or equal to SOURCE-END-ADDRESS. |
| rule name | ASAM_073 [808] |
| severity | error |
| runtime relevance | false |
| short description | FILTER-START in ADDRDEF-FILTER must be less or equal to FILTER-END. |
| full description | FILTER-START in ADDRDEF-FILTER must be less or equal to FILTER-END. |
| rule name | ASAM_074 [808] |
| severity | error |
| runtime relevance | false |
| short description | SOURCE-START-ADDRESS in SEGMENT must be less or equal to SOURCE-END-ADDRESS. |
| full description | SOURCE-START-ADDRESS in SEGMENT must be less or equal to SOURCE-END-ADDRESS. |
| rule name | ASAM_075 [839] |
| severity | error |
| runtime relevance | false |
| short description | The values of SECURITY-METHOD, FW-CHECKSUM, VALIDITY-FOR, FW-SIGNATURE, CHECKSUM-RESULT, IDENT-VALUE and ENCRYPT-COMPRESS-METHOD must conform to their TYPE attributes. |
| full description | The values of SECURITY-METHOD, FW-CHECKSUM, VALIDITY-FOR, FW-SIGNATURE, CHECKSUM-RESULT, IDENT-VALUE and ENCRYPT-COMPRESS-METHOD must be interpretable as values of the datatype specified in the corresponding TYPE attribute. |
| rule name | ASAM_076 [808] |
| severity | error |
| runtime relevance | false |
| short description | Ranges of SEGMENTs within the same DATABLOCK may not overlap. |
| full description | Ranges of SEGMENTs within the same DATABLOCK may not overlap. |
| rule name | ASAM_077 [808] |
| severity | error |
| runtime relevance | false |
| short description | Ranges of FILTERs within the same DATABLOCK may not overlap. |
| full description | Ranges of FILTERs within the same DATABLOCK may not overlap. |
| rule name | ASAM_078 [808] |
| severity | error |
| runtime relevance | false |
| short description | SEGMENTs must be in the FILTER range of their DATABLOCK. |
| full description | Every SEGMENT must be completely in a range defined by one ore more FILTERs of the same DATABLOCK. |
| rule name | ASAM_079 [808] |
| severity | error |
| runtime relevance | false |
| short description | FILTER-SIZE inside SIZEDEF-FILTER must be greater than zero. |
| full description | FILTER-SIZE inside SIZEDEF-FILTER must be greater than zero. |
| rule name | ASAM_080 [808] |
| severity | error |
| runtime relevance | false |
| short description | UNCOMPRESSED-SIZE inside CHECKSUM must be greater than zero. |
| full description | UNCOMPRESSED-SIZE inside CHECKSUM must be greater than zero. |
| rule name | ASAM_081 [808] |
| severity | error |
| runtime relevance | false |
| short description | UNCOMPRESSED-SIZE inside SEGMENT must be greater than zero. |
| full description | UNCOMPRESSED-SIZE inside SEGMENT must be greater than zero. |
| rule name | ASAM_082 [808] |
| severity | error |
| runtime relevance | false |
| short description | SIZE inside SIZEDEF-PHYS-SEGMENT must be greater than zero. |
| full description | SIZE inside SIZEDEF-PHYS-SEGMENT must be greater than zero. |
| rule name | ASAM_083 [817] |
| severity | error |
| runtime relevance | false |
| short description | Ranges of PHYS-SEGMENTs within the same PHYS-MEM may not overlap. |
| full description | Ranges of PHYS-SEGMENTs within the same PHYS-MEM may not overlap. |
| rule name | ASAM_084 [808] |
| severity | error |
| runtime relevance | false |
| short description | If LATEBOUND-DATAFILE in DATAFILE is false the content of DATAFILE must not use wildcards ('*', '?'). |
| full description | If LATEBOUND-DATAFILE in DATAFILE is false the content of DATAFILE must not use wildcards ('*', '?'). |
| rule name | ASAM_085 [808] |
| severity | error |
| runtime relevance | true |
| short description | KEY-DOP-REF inside TABLE must refer to a DATA-OBJECT-PROP. |
| full description | KEY-DOP-REF inside TABLE must refer to a DATA-OBJECT-PROP. |
| rule name | ASAM_086 [808] |
| severity | error |
| runtime relevance | true |
| short description | The value of each KEY must match the KEY-DOPs PHYSICAL-TYPE. |
| full description | The value of each KEY in TABLE-ROW must be interpretable as a value of the datatype specified by the PHYSICAL-TYPE/BASE-DATA-TYPE of the KEY-DOP. |
| rule name | ASAM_087 [860] |
| severity | error |
| runtime relevance | true |
| short description | TABLE-KEY must reference a TABLE if it lies in a RESPONSE. |
| full description | TABLE-KEY must reference a TABLE (not a TABLE-ROW) if it lies in a RESPONSE. This rule is also applied if the TABLE-KEY is not directly defined inside a RESPONSE, but somewhere in its deeper structure. |
| rule name | ASAM_089 [808] |
| severity | error |
| runtime relevance | true |
| short description | TABLE-KEY-REF must reference a TABLE-KEY inside the REQUEST/RESPONSE/STRUCTURE where the referencing TABLE-STRUCT lies. |
| full description | TABLE-KEY-REF must reference a TABLE-KEY inside the REQUEST/RESPONSE/STRUCTURE where the referencing TABLE-STRUCT lies. |
| rule name | ASAM_090 [808] |
| severity | error |
| runtime relevance | true |
| short description | Parameters of type TABLE-ENTRY must only occur in STRUCTUREs which are referenced by a TABLE-ROW. |
| full description | Parameters of type TABLE-ENTRY must only occur in STRUCTUREs which are referenced by a TABLE-ROW. |
| rule name | ASAM_091 [808] |
| severity | error |
| runtime relevance | false |
| short description | The shortnames of the FUNCT-CLASSes referenced via FUNCT-CLASS-REF in DIAG-COMM must be unique among each other. |
| full description | The shortnames of the FUNCT-CLASSes referenced via FUNCT-CLASS-REF in DIAG-COMM must be unique among each other. |
| rule name | ASAM_092 [808] |
| severity | error |
| runtime relevance | false |
| short description | The shortnames of all FLASH-CLASSes referenced via FLASH-CLASS-REF in SESSION-DESC must be unique among each other. |
| full description | The shortnames of all FLASH-CLASSes referenced via FLASH-CLASS-REF in SESSION-DESC must be unique among each other. |
| rule name | ASAM_093 [857] |
| severity | error |
| runtime relevance | true |
| short description | COMPU-METHODs of DOPs used in a REQUEST must be invertible. |
| full description | COMPU-METHODs of DOPs used in a REQUEST must be invertible. COMPU-METHODs of CATEGORY RAT-FUNC and SCALE-RAT-FUNC must not be used in a REQUEST. COMPU-METHODs of CATEGORY LINEAR and TAB-INTP are always invertible. COMPU-METHODs of CATEGORY LINEAR are invertible if VN1 != 0 (VN1 is the coefficient of x^1 in the numerator) or COMPU-INVERSE-VALUE is specified. COMPU-METHODs of CATEGORY SCALE-LINEAR are invertible if the functional characteristics at their intersections match and the requirements for invertibility for COMPU-METHODs of CATEGORY LINEAR are met for every single scale. A COMPU-METHOD of CATEGORY TEXTTABLE is invertible if it is deterministically invertible or COMPU-INVERSE-VALUE is specified. COMPU-METHODs of CATEGORY COMPU-CODE are invertible if COMPU-PHYS-TO-INTERNAL is defined. |
| rule name | ASAM_096 [808] |
| severity | error |
| runtime relevance | true |
| short description | PROTOCOL-SNREFS must only occur in DIAG-COMMs that do not reside in a PROTOCOL themselves. |
| full description | PROTOCOL-SNREFS must only occur in DIAG-COMMs that do not reside in a PROTOCOL themselves. |
| rule name | ASAM_097 [808] |
| severity | error |
| runtime relevance | true |
| short description | For every CASE LOWER- and UPPER-LIMIT must correspond to the SWITCH-KEY. |
| full description | For every MUX' CASE and DEFAULT-CASE the values of LOWER-LIMIT and UPPER-LIMIT must correspond to the PHYSICAL-TYPE/BASE-DATA-TYPE of the SWITCH-KEYs DOP. |
| rule name | ASAM_098 [808] |
| severity | error |
| runtime relevance | true |
| short description | LOWER-LIMIT and UPPER-LIMIT in MUX/CASE must be the same if their datatype is A_UNICODE2STRING. |
| full description | LOWER-LIMIT and UPPER-LIMIT in MUX/CASE must be the same if their datatype is A_UNICODE2STRING. |
| rule name | ASAM_099 [817] |
| severity | error |
| runtime relevance | true |
| short description | Every TABEL-ROWs KEY must be unique inside the containing TABLE. |
| full description | Every TABEL-ROWs KEY must be unique inside the containing TABLE. |
| rule name | ASAM_100 [817] |
| severity | warn |
| runtime relevance | false |
| short description | If a DIAG-COMM is referenced by a MATCHING-PARAMETER its DIAGNOSTIC-CLASS must be VARIANTIDENTIFICATION. |
| full description | If a DIAG-COMM is referenced by a MATCHING-PARAMETER its DIAGNOSTIC-CLASS must be VARIANTIDENTIFICATION. |
| rule name | ASAM_103 [808] |
| severity | error |
| runtime relevance | true |
| short description | PARENT-REFs xsi:type attribute must conform to the actually referenced DIAG-LAYERs type. |
| full description | PARENT-REFs xsi:type attribute must conform to the actually referenced DIAG-LAYERs type. E.g. if a PROTOCOL is referenced xsi:type must be a PROTOCOL-REF. |
| rule name | ASAM_104 [808] |
| severity | error |
| runtime relevance | true |
| short description | Only one DIAG-COMM may exist for each of the DIAG-CLASS-TYPEs STARTCOMM and STOPCOMM. |
| full description | Only one DIAG-COMM may exist for each of the DIAG-CLASS-TYPEs STARTCOMM and STOPCOMMs. |
| rule name | ASAM_105 [808] |
| severity | warn |
| runtime relevance | true |
| short description | Only one DIAG-COMM with SEMANTIC = DEFAULT-FAULT-READ may exist. |
| full description | Only one DIAG-COMM with SEMANTIC = DEFAULT-FAULT-READ may exist. |
| rule name | ASAM_107 [808] |
| severity | error |
| runtime relevance | true |
| short description | A SESSION may reference a DATABLOCK only once. |
| full description | A SESSION may reference a DATABLOCK only once. |
| rule name | ASAM_108 [808] |
| severity | error |
| runtime relevance | true |
| short description | MATCHING-REQUEST-PARAM and DYNAMIC must only be used in a RESPONSE. |
| full description | MATCHING-REQUEST-PARAM and DYNAMIC must only be used in a RESPONSE. |
| rule name | ASAM_110 [817] |
| severity | error |
| runtime relevance | true |
| short description | The parameter referenced by MATCHING-PARAMETER/OUT-PARAM-IF-SNREF must exist. |
| full description | If DIAG-COMM-SNREF of MATCHING-PARAMETER inside a BASE-VARIANT references a DIAG-SERVICE, then the parameter referenced by OUT-PARAM-IF-SNREF must exist in at least one of its POS-RESPONSEs or respectively among one of the OUTPUT-PARAMS if DIAG-COMM-SNREF references a SINGLE-ECU-JOB. |
| rule name | ASAM_112 [808] |
| severity | error |
| runtime relevance | true |
| short description | PHYSICAL-TYPE/BASE-DATA-TYPE must be numeric if DATA-OBJECT-PROP references a UNIT with FACTOR-SI-TO-UNIT or OFFSET-SI-TO-UNIT. |
| full description | PHYSICAL-TYPE/BASE-DATA-TYPE must be numeric if DATA-OBJECT-PROP references a UNIT with FACTOR-SI-TO-UNIT or OFFSET-SI-TO-UNIT. |
| rule name | ASAM_113 [808] |
| severity | warn |
| runtime relevance | true |
| short description | No two PROG-CODEs with same SYNTAX may reside in the same SINGLE-ECU-JOB/MULTIPLE-ECU-JOB. |
| full description | No two PROG-CODEs with same SYNTAX may reside in the same SINGLE-ECU-JOB/MULTIPLE-ECU-JOB. |
| rule name | ASAM_114 [808] |
| severity | error |
| runtime relevance | true |
| short description | If BASE-DATA-TYPE of DIAG-CODED-TYPE is numeric then xsi:type must be STANDARD-LENGTH-TYPE or PARAM-LENGTH-INFO-TYPE. |
| full description | If BASE-DATA-TYPE of DIAG-CODED-TYPE is numeric then xsi:type must be STANDARD-LENGTH-TYPE or PARAM-LENGTH-INFO-TYPE. |
| rule name | ASAM_115 [817] |
| severity | error |
| runtime relevance | true |
| short description | LENGTH-KEY-REF must reference only LENGTH-KEY parameters inside the same PDU. |
| full description | LENGTH-KEY-REF must reference only LENGTH-KEY parameters inside the same PDU. |
| rule name | ASAM_116 [808] |
| severity | error |
| runtime relevance | true |
| short description | LENGTH-KEY must reference a simple DOP with PHYSICAL-TYPE/BASE-DATA-TYPE = A_UINT32. |
| full description | LENGTH-KEY must reference a simple DOP with PHYSICAL-TYPE/BASE-DATA-TYPE = A_UINT32. |
| rule name | ASAM_117 [808] |
| severity | error |
| runtime relevance | true |
| short description | LOWER-LIMIT and UPPER-LIMIT of COMPU-SCALEs in a COMPU-METHOD of category TEXTTABLE must be identical. |
| full description | LOWER-LIMIT and UPPER-LIMIT of COMPU-SCALEs in a COMPU-METHOD of category TEXTTABLE must be identical. |
| rule name | ASAM_118 [808] |
| severity | error |
| runtime relevance | true |
| short description | CODED-VALUE and DIAG-CODED-TYPE within RESERVED must be specified either both together or none of them. |
| full description | CODED-VALUE and DIAG-CODED-TYPE within RESERVED must be specified either both together or none of them. |
| rule name | ASAM_119 [808] |
| severity | error |
| runtime relevance | true |
| short description | DYN-DEFINED-SPEC must only reference TABLEs that have unique TABLE-ROW/KEYs regarding their SEMANTIC attribute. |
| full description | DYN-DEFINED-SPEC must only reference TABLEs that have unique TABLE-ROW/KEYs regarding their SEMANTIC attribute. |
| rule name | ASAM_120 [808] |
| severity | error |
| runtime relevance | true |
| short description | No SHORT-NAME must start with GEN3D_. |
| full description | No SHORT-NAME must start with GEN3D_ because this prefix is reserved for SHORT-NAMEs that are autogenerated by the runtime system. |
| rule name | ASAM_122 [839] |
| severity | error |
| runtime relevance | true |
| short description | LOWER-LIMIT in INTERNAL-CONSTR, SCALE-CONSTR und COMPU-SCALE must be less or equal to UPPER-LIMIT. |
| full description | LOWER-LIMIT in INTERNAL-CONSTR, SCALE-CONSTR und COMPU-SCALE must be less or equal to UPPER-LIMIT. |
| rule name | ASAM_123 [839] |
| severity | error |
| runtime relevance | true |
| short description | The value of PHYSICAL-DEFAULT-VALUE must be applicable for the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP. |
| full description | The value of PHYSICAL-DEFAULT-VALUE must be interpretable as a value of the datatype specified by the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP. |
| rule name | ASAM_124 [831] |
| severity | error |
| runtime relevance | true |
| short description | The value of PHYSICAL-DEFAULT-VALUE must be in the range of the referenced DOPs INTERNAL-CONSTR. |
| full description | The value of PHYSICAL-DEFAULT-VALUE must after its reverse calculation into an internal value be in the range of the INTERNAL-CONSTR defined by the referenced DOP. |
| rule name | ASAM_125 [839] |
| severity | error |
| runtime relevance | true |
| short description | The value of PHYSICAL-CONSTANT-VALUE must be applicable for the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP. |
| full description | The value of PHYSICAL-CONSTANT-VALUE must be interpretable as a value of the datatype specified by the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP. |
| rule name | ASAM_126 [829] |
| severity | error |
| runtime relevance | true |
| short description | The value of PHYS-CONSTANT-VALUE must be in the range of the referenced DOPs INTERNAL-CONSTR. |
| full description | The value of PHYS-CONSTANT-VALUE must after its reverse calculation into an internal value be in the range of the INTERNAL-CONSTR defined by the referenced DOP. |
| rule name | ASAM_127 [808] |
| severity | error |
| runtime relevance | true |
| short description | A LONG-NAME must have at most 255 characters. |
| full description | A LONG-NAME must have at most 255 characters. |
| rule name | ASAM_128 [808] |
| severity | error |
| runtime relevance | true |
| short description | SYSPARAM in SYSTEM may only carry a valid, enumerated value. |
| full description | SYSPARAM in SYSTEM may only carry one of these values: TIMEZONE, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, TESTERID, USERID, CENTURY and WEEK. |
| rule name | ASAM_129 [808] |
| severity | error |
| runtime relevance | true |
| short description | STRUCTUREs referenced by a CASE must set IS-VISIBLE = false. |
| full description | The STRUCTURE referenced by a CASE must have its IS-VISIBLE attribute set to false. |
| rule name | ASAM_130 [809] |
| severity | error |
| runtime relevance | true |
| short description | LOWER-LIMIT in COMPU-SCALE must be specified. |
| full description | LOWER-LIMIT in COMPU-SCALE must be specified except if COMPU-CATEGORY is LINEAR. If no UPPER-LIMIT is given, then the INTERVAL-TYPE of LOWER-LIMIT must be CLOSED. |
| rule name | ASAM_131 [817] |
| severity | error |
| runtime relevance | true |
| short description | CLEAR-DYN-DEF-MESSAGE-REF, READ-DYN-DEF-MESSAGE-REF und DYN-DEF-MESSAGE-REF must point to a DIAG-SERVICE with suitable DIAGNOSTIC-CLASS. |
| full description | CLEAR-DYN-DEF-MESSAGE-REF, READ-DYN-DEF-MESSAGE-REF und DYN-DEF-MESSAGE-REF must point to a DIAG-SERVICE with suitable DIAGNOSTIC-CLASS. |
| rule name | ASAM_133 [817] |
| severity | error |
| runtime relevance | true |
| short description | Parameters referenced by a COMM-RELATION shall not be contained within a FIELD. |
| full description | Parameters referenced by a DIAG-VARIABLE/COMM-RELATION shall not be indirectly contained within a FIELD. |
| rule name | ASAM_134 [817] |
| severity | error |
| runtime relevance | true |
| short description | The parameter referenced by MATCHING-PARAMETER, MATCHING-COMPONENT and IDENT-DESC shall not be contained within a FIELD. |
| full description | The parameter referenced by OUT-PARAM-IF-SNREF in MATCHING-PARAMTER, MATCHING-COMPONENT and IDENT-DESC shall not be (indirectly) contained within a FIELD. |
| rule name | ASAM_135 [808] |
| severity | error |
| runtime relevance | false |
| short description | It is prohibited to define elements with the same shortname like an object of the same type that has been excluded from inheritance by a parent layer. |
| full description | DIAG-COMMs and DIAG-VARIABLEs can be excluded from inheritance via NOT-INHERITED-DIAG-COMM or NOT-INHERITED-VARIABLE. If this is used to completly eliminate an element in a more specialized layer it must not be redefined. |
| rule name | ASAM_136 [817] |
| severity | error |
| runtime relevance | false |
| short description | DIAG-COMMs that are marked MANDATORY must not be excluded from inheritance. |
| full description | If a DiagLayer contains a mandatory (@IS-MANDATORY="true") DIAG-COMM it must not be excluded from inheritance by a more specialized layer. Exception: If a DiagLayer inherits from several other DiagLayers containing mandatory DIAG-COMMs with the same shortname, then all except one of these DIAG-COMMs must be excluded from inheritance, so that it is clear which inheritance path is to be chosen. |
| rule name | ASAM_137 [855] |
| severity | error |
| runtime relevance | false |
| short description | A layer must not inherit two objects of the same type and with the same shortname from several layers of the same specialisation level. |
| full description | A layer must not inherit two objects of the same type and with the same shortname from several layers of the same specialisation level. |
| rule name | ASAM_138 [808] |
| severity | error |
| runtime relevance | false |
| short description | Multiple COMPU-SCALEs of the same TEXTTABLE, that map to the same physical value, must have identical COMPU-INVERSE-VALUEs. |
| full description | If multiple COMPU-SCALEs of a COMPU-METHOD with COMPU-CATEGORY 'TEXTTABLE' map to the same physical value (COMPU-CONST/VT), then these COMPU-SCALEs must have identical COMPU-INVERSE-VALUEs. |
| rule name | ASAM_139 [808] |
| severity | error |
| runtime relevance | false |
| short description | A LOGICAL-LINK can reference a BASE-VARIANT and/or a PROTOCOL or a FUNCTIONAL-GROUP and a PROTOCOL. |
| full description | A LOGICAL-LINK can either reference a BASE-VARIANT alone or a PROTOCOL alone or a PROTOCOL and a BASE-VARIANT or a PROTOCOL and a FUNCTIONAL-GROUP. All other combinations are invalid. |
| rule name | ASAM_140 [844] |
| severity | error |
| runtime relevance | false |
| short description | COMPU-SCALEs of a DOP must cover the valid ranges of the INTERNAL-CONSTR. |
| full description | The COMPU-SCALEs of a DATA-OBJECT-PROP must cover at least the valid ranges (SCALE-CONSTR[@VALIDITY)="VALID") of the corresponding INTERNAL-CONSTR. |
| rule name | ASAM_142 [841] |
| severity | error |
| runtime relevance | false |
| short description | DIAG-SERVICEs with ADDRESSING="FUNCTIONAL" must not be defined in a BASE-VARIANT or an ECU-VARIANT. |
| full description | DIAG-SERVICEs with ADDRESSING="FUNCTIONAL" must not be defined in a BASE-VARIANT or an ECU-VARIANT. |
| rule name | ASAM_143 [808] |
| severity | error |
| runtime relevance | false |
| short description | The SESSION referenced by SESSION-DESC must exist. |
| full description | The SESSION referenced by ECU-MEM-CONNECTOR//SESSION-DESC via SESSION-SNREF must exist in the ECU-MEM which is referenced by ECU-MEM-CONNECTOR/ECU-MEM-REF. |
| rule name | ASAM_144 [817] |
| severity | error |
| runtime relevance | false |
| short description | The DIAG-COMM referenced by SESSION-DESC must exist. |
| full description | The DIAG-COMM referenced by SESSION-DESC in ECU-MEM-CONNECTOR must exist in all ECU-VARIANTs and BASE-VARIANTs that are referenced by the ECU-MEM-CONNECTOR. |
| rule name | ASAM_145 [817] |
| severity | error |
| runtime relevance | true |
| short description | BIT-LENGTH at DIAG-CODED-TYPE must match the bit-length of the float data type. |
| full description | In case if DIAG-CODED-TYPE is A_FLOAT32 the BIT-LENGTH must be equal to 32. In case of A_FLOAT64, the BIT-LENGTH must be equal to 64. That means that the DIAG-CODED-TYPE must be of type STANDARD-LENGTH-TYPE if BASE-DATA-TYPE is set to a float data type. |
| rule name | ASAM_146 [817] |
| severity | error |
| runtime relevance | true |
| short description | The wildcards '*' and '?' can only be used in CODE-FILE if attribute LATEBOUND-CODE-FILE equals 'true'. |
| full description | The wildcards '*' and '?' can only be used in CODE-FILE if attribute LATEBOUND-CODE-FILE equals 'true'. |
| rule name | ASAM_149 [808] |
| severity | error |
| runtime relevance | true |
| short description | IDENT-IF-SNREF must reference to a IDENT-IF that exists within the namespace of the ECU-MEM referenced by the ECU-MEM-CONNECTOR the IDENT-DESC is contained in. |
| full description | IDENT-IF-SNREF must reference to a IDENT-IF that exists within the namespace of the ECU-MEM referenced by the ECU-MEM-CONNECTOR the IDENT-DESC is contained in. |
| rule name | ASAM_151 [808] |
| severity | error |
| runtime relevance | true |
| short description | Each range of COMPU-SCALE must not overlap any other range. |
| full description |
| rule name | ASAM_154 [846] |
| severity | error |
| runtime relevance | true |
| short description | PHYSICAL-DEFAULT-VALUE or PHYS-CONSTANT-VALUE must match with an entry of the corresponding texttable. |
| full description | In case of DOP/COMPUMETHOD/TEXTTABLE the values of PHYSICAL-DEFAULT-VALUE or PHYS-CONSTANT-VALUE must match case-sensitively with an entry of the corresponding texttable. |
| rule name | ASAM_156 [854] |
| severity | warn |
| runtime relevance | true |
| short description | BYTE-SIZE must not be less than the total size of the included parameters. If the STRUCTURE has any dynamic components the BYTE-SIZE must not be specified. |
| full description | BYTE-SIZE must not be less than the total size of the included parameters. If the STRUCTURE has any dynamic components (e.g. MUX or any FIELD with dynamic length) the BYTE-SIZE must not be specified. |
| rule name | ASAM_157 [808] |
| severity | error |
| runtime relevance | true |
| short description | DOCREF and DOCTYPE must be specified either jointly or not at all. |
| full description | DOCREF and DOCTYPE must be specified either jointly or not at all. |
| rule name | VAX_001 [1.5] |
| severity | warn |
| runtime relevance | false |
| short description | Check of shortnames |
| full description | Check of shortnames |
| rule name | VAX_002 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | Check of longnames |
| full description | Check of longnames |
| rule name | VAX_003 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | Check if IDs are unique and correct coded. |
| full description | Check if IDs are unique and correct coded. |
| rule name | VAX_004 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | The protocol layer must contain the DOP "DOP_NRC" |
| full description | The protocol layer must contain the DOP "DOP_NRC" |
| rule name | VAX_005 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | Usage of COMPU-SCALEs and COMPU-DEFAULT-VALUE at COMPU-METHODs except for IDENTICAL and COMPUCODE |
| full description | Usage of COMPU-SCALEs and COMPU-DEFAULT-VALUE at COMPU-METHODs except for IDENTICAL and COMPUCODE: 1). ERROR: COMPU-METHOD must contain at least one COMPU-SCALE, 2). ERROR: In case of STRING and BYTEFIELD the COMPU-DEFAULT-VALUE must be defined, 3). ERROR: The value range must be calculatable (not calculatable e.g. in case of FLOAT32 with BitLength != 32), 4). WARN: COMPU-DEFAULT-VALUE is redundant, if COMPU-SCALEs cover the whole internal data range |
| rule name | VAX_006 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | Check of the existance of the layer referenced via PARENT-REF or IMPORT-REF |
| full description | Check of the existance of the layer referenced via PARENT-REF or IMPORT-REF |
| rule name | VAX_007 [1.5] |
| severity | error |
| runtime relevance | false |
| short description | Check if file name complies with Shortname + Version (3-digit number) |
| full description | Check if file name complies with Shortname + Version (3-digit number) |
| rule name | VAX_008 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | The file referenced by CODE-FILE must exist in the PDX archive. |
| full description | The file referenced by CODE-FILE must exist in the PDX archive. |
| rule name | VAX_009 [1.5] |
| severity | error |
| runtime relevance | false |
| short description | Check whether COMPARAM-SPEC and PROTOCOL exist within the pdx package |
| full description | Check whether COMPARAM-SPEC and PROTOCOL exist within the pdx package |
| rule name | VAX_010 [1.5] |
| severity | error |
| runtime relevance | false |
| short description | For every DIAG-LAYER ADMIN-DATA, LONG-NAME and DESC must be set. For every ODX-CATEGORY except DIAG-LAYER-CONTAINER ADMIN-DATA and DESC must be set. For every ODX-CATEGORY LONG-NAME must be set. |
| full description | For every DIAG-LAYER ADMIN-DATA, LONG-NAME and DESC must be set. For every ODX-CATEGORY except DIAG-LAYER-CONTAINER ADMIN-DATA and DESC must be set. For every ODX-CATEGORY LONG-NAME must be set. |
| rule name | VAX_011 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | Response codes in the DOP "DOP_NRC" must contain only entries froms the predefined list (defined in VAX_NRCs.xml). |
| full description | Response codes in the DOP "DOP_NRC" must contain only entries froms the predefined list (defined in VAX_NRCs.xml). |
| rule name | VAX_012 [1.4] |
| severity | error |
| runtime relevance | false |
| short description | Checking of SDGs at DTC |
| full description | Checking of SDGs at DTC |
| rule name | VAX_013 [1.3] |
| severity | error |
| runtime relevance | false |
| short description | Every ADMIN-DATA element must have at least one DOC-REVISION. |
| full description | Every ADMIN-DATA element must have at least one DOC-REVISION. |
| rule name | VAX_014 [1.6] |
| severity | warn |
| runtime relevance | false |
| short description | TI attributes should only contain values from a predefined list. |
| full description | TI attributes should only contain values from a predefined list. |
| rule name | VAX_015 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | Each DIAG-COMM (service or job) must be assigned to at least one session |
| full description | Each DIAG-COMM (service or job) must be assigned to at least one session |
| rule name | VAX_016 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | Check of the existance of the COMPARAM-SPEC referenced by a PROTOCOL |
| full description | Check of the existance of the COMPARAM-SPEC referenced by a PROTOCOL |
| rule name | VAX_017 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | DISPLAY-TROUBLE-CODE must not be empty. |
| full description | DISPLAY-TROUBLE-CODE must not be empty. |
| rule name | VAX_018 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | Every DTC in ECU- and BASE-VARIANT must have a LEVEL. If defined the LEVEL must have a value between 1 and 9. |
| full description | Every DTC in ECU- and BASE-VARIANT must have a LEVEL. If defined the LEVEL must have a value between 1 and 9. |
| rule name | VAX_019 [1.2] |
| severity | error |
| runtime relevance | true |
| short description | V and VT elements must not be empty. |
| full description | V and VT elements must not be empty. |
| rule name | VAX_020 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | AUDIENCE/IS-AFTERMARKET and AUDIENCE/IS-AFTERSALES of an OBD-Service must not be false. |
| full description | AUDIENCE/IS-AFTERMARKET and AUDIENCE/IS-AFTERSALES of an OBD-Service must not be false. |
| rule name | VAX_021 [1.2] |
| severity | error |
| runtime relevance | true |
| short description | Each DIAG-LAYER-CONTAINER must contain exactly one DIAG-LAYER |
| full description | Each DIAG-LAYER-CONTAINER must contain exactly one DIAG-LAYER |
| rule name | VAX_022 [1.2] |
| severity | error |
| runtime relevance | true |
| short description | ECU-SHARED-DATA must not be referenced by PARENT-REF |
| full description | ECU-SHARED-DATA must not be referenced by PARENT-REF |
| rule name | VAX_023 [1.2] |
| severity | error |
| runtime relevance | true |
| short description | Elimination of services and variables is only allowed for BASE-VARIANTs and ECU-VARIANTs |
| full description | Elimination of services and variables is only allowed for BASE-VARIANTs and ECU-VARIANTs |
| rule name | VAX_024 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | Overwriting of objects is only allowed for BASE-VARIANTs and ECU-VARIANTs |
| full description | Overwriting of objects is only allowed for BASE-VARIANTs and ECU-VARIANTs |
| rule name | VAX_025 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT is not allowed to use objects from another ECU-VARIANT |
| full description | An ECU-VARIANT is not allowed to use objects from another ECU-VARIANT |
| rule name | VAX_026 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT-PATTERN must be unique for each ECU-VARIANT |
| full description | An ECU-VARIANT-PATTERN must be unique for each ECU-VARIANT |
| rule name | VAX_027 [1.6] |
| severity | error |
| runtime relevance | false |
| short description | SHORT-NAME is generated from the LONG-NAME using guidelines |
| full description | SHORT-NAME is generated from the LONG-NAME using guidelines |
| rule name | VAX_028 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | Check if each DIAG-COMM is assigned to at least one functional class |
| full description | Check if each DIAG-COMM is assigned to at least one functional class |
| rule name | VAX_029 [1.5] |
| severity | error |
| runtime relevance | false |
| short description | Shortname of DTCs must comply with the following pattern: "DTC_" + TROUBLE-CODE |
| full description | Shortname of DTCs must comply with the following pattern: "DTC_" + TROUBLE-CODE |
| rule name | VAX_030 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | If the KEY-DOP owns a Compu-Method of type TEXTTABLE, the VTs of the Compu-Scales must be unique and all KEYs must be defined in the TEXTTABLE. |
| full description | If the KEY-DOP owns a Compu-Method of type TEXTTABLE, the VTs of the Compu-Scales must be unique and all KEYs must be defined in the TEXTTABLE. |
| rule name | VAX_031 [1.4] |
| severity | error |
| runtime relevance | true |
| short description | Checks if the V elements are of the correct type |
| full description | Checks if the V elements of COMPU-METHODs are of the correct type. E.g. 0.01 is not allowed if the calculation type is INT. |
| rule name | VAX_032 [1.3] |
| severity | error |
| runtime relevance | true |
| short description | In case of TEXTTABLE as KEY-DOP at each TABLE-ROW the KEY must be equal to the LONG-NAME |
| full description | In case of TEXTTABLE as KEY-DOP at each TABLE-ROW the value of KEY must be equal to the value of LONG-NAME |
| rule name | VAX_033 [1.1] |
| severity | error |
| runtime relevance | true |
| short description | At TABLEs with KEY-DOP of type TEXTTABLE for each TABLE-ROW/KEY exactly one COMPU-SCALE with appropriate text must exist and vice versa |
| full description | At TABLEs with KEY-DOP of type TEXTTABLE for each TABLE-ROW/KEY exactly one COMPU-SCALE with appropriate text (VT) must exist and vice versa, i.e. for each COMPU-SCALE of the KEY-DOP exactly one TABLE-ROW must exist with the same value of KEY |
| rule name | VAX_101 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | Inside a DATA-OBJECT-PROP of CATEGORY TEXTTABLE each TI must not be assigned to more than one text. |
| full description | Inside a DATA-OBJECT-PROP of CATEGORY TEXTTABLE each TI must not be assigned to more than one text. |
| rule name | VAX_102 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | A COMPU-METHOD of CATEGORY LINEAR may only define a single COMPU-SCALE which must have a define a COMPU-DENOMINATOR. |
| full description | A COMPU-METHOD of CATEGORY LINEAR may only define a single COMPU-SCALE which must have a define a COMPU-DENOMINATOR. |
| rule name | VAX_103 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT isn't allowed to import another ECU-VARIANT. |
| full description | An ECU-VARIANT isn't allowed to import another ECU-VARIANT. |
| rule name | VAX_104 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT isn't allowed to reference another ECU-VARIANT. |
| full description | An ECU-VARIANT isn't allowed to reference another ECU-VARIANT. |
| rule name | VAX_105 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT must contain an ECU-VARIANT-PATTERN. |
| full description | An ECU-VARIANT must contain an ECU-VARIANT-PATTERN. |
| rule name | VAX_106 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT must contain ECU-VARIANT-PATTERNs, which contain one different EXPECTED-VALUE. |
| full description | An ECU-VARIANT must contain ECU-VARIANT-PATTERNs, which contain one different EXPECTED-VALUE. |
| rule name | VAX_107 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | An ECU-VARIANT must contain ECU-VARIANT-PATTERNs, which is unique for the whole project. |
| full description | An ECU-VARIANT must contain ECU-VARIANT-PATTERNs, which is unique for the whole project. |
| rule name | VAX_108 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | An ECU-VARIANT must contain a ECU-VARIANT-PATTERN for ASAMODXFileIdentifier and ASAMODXFileVersion. |
| full description | An ECU-VARIANT must contain a ECU-VARIANT-PATTERN for ASAMODXFileIdentifier and ASAMODXFileVersion. |
| rule name | VAX_109 [1.0] |
| severity | warn |
| runtime relevance | true |
| short description | Every REQUEST must contain a PARAM with SHORT-NAME Param_RequeServiId. |
| full description | Every REQUEST must contain a PARAM with SHORT-NAME Param_RequeServiId. |
| rule name | VAX_110 [1.0] |
| severity | warn |
| runtime relevance | true |
| short description | Every RESPONSE must contain a PARAM with SHORT-NAME Param_RespoServiId. |
| full description | Every RESPONSE must contain a PARAM with SHORT-NAME Param_RespoServiId. |
| rule name | VAX_111 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | A PARAM with SHORT-NAME Param_RequeServiId, Param_RespoServiId oder Param_NegatRespoServiIdent must contain SEMANTIC SERVICE-ID. |
| full description | A PARAM with SHORT-NAME Param_RequeServiId, Param_RespoServiId oder Param_NegatRespoServiIdent must contain SEMANTIC SERVICE-ID. |
| rule name | VAX_112 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | A PARAM with SEMANTIC SERVICE-ID must be of type CODED-CONST. |
| full description | A PARAM with SEMANTIC SERVICE-ID must be of type CODED-CONST. |
| rule name | VAX_113 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | A PARAM with SEMANTIC SERVICE-ID must be of type CODED-CONST. Additionally a DIAG-CODED-TYPE element with type STANDARD-LENGTH-TYPE and BIT-LENGTH = 8 must exist |
| full description | A PARAM with SEMANTIC SERVICE-ID must be of type CODED-CONST. Additionally a DIAG-CODED-TYPE element with type STANDARD-LENGTH-TYPE and BIT-LENGTH = 8 must exist |
| rule name | VAX_114 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | DATA-OBJECT-PROP and DTC-DOP elements, which contain the PHYSICAL-TYPE FLOAT* must contain a PRECISION entry, also. |
| full description | DATA-OBJECT-PROP and DTC-DOP elements, which contain the PHYSICAL-TYPE FLOAT* must contain a PRECISION entry, also. |
| rule name | VAX_115 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The DIAG-COMM DiagnServi_ReadDTCInforReporDTCExtenDataRecorByDTCNumbe exists and contains all needed sub elements. |
| full description | The DIAG-COMM DiagnServi_ReadDTCInforReporDTCExtenDataRecorByDTCNumbe exists and contains all needed sub elements. |
| rule name | VAX_116 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Services needed in the flash sequence must be available.All Services must be defined in PROTOCOL or FUNCTIONAL-GROUP, except DiagnServi_WriteDataByIdentECUIdent.For these Services no overwriting is allowed. |
| full description | Services needed in the flash sequence must be available.All Services must be defined in PROTOCOL or FUNCTIONAL-GROUP, except DiagnServi_WriteDataByIdentECUIdent.For these Services no overwriting is allowed. |
| rule name | VAX_117 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | If a MATCHING-PARAMETER is used to match against the ASAM-FileIdentifier, the EXPECTED-VALUE have to be equal to the SHORT-NAME of the ECU-VARIANT, except the last 4 characters. |
| full description | If a MATCHING-PARAMETER is used to match against the ASAM-FileIdentifier, the EXPECTED-VALUE have to be equal to the SHORT-NAME of the ECU-VARIANT, except the last 4 characters. |
| rule name | VAX_118 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | If a MATCHING-PARAMETER is used to match against the ASAM-FileVersion, the EXPECTED-VALUE have to be equal to the last 3 SHORT-NAME characters of the ECU-VARIANT. |
| full description | If a MATCHING-PARAMETER is used to match against the ASAM-FileVersion, the EXPECTED-VALUE have to be equal to the last 3 SHORT-NAME characters of the ECU-VARIANT. |
| rule name | VAX_201 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Filename must comply to one of the following patterns: <VWSparePartNumber>_<VWApplicationSoftwareVersionNumber>.odx or<VWSparePartNumber>_<VWApplicationSoftwareVersionNumber>_<FDSInfo>.odx. |
| full description | Filename of a FLASH-Container must contain the präfix FL, the VWSparePartNumber (9 to 11 chars) and the VWApplicationSoftwareVersionNumber (4 chars). The character _ acts as a seperator between these parts.FDSInfo could be appended and the fileextension has to be .odx. |
| rule name | VAX_202 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | ADMIN-DATA muss exists and TEAM-MEMBER-REF has to reference a TEAM-MEMBER described at he same file. |
| full description | Every FLASH-Container must contain the Element ADMIN-DATA and all references to COMPANY-DATA elements have to be resolved with the help of elements defined in the same file. |
| rule name | VAX_203 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | Every FLASH-Container contains only one COMPANY-DATA element. |
| full description | Every FLASH-Container contains only one COMPANY-DATA element. This element holds the information about the company which has created the FLASH container. |
| rule name | VAX_204 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | An SDG element for FDS-Project-ID and one for ECU-MEM-SPEC-VERSION must exist in the COMPANY-SPECIFIC-INFO eLement. |
| full description | An SDG element for FDS-Project-ID and one for ECU-MEM-SPEC-VERSION must exist in the COMPANY-SPECIFIC-INFO element. |
| rule name | VAX_205 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The FLASH container must contain an ECU-MEMS element. |
| full description | The FLASH container must contain an ECU-MEMS element. |
| rule name | VAX_206 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The FLASH container must contain an ECU-MEM-CONNECTORS element. |
| full description | The FLASH container must contain an ECU-MEM-CONNECTORS element. |
| rule name | VAX_207 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The ECU-MEMS element must contain only one ECU-MEM element. |
| full description | The ECU-MEMS element must contain only one ECU-MEM element. |
| rule name | VAX_208 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The ECU-MEM-CONNECTORS element must contain only one ECU-MEM-CONNECTOR element. |
| full description | The ECU-MEM-CONNECTORS element must contain only one ECU-MEM-CONNECTOR element. |
| rule name | VAX_209 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The SESSIONS element must contain only one SESSION element. |
| full description | The SESSIONS element must contain only one SESSION element. |
| rule name | VAX_210 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | All DATABLOCK elements have to be referenced within the SESSIONS element. |
| full description | All DATABLOCK elements of a MEM element have to be referenced within the SESSIONS element. |
| rule name | VAX_211 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | All DATABLOCK-REF elements have to reference a DATABLOCK within the same ECU-MEM element. |
| full description | All DATABLOCK-REF elements have to reference a DATABLOCK within the same ECU-MEM element. |
| rule name | VAX_212 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The only attribute of all DATABLOCK-REF elements has to be the ID-REF. |
| full description | The only attribute of all DATABLOCK-REF elements has to be the ID-REF. The attributes DOC-TYPE and DOC-REF aren't allowed. |
| rule name | VAX_213 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | All FLASHDATA elements must be referenced by an DATABLOCK within a SESSION. |
| full description | FLASHDATA have to be referenced, within a SESSION, by a DATABLOCK with the help of FLASHDATA-REF. |
| rule name | VAX_214 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | All FLASHDATA-REF elements must reference an FLASHDATA element within a SESSION. |
| full description | FLASHDATA-REF have to reference an FLASHDATA element within a SESSION. |
| rule name | VAX_215 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The only attribute of all FLASHDATA-REF elements has to be the ID-REF. |
| full description | The only attribute of all FLASHDATA-REF elements has to be the ID-REF. The attributes DOC-TYPE and DOC-REF aren't allowed. |
| rule name | VAX_216 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | DATABLOCK elements of type DATA has to be referenced only one time. |
| full description | DATABLOCK elements of type DATA has to be referenced only one time. |
| rule name | VAX_217 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The SESSION Element must not contain a CHECKSUMS element. |
| full description | The SESSION Element must not contain a CHECKSUMS element. |
| rule name | VAX_218 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The SESSION element must contain an EXPECTED-IDENTS element. |
| full description | The SESSION element must contain an EXPECTED-IDENTS element. |
| rule name | VAX_219 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The attribute TYPE of one IDENT-VALUE element must contain an datatype which is compatible to the datatype received from the referenced PARAM. |
| full description | The attribute TYPE of one IDENT-VALUE element of every EXPECTED-IDENT must contain an datatype which is compatible to the datatype received from the referenced PARAM (OUT-PARAM-IF-SNREF). |
| rule name | VAX_220 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The SESSION element must contain an SECURITYS element. |
| full description | The SESSION element must contain an SECURITYS element. |
| rule name | VAX_221 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The SECURITY element must contain an SECURITY-METHOD element. |
| full description | The SECURITY element must contain an SECURITY-METHOD element. |
| rule name | VAX_222 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The attribute TYPE of the SECURITY-METHOD must contain the required VALUE A_ASCIISTRING. |
| full description | The attribute TYPE of the SECURITY-METHOD must contain the required VALUE A_ASCIISTRING. |
| rule name | VAX_223 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Only one SECURITY-METHOD within the SECURITYS Element has to contain the SA2 entry. |
| full description | Only one SECURITY-METHOD within the SECURITYS Element has to contain the SA2 entry. |
| rule name | VAX_224 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY containing a SECURITY-METHOD SA2, the TYPE of FW-SIGNATURE has to be A_BYTEFIELD. |
| full description | If a SECURITY containing a SECURITY-METHOD SA2, the TYPE of FW-SIGNATURE has to be A_BYTEFIELD. |
| rule name | VAX_225 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY containing a SECURITY-METHOD SA2, the element FW-SIGNATURE has to be defined. |
| full description | If a SECURITY containing a SECURITY-METHOD SA2, the element FW-SIGNATURE has to be defined. |
| rule name | VAX_226 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY containing a SECURITY-METHOD SA2, the element FW-CHECKSUM has to be undefined. |
| full description | If a SECURITY containing a SECURITY-METHOD SA2, the element FW-CHECKSUM has to be undefined. |
| rule name | VAX_227 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY is containing a SECURITY-METHOD = CRC, the TYPE of element FW-SIGNATURE has to be A_UINT32. |
| full description | If a SECURITY is containing a SECURITY-METHOD = CRC, the TYPE of element FW-SIGNATURE has to be A_UINT32. |
| rule name | VAX_228 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY is containing a SECURITY-METHOD != SA2, the TYPE of element FW-CHECKSUM has to be A_BYTEFIELD. |
| full description | If a SECURITY is containing a SECURITY-METHOD != SA2, the TYPE of element FW-CHECKSUM has to be A_BYTEFIELD. |
| rule name | VAX_229 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY is containing a SECURITY-METHOD != SA2, the element VALIDITY-FOR has to be defined. |
| full description | If a SECURITY is containing a SECURITY-METHOD != SA2, the element VALIDITY-FOR has to be defined. |
| rule name | VAX_230 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY is containing a SECURITY-METHOD != SA2, the element VALIDITY-FOR (with type A_ASCIISTRING) has to be defined. |
| full description | If a SECURITY is containing a SECURITY-METHOD != SA2, the element VALIDITY-FOR (with type A_ASCIISTRING) has to be defined. |
| rule name | VAX_231 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY is containing a SECURITY-METHOD != SA2, the element VALIDITY-FOR (containing the shortname of a DATABLOCK) has to be defined. |
| full description | If a SECURITY is containing a SECURITY-METHOD != SA2, the element VALIDITY-FOR (containing the shortname of a DATABLOCK) has to be defined. |
| rule name | VAX_232 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | Within a SESSION a SDGS Element has to be undefined. |
| full description | Within a SESSION a SDGS Element has to be undefined. |
| rule name | VAX_233 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | Within a DATABLOCK a FILTERS Element has to be undefined. |
| full description | Within a DATABLOCK a FILTERS Element has to be undefined. |
| rule name | VAX_234 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a DATABLOCK a TARGET-ADDR-OFFSET Element has to be undefined. |
| full description | Within a DATABLOCK a TARGET-ADDR-OFFSET Element has to be undefined. |
| rule name | VAX_235 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a DATABLOCK a SECURITYS Element has to be undefined. |
| full description | Within a DATABLOCK a SECURITYS Element has to be undefined. |
| rule name | VAX_236 [1.0] |
| severity | warn |
| runtime relevance | false |
| short description | Within a DATABLOCK a SDGS Element has to be undefined. |
| full description | Within a DATABLOCK a SDGS Element has to be undefined. |
| rule name | VAX_237 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a SEGMENTS only one SEGMENT Element has to be defined. |
| full description | Within a SEGMENTS only one SEGMENT Element has to be defined. |
| rule name | VAX_238 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a SEGMENT a UNCOMPRESSED-SIZE Element has to be defined. |
| full description | Within a SEGMENT a UNCOMPRESSED-SIZE Element has to be defined. |
| rule name | VAX_239 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | Within a SEGMENT a SOURCE-END-ADDRESS Element has to be undefined. |
| full description | Within a SEGMENT a SOURCE-END-ADDRESS Element has to be undefined. |
| rule name | VAX_240 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a SEGMENT a COMPRESSED-SIZE Element will be defined, if the referenced FLASHDATA contains an ENCRYPT-COMPRESS-METHOD != 0X. |
| full description | Within a SEGMENT a COMPRESSED-SIZE Element will be defined, if the referenced FLASHDATA contains an ENCRYPT-COMPRESS-METHOD != 0X. |
| rule name | VAX_241 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a FLASHDATA a COMPRESSED-SIZE Element must be defined. |
| full description | Within a FLASHDATA a COMPRESSED-SIZE Element must be defined. |
| rule name | VAX_242 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a ENCRYPT-COMPRESS-METHOD the TYPE attribute must contain A_BYTEFIELD. |
| full description | Within a ENCRYPT-COMPRESS-METHOD the TYPE attribute must contain A_BYTEFIELD. |
| rule name | VAX_243 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a ENCRYPT-COMPRESS-METHOD a hexadecimal value with length 1 byte must be available. |
| full description | Within a ENCRYPT-COMPRESS-METHOD a hexadecimal value with length 1 byte must be available. |
| rule name | VAX_244 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a DATAFORMAT the SELECTION attribute must contain the value BINARY. |
| full description | Within a DATAFORMAT the SELECTION attribute must contain the value BINARY. |
| rule name | VAX_245 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a DATA element the amount of characters must be even.. |
| full description | Within a DATA element the amount of characters must be even.. |
| rule name | VAX_246 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a DATA element the amount of characters must be even to the value at COMPRESSED-SIZE or UNCOMPRESSED-SIZE multiplied with 2. |
| full description | Within a DATA element the amount of characters must be even to the value at COMPRESSED-SIZE or UNCOMPRESSED-SIZE multiplied with 2. |
| rule name | VAX_247 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within an EXTERN-FLASHDATA element the DATAFILE must contain the value false at the attribute LATEBOUNDFILE. |
| full description | Within an EXTERN-FLASHDATA element the DATAFILE must contain the value false at the attribute LATEBOUNDFILE. |
| rule name | VAX_248 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within an EXTERN-FLASHDATA element the DATAFILE must contain the path to an existing file. |
| full description | Within an EXTERN-FLASHDATA element the DATAFILE must contain the path to an existing file. |
| rule name | VAX_249 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | Within a DATAFILE element a file is specified. The file size must be even to the value at COMPRESSED-SIZE or UNCOMPRESSED-SIZE. |
| full description | Within a DATAFILE element a file is specified. The file size must be even to the value at COMPRESSED-SIZE or UNCOMPRESSED-SIZE. |
| rule name | VAX_250 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEMS element must not contain a PHYS-MEM element. |
| full description | The ECU-MEMS element must not contain a PHYS-MEM element. |
| rule name | VAX_251 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEM-CONNECTOR element must not contain a FLASH-CLASSS element. |
| full description | The ECU-MEM-CONNECTOR element must not contain a FLASH-CLASSS element. |
| rule name | VAX_252 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEM-REF of ECU-MEM-CONNECTOR must reference an ECU-MEM specified in the same file. |
| full description | The ECU-MEM-REF of ECU-MEM-CONNECTOR must reference an ECU-MEM specified in the same file. |
| rule name | VAX_253 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEM-REF of ECU-MEM-CONNECTOR must not contain a DOCREF or DOCTYPE. |
| full description | The ECU-MEM-REF of ECU-MEM-CONNECTOR must not contain a DOCREF or DOCTYPE. |
| rule name | VAX_254 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEM-CONNECTOR must contain the SESSION-DESCS Element. |
| full description | The ECU-MEM-CONNECTOR must contain the SESSION-DESCS Element. |
| rule name | VAX_255 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The SESSION-DESCS element must contain only one SESSION-SESC element. |
| full description | The SESSION-DESCS element must contain only one SESSION-SESC element. |
| rule name | VAX_256 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The SESSION-DESC element must not contain a PARTNUMBER. |
| full description | The SESSION-DESC element must not contain a PARTNUMBER. |
| rule name | VAX_257 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The SESSION-DESC element must not contain a PRIORITY. |
| full description | The SESSION-DESC element must not contain a PRIORITY. |
| rule name | VAX_258 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The Shortname of DIAG-COMM-SNREF must be part of the file VAX_names.xml. |
| full description | The Shortname of DIAG-COMM-SNREF must be part of the file VAX_names.xml. |
| rule name | VAX_259 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The SESSION-DESC element must not contain a FLASH-CLASS-REFS element. |
| full description | The SESSION-DESC element must not contain a FLASH-CLASS-REFS element. |
| rule name | VAX_260 [1.0] |
| severity | error |
| runtime relevance | false |
| short description | The SESSION-DESC element must not contain a SDGS element. |
| full description | The SESSION-DESC element must not contain a SDGS element. |
| rule name | VAX_261 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEM-CONNECTOR element must contain the IDENT-DESCS element. |
| full description | The ECU-MEM-CONNECTOR element must contain the IDENT-DESCS element. |
| rule name | VAX_262 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The IDENT-DESC elements must reference an EXPECTED-IDENT. |
| full description | The IDENT-DESC elements must reference an EXPECTED-IDENT. |
| rule name | VAX_263 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The ECU-MEM-CONNECTOR element must contain a LAYER-REFS element. |
| full description | The ECU-MEM-CONNECTOR element must contain a LAYER-REFS element. |
| rule name | VAX_264 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The LAYER-REFS element must contain a LAYER-REF element. |
| full description | The LAYER-REFS element must contain a LAYER-REF element. |
| rule name | VAX_265 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The LAYER-REF element must contain a DOCTYPE element. |
| full description | The LAYER-REF element must contain a DOCTYPE element. |
| rule name | VAX_266 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The LAYER-REF element must contain a DOCTYPE element with entry LAYER. |
| full description | The LAYER-REF element must contain a DOCTYPE element with entry LAYER. |
| rule name | VAX_267 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The LAYER-REF element must contain a DOCREF element. |
| full description | The LAYER-REF element must contain a DOCREF element. |
| rule name | VAX_268 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | The LAYER-REF element must contain a DOCREF element with a reference to an ECU-VARIANT. |
| full description | The LAYER-REF element must contain a DOCREF element with a reference to an ECU-VARIANT. |
| rule name | VAX_269 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY containing a SECURITY-METHOD != SA2, the element FW-SIGNATURE has to be defined. |
| full description | If a SECURITY containing a SECURITY-METHOD != SA2, the element FW-SIGNATURE has to be defined. |
| rule name | VAX_270 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY containing a SECURITY-METHOD = SIG, the element FW-SIGNATURE with type A_BYTEFIELD has to be defined. |
| full description | If a SECURITY containing a SECURITY-METHOD = SIG, the element FW-SIGNATURE with type A_BYTEFIELD has to be defined. |
| rule name | VAX_271 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY containing the SECURITY-METHOD = CRC, the element FW-CHECKSUM has to be defined. |
| full description | If a SECURITY containing the SECURITY-METHOD = CRC, the element FW-CHECKSUM has to be defined. |
| rule name | VAX_272 [1.0] |
| severity | error |
| runtime relevance | true |
| short description | If a SECURITY element contains SECURITY-METHOD = SA2, the FW-SIGNATURE element must contain a plausible SA2 algorithm. |
| full description | If a SECURITY element contains SECURITY-METHOD = SA2, the FW-SIGNATURE element must contain a plausible SA2 algorithm. |