Está en la página 1de 191

WinKFPT

User's Guide
Page 1

WinKFPT 5.1
User's Guide
Version 1.8

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 2

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

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 3

5

WINKFPT'S MAIN MENU ........................................................................................................61
5.1 Display Menu ..........................................................................................................................61
5.1.1Display
5.1.2Display

CABI.ERR ......................................................................................................62
ERROR.LOG..................................................................................................62

5.1.3Display

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

5.1.4Display
5.1.5Display

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

5.1.6Display

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

5.1.7Display
5.1.8Display

API Trace File.................................................................................................63
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

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

..........3 Functions of the Programming Execution Phase in Expert Mode..........1Function: Loading a PABD ... 176 10.................. 178 10............................................... 173 9..................................... 171 9.................................................................... 141 8...2Function: Reading the ECU Identification............... 168 9.................................2.............1Function: Reading the UIF.................... 147 8....3..................... 180 10.................... 157 8............................................2 Description and Elimination of Frequently Occurring Errors................................................2 Errors When Importing Assembly Line Data ................................................................................................2................2 Diagnosis Functions ........ 153 8..1........3Function: Loading a Data Set – Program File ......2Function: Programming a Program Data Set ................. 178 10............................ 138 8...............................2Function: Loading a P-SGBD . 161 9.......................................3....................................................1........................ 154 8......................................5Function: Done (Expert Mode) ............................... 179 10....1........................1 Displaying Errors ......................................1..............................................8_eng.....1.......... 159 9 GENERAL FUNCTIONS....................................4Function: VS20/DS2 Mode .......................................04 File: Handb-winkfpt32(5...................2..........1......................................................doc Version: 1.... 169 9....................2................................................ 175 10 ERROR HANDLING IN WINKFPT......2Function: Reading the ECU Baudrates........... 145 8.........................................1 Special Functions....... 177 10................. 155 8.......1Function: Displaying the ECU Status ...............................................2.....................4 Errors During Data Programming ..................................................2....................................4Function: Done...............................................3Function: Reading the ECU Internal Temperature .............. 144 8..... 167 9.........2.2..........2........................................... 170 9.................................................................................4Function: Loading a Data Set – Data File.10...........2.................WinKFPT User's Guide Page 4 8........................1Function: Programming a NAAB Data Set ..........8 ......................................................................................................1)_v1..2... 143 8..2......................................2........ 139 8................ 174 9.................................................1 Functions of Programming Settings Phase Level 1 in Expert Mode ....................1 Errors When Starting WinKFPT.............................................................................3Function: Programming a Data Data Set .............................................................................................................................................................3......................3 Errors When Entering Flash Data ...........................................................................1........1................................... 163 9........................ 165 9.................................2 Functions of Programming Settings Phase Level 2 in Expert Mode .......3Function: Reading and Writing the Calibration Values .. 150 8...................6Function: Done..........................................5Function: EWS Alignment ......................................................................... 162 9......................................................................1Function: Loading an ECU address .....2Function: Loading a Data Set – NAAB File........... 185 Date: 20.......... 169 9..........................................................

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

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

WinKFPT
User's Guide
Page 7

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

172
173
174
177

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 8

List of Tables
Table 2-1: Operating modes of WinKFPT
Table 3-1: System requirements of WinKFPT
Table 3-2: Directories and files of WinKFPT
Table 3-3: Initialization files of WinKFPT
Table 3-4: Configuration in COAPI.INI
Table 3-5: Configuration in WINKFPT.INI
Table 3-6: Configuration in EDIABAS.INI
Table 4-1: Calling parameters of WinKFPT
Table 4-2: Status displays of WinKFPT
Table 4-3: Status displays in the Batch mode monitor
Table 4-4: Contents of a control file for the Batch mode in Comfort mode
Table 4-5: Contents of a control file for the Batch mode in Expert mode
Table 5-1: Import files
Table 6-1: Overview of the job data in the operating modes
Table 7-1: Function phases of Comfort mode
Table 8-1: Function phases of Expert mode

13
16
21
23
25
31
37
41
45
49
52
54
65
111
119
137

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 9

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, the
User'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.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

8 Function Phases in Expert Mode Control functions in Expert mode for flash programming a control unit. 3 First Steps System requirements. list structure and Description of the flash sequence in Batch mode.WinKFPT User's Guide Page 10 1. 7 Function Phases in Comfort Mode Control functions in Comfort mode for flash programming a control unit. 9 General Functions Special and diagnostics functions 10 Known control and configuration errors Date: 20. intended use. operating modes. installation.8_eng. configuration of WinKFPT. 5 WinKFPT's Main Menu The following chapters (5-6) describe how to use WinKFPT in Dialog mode. 4 Starting WinKFPT Description of the calling parameters and starting the various operating modes of WinKFPT.04 File: Handb-winkfpt32(5. programming possibilities and architecture of WinKFPT.doc Version: 1.2 About This User's Guide This User's Guide has been divided into the following chapters: Chapter Description 2 Introduction Brief description.10. Menu options of the main menu bar of WinKFPT and their submenus 6 Functions of WinKFPT Activating Comfort mode and Expert mode.8 .1)_v1.

input fields or display fields. radio buttons.10.8_eng.doc Version: 1. <Configuration> Words underscored and set in single angle brackets denote main-menu and submenu options.8 . 12345 Names written in italics but not set in quotation marks denote entries in input and/or display fields.INI Names written in uppercase letters and italics denote file names. "Operating modes" Words underscored and set in quotation marks denote chapter titles.1)_v1.WinKFPT User's Guide Page 11 1. <<ECU not responding>> Words set in double angle brackets denote messages displayed to the user.3 Conventions Used This User's Guide uses the following typographical conventions: Example Description DEFAULT.04 File: Handb-winkfpt32(5. check boxes. "Import file sets" Names written in italics and set in quotation marks denote a window or dialog box in the program. Date: 20. "OK" Names written in bold type and set in quotation marks denote buttons.

0. This reduces the need to exchange control units in e. As of Version 4.g.2 Possibilities in WinKFPT 2.1 Multiple Instancing Capability To shorten programming times by means of parallel programming of several control units via various HW interfaces or diagnosis channels.6. data) that go beyond the boundaries of ECU families.8 . ECU-specific and general logistics files and assembly line data sets for saving and loading development configurations in order to improve error tracing during development and flash verification of the control units. 2.WinKFPT User's Guide Page 12 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. The possibilities opened up by the Batch mode and the multiple instancing capability of WinKFPT have in the meantime enabled the range of application of the program to be expanded to cover production and service.1)_v1.04 File: Handb-winkfpt32(5. programs.10.doc Version: 1. WinKFPT was originally conceived purely as a reference tool for verifying the programmability of control units in the course of program and data programming. Thanks to continuous expansion of its functionality. WinKFPT is now used as a development tool for suppliers of BMW who are involved in the development of control units.8_eng. WinKFPT uses the import/export functionality of the COAPI to manage development and tool-relevant data. it is possible to call a separate WinKFPT instance for each HW interface connected that can be initialized via the EDIABAS interface.2. and therefore facilitates ECU updates (exchange of boot sectors. Date: 20. WinKFPT is the first tool that uses the COAPI functions for a boot sector update (BSU). the Service Department.

IPO) of the PABD is then located following translation as a resident file in the PABD directory "<root>\sgdat". Batch mode Can be started from Dialog mode or by being called with appropriate calling parameters.8 . Operating mode Description Dialog mode = Standard operating mode – all ECU flash programming entries are made by the user in Dialog mode.8_eng. Compile mode This operating mode is started by means of a special calling parameter and is used only to translate a PABD in source code (XXX. The table below contains a brief description of each of WinKFPT's operating modes.doc Version: 1. Table 2-1: Operating modes of WinKFPT Date: 20.2.04 File: Handb-winkfpt32(5.1)_v1.WinKFPT User's Guide Page 13 2. The programming of ECUs is configured and started by means of specific control files.IPS).10. The object code file (XXX.2 Operating Modes WinKFPT has two main operating modes Dialog mode Batch mode and one special operating mode Compile mode.

WinKFPT User's Guide Page 14 2. actually potentially involving changing the ECU family. P-SGBDs and data set names and subsequent flash programming of the control unit in Expert mode. The two possibilities in Comfort mode: 1. 2. in this case. Selection of a control unit family and of any number of integration positions offered for this family. Date: 20.04 File: Handb-winkfpt32(5. Entry or selection of the assembly identification number (ZUSB No. a number of special and diagnostics functions. selection of any number of integration positions offered for the ZUSB No. and subsequent updating of the control unit or control units in Comfort mode to the latest assembly identification within the respective series of compatible hardware releases. If a transition between non-compatible hardware releases is possible by means of a boot sector update.10. flash programming of the control units is initiated by means of a control file. Selection of the necessary PABDs. such as "Read UIF" or "ECU Status" are supported. and subsequent flash programming of the control unit or control units in Comfort mode.3 Programming of ECUs in Dialog Mode There are three possibilities for flash programming a control unit using the Dialog mode of WinKFPT.doc Version: 1. 2. WinKFPT can be started from an external application in Batch mode.8 .4 Programming of ECUs in Batch Mode Batch mode is used to flash program any number of control units one after the other. updating of the assembly identification code goes beyond just changing the hardware.8_eng.1)_v1. One possibility in Expert mode: 3..2. entry of the vehicle identification number (VIN) when a UIF is written. In addition to be able to flash program control units.).2.

1)_v1.Instance) EDIABASRuntime EDIABAS-API (2. Instance) WinKFPT (2. 2-1: Communication architecture in WinKFPT Date: 20.Instance) P-SGBD EDIABASRuntime HW-Interface I HW-Interface II Diagnosis-Bus Diagnosis-Bus Fig.04 File: Handb-winkfpt32(5.3 Architecture of WinKFPT The following diagram shows the architecture of communication between two WinKFPT instances that have been called from an external application: Application WinKFPT (1.doc Version: 1. Instance) BMWLogistic files COAPI COAPI P ABD EDIABAS-API (1.WinKFPT User's Guide Page 15 2.8 .8_eng.10.

ADS-OBD. the system requirements listed in the table below must be met: Requirement Remark Computer PENTIUM II processor or higher with 64 MB RAM and 50 MB of free memory Operating system MS-Windows NT Version 4. Date: 20. Most / Optolyzer.doc Version: 1.0. You can then import the assembly line data (Comfort mode) or PABD and P-SGBD files and data sets and program data sets (Expert mode) you want online using the import functionality of WinKFPT (see "5.10.1)_v1. EDICcard.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 16 3 FIRST STEPS 3. EDICcard2. At the end of the installation routine. a link to the program is created on the desktop and a program group for UNINSTALL also created. You are prompted to enter the target directory (<root>) in which the software is to be installed.2 Installing WinKFPT WinKFPT is installed by starting WINKFPT32.0 or MS-Windows XP Built-in diagnosis interface ADS.8 .2 Import/Export Menu"REFMERGEFORMAT).1 System Requirements of WinKFPT To be able to flash program control units with WinKFPT. In Version 1. EDICcardC. Most / PC card or Funk / MDA Built-in EDIABAS interface Version 6.8_eng. all configuration files required are available in rudimentary form following installation. CAN / Vector. so that WinKFPT will run up without any problem. CANcard.4 and higher.EXE from the installation CD or disk.2 or higher Control unit Programmable Table 3-1: System requirements of WinKFPT 3.

g.WinKFPT User's Guide Page 17 3.EXE.1)_v1. the file containing the uninstall information • UNWISE. INNENTMP_INTERFACE_unit.8 .INI.LOG. It also serves as a working directory for storing error files and other temporary files created while the program is running (e.OUT).HLP Online help for WinKFPT Date: 20. CABIGER. 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 some point in the future: • INSTALL. Directory Contents \<root>\BIN This directory contains all necessary program files (EXE. The installation directory <root> contains the following subdirectories. the WinKFPT uninstaller.DLL Coding sequence interpreter localization support DLL (German) – CABUS.EXE Executable for WinKFPT WINKFPT32.04 File: Handb-winkfpt32(5. DLL) and the initialization/configuration file WINKFPT.3 Directory Structure of WinKFPT WinKFPT is installed in the directory you specify during installation.INI Configuration file for WinKFPT WINKFPT32.10.doc Version: 1.DLL Coding sequence interpreter localization support DLL (English) – WINKFPT.8_eng.

A.WinKFPT User's Guide Page 18 Directory Contents ERROR_INTERFACE_unit. COAPI.. . the installation directory is only the default directory for storing error files. For further information.1)_v1. *. C.8_eng.INI Configuration for the coding application interface Directory also contains the text files for error messages: \<root>\DATA\DEVELOP COAPIERR.) Temporary files program run interface created during Directory contains the initialization files: INPA.0.LOG As of Version 4. You can select/set any directory you want as the storage directory by means of the main menu option <Configuration>.TXT Text file for COAPI error messages EDIERROR. INTERFACE HW identifier _unit Unit identifier (_.INI Initialization file for the coding sequence interpreter.doc Version: 1.BAF NAAB exchange files Date: 20. 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.TXT Text file for EDIABAS error messages Directory contains the programming data files available in Expert mode. Every error file refers to an instance of WinKFPT. *.PAF Program exchange files *.8 .OUT \<root>\CFGDAT Error file. The file name incorporates the HW interface identifier and unit identifier to enable assignment to the relevant instance.10. see system description of the COAPI..04 File: Handb-winkfpt32(5.6. B.DAF Data exchange files *.

only those ECU members of the imported. but belong to the same ECU family. Of no relevance to WinKFPT.0. <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) Date: 20. integration position.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.DAT Logistics file for retrofit actions in the HO.0PA Data set files for program *. NPV.8_eng. Special configuration files that must be present if required: INFO. valid WDPs are contained. valid WDPs are contained.04 File: Handb-winkfpt32(5. e.WinKFPT User's Guide Page 19 Directory \<root>\DATA\GDATEN Contents *.0DA Data set files for data *. These must always be available. these integration position texts only exist for ECUs that have different ECU members.GER Contains the integration position of an ECU member in plain text for user selection in WinKFPT.doc Version: 1.8 .6.1)_v1. only those hardware numbers for ECU families of the imported.0.e.10. rear". "Passenger side. i. HWNR.g. The files are loaded by importing an assembly line data set: KFCONFxx. In general.0BA Data set files for NAAB Directory contains the logistics files for ECU flash programming.DA2 Contains all the hardware numbers every assigned for all ECUs As of Version 4.6. As of Version 4.

8 . <Optional> Only for Batch mode for flash programming several control units one after the other.AS2 Contains the authentication codes of all ECUs for authentication level "3".HWH Contains the history of compatible hardware numbers of an ECU family in one or more series. \<root>\DATA\<EcuFam> Each of these directories contains the ASCII programming data for an ECU family <EcuFam>.BSU for for control units with Contains the necessary specifications for determining whether a boot sector update is possible for all control units affected. Note: all the logistics files of an ECU family must be present in each case.1)_v1. These are: <EcuFam>. <Optional> Only authentication.HIS Contains all compatible assembly identification numbers ever assigned for an ECU family in one or more series.DAT Contains variable assignments of ECU family to HW interface and diagnosis protocol.04 File: Handb-winkfpt32(5. identification <EcuFam>. HISTORIE.AS2 control units with Contains the authentication codes of all ECUs for authentication level "4".10. <EcuFam>. <Optional> Only authentication. <Optional> Facilitates a boot sector update for certain control units. SGIDC.WinKFPT User's Guide Page 20 Directory Contents PRGIFSEL.DAT Contains all current assembly numbers of an ECU family. SGIDD. These directories are used in Comfort mode.doc Version: 1.8_eng. Date: 20.

Files can be available in source code or in compiled form. The working directory must be created because WinKFPT will otherwise not start.04 File: Handb-winkfpt32(5.8_eng.TMP Temporary directory for storing programming data files while WinKFPT is running through several instances: \<root>\DATA\KONV.TMP3 etc. the compiled form is generated from the source code by means of the CABI compiler..1)_v1. \<root>\DATA\KONV. Since the functionality of the CABI compiler is integrated in the COAPI. Table 3-1: Directories and files of WinKFPT Date: 20.TMP2.WinKFPT User's Guide Page 21 Directory Contents \<root>\DATA\KONV Directory contains the compressed programming data in MoDiC/DIS format. WinKFPT can process both forms of a PABD.10.IPS PABDs in source code *. \<root>\WORK Working directory for COAPI and WinKFPT for storing trace and other temporary files. *.8 . The working directory can be changed by means of the COAPI.INI file. \<root\SGDAT Directory contains the header files and PABDs in source code and/or in compiled code.. \<root>\DATA\KONV.doc Version: 1.IPO PABDs in compiled code The source code of the flash sequence description files (PABDs) is available in the INPA script language.

1)_v1.3. This means it is possible for several instances of WinKFPT to work with one central set of working directories placed anywhere in a network environment.10. Otherwise an error message occurs and the actual valid basic directory is not changed. Date: 20.4 Configuration Menu”) the basic directory for the working directories can be changed at any time.04 File: Handb-winkfpt32(5.8_eng.WinKFPT User's Guide Page 22 3. A new basic directory is only accepted if below there are all working directories containing the minimum set of files as they are provided after a first installation of WinKFPT.1 Configuration of the basic directory for the working directories of WinKFPT By means of the main menu option "Configuration" (see “5.8 . Note: It is possible that existing programming settings are not valid any longer after a change of the working directories.doc Version: 1.

The following sections and entries are of importance to WinKFPT: Configuration entry [Pfadangaben] Possible setting Default Description Paths for configuration files. data and trace files are set in this section.10.WinKFPT User's Guide Page 23 3. [Kennfeldprog] This section contains entries that are required specifically for engine characteristics map programming.4 Configuring WinKFPT WinKFPT is configured by means of the following initialization files: Configuration file Contents COAPI.INI Configuration for WinKFPT EDIABAS.8_eng.1 Configuration in COAPI. GENERAL_KF_DATA_PATH Complete path or <root>\DATA1 relative to 1 <root> The entry specifies the directory in which the programming files are located.INI" 1 serves to configure directories. WORKING_DIR Complete path or <root>\WORK1 relative to <root>1 The entry specifies the directory that is used for COAPI trace files and for temporary files. ERROR_TEXTE Complete path or <root>\CFGDAT1 relative to <root>1 The entry specifies the directory in which the COAPI error text file is located.1)_v1. file names and system data for the COAPI core functions.INI The initialization file "<root>\CFGDAT\COAPI.INI Configuration for the coding application interface WINKFPT. 1 <root>: installation directory of WinKFPT Date: 20.INI Configuration for the diagnosis HW interface Table 3-1: Initialization files of WinKFPT 3.doc Version: 1.4.8 .04 File: Handb-winkfpt32(5.

[Setup] In this section.8 . SWNUMMER3 7-digit number 0000000 The entry specifies the value that is entered as the software number 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.10. TYPNUMMER3 7-digit number 0000000 The entry specifies the value that is entered as the type test number in the user info field. AEINDEX3 2-digit number 00 The entry specifies the value that is entered as the change index in the user info field. 3 The entry is only evaluated if the switch "EXPERT_MIT_AIF" in the file WINKFPT. you set which form of the PABD is to be displayed for selection in WinKFPT.INI is set to ON (Expert mode with UIF writing).doc Version: 1.04 File: Handb-winkfpt32(5. Date: 20.WinKFPT User's Guide Page 24 Configuration entry SERIENNUMMER Possible setting Default 5-digit number 12345 Description The entry specifies the value that is entered as the serial number in the user info field. 2-digit number 0 The entry specifies the value that is entered as the mileage (in km) in the user info field.8_eng. KUNDENNUMMER 5-digit number 11111 The entry specifies the value that is entered as the customer number in the user info field. KM Max.1)_v1.

This entry is however irrelevant because it is cancelled by the corresponding entry in WinKfpt. Compiling is started when PABD file is selected in Expert mode.INI" is performed in the COAPI function: "coapiKfInit ()". Table 3-1: Configuration in COAPI.e. Setting of the default or of the flag in accordance with the configuration entry in "COAPI.10.ini or the setting in the Configuration dialog.WinKFPT User's Guide Page 25 Configuration entry CabdFormat Possible setting Default IPS IPO IPO COM Description The entry defines whether the COAPI (as part of WinKFPT) is to use PABDs as source files or as compiled files.8_eng. BsuActive ON OFF ON The flag influences how the COAPI function behaves: coapiKfCheckBsuPossibleD2 When BsuActive=OFF. a boot sector update cannot be executed.bsu" says it would be possible. the function never returns the name of a NAAB files. even if "historie.IPO files. IPS PABDs as source files IPO PABDs as compiled files COM WinKFPT compiles selected *.doc Version: 1.8 .04 File: Handb-winkfpt32(5.INI Date: 20. i.IPS files and creates *.1)_v1.

8 .04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 26 Date: 20.10.8_eng.doc Version: 1.1)_v1.

-1. The following sections and entries are of importance to WinKFPT: Configuration entry Possible setting Default Description [Einstellungen] Paths for configuration files.8 . The program then starts with the same coordinates when restarted.0. SPRACHE ger eng ger U_PROG ON OFF ON The entry defines the language for WinKFPT.-1. 643. data and trace files are set in this section.1)_v1.INI The initialization file "<root>\BIN\WINKFPT.04 File: Handb-winkfpt32(5.INI" 2 is used to configure characteristics of WinKFPT.4. SCHNELLE_BAUDRATE ON OFF ON The entry specifies whether the fast baudrate is used (ON) or not (OFF) during flash programming. WindowPosition -- 0.424 The entry saves the last window size of WinKFPT when the program is exited.WinKFPT User's Guide Page 27 3. Options: German (ger) and English (eng).2 Configuration in WINKFPT. -1.doc Version: 1. 2 <root>: installation directory of WinKFPT Date: 20.1.8_eng.-1. EXPERT_MIT_AIF ON OFF ON The entry specifies whether the UIF is also programmed (ON) or not (OFF) during flash programming in Expert mode.10. ANZEIGE_U_PROG ON OFF ON The entry specifies whether the value of the programming voltage is displayed (ON) or not (OFF) during flash programming.0. The entry specifies whether the programming voltage is switched ON or OFF during flash programming.

