Winkfp Handbook v1.8 Eng

WinKFPTUser's Guide

Page 1

Date: 20.10.04

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

WinKFPT 5.1

User's Guide

Version 1.8

WinKFPTUser's Guide

Page 2

Date: 20.10.04


Contents1 FOREWORD ............................................................................................................................9

1.1 Using this User's Guide and the Online Help..............................................................................91.2 About This User's Guide..........................................................................................................101.3 Conventions Used ...................................................................................................................11

2 INTRODUCTION.....................................................................................................................122.1 About WinKFPT ......................................................................................................................122.2 Possibilities in WinKFPT .........................................................................................................12

2.2.1Multiple Instancing Capability ..........................................................................................122.2.2Operating Modes.............................................................................................................132.2.3Programming of ECUs in Dialog Mode ............................................................................142.2.4Programming of ECUs in Batch Mode .............................................................................14

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

3 FIRST STEPS.........................................................................................................................163.1 System Requirements of WinKFPT .........................................................................................163.2 Installing WinKFPT .................................................................................................................163.3 Directory Structure of WinKFPT .............................................................................................17

3.3.1Configuration of the basic directory for the working directories of WinKFPT.....................223.4 Configuring WinKFPT .............................................................................................................23

3.4.1Configuration in COAPI.INI..............................................................................................233.4.2Configuration in WINKFPT.INI .........................................................................................263.4.3Configuration for Expert Mode .........................................................................................323.4.4Configuration in EDIABAS.INI..........................................................................................37

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

4 STARTING WINKFPT .............................................................................................................404.1 Calling Parameters of WinKFPT..............................................................................................40

4.1.1Type Description of the Calling Parameters of WinKFPT .................................................424.2 Status Displays of WinKFPT ...................................................................................................434.3 Starting WinKFPT in Compile Mode ........................................................................................464.4 Starting WinKFPT in Batch Mode ............................................................................................48

4.4.1Control File for Batch Mode in Comfort Mode ..................................................................514.4.2Control File for Batch Mode in Expert Mode.....................................................................534.4.3Starting a Programming Job in Batch Mode.....................................................................554.4.4Switching HW Interface and Diagnosis Protocol in Batch Mode .......................................574.4.5Starting Several Instances in Batch Mode........................................................................58

4.5 Starting WinKFPT in Dialog Mode ...........................................................................................594.5.1Starting Several Instances in Dialog Mode.......................................................................59

WinKFPTUser's Guide

Page 3

Date: 20.10.04


5 WINKFPT'S MAIN MENU........................................................................................................615.1 Display Menu ..........................................................................................................................61

5.1.1Display CABI.ERR ......................................................................................................625.1.2Display ERROR.LOG..................................................................................................625.1.3Display PABD Parameters ..........................................................................................625.1.4Display HW History.....................................................................................................625.1.5Display ZB History ......................................................................................................625.1.6Display ZB Rules ........................................................................................................625.1.7Display API Trace File.................................................................................................635.1.8Display IFH Trace File.................................................................................................635.1.9Display Batch Mode ....................................................................................................63

5.2 Import/Export Menu.................................................................................................................645.2.1Import Submenu .............................................................................................................645.2.2Export Submenu .............................................................................................................825.2.3Deleting Assembly Line Data...........................................................................................92

5.3 Communication Menu .............................................................................................................955.3.1Selecting (Choosing) a HW Interface...............................................................................965.3.2Selecting (Choosing) a Diagnosis Protocol ......................................................................98

5.4 Configuration Menu ...............................................................................................................1005.5 Help Menu.............................................................................................................................103

5.5.1Contents - Calling the Online Help.................................................................................1035.5.2Info - Version Information of WinKFPT ..........................................................................104

5.6 End Menu..............................................................................................................................1065.6.1Exit 106

6 FUNCTIONS OF WINKFPT...................................................................................................1076.1 Function Start Menu: Operating Modes of WinKFPT..............................................................110

6.1.1Comfort Mode ...............................................................................................................1126.1.2Expert Mode..................................................................................................................116

7 FUNCTION PHASES IN COMFORT MODE ..........................................................................1197.1 Functions of the Programming Settings Phase in Comfort Mode............................................120

7.1.1Function: Entering a ZUSB Number...............................................................................1217.1.2Function: Selecting a ZUSB number ..............................................................................1247.1.3Function: Updating an Assembly Identification...............................................................1257.1.4Function: Entering a Vehicle Identification Number ........................................................1277.1.5Function: Done (Comfort Mode) ....................................................................................129

7.2 Functions of the Programming Execution Phase in Comfort Mode .........................................1307.2.1Function: Flash Programming .......................................................................................1317.2.2Function: Programming Update.....................................................................................134

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

WinKFPTUser's Guide

Page 4

Date: 20.10.04


8.1 Functions of Programming Settings Phase Level 1 in Expert Mode ........................................1388.1.1Function: Loading a PABD ............................................................................................1398.1.2Function: Loading a P-SGBD ........................................................................................141

