You are on page 1of 24

FORD’S DIAGNOSTIC DEVELOPMENT PROCESS

28.11.2012

Content

 Scope  History of Ford’s Diagnostic Development Process  Ford‘s New Global Diagnostic Development Process  Summary

2

28.11.2012

6. Vector Congress – Ford’s Diagnostic Development Process - Peter Geffers, Bill Waldeck, Jason Miller

11. and communicating to the Service / Plant SystemsTesting and Validation of ECU diagnostics in PD • Testing and Validation of ECU Diagnostics 3 28.2012 6. Bill Waldeck.Peter Geffers. Jason Miller .SCOPE Ford’s Diagnostic Development Process in PD • • ECU On-Board Diagnostics Engineering process of creating the ECU diagnostic data & functions. Vector Congress – Ford’s Diagnostic Development Process .

Ford Europe. differed by brand and region Ford North America. Ford South America. Mazda. Jason Miller .HISTORY OF FORD’S DIAGNOSTICS DEVELOPMENT PROCESS Early 2000‘s: Globally unique processes. Ford Asia-Pacific. Jaguar.Peter Geffers. Land-Rover and Volvo Differences with: • • • Diagnostic Protocols Diagnostic Data und Functions Dokumentation delivered to Service and Manufacturing Plants Not consistent with Ford‘s plans to unify brands and share platforms globally.11. Vector Congress – Ford’s Diagnostic Development Process . Bill Waldeck.2012 6. 4 28.

Bill Waldeck.HISTORY OF FORD’S DIAGNOSTICS DEVELOPMENT PROCESS Multiple Processes & Data Formats Ford-SA Ford-APA Ford-EU Ford-NA Need a better way! Single Process & Data Formats Ford-APA Ford-NA Jaguar Land Rover Volvo Mazda Ford-EU ONE Ford Ford-SA Yeah! Help! 5 28.11. Vector Congress – Ford’s Diagnostic Development Process .Peter Geffers.2012 Service / Manufacturing Tools Service / Manufacturing Tools 6. Jason Miller .

Peter Geffers. • Adoption of the ISO 14229-1 diagnostic standard for all ECUs on CAN. ISO-9141. and UBP. Bill Waldeck. moved away from legacy protocols such as SCP.11. 6 28.2012 6.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS The way forward: • Exclusive use of CAN networks. Jason Miller . • New ECU diagnostic development process in conjunction with the ISO 14229-1 diagnostic protocol. Vector Congress – Ford’s Diagnostic Development Process .