Date: 20.WinKFPT User's Guide Page 28 Configuration entry Possible setting Default Description KOMFORT_MIT_AIF ON OFF ON The entry specifies whether the UIF is also programmed (ON) or not (OFF) during flash programming in Comfort mode. AIF_SCHREIBEN_NACH_DATEN ON OFF ON The entry specifies whether the UIF is also programmed (ON) or not (OFF) during data programming in Comfort or Expert mode. during flash programming in Comfort mode. The entry specifies whether. API_TRACE 0–7 OFF (= 0) ON (= 1) 1 IFH_TRACE 0–3 OFF (= 0) ON (= 1) 1 PROGRAMM_ERZWINGEN ON OFF OFF TEST_CHECKSUMME ON OFF ON The entry specifies the trace level of the API traces of EDIABAS during flash programming. The entry specifies whether the checksum is validated (ON) or not (OFF) after programming of the data.8_eng.10.8 .doc Version: 1.04 File: Handb-winkfpt32(5. a program is also programmed when actually only data programming would be necessary. Trace level 0 means that no traces are generated. Trace level 0 means that no traces are generated. The entry specifies the trace level of the IFH traces of EDIABAS during flash programming.1)_v1. AIF_SCHREIBEN_NACH_PROGRAMM ON OFF ON The entry specifies whether the UIF is also programmed (ON) or not (OFF) during program programming in Comfort or Expert mode.

10. ErrorLogPath any path .WinKFPT User's Guide Page 29 Configuration entry CabdFormat Possible setting IPS IPO (COM) Default Description IPO The entry defines whether WinKFPT is to use PABDs as source files or as compiled files.1)_v1.\ Storage directory ERRORn.LOG file for the ExpertKonfPath any path C:\ Diagprog Base directory for export of a configuration of development files (Expert mode).8_eng.. those HW interfaces are entered that can be switched between online while WinKFPT is being used. it does not have to be set manually in the Ini file.8 .04 File: Handb-winkfpt32(5. rather it is set temporarily and automatically by the calling parameter "-C". However. Date: 20. KomfortKonfPath any path C:\NFSBackup Base directory for export of a configuration of assembly line data (Comfort mode).doc Version: 1. CoapiSearchPath any path .\ Base directory for working directories of WinKFPT [HW-Interface ] In this section. IPS PABDs as source files IPO PABDs as compiled files COM stands for compile mode.

[Expert-Modus-Konfiguration] In this section. the current configuration in Expert mode is saved by the user (if necessary) when the program is exited. Interface can be selected by means of the menu option Communication HW Interface. C. A.1)_v1. Interface unit can be selected by means of the menu option Communication HW Interface. [HW interface identifier] is used internally in the WinKFPT program.8_eng. The identifier is defined and must be known to "EDIABAS" so that "EDIABAS" can also initialize the HW interface. the user is then able to reload this configuration. E empty Saved setting of the HW interface unit in Expert mode. D.8 . K-Line / EDIC). KF_HW_INTERFACE HW interface empty identifier Saved setting of the HW interface in Expert mode.10.doc Version: 1. When the program is restarted and Expert mode reselected. 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. KF_HW_INTERFACE_UNIT _. B. Date: 20.g.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 30 Possible setting Interfaces are to be defined using the following syntax: [Description] = [HW interface identifier] Configuration entry Default Description 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].

P-SGBD file can be selected by pressing the function key Expert Mode P-SGBD.10. KF_PSGBD P-SGBD name file empty Saved setting of the P-SGBD file name in Expert mode.8_eng.doc Version: 1.04 File: Handb-winkfpt32(5. Data set file for program can be selected by pressing the function key Expert Mode Program File. the diagnosis protocol can be selected by means of the menu option Communication Diagnosis protocol. Mode KF_SG_ADR ECU address empty Saved setting of the ECU address in Expert mode. PABD file can be selected by pressing the function key Expert PABD. KF_PABD PABD file name empty Saved setting of the PABD file name in Expert mode. Date: 20. KF_PROGRAMM_DATEI Program file name empty Saved setting of the data set file for program 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.WinKFPT User's Guide Page 31 Configuration entry KF_DIAG_PROT Possible Default setting Identifier of the empty diagnosis protocol Description Saved setting of the diagnosis protocol in Expert mode.1)_v1. Data set file for data can be selected by pressing the function key Expert Mode Data File. in the case of a P-SGBD file that supports several diagnosis protocols.8 .

10. during the import and export of configurations.: The entries in this section must be made by the user only in WinKFPT and not using Editor! Table 3-1: Configuration in WINKFPT. Data set file for NAAB can be selected by pressing the function key Expert Mode NAAB File. N. WINKFPT.04 File: Handb-winkfpt32(5.INI can. Date: 20.WinKFPT User's Guide Page 32 Configuration entry KF_NAAB_DATEI Possible setting NAAB file name Default Description empty Saved setting of the data set file for NAAB in Expert mode.8_eng.1)_v1. contain entries that are generated automatically by the program and that are not allowed to be changed or preset by the user.INI To save start information.B.doc Version: 1.8 .

NAAB file is selected by pressing the function key "NAAB File" in Expert mode (see "8. A configuration is set in Expert mode by means of the free selection of the following job data and settings: • • • • • • • • 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 Expert mode (see "5. Program file is selected by pressing the function key "Program File" in Expert mode (see "8.2.doc Version: 1. Diagnosis protocol is selected by means of the menu option Communication in Expert mode (see "5.1 Selecting (Choosing) a HW Interface").4.1)_v1.2 Function: Loading a P-SGBD").1.4 Function: Loading a Data Set – Data File").8_eng.1 Function: Loading an ECU address"). Control unit address is entered by pressing the function key "ECU Address" in Expert mode (see "8.1 Function: Loading a PABD").2 Selecting (Choosing) a Diagnosis Protocol"). PABD is selected by pressing the function key "PABD" in Expert mode (see "8.3.1.2 Date: 20.2.3 Configuration for Expert Mode The user has the option of saving and also of reloading a configuration in Expert mode if necessary.2.8 .04 File: Handb-winkfpt32(5.2.3.   HW Interface in Diagnosis Protocol P-SGBD is selected by pressing the function key "P-SGBD" in Expert mode (see "8.WinKFPT User's Guide Page 33 3.10. Data file is selected by pressing the function key "Data File" in Expert mode (see "8.3 Function: Loading a Data Set – Program File").

WinKFPT User's Guide Page 34 Function: Loading a Data Set – NAAB File").10. Date: 20.04 File: Handb-winkfpt32(5.doc Version: 1.1)_v1.8_eng.8 .

3. the following dialog box appears before WinKFPT is exited: Fig. you have the option before exiting WinKFPT of saving the current settings you have made in Expert mode so that you can call them up again the next time you start the program.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 35 3.4. The configuration is saved in WINKFPT.doc Version: 1.2 Configuration in WINKFPT.1)_v1.8 .INI").10. Date: 20. The configuration can be saved by clicking "OK" or discarded by clicking "Cancel". To this end. 3-1: Saving a configuration for Expert mode The figure shows a complete set of configuration settings as an example.1 Saving a Configuration for Expert Mode If you have activated Expert mode at least once while using WinKFPT.8_eng.INI in the [Expert mode configuration] section (see "3.4.

3. If the configuration is adopted. the user is informed of this and he can have the format changed automatically.4. the corresponding status displays in the main menu window of WinKFPT are updated (see "4.this configuration is offered to the user for loading when the user first enters or re-enters Expert mode.either following starting of the program from the configuration file WINKFPT.8_eng.8 .4. 3-1: Loading a configuration for Expert mode The configuration can be adopted by clicking "OK" or discarded by clicking "Cancel". 3.3.INI or from a previous entry in Expert mode . If the PABD format of the PABD does not match up with the format currently set. If the configuration is adopted.1)_v1.10.WinKFPT User's Guide Page 36 3.doc Version: 1.2 Loading a Configuration for Expert Mode If a configuration with at least one entry exists . the scope of the job data in the configuration determines the function level of Expert mode to which is switched (see "8 Function Phases in Expert Mode").3 Deleting a Configuration for Expert Mode Date: 20. The following dialog box appears: Fig.04 File: Handb-winkfpt32(5.2 Status Displays of WinKFPT").

perform the following steps: • Start WinKFPT. • Start Expert mode by clicking "Expert Mode".WinKFPT User's Guide Page 37 In contrast to configuration loading.10.INI. The next time WinKFPT is started and Expert mode called.doc Version: 1. • The dialog box "Save last configuration?" then displays an empty configuration for saving.1)_v1. To delete configuration settings.8_eng.8 . the program does not offer any configuration settings for loading.INI are deleted.04 File: Handb-winkfpt32(5. it is also possible to save a totally empty configuration on exiting the program and thus to delete all the entries in the [Expert mode configuration] section of WINKFPT. • Click "Cancel" in the "Load last configuration?" dialog box. • Exit WinKFPT by selecting End  Exit. Save this empty configuration by clicking "OK". WinKFPT is exited and the configuration entries in the [Expert mode configuration] section of WINKFPT. Date: 20.

Table 3-1: Configuration in EDIABAS.8 .4 Configuration in EDIABAS.INI"4 contains the configuration for the diagnosis HW interface.INI The initialization file "<ediabas>\CFGDAT\EDIABAS.4.doc Version: 1.INI 4 <ediabas> = installation directory for EDIABAS Date: 20.04 File: Handb-winkfpt32(5. Configuration entry Possible setting [Configuration] This section contains configuration entries for EDIABAS.1)_v1.10. Interface Default EDIC Description The identifier entered is initialized as the default HW interface when WinKFPT is started without calling parameters.WinKFPT User's Guide Page 38 3.8_eng.

3-1: Reference configuration in the WINKFPT.INI file Date: 20.WinKFPT User's Guide Page 39 3.1)_v1.8_eng.8 .04 File: Handb-winkfpt32(5.-1.10.-1.0.424 U_PROG=ON SCHNELLE_BAUDRATE=ON ANZEIGE_U_PROG=OFF TEST_CHECKSUMME=ON PROGRAMM_ERZWINGEN=OFF . Aif schreiben AIF_SCHREIBEN_NACH_DATEN=OFF AIF_SCHREIBEN_NACH_PROGRAMM=OFF EXPERT_MIT_AIF=OFF KOMFORT_MIT_AIF=OFF .0.5 Reference Configuration of WinKFPT The following figures show the default configuration for WinKFPT after reinstallation: [Einstellungen] . Trace API_TRACE=ON IFH_TRACE=ON [HW-Interface] K-Line / ADS=ADS K-Line / EDIC=EDIC K-Line / ADS-OBD=STD:OBD CAN / EDIC=EDICC CAN / Vector=STD:CAN Most / Optolyzer=STD:MOSTO Most / PC-Karte=STD:MOSTP Funk / MDA=STD:FUNK Fig. allgemeine Einstellungen WindowPosition=0.1.-1.doc Version: 1.-1.643.

genereller Pfad fuer Kennfeld-Daten GENERAL_KF_DATA_PATH = ..\CFGDAT WORKING_DIR = .04 File: Handb-winkfpt32(5. 1 -> Dateien werden immer komprimiert (Für Datenupdate über Netz .8 .------------------------------------------------------. SG Dateien komprimieren . 3-3: Reference configuration in the EDIABAS. Description : . 3-2: Reference configuration in the COAPI.8_eng. während Applikation läuft) Fig.INI file Sektion [Configuration] .\DATA [Kennfeldprog] TEMP_DAT_FILE_DEFAULT_NAME = KFLISTE.\WORK .1)_v1. Daten SERIENNUMMER = 42324 KUNDENNUMMER = 12321 KM = 0 ZBNUMMER = 0000000 SWNUMMER = 0000000 TYPNUMMER = 0000000 AEINDEX = 00 . Interface .doc Version: 1..INI file Date: 20. Initialisierungsdatei fuer COAPIKF-Funktionen [Pfadangaben] ERROR_TEXTE = .DAT ..WinKFPT User's Guide Page 40 . Default = Interface=STD:OBD Connected diagnosis interface EDIC Fig.10.

8_eng.10. The calling parameters are used to set WinKFPT to a desired operating mode or to preset certain operating parameters in WinKFPT to desired values immediately upon the program being started. Example: winkfpt32 –RUN -BATCH= <Control file> Path and name of a control file for Batch "<root>\bin\win mode. Setting in EDIC) that is to be active following "EDIABAS.ctl" Example: winkfpt32 –RUN –BATCH=update_ek928 -INTERFACE= <HW interface> Defines the HW interface (e.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. ADS.g. 4. kfpt.doc Version: 1.INI" starting of WinKFPT.WinKFPT User's Guide Page 41 4 STARTING WINKFPT You can start WinKFPT without calling parameters or with certain combinations of various calling parameters. Example: winkfpt32 –INTERFACE=STD:OBD Date: 20.1)_v1.8 . It can be altered at a later point in Dialog mode by means of the main menu option "HW Interface".04 File: Handb-winkfpt32(5.

ini.8 . 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 "OFF" as the parameter "WITH_MOSTFIREWALL". CabdFormat=COM does not have to be set in WinKfpt.. C..8_eng. . A. B..10.1)_v1.04 File: Handb-winkfpt32(5. Z) that is "_" to be active following starting of WinKFPT. "F1" Example: winkfpt32 -TESTER_ID=FA -C <PABD file name> Compiles an IPS file (PABD source file).. Example: winkfpt32 –C 16ek928 Table 4-1: Calling parameters of WinKFPT Date: 20. Example: winkfpt32 –WITH_MOSTFIREWALL=ON -TESTER_ID= <Hex value> Relays the value to the PABD as the parameter "TESTER_ID"..doc Version: 1.WinKFPT User's Guide Page 42 Parameter name Parameter value Description Default -UNIT= <Interface unit> Defines the unit (_.ini and coapi.

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 Date: 20. Parameters for Batch mode only 3. Parameters for setting the operating mode 2.1.1)_v1.8 .8_eng. which is the standard operating mode for users employed in control unit development.04 File: Handb-winkfpt32(5.1 Type Description of the Calling Parameters of WinKFPT The calling parameters of WinKFPT can be divided into 3 type groups: 1.WinKFPT User's Guide Page 43 4. If neither –C nor –RUN is specified as the calling parameter WinKFPT starts in Dialog mode.doc Version: 1.10. 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.

10.doc Version: 1.1)_v1.g. the software enables you to select a control unit not by means of the ECU address.04 File: Handb-winkfpt32(5.GER These texts are displayed:  following selection of an integration position in Comfort mode (Dialog mode).  during flash programming of an ECU in Batch mode. rear left).  following selection of an integration position and entry of the ECU address in Comfort mode (Dialog mode). control units for seat occupancy detection. To improve user friendliness. e. 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).2 Status Displays of WinKFPT The following status displays are displayed in the main menu window following user inputs or during automatic 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. Passenger seat. These user-selection texts are taken from the file INFO.WinKFPT User's Guide Page 44 4. rather by means of meaningful texts that describe the integration position of the control unit (e. Date: 20.g. Integration position There are control units for multiple integration that belong to the same ECU family but that have different addresses.8 .8_eng. No ECU address can be displayed for control units with "older" description files.

