Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
· Logistics files
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.
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.
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
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 2 of 10
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.
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
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 3 of 10
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.
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 4 of 10
· The file already exists in the target directory and has been
opened by an application.
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 5 of 10
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).
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 6 of 10
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.
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 7 of 10
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
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 8 of 10
Possible cause · A 2-digit, hexadecimal number has not been entered as the
ECU address.
Debugging · Enter a correct hexadecimal number.
Possible cause · The vehicle identification number was either not a 7-digit
number or not alphanumeric.
Debugging · Enter a correct vehicle identification number.
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 9 of 10
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020
Error Handling in WinKFPT Page 10 of 10
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.
file:///C:/Users/sgtma/AppData/Local/Temp/~hh178E.htm 2/4/2020