5 WinKFPT's Main Menu

WinKFPT's Main Menu Page 1 of 43
WinKFPT's Main Menu

The top menu bar offers the user the following main menu options:
· Display
· Import/Export
· Communication
· Configuration
· Help
· End
When you select a main menu option, a pull-down menu containing one or more submenu options
appears via which you can call the various menu options.
File Menu
You use this menu to exit WinKFPT:
Exit
You exit WinKFPT by selecting the menu option File / Exit.
This command terminates the program.
If you have activated Expert mode at least once while using WinKFPT, you have the option before
exiting WinKFPT of saving the current settings you have made in Expert mode so that you can call them
up again the next time you start the program (see “ Configuration for Expert Mode”).
As WinKFPT is terminated, the last window size and window position of the application are saved as
the entry WindowPosition in the WINKFPT.INI file.
file:///C:/Users/sgtma/AppData/Local/Temp/~hh7A5C.htm 2/4/2020
The next time WinKFPT is launched, the program is started with the same window size and position
(see “ Configuration in WINKFPT.INI“).
Display Menu
The main menu option Display contains the following submenu options that be used to switch certain
functions ON or OFF and display error and trace files:
· CABI.ERR
· ERROR.LOG
· PABD Parameters
· HW-History
· ZB History
· ZB Rule
· API Trace File
· IFH-Trace File
· Batch Mode
Display CABI.ERR
Displays the CABI.ERR file that contains the error messages created when an error occurs during
translation of a PABD (= IPS file).
Close the display by clicking OK or by pressing "ESC" or Alt+F4.
Display ERROR.LOG
Displays the ERROR_INTERFACE_UNIT.LOG error file that contains the error messages from the
COAPI and CDH functions.
Display PABD-Parameters
Displays the job and result parameters currently set for a PABD.
Display HW-History
Displays the HW history of the current hardware number.
Display ZB History
Displays the ZB history of the current hardware number.
Display ZB Rule
Displays the ZB rule of the current assembly identification number.
Display API-Trace File
Displays an API trace file present in the EDIABAS directory.
Display IFH-Trace File
Displays an IFH trace file present in the EDIABAS directory.
Display Batch Mode

Switches from Dialog mode to Batch mode.
Batch mode is not yet started following this switching.
Import/Export Menu
Selecting this main menu option opens up the following submenu:
Fig.: Submenu under the main menu option <Import/Export>
Import Submenu
This submenu option in turn activates a pull-down menu that contains the following options:
Fig.: Pull-down menu under the submenu option <Import>
The Import menu can be used to select all the files necessary for flash programming. They can be
selected from any drive or directory. The files selected are then automatically distributed to the
appropriate directories once their adoption has been confirmed.
The following file groups can be imported:
Import Files
*.0DA Data set files for data
*.DAF Data exchange files

Data sets / Program releases / BSU
NAAB-files *.0PA Data set files for program
*.PAF Program exchange files
*.0BA Data set files for NAAB
*.BAF NAAB exchange files
P-SGBD in compiled code

P-SGBD *.PRG
*.IPS PABDs in source code
PABD *.IPO PABDs in compiled code
*.0DA Data set files for data

*.0PA
*.0BA Data set files for program
*.PRG
*.IPS
Data set files for NAAB
*.IPO
*.DAT
*.DA2 P-SGBD in compiled code
*.HWH
*.HIS PABDs in source code
*.ATS
*.ASD PABDs in compiled code
*.AS2 ECU logistics files

*.GER
*.BSU
Assignment of ECU members to names of logistics files
Assembly line data
History of compatible hardware numbers of an ECU family
Compatible assembly identification numbers of an ECU family
Logistics file
Logistics file
Authentication code files
ECU member integration position
Logistics file for checking the possibility of a BSU (boot sector

update)
Files like from import of assembly line data +
Exported configuration – development files and/or tool-relevant files if desired

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