8 .  during flash programming of an ECU in Batch mode. the vehicle identification number is displayed only if an entry is made in the UIF (user info field) following flash programming.  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).04 File: Handb-winkfpt32(5. 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 VIN is displayed:  following selection of an integration position in Comfort mode (Dialog mode).  during flash programming of an ECU in Batch mode. Date: 20.INI is 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.10. Interface unit The default interface unit or the one selected is always displayed. The hardware number is displayed:  during flash programming of an ECU in Expert mode (Dialog mode). ZB number The ZB number (assembly identification number) defines the program data set and data data set to be programmed for a control unit.  during flash programming of an ECU in Comfort mode (Dialog mode).doc Version: 1. HW number The hardware number defines the programmed program data set of a control unit.1)_v1.8_eng. The assembly identification number from the configuration file COAPI. HW interface The default HW interface or the one selected is always displayed.WinKFPT User's Guide Page 45 Status display Vehicle number Description identification In the Comfort mode of Dialog mode.

 following selection of an integration position in Comfort mode (Dialog mode).  following selection of an integration position in Comfort mode (Dialog mode). Boot sector update Is displayed at all times and informs you of whether the boot sector update is ACTIVATED or NOT ACTIVATED.8_eng. The setting can be changed at any time by means of the main menu option "Configuration".doc Version: 1. Table 4-1: Status displays of WinKFPT Date: 20.1)_v1.WinKFPT User's Guide Page 46 Status display Description PABD Flash sequence description file The file is displayed:  following selection in Expert mode (Dialog mode).  P-SGBD Control unit description file for programming The file is displayed:  following selection in Expert mode (Dialog mode).10.04 File: Handb-winkfpt32(5.8 .  import/export of assembly line data sets.100 % in 1 % increments). data files or description files.  during flash programming of an ECU in Batch mode. The progress bar is displayed during:  flash programming (program and data).  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 % .

must be present in the "<root>\sgdat" directory.ERR saved in the <root>\bin directory. Date: 20. an error report is created in the form of the file CABI.ini and coapi.WinKFPT User's Guide Page 47 4. CabdFormat=COM does not have to be set manually in WinKfpt.1)_v1. WinKFPT is exited without any further reaction. In the event of an error. This report contains the errors that have occurred during compilation.8_eng.04 File: Handb-winkfpt32(5. e. The following dialog window appears once WinKFPT has been started: Fig.10.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.8 . 10GD8600.doc Version: 1.ini for compilation.g.IPS. otherwise WinKFPT is aborted and an error message is displayed that must be acknowledged. 4-1: Dialog window in Compile mode If you click "Cancel". The PABD to be compiled. the PABD in question is compiled and the result of this compilation displayed in a message box. If you click "OK". This is done automatically and temporary by WinKFPT.

8_eng. Date: 20.8 .10.1)_v1.04 File: Handb-winkfpt32(5. 4-3: Result display in Compile mode – compilation not OK WinKFPT is exited when "OK" is clicked. 4-2: Result display in Compile mode – compilation OK Result display when compilation has not been successful: Fig.WinKFPT User's Guide Page 48 Result display when compilation has been successful: Fig.doc Version: 1.

In this case. Batch mode is already started.10.4 Starting WinKFPT in Batch Mode Batch mode is used to flash program any number of control units one after the other.1 Calling Parameters of WinKFPT"). for example. Once Batch mode has been activated.doc Version: 1.04 File: Handb-winkfpt32(5. In this case. 4-1: Dialog window for Batch mode (Batch mode monitor) Date: 20. an external application using the calling parameter –RUN (see "4. Batch mode of WinKFPT can be activated in two ways: 1. 2. Automatic activation through calling from.8_eng.1. Manual activation from within Dialog mode (see "5.WinKFPT User's Guide Page 49 4.  Batch Mode").1)_v1.8 . another dialog window (WinKFPT Batch mode monitor) that contains the status displays and the function buttons for user inputs in Batch mode is displayed in addition to the main menu window of WinKFPT: Fig.9 Display Batch mode is not yet started.

e. an error leads to immediate aborting of programming. i. • "Stop": Batch mode is ended.WinKFPT User's Guide Page 50 The following table describes the status displays in the Batch mode monitor: Status display Description Control file Path and name of the default control file or of the control file transferred as calling parameter (-BATCH=<controlfile>). Date: 20.8_eng. 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. Status The status display informs the user about the current activity or about error conditions in Batch mode. Table 4-1: Status displays in the Batch mode monitor The following user inputs are possible in Batch mode: • "Start": Batch mode is started. Target interface Indicates the HW interface+unit that the corresponding WinKFPT instance accesses during flash programming of an ECU. 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.1)_v1.04 File: Handb-winkfpt32(5.10.doc Version: 1. WinKFPT waits for a control file or a existing control file is processed.8 .e. i. Aborts Indicates the number of errors that occur during the flash programming of ECUs. Mode Indicates whether a control file for Comfort mode or for Expert mode is being processed.

It is automatically assumed to be .8 . WinKFPT waits for the Control file indicated. The path and name of the control file can be specified when calling using the calling parameter – BATCH=<controlfile>. including the drive details. <root\bin>.WinKFPT User's Guide Page 51 If Batch mode is started. it is opened.10. Date: 20. If part of the path is missing.1)_v1. There is no need to enter an extension for the control file. if specified. it is decided whether the process is a Batch process in Comfort mode or in Expert mode. As soon as this file exists.8_eng. the control file is expected in the installation directory of WinKFPT.CTL.04 File: Handb-winkfpt32(5. evaluated and processed. the path must be cited in its entirety.doc Version: 1. Depending on the contents of the control file.

1)_v1. [SGADRESSE] (ECUADDRESS) and [BATCH].8 . The table below contains a full description of the sections of a control file and of the contents of these sections.8_eng. each on a separate line. Its contents correspond to the entries the WinKFPT user makes in the "Comfort mode" of Dialog mode (ZB number. [ZBNUMMER] (ZBNUMBER). Other sections are ignored. Format: VIN=<VIN> Example: VIN=WBAAA00000AA00000 [ZBNUMMER] The [ZBNUMMER] (ZBNUMBER) section contains the various assembly identification numbers.1 Control File for Batch Mode in Comfort Mode The control file is processed in order. The syntax of the control file is in line with the file format as familiar from Windows INI files and it is divided up into the following sections: [FGNUMMER] (VIN).WinKFPT User's Guide Page 52 4.4.04 File: Handb-winkfpt32(5. Date: 20. where xxxx is a consecutive number that begins at 0000. Example: ZBN0000=7539765 ZBN0001=7539767 The control units are programmed according to the sequence of the numbers. ECU address (corresponds to the integration position) and vehicle identification number). and there must be no gap.doc Version: 1. Format: ZBNxxxx=<ZBnumber>.10. Section Contents [FGNUMMER] The [FGNUMMER] (VIN) section has just one line that contains the vehicle identification number. Programming is ended when the first number that no longer has a successor number is reached.

Format: END=ON or END=OFF. If the section is left blank (i. each on a separate line. ZBNUMMER and SGADRESSE sections (if present) are ignored.1)_v1. E. Batch mode is ended immediately upon the control file being read in. where xxxx is a consecutive number that begins at 0000. If Batch mode was started automatically by means of the calling parameter –RUN.8_eng. In this case.g.8 . this is interpreted as END=OFF. Table 4-1: Contents of a control file for the Batch mode in Comfort mode Once the control file has been processed. Format: SGADRxxxx=<ECUaddress>.WinKFPT User's Guide Page 53 Section Contents [SGADRESSE] The [SGADRESSE] (ECUADDRESS) section contains the various ECU addresses.e. Example: SGADR0000=12 SGADR0001=13 There must be an ECU address with an identical consecutive number for each assembly identification number entered. WinKFPT is also ended. it is deleted and WinKFPT waits for a new control file.10. no entry) or is missing. The ECU address is entered as a HEXADECIMAL. Date: 20. and there must be no gap.: [ZBNUMMER] ZBN0000=7515985 [SGADRESSE] SGADR0000=A2 [BATCH] The [BATCH] section contains one line with information relating to the ending of Batch mode.doc Version: 1.04 File: Handb-winkfpt32(5. 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. the FGNUMMER.

WinKFPT User's Guide Page 54 4. At least one NAAB file. At least one NAAB file. Format: MF_DIAGNOSEPROTOKOLL=<Diagnosis protocol> Example: MF_DIAGNOSEPROTOKOLL=KWP2000* Date: 20. one data file or one program file must be entered. The table below contains a full description of the parameters in the [MULTIFLASH] section of a control file: Parameter Contents MF_PABD This parameter specifies the PABD to be used for programming.0ba MF_DIAGNOSEPROTOKOLL This parameter specifies the diagnosis protocol to be used.PRG MF_SG_ADR The ECU address is entered as a HEXADECIMAL.1)_v1.0PA MF_NAAB_DATEI This parameter defines the NAAB file to be programmed. data file.04 File: Handb-winkfpt32(5. ECU address. one data file or one program file must be entered.0DA MF_PROGRAMM_DATEI This parameter defines the program file to be programmed.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" of Dialog mode (PABD. The syntax of the control file is in line with the file format as familiar from Windows INI files. Format: MF_PABD=<PABD name> Example: MF_PABD=21EK928.doc Version: 1. P-SGBD. one data file or one program file must be entered. Format: MF_PROGRAMM_DATEI =<Program file name> Example: MF_PROGRAMM_DATEI=7523523A. diagnosis protocol and vehicle identification number).8_eng. Format: MF_DATEN_DATEI =<Data file name> Example: MF_DATEN_DATEI=Q7525491. The file has just the one section: [MULTIFLASH] Other sections are ignored.8 . program file. Format: MF_PSGBD=<P-SGBD name> Example: MF_PSGBD=21EK92.10. Format: MF_SG_ADR=<PABD name> Example: MF_SG_ADR=12 MF_DATEN_DATEI This parameter defines the data file to be programmed.4.IPO MF_PSGBD This parameter specifies the P-SGBD to be used for programming. At least one NAAB file. Format: MF_PROGRAMM_DATEI =<NAAB file name> Example: MF_NAAB_DATEI=555111_555222. This is optional.

1)_v1.8 .WinKFPT User's Guide Page 55 MF_FG_NUMMER This parameter specifies the vehicle identification number. 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.10. Date: 20. it is deleted and WinKFPT terminates itself automatically.04 File: Handb-winkfpt32(5.8_eng.doc Version: 1. It is only required if UIF writing is used for programming.

WinKFPT User's Guide Page 56 4. the same status displays are displayed in the main menu window of WinKFPT as are displayed when programming in Dialog mode. The following is documented in the log file: Name of the control file and its date. The control file is no longer read until processing has been completed. Abort" for error during programming Date: 20. The diagnosis protocol is entered as MF_DIAGNOSEPROTOKOLL=<Diagnosis protocol>. a log is generated that has the same path and name as the control file but the extension .8 .e.PRT. The existence of the control file is determined by WinKFPT in Batch mode by means of polling. In Comfort mode: The VIN is entered as FGN=<VIN>. The ECU address is entered as MF_SG_ADR=<ECU address>. For each individual flash programming of an ECU. In Expert mode: The PABD is entered as MF_PABD=<PABD>.1)_v1. for each processing of a VIN from the control file. The data file is entered as MF_DATEN_DATEI=<Data file name>.04 File: Handb-winkfpt32(5. The P-SGBD is entered as MF_PSGBD=<P-SGBD>.doc Version: 1. The VIN is entered as MF_FG_NUMMER=<VIN>. i. the EDIABAS-API is released and remains bound to the program only during the period the job is being processed.10.8_eng. This is to prevent uncompleted files from being read in. The program file is entered as MF_PROGRAMM_DATEI=<Program file>. The ZB number and ECU address are entered at the start of processing.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 following texts are generated to indicate the result of an individual programming routine: "ERG=Programming OK" for correct programming "ERG=Programming nOK. The control file should first of all be written under a different name or in a different directory and then be made visible for Batch mode by being renamed or copied over. Contents of the control file as they have been scanned.4. Error during scanning of the control file. The NAAB file is entered as MF_NAAB_DATEI=<NAAB file>. While WinKFPT is in Batch mode. Process logging: While the programming job is being processed.

10. In Expert mode.WinKFPT User's Guide Page 57 "ERG=Programming nOK. WinKFPT terminates itself once the batch file has been fully processed.. where xxx is a consecutive number. Messages displayed in Dialog mode of WinKFPT in popup dialog boxes are written to the log file in the format INFOxxx=<Text>.8_eng.04 File: Handb-winkfpt32(5. Date: 20.1)_v1.8 . WinKFPT then waits for a new batch file. Fatal error" for error prior to programming.doc Version: 1. End of a programming job: The end of the processing of a job is indicated by deletion of the control file. In Comfort mode.

DAT" does not exist or if the control unit to be programmed is not entered in this file.04 File: Handb-winkfpt32(5.8 .10. This file contains the HW interface and diagnosis protocol that are to be used for the ECU families entered.4 Switching HW Interface and Diagnosis Protocol in Batch Mode Switching HW interface and diagnosis protocol during the programming of control units in Batch mode in Comfort mode is based on the file \<root>\DATA\GDATEN\PRGIFSEL.4.doc Version: 1.WinKFPT User's Guide Page 58 4.1)_v1. The default diagnosis protocol is the first one from the list of diagnosis protocols that the P-SGBD of the control unit returns as the reply to the prompt with regard to the diagnosis protocols implemented.8_eng. If the file "PRGIFSEL. the last HW interface that was active prior to starting Batch mode and the default diagnosis protocol for this control unit are set.DAT. Date: 20.

If two instances want to access the same control file. Whatever the case. Date: 20. two WinKFPT instances are never able to communicate with a control unit via the same HW interface+unit.e. they have been started with the same HW interface+unit details.8_eng. Note that two instances of WinKFPT are not able to use the same control file. Only that instance that begins processing first is able to access the HW interface properly. Batch mode has a special feature by which two WinKFPT instances can be started that display the same target interface in the Batch mode monitor.WinKFPT User's Guide Page 59 4.1)_v1. the calling parameter –BATCH=<Control file> must be used.04 File: Handb-winkfpt32(5. Apart from that.doc Version: 1.10. 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.4. several instances of WinKFPT can be run and process control files simultaneously. but also to manual activation of Batch mode (starting WinKFPT without -RUN parameter).5 Starting Several Instances in Batch Mode In automatic Batch mode. each instance must communicate over a different piece of hardware (hardware interface + unit) while its control file is being processed. This applies not only to automatic activation (starting WinKFPT with -RUN parameter). i. To define the interface and the unit for a WinKFPT instance at the time of starting.8 . A HW interface conflict only arises when the two instances process their control file simultaneously and want to access the same HW interface. you can use the command line parameters -INTERFACE=<HW interface> and -UNIT=<Unit identifier>. the following error message is displayed: Fig. the HW interface is blocked for the second instance from this point to the time processing of the first instance has been completed.

too.8_eng. 4-1: Error message when the same HW interface+unit is accessed Date: 20.8 .WinKFPT User's Guide Page 60 4. 4.10.04 File: Handb-winkfpt32(5. the second instance starts with the error message: or Fig.1)_v1.doc Version: 1. In such a case. Since the default HW interface+unit or the HW interface+unit entered as the calling parameter is always accessed immediately when WinKFPT is started in Dialog mode. Calling WinKFPT without calling parameters always starts a WinKFPT instance in Dialog mode. it is not possible for two instances to be started that want to access the same HW interface+unit.5 Starting WinKFPT in Dialog Mode All calling parameters except "-C" and "-RUN" may be used to start a WinKFPT instance in Dialog mode. it is theoretically possible to call and run up to 99 different WinKFPT instances simultaneously in Dialog mode.1 Starting Several Instances in Dialog Mode Like in Batch mode.5.

the second instance is automatically closed again.WinKFPT User's Guide Page 61 Once you have acknowledged the error message by clicking "OK".10. Date: 20.04 File: Handb-winkfpt32(5.8_eng.doc Version: 1.1)_v1.8 .

10.8 .8_eng. a pull-down menu containing one or more submenu options appears via which you can call the various menu options.ERR> • <ERROR.1)_v1.LOG> • <PABD Parameters> • <HW History> • <ZB History> • <ZB Rule> • <API Trace File> • <IFH Trace File> • <Batch Mode> Date: 20. 5.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 62 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.1 Display Menu The main menu option Display contains the following submenu options that be used to switch certain functions ON or OFF and display error and trace files: • <CABI.doc Version: 1.

