handb-winkfpt32 5.1 v1.8 eng - coding e90codinge90.com/wp-content/uploads/2014/05/winkfp... · fig....

WinKFPTUser's Guide

Date: 20.10.04

File: Handb-winkfpt32(5.1)_v1.8_eng.doc Version: 1.8

WinKFPT 5.1

User's Guide

Version 1.8

WinKFPTUser's Guide

Date: 20.10.04


Contents

1 FOREWORD ............................................................................................................................9

1.1 Using this User's Guide and the Online Help..............................................................................9

1.2 About This User's Guide..........................................................................................................10

1.3 Conventions Used ...................................................................................................................11

2 INTRODUCTION.....................................................................................................................12

2.1 About WinKFPT ......................................................................................................................12

2.2 Possibilities in WinKFPT .........................................................................................................12

2.2.1Multiple Instancing Capability ..........................................................................................12

2.2.2Operating Modes.............................................................................................................13

2.2.3Programming of ECUs in Dialog Mode ............................................................................14

2.2.4Programming of ECUs in Batch Mode .............................................................................14

2.3 Architecture of WinKFPT.........................................................................................................15

3 FIRST STEPS.........................................................................................................................16

3.1 System Requirements of WinKFPT .........................................................................................16

3.2 Installing WinKFPT .................................................................................................................16

3.3 Directory Structure of WinKFPT .............................................................................................17

3.3.1Configuration of the basic directory for the working directories of WinKFPT.....................22

3.4 Configuring WinKFPT .............................................................................................................23

3.4.1Configuration in COAPI.INI..............................................................................................23

3.4.2Configuration in WINKFPT.INI .........................................................................................26

3.4.3Configuration for Expert Mode .........................................................................................32

3.4.4Configuration in EDIABAS.INI..........................................................................................37

3.5 Reference Configuration of WinKFPT ......................................................................................38

4 STARTING WINKFPT .............................................................................................................40

4.1 Calling Parameters of WinKFPT..............................................................................................40

4.1.1Type Description of the Calling Parameters of WinKFPT .................................................42

4.2 Status Displays of WinKFPT ...................................................................................................43

4.3 Starting WinKFPT in Compile Mode ........................................................................................46

4.4 Starting WinKFPT in Batch Mode ............................................................................................48

4.4.1Control File for Batch Mode in Comfort Mode ..................................................................51

4.4.2Control File for Batch Mode in Expert Mode.....................................................................53

4.4.3Starting a Programming Job in Batch Mode.....................................................................55

4.4.4Switching HW Interface and Diagnosis Protocol in Batch Mode .......................................57

4.4.5Starting Several Instances in Batch Mode........................................................................58

4.5 Starting WinKFPT in Dialog Mode ...........................................................................................59

4.5.1Starting Several Instances in Dialog Mode.......................................................................59

WinKFPTUser's Guide

Date: 20.10.04


5 WINKFPT'S MAIN MENU........................................................................................................61

5.1 Display Menu ..........................................................................................................................61

5.1.1Display �

CABI.ERR ......................................................................................................62

5.1.2Display �

ERROR.LOG..................................................................................................62

5.1.3Display �

PABD Parameters ..........................................................................................62

5.1.4Display �

HW History.....................................................................................................62

5.1.5Display �

ZB History ......................................................................................................62

5.1.6Display �

ZB Rules ........................................................................................................62

5.1.7Display �

API Trace File.................................................................................................63

5.1.8Display �

IFH Trace File.................................................................................................63

5.1.9Display �

Batch Mode ....................................................................................................63

5.2 Import/Export Menu.................................................................................................................64

5.2.1Import Submenu .............................................................................................................64

5.2.2Export Submenu .............................................................................................................82

5.2.3Deleting Assembly Line Data...........................................................................................92

5.3 Communication Menu .............................................................................................................95

5.3.1Selecting (Choosing) a HW Interface...............................................................................96

5.3.2Selecting (Choosing) a Diagnosis Protocol ......................................................................98

5.4 Configuration Menu ...............................................................................................................100

5.5 Help Menu.............................................................................................................................103

5.5.1Contents - Calling the Online Help.................................................................................103

5.5.2Info - Version Information of WinKFPT ..........................................................................104

5.6 End Menu..............................................................................................................................106

5.6.1Exit 106

6 FUNCTIONS OF WINKFPT...................................................................................................107

6.1 Function Start Menu: Operating Modes of WinKFPT..............................................................110

6.1.1Comfort Mode ...............................................................................................................112

6.1.2Expert Mode..................................................................................................................116

7 FUNCTION PHASES IN COMFORT MODE ..........................................................................119

7.1 Functions of the Programming Settings Phase in Comfort Mode............................................120

7.1.1Function: Entering a ZUSB Number...............................................................................121

7.1.2Function: Selecting a ZUSB number ..............................................................................124

7.1.3Function: Updating an Assembly Identification...............................................................125

7.1.4Function: Entering a Vehicle Identification Number ........................................................127

7.1.5Function: Done (Comfort Mode) ....................................................................................129

7.2 Functions of the Programming Execution Phase in Comfort Mode .........................................130

7.2.1Function: Flash Programming .......................................................................................131

7.2.2Function: Programming Update.....................................................................................134

8 FUNCTION PHASES IN EXPERT MODE ..............................................................................137

WinKFPTUser's Guide

Date: 20.10.04


8.1 Functions of Programming Settings Phase Level 1 in Expert Mode ........................................138

8.1.1Function: Loading a PABD ............................................................................................139

8.1.2Function: Loading a P-SGBD ........................................................................................141

8.2 Functions of Programming Settings Phase Level 2 in Expert Mode ........................................143

8.2.1Function: Loading an ECU address ...............................................................................144

8.2.2Function: Loading a Data Set – NAAB File.....................................................................145

8.2.3Function: Loading a Data Set – Program File ................................................................147

8.2.4Function: Loading a Data Set – Data File.......................................................................150

8.2.5Function: Done (Expert Mode) .......................................................................................153

8.3 Functions of the Programming Execution Phase in Expert Mode............................................154

8.3.1Function: Programming a NAAB Data Set .....................................................................155

8.3.2Function: Programming a Program Data Set .................................................................157

8.3.3Function: Programming a Data Data Set .......................................................................159

9 GENERAL FUNCTIONS........................................................................................................161

9.1 Special Functions..................................................................................................................162

9.1.1Function: Reading the UIF.............................................................................................163

9.1.2Function: Reading the ECU Baudrates...........................................................................165

9.1.3Function: Reading and Writing the Calibration Values ................................................... 167

9.1.4Function: VS20/DS2 Mode ............................................................................................168

9.1.5Function: EWS Alignment .............................................................................................169

9.1.6Function: Done..............................................................................................................169

9.2 Diagnosis Functions..............................................................................................................170

9.2.1Function: Displaying the ECU Status .............................................................................171

9.2.2Function: Reading the ECU Identification.......................................................................173

9.2.3Function: Reading the ECU Internal Temperature..........................................................174

9.2.4Function: Done..............................................................................................................175

10 ERROR HANDLING IN WINKFPT.........................................................................................176

10.1 Displaying Errors ................................................................................................................177

10.2 Description and Elimination of Frequently Occurring Errors.................................................178

10.2.1 Errors When Starting WinKFPT..................................................................................178

10.2.2 Errors When Importing Assembly Line Data ...............................................................179

10.2.3 Errors When Entering Flash Data ...............................................................................180

10.2.4 Errors During Data Programming ...............................................................................185

WinKFPTUser's Guide

Date: 20.10.04


List of Figures

Fig. 2-1: Communication architecture in WinKFPT 15Fig. 3-1: Saving a configuration for Expert mode 34Fig. 3-2: Loading a configuration for Expert mode 35Fig. 3-3: Reference configuration in the WINKFPT.INI file 38Fig. 3-4: Reference configuration in the COAPI.INI file 39Fig. 3-5: Reference configuration in the EDIABAS.INI file 39Fig. 4-1: Dialog window in Compile mode 46Fig. 4-2: Result display in Compile mode – compilation OK 47Fig. 4-3: Result display in Compile mode – compilation not OK 47Fig. 4-4: Dialog window for Batch mode (Batch mode monitor) 48Fig. 4-5: Error message when two instances access the same control file 58Fig. 4-6: Error message when the same HW interface+unit is accessed 59Fig. 5-1: Submenu under the main menu option <Import/Export> 64Fig. 5-2: Pull-down menu under the submenu option <Import> 64Fig. 5-3: Selecting the import directory of a configuration of assembly line data 66Fig. 5-4: WDP conflict when importing a configuration of assembly line data 67Fig. 5-5: Selecting the import directory of a configuration of development data 69Fig. 5-6: WDP conflict when importing a configuration of development data 70Fig. 5-7: Selecting the import directory for assembly line data sets 72Fig. 5-8: WDP conflict when importing assembly line data sets 73Fig. 5-9: Importing data sets/program data sets/BSU NAAB files 75Fig. 5-10: Overwriting files during NAAB, data and program file importing 76Fig. 5-11: Importing P-SGBDs 78Fig. 5-12: Overwriting files during P-SGBD importing 79Fig. 5-13: Importing PABDs 80Fig. 5-14: Overwriting files during PABD importing 81Fig. 5-15: Pull-down menu under the submenu option <Export> 82Fig. 5-16: Dialog window for exporting a configuration of assembly line data 83Fig. 5-17: Structure of the target directories for exporting assembly line data 85Fig. 5-18: Dialog window for exporting a configuration of development data 87Fig. 5-19: Prompt asking whether development data should be overwritten during export 88Fig. 5-20: Structure of the target directories for exporting development data 89Fig. 5-21: Deleting assembly line data; message if no assembly line data is present 92Fig. 5-22: Dialog window for deleting assembly line data 93Fig. 5-23: Deleting assembly line data; prompt displayed on clicking "Remove" 94Fig. 5-24: Deleting assembly line data; prompt displayed on clicking "Remove all" 94Fig. 5-25: Selection dialog for HW interface 96Fig. 5-26: Error message displayed when an impermissible choice of HW interface is made 97Fig. 5-27: Error message when the same HW interface+unit is accessed in Dialog mode 97Fig. 5-28: Dialog box for selecting a diagnosis protocol 98Fig. 5-30 Online help of WinKFPT 104Fig. 5-31: Program version and copyright information 105

WinKFPTUser's Guide

Date: 20.10.04


Fig. 6-1: Functional hierarchy phases of WinKFPT 109Fig. 6-2: Function start menu of WinKFPT 110Fig. 7-1: Functions of the programming settings phase in Comfort mode 120Fig. 7-2: Dialog box for entering a ZUSB number in Comfort mode 121Fig. 7-3: Error message - ZUSB number not present in the logistics 122Fig. 7-4: Dialog window for choosing an ECU family, assembly identification number and integration

position 123Fig. 7-5: Dialog box for updating an assembly identification 125Fig. 7-6: Dialog box for entering the vehicle identification number 127Fig. 7-7: Error message displayed when an incorrect vehicle identification number is entered 127Fig. 7-8: Programming execution phase in Comfort mode 130Fig. 7-9: Indication of the number of times the UIF can be programmed 131Fig. 7-10: ECU flash programming in Comfort mode 132Fig. 7-11: Message displayed when ECU programming has been successful 133Fig. 7-12: Message displayed when multiple programming has been successful 133Fig. 7-13: Dialog box displaying the ZB number from the ECU and the current ZB number 134Fig. 7-14: Indication of the number of times the UIF can be programmed 135Fig. 7-15: Message displayed when ZUSB update programming has been successful 136Fig. 7-16: Message displayed when multiple ZUSB update programming has been successful 136Fig. 8-1: Functions of programming settings phase Level 1 in Expert mode 138Fig. 8-2: Dialog box for selecting a PABD 139Fig. 8-3: Dialog box for selecting a P-SGBD 141Fig. 8-4: Programming settings phase Level 2 in Expert mode 143Fig. 8-5: Dialog box for an ECU address 144Fig. 8-6: Dialog box for selecting a NAAB data set 145Fig. 8-7: Dialog box for selecting a program data set 147Fig. 8-8: Error message if references in ECU and program data set do not match up 149Fig. 8-9: Dialog box for selecting a data data set 150Fig. 8-10: Error message if references in ECU and data data set do not match up 152Fig. 8-11: Error message if no ECU address has been entered in Expert mode 153Fig. 8-12: Programming execution phase in Expert mode 155Fig. 8-13: Message displayed following successful ECU flashing programming in Expert mode156Fig. 8-14:Indication of the number of times the UIF can be programmed 157Fig. 8-15: ECU flash programming in Expert mode 158Fig. 8-16: Message displayed following successful ECU flashing programming in Expert mode159Fig. 8-17:Indication of the number of times the UIF can be programmed 159Fig. 9-1: Function menu with the function buttons "Special " and "Diagnosis " 161Fig. 9-2: Function menu for the special functions 162Fig. 9-3: Display dialog for the Special function "Read UIF" 164Fig. 9-4: Error message displayed when you call "ECU baudrates " 166Fig. 9-5: Submenu for reading and writing the calibration values 167Fig. 9-6: Error message displayed when you call "VS20 Mode" or "DS2 Mode" 168Fig. 9-7: Message displayed when you call "EWS Alignment " 169Fig. 9-8: Menu for the diagnosis functions 170

WinKFPTUser's Guide

Date: 20.10.04


Fig. 9-9: Display dialog for the ECU status 172Fig. 9-10: Display dialog for the ECU identification 173Fig. 9-11: Display dialog for the ECU internal temperature 174Fig. 10-1: Error display window in WinKFPT 177

WinKFPTUser's Guide

Date: 20.10.04


List of Tables

Table 2-1: Operating modes of WinKFPT 13Table 3-1: System requirements of WinKFPT 16Table 3-2: Directories and files of WinKFPT 21Table 3-3: Initialization files of WinKFPT 23Table 3-4: Configuration in COAPI.INI 25Table 3-5: Configuration in WINKFPT.INI 31Table 3-6: Configuration in EDIABAS.INI 37Table 4-1: Calling parameters of WinKFPT 41Table 4-2: Status displays of WinKFPT 45Table 4-3: Status displays in the Batch mode monitor 49Table 4-4: Contents of a control file for the Batch mode in Comfort mode 52Table 4-5: Contents of a control file for the Batch mode in Expert mode 54Table 5-1: Import files 65Table 6-1: Overview of the job data in the operating modes 111Table 7-1: Function phases of Comfort mode 119Table 8-1: Function phases of Expert mode 137

WinKFPTUser's Guide

Date: 20.10.04


1 FOREWORD

1.1 Using this User's Guide and the Online Help

The User's Guide and the online help are identical. Whenever updates of WinKFPT are released, theUser's Guide and online help will be updated at the same time.

Publication and distribution of the User's Guide are the responsibility of BMW.

WinKFPTUser's Guide

Date: 20.10.04


1.2 About This User's Guide

This User's Guide has been divided into the following chapters:

Chapter Description

2 Introduction Brief description, intended use, operating modes,programming possibilities and architecture of WinKFPT.

3 First Steps System requirements, installation, list structure andconfiguration of WinKFPT.

4 Starting WinKFPT Description of the calling parameters and starting thevarious operating modes of WinKFPT.

Description of the flash sequence in Batch mode.

5 WinKFPT's Main Menu The following chapters (5-6) describe how to use WinKFPTin Dialog mode.

Menu options of the main menu bar of WinKFPT and theirsubmenus

6 Functions of WinKFPT Activating Comfort mode and Expert mode.

7 Function Phases in Comfort Mode Control functions in Comfort mode for flash programming acontrol unit.

8 Function Phases in Expert Mode Control functions in Expert mode for flash programming acontrol unit.

9 General Functions Special and diagnostics functions

10 Known control and configuration errors

WinKFPTUser's Guide

Date: 20.10.04


1.3 Conventions Used

This User's Guide uses the following typographical conventions:

Example Description

DEFAULT.INI Names written in uppercase letters and italics denotefile names.

"Import file sets" Names written in italics and set in quotation marksdenote a window or dialog box in the program.

12345 Names written in italics but not set in quotation marksdenote entries in input and/or display fields.

"OK" Names written in bold type and set in quotation marksdenote buttons, radio buttons, check boxes, input fieldsor display fields.

<<ECU not responding>> Words set in double angle brackets denote messagesdisplayed to the user.

<Configuration> Words underscored and set in single angle bracketsdenote main-menu and submenu options.

"Operating modes" Words underscored and set in quotation marks denotechapter titles.

WinKFPTUser's Guide

Date: 20.10.04


2 INTRODUCTION

2.1 About WinKFPT

WinKFPT is a program for flash programming (program and data) electronic control units (ECUs)used in the automotive industry.

WinKFPT was originally conceived purely as a reference tool for verifying the programmability ofcontrol units in the course of program and data programming.

Thanks to continuous expansion of its functionality, WinKFPT is now used as a development tool forsuppliers of BMW who are involved in the development of control units.

The possibilities opened up by the Batch mode and the multiple instancing capability of WinKFPThave in the meantime enabled the range of application of the program to be expanded to coverproduction and service.

WinKFPT is the first tool that uses the COAPI functions for a boot sector update (BSU), and thereforefacilitates ECU updates (exchange of boot sectors, programs, data) that go beyond the boundaries ofECU families. This reduces the need to exchange control units in e.g. the Service Department.

As of Version 4.6.0, WinKFPT uses the import/export functionality of the COAPI to managedevelopment and tool-relevant data, ECU-specific and general logistics files and assembly line datasets for saving and loading development configurations in order to improve error tracing duringdevelopment and flash verification of the control units.

2.2 Possibilities in WinKFPT

2.2.1 Multiple Instancing Capability

To shorten programming times by means of parallel programming of several control units via variousHW interfaces or diagnosis channels, it is possible to call a separate WinKFPT instance for each HWinterface connected that can be initialized via the EDIABAS interface.

WinKFPTUser's Guide

Date: 20.10.04


2.2.2 Operating Modes

WinKFPT has two main operating modesDialog modeBatch mode

and one special operating modeCompile mode.

The table below contains a brief description of each of WinKFPT's operating modes.

Operating mode Description

Dialog mode = Standard operating mode – all ECU flash programming entries are made bythe user in Dialog mode.

Batch mode Can be started from Dialog mode or by being called with appropriate callingparameters.The programming of ECUs is configured and started by means of specificcontrol files.

Compile mode This operating mode is started by means of a special calling parameter and isused only to translate a PABD in source code (XXX.IPS).The object code file (XXX.IPO) of the PABD is then located followingtranslation as a resident file in the PABD directory "<root>\sgdat".

Table 2-1: Operating modes of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


2.2.3 Programming of ECUs in Dialog Mode

There are three possibilities for flash programming a control unit using the Dialog mode of WinKFPT.

The two possibilities in Comfort mode:

1. Entry or selection of the assembly identification number (ZUSB No.), selection of any number ofintegration positions offered for the ZUSB No., entry of the vehicle identification number (VIN)when a UIF is written, and subsequent flash programming of the control unit or control units inComfort mode.

2. Selection of a control unit family and of any number of integration positions offered for thisfamily, and subsequent updating of the control unit or control units in Comfort mode to the latestassembly identification within the respective series of compatible hardware releases. If atransition between non-compatible hardware releases is possible by means of a boot sectorupdate, updating of the assembly identification code goes beyond just changing the hardware,actually potentially involving changing the ECU family.

One possibility in Expert mode:

3. Selection of the necessary PABDs, P-SGBDs and data set names and subsequent flashprogramming of the control unit in Expert mode.

In addition to be able to flash program control units, a number of special and diagnostics functions,such as "Read UIF" or "ECU Status" are supported.

2.2.4 Programming of ECUs in Batch Mode

Batch mode is used to flash program any number of control units one after the other.

WinKFPT can be started from an external application in Batch mode; in this case, flash programmingof the control units is initiated by means of a control file.

WinKFPTUser's Guide

Date: 20.10.04


2.3 Architecture of WinKFPT

The following diagram shows the architecture of communication between two WinKFPT instancesthat have been called from an external application:

PABD

Application

COAPI

BMW-Logist ic files

WinKFPT (1. Instance)

Diagnosis-Bus

EDIABAS-Runtime

HW-Interface I

EDIABAS-API(1.Instance)

P-SGBD