8.2 Functions of Programming Settings Phase Level 2 in Expert Mode ........................................1438.2.1Function: Loading an ECU address ...............................................................................1448.2.2Function: Loading a Data Set NAAB File.....................................................................1458.2.3Function: Loading a Data Set Program File ................................................................1478.2.4Function: Loading a Data Set Data File.......................................................................1508.2.5Function: Done (Expert Mode) .......................................................................................153

8.3 Functions of the Programming Execution Phase in Expert Mode............................................1548.3.1Function: Programming a NAAB Data Set .....................................................................1558.3.2Function: Programming a Program Data Set .................................................................1578.3.3Function: Programming a Data Data Set .......................................................................159

9 GENERAL FUNCTIONS........................................................................................................1619.1 Special Functions..................................................................................................................162

9.1.1Function: Reading the UIF.............................................................................................1639.1.2Function: Reading the ECU Baudrates...........................................................................1659.1.3Function: Reading and Writing the Calibration Values ...................................................1679.1.4Function: VS20/DS2 Mode ............................................................................................1689.1.5Function: EWS Alignment .............................................................................................1699.1.6Function: Done..............................................................................................................169

9.2 Diagnosis Functions..............................................................................................................1709.2.1Function: Displaying the ECU Status .............................................................................1719.2.2Function: Reading the ECU Identification.......................................................................1739.2.3Function: Reading the ECU Internal Temperature..........................................................1749.2.4Function: Done..............................................................................................................175

10 ERROR HANDLING IN WINKFPT.........................................................................................17610.1 Displaying Errors ................................................................................................................17710.2 Description and Elimination of Frequently Occurring Errors.................................................178

10.2.1 Errors When Starting WinKFPT..................................................................................17810.2.2 Errors When Importing Assembly Line Data ...............................................................17910.2.3 Errors When Entering Flash Data ...............................................................................18010.2.4 Errors During Data Programming ...............................................................................185

WinKFPTUser's Guide

Page 5

Date: 20.10.04


List of Figures

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

WinKFPTUser's Guide

Page 6

Date: 20.10.04


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

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

WinKFPTUser's Guide

Page 7

Date: 20.10.04


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

WinKFPTUser's Guide

Page 8

Date: 20.10.04


List of Tables

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

WinKFPTUser's Guide

Page 9

Date: 20.10.04


1 FOREWORD

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

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

WinKFPTUser's Guide

Page 10

Date: 20.10.04


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

Chapter Description

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

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

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

Description of the flash sequence in Batch mode.

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

Menu options of the main menu bar of WinKFPT and theirsubmenus

6 Functions of WinKFPT Activating Comfort mode and Expert mode.

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

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

9 General Functions Special and diagnostics functions

10 Known control and configuration errors

WinKFPTUser's Guide

Page 11

Date: 20.10.04


1.3 Conventions UsedThis User's Guide uses the following typographical conventions:

Example Description

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

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

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

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

Words set in double angle brackets denote messagesdisplayed to the user.

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

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

WinKFPTUser's Guide

Page 12

Date: 20.10.04


2 INTRODUCTION

2.1 About WinKFPT

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

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

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

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

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

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

2.2 Possibilities in WinKFPT

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

WinKFPTUser's Guide

Page 13

Date: 20.10.04


2.2.2 Operating ModesWinKFPT has two main operating modesDialog modeBatch mode

and one special operating modeCompile mode.

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

Operating mode Description

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

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

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

Table 2-1: Operating modes of WinKFPT

WinKFPTUser's Guide

Page 14

Date: 20.10.04


2.2.3 Programming of ECUs in Dialog ModeThere are three possibilities for flash programming a control unit using the Dialog mode of WinKFPT.

The two possibilities in Comfort mode:

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

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

One possibility in Expert mode:

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

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

2.2.4 Programming of ECUs in Batch ModeBatch mode is used to flash program any number of control units one after the other.

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

WinKFPTUser's Guide

Page 15

Date: 20.10.04


2.3 Architecture of WinKFPT

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

PABD

Application

COAPI

BMW-Logist ic files

WinKFPT (1. Instance)

Diagnosis-Bus

EDIABAS-Runtime

HW-Interface I

EDIABAS-API(1.Instance)

P-SGBD

COAPI

WinKFPT (2. Instance)

Diagnosis-Bus

EDIABAS-Runtime

HW-Interface II

EDIABAS-API(2.Instance)

Fig. 2-1: Communication architecture in WinKFPT

WinKFPTUser's Guide

Page 16

Date: 20.10.04


3 FIRST STEPS

3.1 System Requirements of WinKFPTTo be able to flash program control units with WinKFPT, the system requirements listed in the tablebelow must be met:

Requirement RemarkComputer PENTIUM II processor or higher with 64 MB RAM

and 50 MB of free memory

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

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

Built-in EDIABAS interface Version 6.0.2 or higher

Control unit Programmable