Exported configuration -
assembly line data
Table: Import files
The importing of exported configuration development data‚ data sets, program data sets, /BSU NAAB
files, P-SGBDs and PABDs is assigned to "Expert mode".
The import of exported configuration assembly line data and assembly line data is assigned to "Comfort
mode".
Importing an "Exported Configuration" of Assembly Line Data
You import an "exported configuration" of assembly line data by selecting the menu option
Import/Export à Import à Exported configuration - assembly line data.
The following dialog window is then displayed to enable you to select the import directory:
Fig.: Selecting the import directory of a configuration of assembly line data
The start directory highlighted in the import dialog window for the first import in a WinKFPT session is
"My Computer". For each subsequent import, the import directory highlighted is the one that was
selected the last time.
A configuration of exported assembly line data can only be imported from directories that contain the
export log file BACKUPEXPORT.LOG. The contents of the log file are not checked.
If the directory selected does not contain this log file, an error message is displayed and the dialog
terminated.
It is only possible to import an entire exported configuration, i.e. you are not able to select parts from the
exported WDPs for import.
Before importing is performed, a check is run to determine whether or not one or more of the WDPs to
be imported is/are already present in the "<root>\Data" directory.
A dialog window appears that contains a list of the WDPs already in this directory and the function
buttons "Replace", "Merge" and "Cancel".
Fig.: WDP conflict when importing a configuration of assembly line data
If the list of WDPs is empty, the list window and its corresponding headline is not shown. The "Merge"
button is not shown too because has not function and the "Replace" button is changed by the
"Import" button
Furthermore, you can also specify whether you want to import with or without tool-relevant data (INI
files) (default is "Import - Tool relevant data" not activated).
Tool-relevant files from the import directory always overwrite those files in the working directory that
have the same name.
KMM files are exported for archiving purposes only and are therefore never reimported.
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):
all the files from the import directory selected are copied to the working directory; files that
are 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 the
working directory.
The following COMMON files are given 'special treatment' that is identical for the two import modes
Replace and Merge:
KFCONFXX.DA2, HWNR.DA2 and SWTCONFx.DAT:
In the file in the working directory, all lines that relate to the ECU family of the assembly line data set to
be imported are overwritten if they are already present or appended if they are not already present.
Special treatment, which is only valid for the import mode Merge, is given to the following ECU-
specific file:
<ECUFAMILY>.DAT:
All lines from the file in the import directory that do not yet exist in the file in the working directory are
appended to the DAT file in the working directory. This operation is only executed for lines that begin
with a number, i.e. not for lines that in particular begin with "$" or ";".
Importing an "Exported Configuration" of Development Data
You import an "exported configuration" of development data by selecting the menu option
Import/Export à Import à Exported configuration - development data.
Fig.: Selecting the import directory of a configuration of development data
A configuration of exported development data can only be imported from directories that contain the
export log file CONFIGEXPORT.LOG. The contents of the log file are not checked.
If the directory selected does not contain this log file, an error message is displayed and the dialog
terminated.
It is only possible to import an entire exported configuration, i.e. you are not able to select parts from the
exported WDPs for import.
be imported is/are already present in the "<root>\Data" directory.
A dialog window appears that contains a list of the WDPs already in this directory and the function
buttons "Replace", "Merge" and "Cancel".
Fig.: WDP conflict when importing a configuration of development data
If the list of WDPs is empty, the list window and its corresponding headline is not shown. The "Merge"
button is not shown too because has not function and the "Replace" button is changed by the
"Import" button
A separate selection element enables you to active or deactivate importing of the development files, i.e.
files from the
<basedirectory>\<configurationname>\Daten\Entwicklung\Data\Develop
<basedirectory>\<configurationname>\Daten\Entwicklung\Sgdat
<basedirectory>\<configurationname>\Daten\Entwicklung\Ecu
directories (default is "Import - Development files" activated).
Note:
The files from the export directory
<basedirectory>\<configurationname>\Daten\Entwicklung\Data\Gdaten
are not reimported.
Furthermore, you can also specify whether you want to import with or without tool-relevant data (INI
files) (default is "Import - Tool relevant data" not activated).
Development files and tool-relevant files from the import directory always overwrite those files in the
working directory that have the same name.
· Cancel (always active):
· Replace and Import respectively(always active):
· Merge (only active when the WDP list is not empty):
only those files that have a more recent date or are not yet preset are copied from the import
directory to the working directory.
Replace and Merge:
specific file:
<ECUFAMILY>.DAT:
Importing Assembly Line Data
You import assembly line data by selecting the menu option Import/Export à Import à Assembly
line data.
Fig.: Selecting the import directory for assembly line data sets
The directory selected contains either an actual assembly line data set or one or more subdirectories that
contain assembly line data sets.
In the example above, you could select either "G:\Trans\EK9282" or "G:\Trans".
WinKFPT automatically finds all data sets immediately in the selected directory or one directory level
lower and executes the import for each data set.
If in the example above you were to select "G:\Trans\EK9282" as the import directory, only the data set
"EK928" would be imported; if you selected "G:\Trans", data sets "EK9282", "EK9294B" etc. would be
imported.
be imported is/are already present in the "<root>\NFS\Data" directory.
A dialog window that contains a list of the WDPs already in this directory and the function buttons
"Replace", "Merge" and "Cancel" appears only when this is the case.
Fig.: WDP conflict when importing assembly line data sets
· Cancel:
· Replace:
· Merge:
only those files that have a more recent date or are not yet preset are copied from the import
directory to the working directory.
Replace and Merge:
specific file:
<ECUFAMILY>.DAT:
The files are distributed to the following directories when assembly line data is imported:
Files Target directory

