17
ECU Diagnostics in HIL Applications Dr.-Ing. Jobst Richert · Section Manager SW Development dSPACE GmbH · Technologiepark 25 · 33100 Paderborn automotive testing expo · 6th of may 2008

ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

  • Upload
    others

  • View
    43

  • Download
    1

Embed Size (px)

Citation preview

Page 1: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

ECU Diagnostics in HIL Applications

Dr.-Ing. Jobst Richert · Section Manager SW Development

dSPACE GmbH · Technologiepark 25 · 33100 Paderborn

automotive testing expo · 6th of may 2008

Page 2: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Content

ECU Diagnostics – Some Basics

Automated Testing of ECU Diagnostics using HIL

ECU Diagnostics as an Auxiliary Means in HIL

Applying ASAM Diagnostics Standards in HIL

Practical Problems

Solution Approaches

Summary and Outlook

Page 3: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Role of ECU Diagnostics

Reading out Failure Memory

Clearing Failure Memory

Reading Measurement Values

Testing of Actuators

Flashing of new Software

Coding of Variants

Identification of assembled components

Determination degree of damage and abrasion

Activation of ECU internal test routines

Customizing, Adaptation, EOL-Testing

Production

Test & Release

Development

Failure Detection, Failure Correction

Service

Page 4: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Importance and Complexity of ECU Diagnostics

Diagnostics in Motronic-Systems covers …

40 % of Calibration Parameters

40 % of Functions

40 % of Lines of Codes

40-50 % of Processor Runtime

Source: KLEE, P.; KNIRSCH, M.; WILLIMOWSKI, M.: Herausforderungen der Diagno-seentwicklung in der Motorsteuerung, in: Onboard-Diagnose – Status der Gesetzgebung und Auswirkungen auf die Fahrzeugentwicklung, expert-Verlag, Renningen, 2005

Percentage of ECU Diagnostics test …

Up to 25 % of overall test costs

Page 5: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Automated Testing of ECU Diagnostics using HIL

Cable Harness

Real-TimeModel

FailureInjection

HIL-Simulator

TestautomationTest Sequences

Test Parameter

PC

DiagnosticsInterface

Diagnosticstool

Database

Page 6: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

ECU Diagnostics as an Auxiliary Means in HIL

Scenario 1: Putting into operation or reconstruction of a HIL simulator …

Failure Memory Handling (reading and clearing)No failure memory entries == reference operation of HIL

Coding of relevant variant(s) of System Under Test

I/O check by activation of actuator test

Adaptation of assembled sensors / actuators

Scenario 2: Manual or automated ECU diagnostics test …

Identification of System Under Test

Subsequent coding of relevant variant(s) of System Under Test

Preparation of error-free starting condition of test sequence by clearing the diagnostic trouble codes

Reading out measurement values

Modification of calibration parameters

Page 7: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Retrospection: Diversity of proprietary Diagnostic Solutions

KIC-Dll

KICETAS

kiclib

K-Line

vagtlib1

rs232lib

KICVAGT

CAN

DTS Base

dtslib

vastlib

EDIABAS

ADSBMW

ediabaslib

SGBD-files

DTS-Database

(prop.)

DIOGENES-DB

(SGML)

Standard ISO9141 hardware

KWP2000baselib

iso9141lib

KWP2000Version 3

KWP2000Version 2

KWP2000Version1

Excerpt from thepalett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000)

Page 8: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Existing Standards around ECU Diagnostics

M

Measu

remen

t

C

Calibra

tionASAM

MCD-2MC(ASAP2)

Database

ASAM MCD 3 (MC)

ClientApplication

ASAM MCD 3 (D)in the past:ASAP3

ASAM MCD-1MC(ASAP1) Bus

DriverASAM MCD-1b

ECU

HWInterface

DriverHW

Interface

ASAM MCD-1a(CCP, XCP) HW

Interface

D

Diagno

stics

Database

