The Relevance of Diagnostics in Automotive Software Development

14
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ßheimer CEO Schleißheimer GmbH

description

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

Transcript of The Relevance of Diagnostics in Automotive Software Development

Page 1: The Relevance of Diagnostics in Automotive Software Development

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ßheimer

CEO Schleißheimer GmbH

Page 2: The Relevance of Diagnostics in Automotive Software Development

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.

Page 3: The Relevance of Diagnostics in Automotive Software Development

• Vehicle diagnostics is the “adjustable wrench” of our tool collection.

What is Diagnostics?

Page 4: The Relevance of Diagnostics in Automotive Software Development

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

What is Diagnostics?

Page 5: The Relevance of Diagnostics in Automotive Software Development

• Each phase of the product cycle has specific requirements on diagnostics.

Development Validation Production Field

Application

Page 6: The Relevance of Diagnostics in Automotive Software Development

•OBD (1988) (emission control)

•Service (repair shop testing devices)

•Checking, encoding•Testing during assembly (integration)

•Validating vehicle functions (HIL)

•Creating/validating individual functions•White-box software tests

(free access of variables, event tracing)

Field

Production

Validation

Development

Requirements

Page 7: The Relevance of Diagnostics in Automotive Software Development

• Layer model

Transport (2..0)

Protocol (4..3)

Application (7..5)

Physical layer UART, CAN, TTC, VAN , LIN, CCD, FlexRay, MOST, Ethernet....

Transfer layer ISO-TP, TP1.6, TP2.0, J1939, FlexRay-TP, ...

Application protocols OBD (US, EU), KW2000, UDS, CCP, XCP, ...

The layers must match between the testing device and the ECU; they are the basis of all communication between testing device and ECU.

Topology

Page 8: The Relevance of Diagnostics in Automotive Software Development

• 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).

Variety

Page 9: The Relevance of Diagnostics in Automotive Software 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

Diagnostics in ECU Development

Page 10: The Relevance of Diagnostics in Automotive Software Development

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

Future XCP Developments

Page 11: The Relevance of Diagnostics in Automotive Software Development

• 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

Future UDS Developments

Page 12: The Relevance of Diagnostics in Automotive Software Development

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

Future Tool Developments

Page 13: The Relevance of Diagnostics in Automotive Software Development

• Very good basis for software testing.

• Improved analysis capabilities.

• Considerably improved testing and analysis even in production devices.

Benefits for Development

Page 14: The Relevance of Diagnostics in Automotive Software Development

Schleißheimer Soft- undHardwareentwicklung GmbH

Am Kalkofen 10D-61206 Nieder-Wöllstadt

Phone: +49 6034 9148-701Fax: +49 6034 9148-91

[email protected]

www.schleissheimer.de

www.CanEasy.de – user friendly analysis, testing, and remaining bus simulation for CAN and LIN buses. Start your product trial and begin saving

time right now!

Contact