*.PRG <ediabas>\ecu
*.IPS, *.IPO <root>\SGDAT\
*.ASD, *.AS2, INFO.GER, HWNR.DA2, KFCONF.DA2, <root>\DATA\GDATEN

HWNR.DAT, NPV.DAT, KFCONF.DAT , HISTORIE.BSU,
SWTCONFx.DAT
<SGFAMILIE>.DAT, *.0DA, *.0PA, *.0BA, *.HWH, *.HIS, <root>\DATA\<ecufam>

*.ATS
Table: Distribution of the files to directories when assembly line data is imported
Importing NAAB, Program and Data Data Sets
You import NAAB files, program data sets and data data sets by selecting the menu option
Import/Export à Import à Data / Program / BSU NAAB files.
By importing NAAB files, program data sets and data data sets, you select the files you want to use for
flash programming in Expert mode and automatically copy them to the appropriate directory.
Fig.: Importing data sets/program data sets/BSU NAAB files
*.BAF, *.0BA, *.PAF, *.0PA, *.DAF and *.0DA files are displayed by default.
To import the files:
· Select the directory with the files you want from the list next to "Search in".
· Select the file(s) to be imported.
You can select a single file from the list simply by clicking it with the left mouse button.
You can select several files to import by holding down the <Ctrl> key
and clicking with the left mouse button.
You can select all the files displayed by pressing <Ctrl> + <A>.
· Then click "Import".
The files you have selected are copied to \<root>\data\develop.
Files that already exist can only be overwritten once a warning prompt has been acknowledged in the
positive.
Fig.: Overwriting files during NAAB, data and program file importing
Bei Auswahl von mehreren Dateien wird der Status des Kopiervorgangs als Fortschrittsbalken (0 -
100%) angezeigt.
If you have selected more than one file, the status of the copying procedure is indicated by a progress
bar (0 - 100 %).
After being imported, files are displayed in the selection list of the "Loading a data set - NAAB file",
"Loading a data set - program file" or "Loading a data set - data file" function in Expert mode (see
Function: Loading a Data Set – Program File“ or “ Function: Loading a Data Set – Data File“).
Importing Control Unit Description Files for Programming (P-SGBDs)
You import P-SGBDs by selecting the menu option Import/Export à Import à P-SGBD.
By importing P-SGBDs, you select the control unit description files you want to use for flash
programming in Expert mode and automatically copy them to the appropriate directory.
Fig.: Importing P-SGBDs
Only *.PRG files are displayed (default setting).
· Select the file to be imported.
The files you have selected are copied to the P-SGBD directory "<ediabas>\ecu".
positive.
Fig. 5-12: Overwriting files during P-SGBD importing
bar (0 - 100 %).
After being imported, files are displayed in the selection list of the "Load P-SGBD" function in Expert
mode (see “ Function: Loading a P-SGBD“).
Importing Flash Sequence Description Files (PABDs)
You import PABDs by selecting the menu option Import/Export à Import à PABD.
By importing PABDs, you select the flash sequence description files you want to use for flash
programming in Expert mode and automatically copy them to the appropriate directory.
Fig.: Importing PABDs
Only *.IPS and *.IPO files are displayed (default setting).
· Select the file to be imported.
The files you have selected are copied to "\<root>\sgdat".
positive.
Fig.: Overwriting files during PABD importing
bar (0 - 100 %).
After being imported, files are displayed in the selection list of the "Load PABD" function in Expert
mode (see “ Function: Loading a PABD“).
Export Submenu
This submenu option in turn activates a pull-down menu that contains the following options:
Fig.: Pull-down menu under the submenu option <Export>
Exporting a "Configuration" of Assembly Line Data
You export a "configuration" of assembly line data by selecting the menu option Import/Export à
Export à Configuration - assembly line data.
When you select this menu option, the following dialog window appears:
Fig.: Dialog window for exporting a configuration of assembly line data
This dialog window displays the export base directory currently set, e.g. <root>\NFS-Backup", and two
input fields ("Type series" and "I-Level") for the names of the two subdirectories.
A list box displays all the valid assembly line data sets (ECU families) available for selection for export.
You can select either no data set at all, one, several or all of the assembly line data sets.
If no valid assembly line data exists, the list box is empty and all you can do is export the tool-relevant
data by activating the corresponding check box.
With each export, the KMM data from the working directory "<root>\KMM\" is exported implicitly,
provided a KMM directory exists.
Before the actual copying process begins, the data to be exported is compared with the corresponding
data last exported and located in the highest-order index directory.
Excluded from comparison are the COMMON files because those to be exported cannot as a rule be
identical with those previously exported.
This basically results in the following two sequences for the export of assembly line data:
1. No new directories are created, i.e. the index directory is not increased. This is the case if the files to
be exported, either all or just some of them, are not yet present in the highest-order index
directory, and if all or some of the files present are identical with those to be exported.
All files are deleted from their respective export directory before copying begins.
2. New directories are created, i.e. the index directory is increased automatically. This is the case if one
and just one file to be exported is not identical with the corresponding file in the highest-order
index directory.
Every export of assembly line data is documented in the export log file "BACKUPEXPORT.LOG" in
the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\ directory.
In the event of repeated export to the same directory (<root>\<NFS-Backup>\<typeseries>\<I-

Level>\<index>\), the relevant information to be stored is in each case appended to the log file that
already exists.
The following pieces of information are entered in a log file for each export procedure:
· Date (format: dd.mm.yyyy)
· Export base directory
· Type series
· I-Level
· Index
· With/Without development files
· With/Without tool-relevant data
· ECU family
· Separating line
Directory Structure for Exporting Assembly Line Data
Fig.: Structure of the target directories for exporting assembly line data
Filing of the Files When Exporting Assembly Line Data
· Export WDPs (if one or more selected)
Flash data, logistics data: The files *.0PA, *.0DA, *.0BA <ECUFAM>.DAT,
<ECUFAM>.HIS, <ECUFAM>.HWH and <ECUFAM>.ATS are copied from the <ecufam>
directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam>
directory.
COMMON files: COMMON files SWTCONFX.DAT, HISTORIE.BSU, SGIDC.AS2,