1)_v1.4 Display  HW History Displays the HW history of the current hardware number. Close the display by clicking OK or by pressing "ESC" or Alt+F4.1.1 Display  CABI. 5.ERR Displays the CABI. 5.04 File: Handb-winkfpt32(5.2 Display  ERROR.1.ERR file that contains the error messages created when an error occurs during translation of a PABD (= IPS file).8_eng. Close the display by clicking OK or by pressing "ESC" or Alt+F4. Close the display by clicking OK or by pressing "ESC" or Alt+F4.WinKFPT User's Guide Page 63 5. Date: 20. 5. Close the display by clicking OK or by pressing "ESC" or Alt+F4.doc Version: 1.5 Display  ZB History Displays the ZB history of the current assembly identification number. 5.1.LOG error file that contains the error messages from the COAPI and CDH functions.LOG Displays the ERROR_INTERFACE_UNIT.1. Close the display by clicking OK or by pressing "ESC" or Alt+F4.1.6 Display  ZB Rules Displays the ZB rule of the current assembly identification number.8 .1. Close the display by clicking OK or by pressing "ESC" or Alt+F4. 5.10.3 Display  PABD Parameters Displays the job and result parameters currently set for a PABD.

WinKFPT User's Guide Page 64 5.8 Display  IFH Trace File Displays an IFH trace file present in the EDIABAS directory.1.8_eng.1.doc Version: 1.04 File: Handb-winkfpt32(5.7 Display  API Trace File Displays an API trace file present in the EDIABAS directory. Close the display by clicking OK or by pressing "ESC" or Alt+F4.1.8 . Batch mode is not yet started following this switching. 5.10.9 Display  Batch Mode Switches from Dialog mode to Batch mode. 5.1)_v1. Date: 20. Close the display by clicking OK or by pressing "ESC" or Alt+F4.

0DA *.DAF *. 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. The files selected are then automatically distributed to the appropriate directories once their adoption has been confirmed.WinKFPT User's Guide Page 65 5.PAF NAAB files *. 5-1: Submenu under the main menu option <Import/Export> 5. They can be selected from any drive or directory.10. The following file groups can be imported: Import Files *.doc Version: 1.2 Import/Export Menu Selecting this main menu option opens up the following submenu: Fig.1)_v1.8_eng.1 Import Submenu This submenu option in turn activates a pull-down menu that contains the following options: Fig.0BA *.0PA Data sets / Program releases / *.8 .BAF Data set files for data Data exchange files Data set files for program Program exchange files Data set files for NAAB NAAB exchange files Date: 20.04 File: Handb-winkfpt32(5.2.

Date: 20.IPO *.8 .10.PRG PABD *. /BSU NAAB files.PRG *.0DA *.assembly line data Files like from import of assembly line data + development files and/or tool-relevant files if desired by user 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.0BA *.IPS *.IPS *.GER Assembly line data *. P-SGBDs and PABDs is assigned to "Expert mode".BSU Exported configuration development data - Exported configuration .HIS *.04 File: Handb-winkfpt32(5.1)_v1.DAT *.DA2 *.8_eng.HWH *.WinKFPT User's Guide Page 66 P-SGBD in compiled code P-SGBD *.doc Version: 1.0PA Data set files for data Data set files for program Data set files for NAAB P-SGBD in compiled code PABDs in source code PABDs in compiled code ECU logistics files Assignment of ECU members to names of logistics files History of compatible hardware numbers of an ECU family Compatible assembly identification numbers of an ECU family Logistics file Logistics file Authentication code files ECU member integration position Logistics file for checking the possibility of a BSU (boot sector update) *. The import of exported configuration assembly line data and assembly line data is assigned to "Comfort mode".ASD *.ATS *.AS2 *.IPO PABDs in source code PABDs in compiled code *.

For each subsequent import.LOG.2.04 File: Handb-winkfpt32(5. If the directory selected does not contain this log file.doc Version: 1.1.8 .WinKFPT User's Guide Page 67 5.1 Importing an "Exported Configuration" of Assembly Line Data You import an "exported configuration" of assembly line data by selecting the menu option Import/Export  Import  Exported configuration . the import directory highlighted is the one that was selected the last time. i. It is only possible to import an entire exported configuration. an error message is displayed and the dialog terminated. A configuration of exported assembly line data can only be imported from directories that contain the export log file BACKUPEXPORT. a check is run to determine whether or not one or more of the WDPs to be imported is/are already present in the "<root>\Data" directory. Date: 20. you are not able to select parts from the exported WDPs for import.e. 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". The following dialog window is then displayed to enable you to select the import directory: Fig.8_eng.1)_v1. The contents of the log file are not checked. Before importing is performed.10.assembly line data.

Fig. The "Merge" button is not shown too because has not function and the "Replace" button is changed by the "Import" button Furthermore. • Replace and Import respectively(always active): Date: 20. "Merge" and "Cancel".8_eng.1)_v1.04 File: Handb-winkfpt32(5. The buttons have the following functions: • Cancel (always active): the dialog window is closed and no files are imported.WinKFPT User's Guide Page 68 A dialog window appears that contains a list of the WDPs already in this directory and the function buttons "Replace". the list window and its corresponding headline is not shown.8 . KMM files are exported for archiving purposes only and are therefore never reimported. you can also specify whether you want to import with or without tool-relevant data (INI files) (default is "Import .Tool relevant data" not activated).10. 5-2: WDP conflict when importing a configuration of assembly line data If the list of WDPs is empty.doc Version: 1. Tool-relevant files from the import directory always overwrite those files in the working directory that have the same name.

1)_v1. which is only valid for the import mode Merge. • 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 the working directory.doc Version: 1.e. all lines that relate to the ECU family of the assembly line data set to be imported are overwritten if they are already present or appended if they are not already present. This operation is only executed for lines that begin with a number. files that are already present are overwritten. The following COMMON files are given 'special treatment' that is identical for the two import modes Replace and Merge: KFCONFXX. Special treatment.DA2: In the file in the working directory. not for lines that in particular begin with "$" or ". i.8 .".10.04 File: Handb-winkfpt32(5. Date: 20.8_eng. is given to the following ECUspecific file: <ECUFAMILY>.WinKFPT User's Guide Page 69 all the files from the import directory selected are copied to the working directory.DAT: All lines from the file in the import directory that do not yet exist in the file in the working directory are appended to the DAT file in the working directory.DA2 and HWNR.

2. If the directory selected does not contain this log file.1.10.04 File: Handb-winkfpt32(5. you are not able to select parts from the exported WDPs for import. The following dialog window is then displayed to enable you to select the import directory: Fig. i. Before importing is performed.8 . The contents of the log file are not checked. an error message is displayed and the dialog terminated. 5-1: Selecting the import directory of a configuration of development data The start directory highlighted in the import dialog window for the first import in a WinKFPT session is "My Computer". a check is run to determine whether or not one or more of the WDPs to be imported is/are already present in the "<root>\Data" directory.development data. For each subsequent import. Date: 20.WinKFPT User's Guide Page 70 5.1)_v1.e. A configuration of exported development data can only be imported from directories that contain the export log file CONFIGEXPORT. It is only possible to import an entire exported configuration.8_eng.doc Version: 1. the import directory highlighted is the one that was selected the last time.2 Importing an "Exported Configuration" of Development Data You import an "exported configuration" of development data by selecting the menu option Import/Export  Import  Exported configuration .LOG.

10. The "Merge" button is not shown too because has not function and the "Replace" button is changed by the "Import" button A separate selection element enables you to active or deactivate importing of the development files.1)_v1.doc Version: 1.WinKFPT User's Guide Page 71 A dialog window appears that contains a list of the WDPs already in this directory and the function buttons "Replace". files from the <basedirectory>\<configurationname>\Daten\Entwicklung\Data\Develop <basedirectory>\<configurationname>\Daten\Entwicklung\Sgdat <basedirectory>\<configurationname>\Daten\Entwicklung\Ecu directories (default is "Import . Fig.Development files" activated). "Merge" and "Cancel". 5-2: WDP conflict when importing a configuration of development data If the list of WDPs is empty. Note: The files from the export directory <basedirectory>\<configurationname>\Daten\Entwicklung\Data\Gdaten are not reimported.e.8 . the list window and its corresponding headline is not shown. i. Date: 20.8_eng.04 File: Handb-winkfpt32(5.

• 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 the import directory to the working directory. is given to the following ECUspecific file: <ECUFAMILY>. The buttons have the following functions: • Cancel (always active): the dialog window is closed and no files are imported. The following COMMON files are given 'special treatment' that is identical for the two import modes Replace and Merge: KFCONFXX. not for lines that in particular begin with "$" or ". Development files and tool-relevant files from the import directory always overwrite those files in the working directory that have the same name. you can also specify whether you want to import with or without tool-relevant data (INI files) (default is "Import .8_eng.DA2: In the file in the working directory.e.10.1)_v1. i. Date: 20.WinKFPT User's Guide Page 72 Furthermore.DAT: All lines from the file in the import directory that do not yet exist in the file in the working directory are appended to the DAT file in the working directory.Tool relevant data" not activated). Special treatment. • Replace and Import respectively(always active): all the files from the import directory selected are copied to the working directory. This operation is only executed for lines that begin with a number. files that are already present are overwritten. which is only valid for the import mode Merge.".DA2 and HWNR.doc Version: 1. all lines that relate to the ECU family of the assembly line data set to be imported are overwritten if they are already present or appended if they are not already present.8 .04 File: Handb-winkfpt32(5.

only the data set "EK928" would be imported. the import directory highlighted is the one that was selected the last time.10. In the example above. The directory selected contains either an actual assembly line data set or one or more subdirectories that contain assembly line data sets. "EK9294B" etc.1.3 Importing Assembly Line Data You import assembly line data by selecting the menu option Import/Export line data. If in the example above you were to select "G:\Trans\EK9282" as the import directory. data sets "EK9282".WinKFPT User's Guide Page 73 5.1)_v1. For each subsequent import.8_eng. Date: 20.2. WinKFPT automatically finds all data sets immediately in the selected directory or one directory level lower and executes the import for each data set. if you selected "G:\Trans". would be imported.04 File: Handb-winkfpt32(5. 5-1: Selecting the import directory for assembly line data sets The start directory highlighted in the import dialog window for the first import in a WinKFPT session is "My Computer".  Import  Assembly The following dialog window is then displayed to enable you to select the import directory: Fig.doc Version: 1.8 . you could select either "G:\Trans\EK9282" or "G:\Trans".

WinKFPT
User's Guide
Page 74

Before importing is performed, a check is run to determine whether or not one or more of the WDPs
to 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
The buttons have the following functions:

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 that
are already present are overwritten.

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

The following COMMON files are given 'special treatment' that is identical for the two import
modes 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 set
to be imported are overwritten if they are already present or appended if they are not already present.
Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 75

Special treatment, which is only valid for the import mode Merge, is given to the following ECUspecific file:
<ECUFAMILY>.DAT:
All lines from the file in the import directory that do not yet exist in the file in the working directory are
appended to the DAT file in the working directory. This operation is only executed for lines that begin
with a number, i.e. not for lines that in particular begin with "$" or ";".
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, <root>\DATA\GDATEN
HWNR.DAT, NPV.DAT, KFCONF.DAT, HISTORIE.BSU
<ECUFAMILY>.DAT, *.0DA, *.0PA, *.0BA, *.HWH, *.HIS, <root>\DATA\<ecufam>
*.ATS
Table 5-1: Distribution of the files to directories when assembly line data is imported

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 76

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 option
Import/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 use
for 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> key
and 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.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

5-2: Overwriting files during NAAB.04 File: Handb-winkfpt32(5.program file" or "Loading a data set .2 Date: 20. After being imported. data and program file importing If you have selected more than one file. Fig.10.doc Version: 1.data file" function in Expert mode (see "8.NAAB file". files are displayed in the selection list of the "Loading a data set . the status of the copying procedure is indicated by a progress bar (0 .2.8 .8_eng. "Loading a data set .100 %).WinKFPT User's Guide Page 77 Files that already exist can only be overwritten once a warning prompt has been acknowledged in the positive.1)_v1.

Date: 20.8 .WinKFPT User's Guide Page 78 Function: Loading a Data Set – NAAB File".8_eng.2.10.3 Function: Loading a Data Set – Program File" or "8.1)_v1.04 File: Handb-winkfpt32(5. "8.4 Function: Loading a Data Set – Data File").2.doc Version: 1.

5-1: Importing P-SGBDs Only *.PRG files are displayed (default setting). To import the files: • Select the directory with the files you want from the list next to "Search in".1)_v1.8 .8_eng. You can select all the files displayed by pressing <Ctrl> + <A>. Fig.10.1. You can select a single file from the list simply by clicking it with the left mouse button. By importing P-SGBDs.2. you select the control unit description files you want to use for flash programming in Expert mode and automatically copy them to the appropriate directory. • Then click "Import".doc Version: 1. • Select the file to be imported. 4 <ediabas> = installation directory for EDIABAS interface Date: 20.WinKFPT User's Guide Page 79 5. You can select several files to import by holding down the <Ctrl> key and clicking with the left mouse button.04 File: Handb-winkfpt32(5. The files you have selected are copied to the P-SGBD directory "<ediabas>\ecu"4.5 Importing Control Unit Description Files for Programming (P-SGBDs) You import P-SGBDs by selecting the menu option Import/Export  Import  P-SGBD.

04 File: Handb-winkfpt32(5. Date: 20.doc Version: 1.2 Function: Loading a P-SGBD").1.1)_v1. files are displayed in the selection list of the "Load P-SGBD" function in Expert mode (see "8.8 .100 %).WinKFPT User's Guide Page 80 Files that already exist can only be overwritten once a warning prompt has been acknowledged in the positive. Fig.8_eng. the status of the copying procedure is indicated by a progress bar (0 .10. 5-2: Overwriting files during P-SGBD importing If you have selected more than one file. After being imported.

doc Version: 1. You can select several files to import by holding down the <Ctrl> key and clicking with the left mouse button. 5-1: Importing PABDs Only *.2. By importing PABDs. • Select the file to be imported.1)_v1. You can select all the files displayed by pressing <Ctrl> + <A>.IPS and *.IPO files are displayed (default setting). • Then click "Import".04 File: Handb-winkfpt32(5.1. Date: 20.8_eng. You can select a single file from the list simply by clicking it with the left mouse button.8 .WinKFPT User's Guide Page 81 5. you select the flash sequence description files you want to use for flash programming in Expert mode and automatically copy them to the appropriate directory. Fig. To import the files: • Select the directory with the files you want from the list next to "Search in".6 Importing Flash Sequence Description Files (PABDs) You import PABDs by selecting the menu option Import/Export  Import  PABD.10.

Fig.8_eng.8 . files are displayed in the selection list of the "Load PABD" function in Expert mode (see "8.100 %). After being imported.1 Function: Loading a PABD"). 5-2: Overwriting files during PABD importing If you have selected more than one file. 5 <root>: installation directory of WinKFPT Date: 20. Files that already exist can only be overwritten once a warning prompt has been acknowledged in the positive.1)_v1.10. the status of the copying procedure is indicated by a progress bar (0 .1.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 82 The files you have selected are copied to "\<root>\sgdat"5.doc Version: 1.

doc Version: 1.04 File: Handb-winkfpt32(5. 5-1: Pull-down menu under the submenu option <Export> Date: 20.2.1)_v1.10.WinKFPT User's Guide Page 83 5.8_eng.8 .2 Export Submenu This submenu option in turn activates a pull-down menu that contains the following options: Fig.

8 . 5-1: Dialog window for exporting a configuration of assembly line data This dialog window displays the export base directory currently set. A list box displays all the valid assembly line data sets (ECU families) available for selection for export. Date: 20.2.  When you select this menu option.2. You can select either no data set at all. one. several or all of the assembly line data sets.04 File: Handb-winkfpt32(5.8_eng.assembly line data. e.doc Version: 1. the following dialog window appears: Fig.WinKFPT User's Guide Page 84 5. If no valid assembly line data exists. the list box is empty and all you can do is export the toolrelevant data by activating the corresponding check box. and two input fields ("Type series" and "I-Level") for the names of the two subdirectories. <root>\NFS-Backup".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 .g.10.1)_v1.

The following pieces of information are entered in a log file for each export procedure: • Date (format: dd. the relevant information to be stored is in each case appended to the log file that already exists.1)_v1. This is the case if the files to be exported.mm.8 .04 File: Handb-winkfpt32(5. Every export of assembly line data is documented in the export log file "BACKUPEXPORT. No new directories are created. i. are not yet present in the highest-order index directory. i.10. the index directory is increased automatically. New directories are created. 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. the index directory is not increased. Before the actual copying process begins.WinKFPT User's Guide Page 85 With each export.e. and if all or some of the files present are identical with those to be exported. provided a KMM directory exists.yyyy) • Export base directory • Type series • I-Level • Index • With/Without development files • With/Without tool-relevant data • ECU family : : • Separating line Date: 20.e. 2. In the event of repeated export to the same directory (<root>\<NFS-Backup>\<typeseries>\<ILevel>\<index>\).doc Version: 1.8_eng. Excluded from comparison are the COMMON files because those to be exported cannot as a rule be identical with those previously exported. This basically results in the following two sequences for the export of assembly line data: 1. either all or just some of them. the data to be exported is compared with the corresponding data last exported and located in the highest-order index directory. All files are deleted from their respective export directory before copying begins. the KMM data from the working directory "<root>\KMM\" is exported implicitly.LOG" in the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\ directory.

. P-SGBD will be placed together in this directory NFS\ bin\ cfgdat\ EDIABAS\bin\ winkfpt. 5-1: Structure of the target directories for exporting assembly line data Date: 20. .. ediabas.2..04 File: Handb-winkfpt32(5. PABD.. . .8 . KMM\ <Log-File> Fig..ini..8_eng.doc Version: 1. EC-Family-Data.1.WinKFPT User's Guide Page 86 5.10.ini.ini. if changend Data is exported <Index>\ daten\ <sgfam1>\ <sgfam2>\ GData. coapi.2.1)_v1.1 Directory Structure for Exporting Assembly Line Data <root>\NFS-Backup\ configurable enter manually on export <Baureihe>\ enter manually on export <i-Stufe>\ Index will be increased automatically.

*.DA2 and KFCONFXX. <ECUFAM>.10.INI from the <root>\NFS\bin\ directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\bin\ directory.1)_v1. PABD: The name of the description file that belongs to the WDP is determined from the KFCONFXX.2 • Filing of the Files When Exporting Assembly Line Data Export WDPs (if one or more selected) Flash data.2. SGIDD. • Export tool-relevant data (optional) Copying of all the files with the extension *. SGIDC. • Export KMMs (always if present) Copying of all the files in the <root>\kmmdat\<typeseries>\ directory to the <root>\<NFSBackup>\<typeseries>\<I-Level>\<Index>\kmm\ directory.AS2.DAT.AS2 and INFO. Copying of all the files with the extension *. *.0BA <ECUFAM>.INI from the <root>\EDIABAS\bin\ directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\EDIABAS\bin\ directory. The relevant parts of the HWNR.DA2 file and copied from EDIABAS\ECU to the <root>\<NFSBackup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.8 . HISTORIE. The file name of the COMMON file is adopted unchanged.2.INI and *. <ECUFAM>.WinKFPT User's Guide Page 87 5.HWH and <ECUFAM>. COMMON files: COMMON files SWTCONFX. P-SGBD: The name of the description file that belongs to the WDP is determined from the KFCONFXX.DA2 file and copied from <root>\Sgdat to the <root>\<NFSBackup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory. Date: 20.DAT.HIS.doc Version: 1. Copying of all the files with the extensions *.0PA.8_eng.ATS are copied from the <ecufam> directory to the <root>\<NFS-Backup>\<typeseries>\<ILevel>\<index>\daten\<ecufam> directory.BSU. logistics data: The files *.1.GER are copied from the <root>\Data\Gdaten directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.DA2 files are determined and only these parts are copied to the <root>\NFS-Backup\<typeseries>\<ILevel>\<index>\daten\<ecufam> directory.0DA.DAT from the <root>\cfgdat directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\cfgdat\ directory.04 File: Handb-winkfpt32(5.

and one input field ("Configuration name") for the name of the subdirectory.1)_v1. If no valid assembly line data exists.g. 5-1: Dialog window for exporting a configuration of development data This dialog window displays the export base directory currently set.  When you select this menu option. You can select either no data set at all.doc Version: 1.8_eng.2. one. several or all of the assembly line data sets.WinKFPT User's Guide Page 88 5.development data. the list box is empty and all you can do is export the development files and/or tool-relevant data by activating the corresponding check box(es). e.10. the following dialog window appears: Fig. Date: 20. A list box displays all the valid assembly line data sets (ECU families) available for selection for export.2.04 File: Handb-winkfpt32(5. "<root>\Diagprog".2 Exporting a "Configuration" of Development Data You export a "configuration" of development data by selecting the menu option Import/Export Export  Configuration .8 .

the following prompt is displayed: Fig. In the event of repeated export to the same directory (<root>\Diagprog \<configurationname>\).WinKFPT User's Guide Page 89 All files selected for export are copied.LOG" in the <root>\Diagprog\<configurationname>\ directory. the relevant information to be stored is in each case appended to the log file that already exists. all the files in the existing directories are deleted first before exporting is conducted.1)_v1.mm. If the files are to be exported to a directory ("Configuration name") that already exists.8_eng.04 File: Handb-winkfpt32(5. Every export of development data is documented in the export log file "CONFIGEXPORT.8 .yyyy) • Export base directory • Configuration name • With/Without development files • With/Without tool-relevant data • ECU family : : • Separating line Date: 20. 5-2: Prompt asking whether development data should be overwritten during export If you click "Yes". The following pieces of information are entered in a log file for each export procedure: • Date (format: dd.10.doc Version: 1.

. ECU-Familly-Data..10.ini. coapi.. ediabas.. .2.04 File: Handb-winkfpt32(5. 5-1: Structure of the target directories for exporting development data Date: 20. <Log-Filei> Fig. P-SGBD wille be placed together in a directory NFS\ bin\ cfgdat\ EDIABAS\bin\ winkfpt..ini.8_eng.WinKFPT User's Guide Page 90 5. .8 ..doc Version: 1.ini.2. .1)_v1. PABD.1 Directory Structure for Exporting Development Data configureable C:\Diagprog\Konfiguration\ enter manually on export <Name der Konfiguration>\ daten\ Entwicklung\ develop\ Complete Develop-Directory gdaten\ all GData from the working directory all P-SGBD ecu\ sgdat\ <sgfam1>\ <sgfam2>\ al PABD GData.2.

0BA.AS2.DA2 file and copied from NFS\Sgdat to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory.AS2 and INFO. HISTORIE.2. SGIDD.8_eng. *. The relevant parts of the HWNR.DAT. SGIDD. *. PABD: The name of the description file that belongs to the WDP is determined from the KFCONFXX.1)_v1.HIS. Date: 20. • Export tool-relevant data (optional) Copying of all the files with the extension *.IPS and *.0PA.BAF are copied from the NFS\Data\Develop directory to the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Develop directory.10. SGIDC.INI from the <root>\bin\ directory to the <root>\Diagprog\<configurationname>\NFS\bin\ directory.DA2 are copied from the NFS\Data\Gdaten directory to the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Gdaten directory.8 .DA2. <ECUFAM>.GER and KFCONFXX.DA2 and KFCONFXX. • Export WDPs (if one or more selected) Flash data. logistics data: The files *.0DA.DAT. SGIDC. <ECUFAM>.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 91 5.GER are copied from the NFS\Data\Gdaten directory to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory. *.BSU.PRG files are copied from the EDIABAS\ECU directory to the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Ecu directory. COMMON files: COMMON files SWTCONFX.PAF.doc Version: 1. COMMON files: COMMON files SWTCONFX. INFO.AS2.0BA <ECUFAM>. *. *.BSU.0DA.DAT. HISTORIE.ATS are copied from the <ecufam> directory to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory.DA2 files are determined and only these parts are copied to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory. HWNR.2.2 • Filing of the Files When Exporting Development Data Export development files (if released for export) Flash data: The files *.DAF and *.IPO files are copied from the NFS\Sgdat directory to the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Sgdat directory. P-SGBDs: All *. The file name of the COMMON file is adopted unchanged. P-SGBD: The name of the description file that belongs to the WDP is determined from the KFCONFXX.2. PABDs: All *.AS2.HWH and <ECUFAM>.DA2 file and copied from EDIABAS\ECU to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory. *.0PA.

INI from the <root>\EDIABAS\bin\ directory to the <root>\Diagprog\<configurationname>\EDIABAS\bin\ directory.8_eng. Date: 20.INI and *.04 File: Handb-winkfpt32(5.10. Copying of all the files with the extension *.doc Version: 1.1)_v1.WinKFPT User's Guide Page 92 Copying of all the files with the extensions *.8 .DAT from the <root>\cfgdat directory to the <root>\Diagprog\<configurationname>\NFS\cfgdat\ directory.

5-1: Deleting assembly line data.2.04 File: Handb-winkfpt32(5.1)_v1.8_eng.8 . message if no assembly line data is present In this case.doc Version: 1.3 Deleting Assembly Line Data You delete assembly line data by selecting the menu option Import/Export line data.assembly If there is no assembly line data present.10. Date: 20.WinKFPT User's Guide Page 93 5. the following message is displayed: Fig. You would first have to import assembly line data to enable flash programming. it is also not possible to conduct flash programming of ECUs in Comfort mode.  Delete .

WinKFPT User's Guide Page 94 If valid assembly line data does exist.04 File: Handb-winkfpt32(5. i.e.da2".8_eng. the following dialog window is opened: Fig. Date: 20.1)_v1.doc Version: 1. one. The directories of the assembly line data selected are completely deleted during the deletion procedure.8 . only if they are not used by one or more other ECU families at the same time. The associated description files (SGBD/PABD) are likewise deleted. but only if they occur no more than once in "kfconfxx.10. You can select either no data set at all. 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 for deletion. several or all of the assembly line data sets.

and the COMMON files "kfconfxx. the dialog window is closed.04 File: Handb-winkfpt32(5.da2". prompt displayed on clicking "Remove" If you click the function button "Remove all". If you click "No". The following prompt appears before deletion is started: Fig. you delete the selected WDPs from the list box and remove the corresponding entries from the COMMON files "kfconfxx. If you click the function button "Cancel".da2" and "hwnr.da2" and "hwnr.8_eng. deletion is started and the dialog window is closed once deletion has been completed. 5-4: Deleting assembly line data.10.e. Date: 20. 5-3: Deleting assembly line data. prompt displayed on clicking "Remove all" If you click "Yes".8 . all WDPs are selected and deleted.doc Version: 1. active deletion procedures are not interrupted. The following prompt appears before deletion is started: Fig.1)_v1. including all "dead" entries for which no WDPs exist.da2" are completely emptied with the exception of their headers. the prompt disappears from the screen and the dialog window remains open. i.WinKFPT User's Guide Page 95 By clicking the function button "Remove".

KWP2000. etc.8_eng. Date: 20. ADS. The menu option "Diagnosis protocol" enables you to choose dynamically between the diagnosis protocols that are supported by a selected control unit (BMW-Fast.WinKFPT User's Guide Page 96 5. The "Diagnosis protocol" menu option is only active if a selected control unit supports more than one diagnosis protocol.8 .). etc.doc Version: 1.10.).04 File: Handb-winkfpt32(5.4. The "HW interface" menu option is only active if HW interfaces are entered in the configuration file WINKFPT.INI").1)_v1.INI (see "3. A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABD and P-SGBD (Expert mode).3 Communication Menu This menu can be used to set the following parameters for communication between WinKFPT and control units: • Hardware interface • Diagnosis protocol The menu option "HW interface" enables you to switch dynamically between HW interfaces (EDIC.2 Configuration in WINKFPT.

All HW interface entries from WINKFPT.INI (see "3.WinKFPT User's Guide Page 97 5.1 Selecting (Choosing) a HW Interface You choose a HW interface by selecting the menu option Communication  HW interface. The HW interface unit is required by EDIABAS to enable it to distinguish between interfaces if several HW interfaces of the same type are integrated (installed) in one computer. A.04 File: Handb-winkfpt32(5.8_eng.4.INI") are presented in a list for selection. If only one interface of this type is integrated in the computer. B. C. • Then click "OK". E) for each HW interface.INI.10. To choose a HW interface: • Choose a HW interface from the "HW interface" list.8 . Fig. • Select the unit for the HW interface.2 Configuration in WINKFPT.doc Version: 1.3. 5-1: Selection dialog for HW interface The "HW interface" menu option is only active if HW interfaces are entered in the configuration file WINKFPT. Date: 20. you must select "_" (= default). You must select a unit identifier (_. D.1)_v1.

INI" is activated and displayed by default (see "3. the HW interface chosen is not installed as hardware or software. the HW interface defined in "EDIABAS.INI"). the following error message appears: Fig. Otherwise.WinKFPT User's Guide Page 98 If WinKFPT is able to activate the HW interface chosen.1)_v1. select a different setting straight away when starting a further WinKFPT instance with the aid of the calling parameters -INTERFACE=<HW interface> and -UNIT=<Unit identifier>.10. however.4 Configuration in EDIABAS.8 .doc Version: 1.4. You can. Fig. error message 304 (which you have to acknowledge) appears and the previous setting remains active. 5-2: Error message displayed when an impermissible choice of HW interface is made The same error occurs if. for example.8_eng. 5-3: Error message when the same HW interface+unit is accessed in Dialog mode When WinKFPT is started. If a different instance of WinKFPT has already accessed the same HW interface+unit. Date: 20.04 File: Handb-winkfpt32(5. the interface is displayed constantly in the "HW interface" box as status information.

If the job is present.8 .10. To choose a diagnosis protocol: • Choose a diagnosis protocol from the "Diagnosis protocol" list. Date: 20. The diagnosis protocol activated is displayed in the "Diagnosis protocol" box a status information. the diagnosis protocols specified in it are displayed in a list for selection.04 File: Handb-winkfpt32(5. If you do not make an explicit selection. WinKFPT automatically tries to call the job "DIAGNOSEPROTOKOLL_LESEN" from the corresponding P-SGBD.  Diagnosis Fig. • Then click "OK". A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABD and P-SGBD (Expert mode).8_eng.1)_v1. A selected diagnosis protocol is set internally by means of the P-SGBD job "DIAGNOSEPROTOKOLL_SETZEN".WinKFPT User's Guide Page 99 5. Once you have chosen a control unit. 5-1: Dialog box for selecting a diagnosis protocol The "Diagnosis protocol" menu option is only active if a selected control unit supports more than one diagnosis protocol. the first diagnosis protocol from the list is activated by default.doc Version: 1.3.2 Selecting (Choosing) a Diagnosis Protocol You choose a diagnosis protocol by selecting the menu option Communication protocol.

8 .doc Version: 1.04 File: Handb-winkfpt32(5.10.1)_v1.WinKFPT User's Guide Page 100 Date: 20.8_eng.

Fig.8 .4 Configuration Menu When you select this menu. 5-1: Configuration dialog window Date: 20.10.doc Version: 1.8_eng. the following configuration dialog window is opened.WinKFPT User's Guide Page 101 5.1)_v1.04 File: Handb-winkfpt32(5.

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. even if only data programming would be necessary. a program is to be programmed whatever the case. 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.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 102 The settings correspond to the following INI parameters: Dialog text Ini file entry Description Sprache / Language SPRACHE The entry defines the language for WinKFPT. i. The entry specifies whether the UIF is also programmed (ON) or not (OFF) during data programming in Comfort or Expert mode. Force program programming in PROGRAMM_ERZWINGEN comfort mode UIF write after data AIF_SCHREIBEN_NACH_DATEN The entry specifies whether.8_eng.10. flash programming of an NAAB file. Date: 20. Options: German (ger) and English (eng).8 . during flash programming in Comfort mode. Programming voltage U_PROG The entry specifies whether the programming voltage is switched ON or OFF during flash programming.1)_v1. is possible or not.doc Version: 1.e. activate Bootsectorupdate BsuActive The entry specifies whether a boot sector update.

PABD format CabdFormat The entry defines whether WinKFPT is to use PABDs as source files or as compiled files.1)_v1.8 . Description UIF write in expert mode EXPERT_MIT_AIF The entry specifies whether the UIF is also programmed (ON) or not (OFF) during flash programming in Expert mode. Storage directory for the ERRORn.10. UIF write in comfort mode KOMFORT_MIT_AIF The entry specifies whether the UIF is also programmed (ON) or not (OFF) during flash programming in Comfort mode. Date: 20.8_eng. IPS PABDs as source files IPO PABDs as compiled files API tracelevel API_TRACE IFH tracelevel IFH_TRACE Directory for error file "error.LOG file Base directory for export of a configuration of assembly line data (Comfort mode).04 File: Handb-winkfpt32(5.log" ErrorLogPath Base directory for exported KomfortKonfPath configurations – assembly line data The entry specifies the level for the API traces in Ediabas (0 means that the trace is switched off). The entry specifies the level for the IFH traces in Ediabas (0 means that the trace is switched off).doc Version: 1.WinKFPT User's Guide Page 103 Dialog text Ini file entry UIF write after program AIF_SCHREIBEN_NACH_PROGRAMM The entry specifies whether the UIF is also programmed (ON) or not (OFF) during program programming in Comfort or Expert mode.

