Documente Academic
Documente Profesional
Documente Cultură
NFS
New Flash System
System Documentation
Authors Georg Rauter Georg Rauter Georg Rauter Georg Rauter Georg Rauter
Changes Generation (engl. version) Update for NFS Version 4.3.x Update GIS-Server and command line Enhancements for version 4.5 (enhanced trailermode) Update for Motorbikes Berlin
Document:
C:\_C\Projekte\NFS_Doku\Neu_45_2\Dokumentation\nfs_e.doc
1.4 Multi-Channel Operation................................................................................7 1.5 Multi Instance Operation ................................................................................8 1.6 Requirements....................................................................................................8
2 Installation............................................................................................ 8
2.1 2.2 2.3 2.4 2.5 Installation from the GIS Server ....................................................................8 Individualization ..............................................................................................8 Documentation and Online Help ....................................................................9 Questions and Answers....................................................................................9 Contact Persons................................................................................................9
3 Command Line................................................................................... 10
3.1 Call-up from CASCADE ...............................................................................10
4 Operation............................................................................................ 11
4.1 Main Window .................................................................................................11
4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 Elements of the Main Window ................................................................................. 11 Traffic Light ............................................................................................................... 13 Signal Lights............................................................................................................... 13 Operating Elements for Process Control................................................................. 14 File Menu.................................................................................................................... 14 Menu Extras ............................................................................................................... 15 Emergency Flashing Menu ....................................................................................... 18 Configuration Menu .................................................................................................. 18 TestMode Menu ......................................................................................................... 18
5 Program Flow..................................................................................... 27
5.1 Rough Flow .....................................................................................................27 5.2 Partial Flow: Normal Flow............................................................................28
5.2.1 Detailed Flow Determining Vehicle Data (Flash) ................................................ 29 5.2.2 Detailed Flow - Flashing............................................................................................ 30
5.3 Partial Flow: CASCADE Run ......................................................................31 5.4 Partial Flow: Emergency Flashing ...............................................................32
6 Logging (Trace).................................................................................. 33
6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 Programming Diary .......................................................................................33 Current Vehicle ..............................................................................................34 Programmable ZB Numbers.........................................................................38 Vehicle Orders................................................................................................39 ID Data ............................................................................................................40 KMM Modification Plans..............................................................................41 KMM Backup Modification Plans................................................................42 Error Log ........................................................................................................42
8 Interfaces ............................................................................................ 53
8.1 CASCADE ......................................................................................................53
1 Overview
1.1 Function Overview
New Flash System (NFS) was conceived for application in the production environment and as a tool for the developer environment. NFS enables the review of current vehicle configurations and organizes the update of the ECUs. NFS comprises the following applications: CASCADE NFS normal operation Trailer operation HO mode Emergency flashing Sample Access via CASCADE (NFS-Light) Manual operation Programming uninstalled ECUs Applications of the trade organizations Programming a select ECU in the vehicle For checking the flashability of all ECUs of a vehicle
Transfer to reworking o o o Test result is displayed to the operator Operator separates the PC from the vehicle If required, the operator transfers the vehicle to reworking
Repeating the vehicle test at the reworking place o o o Operator connects the PC to the vehicle Ignition on (start button is activated) Operator starts the test
Conducting the necessary modifications o o o o o o o o o Test result is displayed to the operator Operator prints out list with ECUs to be exchanged Parallel to the following flash processes, the operator can procure the ECUs to be exchanged (If necessary), operator starts flashing at Terminal_15 Ignition key in the position "Radio" If necessary), operator starts flashing at Terminal_R Ignition off If necessary), operator starts flashing at Terminal_0 (If necessary), operator exchanges ECU(s)
1.3.2 ZB_CHECK If the option ZB_CHECK is activated in the configuration file, only the applicant information field (AIF) is checked. This mode is intended for tests in the early phase of a series (Product Process Prototype = PPP) and without significance for normal operation. 1.3.3 Trailer Operation Trailer operation is the flashing of individual ECUs not installed in the vehicle. Special devices (trailers) are available at the plants for this purpose and on which, as a rule, up to two ECUs can be flashed simultaneously. The trailers are mainly applied when ECUs are equipped with new software. The reprogramming of the ECUs at the plant bridges the time until the software modification has also flown into the ECUs delivered by the manufacturer. 1.3.4 HO Mode There is an inherent operating mode for application in the trade organizations. This concerns modifications on the vehicles after status F2. Due to the transport paths, the processed vehicles may have a different I-level than that used at the plant at the same time (and thus also in the current KMM). The HO mode makes it possible to circumvent certain measures provided by KMM in the modification plan. When the HO mode is activated, this is indicated by a suffix in the header. 1.3.5 Emergency Flashing Emergency flashing enables the flashing of an individual ECU selected by the operator and is required when the programming of an ECU was terminated with errors and if other ECUs can only be reached via this now inoperable ECU. Emergency flashing enables the inoperable ECU to contact other secondary ECUs once again. 1.3.6 Sample In the sample mode, all ECUs of a vehicle are newly flashed in their current state. This is applied by system administrators in order to check whether all installed ECUs are flashable. If this is not the case, it might be due to a production defect at the supplier of the ECUs. The system administrator stipulates the necessity for the test and the corresponding intervals.
1.6 Requirements
The following requirements are necessary for the operation of NFS: Release according to current BIV list (e.g. Siemens Simatic Rack-PC 840) Windows NT or XP EDIABAS (installation of EDIABAS on this computer) NFS (installation of the "New Flash Tool" on this computer)
EDIABAS, NFS and WinKFP require additional hardware equipment for connection to the vehicle (e.g. serial interface and OBD plugs). Especially with regard to the combined application of multi channel and multi instance operation, you need to be aware that the computer power and memory of a single PC are limited. Per NFS and per channel, EDIABAS and WinKFP start separate instances, which still has to be multiplied with the number of instances. Example: number of EDIABAS instances = (number of channels +1) * (number of instances)
The computer power required per instance also depends on the type of the hardware interface selected.
2 Installation
2.1 Installation from the GIS Server
The installation of all components required for NFS takes place via the GIS server (Global Information Service). A corresponding authorization is required in order to use the functions of the GIS server. In GIS choose the forum "BMW Standard Tools" to access NFS in the directories "Standard Tools | WerksInstallationen | NFS". For additional information about GIS, refer to the GIS homepage http://gis.muc. Authorization can be applied for via the homepage.
2.2 Individualization
With different settings in the configuration file, you can adapt the interface to special requirements. The most important settings are: Setting the language Selecting the company logo Fading out headers and/or terminal status
..\doku\nfs_faq.pdf ..\doku\handb-winkfpt32_V1.3.pdf
.\nfs.hlp .\winkfpt.hlp
Note: Notation for paths relative to the NFS\bin path. At present, the Intranet information on EDIABAS and NFS is under construction. The link to these pages is http://www5.muc/ti4-web/ti-430/german/_index4.htm
3 Command Line
3.1 Call-up from CASCADE
In the command line that appears at the start of the program, NFS contains information about the control of the process. The following information in the command line is used in the scope of CASCADE: ZB_CHECK APP_ZB_CHECK AUTOMATIC_FLASH Cascade call-up, only verification of vehicle data (ZB-Numbers) Cascade call-up, only verification of vehicle data (ZB-Numbers) not existing ECUs are ignored (vehicle not mounted complete yet) Flash automatic mode (without user interaction)
APP_AUTOMATIC_FLASH Flash automatic mode (without user interaction), especial for APP, tolerant handling of missing components -XML<datei> -DTD<datei> -FGNR<fgnr> Complete path to the Cascade XML file Complete path to the Cascade DTD file Chassis number of the current vehicle
Note: Only one of the options ZB_CHECK, APP_ZB_CHECK and AUTOMATIC_FLASH kann be used at the same time. The following defaults are used when the corresponding parameter is not contained in the command line (paths relative to executed file) : -XML -DTD -FGNR ..\TRACE\CASCADE.XML ..\TRACE\CASCADE.DTD <leer>
NB: In the path you may also use "/" instead of "\" (is converted internally), which is helpful when the callup takes place from a Java program.
4 Operation
4.1 Main Window
After the start of the program, all important information is displayed in the main window.
Version Responsible Facility
Logo
Main menu
Vehicle ID
Operator information
Terminal status
Operation
Traffic light
Instructions
Integration level
Simulation
4.1.1 Elements of the Main Window Element Logo Description Portrayal of the company logo. The logo to be used is defined in NFS.INI. The logo is part of the header and therefore only visible when the header is displayed.
Instructions
Simulation
4.1.3 Signal Lights The current process status for trailer flashing is visualized by means of signal lights. Here, access takes place via the PC's parallel ports. For further information about connecting the signal lamps, see chapter "Interfaces". The following signal lights are possible: Signal Light Off Description Programming runs or program inactive NB: Signaling only takes place when an action by the operator is required. It is therefore not possible to determine on the basis of the signal light whether the program is inactive or whether programming is running. Red Yellow Green An error has occurred and requires user input. Instruction, requires user input. Result OK. The ECU can be removed.
NB: The application of the signal lights requires the library file INPOUT.DLL, which is copied to c:\nfs\bin during installation.
Only visible and operable when user input is expected in the process flow. Only visible and operable when user input is expected in the process flow. When pressing this button, certain actions (waiting steps, tests) are interrupted or skipped deviating from the normal process flow. For traceability, the pressing of this button is recorded in the trace file (ERROR.TRC). Prints out the current content of the text field "Instructions" on the PC's standard printer and mainly serves to document not OK events as well as printing out the list with the ECUs to be exchanged. The button is only visible in the following process states: Display of the ECUs to be exchanged or flashed Checking the vehicle not OK Emergency flashing not OK
NB: If no printer is configured on the PC, the button is visible but disabled.
The menu options for displaying the files are only enabled when the file to be displayed is actually available.
System Documentation Version 1.5 / 2004-10-05 Author: Georg Rauter Copyright 2004 BMW AG Page 15 of 60 Responsible: TI-430 Reinhold Drexel, Tel. FIZ-44236 reinhold.drexel@bmw.de
Example of the main window without header and terminal status View NFS.INI View ID_CHECK.DAT Configuration file of NFS Contains ECUs with unreliably functioning diagnosis, but that still have to be available depending on the equipment (for example, SINE). List of ECUs included in the modification plan (independent of the KMM result). List of ECUs to be exchanged. The ECUs contained in this list may not be flashed and must be exchanged. List of the flash conditions and programming sequences. Here you define in which ignition key position and in which sequence the ECUs are flashed. List of the ECUs to be simulated. Contains ECUs not currently available in the vehicle (e.g. door dismounted).
View SGSIM.DAT
View FLASH.PRT
View ERROR.TRC
Description Opens the dialog for trailermade configuration. According to the done selections the files KMM_BACK.DAT and ID_CHECK.DAT will be created. Note: KMM is neccessary for configuration but not used during execution.
Views the file TRAILER.DAT and allows changes Here are shown the selections how defined in section [Trailerprofil] in NFS.INI. NFS.INI will be replaced by the selcted profile. Then will be done a reconfiguration automatically.
4.1.9 TestMode Menu The TestMode menu only serves to support the system administrator and should only be used by him/her. The visibility of the TestMode menu is controlled via an entry in the configuration file NFS.INI.
Description All configuration files are newly entered. Is required when configuration files are changed while the program is running (*.INI, *.DAT). The program will first work with the updated data after reconfiguration
Interpretation ID_CHECK.DAT Interpretation AKTION.DAT Interpretation NOFLASH.DAT Interpretation KMM Start of CASCADE ZB-Nr CHECK Start of CASCADE APP ZB-Nr CHECK Start of CASCADE Automatic Flash
Checks the file ID_CHECK.DAT (display of FZG.TMP) Checks the file AKTION.DAT (display of FZG.TMP) Checks the file NOFLASH.DAT (display of FZG.TMP) Checks the overall configuration and the process flow (display of FZG.TMP) Starts a CASCADE sequence for test purposes with the parameter ZB_CHECK (without chassis number). Starts a CASCADE sequence for test purposes with the parameter APP_ZB_CHECK (without chassis number) Starts a CASCADE sequence for test purposes with the parameter AUTOMATIC_FLASH (without chassis number). Runs automatically (without user interaction). Result will be stored in a xml-file. Starts a CASCADE sequence for test purposes with the parameter APP_AUTOMATIC_FLASH (without chassis number). Runs automatically (without user interaction). Result will be stored in a xml-file. Deletes the log files in the directory TRACE with exception of the programming diary.
Description Opens the NFS online help NFS.HLP; If English is preset, the file NFS_E.HLP is used.
About
Opens the information window with version information, copyrights and a history of the conducted changes (expansions or error corrections)
NB: The history is only visible when the language is preset to German.
Description Switches the currently displayed file to edit mode. Now you can change the file content. Attention: If you make changes to the displayed files, this may result in performance disruptions in the NFS or a complete malfunctioning.
Save
Can only be selected when the edit mode is activated. Overwrites the selected file with the current (changed) content of the display section.
Print Exit
Prints the content of the display section. Closes the display window. If there are changes in the display window that were not yet saved, you will be asked whether you want to save these.
Change indication
In normal program flow, this message should never appear. As a rule, the message dialog is used to inform the operator that unforeseen problems are going to render continuation of the program flow impossible. Such problems are, for example: error with file operations parameter files not available parameter files in the wrong format cannot be interpreted error with addressing EDIABAS or WinKFP in multi-channel operation if the vehicle does not support multi-channel operation
4.2.4 Configuration dialog for trailermode According to the done selections the files KMM_BACK.DAT and ID_CHECK.DAT will be created new. Provided options are determined by the content of the KMM and the file TRAILER.DAT.
The selection of components for flashing has to be done in the following order: Carline I-step ECU (multiple selection possible)
Normaly the OK button accepts the selection and following files will be generated: KMM_BACK.DAT ID_CHECK.DAT SGSIM.DAT new generated, old content will be lost new generated, old content will be lost will be completed; entries with VIN+carline (instead of VIN the IP name of the PC will be used)
Some ECU do not permit a unique correlation. In this cases the user will be prompted resolve the conflict manually.
System Documentation Version 1.5 / 2004-10-05 Author: Georg Rauter Copyright 2004 BMW AG Page 24 of 60 Responsible: TI-430 Reinhold Drexel, Tel. FIZ-44236 reinhold.drexel@bmw.de
The selection of the "proper" correlation requires especial knowlege and has to be confirmed with the following dialog:
If there is still ambiguity the proram tries to make the best choice. All remaining options are prompted to the KMM_BACK.DAT, all options beside the best choice are marked as comment. The user will be prompted that there is still a data conflict, an has to verfiy the generated file with the possibility to make changes.
; ---------------------------------------------------------; Trailer configuration ; 20.09.2004 14:45 ; ---------------------------------------------------------; [E89X] E89X-04-12-431 29 S??? K6769019 Z6769779 ; DSC_DXC:DSC:MK60:E90 E89X-04-12-431 29 S??? K6769882 Z6769779 ; DSC_DXC:DSC:MK60:E90 E89X-04-12-431 29 S??? K6766118 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) E89X-04-12-431 29 S??? K6769840 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) E89X-04-12-431 29 S??? K6769884 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) E89X-04-12-431 29 S??? K6766120 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) E89X-04-12-431 29 S??? K6769842 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) E89X-04-12-431 29 S??? K6769886 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) E89X-04-12-431 29 S??? K6769783 Z6769781 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) ;E89X-04-12-431 29 S??? K6766118 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : double !! ;E89X-04-12-431 29 S??? K6769840 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : double !! ;E89X-04-12-431 29 S??? K6769884 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : double !! ;E89X-04-12-431 29 S??? K6769781 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : conflict !! ;E89X-04-12-431 29 S??? K6766120 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : double !! ;E89X-04-12-431 29 S??? K6769842 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : double !! ;E89X-04-12-431 29 S??? K6769886 Z6769783 ; DSC_DXC:DSC:E9X:MK60E5 (Plus) (6Z) : double !! E89X-04-12-431 29 S??? K4033011 Z4033013 ; DSC_DXC:DXC8+_E90/E91: xDrive (m.Kupplungsregelung) ;EOF
5 Program Flow
5.1 Rough Flow
Start
CASCADE call-up
Flow started?
End, abandon?
Stop flow?
Program end
ZB_CHECK?
Flash initialization
Initialization ZB_CHECK
Veh. simulation?
Veh. simulation?
End
Read vehicle order Read chassis number Read raw order data Decode raw data
FA_Log = J
Save FahrzeugAuftragsDatei
Check FahrzeugDaten
KMM_BACK
End flashing
Check ZB-numbers
Show selection mask and wait for operator selection (ECU and ZBnumber)
6 Logging (Trace)
The logging (trace) of data and processes is controlled via the entries in the configuration file (section [Trace]). Here you have to be aware that files with activated function with the ending .TRC are not limited in size and therefore become larger and larger. They should be deleted manually from time to time (possibly saving first!). Deletion of the trace files takes place via an entry in the menu "TestMode" Saving the trace files takes place relative to the path of the executed .exe file. As a rule, the .exe file is located in C:\NFS\Bin. The trace files are also stored in the directory C:\NFS\Trace. There are corresponding menu options for viewing the files under "Extras". Below you will find some examples from the trace files with indication of the corresponding menu option and allocation of the respective entry in the configuration file (File [Section] Entry):
Contains the results of all flash processes performed for individual ECUs. Excerpt of the facility's programming diary (e.g. NFS246_27.DAT):
19.11.2003; 12:24:39; 12:24:48; 00:00:09; NFS_01; WBAGN82090DE78468; dummy ; 6764533; Klemme 15 ; 1; 50; 50; 0; i.O.; 1,0; .. E124-12-34-456; 0x38 19.11.2003; 12:24:58; 12:25:12; 00:00:14; NFS_01; WBAGN82090DE78468; dummy ; 6939151; Klemme 15 ; 1; 50; 50; 0; i.O.; 1,0; .. E124-12-34-456; 0x3B 30.06.2003; 12:37:09; 12:40:16; 00:03:07; NFS246; WBANC71050B147145; CDC60 ; 6938975; Terminal 15 ; 2; 50; 70; 0; OK; 13,7; 5.13 30.06.2003; 12:40:17; 13:07:03; 00:26:46; NFS246; WBANC71050B147145; MASKN1 ; 6941032; Terminal 15 ; 2; 50; 81; 4; OK; 13,7; 5.13 30.06.2003; 13:07:08; 13:12:14; 00:05:06; NFS246; WBANC71050B147145; MANSP1 ; 6940821; Terminal 15 ; 2; 50; 85; 4; OK; 13,7; 5.13 30.06.2003; 13:30:14; 13:30:24; 00:00:10; NFS246; WBANC710X0B147092; Shzh65 ; 6936672; Terminal 15 ; 1; 50; 50; 0; not OK; 14,1; 5.13 30.06.2003; 13:30:47; 13:34:01; 00:03:14; NFS246; WBANC71050B147145; SGMZ60 ; 6938938; Terminal 0 ; 1; 90; 1; 0; OK; 13,7; 5.13 30.06.2003; 13:34:02; 13:37:44; 00:03:42; NFS246; WBANC71050B147145; CAS260 ; 6927928; Terminal 0 ; 1; 90; 2; 0; OK; 13,7; 5.13 30.06.2003; 13:39:16; 13:40:56; 00:01:40; NFS246; WBANC71050B147145; DDE508 ; 7793543; Terminal 15 ; 1; 50; 25; 0; OK; 13,1; 5.13 30.06.2003; 16:08:36; 16:12:50; 00:04:14; NFS246; WBANA71070B100155; MASKG1 ; 6941038; Terminal 15 ; 1; 5; 30; 30; OK; 13,7; 5.13 30.06.2003; 16:13:24; 16:25:11; 00:11:47; NFS246; WBANA71070B100155; MDS450 ; 7533680; Terminal 15 ; 1; 50; 25; 0; OK; 13,7; 5.13 30.06.2003; 16:25:12; 16:31:05; 00:05:53; NFS246; WBANA71070B100155; DSCA60 ; 6766306; Terminal 15 ; 1; 50; 29; 0; not OK; 13,7; 5.13 30.06.2003; 16:31:06; 16:31:14; 00:00:08; NFS246; WBANA71070B100155; KBM60 ; 6939400; Terminal 15 ; 1; 50; 71; 0; not OK; 13,7; 5.13 30.06.2003; 16:31:16; 16:31:22; 00:00:06; NFS246; WBANA71070B100155; ACC65 ; 6766598; Terminal 15 ; 1; 50; 77; 0; not OK; 13,7; 5.13 30.06.2003; 16:31:23; 16:31:31; 00:00:08; NFS246; WBANA71070B100155; AFS60 ; 6766782; Terminal 15 ; 1; 50; 82; 0; not OK; 13,7; 5.13 30.06.2003; 16:31:33; 16:31:43; 00:00:10; NFS246; WBANA71070B100155; TEBF60 ; 6939712; Terminal 15 ; 1; 50; 83; 0; not OK; 13,7; 5.13
The meaning of the individual columns separated by ";" is: Column Start date Start time End time Duration Comment
Temporary file, which is overwritten with the next vehicle. Contains all information gathered on a vehicle.
New Flash System Version 4.2.1 Kmm Server Version 4.9 07.07.2003 13:05:36 VIN : WBANC71080B149648 Carline : E60 Multi channel : Yes Model code : NC71 Coding date : 0103 Actual I-step : 4.64 Nominal I-step : 5.13 Paint code : 0475 Upholstery code: LCSW Nos. of SA : 27 SA169 SA205 SA2RA SA320 SA403 SA423 SA428 SA441 SA442 SA459 SA465 SA473 SA494 SA502 SA508 SA522 SA524 SA534 SA540 SA548 SA606 SA785 SA801 SA851 SA863 SA879 SA915 Nos. of E word : 1 B110 Nos. of HO word: 0 Ident data Addr GROUP SGBD BMW-No. | ZB-No. UIF-date UIF-VIN | Programming status 0x00 D_ZGM ZGM_E65 6937704 | 6937704 **.**.**** | 0x01 Normalbetrieb 0x01 D_SIM SGM_60_2 6940303 | 6940303 08.05.2003 | 0x01 Normalbetrieb 0x02 D_SZL SZL 6937208 | 6937208 14.04.2003 | 0x01 Normalbetrieb System Documentation Version 1.5 / 2004-10-05 Author: Georg Rauter Copyright 2004 BMW AG Page 34 of 60 | Clear error memory | Status | OKAY | OK | OKAY | OK | OKAY | OK Responsible: TI-430 Reinhold Drexel, Tel. FIZ-44236 reinhold.drexel@bmw.de
Flash order data Addr ZB-No. Action Condition Channel Line Ranking Delay time ECU family 0x62 6941038 FlashEcu Terminal 15 1 5 30 30 MASKG1 0x12 7793543 FlashEcu Terminal 15 1 50 25 0 DDE508 0x72 6939400 FlashEcu Terminal 15 1 50 71 0 KBM60 0x63 6941032 FlashEcu Terminal 15 2 50 81 4 MASKN1 0x05 6939709 FlashEcu Terminal 15 1 50 83 0 TEFA60 0x0E 6939287 FlashEcu Terminal 15 1 50 83 0 SFZ60 0x06 6939712 FlashEcu Terminal 15 1 50 83 0 TEBF60 0xA1 6942099 FlashEcu Terminal 15 1 50 83 0 SBL260 0xA2 6942100 FlashEcu Terminal 15 1 50 83 0 SBR260 0x43 6939655 FlashEcu Terminal 15 1 50 84 0 MPM60 0x91 6940821 FlashEcu Terminal 15 2 50 85 4 MANSP1 0x01 6938931 FlashEcu Terminal 15 1 50 99 0 SGMS60 0x00 6938932 FlashEcu Terminal 0 1 90 1 0 SGMZ60 0x40 6927928 FlashEcu Terminal 0 1 90 2 0 CAS260 KMM data Addr Ident Action 0x00 6937704 0x01 6940303 0x02 6937208 0x05 6937701 0x06 6937702 0x0E 6937692 0x12 7793292 0x17 6765705 0x18 7534606 0x22 6934122 0x29 6766302 0x3B 6933234 0x40 6927927 0x43 6938358 0x44 6935690 0x45 6935249 0x60 6937618 0x62 6940520 0x63 6940518 0x64 6922785 0x65 6938313 0x67 6934259 0x6D 6927262 0x6E 6927262 0x70 6936997 0x72 6938530 0x73 6938109 0x78 6938550 0x90 6939735 0x91 6940519 0x92 6934493 0xA1 6939737 0xA2 6939738 Conv. plan Kmm status 6938932 ILevel 6938931 ILevel EcuOkay 6939709 ILevel 6939712 ILevel 6939287 ILevel 7793543 ILevel EcuOkay EcuOkay EcuOkay EcuOkay EcuOkay 6927928 ILevel 6939655 ILevel EcuOkay EcuOkay EcuOkay 6941038 ILevel 6941032 ILevel EcuOkay EcuOkay EcuOkay EcuOkay EcuOkay EcuOkay 6939400 ILevel EcuOkay EcuOkay EcuOkay 6940821 ILevel EcuOkay 6942099 ILevel 6942100 ILevel
8 Conversion plans available 1. Conversion plan 0x00 6938932 FlashEcu 6937704 K-Line 0x01 6938931 FlashEcu 6940303 K-Line 0x05 6939709 FlashEcu 6937701 K-Line 0x06 6939712 FlashEcu 6937702 K-Line 0x0E 6939287 FlashEcu 6937692 K-Line
6937704 K-Line 6940303 K-Line 6937701 K-Line 6937702 K-Line 6937692 K-Line 7793292 K-Line 6933234 6927927 K-Line 6938358 K-Line 6940520 K-Line 6940518 MOST-CONTROL 6936997 6938530 K-Line 6938109 6940519 MOST-CONTROL 6939737 K-Line 6939738 K-Line
The meanings of the individual sections are: Section Version ID Date and time Vehicle order ID data Action data Modification plan data NoFlash data Comment of NFS and KMM of the generation of this file Complete vehicle order (incl. lacquer, upholstery, E numbers, HO numbers) List of the determined ECUs in the vehicle with their properties Measures determined on the basis of the content of AKTION.DAT Modification measures determined according to the 1st modification plan supplied by KMM Measures determined on the basis of the content of NOFLASH.DAT
Contains a list of all capabilities of WinKFP regarding the programming of ECUs. The following listing contains only an excerpt of the 2798 entries in this version.
03.07.2003; 09:52 Number of ZB-Nos. = 2798 SGFAM ZB-No. HW-No. SW-No. ACC65 6760063 6760063 --ACC65 6760156 6760156 --ACC65 6760584 6760584 --ACC65 6761728 6761728 --ACC65 6763392 6763392 --ACC65 6763604 6763604 --ACC65 6762329 6762329 --ACC65 6764350 6764350 --ACC65 6764843 6764843 --ACC65 6765923 6765923 --ACC65 6766507 6766507 --ACC65 6766598 6766598 --AFS60 4021119 4021119 4021119 AFS60 4021123 4021123 4021123 AFS60 4023685 4023685 4023685 AFS60 4022439 4022439 4022439 AFS60 4025245 4025245 4025245 AFS60 4024993 4024993 4024993 AFS60 4025801 4025801 4025801 AFS60 4025334 4025334 4025334 AFS60 6764871 6764871 6764871 AFS60 6766395 6766395 6766395 .. . Zgm_65 6937956 6937956 --Zgm_65 6936740 6936740 --Zgm_65 6939134 6939134 ---
Contains important parts of the vehicle order for all processed vehicles.
11.03.2003; 09:23; WBANC71050B137053; E60 ; Multi channel ; NC71; 0103; 4.42 ; SA169 SA217 SA229 SA261 SA2RA SA302 SA356 SA415 SA423 SA428 SA430 SA431 SA438 SA441 SA456 SA465 SA494 SA496 SA502 SA508 SA522 SA524 SA534 SA536 SA540 SA548 SA563 SA606 SA638 SA672 SA677 SA785 SA801 SA851 SA863 SA879 SA902 SA915 SA991. 11.03.2003; 09:34; WBANC71080B147057; E60 ; Multi channel ; NC71; 0103; 4.40 ; SA169 SA205 SA217 SA229 SA261 SA302 SA356 SA415 SA423 SA428 SA430 SA431 SA435 SA441 SA456 SA465 SA494 SA496 SA502 SA508 SA522 SA524 SA534 SA536 SA540 SA548 SA563 SA588 SA606 SA638 SA672 SA677 SA785 SA801 SA851 SA863 SA879 SA902 SA915 SA991. 11.03.2003; 09:46; WBANA31040B007196; E60 ; Multi channel ; NA31; 0103; 4.44 ; SA216 SA261 SA2RA SA302 SA354 SA403 SA423 SA428 SA431 SA438 SA456 SA465 SA473 SA494 SA502 SA508 SA534 SA540 SA548 SA606 SA640 SA677 SA785 SA801 SA851 SA863 SA879 SA909 SA915 SA998.
The meanings of the individual columns separated by ";" are: Column Date Time Chassis number Series Multi-channel capability of the vehicle Type key Coding level Target integration level SE numbers Termination character Listing of all SE numbers contained in the vehicle order "." Time of entry in the file Comment
All ECUs installed in a vehicle are determined prior to flashing. The result is a listing of ECUs with their properties that are documented in this file. KMM calculates the modification plans with this information.
02.07.2003; 19:04; WBANC71040B149646; 0x00 H6937688 Z6937688; 0x01 H6940307 Z6940307; 0x02 H6937208 Z6937208; 0x05 H6937699 Z6937699; 0x06 H6937700 Z6937700; 0x0E H6937692 Z6937692; 0x12 H7793210 Z7793292; 0x17 H6765705 Z6765705; 0x18 H7532362 Z7534606; 0x22 H6934122 Z6934122; 0x29 H6766302 Z6766302; 0x3B H6933234 Z6933234; 0x40 H6927927 Z6927927; 0x41 H6940588 Z6940588; 0x43 H6938358 Z6938358; 0x44 H6935690 Z6935690; 0x45 H6935249 Z6935249; 0x50 H6936009 Z---; 0x60 H6937608 Z6937626; 0x62 H6940520 Z6940520; 0x63 H6940518 Z6940518; 0x67 H6934259 Z6934259; 0x70 H6936997 Z6936997; 0x72 H6939400 Z6939400; 0x73 H6938109 Z6938109; 0x78 H6938550 Z6938550; 0x90 H6939735 Z6939735; 0x91 H6940519 Z6940519; 0x92 H6934493 Z---; 0xA1 H6939737 Z6939737; 0xA2 H6939738 Z6939738. 02.07.2003; 20:55; WBANA71030B102257; 0x00 H6937704 Z6937704; 0x01 H6940303 Z6940303; 0x02 H6937208 Z6937208; 0x05 H6937699 Z6937699; 0x06 H6937700 Z6937700; 0x0E H6937692 Z6937692; 0x12 H7527072 Z7533680; 0x18 H7530853 Z7533352; 0x29 H6766302 Z6766302; 0x40 H6927927 Z6927927; 0x43 H6938358 Z6938358; 0x45 H6935249 Z6935249; 0x60 H6937608 Z6937610; 0x62 H6940520 Z6940520; 0x63 H6940516 Z6940516; 0x67 H6934259 Z6934259; 0x70 H6937758 Z6937758; 0x72 H6939400 Z6939400; 0x73 H6938109 Z6938109; 0x78 H6938548 Z6938548; 0x90 H6939735 Z6939735; 0x91 H6940517 Z6940517; 0x92 H6934492 Z---; 0xA1 H6939737 Z6939737; 0xA2 H6939738 Z6939738. 02.07.2003; 21:05; WBANA31080B009128; 0x00 H6937704 Z6937704; 0x01 H6940303 Z6940303; 0x02 H6937208 Z6937208; 0x05 H6937701 Z6937701; 0x06 H6937702 Z6937702; 0x0E H6937692 Z6937692; 0x12 H7527072 Z7533672; 0x22 H6934122 Z6934122; 0x29 H6766302 Z6766302; 0x3B H6933234 Z6933234; 0x40 H6927927 Z6927927; 0x43 H6938358 Z6938358; 0x44 H6935690 Z6935690; 0x45 H6935249 Z6935249; 0x60 H6937608 Z6937610; 0x62 H6940520 Z6940520; 0x63 H6940518 Z6940518; 0x64 H6922785 Z6922785; 0x65 H6938317 Z6938313; 0x67 H6934259 Z6934259; 0x6D H6927262 Z6927262; 0x6E H6927262 Z6927262; 0x70 H6937759 Z6937759; 0x72 H6938530 Z6938530; 0x73 H6938109 Z6938109; 0x78 H6938550 Z6938550; 0x90 H6939735 Z6939735; 0x91 H6940519 Z6940519; 0x92 H6934493 Z---; 0xA1 H6939737 Z6939737; 0xA2 H6939738 Z6939738.
The meanings of the individual columns separated by ";" are: Column Date Time Chassis number Listing of the ECUs Per ECU with hex address of the ECU, hardware* number and ZB number as well as the comment (optional) "ignored" (corresponding to the content of SGSIM.DAT) "." Time of entry in the file Comment
Termination character
Listing of the modification plans provided by KMM. A maximum of 10 modification plans can be called up but only the first modification plan is applied.
03.07.2003; 07:48; WBANA31010B009231; 1. Conversion plan, 0x00 6938932 FlashEcu, 0x01 6938931 FlashEcu, 0x05 6939709 FlashEcu, 0x06 6939712 FlashEcu, 0x0E 6939287 FlashEcu, 0x40 6927928 FlashEcu, 0x43 6939655 FlashEcu, 0x62 6941038 FlashEcu, 0x63 6941031 FlashEcu, 0x72 6939400 FlashEcu, 0x91 6940820 FlashEcu, 0xA1 6942099 FlashEcu, 0xA2 6942100 FlashEcu. 03.07.2003; 07:48; WBANA31010B009231; 2. Conversion plan, 0x00 6938932 FlashEcu, 0x01 6938931 FlashEcu, 0x05 6939709 FlashEcu, 0x06 6939712 FlashEcu, 0x0E 6939287 FlashEcu, 0x40 6927928 FlashEcu, 0x43 6939655 FlashEcu, 0x62 6941038 FlashEcu, 0x63 6941031 FlashEcu, 0x72 6939400 FlashEcu, 0x73 6941492 ReplaceEcu, 0x91 6940820 FlashEcu, 0xA1 6942099 FlashEcu, 0xA2 6942100 FlashEcu. 03.07.2003; 07:48; WBANA31010B009231; 3. Conversion plan, 0x00 6938932 FlashEcu, 0x01 6938931 FlashEcu, 0x05 6939709 FlashEcu, 0x06 6939712 FlashEcu, 0x0E 6939287 FlashEcu, 0x40 6927928 FlashEcu, 0x43 6939655 FlashEcu, 0x62 6941038 FlashEcu, 0x63 6941031 FlashEcu, 0x70 6936997 ReplaceEcu, 0x72 6939400 FlashEcu, 0x91 6940820 FlashEcu, 0xA1 6942099 FlashEcu, 0xA2 6942100 FlashEcu. 03.07.2003; 07:48; WBANA31010B009231; 4. Conversion plan, 0x00 6938932 FlashEcu, 0x01 6938931 FlashEcu, 0x05 6939709 FlashEcu, 0x06 6939712 FlashEcu, 0x0E 6939287 FlashEcu, 0x40 6927928 FlashEcu, 0x43 6939655 FlashEcu, 0x62 6941038 FlashEcu, 0x63 6941031 FlashEcu, 0x70 6936997 ReplaceEcu, 0x72 6939400 FlashEcu, 0x73 6941492 ReplaceEcu, 0x91 6940820 FlashEcu, 0xA1 6942099 FlashEcu, 0xA2 6942100 FlashEcu. 03.07.2003; 09:17; WBANA31010B009231; 1. Conversion plan, Blank conversion plan. 03.07.2003; 09:17; WBANA31010B009231; 2. Conversion plan, 0x73 6941492 ReplaceEcu. 03.07.2003; 09:17; WBANA31010B009231; 3. Conversion plan, 0x70 6936997 ReplaceEcu. 03.07.2003; 09:17; WBANA31010B009231; 4. Conversion plan, 0x70 6936997 ReplaceEcu, 0x73 6941492 ReplaceEcu.
Illustration: example of the contents of the file KMM.TRC (in the example, modification plans for 2 vehicles)
The meaning of the individual data: Column Date Time Chassis number Name of the modification plan List of the modification measures per ECU Termination character 1., 2., etc. Per ECU with hex address, ZB-number and measure (flash or replace) "." Time of entry in the file Comment
Corresponds to the KMM modification plans with regard to content, however, the modification plans are not generated by KMM but from KMM_BACK.DAT.
10.06.2003; 15:25; WBANA71040B100114; 0x05 6937701 FlashEcu; 0x06 6937702 FlashEcu; 0x22 6934122 FlashEcu; 0x29 6766302 FlashEcu; 0x3F 4122227 FlashEcu; 0x43 6938358 FlashEcu; 0x44 6935690 FlashEcu; 0x47 4122234 FlashEcu; 0x60 6937610 FlashEcu; 0x63 4124511 FlashEcu. 10.06.2003; 16:21; WBANA71040B100125; 0x3F 4122227 FlashEcu; 0x47 4122234 FlashEcu; 0x63 4124511 FlashEcu. 10.06.2003; 16:33; WBANA71040B100131; 0x62 4124474 FlashEcu; 0x47 4122234 FlashEcu.
02.07.2003; 11:20; WBANA71080B102318; 0x62 6941038 Programmierung n.i.O. fataler Fehler 02.07.2003; 11:22; WBANA71080B102318; 0x36 TELE60 6938781 Telefon ECE,US,Japan Variante Programmierung n.i.O. fataler Fehler 02.07.2003; 11:22; WBANA71080B102318; 0x3C CDC60 6938975 Audio CD-Changer Programmierung n.i.O. fataler Fehler 02.07.2003; 11:22; WBANA71080B102318; 0x63 MASKC1 6941031 MMI Audio System Kontroller Programmierung n.i.O. fataler Fehler 02.07.2003; 11:22; WBANA71080B102318; 0x91 MACSP1 6940820 --- Programmierung n.i.O. fataler Fehler 02.07.2003; 11:40; WBANA71080B102318; 0x36 TELE60 6938781 Telefon ECE,US,Japan Variante Programmierung n.i.O. fataler Fehler 02.07.2003; 11:40; WBANA71080B102318; 0x3C CDC60 6938975 Audio CD-Changer Programmierung n.i.O. fataler Fehler 02.07.2003; 11:40; WBANA71080B102318; 0x63 MASKC1 6941031 MMI Audio System Kontroller Programmierung n.i.O. fataler Fehler 02.07.2003; 13:01; WBANA71080B102318; 0x63 MASKC1 6941031 MMI Audio System Kontroller Programmierung n.i.O. fataler Fehler 02.07.2003; 13:01; WBANA71020B102282; Bordnetzspannung zu gering! Ist: 12,2 Soll: 12,8 02.07.2003; 13:03; WBANA71080B102318; 0x91 MACSP1 6940820 --- Programmierung n.i.O. fataler Fehler 02.07.2003; 14:42; WBANA71080B102318; 0x3C CDC60 6938975 Audio CD-Changer Programmierung n.i.O. fataler Fehler 02.07.2003; 14:45; ; Auswahl Notfallflashen ZB-Nr ABBRUCH durch den Anwender 02.07.2003; 14:46; WBANA71080B102318; 0x3C CDC60 6938975 Audio CD-Changer Programmierung n.i.O. fataler Fehler 03.07.2003; 01:11; WBANC71000B137932; 0x36 TELE60 6938781 Telefon ECE,US,Japan Variante Programmierung n.i.O. Abbruch AIF-Info: Das Anwenderinfofeld ist noch 1 Mal programmierbar SG programmieren?
NB: ECU-specific information is only included (optional) when the entry refers to a specific ECU.
7 Configuration Files
The NFS reads information for the configuration from the following files (INI files) ANLAGE.INI NFS.INI
Both files are located in the same directory as the executed file. NB: The name of the executed file is used for the NFS.INI configuration file. If another version is used for a test, for example, (e.g. NFS_Test.EXE), the configuration file must be named accordingly (NFS_Test.INI). The content of the configuration files is described as follows: [Section] Name of the entry
Format Default
If the entry is not contained in the configuration file, the program works with the setting described under Default.
7.1 ANLAGE.INI
[KONFIGURATION] Anlage
Format Default
ANLAGE.INI Name of the test site, appears in the main window, log is maintained by this name (e.g. NFS_01).
String
"N"
7.2 NFS.INI
[KONFIGURATION] Retry
Format Default
NFS.INI The number of repeat attempts when accessing the vehicle via EDIABAS; can be set to 0, as EDIABAS already conducts repeats internally. The value stated here is to be understood as multiplier of the internal repeat attempts.
Integer
NFS.INI Only the 1st letter is relevant. You define the logo to be displayed: "" = BMW Group logo (default, BMW&Mini) B = BMW Logo (2 logos are distinguished according to the language setting (see "Language")) R = Rolls Royce logo M = Mini logo
String
""
Serves to individualize the user interface depending on the location. Language String "D" Only the first letter is relevant. Defines which language is used: D = German E = English Only the first letter is relevant (J/N). Defines, whether processing continues with the HW*-number if the ZB number cannot be determined. Only the first letter is relevant (J/N). Defines whether processing continues with the ZB number if the HW* number cannot be determined. Only the first letter is relevant (J/N). Defines whether a flash is performed when the KMM does not provide a clear decision. Only the first letter is relevant (J/N). Defines whether the flash instructions contained in AKTION.DAT are to be carried out regardless of the results of KMM/KMM_BACK. Only the first letter is relevant (J/N). Defines whether the backup solution is to be used for KMM. The content of the file KMM_BACK.DAT is then used instead of KMM. Is used when KMM is not up to date yet due to alterations or when the KMM result is to be circumvented on purpose (e.g. in trailer operation) TestModus String "N" Only the first letter is relevant (J/N). Defines whether menus "TestModus" and "Configuration" are displayed.
String
"N"
String
"N"
String
"N"
String
"N"
KMM_BACK
String
"N"
NFS.INI Only the first letter is relevant (J/N). Defines whether NFS is operated in sampling mode.
String
"N"
ZB_CHECK
String
"N"
Only the first letter is relevant (J/N). Defines whether a ZB number check is to be conducted. Only the AIF is checked and no flash orders are performed.
AuftragSimulieren
String
"N"
Only the first letter is relevant (J/N). Defines whether the vehicle order is simulated.
MULTIINSTANZ
String
"N"
Only the first letter is relevant (J/N). Defines whether NFS is operated in multi instance mode.
FIXEDWINDOW
String
"N"
Only the first letter is relevant (J/N). With "Y", the operator cannot position the instance windows. Instead, the program arranges them automatically.
HO_MODUS
String
"N"
Only the first letter is relevant (J/N). Defines whether NFS is operated in HO mode.
TRAILERMODUS
String
"N"
Only the first letter is relevant (J/N). Defines whether NFS is operated in trailer mode.
SIGNLALEUCHTE
String
"N"
Only the first letter is relevant (J/N). Defines whether signal lights are accessed or not (used in connection with trailer operation)
Format
Default
NFS.INI
String String String String String "N" Only the first letter is relevant (J/N). Defines whether several channels are used in an instance.
[TRACE] ID_Log
Format
Default
NFS.INI Only the first letter is relevant (J/N). Defines whether the vehicle ID data is recorded in a file. File = \..\TRACE\ID.TRC Content: the ID data of the vehicle.
String
"N"
FA_Log
String
"N"
Only the first letter is relevant (J/N). Defines whether recordings are made in a file. File = \..\TRACE\FA.TRC Contents: order data of the vehicle
KMM_Log
String
"N"
Only the first letter is relevant (J/N). Defines whether recordings are made in a file. File = \..\TRACE\KMM.TRC Content: modification plans of compatibility management
WARN_Log
String
"N"
Only the first letter is relevant (J/N). Defines whether warnings are recorded in the ERROR.TRC file in addition to errors. Only the first letter is relevant (J/N/S). Defines whether recordings are made in a file. File = \..\TRACE\FZG.TMP N: data will not be recorded J: all information known about this vehicle and overwritten again with the next vehicle S: function like "J", additonally a copy of the file will be generated for eyery vehicle. (filename = <VIN>.TRC; e.g. WBAUF11090JR92179.TRC). Existing files will be overwritten with repeating VIN.
FZG_Log
String
"N"
ZB_Log
String
"N"
Only the first letter is relevant (J/N). Defines whether recordings are made in a file. File = \..\TRACE\ZB.TMP Content: File with ZB numbers (Winkfp)
[REKONFIGURATION] DateiNameEin
Format
Default
NFS.INI Default: C:\NFS\BATCH\MESSAGE.MSG Is used to inform NFS that the configuration has changed. If NFS is idle and detects this file, an automatic reconfiguration takes place and the current parameter files are read in new. NB: In multi instance operation, the instance number is added to the file name. This way NFS checks the first instance for the file MESSAGE_1.MSG, the 2nd instance for the file MESSAGE_2.MSG etc. in multi instance operation.
String
->
DateiNameAus
String
->
Default: C:\NFS\BATCH\MESSAGE.OLD After conducting a reconfiguration due to the abovementioned file, DateiNameEin is renamed to DateiNameAus (naming convention in multi instance operation: see above at DateiNameEin).
The settings in the sections [ANZEIGE], [ANZEIGE_1] etc. define the configuration for the program start. The values can be changed when the program is running and are updated and saved in the configuration file.
[ANZEIGE] Kopfzeile
Format
Default
NFS.INI Only the first letter is relevant (J/N). Defines whether a header is displayed (this setting can be changed via the "Extras" menu). Only the first letter is relevant (J/N). Defines whether the terminal status is displayed (this setting can be changed via the "Extras" menu). Window position for the next program start. The program generates information automatically.
String
"J"
BatterieZuendung
String
"J"
WinPos.
If the program is used several times simultaneously on a computer, the section names are numbered consecutively (e.g. [ANZEIGE_1], [ANZEIGE_2] etc.). The content of these sections is the same as that of the section [ANZEIGE]. The series matrix is a kind of translation list for series. For each series you can determine which parameters and treatment of another series should be used in the further course of the program.
NFS.INI "E65" E66 is treated as an E65 in the further course of the program.
String
""
E67
String
""
Auftrag_SGBD
String
""
Alternative SGBD to obtain the vehicle data set. Use only for motorbikes in Berlin! SGBD (e.g. "MRK24") will be used instead of "CAS".
NFS.INI The parameter set here is transferred 1:1 without testing as ECU to the EDIABAS interface and must be defined in the respective SGBD (database management system) of the vehicle series. The parameter set here is transferred 1:1 without testing as JOB to the Ediabas interface and must be defined in the respective SGBD of the vehicle series. The parameter set here is transferred 1:1 without testing as result name ECU to the EDIABAS interface and must be defined in the respective SGBD of the vehicle series (on-board supply voltage) Limit value for checking the "on-board supply voltage" result. Limit value for checking the "on-board supply voltage" result.
String
UBatt_JOB
String
UBatt_RESULT
String
UBatt_MIN Ubatt_MAX
Integer Integer
? ?
If no section or UBatt_SGBD entry can be found for a vehicle series, the following default settings are used: UBatt_SGBD UBatt_JOB UBatt_RESULT UBatt_MIN UBatt_MAX "UTILITY" "STATUS_ZUENDUNG" "STAT_ZUENDUNG" 1 1
Copyright 2004 BMW AG Page 49 of 60 Responsible: TI-430 Reinhold Drexel, Tel. FIZ-44236 reinhold.drexel@bmw.de
NFS.INI Text for the menu item of the first trailer profile in the configuration menu. Sourcefile to overwrite NFS.INI with selection of the first trailer profile.
? ? ? ? ? ?
It is possible to manage up to 9 trailer profiles. As the program searches for profile 1 to 9, coninuous numbering is not neccessary. This allows to fade out temporary not used profiles by marking as comment.
Example of 2 instances with OBD (excerpt from NFS.INI) 7.3.3 Multi-Channel Operation In multi-channel operation, sections [INHALT] and/or [INHALT_x] must be expanded by 2 entries per channel. The Interface and Unit entries describe the channel used by NFS (via EDIABAS), entries Interface_x and Unit_x describe the channels used by WinKFP. As NFS and WinKFP are never used simultaneously, NFS may use the same channel as one of the WinKFP instances.
[INSTANZ_1] Interface=remote:OPPS_DIAGNOSE_NUR_K_LINE_OPPS1 --> Verweis auf remote.ini Unit=A MEHRKANAL=ja Interface_1= Unit_1 = Interface_2= Unit_2 = remote:OPPS_DIAGNOSE_NUR_K_LINE_OPPS1 A remote:OPPS_DIAGNOSE_NUR_MOST_OPPS1 A
[INSTANZ_2] Interface=remote:OPPS_DIAGNOSE_NUR_K_LINE_OPPS2 Unit=A MEHRKANAL=ja Interface_1= remote:OPPS_DIAGNOSE_NUR_K_LINE_OPPS2 Unit_1 = A Interface_2= remote:OPPS_DIAGNOSE_NUR_MOST_OPPS2 Unit_2 = A
Example of OBD.INI (correlation to NFS.INI) This sample configuration shows the OBD.INI referred to in the examples for NFS.INI. This is supposed to clarify the correlation between the entries in NFS.INI and OBD.INI. In individual cases, OBD.INI must be adapted to the prevailing circumstances (hardware configuration etc.). For further information about the configuration, refer to the EDIABAS documentation. 7.3.5 Sample Configuration REMOTE.INI This sample configuration shows the REMOTE.INI referred to in the examples for NFS.INI. This is supposed to clarify the correlation between the entries in NFS.INI and REMOTE.INI. In individual cases, OBD.INI must be adapted to the prevailing circumstances (hardware configuration, etc.). For further information about the configuration, refer to the EDIABAS documentation.
System Documentation Version 1.5 / 2004-10-05 Author: Georg Rauter Copyright 2004 BMW AG Page 52 of 60 Responsible: TI-430 Reinhold Drexel, Tel. FIZ-44236 reinhold.drexel@bmw.de
; Start REMOTE.INI ; REMOTE.ini (ab EDIABAS 6.4) [Common] ;TimeoutConnect=2000 ;TimeoutReceive=2000 ;TimeoutFunction=10000 ;DisconnectOnApiEnd=1 [OPPS_DIAGNOSE_NUR_K_LINE_OPPS1] ; Mehrfachbetrieb: Nutzt nur K-Line, gibt MOST frei RemoteHost = opps1000 Port = 6801 InitCmd0 = FE 05 00 80 05 [OPPS_DIAGNOSE_NUR_MOST_OPPS1] ; Mehrfachbetrieb: Nutzt MOST, gibt K-Line frei RemoteHost = opps1000 Port = 6802 InitCmd0 = FE 05 00 80 01 [OPPS_DIAGNOSE_NUR_K_LINE_OPPS2] ; Mehrfachbetrieb: Nutzt nur K-Line, gibt MOST frei RemoteHost = opps1001 Port = 6801 InitCmd0 = FE 05 00 80 05 [OPPS_DIAGNOSE_NUR_MOST_OPPS2] ; Mehrfachbetrieb: Nutzt MOST, gibt K-Line frei RemoteHost = opps1001 Port = 6802 InitCmd0 = FE 05 00 80 01 ; E O F ; Ende REMOTE.INI
8 Interfaces
8.1 CASCADE
The parameters for controlling the NFS are provided by CASCADE as described in the chapter, "Command Line". NFS reports back with the result in the file CASCADE.XML.
<?xml version="1.0" encoding="ISO-8859-1" ?> <!DOCTYPE Auftrag-Report SYSTEM "C:\Nfs\Bin\..\TRACE\CASCADE.DTD" > <Ausfuehrungs-Report version="Report Ausfuehrung: V1.0.0"> <DateiInfo> <Datum>16.07.2003, 15:42:50</Datum> <Kommentar>Report Auftrag</Kommentar> <Autor name="NFS V4.2.2"/> </DateiInfo> <Fahrzeugdaten> <Fahrgestell nummer=""/> </Fahrzeugdaten> <Ergebnis> <ID name="NFS APP_ZB_CHECK"/> <Werkzeug name="NFS"/> <Parameter-1 name=""/> <Parameter-2 name=""/> <Parameter-3 name=""/> <Ergebnisname name=""/> <Ergebniswert wert=""/> <Min-Wert wert=""/> <Max-Wert wert=""/> <Anzahl-Wiederholungen anzahl="0"/> System Documentation Version 1.5 / 2004-10-05 Author: Georg Rauter Copyright 2004 BMW AG Page 53 of 60 Responsible: TI-430 Reinhold Drexel, Tel. FIZ-44236 reinhold.drexel@bmw.de
8.2 EDIABAS
The NFS program uses the functionality of EDIABAS by calling up the functions contained in APIVB32.DLL.
8.4 WinKFP
WinKFP is started by calling up WinKFPT.exe from NFS. Information for control in batch mode is provided in the command line. Parameter -BATCH= -RUN -INTERFACE -UNIT Argument Name of the batch file Comment e.g. C:\NFS\BATCH\FLASH.CTL resp. FLASH_#.CTL (#=channel number in multi-channel operation) Starts WinKFP in batch operation Defines the HW interface (optional) Defines the unit (optional)
Once started, WinKFP continuously checks whether there is a FLASH.CTL file. If a file is found, the content is interpreted and the corresponding commands processed. Afterwards, WinKFP deletes the file.
[FGNUMMER] FGN = WBAGL63473DP66387 [ZBNUMMER] ZBN0000 = 6929559 ZBN0001 = 6929558 [SGADRESSE] SGADR0000 = 04 SGADR0001 = 05
WinKFP communicates the result of the execution in a file with the same name and the extension .PRT (e.g. FLASH.PRT). NFS evaluates the contents of this file.
[C:\Nfs\Bin\..\BATCH\FLASH.CTL] [16.07.2003 15:44:51] [Batch] END=OFF [FGNUMMER] fgn = WBAGL63473DP66387 [ZBNUMMER] ZBN0000 = 6929559 / SGADR0000 = 04 ZBN0001 = 6929558 / SGADR0000 = 05 [PROCESSING] [6929559 / 04] fgn = WBAGL63473DP66387 INFO000=ok ERG=Programmierung i.O. [6929558 / 05] fgn = WBAGL63473DP66387 INFO000=ok ERG=Programmierung i.O.
NFS generates the .CTL files for controlling WinKFP. A .TMP file is always generated in order to avoid overlaps. Once generated, this is renamed.CTL. Then NFS waits for the result in the PRT. file. NB: NFS also controls the termination of WinKFP via the file FLASH.CTL. Here it is important that during the programming of WinKFP, NFS activates the inherent EDIABAS instance in such a way that the communication channels to the vehicle are completely available to the EDIABAS instance (instances) of WinKFP. In order to differentiate between the files when using several channels/instances, the file name is generated as follows: FLASH_k_i.PRT resp. FLASH_k_i.CTL (k = channel, i = instance). If the corresponding preselection is not activated, the corresponding part in the name is omitted (_k resp. _i).
Important: Accessing the signal lights takes place LOW-Active Signal condition logical 1 corresponds to Signal condition logical 0 corresponds to lamp OFF lamp ON
Important Note: The usability of additional cards with parallel ports has to be proved. Port addresses shown above can not be changed! To check the function of connected signallights the program "NFS Signallampentest.exe" (in c:\nfs\bin) can be used.
The following SGBDs and jobs are always required regardless which series is concerned: SGBD UTILITY JOB STATUS_UBATT STATUS_ZUENDUNG Result STAT_UBATT STAT_ZUENDUNG Comment
CAS
STATUS_FAHRGESTELLNUMMER FGNUMMER
C_FA_LESEN
FA
FA_STREAM2STRUCT
BR C_TYP C_DATE LACK POLSTER SA_ANZ E_WORT_ANZ HO_Wort_ANZ E_WORT_001 E_WORT_xxx HO_WORT_001 HO_WORT_xxx
In addition and if required, for every series the name of the SGBDs, the job and the result can be set individually in the configuration file NFS.INI for checking the on-board supply voltage (programming voltage).
INPA IO, i.O., OK JOB KMM NFS NFS-Light NOK, not OK, NIO
System Documentation Version 1.5 / 2004-10-05 Author: Georg Rauter