SGIDD.AS2 and INFO.GER are copied from the <root>\Data\Gdaten directory to the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory. The
relevant parts of the HWNR.DA2, KFCONFXX.DA2 and SWTCONFx.DAT files are
determined and only these parts are copied to the <root>\NFS-Backup\<typeseries>\<I-
Level>\<index>\daten\<ecufam> directory.
The file name of the COMMON file is adopted unchanged.
PABD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from <root>\Sgdat to the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
FABD: The name of the description file that belongs to the WDP is determined from the
SWTCONFx.DAT file and copied from <root>\Sgdat to the <root>\<NFS-
Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
P-SGBD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from EDIABAS\ECU to the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
SWT-SGBD: The name of the description file that belongs to the WDP is determined from
the SWTCONFx.DAT file and copied from EDIABAS\ECU to the <root>\<NFS-
Backup>\<typeseries>\<I-Level>\<index>\daten\<ecufam> directory.
· Export KMMs (always if present)
Copying of all the files in the <root>\kmmdat\<typeseries>\ directory to the <root>\<NFS-

Backup>\<typeseries>\<I-Level>\<Index>\kmm\ directory.
· Export tool-relevant data (optional)
Copying of all the files with the extension *.INI from the <root>\NFS\bin\ directory to the
<root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\bin\ directory.
Copying of all the files with the extensions *.INI and *.DAT from the <root>\cfgdat
directory to the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\cfgdat\ directory.
Copying of all the files with the extension *.INI from the <root>\EDIABAS\bin\ directory to
the <root>\<NFS-Backup>\<typeseries>\<I-Level>\<Index>\EDIABAS\bin\ directory.
Exporting a "Configuration" of Development Data
You export a "configuration" of development data by selecting the menu option Import/Export à
Export à Configuration - development data.
When you select this menu option, the following dialog window appears:
Fig. 5-18: Dialog window for exporting a configuration of development data
This dialog window displays the export base directory currently set, e.g. "<root>\Diagprog", and one
input field ("Configuration name") for the name of the subdirectory.
A list box displays all the valid assembly line data sets (ECU families) available for selection for export.
You can select either no data set at all, one, several or all of the assembly line data sets.
If no valid assembly line data exists, the list box is empty and all you can do is export the development
files and/or tool-relevant data by activating the corresponding check box(es).
All files selected for export are copied.
If the files are to be exported to a directory ("Configuration name") that already exists, the following
prompt is displayed:
Fig.: Prompt asking whether development data should be overwritten during export
If you click "Yes", all the files in the existing directories are deleted first before exporting is conducted.
Every export of development data is documented in the export log file "CONFIGEXPORT.LOG" in the
<root>\Diagprog\<configurationname>\ directory.
In the event of repeated export to the same directory (<root>\Diagprog \<configurationname>\), the
relevant information to be stored is in each case appended to the log file that already exists.
The following pieces of information are entered in a log file for each export procedure:
· Date (format: dd.mm.yyyy)
· Export base directory
· Configuration name
· With/Without development files
· With/Without tool-relevant data
· ECU family
· Separating line
Directory Structure for Exporting Development Data
Fig.: Structure of the target directories for exporting development data
Filing of the Files When Exporting Development Data
· Export development files (if released for export)
Flash data: The files *.0PA, *.0DA, *.0BA, *.PAF, *.DAF and *.BAF are copied from the
NFS\Data\Develop directory to the
<root>\Diagprog\<configurationname>\Daten\Entwicklung\Develop directory.
COMMON files: COMMON files SWTCONFX.DAT, HISTORIE.BSU, SGIDC.AS2,