Table 3-1: System requirements of WinKFPT

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

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

WinKFPTUser's Guide

Page 17

Date: 20.10.04


3.3 Directory Structure of WinKFPTWinKFPT is installed in the directory you specify during installation.

The installation directory contains the following subdirectories,the starting directory of WinKFPT: \\BIN

the workong directories of WinKFPT: \\CFGDAT \\DATA \\FORMAT \\SGDAT \\WORK

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

Directory Contents

This directory contains all necessary program files (EXE, DLL) and theinitialization/configuration file WINKFPT.INI.It also serves as a working directory for storing error files and other temporaryfiles created while the program is running (e.g.INNENTMP_INTERFACE_unit.OUT).

CABIGER.DLL Coding sequence interpreter localization support DLL (German)

CABUS.DLL Coding sequence interpreter localization support DLL (English)

WINKFPT.INI Configuration file for WinKFPT

WINKFPT32.EXE Executable for WinKFPT

\\BIN

WINKFPT32.HLP Online help for WinKFPT

WinKFPTUser's Guide

Page 18

Date: 20.10.04


Directory Contents

Error file.Every error file refers to an instanceof WinKFPT.The file name incorporates the HWinterface identifier and unit identifierto enable assignment to the relevantinstance.

INTERFACE HW interfaceidentifier

ERROR_INTERFACE_unit.LOGAs of Version 4.6.0, the installationdirectory is only the default directory forstoring error files.You can select/set any directory youwant as the storage directory by meansof the main menu option.

_unit Unit identifier (_, A,B, C, ...)

*.OUT Temporary files created duringprogram run

Directory contains the initialization files:

INPA.INI Initialization file for the coding sequenceinterpreter.The contents of this file are laid down at the timeof delivery of WinKFPT and are not allowed to beused by the user.

For further information, see system description ofthe COAPI.

COAPI.INI Configuration for the coding application interface

Directory also contains the text files for error messages:

COAPIERR.TXT Text file for COAPI error messages

\\CFGDAT

EDIERROR.TXT Text file for EDIABAS error messages

Directory contains the programming data files available in Expert mode.

*.PAF Program exchange files

*.DAF Data exchange files

\\DATA\DEVELOP

*.BAF NAAB exchange files

WinKFPTUser's Guide

Page 19

Date: 20.10.04


Directory Contents

*.0PA Data set files for program

*.0DA Data set files for data

*.0BA Data set files for NAAB

Directory contains the logistics files for ECU flash programming. These mustalways be available. The files are loaded by importing an assembly line dataset:

KFCONFxx.DA2 Contains all ECU members and the associatednames of the description and ECU-specificlogistics files and a data set identifier for each ofthese ECU members.As of Version 4.6.0, only those ECU members ofthe imported, valid WDPs are contained.

HWNR.DA2 Contains all the hardware numbers everyassigned for all ECUsAs of Version 4.6.0, only those hardwarenumbers for ECU families of the imported, validWDPs are contained.

NPV.DAT Logistics file for retrofit actions in the HO. Of norelevance to WinKFPT.

Special configuration files that must be present if required:

\\DATA\GDATEN

INFO.GER Contains the integration position of an ECUmember in plain text for user selection inWinKFPT, e.g. "Passenger side, rear".In general, these integration position texts onlyexist for ECUs that have different ECU members,i.e. integration position, but belong to the sameECU family.

Only for Comfort mode for selectionof the integration position (= implicit input of theECU address when the same control unit type isinstalled more than once in the same car)

WinKFPTUser's Guide

Page 20

Date: 20.10.04


Directory Contents

PRGIFSEL.DAT Contains variable assignments of ECU family toHW interface and diagnosis protocol.

Only for Batch mode for flashprogramming several control units one after theother.

SGIDC.AS2 Contains the authentication codes of all ECUs forauthentication level "3".

Only for control units withauthentication.

SGIDD.AS2 Contains the authentication codes of all ECUs forauthentication level "4".

Only for control units withauthentication.

HISTORIE.BSU Contains the necessary specifications fordetermining whether a boot sector update ispossible for all control units affected.

Facilitates a boot sector update forcertain control units.

Each of these directories contains the ASCII programming data for an ECUfamily . These directories are used in Comfort mode.

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

.DAT Contains all current assembly identificationnumbers of an ECU family.

.HIS Contains all compatible assembly identificationnumbers ever assigned for an ECU family in oneor more series.

\\DATA\

.HWH Contains the history of compatible hardwarenumbers of an ECU family in one or more series.

WinKFPTUser's Guide

Page 21

Date: 20.10.04


Directory Contents

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

\\DATA\KONV.TMP Temporary directory for storing programming data files while WinKFPT isrunning through several instances:\\DATA\KONV.TMP2,\\DATA\KONV.TMP3 etc...

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

*.IPS PABDs in source code

*.IPO PABDs in compiled code

\

WinKFPTUser's Guide

Page 22

Date: 20.10.04


