Webinar Presentation: New Generation Diagnostic Tools of KPIT and Use Cases

by

Ralf Ramrath

Webinar - New Generation Tools & Use Cases

© KPIT Technologies Limited

Today’s Presenter

9/3/20132

Mr. Ralf RamrathProduct Manager Diagnostics


Today we will show you…

9/3/20133

…how to describe diagnostic functions

…how to check diagnostic data and

…how to document.

…how to commission your ECU

…how to establish a diagnostic communication

…how to validate.

…how to create executable test specifications

…how to generate test reports

…how to create own test cases.



9/3/20134



…how to document.



…how to validate.





The ECU

9/3/20135

Board from ATMEL (DVK90CAN1)

2 (almost) independant CAN Nodes

Starter Kit #1

Starter Kit #2

Inputs (Compass Key)

Outputs (8 LEDs)

Soundmodule

Fault Memory

Monitoring Values, e.g. Voltage Clamp 15/30

Functions


Diagnostic Function – Example 1

9/3/20136

Request (Tester ECU):

$22 02 20 (DID 0x0220 = Battery Voltage)

22 02 20

62 02 20 HI LO



9/3/20137

ECU

Values

0..65535

Battery-

Voltage

10.2V

02 F8

Umrechnungsfkt.:

y=0.0125x + 0.7 [V]



9/3/20138

Request (Tester ECU):

$22 02 00 (DID 0x0200 = Compass Key Status)

Bit-coded:

0=Key releases

1=Key pressed

22 02 00

62 02 00 nn

S W E N - C - -



9/3/20139

22 02 00

62 02 00 40

0 1 0 0 0 0 0 0

Bit-coded:

0=Key releases

1=Key pressed



9/3/201310

22 02 00

62 02 00 84

1 0 0 0 0 1 0 0

Bit-coded:

0=Key releases

1=Key pressed



9/3/201311



…how to document.



…how to validate.





Checking the Diagnostic Data

9/3/201312

EDITOR TESTER

Data

Creation Commissioning

Will it work?

Database

Designer

Diagnostic

CommunicatorChecker

Checking

Trafo

Checking

Report



9/3/201313



…how to document.



…how to validate.





Documenting the Diagnostic Data

9/3/201314

Database

Designer

Diagnostic

CommunicatorChecker Trafo

Checker

Report

Formatter

Diagnostic-

documentation


2 Options for Documentation

9/3/201315

Full Formatting The whole ECU


2 Options for Documentation

9/3/201316

Partial Formatting Single Diagnostic Functions or Data



9/3/201317



…how to document.



…how to validate.





Commissioning the Diagnostic Data

9/3/201318

Only 4 steps towards a successful diagnostic communication:

Step 1: Selection of the diagnostic data

Step 2: Selection of the hardware (VCI) or simulation channel

Step 3: Selection of the ECUs

Step 4 [optional]: Changing communication parameters


Commissioning – Step 1

9/3/201319


Commissioning – Step 2

9/3/201320


Commissioning – Step 3 & 4

9/3/201321



9/3/201322



…how to document.



…how to validate.





…Let’s go!

9/3/201323


Conclusion: DiagnosticCommunicator

9/3/201324



9/3/201325



…how to document.



…how to validate.





OTXSuite – Hello World!

9/3/201326


Extendable & Adaptable Test-Framework

9/3/201327

This ECU Test Panel as well as the Test specification & test report is completely

implemented in the OTX – with the OTXSuite – an executable test specification


Creation of a new Test Case

9/3/201328

ECU Test Panel (GUI)

controls

Test Bench

contains

Test Case #1

Test

Case #2

Test

Case #3

Consists

Of

Test

Steps

Step 1

Step 2

Step N

:

:


Test Case Example: Read-Write-Read

9/3/201329

The Test Case consists of the following test steps:

1. Requests ECU to transit into “Extended Session”

2. Execute Security Access

3. Read Identifier

4. Write defined set of patterns, e.g. AA or 55

5. Read back & check

6. Write back the backuped value

7. Read-Back & check


Thank you

www.kpit.com

9/3/201330

Technology

Webinar Presentation: New Generation Diagnostic Tools of KPIT and Use Cases