SGIDD.AS2, HWNR.DA2, INFO.GER, KFCONFXX.DA2 and SWTCONFx.DAT are copied
from the NFS\Data\Gdaten directory to the

<root>\Diagprog\<configurationname>\Daten\Entwicklung\Gdaten directory.
P-SGBDs: All *.PRG files are copied from the EDIABAS\ECU directory
to the <root>\Diagprog\<configurationname>\Daten\Entwicklung\Ecu directory.
PABDs: All *.IPS and *.IPO files are copied from the NFS\Sgdat directory to the
<root>\Diagprog\<configurationname>\Daten\Entwicklung\Sgdat directory.
· Export WDPs (if one or more selected)
Flash data, logistics data: The files *.0PA, *.0DA, *.0BA <ECUFAM>.DAT,
<ECUFAM>.HIS, <ECUFAM>.HWH and <ECUFAM>.ATS are copied from the <ecufam>
directory to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory.
COMMON files: COMMON files SWTCONFx.DAT, HISTORIE.BSU, SGIDC.AS2,

SGIDD.AS2 and INFO.GER are copied from the NFS\Data\Gdaten directory to the
<root>\Diagprog\<configurationname>\Daten\<ecufam> directory. The relevant parts of the
HWNR.DA2, KFCONFXX.DA2, STWCONFx.DAT files are determined and only these parts
are copied to the <root>\Diagprog\<configurationname>\Daten\<ecufam> directory. The file
name of the COMMON file is adopted unchanged.
PABD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from NFS\Sgdat to the
<root>\Diagprog\<configurationname>\Daten\<ecufam> directory.
FABD: The name of the description file that belongs to the WDP is determined from the
SWTCONFx.DAT file and copied from NFS\Sgdat to the
P-SGBD: The name of the description file that belongs to the WDP is determined from the
KFCONFXX.DA2 and SWTCONFx.DAT file and copied from EDIABAS\ECU to the
SWT-SGBD: The name of the description file that belongs to the WDP is determined from
the SWTCONFx.DAT file and copied from EDIABAS\ECU to the
· Export tool-relevant data (optional)
Copying of all the files with the extension *.INI from the <root>\bin\ directory to the
<root>\Diagprog\<configurationname>\NFS\bin\ directory.
Copying of all the files with the extensions *.INI and *.DAT from the <root>\cfgdat
directory to the <root>\Diagprog\<configurationname>\NFS\cfgdat\ directory.
Copying of all the files with the extension *.INI from the <root>\EDIABAS\bin\ directory to
the <root>\Diagprog\<configurationname>\EDIABAS\bin\ directory.
Deleting Assembly Line Data
You delete assembly line data by selecting the menu option Import/Export à Delete - assembly line
data.
If there is no assembly line data present, the following message is displayed:
Fig.: Deleting assembly line data; message if no assembly line data is present
In this case, it is also not possible to conduct flash programming of ECUs in Comfort mode. You would
first have to import assembly line data to enable flash programming.
If valid assembly line data does exist, the following dialog window is opened:
Fig.: Dialog window for deleting assembly line data
A list box displays all the valid assembly line data sets (ECU families) available for selection for
deletion. You can select either no data set at all, one, several or all of the assembly line data sets.
The directories of the assembly line data selected are completely deleted during the deletion procedure.
The associated description files (SGBD/PABD) are likewise deleted, but only if they occur no more than
once in "KFCONFXX.DA2" or “SWTCONFx.DAT”, i.e. only if they are not used by one or more other
ECU families at the same time.
By clicking the function button "Remove", you delete the selected WDPs from the list box and remove
the corresponding entries from the COMMON files "KFCONFXX.DA2", “SWTCONFx.DAT” and
"HWNR.DA2".
The following prompt appears before deletion is started:
Fig.: Deleting assembly line data; prompt displayed on clicking "Remove"
If you click the function button "Remove all", all WDPs are selected and deleted, and the COMMON
files "KFCONVXX.DA2",SWTCONFx.DAT and "hwnr.da2" are completely emptied with the
exception of their headers, i.e. including all "dead" entries for which no WDPs exist.
The following prompt appears before deletion is started:
Fig.: Deleting assembly line data; prompt displayed on clicking "Remove all"
If you click "Yes", deletion is started and the dialog window is closed once deletion has been
completed.
If you click "No", the prompt disappears from the screen and the dialog window remains open.
If you click the function button "Cancel", the dialog window is closed; active deletion procedures are
not interrupted.
Communication Menu
This menu can be used to set the following parameters for communication between WinKFPT and
control units:
· Hardware interface
· Diagnosis protocol
The menu option "HW interface" enables you to switch dynamically between HW interfaces (EDIC,
ADS, etc.).
The "HW interface" menu option is only active if HW interfaces are entered in the configuration file
WINKFPT.INI (see “ Configuration in WINKFPT.INI”).
The menu option "Diagnosis protocol" enables you to choose dynamically between the diagnosis
protocols that are supported by a selected control unit (BMW-Fast, KWP2000, etc.).
The "Diagnosis protocol" menu option is only active if a selected control unit supports more than one
diagnosis protocol.
A control unit is selected by selecting an integration position (Comfort Mode) or by selecting a PABD
and P-SGBD (Expert Mode).
Selecting (Choosing) a HW Interface
You choose a HW interface by selecting the menu option Communication à HW interface.
Fig.: Selection dialog for HW interface
The "HW interface" menu option is only active if HW interfaces are entered in the configuration file
WINKFPT.INI.
All HW interface entries from WINKFPT.INI (see “ Configuration in WINKFPT.INI”) are presented in a
list for selection.
You must select a unit identifier (_, A, B, C, D, E) for each HW interface.
The HW interface unit is required by EDIABAS to enable it to distinguish between interfaces if several
HW interfaces of the same type are integrated (installed) in one computer.
To choose a HW interface:
· Choose a HW interface from the "HW interface" list.
· Select the unit for the HW interface.
If only one interface of this type is integrated in the computer, you must select "_" (= default).
· Then click "OK".
If WinKFPT is able to activate the HW interface chosen, the interface is displayed constantly in the
"HW interface" box as status information. Otherwise, error message 304 (which you have to
acknowledge) appears and the previous setting remains active.
Fig.: Error message displayed when an impermissible choice of HW interface is made
The same error occurs if, for example, the HW interface chosen is not installed as hardware or software.
If a different instance of WinKFPT has already accessed the same HW interface+unit, the following
error message appears:
Fig.: Error message when the same HW interface+unit is accessed in Dialog mode
When WinKFPT is started, the HW interface defined in "EDIABAS.INI" is activated and displayed by
default (see “ Configuration in EDIABAS.INI”).
You can, however, select a different setting straight away when starting a further WinKFPT instance
with the aid of the calling parameters -INTERFACE=<HW interface> and -UNIT=<Unit identifier>.
Selecting (Choosing) a Diagnosis Protocol