3.3.1 Configuration of the basic directory for the working directories of WinKFPTBy means of the main menu option "Configuration" (see 5.4 Configuration Menu) the basic directoryfor the working directories can be changed at any time.

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

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

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

WinKFPTUser's Guide

Page 23

Date: 20.10.04


3.4 Configuring WinKFPTWinKFPT is configured by means of the following initialization files:

Configuration file Contents

COAPI.INI Configuration for the coding application interface

WINKFPT.INI Configuration for WinKFPT

EDIABAS.INI Configuration for the diagnosis HW interface

Table 3-1: Initialization files of WinKFPT

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

Configuration entry Possible setting Default Description[Pfadangaben] Paths for configuration files, data and trace files are set in this section.

WORKING_DIR Complete path orrelative to1

\WORK1 The entry specifies the directorythat is used for COAPI tracefiles and for temporary files.

ERROR_TEXTE Complete path orrelative to1

\CFGDAT1 The entry specifies the directoryin which the COAPI error textfile is located.

GENERAL_KF_DATA_PATH Complete path orrelative to1

\DATA1 The entry specifies the directoryin which the programming filesare located.

[Kennfeldprog] This section contains entries that are required specifically for enginecharacteristics map programming.

1 : installation directory of WinKFPT

WinKFPTUser's Guide

Page 24

Date: 20.10.04


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

that is entered as the serialnumber in the user info field.

KUNDENNUMMER 5-digit number 11111 The entry specifies the valuethat is entered as the customernumber in the user info field.

KM Max. 2-digitnumber

0 The entry specifies the valuethat is entered as the mileage(in km) in the user info field.

ZBNUMMER3 7-digit number 0000000 The entry specifies the valuethat is entered as the assemblyidentification number in the userinfo field.

SWNUMMER3 7-digit number 0000000 The entry specifies the valuethat is entered as the softwarenumber in the user info field.

TYPNUMMER3 7-digit number 0000000 The entry specifies the valuethat is entered as the type testnumber in the user info field.

AEINDEX3 2-digit number 00 The entry specifies the valuethat is entered as the changeindex in the user info field.

[Setup] In this section, you set which form of the PABD is to be displayed forselection in WinKFPT.

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

mode with UIF writing).

WinKFPTUser's Guide

Page 25

Date: 20.10.04


Configuration entry Possible setting Default DescriptionCabdFormat IPS

IPOCOM

IPO The entry defines whether theCOAPI (as part of WinKFPT) isto use PABDs as source files oras compiled files. This entry ishowever irrelevant because it iscancelled by the correspondingentry in WinKfpt.ini or thesetting in the Configurationdialog.

IPS PABDs as source filesIPO PABDs as compiled filesCOM WinKFPT compiles selected *.IPS files and creates *.IPO files. Compiling is started when PABD file is selected in Expert mode.

BsuActive ONOFF

ON The flag influences how theCOAPI function behaves:coapiKfCheckBsuPossibleD2

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

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

Table 3-1: Configuration in COAPI.INI

WinKFPTUser's Guide

Page 26

Date: 20.10.04


WinKFPTUser's Guide

Page 27

Date: 20.10.04


3.4.2 Configuration in WINKFPT.INIThe initialization file "\BIN\WINKFPT.INI" 2 is used to configure characteristics of WinKFPT.The following sections and entries are of importance to WinKFPT:

Configuration entry Possiblesetting Default Description

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

WindowPosition -- 0,1,-1,-1,-1,-1,0,0,643,424

The entry saves the last windowsize of WinKFPT when theprogram is exited. The programthen starts with the samecoordinates when restarted.

SPRACHE gereng

ger The entry defines the languagefor WinKFPT. Options: German(ger) and English (eng).

U_PROG ONOFF

ON The entry specifies whether theprogramming voltage isswitched ON or OFF duringflash programming.

SCHNELLE_BAUDRATE ONOFF

ON The entry specifies whether thefast baudrate is used (ON) ornot (OFF) during flashprogramming.

ANZEIGE_U_PROG ONOFF

ON The entry specifies whether thevalue of the programmingvoltage is displayed (ON) or not(OFF) during flashprogramming.

EXPERT_MIT_AIF ONOFF

ON The entry specifies whether theUIF is also programmed (ON) ornot (OFF) during flashprogramming in Expert mode.

2 : installation directory of WinKFPT

WinKFPTUser's Guide

Page 28

Date: 20.10.04



KOMFORT_MIT_AIF ONOFF

ON The entry specifies whether theUIF is also programmed (ON) ornot (OFF) during flashprogramming in Comfort mode.

AIF_SCHREIBEN_NACH_DATEN ONOFF

ON The entry specifies whether theUIF is also programmed (ON) ornot (OFF) during dataprogramming in Comfort orExpert mode.

AIF_SCHREIBEN_NACH_PROGRAMM ONOFF

ON The entry specifies whether theUIF is also programmed (ON) ornot (OFF) during programprogramming in Comfort orExpert mode.

