Hands-On: Complete Service Authoring - ODX & Diagnostic Data

Lab: Complete Service Authoring in ODX XML

Deliverable	Specification
RDBI service for EngineSpeed	DID 0xF402; raw uint16; factor 0.25 rpm; range 0-16383.75 rpm
WDBI service for IdleSpeed	DID 0xFD02; raw uint16; range 600-1500 rpm; extended session only
DTC P0507 EngineSpeedHigh	DTC 0x050700; freeze frame: EngineSpeed + Throttle + VehicleSpeed
Variant match for ECU_Petrol	HW=0x0300; FuelType=0x01 (petrol); 3 match params

Exercise 1: RDBI Service for EngineSpeed

XMLengine_speed_rdbi.odx

<!-- DOP: EngineSpeed raw uint16, 0.25 rpm/bit -->
<DATA-OBJECT-PROP ID="DOP_EngineSpeed_rpm">
  <SHORT-NAME>EngineSpeed_rpm</SHORT-NAME>
  <DIAG-CODED-TYPE BASE-DATA-TYPE="A_UINT16"
                   xsi:type="STANDARD-LENGTH-TYPE">
    <BIT-LENGTH>16</BIT-LENGTH>
    <BYTE-ORDER>BIG-ENDIAN</BYTE-ORDER>
    <IS-SIGNED>false</IS-SIGNED>
  </DIAG-CODED-TYPE>
  <COMPU-METHOD>
    <CATEGORY>LINEAR</CATEGORY>
    <COMPU-INTERNAL-TO-PHYS>
      <COMPU-SCALES>
        <COMPU-SCALE>
          <LOWER-LIMIT>0</LOWER-LIMIT>
          <UPPER-LIMIT>65535</UPPER-LIMIT>
          <COMPU-RATIONAL-COEFFS>
            <COMPU-NUMERATOR><V>0</V><V>1</V></COMPU-NUMERATOR>
            <COMPU-DENOMINATOR><V>4</V></COMPU-DENOMINATOR>
          </COMPU-RATIONAL-COEFFS>
        </COMPU-SCALE>
      </COMPU-SCALES>
    </COMPU-INTERNAL-TO-PHYS>
  </COMPU-METHOD>
  <UNIT-REF ID-REF="UNIT_rpm"/>
</DATA-OBJECT-PROP>

<!-- RDBI service 0x22 for DID 0xF402 -->
<DIAG-COMM ID="DC_RDBI_EngineSpeed" xsi:type="REQUEST-RESPONSE-COMM">
  <SHORT-NAME>ReadDataByIdentifier_EngineSpeed</SHORT-NAME>
  <REQUEST ID="REQ_RDBI_EngineSpeed">
    <PARAMS>
      <PARAM xsi:type="CODED-CONST" BYTE-POSITION="0">
        <SHORT-NAME>SID</SHORT-NAME>
        <CODED-VALUE>0x22</CODED-VALUE>
        <DIAG-CODED-TYPE BASE-DATA-TYPE="A_UINT8"
                         xsi:type="STANDARD-LENGTH-TYPE">
          <BIT-LENGTH>8</BIT-LENGTH>
        </DIAG-CODED-TYPE>
      </PARAM>
      <PARAM xsi:type="CODED-CONST" BYTE-POSITION="1">
        <SHORT-NAME>DataIdentifier</SHORT-NAME>
        <CODED-VALUE>0xF402</CODED-VALUE>
        <DIAG-CODED-TYPE BASE-DATA-TYPE="A_UINT16"
                         xsi:type="STANDARD-LENGTH-TYPE">
          <BIT-LENGTH>16</BIT-LENGTH>
        </DIAG-CODED-TYPE>
      </PARAM>
    </PARAMS>
  </REQUEST>
  <POS-RESPONSES>
    <POS-RESPONSE ID="RSP_RDBI_EngineSpeed">
      <PARAMS>
        <PARAM xsi:type="CODED-CONST" BYTE-POSITION="0">
          <SHORT-NAME>SID_Resp</SHORT-NAME>
          <CODED-VALUE>0x62</CODED-VALUE>
          <DIAG-CODED-TYPE BASE-DATA-TYPE="A_UINT8"
                           xsi:type="STANDARD-LENGTH-TYPE">
            <BIT-LENGTH>8</BIT-LENGTH>
          </DIAG-CODED-TYPE>
        </PARAM>
        <PARAM xsi:type="VALUE" BYTE-POSITION="3">
          <SHORT-NAME>EngineSpeed</SHORT-NAME>
          <DOP-REF ID-REF="DOP_EngineSpeed_rpm"/>
        </PARAM>
      </PARAMS>
    </POS-RESPONSE>
  </POS-RESPONSES>
</DIAG-COMM>

Summary

The complete service authoring lab demonstrates that ODX authoring is inherently hierarchical: before writing a DIAG-COMM, you must define its DATA-OBJECT-PROPs; before defining the DOPs, you must define the COMPU-METHODs and UNITS. This bottom-up dependency order means that ODX files are almost always authored using tools (CANdelaStudio, ODXStudio) rather than by hand -- the tools manage the cross-references and IDs automatically. The lab exercises done in raw XML are valuable for understanding the structure, but in production practice the XML is generated by the tool and the engineer interacts with forms and wizards. The key engineering knowledge is understanding what each element means and checking that the tool-generated XML correctly encodes the intended service behaviour.

🔬 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.