COAPI

WinKFPT (2. Instance)

Diagnosis-Bus

EDIABAS-Runtime

HW-Interface II

EDIABAS-API(2.Instance)

Fig. 2-1: Communication architecture in WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


3 FIRST STEPS

3.1 System Requirements of WinKFPT

To be able to flash program control units with WinKFPT, the system requirements listed in the tablebelow must be met:

Requirement Remark

Computer PENTIUM II processor or higher with 64 MB RAMand 50 MB of free memory

Operating system MS-Windows NT Version 4.0 or MS-Windows XP

Built-in diagnosis interface ADS, ADS-OBD, EDICcard, EDICcard2, EDICcardC,CANcard, CAN / Vector, Most / Optolyzer,Most / PC card or Funk / MDA

Built-in EDIABAS interface Version 6.0.2 or higher

Control unit Programmable

Table 3-1: System requirements of WinKFPT

3.2 Installing WinKFPT

WinKFPT is installed by starting WINKFPT32.EXE from the installation CD or disk.You are prompted to enter the target directory (<root>) in which the software is to be installed.At the end of the installation routine, a link to the program is created on the desktop and a programgroup for UNINSTALL also created.

In Version 1.4 and higher, all configuration files required are available in rudimentary form followinginstallation, so that WinKFPT will run up without any problem.You can then import the assembly line data (Comfort mode) or PABD and P-SGBD files and data setsand program data sets (Expert mode) you want online using the import functionality of WinKFPT (see"5.2 Import/Export Menu"REFMERGEFORMAT).

WinKFPTUser's Guide

Date: 20.10.04


3.3 Directory Structure of WinKFPT

WinKFPT is installed in the directory you specify during installation.

The installation directory <root> contains the following subdirectories,the starting directory of WinKFPT:• \<root>\BIN

the workong directories of WinKFPT:• \<root>\CFGDAT• \<root>\DATA• \<root>\FORMAT• \<root>\SGDAT• \<root>\WORK

The installation directory contains two files you will need if you want to uninstall WinKFPT at somepoint in the future:• INSTALL.LOG, the file containing the uninstall information• UNWISE.EXE, the WinKFPT uninstaller.

Directory Contents

This directory contains all necessary program files (EXE, DLL) and the

initialization/configuration file WINKFPT.INI.

It also serves as a working directory for storing error files and other temporary

files created while the program is running (e.g.

INNENTMP_INTERFACE_unit.OUT).

CABIGER.DLL Coding sequence interpreter –

localization support DLL (German)

CABUS.DLL Coding sequence interpreter –

localization support DLL (English)

WINKFPT.INI Configuration file for WinKFPT

WINKFPT32.EXE Executable for WinKFPT

\<root>\BIN

WINKFPT32.HLP Online help for WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


Directory Contents

Error file.

Every error file refers to an instance

of WinKFPT.

The file name incorporates the HW

interface identifier and unit identifier

to enable assignment to the relevant

instance.

INTERFACE HW interface

identifier

ERROR_INTERFACE_unit.LOG

As of Version 4.6.0, the installation

directory is only the default directory for

storing error files.

You can select/set any directory you

want as the storage directory by means

of the main menu option

<Configuration>.

_unit Unit identifier (_, A,

B, C, ...)

*.OUT Temporary files created during

program run

Directory contains the initialization files:

INPA.INI Initialization file for the coding sequence

interpreter.

The contents of this file are laid down at the time

of delivery of WinKFPT and are not allowed to be

used by the user.

For further information, see system description of

the COAPI.

COAPI.INI Configuration for the coding application interface

Directory also contains the text files for error messages:

COAPIERR.TXT Text file for COAPI error messages

\<root>\CFGDAT

EDIERROR.TXT Text file for EDIABAS error messages

Directory contains the programming data files available in Expert mode.

*.PAF Program exchange files

*.DAF Data exchange files

\<root>\DATA\DEVELOP

*.BAF NAAB exchange files

WinKFPTUser's Guide

Date: 20.10.04


Directory Contents

*.0PA Data set files for program

*.0DA Data set files for data

*.0BA Data set files for NAAB

Directory contains the logistics files for ECU flash programming. These must

always be available. The files are loaded by importing an assembly line data

set:

KFCONFxx.DA2 Contains all ECU members and the associated

names of the description and ECU-specific

logistics files and a data set identifier for each of

these ECU members.

As of Version 4.6.0, only those ECU members of

the imported, valid WDPs are contained.

HWNR.DA2 Contains all the hardware numbers every

assigned for all ECUs

As of Version 4.6.0, only those hardware

numbers for ECU families of the imported, valid

WDPs are contained.

NPV.DAT Logistics file for retrofit actions in the HO. Of no

relevance to WinKFPT.

Special configuration files that must be present if required:

\<root>\DATA\GDATEN

INFO.GER Contains the integration position of an ECU

member in plain text for user selection in

WinKFPT, e.g. "Passenger side, rear".

In general, these integration position texts only

exist for ECUs that have different ECU members,

i.e. integration position, but belong to the same

ECU family.

<Optional> Only for Comfort mode for selection

of the integration position (= implicit input of the

ECU address when the same control unit type is

installed more than once in the same car)

WinKFPTUser's Guide

Date: 20.10.04


Directory Contents

PRGIFSEL.DAT Contains variable assignments of ECU family to

HW interface and diagnosis protocol.

<Optional> Only for Batch mode for flash

programming several control units one after the

other.

SGIDC.AS2 Contains the authentication codes of all ECUs for

authentication level "3".

<Optional> Only for control units with

authentication.

SGIDD.AS2 Contains the authentication codes of all ECUs for

authentication level "4".

<Optional> Only for control units with

authentication.

HISTORIE.BSU Contains the necessary specifications for

determining whether a boot sector update is

possible for all control units affected.

<Optional> Facilitates a boot sector update for

certain control units.

Each of these directories contains the ASCII programming data for an ECU

family <EcuFam>. These directories are used in Comfort mode.

Note: all the logistics files of an ECU family must be present in each case.

These are:

<EcuFam>.DAT Contains all current assembly identification

numbers of an ECU family.

<EcuFam>.HIS Contains all compatible assembly identification

numbers ever assigned for an ECU family in one

or more series.

\<root>\DATA\<EcuFam>

<EcuFam>.HWH Contains the history of compatible hardware

numbers of an ECU family in one or more series.

WinKFPTUser's Guide

Date: 20.10.04


Directory Contents

\<root>\DATA\KONV Directory contains the compressed programming data in MoDiC/DIS format.

\<root>\DATA\KONV.TMP Temporary directory for storing programming data files while WinKFPT is

running through several instances:

\<root>\DATA\KONV.TMP2,

\<root>\DATA\KONV.TMP3 etc...

Directory contains the header files and PABDs in source code and/or in

compiled code.

*.IPS PABDs in source code

*.IPO PABDs in compiled code

\<root\SGDAT

The source code of the flash sequence description files (PABDs) is available in

the INPA script language.

Files can be available in source code or in compiled form; the compiled form is

generated from the source code by means of the CABI compiler.

Since the functionality of the CABI compiler is integrated in the COAPI,

WinKFPT can process both forms of a PABD.

\<root>\WORK Working directory for COAPI and WinKFPT for storing trace and other

temporary files.

The working directory can be changed by means of the COAPI.INI file. The

working directory must be created because WinKFPT will otherwise not start.

Table 3-1: Directories and files of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


3.3.1 Configuration of the basic directory for the working directories of WinKFPT

By means of the main menu option "Configuration" (see “5.4 Configuration Menu”) the basic directoryfor the working directories can be changed at any time.

This means it is possible for several instances of WinKFPT to work with one central set of workingdirectories placed anywhere in a network environment.

A new basic directory is only accepted if below there are all working directories containing theminimum set of files as they are provided after a first installation of WinKFPT.Otherwise an error message occurs and the actual valid basic directory is not changed.

Note:It is possible that existing programming settings are not valid any longer after a change of the workingdirectories.

WinKFPTUser's Guide

Date: 20.10.04


3.4 Configuring WinKFPT

WinKFPT is configured by means of the following initialization files:

Configuration file Contents

COAPI.INI Configuration for the coding application interface

WINKFPT.INI Configuration for WinKFPT

EDIABAS.INI Configuration for the diagnosis HW interface

Table 3-1: Initialization files of WinKFPT

3.4.1 Configuration in COAPI.INI

The initialization file "<root>\CFGDAT\COAPI.INI" 1 serves to configure directories, file names andsystem data for the COAPI core functions. The following sections and entries are of importance toWinKFPT:

Configuration entry Possible setting Default Description

[Pfadangaben] Paths for configuration files, data and trace files are set in this section.

WORKING_DIR Complete path or

relative to

<root>1

<root>\WORK1 The entry specifies the directory

that is used for COAPI trace

files and for temporary files.

ERROR_TEXTE Complete path or

relative to

<root>1

<root>\CFGDAT1 The entry specifies the directory

in which the COAPI error text

file is located.

GENERAL_KF_DATA_PATH Complete path or

relative to

<root>1

<root>\DATA1 The entry specifies the directory

in which the programming files

are located.

[Kennfeldprog] This section contains entries that are required specifically for engine

characteristics map programming.

1 <root>: installation directory of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


Configuration entry Possible setting Default DescriptionSERIENNUMMER 5-digit number 12345 The entry specifies the value

that is entered as the serial

number in the user info field.

KUNDENNUMMER 5-digit number 11111 The entry specifies the value

that is entered as the customer


KM Max. 2-digit

number

0 The entry specifies the value

that is entered as the mileage

(in km) in the user info field.

ZBNUMMER3 7-digit number 0000000 The entry specifies the value

that is entered as the assembly

identification number in the user

info field.

SWNUMMER3 7-digit number 0000000 The entry specifies the value

that is entered as the software


TYPNUMMER3 7-digit number 0000000 The entry specifies the value

that is entered as the type test


AEINDEX3 2-digit number 00 The entry specifies the value

that is entered as the change

index in the user info field.

[Setup] In this section, you set which form of the PABD is to be displayed for

selection in WinKFPT.

3 The entry is only evaluated if the switch "EXPERT_MIT_AIF" in the file WINKFPT.INI is set to ON (Expert

mode with UIF writing).

WinKFPTUser's Guide

Date: 20.10.04


Configuration entry Possible setting Default DescriptionCabdFormat IPS

IPO

COM

IPO The entry defines whether the

COAPI (as part of WinKFPT) is

to use PABDs as source files or

as compiled files. This entry is

however irrelevant because it is

cancelled by the corresponding

entry in WinKfpt.ini or the

setting in the Configuration

dialog.

IPS PABDs as source

files

IPO PABDs as compiled

files

COM WinKFPT compiles

selected *.IPS files

and creates *.IPO

files. Compiling

is started when PABD

file is selected in

Expert mode.

BsuActive ON

OFF

ON The flag influences how theCOAPI function behaves:coapiKfCheckBsuPossibleD2

When BsuActive=OFF, thefunction never returns thename of a NAAB files, i.e. aboot sector update cannot beexecuted, even if"historie.bsu" says it wouldbe possible.

Setting of the default or ofthe flag in accordance withthe configuration entry in"COAPI.INI" is performed inthe COAPI function:"coapiKfInit ()".

Table 3-1: Configuration in COAPI.INI

WinKFPTUser's Guide

Date: 20.10.04


WinKFPTUser's Guide

Date: 20.10.04


3.4.2 Configuration in WINKFPT.INI

The initialization file "<root>\BIN\WINKFPT.INI" 2 is used to configure characteristics of WinKFPT.The following sections and entries are of importance to WinKFPT:

Configuration entryPossiblesetting

Default Description

[Einstellungen] Paths for configuration files, data and trace files are set in this

section.

WindowPosition -- 0,1,-1,-1,

-1,-1,0,0,

643,424

The entry saves the last window

size of WinKFPT when the

program is exited. The program

then starts with the same

coordinates when restarted.

SPRACHE ger

eng

ger The entry defines the language

for WinKFPT. Options: German

(ger) and English (eng).

U_PROG ON

OFF

ON The entry specifies whether the

programming voltage is

switched ON or OFF during

flash programming.

SCHNELLE_BAUDRATE ON

OFF


fast baudrate is used (ON) or

not (OFF) during flash

programming.

ANZEIGE_U_PROG ON

OFF


value of the programming

voltage is displayed (ON) or not

(OFF) during flash

programming.

EXPERT_MIT_AIF ON

OFF


UIF is also programmed (ON) or


programming in Expert mode.

2 <root>: installation directory of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04



Default Description

KOMFORT_MIT_AIF ON

OFF




programming in Comfort mode.

AIF_SCHREIBEN_NACH_DATEN ON

OFF



not (OFF) during data

programming in Comfort or

Expert mode.

AIF_SCHREIBEN_NACH_PROGRAMM ON

OFF



not (OFF) during program


Expert mode.

API_TRACE 0 – 7

OFF (= 0)

ON (= 1)

1 The entry specifies the trace

level of the API traces of

EDIABAS during flash

programming. Trace level 0

means that no traces are

generated.

IFH_TRACE 0 – 3

OFF (= 0)

ON (= 1)

1 The entry specifies the trace

level of the IFH traces of

EDIABAS during flash

programming. Trace level 0

means that no traces are

generated.

PROGRAMM_ERZWINGEN ON

OFF

OFF The entry specifies whether,

during flash programming in

Comfort mode, a program is

also programmed when actually

only data programming would

be necessary.

TEST_CHECKSUMME ON

OFF


checksum is validated (ON) or

not (OFF) after programming of

the data.

WinKFPTUser's Guide

Date: 20.10.04



Default Description

CabdFormat IPS

IPO

(COM)

IPO The entry defines whether

WinKFPT is to use PABDs as

source files or as compiled files.

IPS PABDs as source

files


files

COM stands for compile mode.

However, it does not

have to be set manually

in the Ini file, rather it

is set temporarily and

automatically by the

calling parameter "-C".

ErrorLogPath any path .\ Storage directory for the

ERRORn.LOG file

ExpertKonfPath any path C:\

Diagprog

Base directory for export of a

configuration of development

files (Expert mode).

KomfortKonfPath any path C:\NFS-

Backup

Base directory for export of a

configuration of assembly line

data (Comfort mode).

CoapiSearchPath any path ..\ Base directory for working

directories of WinKFPT

[HW-Interface ] In this section, those HW interfaces are entered that can be

switched between online while WinKFPT is being used.

WinKFPTUser's Guide

Date: 20.10.04



Default Description

Interfaces are to be defined using the following syntax:

[Description] = [HW interface identifier]

Example:

K-Line / EDIC=EDIC

K-Line / ADS-OBD=STD:OBD

CAN / EDIC=EDICC

CAN / Vector=STD:CAN

Most / Optolyzer=STD:MOSTO

Most / PC card=STD:MOSTP

You can select any string of letters for [Description].

The texts entered as the [Description] are displayed to the user in a HW interface selection list when the

menu option Communication �

HW Interface is selected, (e.g. K-Line / EDIC).

[HW interface identifier] is used internally in the WinKFPT program.

The identifier is defined and must be known to "EDIABAS" so that "EDIABAS" can also initialize the HW

interface.

[Expert-Modus-Konfiguration] In this section, the current configuration in Expert mode is

saved by the user (if necessary) when the program is exited.

When the program is restarted and Expert mode reselected,

the user is then able to reload this configuration.

KF_HW_INTERFACE HW interface

identifier

empty Saved setting of the HW

interface in Expert mode.

Interface can be selected by

means of the menu option

Communication �

HW

Interface.

KF_HW_INTERFACE_UNIT _, A, B, C, D, E empty Saved setting of the HW

interface unit in Expert mode.

Interface unit can be selected by

means of the menu option

Communication �

HW

Interface.

WinKFPTUser's Guide

Date: 20.10.04



Default Description

KF_DIAG_PROT Identifier of the

diagnosis

protocol

empty Saved setting of the diagnosis

protocol in Expert mode; in the

case of a P-SGBD file that

supports several diagnosis

protocols,

the diagnosis protocol can be

selected by means of the menu

option Communication �

Diagnosis protocol.

KF_PSGBD P-SGBD file

name

empty Saved setting of the P-SGBD

file name in Expert mode.

P-SGBD file can be selected by

pressing the function key Expert

Mode �

P-SGBD.

KF_PABD PABD file name empty Saved setting of the PABD file

name in Expert mode.

PABD file can be selected by

pressing the function key Expert

Mode �

PABD.

KF_SG_ADR ECU address empty Saved setting of the ECU

address in Expert mode.

ECU address can be selected

by pressing the function key

Expert Mode �

ECU Address.

KF_DATEN_DATEI Data file

name

empty Saved setting of the data set file

for data in Expert mode.

Data set file for data can be

selected by pressing the

function key Expert Mode �

Data File.

KF_PROGRAMM_DATEI Program file

name


for program in Expert mode.

Data set file for program can be

selected by pressing

the function key Expert Mode �

Program File.

WinKFPTUser's Guide

Date: 20.10.04



Default Description

KF_NAAB_DATEI NAAB file

name


for NAAB in Expert mode.

Data set file for NAAB can be

selected by pressing

the function key Expert Mode �

NAAB File.

N.B.: The entries in this section must be made by the user only in WinKFPT and not using Editor!

Table 3-1: Configuration in WINKFPT.INI

To save start information, WINKFPT.INI can, during the import and export of configurations, containentries that are generated automatically by the program and that are not allowed to be changed orpreset by the user.

WinKFPTUser's Guide

Date: 20.10.04


3.4.3 Configuration for Expert Mode

The user has the option of saving and also of reloading a configuration in Expert mode if necessary.

A configuration is set in Expert mode by means of the free selection of the following job data andsettings:

• HW interface and unit• Diagnosis protocol• P-SGBD• PABD• Control unit address• Data file• Program file• BSU NAAB file

HW interface and unit is selected by means of the menu option Communication � HW Interface inExpert mode (see "5.3.1 Selecting (Choosing) a HW Interface").

Diagnosis protocol is selected by means of the menu option Communication � Diagnosis Protocolin Expert mode (see "5.3.2 Selecting (Choosing) a Diagnosis Protocol").

P-SGBD is selected by pressing the function key "P-SGBD" in Expert mode (see "8.1.2 Function:Loading a P-SGBD").

PABD is selected by pressing the function key "PABD" in Expert mode (see "8.1.1 Function: Loadinga PABD").

Control unit address is entered by pressing the function key "ECU Address" in Expert mode (see"8.2.1 Function: Loading an ECU address").

Data file is selected by pressing the function key "Data File" in Expert mode (see "8.2.4 Function:Loading a Data Set – Data File").

Program file is selected by pressing the function key "Program File" in Expert mode (see "8.2.3Function: Loading a Data Set – Program File").