API_TRACE 0 7OFF (= 0)ON (= 1)

1 The entry specifies the tracelevel of the API traces ofEDIABAS during flashprogramming. Trace level 0means that no traces aregenerated.

IFH_TRACE 0 3OFF (= 0)ON (= 1)

1 The entry specifies the tracelevel of the IFH traces ofEDIABAS during flashprogramming. Trace level 0means that no traces aregenerated.

PROGRAMM_ERZWINGEN ONOFF

OFF The entry specifies whether,during flash programming inComfort mode, a program isalso programmed when actuallyonly data programming wouldbe necessary.

TEST_CHECKSUMME ONOFF

ON The entry specifies whether thechecksum is validated (ON) ornot (OFF) after programming ofthe data.

WinKFPTUser's Guide

Page 29

Date: 20.10.04



CabdFormat IPSIPO(COM)

IPO The entry defines whetherWinKFPT is to use PABDs assource files or as compiled files.

IPS PABDs as source files

IPO PABDs as compiled files

COM stands for compile mode. However, it does not have to be set manually in the Ini file, rather it is set temporarily and automatically by the calling parameter "-C".

ErrorLogPath any path .\ Storage directory for theERRORn.LOG file

ExpertKonfPath any path C:\Diagprog

Base directory for export of aconfiguration of developmentfiles (Expert mode).

KomfortKonfPath any path C:\NFS-Backup

Base directory for export of aconfiguration of assembly linedata (Comfort mode).

CoapiSearchPath any path ..\ Base directory for workingdirectories of WinKFPT

[HW-Interface ] In this section, those HW interfaces are entered that can beswitched between online while WinKFPT is being used.

WinKFPTUser's Guide

Page 30

Date: 20.10.04



Interfaces are to be defined using the following syntax:[Description] = [HW interface identifier]

Example:K-Line / EDIC=EDICK-Line / ADS-OBD=STD:OBDCAN / EDIC=EDICCCAN / Vector=STD:CANMost / Optolyzer=STD:MOSTOMost / PC card=STD:MOSTP

You can select any string of letters for [Description].The texts entered as the [Description] are displayed to the user in a HW interface selection list when themenu option Communication HW Interface is selected, (e.g. K-Line / EDIC).

[HW interface identifier] is used internally in the WinKFPT program.The identifier is defined and must be known to "EDIABAS" so that "EDIABAS" can also initialize the HWinterface.

[Expert-Modus-Konfiguration] In this section, the current configuration in Expert mode issaved by the user (if necessary) when the program is exited.When the program is restarted and Expert mode reselected,the user is then able to reload this configuration.

KF_HW_INTERFACE HW interfaceidentifier

empty Saved setting of the HWinterface in Expert mode.Interface can be selected bymeans of the menu optionCommunication HWInterface.

KF_HW_INTERFACE_UNIT _, A, B, C, D, E empty Saved setting of the HWinterface unit in Expert mode.Interface unit can be selected bymeans of the menu optionCommunication HWInterface.

WinKFPTUser's Guide

Page 31

Date: 20.10.04



KF_DIAG_PROT Identifier of thediagnosisprotocol

empty Saved setting of the diagnosisprotocol in Expert mode; in thecase of a P-SGBD file thatsupports several diagnosisprotocols,the diagnosis protocol can beselected by means of the menuoption Communication

Diagnosis protocol.

KF_PSGBD P-SGBD filename

empty Saved setting of the P-SGBDfile name in Expert mode.P-SGBD file can be selected bypressing the function key ExpertMode

P-SGBD.

KF_PABD PABD file name empty Saved setting of the PABD filename in Expert mode.PABD file can be selected bypressing the function key ExpertMode

PABD.

KF_SG_ADR ECU address empty Saved setting of the ECUaddress in Expert mode.ECU address can be selectedby pressing the function keyExpert Mode ECU Address.

KF_DATEN_DATEI Data filename

empty Saved setting of the data set filefor data in Expert mode.Data set file for data can beselected by pressing thefunction key Expert Mode

Data File.

KF_PROGRAMM_DATEI Program filename

empty Saved setting of the data set filefor program in Expert mode.Data set file for program can beselected by pressingthe function key Expert Mode

Program File.

WinKFPTUser's Guide

Page 32

Date: 20.10.04



KF_NAAB_DATEI NAAB filename

empty Saved setting of the data set filefor NAAB in Expert mode.Data set file for NAAB can beselected by pressingthe function key Expert Mode

NAAB File.

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

Table 3-1: Configuration in WINKFPT.INI

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

WinKFPTUser's Guide

Page 33

Date: 20.10.04


3.4.3 Configuration for Expert ModeThe user has the option of saving and also of reloading a configuration in Expert mode if necessary.

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

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

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

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

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

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

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

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

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

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

WinKFPTUser's Guide

Page 34

Date: 20.10.04


Function: Loading a Data Set NAAB File").

WinKFPTUser's Guide

Page 35

Date: 20.10.04


