1. The document discusses the evolution of diagnostic applications from ECU-specific to generic applications that are not dependent on tool vendors. 2. It describes how to create a diagnostic flash application using OTX that can be used for any ECU by organizing flash data into sessions for different ECU variants. 3. The process involves designing a GUI interface in OTX, binding parameters to controls, creating sequences to handle GUI actions, setting the right context, retrieving flash data and deploying the reprogramming sequence.

1. by
Ralf Ramrath
Webinar –
Diagnostic Flash Application with OTX

2. © KPIT Technologies Limited
Today’s Presenter
9/3/20132
Mr. Ralf Ramrath
Product Manager
Diagnostics

3. © KPIT Technologies Limited9/3/20133
Overview of diagnostic toolchain

4. © KPIT Technologies Limited
Overview of KPIT’s diagnostic tools
9/3/20134
DatabaseDesignerNG
DiagnosticCommunicator
OTXSuite
DIAGNOSTIC DATA AUTHORING
DIAGNOSTIC TESTING
DIAGNOSTIC SEQUENCE AUTHORING
Softing: Venice
Vector: CandelaStudio, OdxStudio
Softing: Monaco
Vector: Indigo
Softing: OdxStudio
eMotive: DIagnosticFramework
Bosch: Grade-X

5. © KPIT Technologies Limited9/3/20135
The problem statement

6. © KPIT Technologies Limited
Problem statement
9/3/20136
1. Diagnostic applications are either generic or specific
2. Dependency between tool vendor and tool user
THE GOAL
1. To have a generic and specific application
2. No dependency between tool vendor and tool user

7. © KPIT Technologies Limited
Evolution of diagnostic applications (1)
9/3/20137
Flash Application
Data
Flow, GUI
Diagnostic
Protocols

8. © KPIT Technologies Limited
Evolution of diagnostic applications (2)
9/3/20138
Flash Application
Data
Flow
Diagnostic Protocols
GUI

9. © KPIT Technologies Limited
Evolution of diagnostic applications (3)
9/3/20139
ISO 22901-1
(ODX)
Java
Diagnostic Protocols
GUI
Flash application
Runtime system
Hardware Abstraction Layer (HAL)

10. © KPIT Technologies Limited
Evolution of diagnostic applications (4)
9/3/201310
ISO 22901-1
(ODX)
ISO 13209
(OTX)
Diagnostic Protocols
GUI
Flash application
Runtime system
HAL

11. © KPIT Technologies Limited
Evolution of diagnostic applications (5)
9/3/201311
ISO 22901-1
(ODX)
ISO 13209
(OTX)
Diagnostic Protocols
GUI (OTX)
Flash application (OTX)
Runtime system
HAL

12. © KPIT Technologies Limited
Comparison of the evolutionary steps (1)
9/3/201312
1
ECU specific generic
high
low
Specialization level
Dependency level
1 1 1
2222
3 3 3
4
5

13. © KPIT Technologies Limited
Today we will show, how to create a
„type-5“ application
Comparison of the evolutionary steps (2)
9/3/201313
1
ECU specific generic
high
low
Specialization level
Dependency level
1 1 1
2222
3 3 3
4
5

14. © KPIT Technologies Limited
Flash application (functional view)
9/3/201314
The flash application shall be applicable for every ECU in the vehicle
The flash application shall apply for different kind of downloads
Program
Data
Both
The flash application shall prevent from flashing the wrong software

15. © KPIT Technologies Limited
Flash application (GUI view)
9/3/201315
How to create, use & deploy a flash application
Decision 1
Decision 2

16. © KPIT Technologies Limited
How the flash data is organized
9/3/201316
ECUs / Sessions 1 2 3 4 5
Airbag, Tier1 A X
Airbag, Tier1 B X
ECM, Diesel-Engine X X
ECM, Gasoline-Eingine X X
Data for reprogramming is organized in “Flash sessions”
For every ECU variant a list of flash sessions is valid. Example:
For ECM, Diesel-Engine, Sessions 3&4 are valid

17. © KPIT Technologies Limited
How the flash data is organized
9/3/201317
Airbag, Tier1 A
Airbag, Tier1 B
ECM, Diesel
ECM, Gasoline
Session 1
Session 2
Session 3
Session 4
Session 5
ECU
Level
Session
Level
Block 1
Block 2
Segment 1
Segment 2
Segment 3
Block
Level
Segment
Level
Flashdata
Level
Code.hex
Data.hex
All.hex
Decision 1
Decision 2

18. © KPIT Technologies Limited9/3/201318
How it really works...

19. © KPIT Technologies Limited
Flash application – How it works…
9/3/201319
Step 1: Create / Design the user interface

20. © KPIT Technologies Limited
Flash application – How it works…
9/3/201320
Step 2: Bind in-/out parameters to GUI controls
Example:
listOfECUs (variable name)
List<String> (variable type)
„Variable Binding“
Example:
selectedECU (variableName)
Integer (variable type)

21. © KPIT Technologies Limited
Flash application – How it works…
9/3/201321
Step 3: Create top-level sequence that opens screen
Opens the screen
Terminates the screen
Eventhandler for GUI
actions

22. © KPIT Technologies Limited
Flash application – How it works…
9/3/201322
Every GUI action needs an event handler! Example:
User pushes button
Event fired by OTX engine
Thread resumes…
Sequence waits at event handler…

23. © KPIT Technologies Limited9/3/201323
Important OTX (Flash) commands

24. © KPIT Technologies Limited
Important OTX (Flash) commands
9/3/201324
Set the right context

25. © KPIT Technologies Limited
Important OTX (Flash) commands
9/3/201325
Getting the flash data…

26. © KPIT Technologies Limited9/3/201326
Deployment of Reprogramming
Sequence

27. © KPIT Technologies Limited
Important OTX (Flash) commands
9/3/201327
Database
DesignerNG
Sequence can be deployed to execution environment
OTXSuite
DIAGNOSTIC
DATA & SEQUENCE
AUTHORING
Diagnostic
Communicator
Diagnostic
Communicator
Diagnostic
Communicator
DIAGNOSTIC
TESTING
DIAGNOSTIC
TESTING
DEPLOYMENT
OTX
OTX
OTX

28. © KPIT Technologies Limited
Questions
9/3/201328

29. © KPIT Technologies Limited
Thank you
www.kpit.com
9/3/201329