Professional Documents
Culture Documents
User's Guide
Page 1
WinKFPT 5.1
User's Guide
Version 1.8
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_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.1 Multiple Instancing Capability .............................................................................................. 12
2.2.2 Operating Modes ................................................................................................................. 13
2.2.3 Programming of ECUs in Dialog Mode ................................................................................ 14
2.2.4 Programming 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.1 Configuration of the basic directory for the working directories of WinKFPT....................... 22
3.4 Configuring WinKFPT .................................................................................................................. 23
3.4.1 Configuration in COAPI.INI .................................................................................................. 23
3.4.2 Configuration in WINKFPT.INI ............................................................................................. 26
3.4.3 Configuration for Expert Mode ............................................................................................. 32
3.4.4 Configuration in EDIABAS.INI.............................................................................................. 37
3.5 Reference Configuration of WinKFPT.......................................................................................... 38
4 STARTING WINKFPT .................................................................................................................. 40
4.1 Calling Parameters of WinKFPT .................................................................................................. 40
4.1.1 Type 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.1 Control File for Batch Mode in Comfort Mode...................................................................... 51
4.4.2 Control File for Batch Mode in Expert Mode ........................................................................ 53
4.4.3 Starting a Programming Job in Batch Mode ........................................................................ 55
4.4.4 Switching HW Interface and Diagnosis Protocol in Batch Mode ......................................... 57
4.4.5 Starting Several Instances in Batch Mode ........................................................................... 58
4.5 Starting WinKFPT in Dialog Mode................................................................................................ 59
4.5.1 Starting Several Instances in Dialog Mode .......................................................................... 59
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 3
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 4
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 5
List of Figures
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 6
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 7
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 8
List of Tables
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 9
1 FOREWORD
Publication and distribution of the User's Guide are the responsibility of BMW.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 10
Chapter Description
5 WinKFPT's Main Menu The following chapters (5-6) describe how to use WinKFPT
in Dialog mode.
7 Function Phases in Comfort Mode Control functions in Comfort mode for flash programming a
control unit.
8 Function Phases in Expert Mode Control functions in Expert mode for flash programming a
control unit.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 11
Example Description
"Import file sets" Names written in italics and set in quotation marks
denote a window or dialog box in the program.
<<ECU not responding>> Words set in double angle brackets denote messages
displayed to the user.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 12
2 INTRODUCTION
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.
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.
WinKFPT is the first tool that uses the COAPI functions for a boot sector update (BSU), and therefore
facilitates ECU updates (exchange of boot sectors, programs, data) that go beyond the boundaries of
ECU families. This reduces the need to exchange control units in e.g. the Service Department.
As of Version 4.6.0, WinKFPT uses the import/export functionality of the COAPI to manage
development and tool-relevant data, 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 13
The table below contains a brief description of each of WinKFPT's operating modes.
Dialog mode = Standard operating mode – all ECU flash programming entries are made by
the user in Dialog mode.
Batch mode Can be started from Dialog mode or by being called with appropriate calling
parameters.
The programming of ECUs is configured and started by means of specific
control files.
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.IPS).
The object code file (XXX.IPO) of the PABD is then located following
translation as a resident file in the PABD directory "<root>\sgdat".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 14
1. Entry or selection of the assembly identification number (ZUSB No.), selection of any number of
integration positions offered for the ZUSB No., entry of the vehicle identification number (VIN)
when a UIF is written, and subsequent flash programming of the control unit or control units in
Comfort mode.
2. Selection of a control unit family and of any number of integration positions offered for this family,
and subsequent updating of the control unit or control units 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, updating of the
assembly identification code goes beyond just changing the hardware, actually potentially involving
changing the ECU family.
3. Selection of the necessary PABDs, P-SGBDs and data set names and subsequent flash
programming of the control unit in Expert mode.
In addition to be able to flash program control units, a number of special and diagnostics functions,
such as "Read UIF" or "ECU Status" are supported.
WinKFPT can be started from an external application in Batch mode; in this case, flash programming
of the control units is initiated by means of a control file.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 15
Application
WinKFPT WinKFPT
(1. Instance) (2. Instance)
BMW-
Logistic files
COAPI COAPI
PABD
EDIABAS-API EDIABAS-API
(1.Instance) (2.Instance)
HW-Interface I HW-Interface II
Diagnosis-Bus Diagnosis-Bus
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 16
3 FIRST STEPS
Requirement Remark
Computer PENTIUM II processor or higher with 64 MB RAM
and 50 MB of free memory
In Version 1.4 and higher, all configuration files required are available in rudimentary form following
installation, so that WinKFPT will run up without any problem.
You can then import the assembly line data (Comfort mode) or PABD and P-SGBD files and data sets
and program data sets (Expert mode) you want online using the import functionality of WinKFPT (see
"5.2 Import/Export Menu"REFMERGEFORMAT).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 17
The installation directory contains two files you will need if you want to uninstall WinKFPT at some
point in the future:
• INSTALL.LOG, the file containing the uninstall information
• UNWISE.EXE, the WinKFPT uninstaller.
Directory Contents
\<root>\BIN This directory contains all necessary program files (EXE, DLL) and the
initialization/configuration file WINKFPT.INI.
It also serves as a working directory for storing error files and other temporary
files created while the program is running (e.g.
INNENTMP_INTERFACE_unit.OUT).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 18
Directory Contents
\<root>\DATA\DEVELOP Directory contains the programming data files available in Expert mode.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 19
Directory Contents
\<root>\DATA\GDATEN Directory contains the logistics files for ECU flash programming. These must
always be available. The files are loaded by importing an assembly line data set:
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 20
Directory Contents
\<root>\DATA\<EcuFam> Each of these directories contains the ASCII programming data for an ECU
family <EcuFam>. These directories are used in Comfort mode.
Note: all the logistics files of an ECU family must be present in each case.
These are:
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 21
Directory Contents
\<root>\DATA\KONV.TMP Temporary directory for storing programming data files while WinKFPT is
running through several instances:
\<root>\DATA\KONV.TMP2,
\<root>\DATA\KONV.TMP3 etc...
\<root\SGDAT Directory contains the header files and PABDs in source code and/or in
compiled code.
The source code of the flash sequence description files (PABDs) is available in
the INPA script language.
Files can be available in source code or in compiled form; the compiled form is
generated from the source code by means of the CABI compiler.
Since the functionality of the CABI compiler is integrated in the COAPI,
WinKFPT can process both forms of a PABD.
\<root>\WORK Working directory for COAPI and WinKFPT for storing trace and other
temporary files.
The working directory can be changed by means of the COAPI.INI file. The
working directory must be created because WinKFPT will otherwise not start.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 22
3.3.1 Configuration of the basic directory for the working directories of WinKFPT
By means of the main menu option "Configuration" (see “5.4 Configuration Menu”) the basic directory
for the working directories can be changed at any time.
This means it is possible for several instances of WinKFPT to work with one central set of working
directories placed anywhere in a network environment.
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.
Otherwise an error message occurs and the actual valid basic directory is not changed.
Note:
It is possible that existing programming settings are not valid any longer after a change of the working
directories.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 23
[Kennfeldprog] This section contains entries that are required specifically for engine
characteristics map programming.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 24
[Setup] In this section, you set which form of the PABD is to be displayed for
selection in WinKFPT.
3 The entry is only evaluated if the switch "EXPERT_MIT_AIF" in the file WINKFPT.INI is set to ON (Expert
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 25
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 26
Possible
Configuration entry Default Description
setting
[Einstellungen] Paths for configuration files, data and trace files are set in this
section.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 27
Possible
Configuration entry Default Description
setting
KOMFORT_MIT_AIF ON ON The entry specifies whether the
OFF UIF is also programmed (ON) or
not (OFF) during flash
programming in Comfort mode.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 28
Possible
Configuration entry Default Description
setting
CabdFormat IPS IPO The entry defines whether
IPO WinKFPT is to use PABDs as
(COM) source files or as compiled files.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 29
Possible
Configuration entry Default Description
setting
Interfaces are to be defined using the following syntax:
[Description] = [HW interface identifier]
Example:
K-Line / EDIC=EDIC
K-Line / ADS-OBD=STD:OBD
CAN / EDIC=EDICC
CAN / Vector=STD:CAN
Most / Optolyzer=STD:MOSTO
Most / PC card=STD:MOSTP
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 30
Possible
Configuration entry Default Description
setting
KF_DIAG_PROT Identifier of the empty Saved setting of the diagnosis
diagnosis protocol in Expert mode; in the
protocol case of a P-SGBD file that
supports several diagnosis
protocols,
the diagnosis protocol can be
selected by means of the menu
option Communication
Diagnosis protocol.
KF_PABD PABD file name empty Saved setting of the PABD file
name in Expert mode.
PABD file can be selected by
pressing the function key Expert
Mode PABD.
KF_DATEN_DATEI Data file empty Saved setting of the data set file
name for data in Expert mode.
Data set file for data can be
selected by pressing the
function key Expert Mode
Data File.
KF_PROGRAMM_DATEI Program file empty Saved setting of the data set file
name for program in Expert mode.
Data set file for program can be
selected by pressing
the function key Expert Mode
Program File.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 31
Possible
Configuration entry Default Description
setting
KF_NAAB_DATEI NAAB file empty Saved setting of the data set file
name for NAAB in Expert mode.
Data set file for NAAB can be
selected by pressing
the function key Expert Mode
NAAB File.
N.B.: The entries in this section must be made by the user only in WinKFPT and not using Editor!
To save start information, WINKFPT.INI can, during the import and export of configurations, contain
entries that are generated automatically by the program and that are not allowed to be changed or
preset by the user.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 32
A configuration is set in Expert mode by means of the free selection of the following job data and
settings:
HW interface and unit is selected by means of the menu option Communication HW Interface in
Expert mode (see "5.3.1 Selecting (Choosing) a HW Interface").
Diagnosis protocol is selected by means of the menu option Communication Diagnosis Protocol
in Expert mode (see "5.3.2 Selecting (Choosing) a Diagnosis Protocol").
P-SGBD is selected by pressing the function key "P-SGBD" in Expert mode (see "8.1.2 Function:
Loading a P-SGBD").
PABD is selected by pressing the function key "PABD" in Expert mode (see "8.1.1 Function: Loading a
PABD").
Control unit address is entered by pressing the function key "ECU Address" in Expert mode (see
"8.2.1 Function: Loading an ECU address").
Data file is selected by pressing the function key "Data File" in Expert mode (see "8.2.4 Function:
Loading a Data Set – Data File").
Program file is selected by pressing the function key "Program File" in Expert mode (see "8.2.3
Function: Loading a Data Set – Program File").
NAAB file is selected by pressing the function key "NAAB File" in Expert mode (see "8.2.2
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 33
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 34
If you have activated Expert mode at least once while using 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.
To this end, the following dialog box appears before WinKFPT is exited:
The configuration is saved in WINKFPT.INI in the [Expert mode configuration] section (see "3.4.2
Configuration in WINKFPT.INI").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 35
If a configuration with at least one entry exists - either following starting of the program from the
configuration file WINKFPT.INI or from a previous entry in Expert mode - this configuration is offered to
the user for loading when the user first enters or re-enters Expert mode.
If the configuration is adopted, the corresponding status displays in the main menu window of
WinKFPT are updated (see "4.2 Status Displays of WinKFPT").
If the configuration is adopted, the scope of the job data in the configuration determines the function
level of Expert mode to which is switched (see "8 Function Phases in Expert Mode").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 36
In contrast to configuration loading, 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.INI.
WinKFPT is exited and the configuration entries in the [Expert mode configuration] section of
WINKFPT.INI are deleted.
The next time WinKFPT is started and Expert mode called, the program does not offer any
configuration settings for loading.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 37
Possible
Configuration entry Default Description
setting
[Configuration] This section contains configuration entries for EDIABAS.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 38
[Einstellungen]
; allgemeine Einstellungen
WindowPosition=0,1,-1,-1,-1,-1,0,0,643,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
; 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
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 39
[Kennfeldprog]
TEMP_DAT_FILE_DEFAULT_NAME = KFLISTE.DAT
; Daten
SERIENNUMMER = 42324
KUNDENNUMMER = 12321
KM = 0
ZBNUMMER = 0000000
SWNUMMER = 0000000
TYPNUMMER = 0000000
AEINDEX = 00
; SG Dateien komprimieren
; 1 -> Dateien werden immer komprimiert (Für Datenupdate über Netz
; während Applikation läuft)
Sektion [Configuration]
;-------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = EDIC
Interface=STD:OBD
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 40
4 STARTING WINKFPT
You can start WinKFPT without calling parameters or with certain combinations of various calling
parameters.
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. kfpt.ctl"
Example:
winkfpt32 –RUN –BATCH=update_ek928
Example:
winkfpt32 –INTERFACE=STD:OBD
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 41
-UNIT= <Interface unit> Defines the unit (_, A, B, C, ....., Z) that is "_"
to be active following starting of
WinKFPT.
It can be altered at a later point in Dialog
mode by means of the main menu option
"HW Interface".
Example:
winkfpt32 –UNIT=A
Example:
winkfpt32 –WITH_MOSTFIREWALL=ON
Example:
winkfpt32 -TESTER_ID=FA
Example:
winkfpt32 –C 16ek928
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 42
• no par. If neither –C nor –RUN is specified as the calling parameter WinKFPT starts in Dialog
mode, which is the standard operating mode for users employed in control unit
development.
• -BATCH
• -INTERFACE
• -UNIT
• -WITH_MOSTFIREWALL
• -TESTER_ID
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 43
ECU address The control unit address is only explicitly displayed if the standard description files are
used for programming the control unit in question.
No ECU address can be displayed for control units with "older" description files. The
following text appears instead:
PABD uses an internal address
Integration position There are control units for multiple integration that belong to the same ECU family but
that have different addresses, e.g. control units for seat occupancy detection.
To improve user friendliness, the software enables you to select a control unit not by
means of the ECU address, rather by means of meaningful texts that describe the
integration position of the control unit (e.g. Passenger seat, rear left).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 44
Vehicle identification In the Comfort mode of Dialog mode, the vehicle identification number is displayed
number only if an entry is made in the UIF (user info field) following flash programming.
ZB number The ZB number (assembly identification number) defines the program data set and
data data set to be programmed for a control unit.
The ZB number is displayed:
in Expert mode (Dialog mode) if an entry would be made in a UIF (user info field)
following flash programming. The assembly identification number from the
configuration file COAPI.INI is displayed.
following selection of an integration position in Comfort mode (Dialog mode).
during flash programming of an ECU in Batch mode.
HW number The hardware number defines the programmed program data set of a control unit.
The hardware number is displayed:
during flash programming of an ECU in Expert mode (Dialog mode).
during flash programming of an ECU in Comfort mode (Dialog mode).
during flash programming of an ECU in Batch mode.
Interface unit The default interface unit or the one selected is always displayed.
Diagnosis protocol The default diagnosis protocol or the one selected is always displayed if the ECU
facilitates communication with at least 2 diagnosis protocols.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 45
Progress bar Informs you in percentage terms of the progress of an automatic process that takes
some time to be executed (0 % - 100 % in 1 % increments).
The progress bar is displayed during:
flash programming (program and data).
import/export of assembly line data sets, data files or description files.
Boot sector update Is displayed at all times and informs you of whether the boot sector update is
ACTIVATED or NOT ACTIVATED.
The setting can be changed at any time by means of the main menu option
"Configuration".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 46
winkfpt32 –C <filename>
The file name of the PABD (= IPS file) must be entered without the path and file extension, otherwise
WinKFPT is aborted and an error message is displayed that must be acknowledged.
CabdFormat=COM does not have to be set manually in WinKfpt.ini and coapi.ini for compilation. This
is done automatically and temporary by WinKFPT.
The PABD to be compiled, e.g. 10GD8600.IPS, must be present in the "<root>\sgdat" directory.
The following dialog window appears once WinKFPT has been started:
If you click "OK", the PABD in question is compiled and the result of this compilation displayed in a
message box.
In the event of an error, an error report is created in the form of the file CABI.ERR saved in the
<root>\bin directory. This report contains the errors that have occurred during compilation.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 47
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 48
Batch mode is used to flash program any number of control units one after the other.
1. Automatic activation through calling from, for example, an external application using the calling
parameter –RUN (see "4.1 Calling Parameters of WinKFPT"). In this case, Batch mode is
already started.
2. Manual activation from within Dialog mode (see "5.1.9 Display Batch Mode"). In this case,
Batch mode is not yet started.
Once Batch mode has been activated, another dialog window (WinKFPT Batch mode monitor) 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. 4-4: Dialog window for Batch mode (Batch mode monitor)
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 49
The following table describes the status displays in the Batch mode monitor:
Control file Path and name of the default control file or of the control file transferred as calling
parameter (-BATCH=<controlfile>).
Status The status display informs the user about the current activity or about error conditions
in Batch mode.
Errors Indicates the number of errors that occur during control unit communication or during
the evaluation of logistics data.
Aborts Indicates the number of errors that occur during the flash programming of ECUs; an
error leads to immediate aborting of programming.
Target interface Indicates the HW interface+unit that the corresponding WinKFPT instance accesses
during flash programming of an ECU.
Mode Indicates whether a control file for Comfort mode or for Expert mode is being
processed.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 50
If Batch mode is started, WinKFPT waits for the Control file indicated. As soon as this file exists, it is
opened, evaluated and processed. Depending on the contents of the control file, it is decided whether
the process is a Batch process in Comfort mode or in Expert mode.
The path and name of the control file can be specified when calling using the calling parameter –
BATCH=<controlfile>; if specified, the path must be cited in its entirety, including the drive details.
If part of the path is missing, the control file is expected in the installation directory of WinKFPT,
<root\bin>.
There is no need to enter an extension for the control file. It is automatically assumed to be .CTL.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 51
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), [ZBNUMMER] (ZBNUMBER), [SGADRESSE] (ECUADDRESS) and [BATCH].
Other sections are ignored.
The table below contains a full description of the sections of a control file and of the contents of these
sections.
Section Contents
[FGNUMMER] The [FGNUMMER] (VIN) section has just one line that contains the vehicle
identification number.
Format: VIN=<VIN>
Example: VIN=WBAAA00000AA00000
[ZBNUMMER] The [ZBNUMMER] (ZBNUMBER) section contains the various assembly identification
numbers, each on a separate line.
Format: ZBNxxxx=<ZBnumber>, where xxxx is a consecutive number that begins at
0000, and there must be no gap.
Example: ZBN0000=7539765
ZBN0001=7539767
The control units are programmed according to the sequence of the numbers.
Programming is ended when the first number that no longer has a successor number
is reached.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 52
Section Contents
[SGADRESSE] The [SGADRESSE] (ECUADDRESS) section contains the various ECU addresses,
each on a separate line.
Format: SGADRxxxx=<ECUaddress>, where xxxx is a consecutive number that
begins at 0000, and there must be no gap.
The ECU address is entered as a HEXADECIMAL.
Example: SGADR0000=12
SGADR0001=13
There must be an ECU address with an identical consecutive number for each
assembly identification number entered.
E.g.:
[ZBNUMMER]
ZBN0000=7515985
[SGADRESSE]
SGADR0000=A2
[BATCH] The [BATCH] section contains one line with information relating to the ending of
Batch mode.
Format: END=ON or END=OFF.
If the section is left blank (i.e. no entry) or is missing, this is interpreted as END=OFF.
Table 4-4: Contents of a control file for the Batch mode in Comfort mode
Once the control file has been processed, it is deleted and WinKFPT waits for a new control file.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 53
The syntax of the control file is in line with the file format as familiar from Windows INI files. The file
has just the one section: [MULTIFLASH]
Other sections are ignored.
The table below contains a full description of the parameters in the [MULTIFLASH] section of a control
file:
Parameter Contents
MF_DATEN_DATEI This parameter defines the data file to be programmed. At least one NAAB file,
one data file or one program file must be entered.
Format: MF_DATEN_DATEI =<Data file name>
Example: MF_DATEN_DATEI=Q7525491.0DA
MF_PROGRAMM_DATEI This parameter defines the program file to be programmed. At least one NAAB
file, one data file or one program file must be entered.
Format: MF_PROGRAMM_DATEI =<Program file name>
Example: MF_PROGRAMM_DATEI=7523523A.0PA
MF_NAAB_DATEI This parameter defines the NAAB file to be programmed. At least one NAAB
file, one data file or one program file must be entered.
Format: MF_PROGRAMM_DATEI =<NAAB file name>
Example: MF_NAAB_DATEI=555111_555222.0ba
MF_DIAGNOSEPROTOKOLL This parameter specifies the diagnosis protocol to be used. This is optional.
Format: MF_DIAGNOSEPROTOKOLL=<Diagnosis protocol>
Example: MF_DIAGNOSEPROTOKOLL=KWP2000*
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 54
MF_FG_NUMMER This parameter specifies the vehicle identification number. It is only required if
UIF writing is used for programming.
Format: MF_FG_NUMMER=<VIN>
Example: MF_FG_NUMMER WBAAA00000AA00000
Table 4-5: Contents of a control file for the Batch mode in Expert mode
Once the control file has been processed, it is deleted and WinKFPT terminates itself automatically.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 55
The existence of the control file in the relevant directory is the signal for a programming job.
The existence of the control file is determined by WinKFPT in Batch mode by means of polling.
The control file should first of all be written under a different name or in a different directory and then
be made visible for Batch mode by being renamed or copied over. This is to prevent uncompleted files
from being read in.
The control file is no longer read until processing has been completed.
While WinKFPT is in Batch mode, the EDIABAS-API is released and remains bound to the program
only during the period the job is being processed.
For each individual flash programming of an ECU, i.e. for each processing of a VIN from the control
file, the same status displays are displayed in the main menu window of WinKFPT as are displayed
when programming in Dialog mode.
Process logging:
While the programming job is being processed, a log is generated that has the same path and name
as the control file but the extension .PRT.
The following texts are generated to indicate the result of an individual programming routine:
"ERG=Programming OK" for correct programming
"ERG=Programming nOK. Abort" for error during programming
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 56
Messages displayed in Dialog mode of WinKFPT in popup dialog boxes are written to the log file in the
format INFOxxx=<Text>, where xxx is a consecutive number.
The end of the processing of a job is indicated by deletion of the control file. In Comfort mode,
WinKFPT then waits for a new batch file. In Expert mode, WinKFPT terminates itself once the batch
file has been fully processed.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 57
If the file "PRGIFSEL.DAT" does not exist or if the control unit to be programmed is not entered in this
file, the last HW interface that was active prior to starting Batch mode and the default diagnosis
protocol for this control unit are set.
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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 58
In automatic Batch mode, several instances of WinKFPT can be run and process control files
simultaneously.
Note that two instances of WinKFPT are not able to use the same control file.
Apart from that, each instance must communicate over a different piece of hardware (hardware
interface + unit) while its control file is being processed.
If two instances want to access the same control file, the following error message is displayed:
Fig. 4-5: Error message when two instances access the same control file
To prevent two Batch mode instances from wanting to access the same control unit, the calling
parameter –BATCH=<Control file> must be used.
This applies not only to automatic activation (starting WinKFPT with -RUN parameter), but also to
manual activation of Batch mode (starting WinKFPT without -RUN parameter).
Whatever the case, two WinKFPT instances are never able to communicate with a control unit via the
same HW interface+unit.
To define the interface and the unit for a WinKFPT instance at the time of starting, you can use the
command line parameters -INTERFACE=<HW interface> and -UNIT=<Unit identifier>.
Batch mode has a special feature by which two WinKFPT instances can be started that display the
same target interface in the Batch mode monitor, i.e. they have been started with the same HW
interface+unit details.
A HW interface conflict only arises when the two instances process their control file simultaneously and
want to access the same HW interface.
Only that instance that begins processing first is able to access the HW interface properly; the HW
interface is blocked for the second instance from this point to the time processing of the first instance
has been completed.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 59
Calling WinKFPT without calling parameters always starts a WinKFPT instance in Dialog mode.
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, it is not possible for two
instances to be started that want to access the same HW interface+unit.
In such a case, the second instance starts with the error message:
or
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 60
Once you have acknowledged the error message by clicking "OK", the second instance is
automatically closed again.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 61
The top menu bar offers the user the following main menu options:
• <Display>
• <Import/Export>
• <Communication>
• <Configuration>
• <Help>
• <End>
When you select a main menu option, a pull-down menu containing one or more submenu options
appears via which you can call the various menu options.
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.ERR>
• <ERROR.LOG>
• <PABD Parameters>
• <HW History>
• <ZB History>
• <ZB Rule>
• <API Trace File>
• <IFH Trace File>
• <Batch Mode>
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 62
Displays the CABI.ERR file that contains the error messages created when an error occurs during
translation of a PABD (= IPS file).
Close the display by clicking OK or by pressing "ESC" or Alt+F4.
Displays the ERROR_INTERFACE_UNIT.LOG error file that contains the error messages from the
COAPI and CDH functions.
Close the display by clicking OK or by pressing "ESC" or Alt+F4.
Displays the job and result parameters currently set for a PABD.
Close the display by clicking OK or by pressing "ESC" or Alt+F4.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 63
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 64
The Import menu can be used to select all the files necessary for flash programming. They can be
selected from any drive or directory. The files selected are then automatically distributed to the
appropriate directories once their adoption has been confirmed.
Import Files
*.0DA Data set files for data
*.DAF Data exchange files
*.0PA Data set files for program
Data sets / Program releases /
*.PAF Program exchange files
NAAB files
*.0BA Data set files for NAAB
*.BAF NAAB exchange files
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 65
The importing of exported configuration development data‚ data sets, program data sets, /BSU NAAB
files, P-SGBDs and PABDs is assigned to "Expert mode".
The import of exported configuration assembly line data and assembly line data is assigned to
"Comfort mode".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 66
The following dialog window is then displayed to enable you to select the import directory:
Fig. 5-3: Selecting the import directory of a configuration of assembly line data
The start directory highlighted in the import dialog window for the first import in a WinKFPT session is
"My Computer". For each subsequent import, the import directory highlighted is the one that was
selected the last time.
A configuration of exported assembly line data can only be imported from directories that contain the
export log file BACKUPEXPORT.LOG. The contents of the log file are not checked.
If the directory selected does not contain this log file, an error message is displayed and the dialog
terminated.
It is only possible to import an entire exported configuration, i.e. you are not able to select parts from
the exported WDPs for import.
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>\Data" directory.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 67
A dialog window appears that contains a list of the WDPs already in this directory and the function
buttons "Replace", "Merge" and "Cancel".
Fig. 5-4: WDP conflict when importing a configuration of assembly line data
If the list of WDPs is empty, the list window and its corresponding headline is not shown. The "Merge"
button is not shown too because has not function and the "Replace" button is changed by the
"Import" button
Furthermore, 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).
Tool-relevant files from the import directory always overwrite those files in the working directory that
have the same name.
KMM files are exported for archiving purposes only and are therefore never reimported.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 68
all the files from the import directory selected are copied to the working directory; 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:
Special treatment, which is only valid for the import mode Merge, is given to the following ECU-
specific file:
<ECUFAMILY>.DAT:
All lines from the file in the import directory that do not yet exist in the file in the working directory 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 ";".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 69
The following dialog window is then displayed to enable you to select the import directory:
The start directory highlighted in the import dialog window for the first import in a WinKFPT session is
"My Computer". For each subsequent import, the import directory highlighted is the one that was
selected the last time.
A configuration of exported development data can only be imported from directories that contain the
export log file CONFIGEXPORT.LOG. The contents of the log file are not checked.
If the directory selected does not contain this log file, an error message is displayed and the dialog
terminated.
It is only possible to import an entire exported configuration, i.e. you are not able to select parts from
the exported WDPs for import.
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>\Data" directory.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 70
A dialog window appears that contains a list of the WDPs already in this directory and the function
buttons "Replace", "Merge" and "Cancel".
If the list of WDPs is empty, the list window and its corresponding headline is not shown. The "Merge"
button is not shown too because has not function and the "Replace" button is changed by the
"Import" button
A separate selection element enables you to active or deactivate importing of the development files,
i.e. files from the
<basedirectory>\<configurationname>\Daten\Entwicklung\Data\Develop
<basedirectory>\<configurationname>\Daten\Entwicklung\Sgdat
<basedirectory>\<configurationname>\Daten\Entwicklung\Ecu
directories (default is "Import - Development files" activated).
Note:
The files from the export directory
<basedirectory>\<configurationname>\Daten\Entwicklung\Data\Gdaten
are not reimported.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 71
Furthermore, 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).
Development files and tool-relevant files from the import directory always overwrite those files in the
working directory that have the same name.
The following COMMON files are given 'special treatment' that is identical for the two import modes
Replace and Merge:
Special treatment, which is only valid for the import mode Merge, is given to the following ECU-
specific file:
<ECUFAMILY>.DAT:
All lines from the file in the import directory that do not yet exist in the file in the working directory 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 ";".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 72
The following dialog window is then displayed to enable you to select the import directory:
Fig. 5-7: 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". For each subsequent import, the import directory highlighted is the one that was
selected the last time.
The directory selected contains either an actual assembly line data set or one or more subdirectories
that contain assembly line data sets.
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 in the example above you were to select "G:\Trans\EK9282" as the import directory, only the data set
"EK928" would be imported; if you selected "G:\Trans", data sets "EK9282", "EK9294B" etc. would be
imported.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 73
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-8: WDP conflict when importing assembly line data sets
• Cancel:
the dialog window is closed and no files are imported.
• Replace:
all the files from the import directory selected are copied to the working directory; files 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:
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 74
Special treatment, which is only valid for the import mode Merge, is given to the following ECU-
specific file:
<ECUFAMILY>.DAT:
All lines from the file in the import directory that do not yet exist in the file in the working directory 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:
Table 5-2: Distribution of the files to directories when assembly line data is imported
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 75
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.
*.BAF, *.0BA, *.PAF, *.0PA, *.DAF and *.0DA files are displayed by default.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 76
Files that already exist can only be overwritten once a warning prompt has been acknowledged in the
positive.
Fig. 5-10: Overwriting files during NAAB, data and program file importing
If you have selected more than one file, the status of the copying procedure is indicated by a progress
bar (0 - 100 %).
After being imported, files are displayed in the selection list of the "Loading a data set - NAAB file",
"Loading a data set - program file" or "Loading a data set - data file" function in Expert mode (see
"8.2.2
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 77
Function: Loading a Data Set – NAAB File", "8.2.3 Function: Loading a Data Set – Program File" or
"8.2.4 Function: Loading a Data Set – Data File").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 78
By importing P-SGBDs, 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.
The files you have selected are copied to the P-SGBD directory "<ediabas>\ecu"4.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 79
Files that already exist can only be overwritten once a warning prompt has been acknowledged in the
positive.
If you have selected more than one file, the status of the copying procedure is indicated by a progress
bar (0 - 100 %).
After being imported, files are displayed in the selection list of the "Load P-SGBD" function in Expert
mode (see "8.1.2 Function: Loading a P-SGBD").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 80
By importing PABDs, 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 81
Files that already exist can only be overwritten once a warning prompt has been acknowledged in the
positive.
If you have selected more than one file, the status of the copying procedure is indicated by a progress
bar (0 - 100 %).
After being imported, files are displayed in the selection list of the "Load PABD" function in Expert
mode (see "8.1.1 Function: Loading a PABD").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 82
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 83
When you select this menu option, the following dialog window appears:
Fig. 5-16: Dialog window for exporting a configuration of assembly line data
This dialog window displays the export base directory currently set, e.g. <root>\NFS-Backup", and two
input fields ("Type series" and "I-Level") for the names of the two subdirectories.
A list box displays all the valid assembly line data sets (ECU families) available for selection for export.
You can select either no data set at all, one, several or all of the assembly line data sets.
If no valid assembly line data exists, the list box is empty and all you can do is export the tool-relevant
data by activating the corresponding check box.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 84
With each export, the KMM data from the working directory "<root>\KMM\" is exported implicitly,
provided a KMM directory exists.
Before the actual copying process begins, the data to be exported is compared with the corresponding
data last exported and located in the highest-order index directory.
Excluded from comparison are the COMMON files because those to be exported cannot as a rule be
identical with those previously exported.
This basically results in the following two sequences for the export of assembly line data:
1. No new directories are created, i.e. the index directory is not increased. This is the case if the files to be exported, either all
or just some of them, are not yet present in the highest-order index directory, and if all or some of the files present are
identical with those to be exported.
All files are deleted from their respective export directory before copying begins.
2. New directories are created, i.e. the index directory is increased automatically. This is the case if one and just one file to be
exported is not identical with the corresponding file in the highest-order index directory.
Every export of assembly line data is documented in the export log file "BACKUPEXPORT.LOG" in the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\ directory.
The following pieces of information are entered in a log file for each export procedure:
• Date (format: dd.mm.yyyy)
• Export base directory
• Type series
• I-Level
• Index
• With/Without development files
• With/Without tool-relevant data
• ECU family
:
:
• Separating line
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 85
<root>\NFS-Backup\ configurable
daten\
NFS\
KMM\
<Log-File>
Fig. 5-17: Structure of the target directories for exporting assembly line data
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 86
PABD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from <root>\Sgdat to the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
FABD: The name of the description file that belongs to the WDP is determined from the
SWTCONFx.DAT file and copied from <root>\Sgdat to the <root>\<NFS-
Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
P-SGBD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from EDIABAS\ECU to the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
SWT-SGBD: The name of the description file that belongs to the WDP is determined from
the SWTCONFx.DAT file and copied from EDIABAS\ECU to the <root>\<NFS-
Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
Copying of all the files with the extensions *.INI and *.DAT from the <root>\cfgdat directory
to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\cfgdat\ directory.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 87
Copying of all the files with the extension *.INI from the <root>\EDIABAS\bin\ directory to
the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\EDIABAS\bin\ directory.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 88
When you select this menu option, the following dialog window appears:
This dialog window displays the export base directory currently set, e.g. "<root>\Diagprog", and one
input field ("Configuration name") for the name of the subdirectory.
A list box displays all the valid assembly line data sets (ECU families) available for selection for export.
You can select either no data set at all, one, several or all of the assembly line data sets.
If no valid assembly line data exists, the list box is empty and all you can do is export the development
files and/or tool-relevant data by activating the corresponding check box(es).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 89
Fig. 5-19: Prompt asking whether development data should be overwritten during export
If you click "Yes", all the files in the existing directories are deleted first before exporting is conducted.
Every export of development data is documented in the export log file "CONFIGEXPORT.LOG" in the
<root>\Diagprog\<configurationname>\ directory.
In the event of repeated export to the same directory (<root>\Diagprog \<configurationname>\), the
relevant information to be stored is in each case appended to the log file that already exists.
The following pieces of information are entered in a log file for each export procedure:
• Date (format: dd.mm.yyyy)
• Export base directory
• Configuration name
• With/Without development files
• With/Without tool-relevant data
• ECU family
:
:
• Separating line
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 90
C:\Diagprog\Konfiguration\ configureable
daten\
Entwicklung\
sgdat\ al PABD
NFS\
<Log-Filei>
Fig. 5-20: Structure of the target directories for exporting development data
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 91
P-SGBDs: All *.PRG files are copied from the EDIABAS\ECU directory
to the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Ecu directory.
PABDs: All *.IPS and *.IPO files are copied from the NFS\Sgdat directory to the
<root>\Diagprog\<configurationname>\Daten\Entwicklung\Sgdat directory.
PABD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and STWCONFx.DAT file and copied from NFS\Sgdat to the
<root>\Diagprog\<configurationname>\Daten\<ecufam> directory.
P-SGBD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from EDIABAS\ECU to the
<root>\Diagprog\<configurationname>\Daten\<ecufam> directory.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 92
Copying of all the files with the extensions *.INI and *.DAT from the <root>\cfgdat directory
to the <root>\Diagprog\<configurationname>\NFS\cfgdat\ directory.
Copying of all the files with the extension *.INI from the <root>\EDIABAS\bin\ directory to
the <root>\Diagprog\<configurationname>\EDIABAS\bin\ directory.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 93
Fig. 5-21: Deleting assembly line data; message if no assembly line data is present
In this case, it is also not possible to conduct flash programming of ECUs in Comfort mode. You would
first have to import assembly line data to enable flash programming.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 94
If valid assembly line data does exist, the following dialog window is opened:
A list box displays all the valid assembly line data sets (ECU families) available for selection for
deletion. You can select either no data set at all, one, several or all of the assembly line data sets.
The directories of the assembly line data selected are completely deleted during the deletion
procedure.
The associated description files (SGBD/PABD) are likewise deleted, but only if they occur no more
than once in "kfconfxx.da2" and “swtconfx.dat”, i.e. only if they are not used by one or more other ECU
families at the same time.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 95
By clicking the function button "Remove", you delete the selected WDPs from the list box and remove
the corresponding entries from the COMMON files "kfconfxx.da2" and "hwnr.da2".
Fig. 5-23: Deleting assembly line data; prompt displayed on clicking "Remove"
If you click the function button "Remove all", all WDPs are selected and deleted, and the COMMON
files "kfconfxx.da2", “swtconfx.dat” and "hwnr.da2" are completely emptied with the exception of their
headers, i.e. including all "dead" entries for which no WDPs exist.
Fig. 5-24: Deleting assembly line data; prompt displayed on clicking "Remove all"
If you click "Yes", deletion is started and the dialog window is closed once deletion has been
completed.
If you click "No", the prompt disappears from the screen and the dialog window remains open.
If you click the function button "Cancel", the dialog window is closed; active deletion procedures are
not interrupted.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 96
• Hardware interface
• Diagnosis protocol
The menu option "HW interface" enables you to switch dynamically between HW interfaces (EDIC,
ADS, etc.).
The "HW interface" menu option is only active if HW interfaces are entered in the configuration file
WINKFPT.INI (see "3.4.2 Configuration in WINKFPT.INI").
The menu option "Diagnosis protocol" enables you to choose dynamically between the diagnosis
protocols that are supported by a selected control unit (BMW-Fast, KWP2000, etc.).
The "Diagnosis protocol" menu option is only active if a selected control unit supports more than one
diagnosis protocol.
A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABD
and P-SGBD (Expert mode).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 97
The "HW interface" menu option is only active if HW interfaces are entered in the configuration file
WINKFPT.INI.
All HW interface entries from WINKFPT.INI (see "3.4.2 Configuration in WINKFPT.INI") are presented
in a list for selection.
To choose a HW interface:
• Choose a HW interface from the "HW interface" list.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 98
If WinKFPT is able to activate the HW interface chosen, the interface is displayed constantly in the
"HW interface" box as status information. Otherwise, error message 304 (which you have to
acknowledge) appears and the previous setting remains active.
Fig. 5-26: Error message displayed when an impermissible choice of HW interface is made
The same error occurs if, for example, the HW interface chosen is not installed as hardware or
software.
If a different instance of WinKFPT has already accessed the same HW interface+unit, the following
error message appears:
Fig. 5-27: Error message when the same HW interface+unit is accessed in Dialog mode
When WinKFPT is started, the HW interface defined in "EDIABAS.INI" is activated and displayed by
default (see "3.4.4 Configuration in EDIABAS.INI").
You can, however, 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>.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 99
The "Diagnosis protocol" menu option is only active if a selected control unit supports more than one
diagnosis protocol.
A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABD
and P-SGBD (Expert mode).
Once you have chosen a control unit, WinKFPT automatically tries to call the job
"DIAGNOSEPROTOKOLL_LESEN" from the corresponding P-SGBD.
If the job is present, the diagnosis protocols specified in it are displayed in a list for selection.
If you do not make an explicit selection, the first diagnosis protocol from the list is activated by default.
The diagnosis protocol activated is displayed in the "Diagnosis protocol" box a status information.
A selected diagnosis protocol is set internally by means of the P-SGBD job
"DIAGNOSEPROTOKOLL_SETZEN".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 100
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 101
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 102
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.
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: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 103
Base directory for working ExpertKonfPath Base directory for the working
directories of WinKFPT directories: cfgdat, data, sgdat
etc.
If you close the dialog window by clicking "OK" and the settings in the window differ from those in the
Ini file, you are asked whether you would like to save your changes permanently to the Ini file. Even if
you reject this option now, the settings you have entered remain valid for the duration of the WinKFPT
session, and you are given another chance to save this configuration to the Ini file when you end the
session.
If you change the PABD format and a PABD has already been selected, 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). Message boxes prompt you to do this.
This command displays the opening screen of the online help function.
The User's Guide and the online help are identical.
Whenever updates of WinKFPT are released, the Word file of the User's Guide and the online help will
both be updated.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 104
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 105
The top part of this window shows the version of WinKFPT and the versions of the COAPI and Krapi
libraries.
Displayed in the bottom right-hand corner are the creation date and time of the WinKFPT version.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 106
5.6.1 Exit
You exit WinKFPT by selecting the menu option End Exit.
As WinKFPT is terminated, the last window size and window position of the application are saved as
the entry WindowPosition in the WINKFPT.INI file.
The next time WinKFPT is launched, the program is started with the same window size and position
(see "3.4.2 Configuration in WINKFPT.INI").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 107
6 FUNCTIONS OF WINKFPT
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 108
MAIN MENU
COMFORT-MODE EXPERT-MODE
YES
ZUSB
Prog. settings phase, Level 2
NO entered/selected?
and VIN enter ECU-Address
entered? load Dataset - Program
load Dataset - Data
YES
FINISHED
Prog. execution phase
Do program
Do program update
Comfort mode Prog. execution phase
Expert mode
Dataset Data YES
prog. data
selected?
Dataset
YES prog.
Program
program
selected?
Expert mode
Comfort mode
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 109
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 110
The function start menu offers you two WinKFPT operating modes to choose from:
• Comfort mode
• Expert mode.
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").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 111
The following table contains the job data possible in the two operating modes:
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.
In the older description files - these are as a rule the non-standardized description files - the ECU
address is hard-coded for filling the protocol parameters and diagnosis telegrams.
The new standard description files must be fed an ECU address from outside, in this case by means of
a user input. This address is then saved globally for further processing in the description files.
Whether or not the ECU address has to be entered is determined automatically by WinKFPT and
displayed to you on the screen.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 112
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.2.1 Import Submenu").
Entry or selection of the assembly identification number (ZUSB number), selection of any number of
integration positions offered for the ZUSB number, entry of the vehicle identification number (VIN)
when a UIF is written, and subsequent flash programming of the control unit or control units.
Selection of a control unit family and of any number of integration positions offered for this family,
and subsequent updating of the control unit or control units to the latest assembly identification,
whereby updating to an incompatible hardware release by means of a BSU is also taken into
account.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 113
The "Comfort mode" function button is available in the following function phases:
in the function start menu
(see "Fig. 6-2: Function start menu of WinKFPT").
Only PABDs in IPO format are used in Comfort mode. If the IPS format is set in the configuration when
Comfort mode is entered, the following message box appears:
If you click "OK", the PABD format is automatically set to IPO; if you click "Cancel", you do not enter
Comfort mode.
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.
When you activate "Comfort mode", 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
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 114
• Hardware number
are retained.
When you activate "Comfort mode", 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 115
You switch to Expert mode by activating the function button "Expert mode".
When you activate "Expert mode", the following job data and status displays of Comfort mode are
deleted:
• Vehicle identification number
• Assembly identification number
• Hardware number
To completely delete job data in Comfort mode, the following function buttons must be activated one
after the other:
"Expert mode"
"Cancel" (if loading from configuration is offered)
"Done" (<F8> in Expert mode)
"Comfort mode"
"Done" (<F8> in Comfort mode).
Afterwards, WinKFPT displays the function start menu (see: Fig. 6-2: Function start menu of
WinKFPT).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 116
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.1 Import Submenu").
In Expert mode, you do have the possibility of bypassing logistical restrictions by e.g.:
• programming a program data set that is incompatible with the current program data set in the control
unit
• "resetting" a control unit by programming "old" program data sets
• programming data sets that do not suit the current program data set in the control unit.
Caution!
If you embark on actions of this kind, you must know precisely what you are doing because any error
could lead to a control unit being rendered totally unusable for the future. Such a control unit would no
longer be able to be flashed via diagnosis communication and would have to be submitted for
recycling.
When you select Expert mode, the graphical user interface (GUI) immediately displays the assembly
identification number (ZB number) from the configuration file "COAPI.INI" for checking purposes if
EXPERT_MIT_AIF=ON is set in the configuration file "WINKFPT.INI".
If a different ZB number is to be entered in the UIF, you must carry out the following steps:
• Exit WinKFPT.
• Change the entry in "COAPI.INI" (see "3.4.1 Configuration in COAPI.INI").
• Restart WinKFPT.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 117
The "Expert mode" function button is available in the following function phases:
in the function start menu
(see "Fig. 6-2: Function start menu of WinKFPT").
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.
When you activate "Expert mode", all job data and status displays from the preceding session in
Expert mode are retained:
When you activate "Expert mode", the following job data and status displays from the
preceding session in Comfort mode are deleted:
• Vehicle identification number
• Assembly identification number
• Hardware number
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 118
You switch to Comfort mode by activating the function button "Comfort mode".
When you activate" Comfort mode", all job data and status displays of Expert mode are either
completely deleted or are buffered for loading the last configuration for a renewed entry into Expert
mode.
After you click "Done" (or press <F8> in Comfort mode), WinKFPT displays the function start menu
(see: Fig. 6-2: Function start menu of WinKFPT).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 119
The functions of the programming settings phase are used for entering or selecting all the job data
required for flash programming.
The functions of the programming execution phase are used for flash programming one or more
control units.
Whether or not you can switching function phase depends on the scope of the job data you have
entered.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 120
The following functions are available in the programming settings phase of Comfort mode:
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 121
When you activate this function, a dialog box opens in which you enter the assembly identification
number (ZUSB number).
Fig. 7-2: 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 122
• If you click "OK", WinKFPT checks whether the ZUSB number you have entered is present in an
<EcuFam>.DAT file of the existing assembly line data sets in the \<root>\DATA8 directory.
If the assembly identification number you have entered is not found or is invalid, input of the ZUSB
number is aborted and the following error message displayed:
Fig. 7-3: Error message - ZUSB number not present in the logistics
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 123
If the assembly identification number entered is valid, a dialog window appears enabling you to choose
one or more integration positions:
Fig. 7-4: Dialog window for choosing an ECU family, 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. All you have to do is select one or more ECU addresses by means
of their integration position(s) (see also "7.1.2 Function: Selecting a ZUSB number").
Select one, several or all of the integration positions from the "Integration position" list in line with the
standard Windows conventions.
• If you click "Cancel", the ZB number entered and integration position selected are discarded.
• If you click "OK", the ZB number is adopted and displayed together with the corresponding hardware
number as status information.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 124
When you activate this function, a dialog box opens in which you select an ECU family, assembly
identification number and integration position(s) (see "Fig. 7-4: Dialog window for choosing an ECU
family, assembly identification number and integration position").
• "ZB Number"
- which contains the assembly identification numbers that belong to the ECU family selected
• "Integration position"
- which contains the integration positions that belong to the ECU family selected, through whose
selection the ECU address is specified. Control units that can be installed more than once in the
same car are distinguished between only by means of their ECU address or integration position.
The "ECU family" list contains only those ECU families for which the logistics file <ecufam>.DAT,
containing at least one ZB number, is present in the respective directories \<root>\data\<ecufam>9.
The "ZB Number" list contains all the assembly identification numbers present in the <ecufam>.DAT
file that belong to the ECU family selected.
The "Integration position" list contains all the integration positions present in the
\<root>\data\gdaten\INFO.ENG file that belong to the ECU family selected.
Select one, several or all of the integration positions from the "Integration position" list in line with the
standard Windows conventions.
• If you click "Cancel", the ZB number and integration position selected are discarded.
• If you click "OK", the ZB number is adopted and displayed together with the corresponding hardware
number as status information.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 125
When you activate this function, a dialog box opens in which you select an ECU family and integration
position(s).
• "Integration position"
- which contains the integration positions that belong to the ECU family selected, through whose
selection the ECU address is specified. Control units that can be installed more than once in the
same car are distinguished between only by means of their ECU address or integration position.
The "ECU family" list contains only those ECU families for which the logistics file <ecufam>.DAT,
containing at least one ZB number, is present in the respective directories \<root>\data\<ecufam>9.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 126
The "Integration position" list contains all the integration positions present in the
\<root>\data\gdaten\INFO.GER file that belong to the ECU family selected.
Select one, several or all of the integration positions from the "Integration position" list in line with the
standard Windows conventions.
• If you click "Cancel", the ECU family and integration position selected are discarded.
• If you click "OK", the selection is adopted and the corresponding pieces of status information
(description files, ECU address and diagnosis protocol) displayed.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 127
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-6: 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-7: Error message displayed when an incorrect vehicle identification number is entered
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 128
• 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: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 129
You start the function either by clicking the "Done" button or by pressing function key <F8> on the
keyboard.
• If no entries have been made, the program switches to the function start menu (see Fig. 6-2:
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: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 130
The following functions are available in the programming execution phase of Comfort mode:
• ECU flash programming (depends on the job data)
• ECU flash programming update (depends on the job data)
• Calling of general functions (Special, Diagnosis)
• Ending of the programming execution phase of Comfort mode by switching to the programming
settings phase of Comfort mode or Expert mode.
10 Vehicle identification number is displayed only if the KOMFORT_MIT_AIF entry in WINKFPT.INI is set to ON.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 131
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.INI) in the programming settings phase of Comfort mode,
too.
You start the function either by clicking the "Program" button or by pressing function key <F3> on the
keyboard.
This function button/key starts flash programming of one or more control units in Comfort mode.
Fig. 7-9: 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 132
The status of the programming procedure is indicated by a progress bar (0 - 100 %) and as a
percentage display in the blue menu status line.
If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programming
voltage" is displayed in the top right-hand corner.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 133
At the end of the ECU flash programming procedure, the message <<Programming OK>> appears:
Fig. 7-11: 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.INI file
is explicitly set to OFF.
In the event of multiple selection of control units, the job data for the next programming procedure is
displayed automatically after each programming procedure, and programming is started again by
clicking the "Program" function button (or pressing <F3>).
This means it is possible to abort or to change settings (e.g. HW interface or diagnosis protocol) at any
time between the individual programming procedures. At the end of the multiple programming
procedure, the message <<Multiple programming finished>> appears:
Fig. 7-12: Message displayed when multiple programming has been successful
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 134
The function button is activated only following successful input of the job data by means of the
"Update ZUSB" function in the programming settings phase of Comfort mode.
You start the function either by clicking the "Prog. ZB-Update" button or by pressing function key <F3>
on the keyboard.
This function button starts updating of a control unit to the latest assembly identification. Updating to an
incompatible hardware release by means of BSU (boot sector update) is also borne in mind.
For this purpose, the vehicle identification number and the assembly identification number are read out
of the last UIF entry in the control unit.
In addition to this assembly identification number, the latest (current) assembly identification number is
read from the file \<root>\data\<ecufam>\<ecufam>.his (= ZUSB history). A switch to a different ECU
family and therefore to a new, corresponding ZUSB history is possible.
These two assembly identification numbers are displayed in a dialog box that has to be acknowledged:
Fig. 7-13: Dialog box displaying the ZB number from the ECU and the current ZB number
• If you click "No", programming to the latest assembly identification number is aborted.
• If you click "Yes", programming (updating) to the latest assembly identification number is started.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 135
Fig. 7-14: 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.
The status of the programming procedure is indicated by a progress bar (0 - 100 %) and as a
percentage display in the blue menu status line.
"Fig. 7-10: ECU flash programming in Comfort mode").
If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programming
voltage" is displayed in the top right-hand corner.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 136
At the end of the ZUSB update programming procedure, the message <<ZUSB-Update programming
OK>> appears:
Fig. 7-15: 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.INI file
is explicitly set to OFF.
In the event of multiple selection of control units, the job data for the next programming procedure is
displayed automatically after each programming procedure, and programming is started again by
clicking the "Prog. ZB-Update" function button (or pressing <F3>).
This means it is possible to abort or to change settings (e.g. HW interface or diagnosis protocol) at any
time between the individual programming procedures.
At the end of the multiple programming procedure, the message <<Multiple ZUSB-Update
programming finished>> appears:
Fig. 7-16: Message displayed when multiple ZUSB update programming has been successful
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 137
The functions of programming settings phase Level 1 are used to select the description files.
The functions of programming settings phase Level 2 are used to enter the ECU address and select
data set files.
The functions of the programming execution phase are used for flash programming a program data
set or data data set.
Whether or not you can switching function phase depends on the scope of the job data you have
entered.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 138
• Loading a PABD
• Loading a P-SGBD
• Ending programming settings phase Level 1.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 139
When you activate this function, a dialog box opens in which you select a PABD.
The source code of the flash sequence description files (PABDs) is available in the INPA script
language.
For processing in WinKFPT, files can be available in source code or in compiled form; the compiled
form is generated from the source code by means of the CABI compiler.
Since the functionality of the CABI compiler is integrated in the COAPI, WinKFPT can process both
forms of a PABD.
The criterion by which source code and the compiled form can be distinguished is the extension of the
PABD file name, e.g.:
• 17EK924.IPS PABD in source code
• 17EK924.IPO PABD in compiled form.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 140
This dialog box displays either all the files in the <root>\SGDAT 11 directory that have the extension
IPS or the extension IPO.
This depends on the CabdFormat configuration set in WINKFPT.INI and COAPI.INI (see "3.4.1
Configuration in COAPI.INI", "3.4.2 Configuration in WINKFPT.INI").
• If you click "Cancel", selection of a PABD is aborted. The PABD selected beforehand remains
selected.
• If you click "OK", the PABD is adopted and "PABD" is displayed as status information.
After you have selected a PABD, WinKFPT automatically checks whether a P-SGBD has already been
selected and is displayed as status information.
P-SGBD not selected: the function menu for programming settings phase Level 1 remains active.
P-SGBD selected: the program switches to the function menu for programming settings phase
Level 2.
By selecting a PABD and P-SGBD, you implicitly select a control unit and the program checks
whether the control unit supports more than one diagnosis protocol.
If this is the case, the menu option "Diagnosis protocol" is activated and the default diagnosis
protocol is displayed as status information (see "5.3.2 Selecting (Choosing) a Diagnosis
Protocol").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 141
When you activate this function, a dialog box opens in which you select a P-SGBD.
This dialog box displays all the files in the <ediabas>\ECU\12 directory with the extension PRG.
• If you click "Cancel", selection of a P-SGBD is aborted. The P-SGBD selected beforehand remains
selected.
• If you click "OK", the P-SGBD is adopted and "P-SGBD" is displayed as status information.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 142
After you have selected a P-SGBD, WinKFPT automatically checks whether a PABD has already been
selected and is displayed as status information.
PABD not selected: the function menu for programming settings phase Level 1 remains active.
PABD selected: the program switches to the function menu for programming settings phase Level
2.
By selecting a PABD and P-SGBD, you implicitly select a control unit and the program checks
whether the control unit supports more than one diagnosis protocol.
If this is the case, the menu option "Diagnosis protocol" is activated and the default diagnosis
protocol is displayed as status information (see "5.3.2 Selecting (Choosing) a Diagnosis
Protocol").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 143
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 144
When you activate this function, a dialog box opens in which you enter 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", input of an ECU address is aborted and the ECU address entered beforehand
remains entered.
If the P-SGBD does not contain a job for setting the ECU address, the address is fixed in the P-
SGBD and is the text "P-SGBD using internal address" is displayed as status information under
"ECU address/integration position".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 145
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:
This dialog box displays all the files in the \<root>\data\develop12 directory with the extensions 0BA
and BAF.
• If you click "Cancel", selection of a NAAB data set is aborted and the NAAB data set selected
beforehand remains entered.
• If you click "OK", selection of a NAAB data set is completed and displayed as status information in
"NAAB file".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 146
Once the NAAB data set has been selected, the UIF is read.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 147
When you activate this function, a dialog box opens in which you select a program data set:
This dialog box displays all the files in the \<root>\data\develop12 directory with the extensions 0PA
and PAF.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 148
• If you click "Cancel", selection of a program data set is aborted and the program data set selected
beforehand remains entered.
• If you click "OK", selection of a program data set is completed and displayed as status information in
"Program file".
Once the program data set has been selected, WinKFPT checks whether the data set matches the
control unit.
To this end, the hardware reference is read out of the control unit and compared with the reference of
the data set (keyword: $REFERENZ).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 149
• Hardware reference from the ECU and reference from the data set do not match up:
The following error message is displayed:
Fig. 8-8: 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:".
The program data set can be programmed even if the references do not match up.
N.B.:
The control unit may be unusable following programming and have to be submitted for recycling.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 150
When you activate this function, a dialog box opens in which you select a data data set (characteristic-
diagram data):
This dialog box displays all the files in the \<root>\data\develop13 directory with the extensions 0DA
and DAF.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 151
• If you click "Cancel", selection of a data data set is aborted and the data data set selected
beforehand remains entered.
• If you click "OK", selection of a data data set is completed and displayed as status information in
"Data file".
Once the data data set has been selected, WinKFPT checks whether the data set matches the control
unit.
To this end, the data reference is read out of the control unit and compared with the reference of the
data set (keyword: $REFERENZ).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 152
• Data reference from the ECU and reference from the data set do not match up:
The following error message is displayed:
Fig. 8-10: 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 data data set can be programmed even if the references do not match up.
N.B.:
The control unit may be unusable following programming and have to be submitted for recycling.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 153
You start the function either by clicking the "Done" button or by pressing function key <F8> on the
keyboard.
• If no entries have been made, the program switches to the function start menu (see Fig. 6-2:
Function start menu of WinKFPT).
• If only a PABD has been selected, the program switches to the function start menu.
• If only a P-SGBD has been selected, the program switches to the function start menu.
• If a PABD and P-SGBD have been selected, the program checks whether an ECU address has to be
entered.
If an ECU address is not required, the text "P-SGBD using internal address" is displayed as status
information under "ECU address/integration position".
If an ECU address is required and one has not been entered, the following error message is
displayed:
Fig. 8-11: Error message if no ECU address has been entered in Expert mode
When you acknowledge the error message, the program switches to the function start menu.
PABD and P-SGBD remain selected and you can now enter the ECU address.
• If a PABD, P-SGBD and ECU address have been selected, only the general functions are made
available for use (see "9 General Functions").
• If a PABD, P-SGBD, ECU address and a data set for program and/or data have been selected, the
program switches to the function menu of the programming execution phase of Expert mode.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 154
The following functions are available in the programming execution phase of Expert mode:
• NAAB programming (BSU) (depends on the job data)
• Program programming (depends on the job data)
• Data programming (depends on the job data)
• Calling of general functions (Special, Diagnosis)
• Ending of the programming execution phase of Expert mode by switching to the programming
settings phase of Comfort mode or Expert mode.
10 Vehicle identification number is displayed only if the EXPERT_MIT_AIF entry in WINKFPT.INI is set to ON.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 155
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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 156
The status of the programming procedure is indicated by a progress bar (0 - 100 %) and as a
percentage display in the blue menu status line.
If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programming
voltage is displayed in the top right-hand corner.
At the end of the ECU flash programming procedure and exchange of the boot sector, the message
<<Bootsektorupdate OK>> appears:
Fig. 8-13: Message displayed following successful ECU flashing programming in Expert mode
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 157
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.
Note:
The user info field is programmed only if the configuration settings EXPERT_MIT_AIF and
AIF_SCHREIBEN_NACH_PROGRAMM in WINKFPT.INI are set to ON.
Note:
If a UIF is to be programmed, the dialog box for entering the vehicle identification number appears (see
"7.1.4 Function: Entering a Vehicle Identification Number").
Without a vehicle identification number, programming is not possible in this case.
The following prompt appears once you have entered the vehicle identification number:
Note:
The number of times the UIF can be programmed is taken from the PABD.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 158
The status of the programming procedure is indicated by a progress bar (0 - 100 %).
If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programming
voltage" is displayed in the top right-hand corner.
At the end of the ECU flash programming procedure, the message <<Programming OK>> appears:
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 159
Fig. 8-16: Message displayed following successful ECU flashing programming in Expert mode
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.INI are set to ON.
Note:
If a UIF is to be programmed, the dialog box for entering the vehicle identification number appears (see
"7.1.4 Function: Entering a Vehicle Identification Number").
Without a vehicle identification number, programming is not possible in this case.
The following prompt appears once you have entered the vehicle identification number:
Note:
The number of times the UIF can be programmed is taken from the PABD.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 160
The status of the programming procedure is indicated by a progress bar (0 - 100 %) (see "Fig. 8-15:
ECU flash programming in Expert mode").
If the configuration entry "ANZEIGE_U_PROG" has been set to ON in WINKFPT.INI, "Programming
voltage" is displayed in the top right-hand corner.
At the end of the ECU flash programming procedure, the message <<Programming OK>> appears
(see "Fig. 8-16: Message displayed following successful ECU flashing programming in Expert mode").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 161
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. 9-1: Function menu with the function buttons "Special" and "Diagnosis"
Since calling a general function always involves communicating with an ECU, a minimum amount of
job data must have been entered in the active operating mode of WinKFPT.
The function buttons for the general functions are only displayed:
• once programming settings phase Level 1 or 2 of Expert mode has been completed and at least one
PABD, P-SGBD and ECU address (ECU address only if the P-SGBD uses an external address)
have been selected/entered (see "8.1 Functions of Programming Settings Phase Level 1 in Expert
Mode" and "8.2 Functions of Programming Settings Phase Level 2 in Expert Mode").
• once the programming settings phase of Comfort mode has been completed and a ZUSB number
and ECU address/integration position have been selected/entered by means of one of the following
functions: "Enter ZUSB", "Choose ZUSB" or "Update ZUSB" (see "7.1 Functions of the
Programming Settings Phase in Comfort Mode").
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 162
When you click the "Special" function button (or press <F3>) in Expert or Comfort mode, the function
menu with the function buttons for calling the special functions of WinKFPT is opened:
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: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 163
When you activate this function, all the user info field (UIF) entries of the control unit are read out and
displayed by the following PABD job:
• SG_AIF_LESEN
The contents of the UIF display dialog are written to the file AIF_<Interface>_<Unit>.OUT in the
\<root>\BIN directory.
The contents of the AIF_<Interface>_<Unit>.OUT file are overwritten every time "Read UIF" is
activated.
The file name is displayed in the header of the UIF display dialog.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 164
Fig. 9-3: Display dialog for the Special function "Read UIF"
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 165
When you activate this function, 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>.OUT in
the \<root>\BIN directory.
The contents of the BD_<Interface>_<Unit>.OUT file are overwritten every time "ECU baudrates" is
activated.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 166
If you call "ECU baudrates" for control units with standard description files, the following error
message appears:
Fig. 9-4: Error message displayed when you call "ECU baudrates"
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 167
When you activate this function, the submenu for reading and writing the calibration values of the
control unit opens.
Fig. 9-5: 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.
• Connect the control unit to which the calibration values are to be written.
• If necessary, select the HW interface and diagnosis protocol for the second control unit.
You close the submenu for calibration values either by clicking the "Done" button
The submenu for calibration values is closed and the Special function menu is displayed again.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 168
When you activate this function, WinKFPT switches to the submenu for VS20/DS2 mode.
By activating "VS20 Mode" or "DS2 Mode" from this submenu, the control unit connected can be
switched to VS20 or DS2 mode by means of the PABD job VS20_MODE or D2 MODE.
If you call "VS20 Mode" or "DS2 Mode" for control units with standard description files, the following
error message appears:
Fig. 9-6: Error message displayed when you call "VS20 Mode" or "DS2 Mode"
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 169
When you activate this function, 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 170
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 171
When you activate this function, the following data is read out of the control unit and displayed:
• Data reference
• Hardware reference
• Supplier info field (ZIF)
• Backup of the supplier info field
• Programming status (ECU status)
The data is read out of the control unit by the following PABD jobs:
• DATEN_REFERENZ
• HW_REFERENZ
• ZIF
• ZIF_BACKUP
• SG_STATUS_LESEN
The contents of the ECU status display dialog are written to the file REF_<Interface>_<Unit>.OUT in
the \<root>\BIN directory.
The contents of the REF_<Interface>_<Unit>.OUT file are overwritten every time "ECU Status" is
activated.
The file name is displayed in the header of the ECU status display dialog.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 172
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 173
When you activate this function, 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>.OUT in the \<root>\BIN directory.
The contents of the IDENT_<Interface>_<Unit>.OUT file are overwritten every time "ECU Ident" is
activated.
The file name is displayed in the header of the ECU identification display dialog.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 174
When you activate this function, the internal temperature of the control unit is read out and displayed.
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>.OUT in the \<root>\BIN directory.
The contents of the INNENTMP_<Interface>_<Unit>.OUT file are overwritten every time "ECU intern.
Temp" is activated.
The file name is displayed in the header of the ECU internal temperature display dialog.
If the control unit does not support this function, 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".
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 175
When you activate this function, 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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 176
The process of flash programming an ECU with WinKFPT is very complex and depends on trouble-
free interaction of the following components:
• Hardware connection – Test computer ↔ Diagnosis HW interface ↔ ECU
• Software connection – WinKFPT ↔ EDIABAS ↔ Diagnose interface driver ↔ ECU program
• Configuration of WinKFPT and COAPI
• Description files PABD and P-SGBD
• Logistics files
• Programming data files (PAF, DAF, etc.)
Each component contains a multitude of potential errors that must be trapped by WinKFPT 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.
The functions built into WinKFPT can be roughly split into two types: namely, into functions with and
without COAPI calls. The manner in which errors that arise while executing these functions differs
between the two types.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 177
10.1Displaying Errors
The figure below shows the "Normal view" display of a WinKFPT error associated with a defective
COAPI call.
Switching to the "Extended view" is of no benefit to "normal" users. This view is intended merely as an
additional debugging aid for WinKFPT or COAPI experts.
In the example above, you can see that initialization of the COAPI by WinKFPT has failed.
The list of errors from the respective COAPI call levels clearly shows the user which of the many
initialization errors possible is the actual cause of the error.
The first line of the error list displays the error message of the "lowest" COAPI call level and generally
contains comprehensive and crucial information for debugging purposes.
In this case, the user must check whether the file "kfconfxx.da2" is present in the <root>\DATA\gdaten
directory, or whether or not he has read rights to it.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 178
Possible cause • A logistics file is missing in the ../data/gdaten directory. The error
dialog tells you which file it is.
Debugging • Import an up-to-date assembly line data set with description files.
• Copy the missing logistics file to the ../data/gdaten directory by
hand.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 179
Possible cause • The assembly line data set does not contain a file of type
<EcuFamilyname>.dat
Debugging • Fetch the correct assembly line data set (e.g. from Darwin).
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 180
Time of occurrence • 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.
Possible cause • The PABD from the configuration does not exist.
Time of occurrence • 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.
Possible cause • The SGBD from the configuration does not exist.
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: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 181
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: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 182
Possible cause • An ECU family-specific logistics file (DAT, HWH or HIS) is faulty.
The error dialog (in particular error 4206) tells you which file it 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.
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.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 183
Time of occurrence • In Expert mode after selecting PABD and SGBD, when activating
the [Done] button.
Possible cause • A 2-digit, hexadecimal number has not been entered as the ECU
address.
Debugging • Enter a correct hexadecimal number.
Time of occurrence • When entering a vehicle identification number (necessary when UIF
write is active).
Possible cause • The vehicle identification number was either not a 7-digit number or
not alphanumeric.
Debugging • Enter a correct vehicle identification number.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 184
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 185
Time of occurrence • When starting programming by activating the <Prog. Data> button,
following input of the PABD, P-SGBD and the program data set in
Expert mode.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 186
Error COAPI error 2064: Delete error in coding data (e.g. ZCS)
Time of occurrence • When starting programming by activating the <Prog. Data> button.
Possible cause • The last programming session was not successfully completed and
terminated.
Debugging • The program must be flashed to the ECU again.
To this end, enter PABD, P-SGBD and the program data set in Expert
mode. Confirm the entries made in Expert mode by activating the
<Done> button.
Start flash programming of the control unit with the program data set by
activating the <Prog. Program> button.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 187
Glossary
Comfort mode Programming after entering or selecting the job data, assembly
identification number and control unit address, and the vehicle
identification number if UIF write is activated.
Interface Hardware unit for communication with control units, e.g. EDIC, ADS,
MOST
NAAB Boot update description file. 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.
PABD Flash sequence description file
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 188
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.
ZIF Supplier info field. The ZIF in the control unit indicates the state of
development of the control unit program.
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 189
Contents
reading 173
A ECU internal temperature
reading+ 174
Assembly identification
ECU status
updating 125
displaying 171
Expert mode
B definition 187
Baudrates function phase 1 137
reading 165 import files 66
C F
Calibration values Function
reading 167 choosing a ZUSB number 124
COAPI displaying the ECU status 171
definition 187 ending function phase 0 129, 153
Comfort mode entering a vehicle identification number 127
definition 187 entering a ZUSB number 121
import files 66 EWS alignment 169
Configuration 39 flash programming in Comfort mode 131,
COAPI.INI 24, 39 134
EDIABAS.INI 38, 39 Flash programming in Comfort mode 157,
Expert mode 34, 35, 36, 37, 106 159
WinKFPT 24 general functions 161
WINKFPT.INI 28, 39 loading a PABD 139
loading a P-SGBD 141
D reading the calibration values 167
Data sets, data reading the ECU baudrates 165
import 76 reading the ECU identification 173
Data sets, program reading the ECU internal temperature 174
import 76 reading the UIF 163
Diagnosis protocol 95 updating an assembly identification 125
choosing (selecting) 98 VS20/DS2 mode 168
job Function phase 1
DIAGNOSEPROTOKOLL_SETZEN 99 Expert mode 137
Job
DIAGNOSEPROTOKOLL_LESEN 98 H
selecting 103, 104, 106 HW interface 20, 22, 24, 30, 31, 34, 38, 58,
Directory 95, 96, 97, 133, 136, 185
structure 19 choosing (selecting) 96
E I
ECU identification Import
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8
WinKFPT
User's Guide
Page 190
P
Z
PABD
ZUSB number
definition 187
choosing 124
import 80
entering 121
loading 139
Date: 17.11.05
File: Handb-winkfpt32(5.1)_v1.9_eng.doc Version: 1.8