3.4.3.1 Saving a Configuration for Expert Mode

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

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

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

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

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

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

WinKFPTUser's Guide

Page 36

Date: 20.10.04


3.4.3.2 Loading a Configuration for Expert Mode

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

The following dialog box appears:

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

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

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

WinKFPTUser's Guide

Page 37

Date: 20.10.04


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

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

empty configuration by clicking "OK".

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

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

WinKFPTUser's Guide

Page 38

Date: 20.10.04


3.4.4 Configuration in EDIABAS.INIThe initialization file "\CFGDAT\EDIABAS.INI"4 contains the configuration for thediagnosis HW interface.


[Configuration] This section contains configuration entries for EDIABAS.

Interface EDIC The identifier entered isinitialized as the default HWinterface when WinKFPT isstarted without callingparameters.

Table 3-1: Configuration in EDIABAS.INI

4 = installation directory for EDIABAS

WinKFPTUser's Guide

Page 39

Date: 20.10.04


3.5 Reference Configuration of WinKFPTThe following figures show the default configuration for WinKFPT after reinstallation:

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

[Einstellungen]

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

; Aif schreibenAIF_SCHREIBEN_NACH_DATEN=OFFAIF_SCHREIBEN_NACH_PROGRAMM=OFFEXPERT_MIT_AIF=OFFKOMFORT_MIT_AIF=OFF

; TraceAPI_TRACE=ONIFH_TRACE=ON

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

WinKFPTUser's Guide

Page 40

Date: 20.10.04


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

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

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

[Kennfeldprog]TEMP_DAT_FILE_DEFAULT_NAME = KFLISTE.DAT

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

; SG Dateien komprimieren; 1 -> Dateien werden immer komprimiert (Fr Datenupdate ber Netz; whrend Applikation luft)

Sektion [Configuration];-------------------------------------------------------; Interface; Description : Connected diagnosis interface; Default = EDICInterface=STD:OBD

WinKFPTUser's Guide

Page 41

Date: 20.10.04


4 STARTING WINKFPT

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

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

4.1 Calling Parameters of WinKFPT

The following calling parameters can be set in WinKFPT:

Parameter name Parameter value Description Default

-RUN - Starts WinKFPT immediately in Batchmode.

Example:winkfpt32 RUN

-

-BATCH= Path and name of a control file for Batchmode.

Example:winkfpt32 RUN BATCH=update_ek928

"\bin\winkfpt.ctl"

-INTERFACE= Defines the HW interface (e.g. ADS,EDIC) that is to be active followingstarting of WinKFPT.It can be altered at a later point in Dialogmode by means of the main menu option"HW Interface".

Example:winkfpt32 INTERFACE=STD:OBD

Setting in "EDIABAS.INI"

WinKFPTUser's Guide

Page 42

Date: 20.10.04


Parameter name Parameter value Description Default

-UNIT= Defines the unit (_, A, B, C, ....., Z) that isto be active following starting ofWinKFPT.It can be altered at a later point in Dialogmode by means of the main menu option"HW Interface".

Example:winkfpt32 UNIT=A

"_"

-WITH_MOSTFIREWALL= Relays the value to the PABDas the parameter"WITH_MOSTFIREWALL".

Example:winkfpt32 WITH_MOSTFIREWALL=ON

"OFF"

-TESTER_ID= Relays the value to the PABDas the parameter "TESTER_ID".

Example:winkfpt32 -TESTER_ID=FA

"F1"

-C Compiles an IPS file (PABD source file).CabdFormat=COM does not have to beset in WinKfpt.ini and coapi.ini.

Example:winkfpt32 C 16ek928

Table 4-1: Calling parameters of WinKFPT

WinKFPTUser's Guide

Page 43

Date: 20.10.04


4.1.1 Type Description of the Calling Parameters of WinKFPT

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

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

The parameters for setting an operating mode are:

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

-RUN starts WinKFPT in Batch mode

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

The following parameter is used for Batch mode only:

-BATCH

The general parameters for Batch and Dialog modes are:

-INTERFACE -UNIT -WITH_MOSTFIREWALL -TESTER_ID

WinKFPTUser's Guide

Page 44

Date: 20.10.04


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

Status display Description

ECU address The control unit address is only explicitly displayed if the standard description filesare used for programming the control unit in question.

No ECU address can be displayed for control units with "older" description files. Thefollowing text appears instead:PABD uses an internal address

This text is displayed:

following selection of the description files and entry of the ECU address in Expertmode (Dialog mode).

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

during flash programming of an ECU in Batch mode.

Integration position There are control units for multiple integration that belong to the same ECU familybut 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 bymeans of the ECU address, rather by means of meaningful texts that describe theintegration position of the control unit (e.g. Passenger seat, rear left).

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

These texts are displayed:

following selection of an integration position in Comfort mode (Dialog mode).

WinKFPTUser's Guide

Page 45

Date: 20.10.04



Vehicle identificationnumber