10.doc Version: 1.04 File: Handb-winkfpt32(5. The User's Guide and the online help are identical. Message boxes prompt you to do this. 5. Base directory for directories of WinKFPT Base directory for the working directories: cfgdat.WinKFPT User's Guide Page 104 Dialog text Ini file entry Description Base directory for exported KomfortKonfPath configurations – assembly line data Base directory for export of a configuration of assembly line data (Comfort mode). data.5 Help Menu This menu is used to start the online help and display information about the program.8 . and you are given another chance to save this configuration to the Ini file when you end the session. you are asked whether you would like to save your changes permanently to the Ini file. working ExpertKonfPath If you close the dialog window by clicking "OK" and the settings in the window differ from those in the Ini file. If you change the PABD format and a PABD has already been selected.Calling the Online Help You call the online help by selecting the menu option Help  Contents. Date: 20.1 Contents .8_eng. 5. Whenever updates of WinKFPT are released. Even if you reject this option now.1)_v1. you must then explicitly select a new PABD in Expert mode or implicitly select a new PABD in Comfort mode by selecting an assembly identification number (ZB number). the settings you have entered remain valid for the duration of the WinKFPT session. This command displays the opening screen of the online help function. sgdat etc. the Word file of the User's Guide and the online help will both be updated.5.

8_eng.WinKFPT User's Guide Page 105 Fig.Version Information of WinKFPT You display the version information of WinKFPT by selecting the menu option Help This command displays the program version and copyright information.04 File: Handb-winkfpt32(5.1)_v1.doc Version: 1.2 Info .10.5.8 . 5-1 Online help of WinKFPT 5. Date: 20.  Info.

10.1)_v1.8 .04 File: Handb-winkfpt32(5. Displayed in the bottom right-hand corner are the creation date and time of the WinKFPT version.doc Version: 1.8_eng. 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 Krapi libraries.WinKFPT User's Guide Page 106 Fig. Date: 20.

04 File: Handb-winkfpt32(5.INI file.8 .10. The next time WinKFPT is launched.8_eng.WinKFPT User's Guide Page 107 5.4.doc Version: 1.3 Configuration for Expert Mode").6. If you have activated Expert mode at least once while using WinKFPT.INI").2 Configuration in WINKFPT.4. This command terminates the program. As WinKFPT is terminated. the program is started with the same window size and position (see "3. the last window size and window position of the application are saved as the entry WindowPosition in the WINKFPT.1)_v1.1 Exit You exit WinKFPT by selecting the menu option End  Exit.6 End Menu You use this menu to exit WinKFPT. you have the option before exiting WinKFPT of saving the current settings you have made in Expert mode so that you can call them up again the next time you start the program (see "3. 5. Date: 20.

doc Version: 1.8_eng.10.04 File: Handb-winkfpt32(5.8 .1)_v1.WinKFPT User's Guide Page 108 6 FUNCTIONS OF WINKFPT Date: 20.

1)_v1.Program load Dataset .10. execution phase Expert mode Dataset Data selected? Dataset Program selected? YES prog.WinKFPT User's Guide Page 109 MAIN MENU COMFORT-MODE EXPERT-MODE Clear all settings Prog. Level 2 enter ECU-Address load Dataset . execution phase FINISHED Do program Do program update Comfort mode Prog.Data YES Prog. settings phase enter ZUSB choose ZUSB update ZUSB FINISHED enter VIN NO FINISHED PABD and P-SGBD selected? YES NO ZUSB entered/selected? and VIN entered? Prog.8_eng.doc Version: 1.8 . Level 1 load PABD load P-SGBD Prog. settings phase. data YES prog. settings phase.04 File: Handb-winkfpt32(5. program Expert mode Comfort mode Special functions Read UIF Read ECU Baudrates Read and write calibration values VS2/DS2 mode EWS alignment Diagnosis functions read ECU status read ECU identification read ECU internal temperature Date: 20.

8 . 6-1: Functional hierarchy phases of WinKFPT Date: 20.1)_v1.WinKFPT User's Guide Page 110 Fig.10.04 File: Handb-winkfpt32(5.8_eng.doc Version: 1.

doc Version: 1.WinKFPT User's Guide Page 111 6.1 Function Start Menu: Operating Modes of WinKFPT This function menu is opened when a WinKFPT instance is started.10. 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. Use of the "general functions" is identical in both operating modes (see "9 General Functions"). The operating modes differ with respect to their • functions for entering and selecting job data for ECU flash programming during the programming settings phase. The function start menu offers you two WinKFPT operating modes to choose from: • Comfort mode • Expert mode.1)_v1.04 File: Handb-winkfpt32(5.8 .8_eng. Date: 20. • functions for flash programming control unit during the programming execution phase.

 ECU address Whether or not you need to enter the ECU address in Expert mode depends on the state of development of the description files. This address is then saved globally for further processing in the description files.doc Version: 1.8_eng. Date: 20.8 .10.1)_v1. in this case by means of a user input. The new standard description files must be fed an ECU address from outside. the description and data set files required for flash programming are determined from the job data with the aid of the BMW logistics files.ini".04 File: Handb-winkfpt32(5.these are as a rule the non-standardized description files . Flash programming with/without UIF writing can be set by means of the configuration file "winkfpt. Whether or not the ECU address has to be entered is determined automatically by WinKFPT and displayed to you on the screen.  Description files and data set files In Comfort mode.the ECU address is hard-coded for filling the protocol parameters and diagnosis telegrams.WinKFPT User's Guide Page 112 The following table contains the job data possible in the two operating modes: Mode Comfort mode Job data Name of the control unit family Assembly identification number Integration position <Vehicle identification number> Expert mode P-SGBD PABD ECU address Data set name for NAAB Data set file for program Data 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 are flash programming with subsequent writing of the user info field (UIF). In the older description files .