You choose a diagnosis protocol by selecting the menu option Communication à Diagnosis protocol.
Fig.: Dialog box for selecting a diagnosis protocol
The "Diagnosis protocol" menu option is only active if a selected control unit supports more than one
diagnosis protocol.
A control unit is selected by selecting an integration position (Comfort mode) or by selecting a PABD
and P-SGBD (Expert mode).
Once you have chosen a control unit, WinKFPT automatically tries to call the job
"DIAGNOSEPROTOKOLL_LESEN" from the corresponding P-SGBD.
If the job is present, the diagnosis protocols specified in it are displayed in a list for selection.
If you do not make an explicit selection, the first diagnosis protocol from the list is activated by default.
To choose a diagnosis protocol:
· Choose a diagnosis protocol from the "Diagnosis protocol" list.
· Then click "OK".
The diagnosis protocol activated is displayed in the "Diagnosis protocol" box a status information.
A selected diagnosis protocol is set internally by means of the P-SGBD job

"DIAGNOSEPROTOKOLL_SETZEN".
Configuration Menu
When you select this menu, the following configuration dialog window is opened.
Fig. 5-29: Configuration dialog window
The settings correspond to the following INI parameters:
Dialog text Ini file entry Description

Sprache / Language SPRACHE The entry defines the
language for WinKFPT.
Options: German (ger) and
English (eng).
Programming voltage U_PROG The entry specifies whether
the programming voltage is
switched ON or OFF
during flash programming.
Show programming voltage ANZEIGE_U_PROG The entry specifies whether