In the Comfort mode of Dialog mode, the vehicle identification number is displayedonly if an entry is made in the UIF (user info field) following flash programming.

The VIN is displayed:


during flash programming of an ECU in Batch mode (the vehicle identificationnumber from the control file for Batch mode is displayed).

ZB number The ZB number (assembly identification number) defines the program data set anddata 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 theconfiguration file COAPI.INI is displayed.



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).


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

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

Diagnosis protocol The default diagnosis protocol or the one selected is always displayed if the ECUfacilitates communication with at least 2 diagnosis protocols.

WinKFPTUser's Guide

Page 46

Date: 20.10.04



PABD Flash sequence description fileThe file is displayed:

following selection in Expert mode (Dialog mode).



P-SGBD Control unit description file for programmingThe file is displayed:

following selection in Expert mode (Dialog mode).



Progress bar Informs you in percentage terms of the progress of an automatic process that takessome 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 isACTIVATED or NOT ACTIVATED.The setting can be changed at any time by means of the main menu option"Configuration".

Table 4-1: Status displays of WinKFPT

WinKFPTUser's Guide

Page 47

Date: 20.10.04


4.3 Starting WinKFPT in Compile ModeThere is only one call that can be used to start WinKFPT in Compile mode:

winkfpt32 C

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

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

The following dialog window appears once WinKFPT has been started:

Fig. 4-1: Dialog window in Compile mode

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

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

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

WinKFPTUser's Guide

Page 48

Date: 20.10.04


Result display when compilation has been successful:

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

Result display when compilation has not been successful:

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

WinKFPT is exited when "OK" is clicked.

WinKFPTUser's Guide

Page 49

Date: 20.10.04


4.4 Starting WinKFPT in Batch Mode

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

Batch mode of WinKFPT can be activated in two ways:

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

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

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

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

WinKFPTUser's Guide

Page 50

Date: 20.10.04


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


Control file Path and name of the default control file or of the control file transferred as callingparameter (-BATCH=).

Status The status display informs the user about the current activity or about errorconditions in Batch mode.

The following status displays are possible:"not started""started""waiting for control file""reading in control file""programming active""waiting for end of programming""programming ended""no control file specified""report file cannot be opened""WinKFPT Batch mode error""Batch cannot be started. Programming in progress"

Errors Indicates the number of errors that occur during control unit communication orduring the evaluation of logistics data.

Aborts Indicates the number of errors that occur during the flash programming of ECUs; anerror leads to immediate aborting of programming.

Target interface Indicates the HW interface+unit that the corresponding WinKFPT instance accessesduring flash programming of an ECU.

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

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

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

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

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

WinKFPTUser's Guide

Page 51

Date: 20.10.04


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

The path and name of the control file can be specified when calling using the calling parameter BATCH=; 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,.There is no need to enter an extension for the control file. It is automatically assumed to be .CTL.

WinKFPTUser's Guide

Page 52

Date: 20.10.04


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

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

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

[FGNUMMER] The [FGNUMMER] (VIN) section has just one line that contains the vehicleidentification number.Format: VIN=Example: VIN=WBAAA00000AA00000

[ZBNUMMER] The [ZBNUMMER] (ZBNUMBER) section contains the various assemblyidentification numbers, each on a separate line.Format: ZBNxxxx=, where xxxx is a consecutive number that begins at0000, 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 numberis reached.

WinKFPTUser's Guide

Page 53

Date: 20.10.04


Section Contents

[SGADRESSE] The [SGADRESSE] (ECUADDRESS) section contains the various ECU addresses,each on a separate line.Format: SGADRxxxx=, where xxxx is a consecutive number thatbegins 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 eachassembly identification number entered.E.g.:[ZBNUMMER]ZBN0000=7515985

[SGADRESSE]SGADR0000=A2

[BATCH] The [BATCH] section contains one line with information relating to the ending ofBatch mode.Format: END=ON or END=OFF.

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

The purpose of the END=ON option is to enable WinKFPT to be ended in Batchmode by a calling external application that creates a control file that contains just thesection BATCH with the entry END=ON.Batch mode is ended immediately upon the control file being read in.If Batch mode was started automatically by means of the calling parameter RUN,WinKFPT is also ended.In this case, the FGNUMMER, ZBNUMMER and SGADRESSE sections (if present)are ignored.

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

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

WinKFPTUser's Guide

Page 54

Date: 20.10.04


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

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

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

MF_PABD This parameter specifies the PABD to be used for programming.Format: MF_PABD=Example: MF_PABD=21EK928.IPO

MF_PSGBD This parameter specifies the P-SGBD to be used for programming.Format: MF_PSGBD=Example: MF_PSGBD=21EK92.PRG

MF_SG_ADR The ECU address is entered as a HEXADECIMAL.Format: MF_SG_ADR=Example: MF_SG_ADR=12

MF_DATEN_DATEI This parameter defines the data file to be programmed. At least one NAABfile, one data file or one program file must be entered.Format: MF_DATEN_DATEI =Example: MF_DATEN_DATEI=Q7525491.0DA