8_eng. selection of any number of integration positions offered for the ZUSB number.2. have to be conducted for end-of-line programming at the factory.doc Version: 1. Date: 20.8 .04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 113 6. including all logistical checks that. Prerequisite for flash programming of a control unit in Comfort mode is the presence of a complete assembly line data set for this control unit (see "5.1 Import Submenu"). Selection of a control unit family and of any number of integration positions offered for this family. whereby updating to an incompatible hardware release by means of a BSU is also taken into account. and subsequent updating of the control unit or control units to the latest assembly identification. entry of the vehicle identification number (VIN) when a UIF is written. for example.10. Control units can be flashed in Comfort mode in the following ways:   Entry or selection of the assembly identification number (ZUSB number).1. and subsequent flash programming of the control unit or control units.1 Comfort Mode This mode is used for flash programming control units.1)_v1.

The "Comfort mode" button takes you to the programming settings phase of Comfort mode to enable you to enter job data required for flash programming. the following job data and status displays from the preceding session 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 Date: 20.10. If the IPS format is set in the configuration when Comfort mode is entered.04 File: Handb-winkfpt32(5. 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"). 7-1: Programming execution phase in Comfort mode"). Only PABDs in IPO format are used in Comfort mode.  in the function menu of the programming execution phase of Expert mode (see "Fig.1. When you activate "Comfort mode".8_eng. if you click "Cancel". you do not enter Comfort mode. the following message box appears: Fig. the PABD format is automatically set to IPO.  in the function menu of the programming execution phase of Comfort mode (see "Fig.1 Starting Comfort Mode Comfort mode is started either by clicking the function button "Comfort mode" or by pressing function key <F1> on the keyboard.doc Version: 1.1. 8-1: Programming execution phase in Expert mode").1)_v1. 6-1: Format switchover on entering Comfort mode If you click "OK".8 .WinKFPT User's Guide Page 114 6.

Date: 20. When you activate "Comfort mode".WinKFPT User's Guide Page 115 • Hardware number are retained.10.1)_v1.8_eng. the job data and status displays from the preceding session in Expert mode are either completely deleted or are buffered for loading the last configuration for a renewed entry into Expert mode.8 .doc Version: 1.04 File: Handb-winkfpt32(5.

Afterwards.  To completely delete job data in Comfort mode. 6-1: Function start menu of WinKFPT).  You switch to Expert mode by activating the function button "Expert mode".WinKFPT User's Guide Page 116 6.04 File: Handb-winkfpt32(5.10. the following job data and status displays of 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-SGBD are retained and lead in Expert mode to the switch to programming settings phase Level 2 (see: Fig. WinKFPT displays the function start menu (see: Fig.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.1. Date: 20.doc Version: 1.1)_v1.1.8 . 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). 8-1: Programming settings phase Level 2 in Expert mode). When you activate "Expert mode".8_eng.

Caution! If you embark on actions of this kind. you do have the possibility of bypassing logistical restrictions by e. Date: 20.1)_v1.g.doc Version: 1. This ZB number is written to the UIF.1.INI"). you must carry out the following steps: Exit WinKFPT.8 . In Expert mode.1 Import Submenu").WinKFPT User's Guide Page 117 6. If • • • a different ZB number is to be entered in the UIF.INI" for checking purposes if EXPERT_MIT_AIF=ON is set in the configuration file "WINKFPT.: • 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.04 File: Handb-winkfpt32(5.4.INI". the graphical user interface (GUI) immediately displays the assembly identification number (ZB number) from the configuration file "COAPI.10.2. Restart WinKFPT. you must know precisely what you are doing because any error could lead to a control unit being rendered totally unusable for the future. Change the entry in "COAPI.INI" (see "3.8_eng. When you select Expert mode. Prerequisite for flash programming of a control unit in Expert mode is the presence of the description files and data sets wanted for this control unit (see "5.2 Expert Mode This mode is used to select or enter the job data (PABD.1 Configuration in COAPI. P-SGBD and data sets) and then flash program the control unit. Such a control unit would no longer be able to be flashed via diagnosis communication and would have to be submitted for recycling.

the following job data and status displays from the preceding 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-SGBD are retained.8_eng.04 File: Handb-winkfpt32(5.2.WinKFPT User's Guide Page 118 6. 6-1: Function start menu of WinKFPT"). 8-1: Programming execution phase in Expert mode").1 Starting Expert Mode Expert mode is started either by clicking the function button "Expert mode" or by pressing function key <F2> on the keyboard. The "Expert mode" function button is available in the following function phases:  in the function start menu (see "Fig.10. The "Expert mode" button takes you to the programming settings phase Level 1 or Level 2 of Expert mode to enable you to enter job data required for flash programming. Date: 20. 7-1: Programming execution phase in Comfort mode").doc Version: 1.1. When you activate "Expert mode".  in the function menu of the programming execution phase of Expert mode (see "Fig.8 .1)_v1.  in the function menu of the programming execution phase of Comfort mode (see "Fig. all job data and status displays from the preceding session in Expert mode are retained: When you activate "Expert mode".

8_eng. When you activate" Comfort mode". all job data and status displays of Expert mode are either completely deleted or are buffered for loading the last configuration for a renewed entry into Expert mode.1.10.8 .doc Version: 1.  You switch to Comfort mode by activating the function button "Comfort mode". After you click "Done" (or press <F8> in Comfort mode).WinKFPT User's Guide Page 119 6. Date: 20. 6-1: Function start menu of WinKFPT).2 Exiting Expert Mode You exit Expert mode by:  switching to Comfort mode.04 File: Handb-winkfpt32(5.1)_v1.2. WinKFPT displays the function start menu (see: Fig.

Function phase Functions Programming settings phase • Entering a ZUSB number • Choosing a ZUSB number • Updating an assembly identification No entries • Entering a VIN • Finishing the programming settings phase Programming execution phase • • • • Programming a ZUSB number Programming a ZUSB update Special Diagnosis Entries required for switching to the level Integration position(s) for a ZUSB number or a control unit family Table 7-1: Function phases of Comfort mode Date: 20.8 . The functions of the programming execution phase are used for flash programming one or more control units.1)_v1.8_eng.   The functions of the programming settings phase are used for entering or selecting all the job data required for flash programming.WinKFPT User's Guide Page 120 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.04 File: Handb-winkfpt32(5.doc Version: 1. Whether or not you can switching function phase depends on the scope of the job data you have entered.10.

7-1: Functions of the programming settings phase in Comfort mode Date: 20.8 .WinKFPT User's Guide Page 121 7. Fig.04 File: Handb-winkfpt32(5.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.8_eng.doc Version: 1.10.1)_v1.

doc Version: 1.8_eng. When you activate this function.WinKFPT User's Guide Page 122 7.04 File: Handb-winkfpt32(5. 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 message appears which you have to acknowledge.10. Fig.1)_v1. a dialog box opens in which you enter the assembly identification number (ZUSB number).1 Function: Entering a ZUSB Number You start the function for entering a ZUSB number either by clicking the "Enter ZUSB" button or by pressing function key <F1> on the keyboard. Date: 20.8 .1.

10. • If you click "OK".8_eng. input of the ZUSB number is aborted and the following error message displayed: Fig. your entry is discarded.WinKFPT User's Guide Page 123 • If you click "Cancel". 7-2: Error message . WinKFPT checks whether the ZUSB number you have entered is present in an <EcuFam>.04 File: Handb-winkfpt32(5.doc Version: 1.DAT file of the existing assembly line data sets in the \<root>\DATA8 directory.1)_v1.8 .ZUSB number not present in the logistics 8 <root> = installation directory of WinKFPT Date: 20. If the assembly identification number you have entered is not found or is invalid.

8_eng. a dialog window appears enabling you to choose one or more integration positions: Fig. • If you click "Cancel".04 File: Handb-winkfpt32(5.1)_v1. 7-3: Dialog window for choosing an ECU family.1. All you have to do is select one or more ECU addresses by means of their integration position(s) (see also "7. Select one. the ZB number entered and integration position selected are discarded.10.8 . the ZB number is adopted and displayed together with the corresponding hardware number as status information. Date: 20. • If you click "OK". several or all of the integration positions from the "Integration position" list in line with the standard Windows conventions.2 Function: Selecting a ZUSB number").doc Version: 1. assembly identification number and integration position The assembly identification number entered and the name of the ECU family associated with it are already highlighted in the window.WinKFPT User's Guide Page 124 If the assembly identification number entered is valid.

Control units that can be installed more than once in the same car are distinguished between only by means of their ECU address or integration position.8_eng.04 File: Handb-winkfpt32(5. The "Integration position" list contains all the integration positions \<root>\data\gdaten\INFO.1)_v1.WinKFPT User's Guide Page 125 7. assembly identification number and integration position(s) (see "Fig. the ZB number and integration position selected are discarded. This dialog box contains three lists: • "ECU family" . assembly identification number and integration position").2 Function: Selecting a ZUSB number You start the function for selecting a ZUSB number either by clicking the "Choose ZUSB" button or by pressing function key <F2> on the keyboard. through whose selection the ECU address is specified. containing at least one ZB number.8 . several or all of the integration positions from the "Integration position" list in line with the standard Windows conventions.which contains the integration positions that belong to the ECU family selected.which contains the assembly identification numbers that belong to the ECU family selected • "Integration position" . • If you click "Cancel". the ZB number is adopted and displayed together with the corresponding hardware number as status information.DAT file that belong to the ECU family selected.DAT. The "ECU family" list contains only those ECU families for which the logistics file <ecufam>. When you activate this function. present in the Select one. 7-3: Dialog window for choosing an ECU family.doc Version: 1. a dialog box opens in which you select an ECU family. The "ZB Number" list contains all the assembly identification numbers present in the <ecufam>. is present in the respective directories \<root>\data\<ecufam>9.10.which contains a list of ECU families or assembly line data sets that exist • "ZB Number" .1.ENG file that belong to the ECU family selected. • If you click "OK". 9 <root> = installation directory of WinKFPT Date: 20.