the value of the
programming voltage is
displayed (ON) or not
(OFF) during flash
programming.
Fast baudrate SCHNELLE_BAUDRATE The entry specifies whether

the fast baudrate is used
(ON) or not (OFF) during
flash programming.
Test Checksum TEST_CHECKSUMME The entry specifies whether

the checksum is validated
(ON) or not (OFF) after
programming of the data.
activate Bootsectorupdate BsuActive The entry specifies whether

a boot sector update, i.e.
flash programming of an
NAAB file, is possible or
not.
Force program PROGRAMM_ERZWINGEN The entry specifies

programming in comfort whether, during flash
mode programming in Comfort
mode, a program is to be
programmed whatever the

case, even if only data
programming would be
necessary.
UIF write after data AIF_SCHREIBEN_NACH_DATEN The entry specifies whether
the UIF is also
programmed (ON) or not
(OFF) during data
programming in Comfort
or Expert mode.
UIF write after program AIF_SCHREIBEN_NACH_PROGRAMM The entry specifies whether

the UIF is also
(OFF) during program
or Expert mode.
UIF write in expert mode EXPERT_MIT_AIF The entry specifies whether

the UIF is also
(OFF) during flash
programming in Expert
mode.
UIF write in comfort mode KOMFORT_MIT_AIF The entry specifies whether

the UIF is also
(OFF) during flash
mode.
PABD format CabdFormat The entry defines whether

WinKFPT is to use PABDs
as source files or as
compiled files.
IPS PABDs as source
files
IPO PABDs as compiled
files
API tracelevel API_TRACE The entry specifies the

