The Relevance of Diagnostics in Automotive Software Development


Published on

Diagnostic systems have become increasingly important throughout the automotive development chain, for instance in ECU software development. This presentation illustrates the increasing requirements for development tools regarding different diagnostic standards.

The presentation was held by Hans-Joachim Schleissheimer, CEO of Schleissheimer GmbH, at the 9th CTI forum “Automotive Diagnostic Systems” (Stuttgart, March 13-14, 2012).

Published in: Automotive, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Relevance of Diagnostics in Automotive Software Development

  1. 1. 9th International CTI Forum The Relevance of Diagnostics in Automotive Development • Increased requirements for development tools in diagnostics, complex bus communication and analysis. • Concept of a manufacturer-independent tool landscape.Hans-Joachim SchleißheimerCEO Schleißheimer GmbH
  2. 2. What is Diagnostics?• Automotive diagnostics is: – Information exchange between vehicle electronics and testing devices. – Used comprehensively during the complete product cycle. – Relevant to all ECUs and numerous testing systems. – Mainly a software feature. – Not visible to customers.
  3. 3. What is Diagnostics?• Vehicle diagnostics is the “adjustable wrench” of our tool collection.
  4. 4. What is Diagnostics?• On-board diagnostics – Built-in software functions of ECUs, used for self- diagnosis and to monitor sensors and actuators.• Off-board diagnostics – Specific diagnostic devices (testing tools) combined with measurement technology, remaining bus simulation and databases.
  5. 5. Application Development Validation Production Field• Each phase of the product cycle has specific requirements on diagnostics.
  6. 6. Requirements Field •OBD (1988) (emission control) •Service (repair shop testing devices)Production •Checking, encoding •Testing during assembly (integration) Validation •Validating vehicle functions (HIL)Development •Creating/validating individual functions •White-box software tests (free access of variables, event tracing)
  7. 7. Topology• Layer model Application protocols Application (7..5) OBD (US, EU), KW2000, UDS, CCP, XCP, ... Transfer layer Protocol (4..3) ISO-TP, TP1.6, TP2.0, J1939, FlexRay-TP, ... Physical layer Transport (2..0) UART, CAN, TTC, VAN , LIN, CCD, FlexRay, MOST, Ethernet....The layers must match between the testing device and the ECU; they are the basisof all communication between testing device and ECU.
  8. 8. Variety• Transport layer – High degree of variety; required to use diagnostics on available busses.• Protocol layer – Required in some cases; varied manufacturer- specific requirements.• Application layer – Progress (OBD, KW2000, UDS). – Increased requirements in development (UDS XCP).
  9. 9. Diagnostics in ECU Development• KWP/UDS is available in nearly every project.• XCP is seldom available, but better suited to development purposes, because: – XCP is faster due to reduced protocol overhead. – XCP offers improved access to internal data: • Scalable variables (A2L) • Bypass capability • Event availability
  10. 10. Future XCP Developments• Variable description – Description and declaration are inconsistent. Consistent description and declaration of variables inside the code or inside the configuration. Check and automatic generation of A2L files during code creation.• Events  Not only measurements, but events and their descriptions.
  11. 11. Future UDS Developments• Adoption of XCP functionality (free variable access, scaling definitions in A2L files, events)• Variable increase of bandwidth (reduced timings as required )  Merging of UDS and XCP
  12. 12. Future Tool Developments• Simultaneous recording of bus communication, values of variables and state changes in one log file.• Display of variables and events in physical values or clear text.
  13. 13. Benefits for Development• Very good basis for software testing.• Improved analysis capabilities.• Considerably improved testing and analysis even in production devices.
  14. 14. Contact Schleißheimer Soft- und Hardwareentwicklung GmbH Am Kalkofen 10 D-61206 Nieder-Wöllstadt Phone: +49 6034 9148-701 Fax: +49 6034 9148-91 – user friendly analysis, testing, and remaining bussimulation for CAN and LIN buses. Start your product trial and begin saving time right now!