DAT. is present in the respective directories \<root>\data\<ecufam>9.1. Control units that can be installed more than once in the same car are distinguished between only by means of their ECU address or integration position.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. 7-1: Dialog box for updating an assembly identification This dialog box contains two lists: • "ECU family" . a dialog box opens in which you select an ECU family and integration position(s). When you activate this function. Fig.which contains a list of ECU families or assembly line data sets that exist • "Integration position" .1)_v1.04 File: Handb-winkfpt32(5.8_eng.10.WinKFPT User's Guide Page 126 7. containing at least one ZB number.which contains the integration positions that belong to the ECU family selected.8 . 9 <root> = installation directory of WinKFPT Date: 20. The "ECU family" list contains only those ECU families for which the logistics file <ecufam>.doc Version: 1. through whose selection the ECU address is specified.

WinKFPT User's Guide Page 127 The "Integration position" list contains all the integration positions \<root>\data\gdaten\INFO. Date: 20.8 .8_eng. • If you click "Cancel". • If you click "OK". the ECU family and integration position selected are discarded.04 File: Handb-winkfpt32(5.10.1)_v1.GER file that belong to the ECU family selected. ECU address and diagnosis protocol) displayed. the selection is adopted and the corresponding pieces of status information (description files.doc Version: 1. present in the Select one. several or all of the integration positions from the "Integration position" list in line with the standard Windows conventions.

WinKFPT
User's Guide
Page 128

7.1.4

Function: Entering a Vehicle Identification Number

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 file
WINKFPT.INI
When you activate this function, a dialog box opens in which you enter the vehicle identification
number.

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 the
following error message appears which you have to acknowledge.

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

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 129

• 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 identification
number is mandatory if KOMFORT_MIT_AIF=ON is set in WINKFPT.INI
Flash 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 identification
number by means of the "Enter VIN" function because in this case the vehicle identification number
from 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 is
entered in the new UIF.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 130

7.1.5

Function: Done (Comfort Mode)

The "Done" function completes and ends input and selection of the job data in the programming
settings phase of Comfort mode.
You start the function either by clicking the "Done" button or by pressing function key <F8> on the
keyboard.

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 program
switches to the "Program" function in the function menu of the programming execution phase of
Comfort mode.
Note:
If, with KOMFORT_MIT_AIF=ON set in the configuration file WINKFPT.INI, no vehicle identification
number is entered, it is not possible to flash program the control unit, and only the general functions
are displayed following switching of the function phase (see Fig. 9-1: Function menu with the
function 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.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

1)_v1.WinKFPT User's Guide Page 131 7.8 .10. 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. Date: 20. Diagnosis) • Ending of the programming execution phase of Comfort mode by switching to the programming settings phase of Comfort mode or Expert mode.8_eng. Fig.04 File: Handb-winkfpt32(5.doc Version: 1.2 Functions of the Programming Execution Phase in Comfort Mode The following status information is displayed when the switch is made to the programming execution phase 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.

This function button/key starts flash programming of one or more control units in Comfort mode. You start the function either by clicking the "Program" button or by pressing function key <F3> on the keyboard.WinKFPT User's Guide Page 132 7. Date: 20. 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.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 (with KOMFORT_MIT_AIF=ON set in WINKFPT.8 .1)_v1.INI) in the programming settings phase of Comfort mode.10.INI.04 File: Handb-winkfpt32(5. too. If KOMFORT_MIT_AIF=ON is set in configuration file WINKFPT.doc Version: 1.8_eng.2. the following prompt appears before ECU flash programming starts: Fig.

100 %) and as a percentage display in the blue menu status line.1)_v1. 7-2: ECU flash programming in Comfort mode The status of the programming procedure is indicated by a progress bar (0 .8 . • If you click "OK". Fig.10. programming is started. Date: 20.INI. "Programming voltage" is displayed in the top right-hand corner.04 File: Handb-winkfpt32(5. programming is aborted. If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.8_eng.WinKFPT User's Guide Page 133 • If you click "Cancel".doc Version: 1.

04 File: Handb-winkfpt32(5. 7-4: Message displayed when multiple programming has been successful Date: 20.INI file is explicitly set to OFF. At the end of the multiple programming procedure. and programming is started again by clicking the "Program" function button (or pressing <F3>). the job data for the next programming procedure is displayed automatically after each programming procedure. the message <<Multiple programming finished>> appears: Fig.8_eng. In the event of multiple selection of control units. This means it is possible to abort or to change settings (e.WinKFPT User's Guide Page 134 At the end of the ECU flash programming procedure.10.doc Version: 1. 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.8 .1)_v1.g. the message <<Programming OK>> appears: Fig. HW interface or diagnosis protocol) at any time between the individual programming procedures.

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. This function button starts updating of a control unit to the latest assembly identification.his (= ZUSB history). These two assembly identification numbers are displayed in a dialog box that has to be acknowledged: Fig. programming to the latest assembly identification number is aborted.doc Version: 1.8_eng.2. • If you click "Yes". Date: 20.2 Function: Programming Update A control unit is flashed to the latest assembly identification by activating "Prog. the latest (current) assembly identification number is read from the file \<root>\data\<ecufam>\<ecufam>. programming (updating) to the latest assembly identification number is started. the vehicle identification number and the assembly identification number are read out of the last UIF entry in the control unit.10.8 .04 File: Handb-winkfpt32(5. corresponding ZUSB history is possible. For this purpose. In addition to this assembly identification number.WinKFPT User's Guide Page 135 7. ZB-Update". 7-1: Dialog box displaying the ZB number from the ECU and the current ZB number • If you click "No". Updating to an incompatible hardware release by means of BSU (boot sector update) is also borne in mind. A switch to a different ECU family and therefore to a new.1)_v1. ZB-Update" button or by pressing function key <F3> on the keyboard. You start the function either by clicking the "Prog.

WinKFPT User's Guide Page 136 If KOMFORT_MIT_AIF=ON is set in configuration file WINKFPT. Date: 20. 7-2: 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.100 %) and as a percentage display in the blue menu status line. programming is started.8 . the following prompt appears before ECU flash programming starts: Fig. programming is aborted. • If you click "Cancel".1)_v1. "Programming voltage" is displayed in the top right-hand corner.doc Version: 1. • If you click "OK". If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI.INI. 7-2: ECU flash programming in Comfort mode"). "Fig.04 File: Handb-winkfpt32(5. The status of the programming procedure is indicated by a progress bar (0 .8_eng.10.

INI file is explicitly set to OFF.doc Version: 1. and programming is started again by clicking the "Prog.WinKFPT User's Guide Page 137 At the end of the ZUSB update programming procedure. the message <<ZUSB-Update programming OK>> appears: Fig. In the event of multiple selection of control units.10.04 File: Handb-winkfpt32(5.g. HW interface or diagnosis protocol) at any time between the individual programming procedures. the job data for the next programming procedure is displayed automatically after each programming procedure. At the end of the multiple programming procedure. ZB-Update" function button (or pressing <F3>).8_eng. 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. This means it is possible to abort or to change settings (e. the message <<Multiple ZUSB-Update programming finished>> appears: Fig.8 .1)_v1. 7-4: Message displayed when multiple ZUSB update programming has been successful Date: 20.

Whether or not you can switching function phase depends on the scope of the job data you have entered.8_eng. just P-SGBD • Entering an ECU address • Loading a data set – NAAB file Programming settings phase Level 2 • Loading a data set – program file • Loading a data set – data file • Ending the function phase Both description files PABD and P-SGBD • Programming a NAAB data set Programming execution phase • • • • Programming a program data set Programming a data data set Special Diagnosis Description files (PABD and P-SGBD). The functions of the programming execution phase are used for flash programming a program data set or data data set. The functions of programming settings phase Level 2 are used to enter the ECU address and select data set files.WinKFPT User's Guide Page 138 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.8 . data set files (for Program and/or Data). just PABD. <ECU address> Table 8-1: Function phases of Expert mode Date: 20.1)_v1.10. Function phase Functions Entries required for switching to the level Programming settings phase Level 1 • Loading a PABD • Loading a P-SGBD • Ending the function phase No entries.doc Version: 1.04 File: Handb-winkfpt32(5.    The functions of programming settings phase Level 1 are used to select the description files.

8-1: Functions of programming settings phase Level 1 in Expert mode Date: 20.doc Version: 1.04 File: Handb-winkfpt32(5.8_eng.WinKFPT User's Guide Page 139 8.1)_v1.10.8 . Fig.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.

e. Date: 20. files can be available in source code or in compiled form.1.04 File: Handb-winkfpt32(5.doc Version: 1. 8-1: Dialog box for selecting a PABD The source code of the flash sequence description files (PABDs) is available in the INPA script language. the compiled form is generated from the source code by means of the CABI compiler.10. WinKFPT can process both forms of a PABD.IPS  PABD in source code • 17EK924.8 .1)_v1. Since the functionality of the CABI compiler is integrated in the COAPI.: • 17EK924. The criterion by which source code and the compiled form can be distinguished is the extension of the PABD file name.WinKFPT User's Guide Page 140 8.IPO  PABD in compiled form.1 Function: Loading a PABD You start the function for selecting a PABD either by clicking the "PABD" button or by pressing function key <F1> on the keyboard.g. a dialog box opens in which you select a PABD. Fig. When you activate this function. For processing in WinKFPT.8_eng.

04 File: Handb-winkfpt32(5.1)_v1.INI and COAPI. selection of a PABD is aborted.3.10. • If you click "Cancel".4. the menu option "Diagnosis protocol" is activated and the default diagnosis protocol is displayed as status information (see "5.   P-SGBD not selected: the function menu for programming settings phase Level 1 remains active. • If you click "OK". The PABD selected beforehand remains selected.INI (see "3. This depends on the CabdFormat configuration set in WINKFPT. P-SGBD selected: the program switches to the function menu for programming settings phase Level 2. WinKFPT automatically checks whether a P-SGBD has already been selected and is displayed as status information.4.1 Configuration in COAPI. After you have selected a PABD.INI"). you implicitly select a control unit and the program checks whether the control unit supports more than one diagnosis protocol.WinKFPT User's Guide Page 141 This dialog box displays either all the files in the <root>\SGDAT 11 directory that have the extension IPS or the extension IPO. By selecting a PABD and P-SGBD.8_eng.doc Version: 1. If this is the case.2 Selecting (Choosing) a Diagnosis Protocol").8 . "3.2 Configuration in WINKFPT. 11 <root> = installation directory of WinKFPT Date: 20. the PABD is adopted and "PABD" is displayed as status information.INI".

the P-SGBD is adopted and "P-SGBD" is displayed as status information.WinKFPT User's Guide Page 142 8. 12 <ediabas> = installation directory for EDIABAS interface Date: 20. 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.doc Version: 1.10. • If you click "OK".04 File: Handb-winkfpt32(5. selection of a P-SGBD is aborted. a dialog box opens in which you select a P-SGBD.1)_v1. When you activate this function. The P-SGBD selected beforehand remains selected.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 pressing function key <F2> on the keyboard. • If you click "Cancel".8_eng. Fig.

1)_v1.doc Version: 1.8_eng. you implicitly select a control unit and the program checks whether the control unit supports more than one diagnosis protocol.2 Selecting (Choosing) a Diagnosis Protocol").3.8 . PABD selected: the program switches to the function menu for programming settings phase Level 2.   PABD not selected: the function menu for programming settings phase Level 1 remains active. Date: 20.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 143 After you have selected a P-SGBD.10. If this is the case. the menu option "Diagnosis protocol" is activated and the default diagnosis protocol is displayed as status information (see "5. WinKFPT automatically checks whether a PABD has already been selected and is displayed as status information. By selecting a PABD and P-SGBD.

10.8_eng.04 File: Handb-winkfpt32(5.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.WinKFPT User's Guide Page 144 8.8 .doc Version: 1. 8-1: Programming settings phase Level 2 in Expert mode Date: 20.1)_v1. Fig.

8_eng. does not guarantee that the ECU can be addressed via this address because there is so far no communication with the control unit for this job. Date: 20. input of the ECU address is completed. This involves the program calling a P-SGBD job in order to set the ECU address globally.1 Function: Loading an ECU address You start the function for entering an ECU address either by clicking the "ECU Address" button or by pressing function key <F3> on the keyboard.10. • If you click "OK". 8-1: Dialog box for an ECU address Note! The ECU address must consist of 2 digits and be hexadecimal otherwise an error message appears which you have to acknowledge and the dialog box is closed. • If you click "Cancel". If this job is present in the P-SGBD. input of an ECU address is aborted and the ECU address entered beforehand remains entered.doc Version: 1.2.1)_v1.8 . If the P-SGBD does not contain a job for setting the ECU address. Fig. a dialog box opens in which you enter an ECU address.04 File: Handb-winkfpt32(5. A control unit that is addressed using an incorrect address does not answer and an error message to this effect is displayed.WinKFPT User's Guide Page 145 8. When you activate this function. the address is fixed in the PSGBD and is the text "P-SGBD using internal address" is displayed as status information under "ECU address/integration position". the ECU address you have entered is displayed as status information under "ECU address/integration position". This. however.

selection of a NAAB data set is aborted and the NAAB data set selected beforehand remains entered. selection of a NAAB data set is completed and displayed as status information in "NAAB file".04 File: Handb-winkfpt32(5.8 .WinKFPT User's Guide Page 146 8. • If you click "OK".doc Version: 1.2 Function: Loading a Data Set – NAAB File NAAB: Boot update description file. 8-1: Dialog box for selecting a NAAB data set This dialog box displays all the files in the \<root>\data\develop12 directory with the extensions 0BA and BAF.1)_v1. You start the function for selecting a NAAB data set either by clicking the "NAAB file" button or by pressing function key <F6> on the keyboard. When you activate this function. a dialog box opens in which you select a NAAB data set: Fig. • If you click "Cancel".2.8_eng.10. This is a data file that is flashed to the program area of an ECU and contains the program for boot sector update and the boot sector itself. The program executes the boot sector update immediately following an ECU reset. 12 <root> = installation directory of WinKFPT Date: 20.

10.doc Version: 1. Date: 20. 8-1: Error message if no ECU address has been entered in Expert mode"). an error message to this effect is displayed (see "Fig. • Control unit is not connected or does not answer: The control unit does not answer and an error message to this effect is displayed. It is not possible to switch to the programming execution phase of Expert mode unless you have entered an ECU address. 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).1)_v1.8_eng. It is possible to switch to the programming execution phase of Expert mode.WinKFPT User's Guide Page 147 Once the NAAB data set has been selected.8 . the UIF is read. • ECU address entered is wrong: The control unit can not answer and an error message to this effect is displayed. The data set remains selected.04 File: Handb-winkfpt32(5.

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 or by pressing function key <F5> on the keyboard. a dialog box opens in which you select a program data set: Fig. 12 <root> = installation directory of WinKFPT Date: 20.8_eng.WinKFPT User's Guide Page 148 8. When you activate this function.1)_v1.10.04 File: Handb-winkfpt32(5.doc Version: 1.8 .2. 8-1: Dialog box for selecting a program data set This dialog box displays all the files in the \<root>\data\develop12 directory with the extensions 0PA and PAF.

selection of a program data set is completed and displayed as status information in "Program file".1)_v1. To this end. • Control unit is not connected or does not answer: The control unit does not answer and an error message to this effect is displayed.8_eng. you should select the data set once again so that comparison of the references is not unintentionally suppressed. the hardware reference is read out of the control unit and compared with the reference of the data set (keyword: $REFERENZ). WinKFPT checks whether the data set matches the control unit. Date: 20.04 File: Handb-winkfpt32(5. selection of a program data set is aborted and the program data set selected beforehand remains entered. 8-1: Error message if no ECU address has been entered in Expert mode").8 . It is possible to switch to the programming execution phase of Expert mode. Note: Since the data set remains selected and consequently does not have to be reselected once the ECU address has been corrected. The data set remains selected. 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). It is possible to switch to the programming execution phase of Expert mode. It is not possible to switch to the programming execution phase of Expert mode unless you have entered an ECU address.10. • If you click "OK". • ECU address entered is wrong: The control unit can not answer and an error message to this effect is displayed.doc Version: 1. Once the program data set has been selected. Note: Since the data set remains selected and consequently does not have to be reselected once the control unit has been properly connected.WinKFPT User's Guide Page 149 • If you click "Cancel". you should select the data set once again so that comparison of the references is not unintentionally suppressed. an error message to this effect is displayed (see "Fig.

doc Version: 1. 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:".8_eng. N.1)_v1. 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.8 .10.: The control unit may be unusable following programming and have to be submitted for recycling.WinKFPT User's Guide Page 150 • Hardware reference from the ECU and reference from the data set do not match up: The following error message is displayed: Fig.04 File: Handb-winkfpt32(5.B. Date: 20.

8 .WinKFPT User's Guide Page 151 8. 13 <root> = installation directory of WinKFPT Date: 20. 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\develop13 directory with the extensions 0DA and DAF.04 File: Handb-winkfpt32(5.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 by pressing function key <F4> on the keyboard.1)_v1.10. When you activate this function.8_eng.2.doc Version: 1.

To this end. selection of a data data set is completed and displayed as status information in "Data file". • ECU address entered is wrong: The control unit can not answer and an error message to this effect is displayed. Date: 20. you should select the data set once again so that comparison of the references is not unintentionally suppressed. WinKFPT checks whether the data set matches the control unit. It is not possible to switch to the programming execution phase of Expert mode unless you have entered an ECU address. selection of a data data set is aborted and the data data set selected beforehand remains entered. • If you click "OK". Note: Since the data set remains selected and consequently does not have to be reselected once the ECU address has been corrected.04 File: Handb-winkfpt32(5. It is possible to switch to the programming execution phase of Expert mode. It is possible to switch to the programming execution phase of Expert mode.8_eng. you should select the data set once again so that comparison of the references is not unintentionally suppressed. 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).1)_v1.WinKFPT User's Guide Page 152 • If you click "Cancel".8 . 8-1: Error message if no ECU address has been entered in Expert mode").10. an error message to this effect is displayed (see "Fig.doc Version: 1. Once the data data set has been selected. Note: Since the data set remains selected and consequently does not have to be reselected once the control unit has been properly connected. The data set remains selected. the data reference is read out of the control unit and compared with the reference of the data set (keyword: $REFERENZ). • Control unit is not connected or does not answer: The control unit does not answer and an error message to this effect is displayed.

The data data set can be programmed even if the references do not match up.WinKFPT User's Guide Page 153 • Data reference from the ECU and reference from the data set do not match up: The following error message is displayed: Fig. N. It is possible to switch to the programming execution phase of Expert mode.8 .8_eng.1)_v1.B. Date: 20. 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:".: The control unit may be unusable following programming and have to be submitted for recycling.10.doc Version: 1.04 File: Handb-winkfpt32(5.

the text "P-SGBD using internal address" is displayed as status information under "ECU address/integration position". P-SGBD. the program switches to the function start menu.WinKFPT User's Guide Page 154 8. • If a PABD.2. • If only a P-SGBD has been selected.5 Function: Done (Expert Mode) The "Done" function completes and ends input and selection of the job data in programming settings phase Levels 1 and 2 of Expert mode. the program switches to the function start menu.8 . only the general functions are made available for use (see "9 General Functions"). ECU address and a data set for program and/or data have been selected. P-SGBD and ECU address have been selected.8_eng. the program switches to the function start menu (see Fig. the following error message is displayed: Fig.10.1)_v1. • If a PABD.doc Version: 1. Date: 20. the program switches to the function start menu. PABD and P-SGBD remain selected and you can now enter the ECU address. the program switches to the function menu of the programming execution phase of Expert mode. the program checks whether an ECU address has to be entered. 6-1: Function start menu of WinKFPT). • If only a PABD has been selected.04 File: Handb-winkfpt32(5. If an ECU address is required and one has not been entered. You start the function either by clicking the "Done" button or by pressing function key <F8> on the keyboard. • If a PABD and P-SGBD have been selected. 8-1: Error message if no ECU address has been entered in Expert mode When you acknowledge the error message. Activating this function leads to a switch of function phase: • If no entries have been made. If an ECU address is not required.

1)_v1.doc Version: 1.WinKFPT User's Guide Page 155 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 execution phase 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.04 File: Handb-winkfpt32(5.8 . Diagnosis) • Ending of the programming execution phase of Expert mode by switching to the programming settings phase of Comfort mode or Expert mode.8_eng.INI is set to ON. Date: 20. 10 Vehicle identification number is displayed only if the EXPERT_MIT_AIF entry in WINKFPT.10.

8-1: Programming execution phase in Expert mode 8. Date: 20.8_eng.10. NAAB" button or by pressing function key <F3> on the keyboard.doc Version: 1.3.1 Function: Programming a NAAB Data Set You start the function for programming a NAAB data set either by clicking the "Prog. The function button is activated only following successful selection of an NAAB data set file by means of the "NAAB file" function in programming settings phase Level 2 of Expert mode.WinKFPT User's Guide Page 156 Fig.04 File: Handb-winkfpt32(5.1)_v1.8 .

1)_v1.100 %) and as a percentage display in the blue menu status line. the message <<Bootsektorupdate OK>> appears: Fig.04 File: Handb-winkfpt32(5.10.INI. At the end of the ECU flash programming procedure and exchange of the boot sector. "Programming voltage is displayed in the top right-hand corner.8_eng.8 . If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT. 8-1: Message displayed following successful ECU flashing programming in Expert mode Date: 20.WinKFPT User's Guide Page 157 The status of the programming procedure is indicated by a progress bar (0 .doc Version: 1.

8-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.04 File: Handb-winkfpt32(5.3.1.4 Function: Entering a Vehicle Identification Number"). Without a vehicle identification number. Date: 20. Note: The user info field is programmed only if the configuration settings EXPERT_MIT_AIF and AIF_SCHREIBEN_NACH_PROGRAMM in WINKFPT.8_eng.1)_v1.WinKFPT User's Guide Page 158 8. Program" button or by pressing function key <F3> on the keyboard.INI are set to ON.10. The function button is activated only following successful selection of a program data set file by means of the "Program file" function in programming settings phase Level 2 of Expert mode. The following prompt appears once you have entered the vehicle identification number: Fig.doc Version: 1. programming is not possible in this case.2 Function: Programming a Program Data Set You start the function for programming a program data set either by clicking the "Prog. the dialog box for entering the vehicle identification number appears (see "7. Note: If a UIF is to be programmed.8 .

If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.WinKFPT User's Guide Page 159 The status of the programming procedure is indicated by a progress bar (0 .8 . 8-2: ECU flash programming in Expert mode At the end of the ECU flash programming procedure.1)_v1. "Programming voltage" is displayed in the top right-hand corner.8_eng.doc Version: 1.INI.04 File: Handb-winkfpt32(5.100 %). Fig. the message <<Programming OK>> appears: Date: 20.10.

1.3. 8-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.8_eng. 8-3: Message displayed following successful ECU flashing programming in Expert mode 8. Note: If a UIF is to be programmed.WinKFPT User's Guide Page 160 Fig.doc Version: 1. The function button is activated only following successful selection of a data data set file by means of the "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 and AIF_SCHREIBEN_NACH_DATEN in WINKFPT. Data" button or by pressing function key <F5> on the keyboard. Without a vehicle identification number. the dialog box for entering the vehicle identification number appears (see "7.1)_v1.04 File: Handb-winkfpt32(5. The following prompt appears once you have entered the vehicle identification number: Fig.10.8 .4 Function: Entering a Vehicle Identification Number").3 Function: Programming a Data Data Set You start the function for programming a data data set either by clicking the "Prog. Date: 20. programming is not possible in this case.INI are set to ON.

"Programming voltage" is displayed in the top right-hand corner.doc Version: 1.INI. Date: 20. the message <<Programming OK>> appears (see "Fig. At the end of the ECU flash programming procedure.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 161 The status of the programming procedure is indicated by a progress bar (0 .100 %) (see "Fig.8_eng.8 . If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT. 8-3: Message displayed following successful ECU flashing programming in Expert mode").1)_v1. 8-2: ECU flash programming in Expert mode").10.

8 . P-SGBD and ECU address (ECU address only if the P-SGBD uses an external address) have been selected/entered (see "8. • once the programming settings phase of Comfort mode has been completed and a ZUSB number and ECU address/integration position have been selected/entered by means of one of the following functions: "Enter ZUSB". a minimum amount of job data must have been entered in the active operating mode of WinKFPT.WinKFPT User's Guide Page 162 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 corresponding function key on the keyboard: • "Special" • "Diagnosis" Fig.10. "Choose ZUSB" or "Update ZUSB" (see "7.2 Functions of Programming Settings Phase Level 2 in Expert Mode").doc Version: 1. 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 least one PABD.1 Functions of the Programming Settings Phase in Comfort Mode"). 9-1: Function menu with the function buttons "Special" and "Diagnosis" Since calling a general function always involves communicating with an ECU. Date: 20.04 File: Handb-winkfpt32(5.8_eng.1 Functions of Programming Settings Phase Level 1 in Expert Mode" and "8.1)_v1.

1)_v1.doc Version: 1.10. 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 Date: 20.8 .1 Special Functions When you click the "Special" function button (or press <F3>) in Expert or Comfort mode.04 File: Handb-winkfpt32(5. the function menu with the function buttons for calling the special functions of WinKFPT is opened: Fig.8_eng.WinKFPT User's Guide Page 163 9.

04 File: Handb-winkfpt32(5.OUT file are overwritten every time "Read UIF" is activated.1. all the user info field (UIF) entries of the control unit are read out and displayed by the following PABD job: • SG_AIF_LESEN Prerequisite for this is a valid UIF entry in the control unit.1)_v1.8 .doc Version: 1.WinKFPT User's Guide Page 164 9. The contents of the AIF_<Interface>_<Unit>.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.8_eng.OUT in the \<root>\BIN directory. The file name is displayed in the header of the UIF display dialog.10. Date: 20. The contents of the UIF display dialog are written to the file AIF_<Interface>_<Unit>.

04 File: Handb-winkfpt32(5.doc Version: 1. 9-1: Display dialog for the Special function "Read UIF" You close the UIF display dialog by clicking "OK".10. Date: 20.WinKFPT User's Guide Page 165 Fig.8_eng.8 .1)_v1.

1.04 File: Handb-winkfpt32(5.8_eng.8 . Date: 20. When you activate this function.doc Version: 1.OUT in the \<root>\BIN directory.10. The contents of the BD_<Interface>_<Unit>.1)_v1.2 Function: Reading the ECU Baudrates You start the function for displaying the ECU baudrates of a control unit either by clicking the "ECU baudrates" button in the Special function menu or by pressing function key <F2> on the keyboard.OUT file are overwritten every time "ECU baudrates" is activated. This functionality is no longer supported by standard PABD jobs. all the possible baudrates of the control unit are read out and displayed by the following PABD job: • BAUDRATE_LESEN The contents of the ECU baudrates display dialog are written to the file BD_<Interface>_<Unit>.WinKFPT User's Guide Page 166 9.

8_eng.04 File: Handb-winkfpt32(5.10.1)_v1.8 . 9-1: Error message displayed when you call "ECU baudrates" Date: 20.WinKFPT User's Guide Page 167 If you call "ECU baudrates" for control units with standard description files.doc Version: 1. the following error message appears: Fig.

The submenu for calibration values is closed and the Special function menu is displayed again.8 . Date: 20.WinKFPT User's Guide Page 168 9. 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 to another control unit. When you activate this function. • Click the "Read Calib. • Connect the control unit to which the calibration values are to be written. The "Write Calib. • If necessary.10. • Click the "Write Calib.doc Version: 1.1. A message confirming that the data has been successfully transferred is then displayed. the submenu for reading and writing the calibration values of the control unit opens." button or press <F1> on the keyboard. The calibration values are read out of the temporary file and written to the ECU. Procedure for transferring calibration values: • Connect the control unit from which the calibration values are to be read. The calibration values are read out of the ECU and buffered in a temporary file.1)_v1.8_eng.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 clicking the "Calibration values" button in the Special function menu or by pressing function key <F3> on the keyboard." function button is now active. Fig. You close the submenu for calibration values either by clicking the "Done" button or by pressing function key <F8> on the keyboard. select the HW interface and diagnosis protocol for the second control unit." button.04 File: Handb-winkfpt32(5.

8_eng. By activating "VS20 Mode" or "DS2 Mode" from this submenu.10. When you activate this function. the control unit connected can be switched to VS20 or DS2 mode by means of the PABD job VS20_MODE or D2 MODE.8 . This functionality is no longer supported by standard PABD jobs. the following error message appears: Fig.4 Function: VS20/DS2 Mode You start the function for selecting VS20/DS2 mode either by clicking the "VS20/DS2-Mode" button in the Special function menu or by pressing function key <F4> on the keyboard. 9-1: Error message displayed when you call "VS20 Mode" or "DS2 Mode" Date: 20. WinKFPT switches to the submenu for VS20/DS2 mode.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 169 9.1.doc Version: 1.1)_v1. If you call "VS20 Mode" or "DS2 Mode" for control units with standard description files.

9-1: Message displayed when you call "EWS Alignment" 9.10.8 . This functionality is no longer supported. the Special function menu is closed and WinKFPT switches back to the main menu or to the function phase of the operating mode from which the Special function menu was started.1.WinKFPT User's Guide Page 170 9.doc Version: 1. Date: 20.1)_v1.1. the following message appears: Fig. When you activate this function. When you call "EWS Alignment".5 Function: EWS Alignment You start the function for EWS alignment either by clicking the "EWS Alignment" button in the Special function menu or by pressing function key <F5> on the keyboard.04 File: Handb-winkfpt32(5.6 Function: Done You close the Special function menu either by clicking the "Done" button in the Special function menu or by pressing function key <F8> on the keyboard.8_eng.

WinKFPT User's Guide Page 171 9.8_eng.1)_v1. 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 Date: 20.10.doc Version: 1.8 .04 File: Handb-winkfpt32(5. the function menu with the function buttons for calling the diagnosis functions of WinKFPT is opened: Fig.2 Diagnosis Functions When you click the "Diagnosis" function button (or press <F4>) in Expert or Comfort mode.

OUT file are overwritten every time "ECU Status" is activated.8 . 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>.WinKFPT User's Guide Page 172 9.2.1)_v1. The contents of the REF_<Interface>_<Unit>.04 File: Handb-winkfpt32(5.OUT in the \<root>\BIN directory.doc Version: 1. Date: 20. When you activate this function.1 Function: Displaying the ECU Status You start the function for displaying the ECU status of a control unit either by clicking the "ECU Status" button in the Diagnosis function menu or by pressing function key <F1> on the keyboard.8_eng. The file name is displayed in the header of the ECU status display dialog.10.

9-1: Display dialog for the ECU status You close the ECU status display dialog by clicking "OK".8 .8_eng.WinKFPT User's Guide Page 173 Fig. Date: 20.doc Version: 1.10.04 File: Handb-winkfpt32(5.1)_v1.

1)_v1.doc Version: 1. Fig.04 File: Handb-winkfpt32(5.WinKFPT User's Guide Page 174 9.OUT in the \<root>\BIN directory. The contents of the IDENT_<Interface>_<Unit>.2. When you activate this function. 9-1: Display dialog for the ECU identification You close the ECU identification display dialog by clicking "OK". The file name is displayed in the header of the ECU identification display dialog.2 Function: Reading the ECU Identification You start the function for displaying the identification of a control unit either by clicking the "ECU Ident" button in the Diagnosis function menu or by pressing function key <F2> on the keyboard.10.8_eng. the identification data of the control unit is read out and displayed by the following PABD jobs: • SG_IDENT_LESEN • SG_PHYS_HWNR_LESEN The contents of the ECU identification display dialog are written to the file IDENT_<Interface>_<Unit>.8 .OUT file are overwritten every time "ECU Ident" is activated. Date: 20.

Fig. the internal temperature of the control unit is read out and displayed. When you activate this function.doc Version: 1. Date: 20. The file name is displayed in the header of the ECU internal temperature display dialog. The contents of the INNENTMP_<Interface>_<Unit>.3 Function: Reading the ECU Internal Temperature You start the function for displaying the internal temperature of a control unit either by clicking the "ECU intern.OUT in the \<root>\BIN directory.04 File: Handb-winkfpt32(5. Temp" button in the Diagnosis function menu or by pressing function key <F3> on the keyboard.8_eng.OUT file are overwritten every time "ECU intern.WinKFPT User's Guide Page 175 9.2. 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 file INNENTMP_<Interface>_<Unit>. the following message is displayed which you have to acknowledge: <<ECU internal temperature not supported>> You close the ECU internal temperature display dialog by clicking "OK".8 . Temp" is activated.10.1)_v1. 9-1: Display dialog for the ECU internal temperature If the control unit does not support this function.

04 File: Handb-winkfpt32(5.10.4 Function: Done You close the Diagnosis function menu either by clicking the "Done" button in the Diagnosis function menu or by pressing function key <F8> on the keyboard. Date: 20.8 . the Diagnosis function menu is closed and WinKFPT switches back to the main menu or to the function phase of the operating mode from which the Diagnosis function menu was started.2.1)_v1.doc Version: 1. When you activate this function.WinKFPT User's Guide Page 176 9.8_eng.

• Displaying errors in WinKFPT functions with COAPI calls: Each time an error occurs when a COAPI function is called.) Each component contains a multitude of potential errors that must be trapped by WinKFPT and displayed to the user in a manner that enables him to recognize the cause from the error message displayed and eliminate this cause on his own initiative. Date: 20. diagnosis and info texts in appropriate message boxes. The list box below this contains a detailed list of errors traced through all the COAPI call levels run through. rather as a breakdown of just a single error.8_eng. The top text box in this dialog contains a text that informs you of which active WinKFPT function the error has occurred in. The texts are loaded dynamically from the text file "winkfpt. It is possible to improve on the explanatory power/correctness of the texts at any time without making changes to WinKFPT.1)_v1. into functions with and without COAPI calls. The manner in which errors that arise while executing these functions differs between the two types.doc Version: 1.txt".txt". DAF.WinKFPT User's Guide Page 177 10 ERROR HANDLING IN WINKFPT The process of flash programming an ECU with WinKFPT is very complex and depends on troublefree 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. with the respective information that has been able to be established from the relevant COAPI call levels.8 . This error list should not be viewed as a list of different errors. The COAPI error texts are loaded dynamically from the text file "coapierr. an error dialog is displayed. etc.10.04 File: Handb-winkfpt32(5. • Displaying errors in WinKFPT functions without COAPI calls: Display of informative error. The functions built into WinKFPT can be roughly split into two types: namely.

10. The first line of the error list displays the error message of the "lowest" COAPI call level and generally contains comprehensive and crucial information for debugging purposes.doc Version: 1. the user must check whether the file "kfconfxx. Fig. 10-1: Error display window in WinKFPT In the example above. In this case. you can see that initialization of the COAPI by WinKFPT has failed.8 . This view is intended merely as an additional debugging aid for WinKFPT or COAPI experts.1)_v1.8_eng. or whether or not he has read rights to it.1 Displaying Errors The figure below shows the "Normal view" display of a WinKFPT error associated with a defective COAPI call. The list of errors from the respective COAPI call levels clearly shows the user which of the many initialization errors possible is the actual cause of the error. Date: 20.WinKFPT User's Guide Page 178 10.04 File: Handb-winkfpt32(5.da2" is present in the <root>\DATA\gdaten directory. Switching to the "Extended view" is of no benefit to "normal" users.

.1 Errors When Starting WinKFPT Error COAPI errors 1020.1)_v1.. The error dialog tells you which file it is. Error COAPI errors 4211. If not: check Ediabas and/or the interface driver. (Application may only be able to be seen in the task manager. 3017. Import an up-to-date assembly line data set with correct description files.doc Version: 1. Possible cause • Debugging • The .WinKFPT User's Guide Page 179 10./data/gdaten directory by hand.2 Description and Elimination of Frequently Occurring Errors 10./data/gdaten directory by hand. 4206. • Date: 20. Debugging • • Import an up-to-date assembly line data set with description files./data/gdaten directory contains a faulty and therefore unconvertible logistics file. TEOF in the Ediabas\bin directory) to check whether the interface actually functions. • Error WinKFPT error 300 Time of occurrence • When starting WinKFPT./data/gdaten directory.8 ..8_eng.04 File: Handb-winkfpt32(5. Possible causes • Debugging • • The interface is already being used by a different program or possibly by a different instance of WinKFPT.. 1040.10. Copy the missing logistics file to the . Repair the faulty logistics file in the . Possible cause • A logistics file is missing in the . The error dialog (in particular error 4206) tells you which file it is and in which line the error occurred.2.g. Close the other application that is using the interface. WinKFPT error 1 Time of occurrence • When starting WinKFPT. WinKFPT error 1 Time of occurrence • When starting WinKFPT. The default interface is not correctly set up in Ediabas. 3017.) Use a different application (e.

2 Errors When Importing Assembly Line Data Error ECU directory is not displayed Time of occurrence • When selecting an assembly identification number in Comfort mode. The file already exists in the target directory and has been opened by an application.8 .10. Error WinKFPT error 111 Time of occurrence • When importing an assembly line data set.1)_v1. Debugging • Import an assembly line data set with description files.doc Version: 1. Possible cause • The assembly line data set does not contain a file of type <EcuFamilyname>. The file already exists in the target directory and is write-protected. The description file could not be copied.04 File: Handb-winkfpt32(5. Error WinKFPT error 11 Time of occurrence • Possible causes • • • Debugging When importing a single description file. Date: 20.WinKFPT User's Guide Page 180 10. • The source file has no read rights. • Close the application that has opened the file. • No write rights in the target directory. Depending on the cause: • Cancel write protection.8_eng. from Darwin).2. • Check and adapt the file rights.dat Debugging • Fetch the correct assembly line data set (e. Possible cause • Imported ECU directory does not contain any PABD/P-SGBD description files.g.

WinKFPT
User's Guide
Page 181

10.2.3 Errors When Entering Flash Data
Error

COAPI errors 1065, 1000, WinKFPT error 106

Time of occurrence

Possible cause

When loading the suggested configuration after activating the
<Expert mode> button.
In Comfort mode when activating the [Done] button after selecting
a ZB number and integration position.
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

Possible cause

When loading the suggested configuration after activating the
<Expert mode> button.
In Comfort mode when activating the [Done] button after selecting
a ZB number and integration position.
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 the
ZB number belongs.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 182

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

Debugging


The wrong ECU has been connected. The ECU identifier in the
data/program file selected does not match up with the identifier of
the ECU connected.
The wrong data/program file has been selected.
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.

Error

COAPI error 2020

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.

Error

COAPI error 1020

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.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

WinKFPT
User's Guide
Page 183

Error

COAPI errors 4209 or 4211, 4206, 1040, 3000

Time of occurrence

When activating the [Program] button in Comfort mode.

Possible cause

Debugging


An ECU family-specific logistics file (DAT, HWH or HIS) is faulty.
The error dialog (in particular error 4206) tells you which file it is
and in which line the error occurred.
Fetch an intact file by importing the assembly line data
or eliminate the error in the file by hand.

Error

COAPI errors 4204, 1040

Time of occurrence

When activating the [Program] button in Comfort mode.

Possible cause

The file to be flashed does not exist. The error dialog (in particular
error 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 error
4221) 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.

Date: 20.10.04
File: Handb-winkfpt32(5.1)_v1.8_eng.doc

Version: 1.8

Error WinKFPT error 102 or 103 Time of occurrence • In Expert mode when entering an ECU address.04 File: Handb-winkfpt32(5.1)_v1. Debugging • Enter a correct vehicle identification number. Date: 20.8_eng.8 . Possible cause • The vehicle identification number was either not a 7-digit number or not alphanumeric.doc Version: 1. Debugging • Enter a correct hexadecimal number. when activating the [Done] button.10. Possible cause • The SGBD demands an external ECU address.WinKFPT User's Guide Page 184 Error WinKFPT error 100 Time of occurrence • In Expert mode after selecting PABD and SGBD. Error WinKFPT error 107 Time of occurrence • When entering a vehicle identification number (necessary when UIF write is active). hexadecimal number has not been entered as the ECU address. Possible cause • A 2-digit. Debugging • Enter an ECU address.

doc Version: 1. Debugging • Enter a 7-digit ZB number. Possible cause • The ZB number was not a 7-digit number.1)_v1. Date: 20.8 .04 File: Handb-winkfpt32(5.8_eng.10.WinKFPT User's Guide Page 185 Error WinKFPT error 108 Time of occurrence • When entering a ZB number in Comfort mode.

WinKFPT User's Guide Page 186 10. Determine whether the interface hardware is connected.10. P-SGBD and the program data set in Expert mode. Data> button.4 Errors During Data Programming Error CAPI error 2020 or 2021 Time of occurrence • When starting programming in both operating modes. Re-install the interface. • • • Date: 20. Debugging • • • Determine whether the ECU is connected. Error COAPI error 1060 Time of occurrence • When starting programming by activating the <Prog. Determine whether the ECU is connected. The interface is not connected.04 File: Handb-winkfpt32(5. following input of the PABD. If necessary. Re-install the interface. Possible causes • • • • The wrong hardware interface has been selected.doc Version: 1. The interface is not fully installed.2. The interface is not connected.8_eng. Debugging • Determine whether the correct HW interface is displayed as status information.1)_v1. Possible causes • • • The ECU is not connected. select the correct HW interface under menu option Communication  HW interface. Determine whether the interface hardware is connected.8 .. The HW interface is not fully installed. The ECU is not connected.

enter PABD. Confirm the entries made in Expert mode by activating the <Done> button. Program> button.10.8_eng. Date: 20. Start flash programming of the control unit with the program data set by activating the <Prog. Debugging • The program must be flashed to the ECU again.8 .04 File: Handb-winkfpt32(5. Possible cause • The last programming session was not successfully completed and terminated. P-SGBD and the program data set in Expert mode. ZCS) Time of occurrence • When starting programming by activating the <Prog.1)_v1.doc Version: 1. To this end.g.WinKFPT User's Guide Page 187 Error COAPI error 2064: Delete error in coding data (e. Data> button.