ASAM MCD-2D(ODX)

No ASAM Standard

ISO9141, ISO14229, ISO14230, ISO15765

Page 9: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Server side implementation of ECU Diagnostics Standards in CalDesk

ASAP 3 Server (RS232 or TCP/IP)

MCD 3 Server (D(COM))

Database

ASAM MCD-2MC(ASAP2)

ECU

e.g. ASAM MCD 1(CCP, XCP on CAN, XCP on USB,XCP on Flexray)

MCD 3DServer

Database

ASAM MCD-2D(ODX)

MVCI PDU API

e.g. ISO9141 (K-Line)ISO14230 (KWP2000),ISO15765 (KWP on CAN), ISO14229 (UDS)

CalDeskCalDesk

Page 10: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Client side implementation of ECU Diagnostics Standards in AutomationDesk

Graphical TestsequencesAccess to interfaces via block librariesManagement of test projectsArchiving test results, report generation

AutomationDeskAutomationDesk

MC ToolsINCACANape…

…D Tools

IN2SOFTDTSDSAT-Systems

dSPACE

Simulator

FailureInjectionHardware

ASAMMCD-3MC

ASAMMCD-3D

CalDeskCalDesk

D ToolsRA-Consulting…

3rd PartySimulators

dSPACE Products

3rd Party Products

ASAM standardized

proprietary

Page 11: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Client side implementation of ECU Diagnostics Standards in AutomationDesk

MCD 3D ServerMCD 3D Server

ASAM MCD-2D(ODX)

(D)COM

e.g. IN2SOFT,SOFTING, T-Systems,…

Analog I/O, Digital I/O, CAN

Host interface

HIL simulator

ECU

AutomationDesk

Page 12: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

AutomationDesk

Page 13: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Practical Problems

1. Weak point: Diagnostics Data Bases Content

Still in practise: proprietary data bases

ODX complexity, incompatibilities resp. missing semantic clearness

Migration

2. Weak point: Diagnostics Data Bases Availability in time

3. Weak point: Automation Interface

Still in practise: proprietary APIs, using very different technologies

Very complex, very generic MCD-3D API – hard to use for ECU test developers

4. Weak point: OEM spefic binaries

5. Weak point: Know-how hurdle between HIL- and ECU diagnostics area

Page 14: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Solution Approaches

1. Weak point: Diagnostics Data Bases Content

Freeze ODX in its today‘s version

ODX Authoring Guidelines

Best practise exchange between OEMs and Tier1

2. Weak point: Diagnostics Data Bases Availability in time

ODX Development to follow the entire software development cyclefrom specification to prototyping to implementation to test

3. Weak point: Automation Interface

HIL, i.e test-oriented convenience layer

new ASAM HIL-API project (DIAG Port)

5. Weak point: Know-how hurdle between HIL- and ECU diagnostics area

ASAM HIL API project (DIAG Port)

Page 15: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

ASAM HIL API project

Separated test systems today

ASAM HIL API Goal:Separation of Test HW and Test SW by means of standardized APIs

Future Standardization (under prep.):Exchange of test cases between different softwaresystems by means of astandardized Test Exhange Format

Page 16: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Summary and Outlook

ECU diagnostics is a very complex topic

HIL technology is essential for ECU diagnostics testing

ASAM Standards are indispensable for cost-effective test environments

ASAM Standards are indispensable for ECU development processes

Interaction of HIL and ECU diagnostics can be optimized

Very promising new standardization project HIL API will lead to new solutionsprobably in 2009

Page 17: ECU Diagnostics in HIL ApplicationsKWP2000 Version 2 KWP2000 Version1 Excerpt from the palett of dSPACE solutions for ECU Diagnostics Interface (Mid 2000) Existing Standards around

Important Notice

© Copyright 2008, dSPACE GmbH. All rights reserved.

Brand names or product names are trademarks or registered trademarks of their respective companies or organizations.

Thank you !