NAAB file is selected by pressing the function key "NAAB File" in Expert mode (see "8.2.2

WinKFPTUser's Guide

Date: 20.10.04


Function: Loading a Data Set – NAAB File").

WinKFPTUser's Guide

Date: 20.10.04


3.4.3.1 Saving a Configuration for Expert Mode

If you have activated Expert mode at least once while using WinKFPT, you have the option beforeexiting WinKFPT of saving the current settings you have made in Expert mode so that you can callthem up again the next time you start the program.

To this end, the following dialog box appears before WinKFPT is exited:

Fig. 3-1: Saving a configuration for Expert mode

The figure shows a complete set of configuration settings as an example.

The configuration can be saved by clicking "OK" or discarded by clicking "Cancel" .

The configuration is saved in WINKFPT.INI in the [Expert mode configuration] section (see "3.4.2Configuration in WINKFPT.INI").

WinKFPTUser's Guide

Date: 20.10.04


3.4.3.2 Loading a Configuration for Expert Mode

If a configuration with at least one entry exists - either following starting of the program from theconfiguration file WINKFPT.INI or from a previous entry in Expert mode - this configuration is offeredto the user for loading when the user first enters or re-enters Expert mode.

The following dialog box appears:

Fig. 3-1: Loading a configuration for Expert mode

The configuration can be adopted by clicking "OK" or discarded by clicking "Cancel" .If the PABD format of the PABD does not match up with the format currently set, the user is informedof this and he can have the format changed automatically.

If the configuration is adopted, the corresponding status displays in the main menu window ofWinKFPT are updated (see "4.2 Status Displays of WinKFPT").If the configuration is adopted, the scope of the job data in the configuration determines the functionlevel of Expert mode to which is switched (see "8 Function Phases in Expert Mode").

3.4.3.3 Deleting a Configuration for Expert Mode

WinKFPTUser's Guide

Date: 20.10.04


In contrast to configuration loading, it is also possible to save a totally empty configuration on exitingthe program and thus to delete all the entries in the [Expert mode configuration] section ofWINKFPT.INI.

To delete configuration settings, perform the following steps:• Start WinKFPT.• Start Expert mode by clicking "Expert Mode" .• Click "Cancel" in the "Load last configuration?" dialog box.• Exit WinKFPT by selecting End � Exit .• The dialog box "Save last configuration?" then displays an empty configuration for saving. Save this

empty configuration by clicking "OK" .

WinKFPT is exited and the configuration entries in the [Expert mode configuration] section ofWINKFPT.INI are deleted.

The next time WinKFPT is started and Expert mode called, the program does not offer anyconfiguration settings for loading.

WinKFPTUser's Guide

Date: 20.10.04


3.4.4 Configuration in EDIABAS.INI

The initialization file "<ediabas>\CFGDAT\EDIABAS.INI"4 contains the configuration for thediagnosis HW interface.


Default Description

[Configuration] This section contains configuration entries for EDIABAS.

Interface EDIC The identifier entered is

initialized as the default HW

interface when WinKFPT is

started without calling

parameters.

Table 3-1: Configuration in EDIABAS.INI

4 <ediabas> = installation directory for EDIABAS

WinKFPTUser's Guide

Date: 20.10.04


3.5 Reference Configuration of WinKFPT

The following figures show the default configuration for WinKFPT after reinstallation:

Fig. 3-1: Reference configuration in the WINKFPT.INI file

[Einstellungen]

; allgemeine EinstellungenWindowPosition=0,1,-1,-1,-1,-1,0,0,643,424U_PROG=ONSCHNELLE_BAUDRATE=ONANZEIGE_U_PROG=OFFTEST_CHECKSUMME=ONPROGRAMM_ERZWINGEN=OFF

; Aif schreibenAIF_SCHREIBEN_NACH_DATEN=OFFAIF_SCHREIBEN_NACH_PROGRAMM=OFFEXPERT_MIT_AIF=OFFKOMFORT_MIT_AIF=OFF

; TraceAPI_TRACE=ONIFH_TRACE=ON

[HW-Interface]K-Line / ADS=ADSK-Line / EDIC=EDICK-Line / ADS-OBD=STD:OBDCAN / EDIC=EDICCCAN / Vector=STD:CANMost / Optolyzer=STD:MOSTOMost / PC-Karte=STD:MOSTPFunk / MDA=STD:FUNK

WinKFPTUser's Guide

Date: 20.10.04


Fig. 3-2: Reference configuration in the COAPI.INI file

Fig. 3-3: Reference configuration in the EDIABAS.INI file

; Initialisierungsdatei fuer COAPIKF-Funktionen[Pfadangaben]ERROR_TEXTE = ..\CFGDATWORKING_DIR = ..\WORK; genereller Pfad fuer Kennfeld-DatenGENERAL_KF_DATA_PATH = ..\DATA

[Kennfeldprog]TEMP_DAT_FILE_DEFAULT_NAME = KFLISTE.DAT

; DatenSERIENNUMMER = 42324KUNDENNUMMER = 12321KM = 0ZBNUMMER = 0000000SWNUMMER = 0000000TYPNUMMER = 0000000AEINDEX = 00

; SG Dateien komprimieren; 1 -> Dateien werden immer komprimiert (Für Datenupdate über Netz; während Applikation läuft)

Sektion [Configuration]

;-------------------------------------------------------

; Interface

; Description : Connected diagnosis interface

; Default = EDIC

Interface=STD:OBD

WinKFPTUser's Guide

Date: 20.10.04


4 STARTING WINKFPT

You can start WinKFPT without calling parameters or with certain combinations of various callingparameters.

The calling parameters are used to set WinKFPT to a desired operating mode or to preset certainoperating parameters in WinKFPT to desired values immediately upon the program being started.

4.1 Calling Parameters of WinKFPT

The following calling parameters can be set in WinKFPT:

Parameter name Parameter value Description Default

-RUN - Starts WinKFPT immediately in Batch

mode.

Example:

winkfpt32 –RUN

-

-BATCH= <Control file> Path and name of a control file for Batch

mode.

Example:

winkfpt32 –RUN –BATCH=update_ek928

"<root>\bin\win

kfpt.ctl"

-INTERFACE= <HW interface> Defines the HW interface (e.g. ADS,

EDIC) that is to be active following

starting of WinKFPT.

It can be altered at a later point in Dialog

mode by means of the main menu option

"HW Interface".

Example:

winkfpt32 –INTERFACE=STD:OBD

Setting in

"EDIABAS.INI"

WinKFPTUser's Guide

Date: 20.10.04


Parameter name Parameter value Description Default

-UNIT= <Interface unit> Defines the unit (_, A, B, C, ....., Z) that is

to be active following starting of

WinKFPT.

It can be altered at a later point in Dialog

mode by means of the main menu option

"HW Interface".

Example:

winkfpt32 –UNIT=A

"_"

-WITH_MOSTFIREWALL= <ON/OFF> Relays the value to the PABD

as the parameter

"WITH_MOSTFIREWALL".

Example:

winkfpt32 –WITH_MOSTFIREWALL=ON

"OFF"

-TESTER_ID= <Hex value> Relays the value to the PABD

as the parameter "TESTER_ID".

Example:

winkfpt32 -TESTER_ID=FA

"F1"

-C <PABD file name> Compiles an IPS file (PABD source file).

CabdFormat=COM does not have to be

set in WinKfpt.ini and coapi.ini.

Example:

winkfpt32 –C 16ek928

Table 4-1: Calling parameters of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


4.1.1 Type Description of the Calling Parameters of WinKFPT

The calling parameters of WinKFPT can be divided into 3 type groups:

1. Parameters for setting the operating mode2. Parameters for Batch mode only3. General parameters for Batch and Dialog modes

The parameters for setting an operating mode are:

• -C starts WinKFPT in Compile mode – no other parameter is permissible!

• -RUN starts WinKFPT in Batch mode

• no par. If neither –C nor –RUN is specified as the calling parameter WinKFPT starts in Dialogmode, which is the standard operating mode for users employed in control unitdevelopment.

The following parameter is used for Batch mode only:

• -BATCH

The general parameters for Batch and Dialog modes are:

• -INTERFACE• -UNIT• -WITH_MOSTFIREWALL• -TESTER_ID

WinKFPTUser's Guide

Date: 20.10.04


4.2 Status Displays of WinKFPT

The following status displays are displayed in the main menu window following user inputs or duringautomatic routines such as ECU flash programming or importing of files:

Status display Description

ECU address The control unit address is only explicitly displayed if the standard description files

are used for programming the control unit in question.

No ECU address can be displayed for control units with "older" description files. The

following text appears instead:

PABD uses an internal address

This text is displayed:� following selection of the description files and entry of the ECU address in Expert

mode (Dialog mode).� following selection of an integration position and entry of the ECU address in

Comfort mode (Dialog mode).� during flash programming of an ECU in Batch mode.

Integration position There are control units for multiple integration that belong to the same ECU family

but that have different addresses, e.g. control units for seat occupancy detection.

To improve user friendliness, the software enables you to select a control unit not by

means of the ECU address, rather by means of meaningful texts that describe the

integration position of the control unit (e.g. Passenger seat, rear left).

These user-selection texts are taken from the file INFO.GER

These texts are displayed:� following selection of an integration position in Comfort mode (Dialog mode).

WinKFPTUser's Guide

Date: 20.10.04



Vehicle identification

number

In the Comfort mode of Dialog mode, the vehicle identification number is displayed

only if an entry is made in the UIF (user info field) following flash programming.

The VIN is displayed:� following selection of an integration position in Comfort mode (Dialog mode).� during flash programming of an ECU in Batch mode (the vehicle identification

number from the control file for Batch mode is displayed).

ZB number The ZB number (assembly identification number) defines the program data set and

data data set to be programmed for a control unit.

The ZB number is displayed:� in Expert mode (Dialog mode) if an entry would be made in a UIF (user info field)

following flash programming. The assembly identification number from the

configuration file COAPI.INI is displayed.� following selection of an integration position in Comfort mode (Dialog mode).� during flash programming of an ECU in Batch mode.

HW number The hardware number defines the programmed program data set of a control unit.

The hardware number is displayed:� during flash programming of an ECU in Expert mode (Dialog mode).� during flash programming of an ECU in Comfort mode (Dialog mode).� during flash programming of an ECU in Batch mode.

HW interface The default HW interface or the one selected is always displayed.

Interface unit The default interface unit or the one selected is always displayed.

Diagnosis protocol The default diagnosis protocol or the one selected is always displayed if the ECU

facilitates communication with at least 2 diagnosis protocols.

WinKFPTUser's Guide

Date: 20.10.04



PABD Flash sequence description file

The file is displayed:� following selection in Expert mode (Dialog mode).� following selection of an integration position in Comfort mode (Dialog mode).� during flash programming of an ECU in Batch mode.� P-SGBD Control unit description file for programming

The file is displayed:� following selection in Expert mode (Dialog mode).� following selection of an integration position in Comfort mode (Dialog mode).� during flash programming of an ECU in Batch mode.

Progress bar Informs you in percentage terms of the progress of an automatic process that takes

some time to be executed (0 % - 100 % in 1 % increments).

The progress bar is displayed during:� flash programming (program and data).� import/export of assembly line data sets, data files or description files.

Boot sector update Is displayed at all times and informs you of whether the boot sector update is

ACTIVATED or NOT ACTIVATED.

The setting can be changed at any time by means of the main menu option

"Configuration".

Table 4-1: Status displays of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


4.3 Starting WinKFPT in Compile Mode

There is only one call that can be used to start WinKFPT in Compile mode:

winkfpt32 –C <filename>

The file name of the PABD (= IPS file) must be entered without the path and file extension, otherwiseWinKFPT is aborted and an error message is displayed that must be acknowledged.CabdFormat=COM does not have to be set manually in WinKfpt.ini and coapi.ini for compilation. Thisis done automatically and temporary by WinKFPT.

The PABD to be compiled, e.g. 10GD8600.IPS, must be present in the "<root>\sgdat" directory.

The following dialog window appears once WinKFPT has been started:

Fig. 4-1: Dialog window in Compile mode

If you click "Cancel ", WinKFPT is exited without any further reaction.

If you click "OK", the PABD in question is compiled and the result of this compilation displayed in amessage box.

In the event of an error, an error report is created in the form of the file CABI.ERR saved in the<root>\bin directory. This report contains the errors that have occurred during compilation.

WinKFPTUser's Guide

Date: 20.10.04


Result display when compilation has been successful:

Fig. 4-2: Result display in Compile mode – compilation OK

Result display when compilation has not been successful:

Fig. 4-3: Result display in Compile mode – compilation not OK

WinKFPT is exited when "OK" is clicked.

WinKFPTUser's Guide

Date: 20.10.04


4.4 Starting WinKFPT in Batch Mode

Batch mode is used to flash program any number of control units one after the other.

Batch mode of WinKFPT can be activated in two ways:

1. Automatic activation through calling from, for example, an external application using the callingparameter –RUN (see "4.1 Calling Parameters of WinKFPT"). In this case, Batch mode isalready started.

2. Manual activation from within Dialog mode (see "5.1.9 Display � Batch Mode"). In this case,Batch mode is not yet started.

Once Batch mode has been activated, another dialog window (WinKFPT Batch mode monitor) thatcontains the status displays and the function buttons for user inputs in Batch mode is displayed inaddition to the main menu window of WinKFPT:

Fig. 4-1: Dialog window for Batch mode (Batch mode monitor)

WinKFPTUser's Guide

Date: 20.10.04


The following table describes the status displays in the Batch mode monitor:


Control file Path and name of the default control file or of the control file transferred as calling

parameter (-BATCH=<controlfile>).

Status The status display informs the user about the current activity or about error

conditions in Batch mode.

The following status displays are possible:

"not started"

"started"

"waiting for control file"

"reading in control file"

"programming active"

"waiting for end of programming"

"programming ended"

"no control file specified"

"report file cannot be opened"

"WinKFPT Batch mode error"

"Batch cannot be started. Programming in progress"

Errors Indicates the number of errors that occur during control unit communication or

during the evaluation of logistics data.

Aborts Indicates the number of errors that occur during the flash programming of ECUs; an

error leads to immediate aborting of programming.

Target interface Indicates the HW interface+unit that the corresponding WinKFPT instance accesses

during flash programming of an ECU.

Mode Indicates whether a control file for Comfort mode or for Expert mode is being

processed.

Table 4-1: Status displays in the Batch mode monitor

The following user inputs are possible in Batch mode:• "Start ": Batch mode is started, i.e. WinKFPT waits for a control file or a existing

control file is processed.• "Stop ": Batch mode is ended, i.e. it can be restarted with "Start " or deactivated

by closing the Batch mode monitor.• "Close dialog ": The Batch mode monitor is closed and Batch mode deactivated.

WinKFPTUser's Guide

Date: 20.10.04


If Batch mode is started, WinKFPT waits for the Control file indicated. As soon as this file exists, it isopened, evaluated and processed. Depending on the contents of the control file, it is decided whetherthe process is a Batch process in Comfort mode or in Expert mode.

The path and name of the control file can be specified when calling using the calling parameter –BATCH=<controlfile>; if specified, the path must be cited in its entirety, including the drive details.If part of the path is missing, the control file is expected in the installation directory of WinKFPT,<root\bin>.There is no need to enter an extension for the control file. It is automatically assumed to be .CTL.

WinKFPTUser's Guide

Date: 20.10.04


4.4.1 Control File for Batch Mode in Comfort Mode

The control file is processed in order.Its contents correspond to the entries the WinKFPT user makes in the "Comfort mode" of Dialogmode (ZB number, ECU address (corresponds to the integration position) and vehicle identificationnumber).

The syntax of the control file is in line with the file format as familiar from Windows INI files and it isdivided up into the following sections:[FGNUMMER] (VIN), [ZBNUMMER] (ZBNUMBER), [SGADRESSE] (ECUADDRESS) and [BATCH].Other sections are ignored.

The table below contains a full description of the sections of a control file and of the contents of thesesections.Section Contents

[FGNUMMER] The [FGNUMMER] (VIN) section has just one line that contains the vehicle

identification number.

Format: VIN=<VIN>

Example: VIN=WBAAA00000AA00000

[ZBNUMMER] The [ZBNUMMER] (ZBNUMBER) section contains the various assembly

identification numbers, each on a separate line.

Format: ZBNxxxx=<ZBnumber>, where xxxx is a consecutive number that begins at

0000, and there must be no gap.

Example: ZBN0000=7539765

ZBN0001=7539767

The control units are programmed according to the sequence of the numbers.

Programming is ended when the first number that no longer has a successor number

is reached.

WinKFPTUser's Guide

Date: 20.10.04


Section Contents

[SGADRESSE] The [SGADRESSE] (ECUADDRESS) section contains the various ECU addresses,

each on a separate line.

Format: SGADRxxxx=<ECUaddress>, where xxxx is a consecutive number that

begins at 0000, and there must be no gap.

The ECU address is entered as a HEXADECIMAL.

Example: SGADR0000=12

SGADR0001=13

There must be an ECU address with an identical consecutive number for each

assembly identification number entered.E.g.:[ZBNUMMER]ZBN0000=7515985

[SGADRESSE]SGADR0000=A2

[BATCH] The [BATCH] section contains one line with information relating to the ending of

Batch mode.

Format: END=ON or END=OFF.

If the section is left blank (i.e. no entry) or is missing, this is interpreted as

END=OFF.

The purpose of the END=ON option is to enable WinKFPT to be ended in Batch

mode by a calling external application that creates a control file that contains just the

section BATCH with the entry END=ON.

Batch mode is ended immediately upon the control file being read in.

If Batch mode was started automatically by means of the calling parameter –RUN,

WinKFPT is also ended.

In this case, the FGNUMMER, ZBNUMMER and SGADRESSE sections (if present)

are ignored.

Table 4-1: Contents of a control file for the Batch mode in Comfort mode

Once the control file has been processed, it is deleted and WinKFPT waits for a new control file.

WinKFPTUser's Guide

Date: 20.10.04


4.4.2 Control File for Batch Mode in Expert Mode

The control file's contents correspond to the entries the WinKFPT user makes in the "Expert mode" ofDialog mode (PABD, P-SGBD, ECU address, data file, program file, diagnosis protocol and vehicleidentification number).

The syntax of the control file is in line with the file format as familiar from Windows INI files. The filehas just the one section: [MULTIFLASH]Other sections are ignored.

The table below contains a full description of the parameters in the [MULTIFLASH] section of acontrol file:Parameter Contents

MF_PABD This parameter specifies the PABD to be used for programming.

Format: MF_PABD=<PABD name>

Example: MF_PABD=21EK928.IPO

MF_PSGBD This parameter specifies the P-SGBD to be used for programming.

Format: MF_PSGBD=<P-SGBD name>

Example: MF_PSGBD=21EK92.PRG

MF_SG_ADR The ECU address is entered as a HEXADECIMAL.

Format: MF_SG_ADR=<PABD name>

Example: MF_SG_ADR=12

MF_DATEN_DATEI This parameter defines the data file to be programmed. At least one NAAB

file, one data file or one program file must be entered.

Format: MF_DATEN_DATEI =<Data file name>

Example: MF_DATEN_DATEI=Q7525491.0DA

MF_PROGRAMM_DATEI This parameter defines the program file to be programmed. At least one

NAAB file, one data file or one program file must be entered.

Format: MF_PROGRAMM_DATEI =<Program file name>

Example: MF_PROGRAMM_DATEI=7523523A.0PA

MF_NAAB_DATEI This parameter defines the NAAB file to be programmed. At least one NAAB

file, one data file or one program file must be entered.

Format: MF_PROGRAMM_DATEI =<NAAB file name>

Example: MF_NAAB_DATEI=555111_555222.0ba

MF_DIAGNOSEPROTOKOLL This parameter specifies the diagnosis protocol to be used. This is optional.

Format: MF_DIAGNOSEPROTOKOLL=<Diagnosis protocol>

Example: MF_DIAGNOSEPROTOKOLL=KWP2000*

WinKFPTUser's Guide

Date: 20.10.04


MF_FG_NUMMER This parameter specifies the vehicle identification number. It is only required if

UIF writing is used for programming.

Format: MF_FG_NUMMER=<VIN>

Example: MF_FG_NUMMER WBAAA00000AA00000

Table 4-1: Contents of a control file for the Batch mode in Expert mode

Once the control file has been processed, it is deleted and WinKFPT terminates itself automatically.

WinKFPTUser's Guide

Date: 20.10.04


4.4.3 Starting a Programming Job in Batch Mode

Starting the programming job:

The existence of the control file in the relevant directory is the signal for a programming job.The existence of the control file is determined by WinKFPT in Batch mode by means of polling.The control file should first of all be written under a different name or in a different directory and thenbe made visible for Batch mode by being renamed or copied over. This is to prevent uncompletedfiles from being read in.

The control file is no longer read until processing has been completed.

While WinKFPT is in Batch mode, the EDIABAS-API is released and remains bound to the programonly during the period the job is being processed.

For each individual flash programming of an ECU, i.e. for each processing of a VIN from the controlfile, the same status displays are displayed in the main menu window of WinKFPT as are displayedwhen programming in Dialog mode.

Process logging:

While the programming job is being processed, a log is generated that has the same path and nameas the control file but the extension .PRT.

The following is documented in the log file:Name of the control file and its date.Contents of the control file as they have been scanned.Error during scanning of the control file.In Comfort mode:The VIN is entered as FGN=<VIN>.The ZB number and ECU address are entered at the start of processing.In Expert mode:The PABD is entered as MF_PABD=<PABD>.The P-SGBD is entered as MF_PSGBD=<P-SGBD>.The ECU address is entered as MF_SG_ADR=<ECU address>.The data file is entered as MF_DATEN_DATEI=<Data file name>.The program file is entered as MF_PROGRAMM_DATEI=<Program file>.The NAAB file is entered as MF_NAAB_DATEI=<NAAB file>.The VIN is entered as MF_FG_NUMMER=<VIN>.The diagnosis protocol is entered as MF_DIAGNOSEPROTOKOLL=<Diagnosis protocol>.

The following texts are generated to indicate the result of an individual programming routine:"ERG=Programming OK" for correct programming"ERG=Programming nOK. Abort" for error during programming

WinKFPTUser's Guide

Date: 20.10.04


"ERG=Programming nOK. Fatal error" for error prior to programming..

Messages displayed in Dialog mode of WinKFPT in popup dialog boxes are written to the log file inthe format INFOxxx=<Text>, where xxx is a consecutive number.

End of a programming job:

The end of the processing of a job is indicated by deletion of the control file. In Comfort mode,WinKFPT then waits for a new batch file. In Expert mode, WinKFPT terminates itself once the batchfile has been fully processed.

WinKFPTUser's Guide

Date: 20.10.04


4.4.4 Switching HW Interface and Diagnosis Protocol in Batch Mode

Switching HW interface and diagnosis protocol during the programming of control units in Batch modein Comfort mode is based on the file \<root>\DATA\GDATEN\ PRGIFSEL.DAT.This file contains the HW interface and diagnosis protocol that are to be used for the ECU familiesentered.

If the file "PRGIFSEL.DAT" does not exist or if the control unit to be programmed is not entered inthis file, the last HW interface that was active prior to starting Batch mode and the default diagnosisprotocol for this control unit are set.

The default diagnosis protocol is the first one from the list of diagnosis protocols that the P-SGBD ofthe control unit returns as the reply to the prompt with regard to the diagnosis protocols implemented.

WinKFPTUser's Guide

Date: 20.10.04


4.4.5 Starting Several Instances in Batch Mode

In automatic Batch mode, several instances of WinKFPT can be run and process control filessimultaneously.Note that two instances of WinKFPT are not able to use the same control file.Apart from that, each instance must communicate over a different piece of hardware (hardwareinterface + unit) while its control file is being processed.

If two instances want to access the same control file, the following error message is displayed:

Fig. 4-1: Error message when two instances access the same control file

To prevent two Batch mode instances from wanting to access the same control unit, the callingparameter –BATCH=<Control file> must be used.This applies not only to automatic activation (starting WinKFPT with -RUN parameter), but also tomanual activation of Batch mode (starting WinKFPT without -RUN parameter).

Whatever the case, two WinKFPT instances are never able to communicate with a control unit via thesame HW interface+unit.To define the interface and the unit for a WinKFPT instance at the time of starting, you can use thecommand line parameters -INTERFACE=<HW interface> and -UNIT=<Unit identifier>.

Batch mode has a special feature by which two WinKFPT instances can be started that display thesame target interface in the Batch mode monitor, i.e. they have been started with the same HWinterface+unit details.

A HW interface conflict only arises when the two instances process their control file simultaneouslyand want to access the same HW interface.Only that instance that begins processing first is able to access the HW interface properly; the HWinterface is blocked for the second instance from this point to the time processing of the first instancehas been completed.

WinKFPTUser's Guide

Date: 20.10.04


4.5 Starting WinKFPT in Dialog Mode

All calling parameters except "-C" and "-RUN" may be used to start a WinKFPT instance in Dialogmode.

Calling WinKFPT without calling parameters always starts a WinKFPT instance in Dialog mode.

4.5.1 Starting Several Instances in Dialog Mode

Like in Batch mode, it is theoretically possible to call and run up to 99 different WinKFPT instancessimultaneously in Dialog mode, too.

Since the default HW interface+unit or the HW interface+unit entered as the calling parameter isalways accessed immediately when WinKFPT is started in Dialog mode, it is not possible for twoinstances to be started that want to access the same HW interface+unit.

In such a case, the second instance starts with the error message:

or

Fig. 4-1: Error message when the same HW interface+unit is accessed

WinKFPTUser's Guide

Date: 20.10.04


Once you have acknowledged the error message by clicking "OK", the second instance isautomatically closed again.

WinKFPTUser's Guide

Date: 20.10.04


5 WINKFPT'S MAIN MENU

The top menu bar offers the user the following main menu options:

• <Display>• <Import/Export>• <Communication>• <Configuration>• <Help>• <End>

When you select a main menu option, a pull-down menu containing one or more submenu optionsappears via which you can call the various menu options.

5.1 Display Menu

The main menu option Display contains the following submenu options that be used to switch certainfunctions ON or OFF and display error and trace files:

• <CABI.ERR>

• <ERROR.LOG>

• <PABD Parameters>

• <HW History>

• <ZB History>

• <ZB Rule>

• <API Trace File>

• <IFH Trace File>

• <Batch Mode>

WinKFPTUser's Guide

Date: 20.10.04


5.1.1 Display � CABI.ERR

Displays the CABI.ERR file that contains the error messages created when an error occurs duringtranslation of a PABD (= IPS file).

Close the display by clicking OK or by pressing "ESC" or Alt+F4.

5.1.2 Display � ERROR.LOG

Displays the ERROR_INTERFACE_UNIT.LOG error file that contains the error messages from theCOAPI and CDH functions.


5.1.3 Display � PABD Parameters

Displays the job and result parameters currently set for a PABD.


5.1.4 Display � HW History

Displays the HW history of the current hardware number.


5.1.5 Display � ZB History

Displays the ZB history of the current assembly identification number.


5.1.6 Display � ZB Rules

Displays the ZB rule of the current assembly identification number.


WinKFPTUser's Guide

Date: 20.10.04


5.1.7 Display � API Trace File

Displays an API trace file present in the EDIABAS directory.


5.1.8 Display � IFH Trace File

Displays an IFH trace file present in the EDIABAS directory.


5.1.9 Display � Batch Mode

Switches from Dialog mode to Batch mode.

Batch mode is not yet started following this switching.

WinKFPTUser's Guide

Date: 20.10.04


5.2 Import/Export Menu

Selecting this main menu option opens up the following submenu:

Fig. 5-1: Submenu under the main menu option <Import/Export>

5.2.1 Import Submenu

This submenu option in turn activates a pull-down menu that contains the following options:

Fig. 5-1: Pull-down menu under the submenu option <Import>

The Import menu can be used to select all the files necessary for flash programming. They can beselected from any drive or directory. The files selected are then automatically distributed to theappropriate directories once their adoption has been confirmed.

The following file groups can be imported:

Import Files

Data sets / Program releases /NAAB files

*.0DA*.DAF*.0PA*.PAF*.0BA*.BAF

Data set files for dataData exchange filesData set files for programProgram exchange filesData set files for NAABNAAB exchange files

WinKFPTUser's Guide

Date: 20.10.04


P-SGBD *.PRGP-SGBD in compiled code

PABD*.IPS*.IPO

PABDs in source codePABDs in compiled code

Assembly line data

*.0DA*.0PA*.0BA

*.PRG*.IPS*.IPO*.DAT*.DA2*.HWH*.HIS*.ATS*.ASD*.AS2*.GER*.BSU

Data set files for dataData set files for programData set files for NAABP-SGBD in compiled codePABDs in source codePABDs in compiled codeECU logistics filesAssignment of ECU members to names of logistics filesHistory of compatible hardware numbers of an ECUfamilyCompatible assembly identification numbers of an ECUfamilyLogistics fileLogistics fileAuthentication code filesECU member integration positionLogistics file for checking the possibility of a BSU (bootsector update)

Exported configuration -

development data

Files like from import of assembly line data +development files and/or tool-relevant files if desired byuser

Exported configuration - assembly

line data

Files like from import of assembly line data +tool-relevant files if desired by user

Table 5-1: Import files

The importing of exported configuration development data‚ data sets, program data sets, /BSU NAABfiles, P-SGBDs and PABDs is assigned to "Expert mode".The import of exported configuration assembly line data and assembly line data is assigned to"Comfort mode".

WinKFPTUser's Guide

Date: 20.10.04


5.2.1.1 Importing an "Exported Configuration" of Assembly Line Data

You import an "exported configuration" of assembly line data by selecting the menu optionImport/Export � Import � Exported configuration - assembly line data .

The following dialog window is then displayed to enable you to select the import directory:

Fig. 5-1: Selecting the import directory of a configuration of assembly line data

The start directory highlighted in the import dialog window for the first import in a WinKFPT session is"My Computer". For each subsequent import, the import directory highlighted is the one that wasselected the last time.

A configuration of exported assembly line data can only be imported from directories that contain theexport log file BACKUPEXPORT.LOG. The contents of the log file are not checked.If the directory selected does not contain this log file, an error message is displayed and the dialogterminated.

It is only possible to import an entire exported configuration, i.e. you are not able to select parts fromthe exported WDPs for import.

Before importing is performed, a check is run to determine whether or not one or more of the WDPsto be imported is/are already present in the "<root>\Data" directory.

WinKFPTUser's Guide

Date: 20.10.04


A dialog window appears that contains a list of the WDPs already in this directory and the functionbuttons "Replace" , "Merge" and "Cancel" .

Fig. 5-2: WDP conflict when importing a configuration of assembly line data

If the list of WDPs is empty, the list window and its corresponding headline is not shown. The"Merge" button is not shown too because has not function and the "Replace" button is changed bythe "Import" button

Furthermore, you can also specify whether you want to import with or without tool-relevant data (INIfiles) (default is "Import - Tool relevant data" not activated).

Tool-relevant files from the import directory always overwrite those files in the working directory thathave the same name.

KMM files are exported for archiving purposes only and are therefore never reimported.

The buttons have the following functions:

• Cancel (always active):the dialog window is closed and no files are imported.

• Replace and Import respectively(always active):

WinKFPTUser's Guide

Date: 20.10.04


all the files from the import directory selected are copied to the working directory; files thatare already present are overwritten.

• Merge (only active when the WDP list is not empty):only those files that have a more recent date are copied from the import directory to theworking directory.

The following COMMON files are given 'special treatment' that is identical for the two importmodes Replace and Merge :

KFCONFXX.DA2 and HWNR.DA2:In the file in the working directory, all lines that relate to the ECU family of the assembly line data setto be imported are overwritten if they are already present or appended if they are not already present.

Special treatment, which is only valid for the import mode Merge , is given to the following ECU-specific file:

<ECUFAMILY>.DAT:All lines from the file in the import directory that do not yet exist in the file in the working directory areappended to the DAT file in the working directory. This operation is only executed for lines that beginwith a number, i.e. not for lines that in particular begin with "$" or ";".

WinKFPTUser's Guide

Date: 20.10.04


5.2.1.2 Importing an "Exported Configuration" of Development Data

You import an "exported configuration" of development data by selecting the menu optionImport/Export � Import � Exported configuration - development data .


Fig. 5-1: Selecting the import directory of a configuration of development data


A configuration of exported development data can only be imported from directories that contain theexport log file CONFIGEXPORT.LOG. The contents of the log file are not checked.If the directory selected does not contain this log file, an error message is displayed and the dialogterminated.

It is only possible to import an entire exported configuration, i.e. you are not able to select parts fromthe exported WDPs for import.

Before importing is performed, a check is run to determine whether or not one or more of the WDPsto be imported is/are already present in the "<root>\Data" directory.

WinKFPTUser's Guide

Date: 20.10.04


A dialog window appears that contains a list of the WDPs already in this directory and the functionbuttons "Replace" , "Merge" and "Cancel" .

Fig. 5-2: WDP conflict when importing a configuration of development data

If the list of WDPs is empty, the list window and its corresponding headline is not shown. The"Merge" button is not shown too because has not function and the "Replace" button is changed bythe "Import" button

A separate selection element enables you to active or deactivate importing of the development files,i.e. files from the

<basedirectory>\<configurationname>\Daten\Entwicklung\Data\Develop<basedirectory>\<configurationname>\Daten\Entwicklung\Sgdat<basedirectory>\<configurationname>\Daten\Entwicklung\Ecu

directories (default is "Import - Development files" activated).

Note:The files from the export directory

<basedirectory>\<configurationname>\Daten\Entwicklung\Data\Gdatenare not reimported.

WinKFPTUser's Guide

Date: 20.10.04


Furthermore, you can also specify whether you want to import with or without tool-relevant data (INIfiles) (default is "Import - Tool relevant data" not activated).

Development files and tool-relevant files from the import directory always overwrite those files in theworking directory that have the same name.


• Cancel (always active):the dialog window is closed and no files are imported.

• Replace and Import respectively(always active):all the files from the import directory selected are copied to the working directory; files thatare already present are overwritten.

• Merge (only active when the WDP list is not empty):only those files that have a more recent date or are not yet preset are copied from theimport directory to the working directory.





WinKFPTUser's Guide

Date: 20.10.04


5.2.1.3 Importing Assembly Line Data

You import assembly line data by selecting the menu option Import/Export � Import � Assemblyline data .


Fig. 5-1: Selecting the import directory for assembly line data sets


The directory selected contains either an actual assembly line data set or one or more subdirectoriesthat contain assembly line data sets.

In the example above, you could select either "G:\Trans\EK9282" or "G:\Trans".

WinKFPT automatically finds all data sets immediately in the selected directory or one directory levellower and executes the import for each data set.If in the example above you were to select "G:\Trans\EK9282" as the import directory, only the dataset "EK928" would be imported; if you selected "G:\Trans", data sets "EK9282", "EK9294B" etc. wouldbe imported.

WinKFPTUser's Guide

Date: 20.10.04


Before importing is performed, a check is run to determine whether or not one or more of the WDPsto be imported is/are already present in the "<root>\NFS\Data" directory.

A dialog window that contains a list of the WDPs already in this directory and the function buttons"Replace" , "Merge" and "Cancel" appears only when this is the case.

Fig. 5-2: WDP conflict when importing assembly line data sets


• Cancel:the dialog window is closed and no files are imported.

• Replace:all the files from the import directory selected are copied to the working directory; files thatare already present are overwritten.

• Merge:only those files that have a more recent date or are not yet preset are copied from theimport directory to the working directory.



WinKFPTUser's Guide

Date: 20.10.04




The files are distributed to the following directories when assembly line data is imported:

Files Target directory

*.PRG <ediabas>\ecu

*.IPS, *.IPO <root>\SGDAT\

*.ASD, *.AS2, INFO.GER, HWNR.DA2, KFCONF.DA2,HWNR.DAT, NPV.DAT, KFCONF.DAT, HISTORIE.BSU

<root>\DATA\GDATEN

<ECUFAMILY>.DAT, *.0DA, *.0PA, *.0BA, *.HWH, *.HIS,*.ATS

<root>\DATA\<ecufam>

Table 5-1: Distribution of the files to directories when assembly line data is imported

WinKFPTUser's Guide

Date: 20.10.04


5.2.1.4 Importing NAAB, Program and Data Data Sets

You import NAAB files, program data sets and data data sets by selecting the menu optionImport/Export � Import � Data / Program / BSU NAAB files .

By importing NAAB files, program data sets and data data sets, you select the files you want to usefor flash programming in Expert mode and automatically copy them to the appropriate directory.

Fig. 5-1: Importing data sets/program data sets/BSU NAAB files

*.BAF, *.0BA, *.PAF, *.0PA, *.DAF and *.0DA files are displayed by default.

To import the files:• Select the directory with the files you want from the list next to "Search in" .

• Select the file(s) to be imported.You can select a single file from the list simply by clicking it with the left mouse button.You can select several files to import by holding down the <Ctrl> keyand clicking with the left mouse button.You can select all the files displayed by pressing <Ctrl> + <A> .

• Then click "Import" .

The files you have selected are copied to \<root>\data\develop .

WinKFPTUser's Guide

Date: 20.10.04


Files that already exist can only be overwritten once a warning prompt has been acknowledged in thepositive.

Fig. 5-2: Overwriting files during NAAB, data and program file importing

If you have selected more than one file, the status of the copying procedure is indicated by a progressbar (0 - 100 %).

After being imported, files are displayed in the selection list of the "Loading a data set - NAAB file","Loading a data set - program file" or "Loading a data set - data file" function in Expert mode (see"8.2.2

WinKFPTUser's Guide

Date: 20.10.04


Function: Loading a Data Set – NAAB File", "8.2.3 Function: Loading a Data Set – Program File" or"8.2.4 Function: Loading a Data Set – Data File").

WinKFPTUser's Guide

Date: 20.10.04


5.2.1.5 Importing Control Unit Description Files for Programming (P-SGBDs)

You import P-SGBDs by selecting the menu option Import/Export � Import � P-SGBD.

By importing P-SGBDs, you select the control unit description files you want to use for flashprogramming in Expert mode and automatically copy them to the appropriate directory.

Fig. 5-1: Importing P-SGBDs

Only *.PRG files are displayed (default setting).


• Select the file to be imported.You can select a single file from the list simply by clicking it with the left mouse button.You can select several files to import by holding down the <Ctrl> keyand clicking with the left mouse button.You can select all the files displayed by pressing <Ctrl> + <A> .


The files you have selected are copied to the P-SGBD directory "<ediabas>\ecu "4.

4 <ediabas> = installation directory for EDIABAS interface

WinKFPTUser's Guide

Date: 20.10.04



Fig. 5-2: Overwriting files during P-SGBD importing


After being imported, files are displayed in the selection list of the "Load P-SGBD " function in Expertmode (see "8.1.2 Function: Loading a P-SGBD").

WinKFPTUser's Guide

Date: 20.10.04


5.2.1.6 Importing Flash Sequence Description Files (PABDs)

You import PABDs by selecting the menu option Import/Export � Import � PABD .

By importing PABDs, you select the flash sequence description files you want to use for flashprogramming in Expert mode and automatically copy them to the appropriate directory.

Fig. 5-1: Importing PABDs

Only *.IPS and *.IPO files are displayed (default setting).


• Select the file to be imported.You can select a single file from the list simply by clicking it with the left mouse button.You can select several files to import by holding down the <Ctrl> keyand clicking with the left mouse button.You can select all the files displayed by pressing <Ctrl> + <A> .


WinKFPTUser's Guide

Date: 20.10.04


The files you have selected are copied to "\<root>\sgdat" 5.


Fig. 5-2: Overwriting files during PABD importing


After being imported, files are displayed in the selection list of the "Load PABD" function in Expertmode (see "8.1.1 Function: Loading a PABD").

5 <root> : installation directory of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


5.2.2 Export Submenu

This submenu option in turn activates a pull-down menu that contains the following options:

Fig. 5-1: Pull-down menu under the submenu option <Export>

WinKFPTUser's Guide

Date: 20.10.04


5.2.2.1 Exporting a "Configuration" of Assembly Line Data

You export a "configuration" of assembly line data by selecting the menu option Import/Export �Export � Configuration - assembly line data .

When you select this menu option, the following dialog window appears:

Fig. 5-1: Dialog window for exporting a configuration of assembly line data

This dialog window displays the export base directory currently set, e.g. <root>\NFS-Backup", and twoinput fields ("Type series" and "I-Level") for the names of the two subdirectories.

A list box displays all the valid assembly line data sets (ECU families) available for selection forexport. You can select either no data set at all, one, several or all of the assembly line data sets.If no valid assembly line data exists, the list box is empty and all you can do is export the tool-relevant data by activating the corresponding check box.

WinKFPTUser's Guide

Date: 20.10.04


With each export, the KMM data from the working directory "<root>\KMM\" is exported implicitly,provided a KMM directory exists.

Before the actual copying process begins, the data to be exported is compared with the correspondingdata last exported and located in the highest-order index directory.Excluded from comparison are the COMMON files because those to be exported cannot as a rule beidentical with those previously exported.

This basically results in the following two sequences for the export of assembly line data:1. No new directories are created, i.e. the index directory is not increased. This is the case if the files to be exported, either all or just

some of them, are not yet present in the highest-order index directory, and if all or some of the files present are identical

with those to be exported.

All files are deleted from their respective export directory before copying begins.

2. New directories are created, i.e. the index directory is increased automatically. This is the case if one and just one file to be

exported is not identical with the corresponding file in the highest-order index directory.

Every export of assembly line data is documented in the export log file "BACKUPEXPORT.LOG" inthe <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\ directory.

In the event of repeated export to the same directory (<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\), the relevant information to be stored is in each case appended to the log file thatalready exists.

The following pieces of information are entered in a log file for each export procedure:• Date (format: dd.mm.yyyy)• Export base directory• Type series• I-Level• Index• With/Without development files• With/Without tool-relevant data• ECU family

: :

• Separating line

WinKFPTUser's Guide

Date: 20.10.04


5.2.2.1.1 Directory Structure for Exporting Assembly Line Data

<Baureihe>\

<i-Stufe>\

daten\

<sgfam1>\

<sgfam2>\

NFS\

EDIABAS\bin\

bin\

cfgdat\

GData, EC-Family-Data, PABD,P-SGBD will be placed togetherin this directory

winkfpt.ini, ...

coapi.ini, ...

ediabas.ini, ...

KMM\

<root>\NFS-Backup\ configurable

enter manually on export


<Index>\Index will be increased automatically,if changend Data is exported

<Log-File>

Fig. 5-1: Structure of the target directories for exporting assembly line data

WinKFPTUser's Guide

Date: 20.10.04


5.2.2.1.2 Filing of the Files When Exporting Assembly Line Data

• Export WDPs (if one or more selected)Flash data, logistics data: The files *.0PA, *.0DA, *.0BA <ECUFAM>.DAT,<ECUFAM>.HIS, <ECUFAM>.HWH and <ECUFAM>.ATS are copied from the<ecufam> directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.

COMMON files: COMMON files SWTCONFX.DAT, HISTORIE.BSU, SGIDC.AS2,SGIDD.AS2 and INFO.GER are copied from the <root>\Data\Gdaten directory to the<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory. Therelevant parts of the HWNR.DA2 and KFCONFXX.DA2 files are determined and onlythese parts are copied to the <root>\NFS-Backup\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.The file name of the COMMON file is adopted unchanged.

PABD: The name of the description file that belongs to the WDP is determined from theKFCONFXX.DA2 file and copied from <root>\Sgdat to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.

P-SGBD: The name of the description file that belongs to the WDP is determined fromthe KFCONFXX.DA2 file and copied from EDIABAS\ECU to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.

• Export KMMs (always if present)

Copying of all the files in the <root>\kmmdat\<typeseries>\ directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\kmm\ directory.

• Export tool-relevant data (optional)

Copying of all the files with the extension *.INI from the <root>\NFS\bin\ directory to the<root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\bin\ directory.

Copying of all the files with the extensions *.INI and *.DAT from the <root>\cfgdatdirectory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\cfgdat\ directory.

Copying of all the files with the extension *.INI from the <root>\EDIABAS\bin\ directory tothe <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\EDIABAS\bin\ directory.

WinKFPTUser's Guide

Date: 20.10.04


5.2.2.2 Exporting a "Configuration" of Development Data

You export a "configuration" of development data by selecting the menu option Import/Export �Export � Configuration - development data .

When you select this menu option, the following dialog window appears:

Fig. 5-1: Dialog window for exporting a configuration of development data

This dialog window displays the export base directory currently set, e.g. "<root>\Diagprog", and oneinput field ("Configuration name") for the name of the subdirectory.

A list box displays all the valid assembly line data sets (ECU families) available for selection forexport. You can select either no data set at all, one, several or all of the assembly line data sets.

If no valid assembly line data exists, the list box is empty and all you can do is export thedevelopment files and/or tool-relevant data by activating the corresponding check box(es).

WinKFPTUser's Guide

Date: 20.10.04


All files selected for export are copied.If the files are to be exported to a directory ("Configuration name") that already exists, the followingprompt is displayed:

Fig. 5-2: Prompt asking whether development data should be overwritten during export

If you click "Yes" , all the files in the existing directories are deleted first before exporting isconducted.

Every export of development data is documented in the export log file "CONFIGEXPORT.LOG" in the<root>\Diagprog\<configurationname>\ directory.

In the event of repeated export to the same directory (<root>\Diagprog \<configurationname>\), therelevant information to be stored is in each case appended to the log file that already exists.

The following pieces of information are entered in a log file for each export procedure:• Date (format: dd.mm.yyyy)• Export base directory• Configuration name• With/Without development files• With/Without tool-relevant data• ECU family

: :

• Separating line

WinKFPTUser's Guide

Date: 20.10.04


5.2.2.2.1 Directory Structure for Exporting Development Data

<Name der Konfiguration>\

daten\

Entwicklung\

ecu\

sgdat\

gdaten\

develop\

<sgfam2>\

<sgfam1>\

all P-SGBD

al PABD


C:\Diagprog\Konfiguration\ configureable

all GData from the working directory

Complete Develop-Directory

NFS\

EDIABAS\bin\

bin\

cfgdat\

winkfpt.ini, ...

coapi.ini, ...

ediabas.ini, ...

<Log-Filei>

GData, ECU-Familly-Data, PABD,P-SGBD wille be placed together ina directory

Fig. 5-1: Structure of the target directories for exporting development data

WinKFPTUser's Guide

Date: 20.10.04


5.2.2.2.2 Filing of the Files When Exporting Development Data

• Export development files (if released for export)Flash data: The files *.0PA, *.0DA, *.0BA, *.PAF, *.DAF and *.BAF are copied from theNFS\Data\Develop directory to the<root>\Diagprog\<configurationname>\Daten\Entwicklung\Develop directory.

COMMON files: COMMON files SWTCONFX.DAT, HISTORIE.BSU, SGIDC.AS2,SGIDD.AS2, HWNR.DA2, INFO.GER and KFCONFXX.DA2 are copied from theNFS\Data\Gdaten directory to the<root>\Diagprog\<configurationname>\Daten\Entwicklung\Gdaten directory.

P-SGBDs: All *.PRG files are copied from the EDIABAS\ECU directoryto the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Ecu directory.

PABDs: All *.IPS and *.IPO files are copied from the NFS\Sgdat directory to the<root>\Diagprog\<configurationname>\Daten\Entwicklung\Sgdat directory.

• Export WDPs (if one or more selected)Flash data, logistics data: The files *.0PA, *.0DA, *.0BA <ECUFAM>.DAT,<ECUFAM>.HIS, <ECUFAM>.HWH and <ECUFAM>.ATS are copied from the<ecufam> directory to the <root>\Diagprog\<configurationname>\Daten\<ecufam>directory.

COMMON files: COMMON files SWTCONFX.DAT, HISTORIE.BSU, SGIDC.AS2,SGIDD.AS2 and INFO.GER are copied from the NFS\Data\Gdaten directory to the<root>\Diagprog\<configurationname>\Daten\<ecufam> directory. The relevant parts ofthe HWNR.DA2 and KFCONFXX.DA2 files are determined and only these parts arecopied to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory. The filename of the COMMON file is adopted unchanged.

PABD: The name of the description file that belongs to the WDP is determined from theKFCONFXX.DA2 file and copied from NFS\Sgdat to the<root>\Diagprog\<configurationname>\Daten\<ecufam> directory.

P-SGBD: The name of the description file that belongs to the WDP is determined fromthe KFCONFXX.DA2 file and copied from EDIABAS\ECU to the<root>\Diagprog\<configurationname>\Daten\<ecufam> directory.

• Export tool-relevant data (optional)

Copying of all the files with the extension *.INI from the <root>\bin\ directory to the<root>\Diagprog\<configurationname>\NFS\bin\ directory.

WinKFPTUser's Guide

Date: 20.10.04


Copying of all the files with the extensions *.INI and *.DAT from the <root>\cfgdatdirectory to the <root>\Diagprog\<configurationname>\NFS\cfgdat\ directory.

Copying of all the files with the extension *.INI from the <root>\EDIABAS\bin\ directory tothe <root>\Diagprog\<configurationname>\EDIABAS\bin\ directory.

WinKFPTUser's Guide

Date: 20.10.04


5.2.3 Deleting Assembly Line Data

You delete assembly line data by selecting the menu option Import/Export � Delete - assemblyline data .

If there is no assembly line data present, the following message is displayed:

Fig. 5-1: Deleting assembly line data; message if no assembly line data is present

In this case, it is also not possible to conduct flash programming of ECUs in Comfort mode. Youwould first have to import assembly line data to enable flash programming.

WinKFPTUser's Guide

Date: 20.10.04


If valid assembly line data does exist, the following dialog window is opened:

Fig. 5-2: Dialog window for deleting assembly line data

A list box displays all the valid assembly line data sets (ECU families) available for selection fordeletion. You can select either no data set at all, one, several or all of the assembly line data sets.

The directories of the assembly line data selected are completely deleted during the deletionprocedure.The associated description files (SGBD/PABD) are likewise deleted, but only if they occur no morethan once in "kfconfxx.da2", i.e. only if they are not used by one or more other ECU families at thesame time.

WinKFPTUser's Guide

Date: 20.10.04


By clicking the function button "Remove" , you delete the selected WDPs from the list box andremove the corresponding entries from the COMMON files "kfconfxx.da2" and "hwnr.da2".

The following prompt appears before deletion is started:

Fig. 5-3: Deleting assembly line data; prompt displayed on clicking "Remove"

If you click the function button "Remove all" , all WDPs are selected and deleted, and the COMMONfiles "kfconfxx.da2" and "hwnr.da2" are completely emptied with the exception of their headers, i.e.including all "dead" entries for which no WDPs exist.

The following prompt appears before deletion is started:

Fig. 5-4: Deleting assembly line data; prompt displayed on clicking "Remove all"

If you click "Yes" , deletion is started and the dialog window is closed once deletion has beencompleted.If you click "No" , the prompt disappears from the screen and the dialog window remains open.

If you click the function button "Cancel" , the dialog window is closed; active deletion procedures arenot interrupted.

WinKFPTUser's Guide

Date: 20.10.04


5.3 Communication Menu

This menu can be used to set the following parameters for communication between WinKFPT andcontrol units:

• Hardware interface• Diagnosis protocol

The menu option "HW interface" enables you to switch dynamically between HW interfaces (EDIC,ADS, etc.).

The "HW interface" menu option is only active if HW interfaces are entered in the configuration fileWINKFPT.INI (see "3.4.2 Configuration in WINKFPT.INI").

The menu option "Diagnosis protocol" enables you to choose dynamically between the diagnosisprotocols that are supported by a selected control unit (BMW-Fast, KWP2000, etc.).

The "Diagnosis protocol" menu option is only active if a selected control unit supports more thanone diagnosis protocol.

A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABDand P-SGBD (Expert mode).

WinKFPTUser's Guide

Date: 20.10.04


5.3.1 Selecting (Choosing) a HW Interface

You choose a HW interface by selecting the menu option Communication � HW interface .

Fig. 5-1: Selection dialog for HW interface

The "HW interface" menu option is only active if HW interfaces are entered in the configuration fileWINKFPT.INI.

All HW interface entries from WINKFPT.INI (see "3.4.2 Configuration in WINKFPT.INI") are presentedin a list for selection.

You must select a unit identifier (_, A, B, C, D, E) for each HW interface.The HW interface unit is required by EDIABAS to enable it to distinguish between interfaces if severalHW interfaces of the same type are integrated (installed) in one computer.

To choose a HW interface:• Choose a HW interface from the "HW interface" list.

• Select the unit for the HW interface.If only one interface of this type is integrated in the computer, you must select "_" (= default).

• Then click "OK" .

WinKFPTUser's Guide

Date: 20.10.04


If WinKFPT is able to activate the HW interface chosen, the interface is displayed constantly in the"HW interface" box as status information. Otherwise, error message 304 (which you have toacknowledge) appears and the previous setting remains active.

Fig. 5-2: Error message displayed when an impermissible choice of HW interface is made

The same error occurs if, for example, the HW interface chosen is not installed as hardware orsoftware.

If a different instance of WinKFPT has already accessed the same HW interface+unit, the followingerror message appears:

Fig. 5-3: Error message when the same HW interface+unit is accessed in Dialog mode

When WinKFPT is started, the HW interface defined in "EDIABAS.INI" is activated and displayed bydefault (see "3.4.4 Configuration in EDIABAS.INI").

You can, however, select a different setting straight away when starting a further WinKFPT instancewith the aid of the calling parameters -INTERFACE=<HW interface> and -UNIT=<Unit identifier> .

WinKFPTUser's Guide

Date: 20.10.04


5.3.2 Selecting (Choosing) a Diagnosis Protocol

You choose a diagnosis protocol by selecting the menu option Communication � Diagnosisprotocol .

Fig. 5-1: Dialog box for selecting a diagnosis protocol

The "Diagnosis protocol" menu option is only active if a selected control unit supports more thanone diagnosis protocol.A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABDand P-SGBD (Expert mode).Once you have chosen a control unit, WinKFPT automatically tries to call the job"DIAGNOSEPROTOKOLL_LESEN" from the corresponding P-SGBD.If the job is present, the diagnosis protocols specified in it are displayed in a list for selection.If you do not make an explicit selection, the first diagnosis protocol from the list is activated bydefault.

To choose a diagnosis protocol:• Choose a diagnosis protocol from the "Diagnosis protocol" list.

• Then click "OK" .

The diagnosis protocol activated is displayed in the "Diagnosis protocol" box a status information.A selected diagnosis protocol is set internally by means of the P-SGBD job"DIAGNOSEPROTOKOLL_SETZEN".

WinKFPTUser's Guide

Date: 20.10.04


WinKFPTUser's Guide

Date: 20.10.04


5.4 Configuration Menu

When you select this menu, the following configuration dialog window is opened.

Fig. 5-1: Configuration dialog window

WinKFPTUser's Guide

Date: 20.10.04


The settings correspond to the following INI parameters:

Dialog text Ini file entry Description

Sprache / Language SPRACHE The entry defines the language

for WinKFPT. Options: German

(ger) and English (eng).

Programming voltage U_PROG The entry specifies whether the

programming voltage is switched

ON or OFF during flash

programming.

Show programming voltage ANZEIGE_U_PROG The entry specifies whether the

value of the programming

voltage is displayed (ON) or not

(OFF) during flash programming.

Fast baudrate SCHNELLE_BAUDRATE The entry specifies whether the

fast baudrate is used (ON) or not

(OFF) during flash programming.

Test Checksum TEST_CHECKSUMME The entry specifies whether the

checksum is validated (ON) or

not (OFF) after programming of

the data.

activate Bootsectorupdate BsuActive The entry specifies whether a

boot sector update, i.e. flash

programming of an NAAB file, is

possible or not.

Force program programming in

comfort mode

PROGRAMM_ERZWINGEN The entry specifies whether,

during flash programming in

Comfort mode, a program is to

be programmed whatever the

case, even if only data

programming would be

necessary.

UIF write after data AIF_SCHREIBEN_NACH_DATEN The entry specifies whether the


not (OFF) during data


Expert mode.

WinKFPTUser's Guide

Date: 20.10.04



UIF write after program AIF_SCHREIBEN_NACH_PROGRAMM The entry specifies whether the


not (OFF) during program


Expert mode.

UIF write in expert mode EXPERT_MIT_AIF The entry specifies whether the



programming in Expert mode.

UIF write in comfort mode KOMFORT_MIT_AIF The entry specifies whether the



programming in Comfort mode.

PABD format CabdFormat The entry defines whether

WinKFPT is to use PABDs as

source files or as compiled files.

IPS PABDs as source

files


files

API tracelevel API_TRACE The entry specifies the level for

the API traces in Ediabas (0

means that the trace is switched

off).

IFH tracelevel IFH_TRACE The entry specifies the level for

the IFH traces in Ediabas (0

means that the trace is switched

off).

Directory for error file "error.log" ErrorLogPath Storage directory for the

ERRORn.LOG file

Base directory for exported

configurations – assembly line

data

KomfortKonfPath Base directory for export of a



WinKFPTUser's Guide

Date: 20.10.04



Base directory for exported

configurations – assembly line

data

KomfortKonfPath Base directory for export of a



Base directory for working

directories of WinKFPT

ExpertKonfPath Base directory for the working

directories: cfgdat, data, sgdat

etc.

If you close the dialog window by clicking "OK" and the settings in the window differ from those in theIni file, you are asked whether you would like to save your changes permanently to the Ini file. Even ifyou reject this option now, the settings you have entered remain valid for the duration of theWinKFPT session, and you are given another chance to save this configuration to the Ini file whenyou end the session.

If you change the PABD format and a PABD has already been selected, you must then explicitlyselect a new PABD in Expert mode or implicitly select a new PABD in Comfort mode by selecting anassembly identification number (ZB number). Message boxes prompt you to do this.

5.5 Help Menu

This menu is used to start the online help and display information about the program.

5.5.1 Contents - Calling the Online Help

You call the online help by selecting the menu option Help � Contents .

This command displays the opening screen of the online help function.The User's Guide and the online help are identical.Whenever updates of WinKFPT are released, the Word file of the User's Guide and the online helpwill both be updated.

WinKFPTUser's Guide

Date: 20.10.04


Fig. 5-1 Online help of WinKFPT

5.5.2 Info - Version Information of WinKFPT

You display the version information of WinKFPT by selecting the menu option Help � Info .This command displays the program version and copyright information.

WinKFPTUser's Guide

Date: 20.10.04


Fig. 5-1: Program version and copyright information

The top part of this window shows the version of WinKFPT and the versions of the COAPI and Krapilibraries.

Displayed in the bottom right-hand corner are the creation date and time of the WinKFPT version.

WinKFPTUser's Guide

Date: 20.10.04


5.6 End Menu

You use this menu to exit WinKFPT.

5.6.1 Exit

You exit WinKFPT by selecting the menu option End � Exit .

This command terminates the program.If you have activated Expert mode at least once while using WinKFPT, you have the option beforeexiting WinKFPT of saving the current settings you have made in Expert mode so that you can callthem up again the next time you start the program (see "3.4.3 Configuration for Expert Mode").

As WinKFPT is terminated, the last window size and window position of the application are saved asthe entry WindowPosition in the WINKFPT.INI file.The next time WinKFPT is launched, the program is started with the same window size and position(see "3.4.2 Configuration in WINKFPT.INI").

WinKFPTUser's Guide

Date: 20.10.04


6 FUNCTIONS OF WINKFPT

WinKFPTUser's Guide

Date: 20.10.04


Special functions Diagnosis functions

Read UIFRead ECU BaudratesRead and write calibration valuesVS2/DS2 modeEWS alignment

Prog. settings phase, Level 2

enter ECU-Addressload Dataset - Programload Dataset - Data

FINISHED

MAIN MENU

COMFORT-MODE EXPERT-MODE

Clear all settings

Prog. execution phase

Do programDo program update

Prog. settings phase

enter ZUSBchoose ZUSBupdate ZUSB

enter VIN

FINISHED

ZUSBentered/selected?

and VINentered?

Comfort mode

Expert mode

NO

Prog. settings phase, Level 1

load PABDload P-SGBD

FINISHED

PABD and P-SGBDselected?

NO

YES

Comfort mode

Expert mode

read ECU statusread ECU identificationread ECU internal temperature

YES

prog.program

YESDatasetProgramselected?

Dataset Dataselected?

prog. dataYES

Prog. execution phase

WinKFPTUser's Guide

Date: 20.10.04


Fig. 6-1: Functional hierarchy phases of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


6.1 Function Start Menu: Operating Modes of WinKFPT

This function menu is opened when a WinKFPT instance is started.

The function start menu offers you two WinKFPT operating modes to choose from:• Comfort mode• Expert mode.

Fig. 6-1: Function start menu of WinKFPT

Each of these two operating modes offers functions that can be divided into two phases:• Functions of the programming settings phase• Functions of the programming execution phase.

The operating modes differ with respect to their• functions for entering and selecting job data for ECU flash programming during the programming

settings phase.• functions for flash programming control unit during the programming execution phase.

Use of the "general functions" is identical in both operating modes (see "9 General Functions").

WinKFPTUser's Guide

Date: 20.10.04


The following table contains the job data possible in the two operating modes:

Mode Job dataComfort mode Name of the control unit family

Assembly identification numberIntegration position<Vehicle identification number>

Expert mode P-SGBDPABDECU addressData set name for NAABData set file for programData set file for data<Vehicle identification number>

Table 6-1: Overview of the job data in the operating modes� <Vehicle identification number>The vehicle identification number (VIN) only has to be entered (irrespective of the mode) if you areflash programming with subsequent writing of the user info field (UIF).Flash programming with/without UIF writing can be set by means of the configuration file "winkfpt.ini".

� ECU addressWhether or not you need to enter the ECU address in Expert mode depends on the state ofdevelopment of the description files.In the older description files - these are as a rule the non-standardized description files - the ECUaddress is hard-coded for filling the protocol parameters and diagnosis telegrams.

The new standard description files must be fed an ECU address from outside, in this case by meansof a user input. This address is then saved globally for further processing in the description files.

Whether or not the ECU address has to be entered is determined automatically by WinKFPT anddisplayed to you on the screen.

� Description files and data set filesIn Comfort mode, the description and data set files required for flash programming are determinedfrom the job data with the aid of the BMW logistics files.

WinKFPTUser's Guide

Date: 20.10.04


6.1.1 Comfort Mode

This mode is used for flash programming control units, including all logistical checks that, forexample, have to be conducted for end-of-line programming at the factory.

Prerequisite for flash programming of a control unit in Comfort mode is the presence of a completeassembly line data set for this control unit (see "5.2.1 Import Submenu").

Control units can be flashed in Comfort mode in the following ways:� Entry or selection of the assembly identification number (ZUSB number), selection of any number

of integration positions offered for the ZUSB number, entry of the vehicle identification number(VIN) when a UIF is written, and subsequent flash programming of the control unit or control units.�

Selection of a control unit family and of any number of integration positions offered for this family,and subsequent updating of the control unit or control units to the latest assembly identification,whereby updating to an incompatible hardware release by means of a BSU is also taken intoaccount.

WinKFPTUser's Guide

Date: 20.10.04


6.1.1.1 Starting Comfort Mode

Comfort mode is started either by clicking the function button "Comfort mode " or by pressingfunction key <F1> on the keyboard.

The "Comfort mode " function button is available in the following function phases:� in the function start menu(see "Fig. 6-1: Function start menu of WinKFPT").� in the function menu of the programming execution phase of Comfort mode(see "Fig. 7-1: Programming execution phase in Comfort mode").� in the function menu of the programming execution phase of Expert mode (see "Fig. 8-1: Programming execution phase in Expert mode").

Only PABDs in IPO format are used in Comfort mode. If the IPS format is set in the configurationwhen Comfort mode is entered, the following message box appears:

Fig. 6-1: Format switchover on entering Comfort mode

If you click "OK", the PABD format is automatically set to IPO; if you click "Cancel", you do not enterComfort mode.

The "Comfort mode " button takes you to the programming settings phase of Comfort mode to enableyou to enter job data required for flash programming.

When you activate "Comfort mode ", the following job data and status displays from the precedingsession in Comfort mode are deleted:• ECU address or integration position• Diagnosis protocol• PABD• P-SGBD

The job data and status displays:• Vehicle identification number• Assembly identification number

WinKFPTUser's Guide

Date: 20.10.04


• Hardware numberare retained.

When you activate "Comfort mode ", the job data and status displays from the preceding session inExpert mode are either completely deleted or are buffered for loading the last configuration for arenewed entry into Expert mode.

WinKFPTUser's Guide

Date: 20.10.04


6.1.1.2 Exiting Comfort Mode

Comfort mode can be exited in two ways:� By switching to Expert mode� By deleting the job data for Comfort mode.

� You switch to Expert mode by activating the function button "Expert mode ".

When you activate "Expert mode ", the following job data and status displays of Comfort mode aredeleted:• Vehicle identification number• Assembly identification number• Hardware number

The job data and status displays:• ECU address or integration position• Diagnosis protocol• PABD• P-SGBDare retained and lead in Expert mode to the switch to programming settings phase Level 2 (see: Fig.8-1: Programming settings phase Level 2 in Expert mode).

� To completely delete job data in Comfort mode, the following function buttons must be activated

one after the other:"Expert mode ""Cancel " (if loading from configuration is offered)"Done" (<F8> in Expert mode)"Comfort mode ""Done" (<F8> in Comfort mode).

Afterwards, WinKFPT displays the function start menu (see: Fig. 6-1: Function start menu ofWinKFPT).

WinKFPTUser's Guide

Date: 20.10.04


6.1.2 Expert Mode

This mode is used to select or enter the job data (PABD, P-SGBD and data sets) and then flashprogram the control unit.

Prerequisite for flash programming of a control unit in Expert mode is the presence of the descriptionfiles and data sets wanted for this control unit (see "5.2.1 Import Submenu").

In Expert mode, you do have the possibility of bypassing logistical restrictions by e.g.:• programming a program data set that is incompatible with the current program data set in the

control unit• "resetting" a control unit by programming "old" program data sets• programming data sets that do not suit the current program data set in the control unit.

Caution!If you embark on actions of this kind, you must know precisely what you are doing because any errorcould lead to a control unit being rendered totally unusable for the future. Such a control unit would nolonger be able to be flashed via diagnosis communication and would have to be submitted forrecycling.

When you select Expert mode, the graphical user interface (GUI) immediately displays the assemblyidentification number (ZB number) from the configuration file "COAPI.INI" for checking purposes ifEXPERT_MIT_AIF=ON is set in the configuration file "WINKFPT.INI".

This ZB number is written to the UIF.

If a different ZB number is to be entered in the UIF, you must carry out the following steps:• Exit WinKFPT.• Change the entry in "COAPI.INI" (see "3.4.1 Configuration in COAPI.INI").• Restart WinKFPT.

WinKFPTUser's Guide

Date: 20.10.04


6.1.2.1 Starting Expert Mode

Expert mode is started either by clicking the function button "Expert mode " or by pressing functionkey <F2> on the keyboard.

The "Expert mode " function button is available in the following function phases:� in the function start menu(see "Fig. 6-1: Function start menu of WinKFPT").� in the function menu of the programming execution phase of Comfort mode(see "Fig. 7-1: Programming execution phase in Comfort mode").� in the function menu of the programming execution phase of Expert mode (see "Fig. 8-1: Programming execution phase in Expert mode").

The "Expert mode " button takes you to the programming settings phase Level 1 or Level 2 of Expertmode to enable you to enter job data required for flash programming.

When you activate "Expert mode ", all job data and status displays from the preceding session inExpert mode are retained:

When you activate "Expert mode ", the following job data and status displays from thepreceding session in Comfort mode are deleted:• Vehicle identification number• Assembly identification number• Hardware number

The job data and status displays:• ECU address or integration position• Diagnosis protocol• PABD• P-SGBDare retained.

WinKFPTUser's Guide

Date: 20.10.04


6.1.2.2 Exiting Expert Mode

You exit Expert mode by:� switching to Comfort mode.

� You switch to Comfort mode by activating the function button "Comfort mode ".

When you activate" Comfort mode ", all job data and status displays of Expert mode are eithercompletely deleted or are buffered for loading the last configuration for a renewed entry into Expertmode.

After you click "Done" (or press <F8> in Comfort mode), WinKFPT displays the function start menu(see: Fig. 6-1: Function start menu of WinKFPT).

WinKFPTUser's Guide

Date: 20.10.04


7 FUNCTION PHASES IN COMFORT MODE

The functions of Comfort mode are divided into two phases:� Functions of the programming settings phase� Functions of the programming execution phase.� The functions of the programming settings phase are used for entering or selecting all the job data

required for flash programming.� The functions of the programming execution phase are used for flash programming one or more

control units.

Whether or not you can switching function phase depends on the scope of the job data you haveentered.

Function phase Functions Entries required for switching to the level

Programming settings

phase

• Entering a ZUSB number• Choosing a ZUSB number• Updating an assembly

identification• Entering a VIN• Finishing the programming

settings phase

No entries

Programming

execution phase

• Programming a ZUSB number• Programming a ZUSB update• Special• Diagnosis

Integration position(s) for a ZUSB number or

a control unit family

Table 7-1: Function phases of Comfort mode

WinKFPTUser's Guide

Date: 20.10.04


7.1 Functions of the Programming Settings Phase in Comfort Mode

The following functions are available in the programming settings phase of Comfort mode:

• Entering a ZUSB number• Choosing a ZUSB number• Updating an assembly identification• Entering a vehicle identification number• Finishing the input of job data.

Fig. 7-1: Functions of the programming settings phase in Comfort mode

WinKFPTUser's Guide

Date: 20.10.04


7.1.1 Function: Entering a ZUSB Number

You start the function for entering a ZUSB number either by clicking the "Enter ZUSB " button or bypressing function key <F1> on the keyboard.

When you activate this function, a dialog box opens in which you enter the assembly identificationnumber (ZUSB number).

Fig. 7-1: Dialog box for entering a ZUSB number in Comfort mode

Note!The ZUSB number must consist of 7 digits and solely of numbers otherwise an error messageappears which you have to acknowledge.

WinKFPTUser's Guide

Date: 20.10.04


• If you click "Cancel ", your entry is discarded.

• If you click "OK", WinKFPT checks whether the ZUSB number you have entered is present in an<EcuFam>.DAT file of the existing assembly line data sets in the \<root>\DATA 8 directory.

If the assembly identification number you have entered is not found or is invalid, input of the ZUSBnumber is aborted and the following error message displayed:

Fig. 7-2: Error message - ZUSB number not present in the logistics

8 <root> = installation directory of WinKFPT

WinKFPTUser's Guide

Date: 20.10.04


If the assembly identification number entered is valid, a dialog window appears enabling you tochoose one or more integration positions:

Fig. 7-3: Dialog window for choosing an ECU family, assembly identification number and integrationposition

The assembly identification number entered and the name of the ECU family associated with it arealready highlighted in the window. All you have to do is select one or more ECU addresses by meansof their integration position(s) (see also "7.1.2 Function: Selecting a ZUSB number").

Select one, several or all of the integration positions from the "Integration position " list in line withthe standard Windows conventions.

• If you click "Cancel ", the ZB number entered and integration position selected are discarded.

• If you click "OK", the ZB number is adopted and displayed together with the correspondinghardware number as status information.

WinKFPTUser's Guide

Date: 20.10.04


7.1.2 Function: Selecting a ZUSB number

You start the function for selecting a ZUSB number either by clicking the "Choose ZUSB " button orby pressing function key <F2> on the keyboard.

When you activate this function, a dialog box opens in which you select an ECU family, assemblyidentification number and integration position(s) (see "Fig. 7-3: Dialog window for choosing an ECUfamily, assembly identification number and integration position").

This dialog box contains three lists:• "ECU family "

- which contains a list of ECU families or assembly line data sets that exist

• "ZB Number "- which contains the assembly identification numbers that belong to the ECU family selected

• "Integration position "- which contains the integration positions that belong to the ECU family selected, through whose

selection the ECU address is specified. Control units that can be installed more than once inthe same car are distinguished between only by means of their ECU address or integrationposition.

The "ECU family " list contains only those ECU families for which the logistics file <ecufam>.DAT,containing at least one ZB number, is present in the respective directories \<root>\data\<ecufam> 9.

The "ZB Number" list contains all the assembly identification numbers present in the <ecufam>.DATfile that belong to the ECU family selected.

The "Integration position" list contains all the integration positions present in the\<root>\data\gdaten\ INFO.ENG file that belong to the ECU family selected.


• If you click "Cancel ", the ZB number and integration position selected are discarded.

• If you click "OK", the ZB number is adopted and displayed together with the correspondinghardware number as status information.


WinKFPTUser's Guide

Date: 20.10.04


7.1.3 Function: Updating an Assembly Identification

You start the function for updating an assembly identification either by clicking the "Update ZUSB "button or by pressing function key <F3> on the keyboard.

When you activate this function, a dialog box opens in which you select an ECU family andintegration position(s).

Fig. 7-1: Dialog box for updating an assembly identification

This dialog box contains two lists:• "ECU family "

- which contains a list of ECU families or assembly line data sets that exist

• "Integration position " - which contains the integration positions that belong to the ECU family selected, through whose

selection the ECU address is specified. Control units that can be installed more than once inthe same car are distinguished between only by means of their ECU address or integrationposition.

The "ECU family " list contains only those ECU families for which the logistics file <ecufam>.DAT,containing at least one ZB number, is present in the respective directories \<root>\data\<ecufam> 9.


WinKFPTUser's Guide

Date: 20.10.04


The "Integration position" list contains all the integration positions present in the\<root>\data\gdaten\ INFO.GER file that belong to the ECU family selected.


• If you click "Cancel ", the ECU family and integration position selected are discarded.

• If you click "OK", the selection is adopted and the corresponding pieces of status information(description files, ECU address and diagnosis protocol) displayed.

WinKFPTUser's Guide

Date: 20.10.04


7.1.4 Function: Entering a Vehicle Identification N umber

You start the function for entering a vehicle identification number either by clicking the "Enter VIN "button or by pressing function key <F4> on the keyboard.

This function button is only displayed if KOMFORT_MIT_AIF=ON is set in the configuration fileWINKFPT.INI

When you activate this function, a dialog box opens in which you enter the vehicle identificationnumber.

Fig. 7-1: Dialog box for entering the vehicle identification number

Note!The vehicle identification number must consist of 7 or 17 alphanumeric characters otherwise thefollowing error message appears which you have to acknowledge.

Fig. 7-2: Error message displayed when an incorrect vehicle identification number is entered

WinKFPTUser's Guide

Date: 20.10.04


• If you click "Cancel ", the vehicle identification number entered is discarded.

• If you click "OK", the vehicle identification number is adopted and displayed as status information.

Note:With respect to the functions "Enter ZUSB" and "Choose ZUSB", entry of a vehicle identificationnumber is mandatory if KOMFORT_MIT_AIF=ON is set in WINKFPT.INIFlash programming of the control unit is otherwise not possible in this case.

With respect to the function "Update ZUSB", it is not necessary to enter a vehicle identificationnumber by means of the "Enter VIN" function because in this case the vehicle identification numberfrom the last UIF entry read out beforehand is used for the new UIF entry.If you nevertheless enter a vehicle identification number by means of "Enter VIN", this number isentered in the new UIF.

WinKFPTUser's Guide

Date: 20.10.04


7.1.5 Function: Done (Comfort Mode)

The "Done" function completes and ends input and selection of the job data in the programmingsettings phase of Comfort mode.

You start the function either by clicking the "Done" button or by pressing function key <F8> on thekeyboard.

Activating this function leads to a switch of function phase:

• If no entries have been made, the program switches to the function start menu (see Fig. 6-1:Function start menu of WinKFPT).

• If you have entered valid job data by means of "Enter ZUSB " or "Choose ZUSB ", the programswitches to the "Program " function in the function menu of the programming execution phase ofComfort mode.Note:If, with KOMFORT_MIT_AIF=ON set in the configuration file WINKFPT.INI, no vehicle identificationnumber is entered, it is not possible to flash program the control unit, and only the general functionsare displayed following switching of the function phase (see Fig. 9-1: Function menu with thefunction buttons "Special" and "Diagnosis").

• If you have entered valid job data by means of "Update ZUSB ", the program switches to the "Prog.ZB-Update " function in the function menu of the programming execution phase of Comfort mode.

WinKFPTUser's Guide

Date: 20.10.04


7.2 Functions of the Programming Execution Phase in Comfort Mode

The following status information is displayed when the switch is made to the programming executionphase of Comfort mode:

• "ECU address/Integration position"• "Vehicle identification number"10

• "Assembly identification number"• "Hardware number"• "HW interface"• "Diagnosis protocol"• "PABD"• "P-SGBD"

The following functions are available in the programming execution phase of Comfort mode:• ECU flash programming (depends on the job data)• ECU flash programming update (depends on the job data)• Calling of general functions (Special, Diagnosis)• Ending of the programming execution phase of Comfort mode by switching to the programming

settings phase of Comfort mode or Expert mode.

Fig. 7-1: Programming execution phase in Comfort mode

10 Vehicle identification number is displayed only if the KOMFORT_MIT_AIF entry in WINKFPT.INI is set to ON.

WinKFPTUser's Guide

Date: 20.10.04


7.2.1 Function: Flash Programming

A control unit is flashed by activating the "Program " function.

The function button is activated only after successful input of the ZUSB number by means of the"Enter ZUSB" or "Choose ZUSB" function and/or of the vehicle identification number (withKOMFORT_MIT_AIF=ON set in WINKFPT.INI) in the programming settings phase of Comfort mode,too.

You start the function either by clicking the "Program" button or by pressing function key <F3> on thekeyboard.

This function button/key starts flash programming of one or more control units in Comfort mode.

If KOMFORT_MIT_AIF=ON is set in configuration file WINKFPT.INI, the following prompt appearsbefore ECU flash programming starts:

Fig. 7-1: Indication of the number of times the UIF can be programmed

Note:The number of times the UIF can be programmed is taken from the PABD.

WinKFPTUser's Guide

Date: 20.10.04


• If you click "Cancel ", programming is aborted.

• If you click "OK", programming is started.

Fig. 7-2: ECU flash programming in Comfort mode

The status of the programming procedure is indicated by a progress bar (0 - 100 %) and as apercentage display in the blue menu status line.If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programmingvoltage" is displayed in the top right-hand corner.

WinKFPTUser's Guide

Date: 20.10.04


At the end of the ECU flash programming procedure, the message <<Programming OK>> appears:

Fig. 7-3: Message displayed when ECU programming has been successful

The user info field is not programmed only if the "KOMFORT_MIT_AIF" switch in the WINKFPT.INIfile is explicitly set to OFF.

In the event of multiple selection of control units, the job data for the next programming procedure isdisplayed automatically after each programming procedure, and programming is started again byclicking the "Program" function button (or pressing <F3>).This means it is possible to abort or to change settings (e.g. HW interface or diagnosis protocol) atany time between the individual programming procedures. At the end of the multiple programmingprocedure, the message <<Multiple programming finished>> appears:

Fig. 7-4: Message displayed when multiple programming has been successful

WinKFPTUser's Guide

Date: 20.10.04


7.2.2 Function: Programming Update

A control unit is flashed to the latest assembly identification by activating "Prog. ZB-Update ".

The function button is activated only following successful input of the job data by means of the"Update ZUSB" function in the programming settings phase of Comfort mode.

You start the function either by clicking the "Prog. ZB-Update" button or by pressing function key<F3> on the keyboard.

This function button starts updating of a control unit to the latest assembly identification. Updating toan incompatible hardware release by means of BSU (boot sector update) is also borne in mind.

For this purpose, the vehicle identification number and the assembly identification number are readout of the last UIF entry in the control unit.In addition to this assembly identification number, the latest (current) assembly identification numberis read from the file \<root>\data\<ecufam>\ <ecufam>.his (= ZUSB history). A switch to a differentECU family and therefore to a new, corresponding ZUSB history is possible.These two assembly identification numbers are displayed in a dialog box that has to beacknowledged:

Fig. 7-1: Dialog box displaying the ZB number from the ECU and the current ZB number

• If you click "No" , programming to the latest assembly identification number is aborted.

• If you click "Yes" , programming (updating) to the latest assembly identification number is started.

WinKFPTUser's Guide

Date: 20.10.04


If KOMFORT_MIT_AIF=ON is set in configuration file WINKFPT.INI, the following prompt appearsbefore ECU flash programming starts:

Fig. 7-2: Indication of the number of times the UIF can be programmed


• If you click "Cancel ", programming is aborted.

• If you click "OK", programming is started.

The status of the programming procedure is indicated by a progress bar (0 - 100 %) and as apercentage display in the blue menu status line."Fig. 7-2: ECU flash programming in Comfort mode").If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programmingvoltage" is displayed in the top right-hand corner.

WinKFPTUser's Guide

Date: 20.10.04


At the end of the ZUSB update programming procedure, the message <<ZUSB-Update programmingOK>> appears:

Fig. 7-3: Message displayed when ZUSB update programming has been successful

The user info field is not programmed only if the "KOMFORT_MIT_AIF" switch in the WINKFPT.INIfile is explicitly set to OFF.

In the event of multiple selection of control units, the job data for the next programming procedure isdisplayed automatically after each programming procedure, and programming is started again byclicking the "Prog. ZB-Update" function button (or pressing <F3>).This means it is possible to abort or to change settings (e.g. HW interface or diagnosis protocol) atany time between the individual programming procedures.At the end of the multiple programming procedure, the message <<Multiple ZUSB-Updateprogramming finished>> appears:

Fig. 7-4: Message displayed when multiple ZUSB update programming has been successful

WinKFPTUser's Guide

Date: 20.10.04


8 FUNCTION PHASES IN EXPERT MODE

The functions of Expert mode are divided into three phases:� Functions of programming settings phase Level 1� Functions of programming settings phase Level 2� Functions of the programming execution phase.� The functions of programming settings phase Level 1 are used to select the description files.� The functions of programming settings phase Level 2 are used to enter the ECU address and select

data set files.� The functions of the programming execution phase are used for flash programming a program data

set or data data set.

Whether or not you can switching function phase depends on the scope of the job data you haveentered.

Function phase Functions Entries required for switching to the level


phase Level 1

• Loading a PABD

• Loading a P-SGBD

• Ending the function phase

No entries,

just PABD,

just P-SGBD


phase Level 2

• Entering an ECU address

• Loading a data set – NAAB file• Loading a data set – program file

• Loading a data set – data file

• Ending the function phase

Both description files

PABD and P-SGBD

Programming

execution phase

• Programming a NAAB data set• Programming a program data set

• Programming a data data set

• Special

• Diagnosis

Description files (PABD and P-SGBD), data

set files (for Program and/or Data),

<ECU address>

Table 8-1: Function phases of Expert mode

WinKFPTUser's Guide

Date: 20.10.04


8.1 Functions of Programming Settings Phase Level 1 in Expert Mode

The following functions are available in programming settings phase Level 1 of Expert mode:

• Loading a PABD• Loading a P-SGBD• Ending programming settings phase Level 1.

Fig. 8-1: Functions of programming settings phase Level 1 in Expert mode

WinKFPTUser's Guide

Date: 20.10.04


8.1.1 Function: Loading a PABD

You start the function for selecting a PABD either by clicking the "PABD" button or by pressingfunction key <F1> on the keyboard.

When you activate this function, a dialog box opens in which you select a PABD.

Fig. 8-1: Dialog box for selecting a PABD

The source code of the flash sequence description files (PABDs) is available in the INPA scriptlanguage.

For processing in WinKFPT, files can be available in source code or in compiled form; the compiledform is generated from the source code by means of the CABI compiler.Since the functionality of the CABI compiler is integrated in the COAPI, WinKFPT can process bothforms of a PABD.

The criterion by which source code and the compiled form can be distinguished is the extension of thePABD file name, e.g.:• 17EK924.IPS � PABD in source code• 17EK924.IPO � PABD in compiled form .

WinKFPTUser's Guide

Date: 20.10.04


This dialog box displays either all the files in the <root>\SGDAT 11 directory that have the extensionIPS or the extension IPO.This depends on the CabdFormat configuration set in WINKFPT.INI and COAPI.INI (see "3.4.1Configuration in COAPI.INI", "3.4.2 Configuration in WINKFPT.INI").

• If you click "Cancel ", selection of a PABD is aborted. The PABD selected beforehand remainsselected.

• If you click "OK", the PABD is adopted and "PABD" is displayed as status information.

After you have selected a PABD, WinKFPT automatically checks whether a P-SGBD has alreadybeen selected and is displayed as status information.�

P-SGBD not selected: the function menu for programming settings phase Level 1 remainsactive.�

P-SGBD selected: the program switches to the function menu for programming settings phaseLevel 2.By selecting a PABD and P-SGBD, you implicitly select a control unit and the program checkswhether the control unit supports more than one diagnosis protocol.If this is the case, the menu option "Diagnosis protocol" is activated and the default diagnosisprotocol is displayed as status information (see "5.3.2 Selecting (Choosing) a DiagnosisProtocol").


WinKFPTUser's Guide

Date: 20.10.04


8.1.2 Function: Loading a P-SGBD

You start the function for selecting a P-SGBD either by clicking the "P-SGBD" button or by pressingfunction key <F2> on the keyboard.

When you activate this function, a dialog box opens in which you select a P-SGBD.

Fig. 8-1: Dialog box for selecting a P-SGBD

This dialog box displays all the files in the <ediabas>\ECU\ 12 directory with the extension PRG.

• If you click "Cancel ", selection of a P-SGBD is aborted. The P-SGBD selected beforehand remainsselected.

• If you click "OK", the P-SGBD is adopted and "P-SGBD" is displayed as status information.

12 <ediabas> = installation directory for EDIABAS interface

WinKFPTUser's Guide

Date: 20.10.04


After you have selected a P-SGBD, WinKFPT automatically checks whether a PABD has alreadybeen selected and is displayed as status information.�

PABD not selected: the function menu for programming settings phase Level 1 remains active.� PABD selected: the program switches to the function menu for programming settings phase

Level 2.By selecting a PABD and P-SGBD, you implicitly select a control unit and the program checkswhether the control unit supports more than one diagnosis protocol.If this is the case, the menu option "Diagnosis protocol" is activated and the default diagnosisprotocol is displayed as status information (see "5.3.2 Selecting (Choosing) a DiagnosisProtocol").

WinKFPTUser's Guide

Date: 20.10.04


8.2 Functions of Programming Settings Phase Level 2 in Expert Mode

The following functions are available in programming settings phase Level 2 of Expert mode:• Loading an ECU address• Loading a data set – Data file• Loading a data set – Program file• Loading a data set – NAAB file• Ending programming settings phase Level 2.

Fig. 8-1: Programming settings phase Level 2 in Expert mode

WinKFPTUser's Guide

Date: 20.10.04


8.2.1 Function: Loading an ECU address

You start the function for entering an ECU address either by clicking the "ECU Address " button or bypressing function key <F3> on the keyboard.

When you activate this function, a dialog box opens in which you enter an ECU address.

Fig. 8-1: Dialog box for an ECU address

Note!The ECU address must consist of 2 digits and be hexadecimal otherwise an error message appearswhich you have to acknowledge and the dialog box is closed.

• If you click "Cancel ", input of an ECU address is aborted and the ECU address entered beforehandremains entered.

• If you click "OK", input of the ECU address is completed.This involves the program calling a P-SGBD job in order to set the ECU address globally.If this job is present in the P-SGBD, the ECU address you have entered is displayed as statusinformation under "ECU address/integration position ".This, however, does not guarantee that the ECU can be addressed via this address because thereis so far no communication with the control unit for this job.A control unit that is addressed using an incorrect address does not answer and an error messageto this effect is displayed.

If the P-SGBD does not contain a job for setting the ECU address, the address is fixed in the P-SGBD and is the text "P-SGBD using internal address" is displayed as status information under"ECU address/integration position" .

WinKFPTUser's Guide

Date: 20.10.04


8.2.2 Function: Loading a Data Set – NAAB File

NAAB:Boot update description file. This is a data file that is flashed to the program area of an ECU andcontains the program for boot sector update and the boot sector itself. The program executes the bootsector update immediately following an ECU reset.

You start the function for selecting a NAAB data set either by clicking the "NAAB file " button or bypressing function key <F6> on the keyboard.

When you activate this function, a dialog box opens in which you select a NAAB data set:

Fig. 8-1: Dialog box for selecting a NAAB data set

This dialog box displays all the files in the \<root>\data\develop 12 directory with the extensions 0BAand BAF.

• If you click "Cancel ", selection of a NAAB data set is aborted and the NAAB data set selectedbeforehand remains entered.

• If you click "OK", selection of a NAAB data set is completed and displayed as status information in"NAAB file ".


WinKFPTUser's Guide

Date: 20.10.04


Once the NAAB data set has been selected, the UIF is read.

The following error situations are possible:

• No ECU address has been entered:If the description files selected require input of an ECU address (external address), an errormessage to this effect is displayed (see "Fig. 8-1: Error message if no ECU address has beenentered in Expert mode").The data set remains selected. It is not possible to switch to the programming execution phase ofExpert mode unless you have entered an ECU address.

• ECU address entered is wrong:The control unit can not answer and an error message to this effect is displayed.It is possible to switch to the programming execution phase of Expert mode.

• Control unit is not connected or does not answer:The control unit does not answer and an error message to this effect is displayed.

WinKFPTUser's Guide

Date: 20.10.04


8.2.3 Function: Loading a Data Set – Program File

You start the function for selecting a program data set either by clicking the "Program file " button orby pressing function key <F5> on the keyboard.

When you activate this function, a dialog box opens in which you select a program data set:

Fig. 8-1: Dialog box for selecting a program data set

This dialog box displays all the files in the \<root>\data\develop 12 directory with the extensions 0PAand PAF.


WinKFPTUser's Guide

Date: 20.10.04


• If you click "Cancel ", selection of a program data set is aborted and the program data set selectedbeforehand remains entered.

• If you click "OK", selection of a program data set is completed and displayed as status informationin "Program file ".

Once the program data set has been selected, WinKFPT checks whether the data set matches thecontrol unit.To this end, the hardware reference is read out of the control unit and compared with the reference ofthe data set (keyword: $REFERENZ).



• ECU address entered is wrong:The control unit can not answer and an error message to this effect is displayed.Note:Since the data set remains selected and consequently does not have to be reselected once theECU address has been corrected, you should select the data set once again so that comparison ofthe references is not unintentionally suppressed.It is possible to switch to the programming execution phase of Expert mode.

• Control unit is not connected or does not answer:The control unit does not answer and an error message to this effect is displayed.Note:Since the data set remains selected and consequently does not have to be reselected once thecontrol unit has been properly connected, you should select the data set once again so thatcomparison of the references is not unintentionally suppressed.It is possible to switch to the programming execution phase of Expert mode.

WinKFPTUser's Guide

Date: 20.10.04


• Hardware reference from the ECU and reference from the data set do not match up:The following error message is displayed:

Fig. 8-2: Error message if references in ECU and program data set do not match up

This error message indicates the data set reference after "DS:" and the control unit reference after"ECU:" .

It is possible to switch to the programming execution phase of Expert mode.

The program data set can be programmed even if the references do not match up.N.B.:The control unit may be unusable following programming and have to be submitted for recycling.

WinKFPTUser's Guide

Date: 20.10.04


8.2.4 Function: Loading a Data Set – Data File

You start the function for selecting a data data set either by clicking the "Data file " button or bypressing function key <F4> on the keyboard.

When you activate this function, a dialog box opens in which you select a data data set(characteristic-diagram data):

Fig. 8-1: Dialog box for selecting a data data set

This dialog box displays all the files in the \<root>\data\develop 13 directory with the extensions 0DAand DAF.


WinKFPTUser's Guide

Date: 20.10.04


• If you click "Cancel ", selection of a data data set is aborted and the data data set selectedbeforehand remains entered.

• If you click "OK", selection of a data data set is completed and displayed as status information in"Data file ".

Once the data data set has been selected, WinKFPT checks whether the data set matches the controlunit.To this end, the data reference is read out of the control unit and compared with the reference of thedata set (keyword: $REFERENZ).



• ECU address entered is wrong:The control unit can not answer and an error message to this effect is displayed.Note:Since the data set remains selected and consequently does not have to be reselected once theECU address has been corrected, you should select the data set once again so that comparison ofthe references is not unintentionally suppressed.It is possible to switch to the programming execution phase of Expert mode.

• Control unit is not connected or does not answer:The control unit does not answer and an error message to this effect is displayed.Note:Since the data set remains selected and consequently does not have to be reselected once thecontrol unit has been properly connected, you should select the data set once again so thatcomparison of the references is not unintentionally suppressed.It is possible to switch to the programming execution phase of Expert mode.

WinKFPTUser's Guide

Date: 20.10.04


• Data reference from the ECU and reference from the data set do not match up:The following error message is displayed:

Fig. 8-2: Error message if references in ECU and data data set do not match up

This error message indicates the data set reference after "DS:" and the control unit reference after"ECU:" .

It is possible to switch to the programming execution phase of Expert mode.

The data data set can be programmed even if the references do not match up.N.B.:The control unit may be unusable following programming and have to be submitted for recycling.

WinKFPTUser's Guide

Date: 20.10.04


8.2.5 Function: Done (Expert Mode)

The "Done" function completes and ends input and selection of the job data in programming settingsphase Levels 1 and 2 of Expert mode.

You start the function either by clicking the "Done" button or by pressing function key <F8> on thekeyboard.

Activating this function leads to a switch of function phase:

• If no entries have been made, the program switches to the function start menu (see Fig. 6-1:Function start menu of WinKFPT).

• If only a PABD has been selected, the program switches to the function start menu.

• If only a P-SGBD has been selected, the program switches to the function start menu.

• If a PABD and P-SGBD have been selected, the program checks whether an ECU address has tobe entered.If an ECU address is not required, the text "P-SGBD using internal address" is displayed asstatus information under "ECU address/integration position" .If an ECU address is required and one has not been entered, the following error message isdisplayed:

Fig. 8-1: Error message if no ECU address has been entered in Expert mode

When you acknowledge the error message, the program switches to the function start menu.PABD and P-SGBD remain selected and you can now enter the ECU address.

• If a PABD, P-SGBD and ECU address have been selected, only the general functions are madeavailable for use (see "9 General Functions").

• If a PABD, P-SGBD, ECU address and a data set for program and/or data have been selected, theprogram switches to the function menu of the programming execution phase of Expert mode.

WinKFPTUser's Guide

Date: 20.10.04


8.3 Functions of the Programming Execution Phase in Expert Mode

The following status information is displayed when the switch is made to the programming executionphase of Expert mode:• "ECU address"• "Vehicle identification number"10

• "HW interface"• "Diagnosis protocol"• "Data file"• "Program file"• "NAAB file"• "PABD"• "P-SGBD"

The following functions are available in the programming execution phase of Expert mode:• NAAB programming (BSU) (depends on the job data)• Program programming (depends on the job data)• Data programming (depends on the job data)• Calling of general functions (Special, Diagnosis)• Ending of the programming execution phase of Expert mode by switching to the programming

settings phase of Comfort mode or Expert mode.

10 Vehicle identification number is displayed only if the EXPERT_MIT_AIF entry in WINKFPT.INI is set to ON.

WinKFPTUser's Guide

Date: 20.10.04


Fig. 8-1: Programming execution phase in Expert mode

8.3.1 Function: Programming a NAAB Data Set

You start the function for programming a NAAB data set either by clicking the "Prog. NAAB " button orby pressing function key <F3> on the keyboard.

The function button is activated only following successful selection of an NAAB data set file by meansof the "NAAB file" function in programming settings phase Level 2 of Expert mode.

WinKFPTUser's Guide

Date: 20.10.04


The status of the programming procedure is indicated by a progress bar (0 - 100 %) and as apercentage display in the blue menu status line.If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programmingvoltage is displayed in the top right-hand corner.

At the end of the ECU flash programming procedure and exchange of the boot sector, the message<<Bootsektorupdate OK>> appears:

Fig. 8-1: Message displayed following successful ECU flashing programming in Expert mode

WinKFPTUser's Guide

Date: 20.10.04


8.3.2 Function: Programming a Program Data Set

You start the function for programming a program data set either by clicking the "Prog. Program "button or by pressing function key <F3> on the keyboard.

The function button is activated only following successful selection of a program data set file bymeans of the "Program file" function in programming settings phase Level 2 of Expert mode.

Note:The user info field is programmed only if the configuration settings EXPERT_MIT_AIF andAIF_SCHREIBEN_NACH_PROGRAMM in WINKFPT.INI are set to ON.Note:If a UIF is to be programmed, the dialog box for entering the vehicle identification number appears(see "7.1.4 Function: Entering a Vehicle Identification Number").Without a vehicle identification number, programming is not possible in this case.

The following prompt appears once you have entered the vehicle identification number:

Fig. 8-1:Indication of the number of times the UIF can be programmed


WinKFPTUser's Guide

Date: 20.10.04


The status of the programming procedure is indicated by a progress bar (0 - 100 %).If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programmingvoltage" is displayed in the top right-hand corner.

Fig. 8-2: ECU flash programming in Expert mode

At the end of the ECU flash programming procedure, the message <<Programming OK>> appears:

WinKFPTUser's Guide

Date: 20.10.04


Fig. 8-3: Message displayed following successful ECU flashing programming in Expert mode

8.3.3 Function: Programming a Data Data Set

You start the function for programming a data data set either by clicking the "Prog. Data " button or bypressing function key <F5> on the keyboard.

The function button is activated only following successful selection of a data data set file by means ofthe "Data file" function in programming settings phase Level 2 of Expert mode.

Note:The user info field is programmed only if the configuration settings EXPERT_MIT_AIF andAIF_SCHREIBEN_NACH_DATEN in WINKFPT.INI are set to ON.Note:If a UIF is to be programmed, the dialog box for entering the vehicle identification number appears(see "7.1.4 Function: Entering a Vehicle Identification Number").Without a vehicle identification number, programming is not possible in this case.

The following prompt appears once you have entered the vehicle identification number:

Fig. 8-1:Indication of the number of times the UIF can be programmed


WinKFPTUser's Guide

Date: 20.10.04


The status of the programming procedure is indicated by a progress bar (0 - 100 %) (see "Fig. 8-2:ECU flash programming in Expert mode").If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programmingvoltage" is displayed in the top right-hand corner.

At the end of the ECU flash programming procedure, the message <<Programming OK>> appears(see "Fig. 8-3: Message displayed following successful ECU flashing programming in Expert mode").

WinKFPTUser's Guide

Date: 20.10.04


9 GENERAL FUNCTIONS

The general functions of WinKFPT are divided up into the following groups:• Special Functions• Diagnosis Functions

You select a group by clicking one of the following function buttons or pressing the correspondingfunction key on the keyboard:• "Special "• "Diagnosis "

Fig. 9-1: Function menu with the function buttons "Special " and "Diagnosis "

Since calling a general function always involves communicating with an ECU, a minimum amount ofjob data must have been entered in the active operating mode of WinKFPT.

The function buttons for the general functions are only displayed:

• once programming settings phase Level 1 or 2 of Expert mode has been completed and at leastone PABD, P-SGBD and ECU address (ECU address only if the P-SGBD uses an external address)have been selected/entered (see "8.1 Functions of Programming Settings Phase Level 1 in ExpertMode" and "8.2 Functions of Programming Settings Phase Level 2 in Expert Mode").

• once the programming settings phase of Comfort mode has been completed and a ZUSB numberand ECU address/integration position have been selected/entered by means of one of the followingfunctions: "Enter ZUSB" , "Choose ZUSB" or "Update ZUSB" (see "7.1 Functions of theProgramming Settings Phase in Comfort Mode").

WinKFPTUser's Guide

Date: 20.10.04


9.1 Special Functions

When you click the "Special" function button (or press <F3>) in Expert or Comfort mode, thefunction menu with the function buttons for calling the special functions of WinKFPT is opened:

Fig. 9-1: Function menu for the special functions

This function menu contains buttons for activating the following functions:• Reading the UIF• Reading the ECU baudrates• Reading and writing the calibration values• VS20/DS2 Mode• EWS alignment• Exiting the Special function menu

WinKFPTUser's Guide

Date: 20.10.04


9.1.1 Function: Reading the UIF

You start the function for displaying the UIF entries of a control unit either by clicking the "Read UIF"button in the Special function menu or by pressing function key <F1> on the keyboard.

When you activate this function, all the user info field (UIF) entries of the control unit are read out anddisplayed by the following PABD job:• SG_AIF_LESEN

Prerequisite for this is a valid UIF entry in the control unit.

The contents of the UIF display dialog are written to the file AIF_<Interface>_<Unit>.OUT in the\<root> \BIN directory.The contents of the AIF_<Interface>_<Unit>.OUT file are overwritten every time "Read UIF" isactivated.

The file name is displayed in the header of the UIF display dialog.

WinKFPTUser's Guide

Date: 20.10.04


Fig. 9-1: Display dialog for the Special function "Read UIF"

You close the UIF display dialog by clicking "OK" .

WinKFPTUser's Guide

Date: 20.10.04


9.1.2 Function: Reading the ECU Baudrates

You start the function for displaying the ECU baudrates of a control unit either by clicking the "ECUbaudrates " button in the Special function menu or by pressing function key <F2> on the keyboard.

When you activate this function, all the possible baudrates of the control unit are read out anddisplayed by the following PABD job:• BAUDRATE_LESEN

The contents of the ECU baudrates display dialog are written to the file BD_<Interface>_<Unit>.OUTin the \<root> \BIN directory.The contents of the BD_<Interface>_<Unit>.OUT file are overwritten every time "ECU baudrates " isactivated.

This functionality is no longer supported by standard PABD jobs.

WinKFPTUser's Guide

Date: 20.10.04


If you call "ECU baudrates" for control units with standard description files, the following errormessage appears:

Fig. 9-1: Error message displayed when you call "ECU baudrates "

WinKFPTUser's Guide

Date: 20.10.04


9.1.3 Function: Reading and Writing the Calibration Values

You start the function for reading and writing the calibration values of a control unit either by clickingthe "Calibration values " button in the Special function menu or by pressing function key <F3> on thekeyboard.

When you activate this function, the submenu for reading and writing the calibration values of thecontrol unit opens.

Fig. 9-1: Submenu for reading and writing the calibration values

This function enables you to read specific data (calibration values) out of a control unit and write it toanother control unit.

Procedure for transferring calibration values:• Connect the control unit from which the calibration values are to be read.

• Click the "Read Calib. " button or press <F1> on the keyboard.The calibration values are read out of the ECU and buffered in a temporary file.The "Write Calib. " function button is now active.

• Connect the control unit to which the calibration values are to be written.

• If necessary, select the HW interface and diagnosis protocol for the second control unit.

• Click the "Write Calib. " button.The calibration values are read out of the temporary file and written to the ECU.A message confirming that the data has been successfully transferred is then displayed.

You close the submenu for calibration values either by clicking the "Done" button

or by pressing function key <F8> on the keyboard.

The submenu for calibration values is closed and the Special function menu is displayed again.

WinKFPTUser's Guide

Date: 20.10.04


9.1.4 Function: VS20/DS2 Mode

You start the function for selecting VS20/DS2 mode either by clicking the "VS20/DS2-Mode" buttonin the Special function menu or by pressing function key <F4> on the keyboard.

When you activate this function, WinKFPT switches to the submenu for VS20/DS2 mode.By activating "VS20 Mode" or "DS2 Mode" from this submenu, the control unit connected can beswitched to VS20 or DS2 mode by means of the PABD job VS20_MODE or D2 MODE.

This functionality is no longer supported by standard PABD jobs.

If you call "VS20 Mode" or "DS2 Mode" for control units with standard description files, the followingerror message appears:

Fig. 9-1: Error message displayed when you call "VS20 Mode" or "DS2 Mode"

WinKFPTUser's Guide

Date: 20.10.04


9.1.5 Function: EWS Alignment

You start the function for EWS alignment either by clicking the "EWS Alignment " button in theSpecial function menu or by pressing function key <F5> on the keyboard.

This functionality is no longer supported.

When you call "EWS Alignment ", the following message appears:

Fig. 9-1: Message displayed when you call "EWS Alignment "

9.1.6 Function: Done

You close the Special function menu either by clicking the "Done" button in the Special functionmenu


When you activate this function, the Special function menu is closed and WinKFPT switches back tothe main menu or to the function phase of the operating mode from which the Special function menuwas started.

WinKFPTUser's Guide

Date: 20.10.04


9.2 Diagnosis Functions

When you click the "Diagnosis" function button (or press <F4>) in Expert or Comfort mode, thefunction menu with the function buttons for calling the diagnosis functions of WinKFPT is opened:

Fig. 9-1: Menu for the diagnosis functions

This menu contains buttons for activating the following functions:• Displaying the ECU status• Reading the ECU identification• Reading the ECU internal temperature• Exiting the Diagnosis menu

WinKFPTUser's Guide

Date: 20.10.04


9.2.1 Function: Displaying the ECU Status

You start the function for displaying the ECU status of a control unit either by clicking the "ECUStatus " button in the Diagnosis function menu or by pressing function key <F1> on the keyboard.

When you activate this function, the following data is read out of the control unit and displayed:• Data reference• Hardware reference• Supplier info field (ZIF)• Backup of the supplier info field• Programming status (ECU status)

The data is read out of the control unit by the following PABD jobs:• DATEN_REFERENZ• HW_REFERENZ• ZIF• ZIF_BACKUP• SG_STATUS_LESEN

The contents of the ECU status display dialog are written to the file REF_<Interface>_<Unit>.OUT inthe \<root> \BIN directory.The contents of the REF_<Interface>_<Unit>.OUT file are overwritten every time "ECU Status " isactivated.

The file name is displayed in the header of the ECU status display dialog.

WinKFPTUser's Guide

Date: 20.10.04


Fig. 9-1: Display dialog for the ECU status

You close the ECU status display dialog by clicking "OK" .

WinKFPTUser's Guide

Date: 20.10.04


9.2.2 Function: Reading the ECU Identification

You start the function for displaying the identification of a control unit either by clicking the "ECUIdent " button in the Diagnosis function menu or by pressing function key <F2> on the keyboard.

When you activate this function, the identification data of the control unit is read out and displayed bythe following PABD jobs:• SG_IDENT_LESEN• SG_PHYS_HWNR_LESEN

The contents of the ECU identification display dialog are written to the fileIDENT_<Interface>_<Unit>.OUT in the \<root> \BIN directory.The contents of the IDENT_<Interface>_<Unit>.OUT file are overwritten every time "ECU Ident " isactivated.

The file name is displayed in the header of the ECU identification display dialog.

Fig. 9-1: Display dialog for the ECU identification

You close the ECU identification display dialog by clicking "OK" .

WinKFPTUser's Guide

Date: 20.10.04


9.2.3 Function: Reading the ECU Internal Temperatur e

You start the function for displaying the internal temperature of a control unit either by clicking the"ECU intern. Temp " button in the Diagnosis function menu or by pressing function key <F3> on thekeyboard.

When you activate this function, the internal temperature of the control unit is read out anddisplayed.The following standard PABD job is executed to read the internal temperature out of a control unit:• SG_INNENTEMP_LESEN

The contents of the ECU internal temperature display dialog are written to the fileINNENTMP_<Interface>_<Unit>.OUT in the \<root> \BIN directory.The contents of the INNENTMP_<Interface>_<Unit>.OUT file are overwritten every time "ECUintern. Temp " is activated.

The file name is displayed in the header of the ECU internal temperature display dialog.

Fig. 9-1: Display dialog for the ECU internal temperature

If the control unit does not support this function, the following message is displayed which you have toacknowledge:

<<ECU internal temperature not supported>>

You close the ECU internal temperature display dialog by clicking "OK" .

WinKFPTUser's Guide

Date: 20.10.04


9.2.4 Function: Done

You close the Diagnosis function menu either by clicking the "Done" button in the Diagnosis functionmenu


When you activate this function, the Diagnosis function menu is closed and WinKFPT switches backto the main menu or to the function phase of the operating mode from which the Diagnosis functionmenu was started.

WinKFPTUser's Guide

Date: 20.10.04


10 ERROR HANDLING IN WINKFPT

The process of flash programming an ECU with WinKFPT is very complex and depends on trouble-free interaction of the following components:• Hardware connection – Test computer ↔ Diagnosis HW interface ↔ ECU• Software connection – WinKFPT ↔ EDIABAS ↔ Diagnose interface driver ↔ ECU program

• Configuration of WinKFPT and COAPI

• Description files PABD and P-SGBD

• Logistics files

• Programming data files (PAF, DAF, etc.)

Each component contains a multitude of potential errors that must be trapped by WinKFPT anddisplayed to the user in a manner that enables him to recognize the cause from the error messagedisplayed and eliminate this cause on his own initiative.

The functions built into WinKFPT can be roughly split into two types: namely, into functions with andwithout COAPI calls. The manner in which errors that arise while executing these functions differsbetween the two types.

• Displaying errors in WinKFPT functions without COAPI calls:Display of informative error, diagnosis and info texts in appropriate message boxes.The texts are loaded dynamically from the text file "winkfpt.txt". It is possible to improve onthe explanatory power/correctness of the texts at any time without making changes toWinKFPT.

• Displaying errors in WinKFPT functions with COAPI calls:Each time an error occurs when a COAPI function is called, an error dialog is displayed. Thetop text box in this dialog contains a text that informs you of which active WinKFPT functionthe error has occurred in. The list box below this contains a detailed list of errors tracedthrough all the COAPI call levels run through.This error list should not be viewed as a list of different errors, rather as a breakdown of just asingle error, with the respective information that has been able to be established from therelevant COAPI call levels.The COAPI error texts are loaded dynamically from the text file "coapierr.txt".

WinKFPTUser's Guide

Date: 20.10.04


10.1 Displaying Errors

The figure below shows the "Normal view" display of a WinKFPT error associated with a defectiveCOAPI call.Switching to the "Extended view" is of no benefit to "normal" users. This view is intended merely asan additional debugging aid for WinKFPT or COAPI experts.

Fig. 10-1: Error display window in WinKFPT

In the example above, you can see that initialization of the COAPI by WinKFPT has failed.The list of errors from the respective COAPI call levels clearly shows the user which of the manyinitialization errors possible is the actual cause of the error.The first line of the error list displays the error message of the "lowest" COAPI call level and generallycontains comprehensive and crucial information for debugging purposes.In this case, the user must check whether the file "kfconfxx.da2" is present in the <root>\DATA\gdatendirectory, or whether or not he has read rights to it.

WinKFPTUser's Guide

Date: 20.10.04


10.2 Description and Elimination of Frequently Occu rring Errors

10.2.1 Errors When Starting WinKFPT

Error COAPI errors 1020, 3017, WinKFPT error 1

Time of occurrence • When starting WinKFPT.

Possible cause • A logistics file is missing in the ../data/gdaten directory. The errordialog tells you which file it is.

Debugging • Import an up-to-date assembly line data set with description files.• Copy the missing logistics file to the ../data/gdaten directory by

hand.

Error COAPI errors 4211, 4206, 1040, 3017, WinKFPT error 1


Possible cause • The ../data/gdaten directory contains a faulty and thereforeunconvertible logistics file. The error dialog (in particular error4206) tells you which file it is and in which line the error occurred.

Debugging • Import an up-to-date assembly line data set with correct descriptionfiles.

• Repair the faulty logistics file in the ../data/gdaten directory byhand.

Error WinKFPT error 300


Possible causes • The interface is already being used by a different program orpossibly by a different instance of WinKFPT.

• The default interface is not correctly set up in Ediabas.Debugging • Close the other application that is using the interface. (Application

may only be able to be seen in the task manager.)• Use a different application (e.g. TEOF in the Ediabas\bin directory)

to check whether the interface actually functions. If not: checkEdiabas and/or the interface driver.

WinKFPTUser's Guide

Date: 20.10.04


10.2.2 Errors When Importing Assembly Line Data

Error ECU directory is not displayed

Time of occurrence • When selecting an assembly identification number in Comfortmode.

Possible cause • Imported ECU directory does not contain any PABD/P-SGBDdescription files.

Debugging • Import an assembly line data set with description files.


Time of occurrence • When importing a single description file.

Possible causes • The description file could not be copied.• The file already exists in the target directory and is write-protected.• The file already exists in the target directory and has been opened

by an application.• The source file has no read rights.• No write rights in the target directory.

Debugging Depending on the cause:• Cancel write protection.• Close the application that has opened the file.• Check and adapt the file rights.


Time of occurrence • When importing an assembly line data set.

Possible cause • The assembly line data set does not contain a file of type<EcuFamilyname>.dat

Debugging • Fetch the correct assembly line data set (e.g. from Darwin).

WinKFPTUser's Guide

Date: 20.10.04


10.2.3 Errors When Entering Flash Data

Error COAPI errors 1065, 1000, WinKFPT error 106

Time of occurrence • When loading the suggested configuration after activating the<Expert mode> button.

• In Comfort mode when activating the [Done] button after selectinga ZB number and integration position.

Possible cause • The PABD from the configuration does not exist.

Debugging • Copy or import the PABD to the relevant Ediabas directory.

Error COAPI error 2000, WinKFPT error 106

Time of occurrence • When loading the suggested configuration after activating the<Expert mode> button.

• In Comfort mode when activating the [Done] button after selectinga ZB number and integration position.

Possible cause • The SGBD from the configuration does not exist.

Debugging • Copy or import the SGBD to the relevant Ediabas directory.

Error COAPI error 3000

Time of occurrence • In Comfort mode after entering a ZB number by hand.

Possible cause • This is no (correct) DAT file that contains the ZB number.

Debugging • Import the assembly line data set for the ECU family to which theZB number belongs.

WinKFPTUser's Guide

Date: 20.10.04


Error WinKFPT errors 500 to 503

Time of occurrence • When selecting the data file in Expert mode.• When selecting the program file in Expert mode.

Possible causes • The wrong ECU has been connected. The ECU identifier in thedata/program file selected does not match up with the identifier ofthe ECU connected.

• The wrong data/program file has been selected.Debugging • Determine whether the correct ECU is connected. If necessary,

connect the correct ECU.• Determine whether the correct data/program file has been selected.

If necessary, select the correct file.


Time of occurrence • When selecting the data file in Expert mode.• When selecting the program file in Expert mode.

Possible cause • An incorrect ECU address has been entered:• The control unit is not connected or communication is disrupted.

Debugging • Enter the correct ECU address.• Connect the ECU. Check whether communication is actually

possible.


Time of occurrence • When activating the [Program] button in Comfort mode.

Possible cause • An ECU family-specific logistics file (HWH or HIS) is not present.The error dialog tells you which file it is.

Debugging • Fetch the file by importing the assembly line data• or copy the file to the data directory by hand.

WinKFPTUser's Guide

Date: 20.10.04


Error COAPI errors 4209 or 4211, 4206, 1040, 3000


Possible cause • An ECU family-specific logistics file (DAT, HWH or HIS) is faulty.The error dialog (in particular error 4206) tells you which file it isand in which line the error occurred.

Debugging • Fetch an intact file by importing the assembly line data• or eliminate the error in the file by hand.

Error COAPI errors 4204, 1040


Possible cause • The file to be flashed does not exist. The error dialog (in particularerror 4204) tells you which file it is.

Debugging • Fetch the file by importing the assembly line data• or copy the file to the data directory by hand.

Error COAPI errors 4220 or 4209, 4221, 1040,

Time of occurrence • When selecting a program or data file in Expert mode.• When activating the [Program] button in Comfort mode.

Possible cause • The file to be flashed is faulty. The error dialog (in particular error4221) tells you which file it is and in which line the error occurred.

Debugging • Fetch an intact file by importing the assembly line data• or eliminate the error in the file by hand.

WinKFPTUser's Guide

Date: 20.10.04



Time of occurrence • In Expert mode after selecting PABD and SGBD, when activatingthe [Done] button.

Possible cause • The SGBD demands an external ECU address.

Debugging • Enter an ECU address.

Error WinKFPT error 102 or 103

Time of occurrence • In Expert mode when entering an ECU address.

Possible cause • A 2-digit, hexadecimal number has not been entered as the ECUaddress.

Debugging • Enter a correct hexadecimal number.


Time of occurrence • When entering a vehicle identification number (necessary whenUIF write is active).

Possible cause • The vehicle identification number was either not a 7-digit numberor not alphanumeric.

Debugging • Enter a correct vehicle identification number.

WinKFPTUser's Guide

Date: 20.10.04



Time of occurrence • When entering a ZB number in Comfort mode.

Possible cause • The ZB number was not a 7-digit number.

Debugging • Enter a 7-digit ZB number.

WinKFPTUser's Guide

Date: 20.10.04


10.2.4 Errors During Data Programming

Error CAPI error 2020 or 2021

Time of occurrence • When starting programming in both operating modes..

Possible causes • The ECU is not connected.• The HW interface is not fully installed.• The interface is not connected.

Debugging • Determine whether the ECU is connected.• Re-install the interface.• Determine whether the interface hardware is connected.


Time of occurrence • When starting programming by activating the <Prog. Data> button,following input of the PABD, P-SGBD and the program data set inExpert mode.

Possible causes • The wrong hardware interface has been selected.• The interface is not fully installed.• The interface is not connected.• The ECU is not connected.

Debugging • Determine whether the correct HW interface is displayed as statusinformation. If necessary, select the correct HW interface undermenu option Communication � HW interface.

• Re-install the interface.• Determine whether the interface hardware is connected.• Determine whether the ECU is connected.

WinKFPTUser's Guide

Date: 20.10.04


Error COAPI error 2064: Delete error in coding data (e.g. ZCS)

Time of occurrence • When starting programming by activating the <Prog. Data> button.

Possible cause • The last programming session was not successfully completed andterminated.

Debugging • The program must be flashed to the ECU again.To this end, enter PABD, P-SGBD and the program data set in Expertmode. Confirm the entries made in Expert mode by activating the<Done> button.Start flash programming of the control unit with the program data set byactivating the <Prog. Program> button.

WinKFPTUser's Guide

Date: 20.10.04


Glossary

CABD Coding sequence description file

CABI Coding sequence interpreter

COAPI Coding application interface

Comfort mode Programming after entering or selecting the job data, assemblyidentification number and control unit address, and the vehicleidentification number if UIF write is activated.

DAF Flash data image file

Expert mode Programming after selecting the PABD,P-SGBD, data file and/or program file.

HIS (Assembly) History file

IFH Interface handler

INPA Interpreter for test sequences

Interface Hardware unit for communication with control units, e.g. EDIC, ADS,MOST

IPO Extension of a sequence description file in object format

IPS Extension of a sequence description file in source format

NAAB Boot update description file. This is a data file that is flashed to theprogram area of an ECU and contains the program for boot sectorupdate and the boot sector itself.

PABD Flash sequence description file

PAF Flash program image file

P-SGBD Control unit description file for programming.

SGBD ECU description file

WinKFPTUser's Guide

Date: 20.10.04


UIF User info field

Unit Subunits of interfaces designated _, A, B, C, etc. if several interfacesof one type are installed in the same computer.

WDP An importable directory that contains all the files of an ECU familyrequired to flash control units from this ECU family with the aid of aBMW programming tool.

ZIF Supplier info field. The ZIF in the control unit indicates the state ofdevelopment of the control unit program.

ZUSB numberZB number

Assembly identification number

WinKFPTUser's Guide

Date: 20.10.04


Contents

AAssembly identification

updating 125

BBaudrates

reading 165

CCalibration values

reading 167COAPI

definition 187Comfort mode

definition 187import files 66

Configuration 39COAPI.INI 24, 39EDIABAS.INI 38, 39Expert mode 34, 35, 36, 37, 106WinKFPT 24WINKFPT.INI 28, 39

DData sets, data

import 76Data sets, program

import 76Diagnosis protocol 95

choosing (selecting) 98job

DIAGNOSEPROTOKOLL_SETZEN 99Job

DIAGNOSEPROTOKOLL_LESEN 98selecting 103, 104, 106

Directorystructure 19

EECU identification

reading 173ECU internal temperature

reading+ 174ECU status

displaying 171Expert mode

definition 187function phase 1 137import files 66

FFunction

choosing a ZUSB number 124displaying the ECU status 171ending function phase 0 129, 153entering a vehicle identification number127entering a ZUSB number 121EWS alignment 169flash programming in Comfort mode 131,134Flash programming in Comfort mode 157,159general functions 161loading a PABD 139loading a P-SGBD 141reading the calibration values 167reading the ECU baudrates 165reading the ECU identification 173reading the ECU internal temperature 174reading the UIF 163updating an assembly identification 125VS20/DS2 mode 168

Function phase 1Expert mode 137

HHW interface 20, 22, 24, 30, 31, 34, 38, 58,95, 96, 97, 133, 136, 185

choosing (selecting) 96

WinKFPTUser's Guide

Date: 20.10.04


IImport

data sets, files 76data sets, program 76files for Comfort mode 66files for Expert mode 66import menu 65PABD 80P-SGBD 78

Import menufiles 65

Initialization fileWINKFPT.INI 19

InstallationWinKFPT 18

Integration positionchoosing 124, 125

Interfacedefinition 187

IPOdefinition 187import file 80

IPSdefinition 187import file 80

PPABD

definition 187import 80loading 139

P-SGBDdefinition 187import 78loading 141

TTemporary files

INNENTMP.OUT 19

UUIF

definition 188reading 163

UNINSTALLWinKFPT 18

Unitdefining 96definition 188

VVehicle identification number

entering 127

ZZUSB number

choosing 124entering 121

handb-winkfpt32 5.1 v1.8 eng - coding e90codinge90.com/wp-content/uploads/2014/05/winkfp... · fig....

Documents