MF_PROGRAMM_DATEI This parameter defines the program file to be programmed. At least oneNAAB file, one data file or one program file must be entered.Format: MF_PROGRAMM_DATEI =Example: MF_PROGRAMM_DATEI=7523523A.0PA

MF_NAAB_DATEI This parameter defines the NAAB file to be programmed. At least one NAABfile, one data file or one program file must be entered.Format: MF_PROGRAMM_DATEI =Example: MF_NAAB_DATEI=555111_555222.0ba

MF_DIAGNOSEPROTOKOLL This parameter specifies the diagnosis protocol to be used. This is optional.Format: MF_DIAGNOSEPROTOKOLL=Example: MF_DIAGNOSEPROTOKOLL=KWP2000*

WinKFPTUser's Guide

Page 55

Date: 20.10.04


MF_FG_NUMMER This parameter specifies the vehicle identification number. It is only required ifUIF writing is used for programming.Format: MF_FG_NUMMER=Example: MF_FG_NUMMER WBAAA00000AA00000

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

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

WinKFPTUser's Guide

Page 56

Date: 20.10.04


4.4.3 Starting a Programming Job in Batch ModeStarting the programming job:

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

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

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

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

Process logging:

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

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

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

WinKFPTUser's Guide

Page 57

Date: 20.10.04


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

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

End of a programming job:

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

WinKFPTUser's Guide

Page 58

Date: 20.10.04


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

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

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

WinKFPTUser's Guide

Page 59

Date: 20.10.04


4.4.5 Starting Several Instances in Batch Mode

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

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

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

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

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

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

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

WinKFPTUser's Guide

Page 60

Date: 20.10.04


4.5 Starting WinKFPT in Dialog ModeAll calling parameters except "-C" and "-RUN" may be used to start a WinKFPT instance in Dialogmode.

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

4.5.1 Starting Several Instances in Dialog ModeLike in Batch mode, it is theoretically possible to call and run up to 99 different WinKFPT instancessimultaneously in Dialog mode, too.

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

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

or

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

WinKFPTUser's Guide

Page 61

Date: 20.10.04


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

WinKFPTUser's Guide

Page 62

Date: 20.10.04


5 WINKFPT'S MAIN MENU

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

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

5.1 Display Menu

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

WinKFPTUser's Guide

Page 63

Date: 20.10.04


5.1.1 Display CABI.ERR

Displays the CABI.ERR file that contains the error messages created when an error occurs duringtranslation of a PABD (= IPS file).Close the display by clicking OK or by pressing "ESC" or Alt+F4.

5.1.2 Display ERROR.LOG

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

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

5.1.3 Display PABD Parameters

Displays the job and result parameters currently set for a PABD.Close the display by clicking OK or by pressing "ESC" or Alt+F4.

5.1.4 Display HW History

Displays the HW history of the current hardware number.


5.1.5 Display ZB History

Displays the ZB history of the current assembly identification number.


5.1.6 Display ZB Rules

Displays the ZB rule of the current assembly identification number.


WinKFPTUser's Guide

Page 64

Date: 20.10.04


5.1.7 Display API Trace File

Displays an API trace file present in the EDIABAS directory.


5.1.8 Display IFH Trace File

Displays an IFH trace file present in the EDIABAS directory.


5.1.9 Display Batch ModeSwitches from Dialog mode to Batch mode.

Batch mode is not yet started following this switching.

WinKFPTUser's Guide

Page 65

Date: 20.10.04


5.2 Import/Export MenuSelecting this main menu option opens up the following submenu:

Fig. 5-1: Submenu under the main menu option

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

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

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

The following file groups can be imported:

Import Files

Data sets / Program releases /NAAB files

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

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

WinKFPTUser's Guide

Page 66

Date: 20.10.04


P-SGBD *.PRG P-SGBD in compiled code

PABD*.IPS*.IPO

PABDs in source codePABDs in compiled code

Assembly line data

*.0DA*.0PA*.0BA*.PRG*.IPS*.IPO*.DAT*.DA2*.HWH*.HIS*.ATS*.ASD*.AS2*.GER*.BSU

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

Exported configuration -development data

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

Exported configuration - assemblyline data

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

Table 5-1: Import files

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

WinKFPTUser's Guide

Page 67

Date: 20.10.04


5.2.1.1 Importing an "Exported Configuration" of Assembly Line DataYou import an "exported configuration" of assembly line data by selecting the menu optionImport/Export Import Exported configuration - assembly line data.

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

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

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

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

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

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

WinKFPTUser's Guide

Page 68

Date: 20.10.04


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

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

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

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

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

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

The buttons have the following functions:

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

Replace and Import respectively(always active):

WinKFPTUser's Guide

Page 69

Date: 20.10.04


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

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

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

Winkfp Handbook v1.8 Eng

Documents

Transcript of Winkfp Handbook v1.8 Eng