1)_v1. HIS (Assembly) History file IFH Interface handler INPA Interpreter for test sequences Interface Hardware unit for communication with control units.g. MOST IPO Extension of a sequence description file in object format IPS Extension of a sequence description file in source format NAAB PABD Boot update description file.8 . data file and/or program file. DAF Flash data image file Expert mode Programming after selecting the PABD. e. This is a data file that is flashed to the program area of an ECU and contains the program for boot sector update and the boot sector itself. SGBD ECU description file Date: 20. Flash sequence description file PAF Flash program image file P-SGBD Control unit description file for programming. and the vehicle identification number if UIF write is activated.8_eng.WinKFPT User's Guide Page 188 Glossary CABD Coding sequence description file CABI Coding sequence interpreter COAPI Coding application interface Comfort mode Programming after entering or selecting the job data.10.04 File: Handb-winkfpt32(5. ADS. assembly identification number and control unit address.doc Version: 1. P-SGBD. EDIC.

etc. C.10. The ZIF in the control unit indicates the state of development of the control unit program. B.doc Version: 1.8 . if several interfaces of one type are installed in the same computer. ZUSB number ZB number Assembly identification number Date: 20.WinKFPT User's Guide Page 189 UIF User info field Unit Subunits of interfaces designated _. ZIF Supplier info field.04 File: Handb-winkfpt32(5. A.8_eng. WDP An importable directory that contains all the files of an ECU family required to flash control units from this ECU family with the aid of a BMW programming tool.1)_v1.

10.WinKFPT User's Guide Page 190 Contents A Assembly identification updating 125 B Baudrates reading 165 C Calibration values reading 167 COAPI definition 187 Comfort mode definition 187 import files 66 Configuration 39 COAPI. 24. 38. 106 Directory structure 19 E reading 173 ECU internal temperature reading+ 174 ECU status displaying 171 Expert mode definition 187 function phase 1 137 import files 66 F Function choosing a ZUSB number 124 displaying the ECU status 171 ending function phase 0 129. 153 entering a vehicle identification number 127 entering a ZUSB number 121 EWS alignment 169 flash programming in Comfort mode 131. 36. data import 76 Data sets.8 . 97. 58.INI 38. 39 Expert mode 34. 31. 106 WinKFPT 24 WINKFPT. 39 EDIABAS. 136. 185 choosing (selecting) 96 ECU identification Date: 20. 39 D Data sets. program import 76 Diagnosis protocol 95 choosing (selecting) 98 job DIAGNOSEPROTOKOLL_SETZEN 99 Job DIAGNOSEPROTOKOLL_LESEN 98 selecting 103.INI 24. 133.doc Version: 1. 30.8_eng. 37. 104.INI 28. 95. 22. 159 general functions 161 loading a PABD 139 loading a P-SGBD 141 reading the calibration values 167 reading the ECU baudrates 165 reading the ECU identification 173 reading the ECU internal temperature 174 reading the UIF 163 updating an assembly identification 125 VS20/DS2 mode 168 Function phase 1 Expert mode 137 H HW interface 20. 35. 134 Flash programming in Comfort mode 157. 96.04 File: Handb-winkfpt32(5. 34.1)_v1.

WinKFPT User's Guide Page 191 I Import data sets.OUT 19 U UIF definition 188 reading 163 UNINSTALL WinKFPT 18 Unit defining 96 definition 188 V Vehicle identification number entering 127 Z ZUSB number choosing 124 entering 121 Date: 20. program 76 files for Comfort mode 66 files for Expert mode 66 import menu 65 PABD 80 P-SGBD 78 Import menu files 65 Initialization file WINKFPT. 125 Interface definition 187 IPO definition 187 import file 80 IPS definition 187 import file 80 P PABD definition 187 import 80 loading 139 P-SGBD definition 187 import 78 loading 141 T Temporary files INNENTMP. files 76 data sets.04 File: Handb-winkfpt32(5.INI 19 Installation WinKFPT 18 Integration position choosing 124.8 .1)_v1.10.doc Version: 1.8_eng.