11.C <file>. functional requirements spec) 7 28.rtf (Feedback to Supplier) Supplier enters ECU diagnostic info based on direction from D&R (e.g. Bill Waldeck. Jason Miller . Vector Congress – Ford’s Diagnostic Development Process . Service and EOL) GDX ECU Diagnostic Spec CANdela Studio MDX Invalid MDX Validator Tool Valid MDX Formatting Tool *.Peter Geffers.h ECU ECU Diagnostic Code (CANdesc) Conformance Tool 6.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Key Components GMRDB Engineering Tools Diagnostic Databases (e.g..doc *.2012 <file>.

Bill Waldeck. • ECU Diagnostic Validation & Conformance Tools • • Verifies that an MDX file is correct. • Vector’s CANdelaStudio diagnostic authoring tool • Common tool for suppliers to author On-board diagnostics. Verifies that an ECU actually behaves according to its diagnostic documentation (MDX).2012 6. consistent.Peter Geffers. and Routines that may be used by an ECU. DTCs. and plausible. • "Multiplex Diagnostic EXchange Format" (MDX) • XML diagnostic documentation for an ECU. 8 28. Jason Miller .FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS • Global Master Reference Database (GMRDB) • Master list of all ECU CAN IDs. DIDs.11. Vector Congress – Ford’s Diagnostic Development Process .

doc *.h ECU ECU Diagnostic Code (CANdesc) Conformance Tool 6.g.rtf (Feedback to Supplier) Supplier enters ECU diagnostic info based on direction from D&R (e. functional requirements spec) 9 28.g.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Key Components GMRDB Engineering Tools Diagnostic Databases (e.C <file>. Bill Waldeck..Peter Geffers. Vector Congress – Ford’s Diagnostic Development Process .11.2012 <file>. Jason Miller . Service and EOL) GDX ECU Diagnostic Spec CANdela Studio MDX Invalid MDX Validator Tool Valid MDX Formatting Tool *.

Vector Congress – Ford’s Diagnostic Development Process . such as Ford Engineering Tools.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS GMRDB = Global Master Reference Database All Ford ISO 14229 ECUs use Diagnostic Data from this global core database.globally All GMRDB data exported to XML Format (GDX) GDX -> GDX “GMRDB Diagnostic EXchange Format” Facilitates automatic import by other databases and tools.2012 6.g. Bill Waldeck. Jason Miller . 10 28. EOL Tools und CANdelaStudio.11. Service Tools.Peter Geffers. • • • • ECU Diagnostic IDs Data Identifiers (DIDs) Diagnostic Trouble Codes (DTCs) Control Routines GMRDB Common Global meaning of e.g. DID 0x1234) same meaning in all Ford ECUs . Parameter Number (e.

rtf (Feedback to Supplier) Supplier enters ECU diagnostic info based on direction from D&R (e.2012 <file>. Bill Waldeck.Peter Geffers.g.g.CDD MDX Invalid MDX Validator Tool Valid MDX Formatting Tool *.CDD ECU Diagnostic Spec CANdela Studio ECU. Service and EOL) GDX XSLT GMRDB.11. Vector Congress – Ford’s Diagnostic Development Process . functional requirements spec) 11 28. Jason Miller .C <file>.doc *.h ECU ECU Diagnostic Code (CANdesc) Conformance Tool 6..FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Key Components GMRDB Engineering Tools Diagnostic Databases (e.

Peter Geffers.CDD CANdela Studio ECU.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Vector’s CANdelaStudio used as Diagnostic Authoring Tool.11.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. Vector Congress – Ford’s Diagnostic Development Process . CANdela Studio output used for: • • Diagnostic embedded source code Diagnostic documentation (MDX) GMRDB. Bill Waldeck.2012 6. Jason Miller .

. 13 28.CDD • Two versions of the template exists: • • Bootloader Non-bootloader CANdela Studio ECU. Jason Miller .11.) GMRDB.CDD • Ford has developed a detailed walk-through user guide that is specifically for the Ford CANdelaStudio templates. DIDs.g. Routines. Vector Congress – Ford’s Diagnostic Development Process . Bill Waldeck.Peter Geffers. etc.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Vector’s 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.2012 6.

