Data Types & COMPU-METHODs - ODX & Diagnostic Data

Data Object Props (DOPs)

DOP: The Bridge Between Bytes and Physical Values

A DATA-OBJECT-PROP (DOP) is the ODX element that connects the raw byte encoding of a parameter to its physical meaning. Every VALUE parameter in ODX references a DOP, which in turn references:

DIAG-CODED-TYPE: how to extract the raw integer from the byte stream (bit position, length, byte order, sign)
COMPU-METHOD: how to convert the raw integer to a physical value with units (linear scaling, lookup table, text table)
UNIT-REF: the physical unit (km/h, bar, degC, ...)

DOPs are defined once and reused across multiple services. The same VehicleSpeed DOP is referenced by ReadDataByIdentifier_Speed, by the DTC snapshot record, and by any measured data service that uses vehicle speed.

Linear COMPU-METHOD XML

XMLcompu_methods.odx

<!-- DOP for VehicleSpeed: raw uint16, factor 0.01 km/h -->
<DATA-OBJECT-PROP ID="DOP_VehicleSpeed_kmh">
  <SHORT-NAME>VehicleSpeed_kmh</SHORT-NAME>
  <LONG-NAME>Vehicle Speed in km/h</LONG-NAME>

  <!-- Raw encoding: 16-bit unsigned, big-endian -->
  <DIAG-CODED-TYPE BASE-DATA-TYPE="A_UINT16"
                   xsi:type="STANDARD-LENGTH-TYPE">
    <BIT-LENGTH>16</BIT-LENGTH>
    <BIT-MASK>0xFFFF</BIT-MASK>
    <BYTE-ORDER>BIG-ENDIAN</BYTE-ORDER>
    <IS-SIGNED>false</IS-SIGNED>
  </DIAG-CODED-TYPE>

  <!-- Physical conversion: physical = raw * 0.01 -->
  <COMPU-METHOD>
    <SHORT-NAME>CM_VehicleSpeed_kmh</SHORT-NAME>
    <CATEGORY>LINEAR</CATEGORY>
    <COMPU-INTERNAL-TO-PHYS>
      <COMPU-SCALES>
        <COMPU-SCALE>
          <LOWER-LIMIT>0</LOWER-LIMIT>
          <UPPER-LIMIT>65535</UPPER-LIMIT>
          <COMPU-RATIONAL-COEFFS>
            <!-- physical = (V1 + V2*raw) / V3 -->
            <!-- = (0 + 1*raw) / 100 = raw * 0.01 -->
            <COMPU-NUMERATOR>
              <V>0</V>    <!-- offset -->
              <V>1</V>    <!-- multiplier -->
            </COMPU-NUMERATOR>
            <COMPU-DENOMINATOR>
              <V>100</V>  <!-- divisor -->
            </COMPU-DENOMINATOR>
          </COMPU-RATIONAL-COEFFS>
        </COMPU-SCALE>
      </COMPU-SCALES>
    </COMPU-INTERNAL-TO-PHYS>
  </COMPU-METHOD>

  <UNIT-REF ID-REF="UNIT_km_h"/>
  <PHYS-CONSTRAINT>
    <LOWER-LIMIT>0.0</LOWER-LIMIT>
    <UPPER-LIMIT>655.35</UPPER-LIMIT>
  </PHYS-CONSTRAINT>
</DATA-OBJECT-PROP>

Scale-Linear and Text-Table COMPU-METHODs

Pythoncompu_decoder.py

"""Decode raw ODX values using COMPU-METHOD logic."""

def decode_linear(raw: int, offset: float, factor: float,
                   divisor: float = 1.0) -> float:
    """LINEAR: physical = (offset + factor * raw) / divisor"""
    return (offset + factor * raw) / divisor

def decode_text_table(raw: int, table: dict) -> str:
    """TEXTTABLE: map raw integer to text string"""
    return table.get(raw, f"Unknown(0x{raw:02X})")

def decode_scale_linear(raw: int, scales: list) -> float:
    """SCALE-LINEAR: different linear params per range"""
    for lo, hi, offset, factor, divisor in scales:
        if lo <= raw <= hi:
            return (offset + factor * raw) / divisor
    raise ValueError(f"raw {raw} out of all defined ranges")

# Examples:
speed_raw = 5000
speed_kmh = decode_linear(speed_raw, offset=0, factor=1, divisor=100)
print(f"Speed: {speed_kmh} km/h")  # 50.0 km/h

dtc_status_raw = 0x08
status_text = decode_text_table(dtc_status_raw, {
    0x00: "noFault",
    0x08: "confirmedDTC",
    0x09: "confirmedDTC_testFailed",
    0x28: "pendingDTC_testFailed"
})
print(f"DTC status: {status_text}")  # confirmedDTC

Summary

COMPU-METHODs are the heart of ODX value interpretation. The most common is LINEAR (raw * factor + offset), which covers the majority of ECU measurement signals (temperature, pressure, speed). TEXTTABLE (lookup table from raw integer to text string) covers enumerated values like DTC status bytes and ECU operating modes. SCALE-LINEAR (piecewise linear with different coefficients per range) covers signals that need different scaling at different physical ranges -- common in powertrain calibration data. The COMPU-METHOD is what transforms an ODX decoder from a hex dump viewer into a meaningful diagnostic tool: without it, 0x1388 is just a number; with it, 0x1388 = 5000 / 100 = 50.0 km/h. Every diagnostic tool that displays human-readable values from ECU responses is implementing exactly this COMPU-METHOD decoding chain.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.