Glossary
CABD
Coding sequence description file
CABI
Coding sequence interpreter
COAPI
Coding application interface
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.
DAF
Flash data image file
Expert mode
Programming after selecting the PABD,
P-SGBD, data file and/or program file.
HIS
(Assembly) History file
IFH
Interface handler
INPA
Interpreter for test sequences
Interface
Hardware unit for communication with control units, e.g. EDIC, ADS, MOST
IPO
Extension of a sequence description file in object format
IPS
Extension of a sequence description file in source format
NAAB
Boot update description file. This is a data file that is flashed to the program area of an ECU and contains the program for boot sector update and the boot sector itself.
PABD
Flash sequence description file
PAF
Flash program image file
P-SGBD
Control unit description file for programming.
SGBD
ECU description file
UIF
User info field
Unit
Subunits of interfaces designated _, A, B, C, etc. if several interfaces of one type are installed in the same computer.
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.
ZUSB number
ZB number
Assembly identification number
............................................................
Error Handling in WinKFPT
The process of flash programming an ECU with WinKFPT is very complex and depends on trouble-free interaction of the following components:
· Hardware connection – Test computer Ö Diagnosis HW interface Ö ECU
· Software connection – WinKFPT Ö EDIABAS Ö Diagnose interface driver Ö ECU program
· Configuration of WinKFPT and COAPI
· Description files PABD and P-SGBD
· Logistics files
· Programming data files (PAF, DAF, etc.)
Each component contains a multitude of potential errors that must be trapped by WinKFPT 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.
· Displaying errors in WinKFPT functions without COAPI calls:
Display of informative error, diagnosis and info texts in appropriate message boxes.
The texts are loaded dynamically from the text file "winkfpt.txt". It is possible to improve on the explanatory power/correctness of the texts at any time without making changes to WinKFPT.
· Displaying errors in WinKFPT functions with COAPI calls:
Each time an error occurs when a COAPI function is called, an error dialog is displayed. The top text box in this dialog contains a text that informs you of which active WinKFPT function the error has occurred in. The list box below this contains a detailed list of errors traced through all the COAPI call levels run through.
This error list should not be viewed as a list of different errors, rather as a breakdown of just a single error, with the respective information that has been able to be established from the relevant COAPI call levels.
The COAPI error texts are loaded dynamically from the text file "coapierr.txt".
................................................................
Displaying 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.
![[Image: 2017-02-08_10-08-28_zpsvpp3u1qm.jpg]]()
Fig.: Error display window in WinKFPT
In the example above, you can see that initialization of the COAPI by WinKFPT has failed.
The list of errors from the respective COAPI call levels clearly shows the user which of the 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.DA” is present in the <root>\DATA\gdaten directory, or whether or not he has read rights to it.
............................................................
Errors When Starting WinKFPT
Error
COAPI errors 1020, 3017, WinKFPT error 1
Time of occurrence
· When starting WinKFPT.
Possible cause
· A logistics file is missing in the ../data/gdaten directory. The 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.
Error
COAPI errors 4211, 4206, 1040, 3017, WinKFPT error 1
Time of occurrence
· When starting WinKFPT.
Possible cause
· The ../data/gdaten directory contains a faulty and therefore unconvertible logistics file. The error dialog (in particular error 4206) tells you which file it is and in which line the error occurred.
Debugging
· Import an up-to-date assembly line data set with correct description files.
· Repair the faulty logistics file in the ../data/gdaten directory by hand.
Error
WinKFPT error 300
Time of occurrence
· When starting WinKFPT.
Possible causes
· The interface is already being used by a different program or possibly by a different instance of WinKFPT.
· The default interface is not correctly set up in Ediabas.
Debugging
· Close the other application that is using the interface. (Application may only be able to be seen in the task manager.)
· Use a different application (e.g. TEOF in the Ediabas\bin directory) to check whether the interface actually functions. If not: check Ediabas and/or the interface driver.
.....................................................
Errors When Importing Assembly Line Data
Error
ECU directory is not displayed
Time of occurrence
· When selecting an assembly identification number in Comfort mode.
Possible cause
· Imported ECU directory does not contain any PABD/P-SGBD description files.
Debugging
· Import an assembly line data set with description files.
Error
WinKFPT error 11
Time of occurrence
· When importing a single description file.
Possible causes
· The description file could not be copied.
· The file already exists in the target directory and is write-protected.
· The file already exists in the target directory and has been opened by an application.
· The source file has no read rights.
· No write rights in the target directory.
Debugging
Depending on the cause:
· Cancel write protection.
· Close the application that has opened the file.
· Check and adapt the file rights.
Error
WinKFPT error 111
Time of occurrence
· When importing an assembly line data set.
Possible cause
· The assembly line data set does not contain a file of type <EcuFamilyname>.dat
Debugging
· Fetch the correct assembly line data set (e.g. from Darwin).
..........................................................................................
Errors When Entering Flash Data
Error
COAPI errors 1065, 1000, WinKFPT error 106
Time of occurrence
· When loading the suggested configuration after activating the <Expert mode> button.
· In Comfort mode when activating the [Done] button after selecting a ZB number and integration position.
Possible cause
· The PABD from the configuration does not exist.
Debugging
· Copy or import the PABD to the relevant Ediabas directory.
Error
COAPI error 2000, WinKFPT error 106
Time of occurrence
· When loading the suggested configuration after activating the <Expert mode> button.
· In Comfort mode when activating the [Done] button after selecting a ZB number and integration position.
Possible cause
· The SGBD from the configuration does not exist.
Debugging
· Copy or import the SGBD to the relevant Ediabas directory.
Error
COAPI error 3000
Time of occurrence
· In Comfort mode after entering a ZB number by hand.
Possible cause
· This is no (correct) DAT file that contains the ZB number.
Debugging
· Import the assembly line data set for the ECU family to which the ZB number belongs.
Error
WinKFPT errors 500 to 503
Time of occurrence
· When selecting the data file in Expert mode.
· When selecting the program file in Expert mode.
Possible causes
· The wrong ECU has been connected. The ECU identifier in the data/program file selected does not match up with the identifier of the ECU connected.
· The wrong data/program file has been selected.
Debugging
· Determine whether the correct ECU is connected. If necessary, connect the correct ECU.
· Determine whether the correct data/program file has been selected. If necessary, select the correct file.
Error
COAPI error 2020
Time of occurrence
· When selecting the data file in Expert mode.
· When selecting the program file in Expert mode.
Possible cause
· An incorrect ECU address has been entered:
· The control unit is not connected or communication is disrupted.
Debugging
· Enter the correct ECU address.
· Connect the ECU. Check whether communication is actually possible.
Error
COAPI error 1020
Time of occurrence
· When activating the [Program] button in Comfort mode.
Possible cause
· An ECU family-specific logistics file (HWH or HIS) is not present. The error dialog tells you which file it is.
Debugging
· Fetch the file by importing the assembly line data
· or copy the file to the data directory by hand.
Error
COAPI errors 4209 or 4211, 4206, 1040, 3000
Time of occurrence
· When activating the [Program] button in Comfort mode.
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.
Error
COAPI errors 4204, 1040
Time of occurrence
· When activating the [Program] button in Comfort mode.
Possible cause
· The file to be flashed does not exist. The error dialog (in particular error 4204) tells you which file it is.
Debugging
· Fetch the file by importing the assembly line data
· or copy the file to the data directory by hand.
Error
COAPI errors 4220 or 4209, 4221, 1040,
Time of occurrence
· When selecting a program or data file in Expert mode.
· When activating the [Program] button in Comfort mode.
Possible cause
· The file to be flashed is faulty. The error dialog (in particular error 4221) tells you which file it is and in which line the error occurred.
Debugging
· Fetch an intact file by importing the assembly line data
· or eliminate the error in the file by hand.
Error
WinKFPT error 100
Time of occurrence
· In Expert mode after selecting PABD and SGBD, when activating the [Done] button.
Possible cause
· The SGBD demands an external ECU address.
Debugging
· Enter an ECU address.
Error
WinKFPT error 102 or 103
Time of occurrence
· In Expert mode when entering an ECU address.
Possible cause
· A 2-digit, hexadecimal number has not been entered as the ECU address.
Debugging
· Enter a correct hexadecimal number.
Error
WinKFPT error 107
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.
Error
WinKFPT error 108
Time of occurrence
· When entering a ZB number in Comfort mode.
Possible cause
· The ZB number was not a 7-digit number.
Debugging
· Enter a 7-digit ZB number.
....................................................................
Errors During Data Programming
Error
CAPI error 2020 or 2021
Time of occurrence
· When starting programming in both operating modes..
Possible causes
· The ECU is not connected.
· The HW interface is not fully installed.
· The interface is not connected.
Debugging
· Determine whether the ECU is connected.
· Re-install the interface.
· Determine whether the interface hardware is connected.
Error
COAPI error 1060
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.
Possible causes
· The wrong hardware interface has been selected.
· The interface is not fully installed.
· The interface is not connected.
· The ECU is not connected.
Debugging
· Determine whether the correct HW interface is displayed as status information. If necessary, select the correct HW interface under menu option Communication à HW interface.
· Re-install the interface.
· Determine whether the interface hardware is connected.
· Determine whether the ECU is connected.
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.
![[Image: 2017-02-08_10-08-28_zpsvpp3u1qm.jpg]](http://i1174.photobucket.com/albums/r612/Wild_Joke/2017-02-08_10-08-28_zpsvpp3u1qm.jpg)
![[Image: DME%20FAILED%20PROGRAMMING_2017-02-16_16...wclxxd.jpg]](http://i1174.photobucket.com/albums/r612/Wild_Joke/DME%20FAILED%20PROGRAMMING_2017-02-16_16-55-22_zpsdqwclxxd.jpg)