ASAM 3D Server Xentry: Migrating Daimler’s Diagnostic System

Daimler’s legacy diagnostic system, in use since 1997, relied on a proprietary data-driven communication platform. With the launch of the 2013 S-Class (W222), Daimler transitioned to a commercial off-the-shelf (COTS) solution, leveraging an Asam 3d Server Xentry setup. This article details Daimler’s successful migration to Softing’s ASAM-compliant diagnostic platform, highlighting the strategic approach and resulting benefits.

From Proprietary to Standardized Diagnostics

Daimler’s initial system utilized a custom database for storing ECU diagnostic information and sequence systems with a proprietary API. While effective, maintaining this bespoke environment proved resource-intensive. The emergence of industry standards like ASAM MCD-2 D (ODX) for data standardization and ASAM MCD-3 D for a standardized diagnostic interface provided the impetus for change. Coupled with the maturity of ODX 2.2, a migration to a COTS solution became viable.

Choosing a COTS Solution: The Softing ASAM 3D Server

The decision to adopt a COTS solution offered Daimler several key advantages:

  • Leveraging Industry Standards: Utilizing ASAM standards ensured interoperability and future-proofing.
  • Reduced Maintenance Costs: Shifting from in-house development to a supported platform significantly reduced maintenance overhead.
  • Vendor Independence: Embracing open standards fostered competition and flexibility in choosing diagnostic tools and suppliers.

Softing’s ASAM 3D server, a core component of the Xentry Diagnostics system, became the chosen platform. This allowed Daimler to integrate seamlessly with existing tools like DTS Monaco for engineering testing.

The Migration Strategy: A Phased Approach

A meticulous, multi-phase migration strategy was crucial for minimizing disruption:

  1. VCI Driver Conversion: The Vehicle Communication Interface (VCI) driver was converted to the D-PDU API standard, enabling compatibility with both the legacy system and the new ASAM 3D server.
  2. Proof of Concept: A successful Proof of Concept (PoC) validated the feasibility and capabilities of the ASAM-based solution within Daimler’s environment.
  3. Phased Rollout: The new system was initially deployed with the engineering tester (DTS Monaco), followed by piloting in manufacturing (NISP) and after-sales (XENTRY Diagnostics). This allowed for iterative testing and refinement.
  4. Parallel Operation: Running both systems concurrently enabled a gradual phase-out of the legacy platform, ensuring continued support for older vehicles in after-sales while minimizing disruption to existing processes. This eliminated the need for immediate mass conversion of legacy data and test sequences.

Challenges and Solutions

The migration wasn’t without its challenges. Certain existing functionalities within Daimler’s tools required specific extensions to the Softing ASAM 3D server. However, the inherent flexibility of the ASAM standard and Softing’s development methodology allowed for seamless implementation of these necessary additions.

Results and Benefits

The migration to Softing’s ASAM 3D server Xentry solution proved highly successful. Daimler achieved:

  • Standardized Diagnostics: Full compliance with ASAM standards ensured interoperability and simplified collaboration with other OEMs.
  • Cost Savings: Reduced maintenance and development costs through leveraging a COTS solution.
  • Improved Efficiency: Standardized data and processes streamlined workflows across engineering, manufacturing, and after-sales.
  • Future-Proofing: The adoption of open standards ensured adaptability to future diagnostic technologies.

The successful implementation validated the years of effort invested in developing and standardizing the ASAM framework, demonstrating the real-world benefits of embracing open standards in automotive diagnostics. The ASAM 3D server Xentry implementation provided Daimler with a robust, scalable, and future-proof diagnostic platform.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *