VeCo12 3 Diagnostics 1 Geffers Lecture PDF

FORDS DIAGNOSTIC
DEVELOPMENT PROCESS
28.11.2012
Content
Scope
History of Fords Diagnostic Development
Process
Fords New Global Diagnostic
Development Process
Summary
28.11.2012
6. Vector Congress Fords Diagnostic Development Process - Peter Geffers, Bill Waldeck, Jason Miller
SCOPE
Fords Diagnostic Development Process in PD
ECU On-Board Diagnostics
Engineering process of creating the ECU diagnostic data & functions,

and communicating to the Service / Plant SystemsTesting and
Validation of ECU diagnostics in PD
Testing and Validation of ECU Diagnostics
28.11.2012
HISTORY OF FORDS DIAGNOSTICS DEVELOPMENT PROCESS
Early 2000s:
Globally unique processes, differed by brand and region
Ford North America, Ford Europe, Ford Asia-Pacific, Ford South America,
Mazda, Jaguar, Land-Rover and Volvo
Differences with:
Diagnostic Protocols
Diagnostic Data und Functions
Dokumentation delivered to Service and Manufacturing Plants
Not consistent with Fords plans to unify brands and share

platforms globally.
4
28.11.2012
HISTORY OF FORDS DIAGNOSTICS DEVELOPMENT PROCESS

Multiple Processes &
Data Formats
Need a better way!
Ford-SA
Jaguar
Ford-APA
Land Rover
Ford-EU
Volvo
Ford-NA
Mazda
Single Process & Data

Formats
Ford-NA
Ford-APA
Ford-EU
ONE Ford
Ford-SA
Yeah!
Help!
5
28.11.2012
Service / Manufacturing Tools
Service / Manufacturing Tools
FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS
The way forward:

Exclusive use of CAN networks; moved away from legacy
protocols such as SCP, ISO-9141, and UBP.
Adoption of the ISO 14229-1 diagnostic standard for all
ECUs on CAN.
New ECU diagnostic development process in conjunction
with the ISO 14229-1 diagnostic protocol.
28.11.2012
Key Components
Engineering
Tools
GMRDB
Diagnostic
Databases
(e.g. Service
and EOL)
GDX
ECU Diagnostic Spec
CANdela
Studio
MDX
Validator
Tool
MDX
Valid
MDX
Formatting
Tool
*.doc
*.rtf
Invalid
(Feedback to Supplier)
Supplier enters ECU

diagnostic info based on
direction from D&R (e.g.,
functional requirements spec)
7
28.11.2012
<file>.C
<file>.h
ECU
ECU Diagnostic Code (CANdesc)
Conformance
Tool
Global Master Reference Database (GMRDB)
Master list of all ECU CAN IDs, DIDs, DTCs, and Routines that
may be used by an ECU.
Vectors CANdelaStudio diagnostic authoring tool
Common tool for suppliers to author On-board diagnostics.
"Multiplex Diagnostic EXchange Format" (MDX)
XML diagnostic documentation for an ECU.
ECU Diagnostic Validation & Conformance Tools
Verifies that an MDX file is correct, consistent, and plausible.

Verifies that an ECU actually behaves according to its diagnostic
documentation (MDX).
28.11.2012
Key Components
Engineering
Tools
GMRDB
Diagnostic
Databases
(e.g. Service
and EOL)
GDX
ECU Diagnostic Spec
CANdela
Studio
MDX
Validator
Tool
MDX
Valid
MDX
Formatting
Tool
*.doc
*.rtf
Invalid
Supplier enters ECU

9
28.11.2012
<file>.C
<file>.h
ECU
Conformance
Tool
GMRDB = Global Master Reference Database

All Ford ISO 14229 ECUs use Diagnostic Data from this global core database.
ECU Diagnostic IDs
Data Identifiers (DIDs)
Diagnostic Trouble Codes (DTCs)
Control Routines
Common Global meaning of e.g. Parameter

Number (e.g. DID 0x1234) same meaning in
all Ford ECUs - globally
GMRDB
All GMRDB data exported to XML Format (GDX)

GDX
-> GDX GMRDB Diagnostic EXchange Format
Facilitates automatic import by other databases and tools, such as Ford