level for the API traces in
Ediabas (0 means that the
trace is switched off).
IFH tracelevel IFH_TRACE The entry specifies the
level for the IFH traces in
Ediabas (0 means that the
trace is switched off).
Directory for error file ErrorLogPath Storage directory for the
"error.log" ERRORn.LOG file
Base directory for exported ExpertKonfPath Base directory for export of

configurations – a configuration of
development data development data (Expert
mode).
Base directory for exported KomfortKonfPath Base directory for export of

configurations – assembly a configuration of assembly
line data line data (Comfort mode).
Base directory for working CoapiSearchPath Base directory for working

directories of WinKFPT directories: cfgdat, data,
sgdat etc.
If you close the dialog window by clicking "OK" and the settings in the window differ from those in the
Ini file, you are asked whether you would like to save your changes permanently to the Ini file. Even if
you reject this option now, the settings you have entered remain valid for the duration of the WinKFPT
session, and you are given another chance to save this configuration to the Ini file when you end the
session.
If you change the PABD format and a PABD has already been selected, you must then explicitly select a
new PABD in Expert mode or implicitly select a new PABD in Comfort mode by selecting an assembly
identification number (ZB number). Message boxes prompt you to do this.
Help Menu
This menu is used to start the online help and display information about the program.
Contents - Calling the Online Help

You call the online help by selecting the menu option Help à Contents.
This command displays the opening screen of the online help function.
The User's Guide and the online help are identical.
Whenever updates of WinKFPT are released, the Word file of the User's Guide and the online help will
both be updated.
Fig.: Online help of WinKFPT
Info - Version Information of WinKFPT
You display the version information of WinKFPT by selecting the menu option Help à Info.
This command displays the program version and copyright information.
Fig.: Program version and copyright information
The top part of this window shows the version of WinKFPT and the versions of the COAPI and Krapi
libraries.
Displayed in the bottom right-hand corner are the creation date and time of the WinKFPT version.

5 WinKFPT&#39;s Main Menu

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

5 WinKFPT&#39;s Main Menu

Caricato da

Copyright:

Formati disponibili

WinKFPT's Main Menu Page 1 of 43

WinKFPT's Main Menu

You exit WinKFPT by selecting the menu option File / Exit.

This command terminates the program.

· API Trace File

Display CABI.ERR

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

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

Display PABD-Parameters

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

Displays the HW history of the current hardware number.

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

Displays the ZB history of the current hardware number.

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

Displays the ZB rule of the current assembly identification number.

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

Display API-Trace File

Displays an API trace file present in the EDIABAS directory.

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

Display IFH-Trace File

Displays an IFH trace file present in the EDIABAS directory.

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

Display Batch Mode

Batch mode is not yet started following this switching.

Fig.: Submenu under the main menu option <Import/Export>

Fig.: Pull-down menu under the submenu option <Import>

The following file groups can be imported:

*.DAF Data exchange files

*.PAF Program exchange files

*.0BA Data set files for NAAB

*.BAF NAAB exchange files

P-SGBD in compiled code

*.IPS PABDs in source code

PABD *.IPO PABDs in compiled code

*.0DA Data set files for data

*.AS2 ECU logistics files

Compatible assembly identification numbers of an ECU family

Authentication code files

ECU member integration position

Logistics file for checking the possibility of a BSU (boot sector

Files like from import of assembly line data +

Exported configuration – development files and/or tool-relevant files if desired

Files like from import of assembly line data +

tool-relevant files if desired by user

Table: Import files

Importing an "Exported Configuration" of Assembly Line Data

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

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

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

· Merge (only active when the WDP list is not empty):

KFCONFXX.DA2, HWNR.DA2 and SWTCONFx.DAT:

Importing an "Exported Configuration" of Development Data

Fig.: Selecting the import directory of a configuration of development data

Fig.: WDP conflict when importing a configuration of development data

directories (default is "Import - Development files" activated).

The files from the export directory

are not 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):

5 WinKFPT's Main Menu

5 WinKFPT's Main Menu

.IPS, .IPO <root>\SGDAT\

.ASD, .AS2, INFO.GER, HWNR.DA2, KFCONF.DA2, <root>\DATA\GDATEN

<SGFAMILIE>.DAT, .0DA, .0PA, .0BA, .HWH, *.HIS, <root>\DATA\<ecufam>

Only .IPS and .IPO files are displayed (default setting).