| Aspect | CDD (Vector) | ODX (ISO 22901) |
|---|---|---|
| Standard | Proprietary (Vector) | Open standard (ISO) |
| Tooling | CANdelaStudio (Vector) | ODXStudio, Eclipse ODX Plugin, odxtools |
| Industry use | Dominant in European OEM supply chains | Mandated by new OEM programmes; growing adoption |
| Feature parity | Mature; all UDS features; variant coding | Equivalent feature set; richer type system |
| Interoperability | Tool-vendor dependent conversion | Any ISO 22901-compliant tool |
| Typical format | Binary .cdd or XML-based .cdd | XML .odx or .odx-d |
CDD Format vs ODX
CANdelaStudio Authoring Workflow
CANdelaStudio Workflow
1. Create CDD Database
-- New ECU diagnostic description
-- Set protocol (UDS, KWP2000, OBD-II)
-- Configure CAN IDs, timing
|
2. Define Data Types (DOPs)
-- Physical values (speed, temp, pressure)
-- Enumeration types (DTC status, mode enum)
-- Units assignment
|
3. Define Diagnostic Services
-- Select service template (RDBI, WDBI, ClearDTC...)
-- Assign parameters and DOPs
-- Set session/security requirements
|
4. Define DTCs
-- Add DTC codes with severity
-- Assign freeze frame DOPs
|
5. Configure Variants
-- Add ECU variant layers
-- Set match parameters
-- Override variant-specific services
|
6. Validate + Export
-- Run consistency check
-- Export to ODX for tool distributionSummary
CANdelaStudio is the dominant ODX/CDD authoring tool in European automotive supply chains because Vector tooling has been the standard for CAN diagnostics since the 1990s. Most OEM diagnostic data at Tier-1 suppliers exists as CDD files, and the workflow is to maintain the master in CDD format and export to ODX for exchange with non-Vector tools. The CDD-to-ODX export is mature and produces valid ODX files for all standard UDS services, but edge cases -- particularly complex variant coding logic and non-standard service types -- sometimes require manual XML correction after export. The strategic direction of new automotive programmes (especially electric vehicle platforms) is to mandate ODX as the primary format from the start, bypassing the CDD layer entirely. Engineers who understand both formats are valuable during the industry transition period.
🔬 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.