Engineering Tools, Service Tools, EOL Tools und CANdelaStudio.
10
28.11.2012
Key Components
Engineering
Tools
GMRDB
Diagnostic
Databases
(e.g. Service
and EOL)
GDX
XSLT
ECU Diagnostic Spec
GMRDB.CDD
CANdela
Studio
MDX
Validator
Tool
MDX
Valid
MDX
Formatting
Tool
ECU.CDD
*.doc
*.rtf
Invalid
Supplier enters ECU

11
28.11.2012
<file>.C
<file>.h
ECU
Conformance
Tool
Vectors CANdelaStudio used as Diagnostic Authoring Tool.

CANdela Studio output used for:
Diagnostic embedded source code
Diagnostic documentation (MDX)
GMRDB.CDD
CANdela
Studio
ECU.CDD
CANdela Studio captures all ECU Diagnostic Information
Some information affects documentation only
Some information affects Embedded Source Code only
Most information affects both documentation and embedded source

code
12
28.11.2012
Vectors CANdelaStudio Ford template

Ford & Vector have created a special CANdelaStudio
template for Ford diagnostics
Helps guarantee specific Ford requirements are met
Contains mandatory diagnostic services and data parameters (e.g.,

DIDs, Routines, etc.)
Two versions of the template exists:
Bootloader
Non-bootloader
GMRDB.CDD
CANdela
Studio
ECU.CDD
Ford has developed a detailed walk-through user guide that

is specifically for the Ford CANdelaStudio templates.
13
28.11.2012
GMRDB and Vectors CANdelaStudio
Ford and Vector have worked together to develop a linkage between

Fords GDX format (global diagnostic data export) and CANdelaStudio.
XSL Transformation (XSLT) is used to create a CANdelaStudio input

file from the Ford GDX file. This includes:
DTCs (numbers and descriptions)

DIDs (numbers, descriptions, and all details)
Routines (numbers, descriptions, and all details)
CANdelaStudio user opens both their ECU specific CDD file and the
Ford GMRDB data CDD file.
User can copy/paste or drag/drop data parameters from GMRDB CDD

file to ECU specific CDD file.
14
28.11.2012
Key Components
Engineering
Tools
GMRDB
Diagnostic
Databases
(e.g. Service
and EOL)
GDX
ECU Diagnostic Spec
CANdela
Studio
MDX
Validator
Tool
MDX
Valid
MDX
Formatting
Tool
*.doc
*.rtf
Invalid
Supplier enters ECU

15
28.11.2012
<file>.C
<file>.h
ECU
Conformance
Tool
MDX
MDX = Multiplex Diagnostic Data Exchange Format
Next Generation Ford ECU Specific Diagnostic Specification
XML based
Replaces Fords old Excel format diagnostic specification
Global format for capturing diagnostic data in the ECU
ECU Name and ID, Protocol, Diagnostic Services,
Sessions, DTCs, DIDs, Control Routines, Security
Levels, etc.
Captures more details than traditionally captured by Ford
in the past
16
28.11.2012
MDX
MDX does not capture any details of the diagnostic request /
response PDUs.
Assumes underlying ISO 14229-1 service format.
MDX captures all supported ECU data and all relationships

between them.
MDX specifies a single method for documenting the supported

diagnostic data and the relationships between them. E.g.
Supported diagnostic sessions, security levels, DIDs, DTCs, and

Routines documented in a single standardized way.
The single method is critical to ensuring MDX tool

compatibility.
17
28.11.2012
MDX example
18
28.11.2012
6. Vector Congress Fords Diagnostic Development Process - Peter Geffers, Bill Waldeck
Key Components
Engineering
Tools
GMRDB
Diagnostic
Databases
(e.g. Service
and EOL)
GDX
ECU Diagnostic Spec
CANdela
Studio
MDX
Validator
Tool
MDX
Valid
MDX
Formatting
Tool
*.doc
*.rtf
Invalid
Supplier enters ECU

19
28.11.2012
<file>.C
<file>.h
ECU
Conformance
Tool
MDX Validator Tool

Automated validation that assists in ensuring an MDX file meets certain
requirements.
Consistency checks for:
MDX
MDX Specification / Structure
Validator
GMRDB data
Tool
DTC names, DID size, data type, resolution, etc.
GDX files as input format
General plausibility checks (e.g. mapping of DIDs with I/O control to

related diagnostic session)
Many of these checks previously performed manually
20
28.11.2012
Key Components
Engineering
Tools
GMRDB
Diagnostic
Databases
(e.g. Service
and EOL)
GDX
ECU Diagnostic Spec
CANdela
Studio
MDX
Validator
Tool
MDX
Valid
MDX
Formatting
Tool
*.doc
*.rtf
Invalid
Supplier enters ECU