Peter Geffers. User can copy/paste or drag/drop data parameters from GMRDB CDD file to ECU specific CDD file. descriptions. and all details) • CANdelaStudio user opens both their ECU specific CDD file and the Ford GMRDB data CDD file. and all details) Routines (numbers.2012 6. descriptions. XSL Transformation (XSLT) is used to create a CANdelaStudio input file from the Ford GDX file.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS GMRDB and Vector’s CANdelaStudio • Ford and Vector have worked together to develop a linkage between Ford’s GDX format (global diagnostic data export) and CANdelaStudio. Jason Miller . Vector Congress – Ford’s Diagnostic Development Process . This includes: • • • • DTCs (numbers and descriptions) DIDs (numbers. • 14 28. Bill Waldeck.11.

FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Key Components GMRDB Engineering Tools Diagnostic Databases (e.rtf (Feedback to Supplier) Supplier enters ECU diagnostic info based on direction from D&R (e.g. Vector Congress – Ford’s Diagnostic Development Process .11. Jason Miller .2012 <file>.g.. Service and EOL) GDX ECU Diagnostic Spec CANdela Studio MDX Invalid MDX Validator Tool Valid MDX Formatting Tool *.doc *. Bill Waldeck. functional requirements spec) 15 28.Peter Geffers.C <file>.h ECU ECU Diagnostic Code (CANdesc) Conformance Tool 6.

• Captures more details than traditionally captured by Ford in the past 16 28. Control Routines.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS MDX MDX = Multiplex Diagnostic Data Exchange Format • Next Generation Ford ECU Specific Diagnostic Specification • XML based • Replaces Ford’s old Excel format diagnostic specification • Global format for capturing diagnostic data in the ECU • ECU Name and ID. Protocol. Sessions.2012 6. Security Levels. Vector Congress – Ford’s Diagnostic Development Process .11. DTCs. Bill Waldeck. etc. Jason Miller .Peter Geffers. DIDs. Diagnostic Services.

11.g. and Routines documented in a single standardized way. • MDX specifies a single method for documenting the supported diagnostic data and the relationships between them. • The single method is critical to ensuring MDX tool compatibility.2012 6. • MDX captures all supported ECU data and all relationships between them. Bill Waldeck. 17 28. security levels. DIDs. DTCs.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS MDX • MDX does not capture any details of the diagnostic request / response PDUs. • Assumes underlying ISO 14229-1 service format. Jason Miller . Vector Congress – Ford’s Diagnostic Development Process . • Supported diagnostic sessions. E.Peter Geffers.

Peter Geffers.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS MDX example 18 28. Bill Waldeck . Vector Congress – Ford’s Diagnostic Development Process .2012 6.11.

. Vector Congress – Ford’s Diagnostic Development Process . Bill Waldeck.11. Jason Miller . Service and EOL) GDX ECU Diagnostic Spec CANdela Studio MDX Invalid MDX Validator Tool Valid MDX Formatting Tool *. functional requirements spec) 19 28.h ECU ECU Diagnostic Code (CANdesc) Conformance Tool 6.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Key Components GMRDB Engineering Tools Diagnostic Databases (e.g.C <file>.rtf (Feedback to Supplier) Supplier enters ECU diagnostic info based on direction from D&R (e.doc *.Peter Geffers.g.2012 <file>.

mapping of DIDs with I/O control to related diagnostic session) Many of these checks previously performed manually 20 28.g.Peter Geffers. resolution.2012 6. Vector Congress – Ford’s Diagnostic Development Process .FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS MDX Validator Tool Automated validation that assists in ensuring an MDX file meets certain requirements. • GDX files as input format • • General plausibility checks (e. data type. etc.11. Bill Waldeck. Consistency checks for: MDX • MDX Specification / Structure Validator • GMRDB data Tool • DTC names. Jason Miller . DID size.

functional requirements spec) 21 28.g.rtf (Feedback to Supplier) Supplier enters ECU diagnostic info based on direction from D&R (e.11.Peter Geffers.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Key Components GMRDB Engineering Tools Diagnostic Databases (e. Service and EOL) GDX ECU Diagnostic Spec CANdela Studio MDX Invalid MDX Validator Tool Valid MDX Formatting Tool *..doc *. Bill Waldeck.2012 <file>.g. Jason Miller .C <file>. Vector Congress – Ford’s Diagnostic Development Process .h ECU ECU Diagnostic Code (CANdesc) Conformance Tool 6.

Sessions. and Security (e.g.FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS 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. test of supported DIDs in all supported Diag. Vector CANdiva possible (via CANdela export) Prior to MDX.Peter Geffers. other tools like e. all conformance tool data configured manually! 22 28. Vector Congress – Ford’s Diagnostic Development Process .g. Jason Miller .11. Sessions) Important to have single method of documenting relationships with MDX Useage of proprietary Conformance Tools.2012 6. Bill Waldeck.

manufacturing and service using MDX Automated validation of core diagnostic requirements. Jason Miller .FORD‘S NEW GLOBAL DIAGNOSTIC DEVELOPMENT PROCESS Summary • • Key components of the Ford Diagnostic Process are: • • • GMRDB. data consistency and diagnostic plausibility 23 28. engineering.11. MDX. Bill Waldeck. CANdelaStudio. Validation & Conformance Tools ONE Global Process CANdelaStudio and MDX help eliminating human error • • • • Partial generation of embedded diagnostic source code Helps to ensure that documentation matches implementation Benefits of the new Ford Diagnostic Prozess Standardized elektronic exchange of diagnostic informationen between supplier. Vector Congress – Ford’s Diagnostic Development Process .2012 6.Peter Geffers.

Peter Geffers.11. Bill Waldeck. Vector Congress – Ford’s Diagnostic Development Process .2012 6. Jason Miller .DISCUSSION Danke! Merci! Gracias! Thank You! Grazie! Fragen…? Domandas…? Questions…? Preguntas…? Enjeux…? 24 28.