21
28.11.2012
<file>.C
<file>.h
ECU
Conformance
Tool
ECU Conformance Tools

Ford created proprietary Tools for ECU Diagnostic Validation
Detailed Testing of supported Diagnostic Services / Data Parameters:
Detailed testing of ISO 15765-2 network layer implementation

(Ford ScriptPlayer)
MDX file is critical input when configuring the conformance tool
Validation of dependencies between Parameters, Sessions, and Security (e.g.

test of supported DIDs in all supported Diag. Sessions)
Important to have single method of documenting relationships with MDX
Useage of proprietary Conformance Tools, other tools like e.g. Vector CANdiva
possible (via CANdela export)
Prior to MDX, all conformance tool data configured manually!
22
28.11.2012
Summary
Key components of the Ford Diagnostic Process are:
GMRDB, CANdelaStudio, MDX, Validation & Conformance Tools
Benefits of the new Ford Diagnostic Prozess
23
ONE Global Process
CANdelaStudio and MDX help eliminating human error
Partial generation of embedded diagnostic source code
Helps to ensure that documentation matches implementation
Standardized elektronic exchange of diagnostic informationen

between supplier, engineering, manufacturing and service using MDX
Automated validation of core diagnostic requirements, data

consistency and diagnostic plausibility
28.11.2012
DISCUSSION
Danke!
Gracias!
Merci!
Thank You!
Grazie!
Fragen?
Questions?
Domandas?
Preguntas?
24
28.11.2012
Enjeux?

VeCo12 3 Diagnostics 1 Geffers Lecture PDF

Uploaded by

Copyright:

Available Formats

VeCo12 3 Diagnostics 1 Geffers Lecture PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VeCo12 3 Diagnostics 1 Geffers Lecture PDF

Uploaded by

Copyright:

Available Formats

What were the issues with Ford's previous diagnostic development processes?

What were the issues with Ford's previous diagnostic development processes?

What are the main components of Ford's new global diagnostic development process?

What are the main components of Ford's new global diagnostic development process?

FORDS DIAGNOSTIC

Fords Diagnostic Development Process in PD

ECU On-Board Diagnostics

Engineering process of creating the ECU diagnostic data & functions,

Testing and Validation of ECU Diagnostics

HISTORY OF FORDS DIAGNOSTICS DEVELOPMENT PROCESS

Diagnostic Data und Functions

Dokumentation delivered to Service and Manufacturing Plants

Not consistent with Fords plans to unify brands and share

HISTORY OF FORDS DIAGNOSTICS DEVELOPMENT PROCESS

Need a better way!

Single Process & Data

Service / Manufacturing Tools

Service / Manufacturing Tools

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

The way forward:

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

Supplier enters ECU

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

Global Master Reference Database (GMRDB)

Vectors CANdelaStudio diagnostic authoring tool

Common tool for suppliers to author On-board diagnostics.

"Multiplex Diagnostic EXchange Format" (MDX)

XML diagnostic documentation for an ECU.

ECU Diagnostic Validation & Conformance Tools

Verifies that an MDX file is correct, consistent, and plausible.

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

Supplier enters ECU

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

GMRDB = Global Master Reference Database

ECU Diagnostic IDs

Data Identifiers (DIDs)

Diagnostic Trouble Codes (DTCs)

Common Global meaning of e.g. Parameter

All GMRDB data exported to XML Format (GDX)

Facilitates automatic import by other databases and tools, such as Ford

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

ECU Diagnostic Spec

Supplier enters ECU

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

Vectors CANdelaStudio used as Diagnostic Authoring Tool.

Diagnostic embedded source code

Diagnostic documentation (MDX)

CANdela Studio captures all ECU Diagnostic Information

Some information affects documentation only

Some information affects Embedded Source Code only

Most information affects both documentation and embedded source

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

Vectors CANdelaStudio Ford template

Contains mandatory diagnostic services and data parameters (e.g.,

Two versions of the template exists:

Ford has developed a detailed walk-through user guide that

FORDS NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS

GMRDB and Vectors CANdelaStudio

Ford and Vector have worked together to develop a linkage between