Tag Archives: INPA

How to solve NCS Expert VIN is faulty COAPI-2000

Have spent my entire Saturday on this:

All running on XP and also tried on Win7 x64

INPA is working fine. Battery and ignition both ON
When running NCS Expert, try to read the VIN from ECU i get VIN Faulty

Vin is faulty
COAPI-2000 Error or in ECU description file (SGBD) IFH-0018 CAS
COAPI-2000 Error or in ECU description file (SGBD) FGNR_LESEN
COAPI-2000 Error or in ECU description file (SGBD) FGNR_A_E65CAS

ncs-expert-vin-is-faulty-1
ncs-expert-vin-is-faulty-2

Solution 1:

If you have Standard tools 2.12 you are fine.

Check if you have E89 folder in C:\NCSEXPERT\DATEN\

And make sure that you copied all files from sp-daten\daten\*.* to here C:\NCSEXPERT\DATEN\ and here C:\NCSEXPERT\DATEN\E89

Just recopy this and check if this helps

Solution 2:

You can only run INPA or NCS one at a time, not simultaneously.

Also, sometimes mine gives me that error. It’s usually because I didn’t initialize the USB cable properly. Unplugging it, closing NCS, plugging it back and restarting NCS usually solves my problem.

Hope this helps.

Solution 3:

you are missing some files for E65 at sp-daten. Try to download newer spdaten and copy at least e65 folder or update whole data.

Solution 4:

make sure you update your daten files correctly as well

you can do the following copy-paste procedure: (copy the files and replace )

Target —————————Source .(SP-Daten-Exx directory )

\NCSEXPER\SGDAT\ ——– .ipo files
\NCSEXPER\DATEN\ ——– coding data (daten) for models
\EDIABAS\Ecu\ ————– .prg files……

If not work, please empty your .man file .. delelete everything inside then save.. then try again

ON YOUR NCS EXPERT FOLDER YOU SHOULD SEE A FILE:

FSW_PSW (MAN)
FSW_PSW (TRC)

INSIDE THE (MAN) ONE DELETE ALL THE VALUES INSIDE THEN SAVE AS.MAN SO FSW_PSW.MAN MAKE SURE SAVE AS ALL FILES OTHERWISE IT WOULD SAVE ONLY AS PLAIN TEXT.

After You Do That.. Try To Read The Car Again.. So Ncs Expert,f1,f3 E89,cas, Then Back

NOTE:
All above solutions are shared on BMW forums; never know he/she is the professional or amateur. So, YOU ARE TRYING EACH SOLUTION ON YOUR OWN RISK.

Reference: NCS EXPERT User Guide

Proceed at your own risk, this is just my interpretation for educational/entertainment value only. I am not responsible for you blowing up your car or damaging your modules. Im serious!

DUMMIES GUIDE TO UNDERSTANDING NCS AND CODING

This is roughly how it works… and my dummy interpretation of it. Please read it fully if you want to understand, this isn’t exactly a quick cheat sheet guide.

On Pre ’02 cars the coding is slightly different method than Post ’02 cars. I am only going to elaborate on coding individual parameters, you can go learn how to code entire modules thru the VO later once you learn the basics below.

The first part to understand is what this stuff about ZCS/VO or “vehicle order” is. When BMW makes a car, they create whats called a “vehicle order”, this is basically a bunch of numbers written into the car that tell what modules are installed in the car, regional info etc. This is like your car’s DNA! for example if the car has a sunroof, or a convertible or radio etc etc and that it was meant for US,Canada,France etc. Because each car is different with a different set of options/modules or country that its located, the “vehicle order” aka. “ZCS” or “VO” may be different. Why is it called ZCS you ask? because its abbreviated german, and its confusing as hell.

The VO is written into a couple modules of the car, usually ones that start with an “A”, like AKMB or ALSZ. On some cars its written elsewhere. In my 02 M3, the VO was written in ALSZ and AKMB. On my ’00 328ci it was stored in EWS, KMB. Its nothing more than a string of text/numbers stored in the flash memory of these modules, nothing special. Why is it written into two places? because if one module is failed and has to be replaced, then the other will serve as a backup so you can code the new replacement module to your car. For example ALSZ is the “light switch module” in your car, for some reason it fails. When you buy a new LSZ/LCM, you can retrieve all your settings of VO from AKMB and then code your new LCM to YOUR factory settings. The chances of both modules failing is slim, but if it does… you’ll have to contact BMW so they can give you the VO for your car from their records.

OK the one difference is pre-02 cars don’t have a VO. Those cars have their ZCS (which acts like a VO) stored in the EWS or KMB modules. The stuff below is basically identical however for individual parameter coding.

Now go get into the basics of coding.

1. When you load NCS expert, you need to load a profile. These profiles just change how ncs expert behaves when you read your car. The two profiles i stick to are “expertmode” and “revtor’s expert profile”. if you don’t have it, you can find it on the net easily. In order to code your car the first time, you should pick “revtors“. This has something called “manipulation” enabled… ill elaborate on that later.

2. Once the profile is loaded, you basically need to select Vin/ZCS/FA in order for ncs to download VIN info off your car. Once it does this, it will ask you to select a module. Why? because it needs to know your “vehicle order” information. In most cases it will probably be in an “A” module. if it doesn’t load, or cant be accessed, no harm done, just try a different module. When it is able to read it, you will see a long string next to “FA” starting with your chassis “E46_” followed by numbers and text along with #’s and $’s. This is your VO. Now that NCS Expert knows it, it can code your car properly!

CODING HAS NOTHING TO DO WITH THE MODULE YOU JUST SELECTED TO READ THE VO FROM! This perplexed me for the longest time, I didn’t understand why i selected two modules each time, or what the difference selecting AKMB or ALSZ or etc the first time was. Well… It has no bearing!! all NCS is doing is reading the text/number string that is your VO off the memory in these modules in this first step. You will actually select the desired module to code in later steps.

** PRE-02 cars, you wont see the long FA “VO” string, instead there will be a few lines FG, GM, VN, SA followed by numbers, its basically the same thing different format. For all intents and purposes this is referred to by me as the vehicle order or ZCS for a pre-02 car.

ON POST-02 cars select any module with “A’ in front of it, on PRE-02 the “A” modules wont work, you will need to use EWS or KMB for this step… It doesn’t matter which. 

Now this guide will touch on the basics to code INDIVIDUAL items on your car. The steps to add items to your VO and code your modules is different and i wont comment on that here, because it will confuse the amateur. Just understand the basics of individual coding first, then coding from your VO will all make sense later.

3. The next part is to download your factory settings in your car to your PC. Once you get the VO loaded, you hit the BACK button. The default job in NCS is to write SO BE VERY CAREFUL here. You will see all your modules listed, for example “EWS,ABG,ASC,KMB,APL,…..etc” and underneath “SG_CODIEREN”

NCS at this point is set to SG_CODIEREN, which means to WRITE to ALL modules listed. You don’t want to do that.

4. So now select “Process ECU”, and select the INDIVIDUAL MODULE you want to code. For example LSZ (light switch module). Once you do this, it will say only LSZ (and not all the modules in your car).

5. Now you want to change the job from WRITE to READ. Select “CHANGE JOB”, then select “CODIERDATEN_LESEN”. This is to READ DATA.

6. Once selected it will confirm this by indicating the module and job type on the screen. Now you are ready. Hit “EXECUTE JOB”.

It will say Coding Activ, then Coding Ended.

7. At this point, in your NCSexpert/WORK/ folder there will be a file called “FSW_PSW.TRC”

This is what we want, the coding of your LSZ module that we read earlier. IMMEDIATELY save a backup of this file, rename it to FSW_PSW_LSZ_ORIGINAL.TRC and save it somewhere in case you decide you want to revert to the original copy. Now I want you to resave another copy of this FSW_PSW.TRC file as FSW_PSW.MAN (manipulation…hint hint). Make sure it doesn’t save as FSW_PSW.MAN.TXT or some crap like that, it wont work properly.

OK why all this juggling?? because NCS expert only reads modules and saves EVERYTHING as a FSW_PSW.TRC file. Regardless of what module you read in your car, this is what the filename will be. And everytime you load NCS expert, this file is constantly erased, written and re-written. So thats why we are saving it as FSW_PSW.MAN so we can alter it safely without our copy being overwritten.

8. Now open up FSW_PSW.MAN with a text editor.

You will see a long list of stuff like this..

LEUCHTWEITENREG_AUTOM
aktiv
FEHLER_BREMSLICHT
nicht_melden
TAGFAHRLICHT
aktiv

This is where you can code. now its all in german, so you will need to run these words in a translator (google) to understand it, OR you can use NCS Dummy that translates this stuff for you and gives you all available parameters, but thats a whole different program and you ought to learn how to use it.

This is what the above looks like if translated. Now you can see how we can deactivate/activate certain things. I’m going to deactivate DRLs here.
Translated…

AUTOMATIC HEADLIGHT CONTROL
active
BRAKE LIGHT ERROR REPORTING
don’t report
DAYTIME RUNNING LIGHTS
active 

edited…

LEUCHTWEITENREG_AUTOM
aktiv
FEHLER_BREMSLICHT
nicht_melden
TAGFAHRLICHT
nicht_aktiv

By changing to nicht_activ, it deactivates this setting. Now don’t go crazy, some codes are redundant so changing just one thing wont do the trick. This takes some time and effort to find the right code/codes to work with.

9. Once you are happy, SAVE your FSW_PSW.MAN file.

10. Open up NCS expert, load up “revtors” profile (with manipulation enabled), and reload it to the part where the VO is loaded and its asking you to process ecu (Basically steps 1-3) Look above how to do this. Once you’re there, select “PROCESS ECU”, select the correct module you are coding, in this case “LSZ”. Then select “CHANGE JOB” and make sure you pick “SG_CODIEREN”. Once this is done, you are ready to code the car.

NCS will basically now take the FSW_PSW.MAN file, and overwrite the codes in your car’s LSZ module with your new settings. It only uses the MAN file because you are using a profile with “manipulation” enabled. The other mode “expertmode” does not have manipulation, and you cannot code individual stuff like this using that profile.

11. Hit “EXECUTE JOB”. Wait till it says “Coding ended”. Now your new LSZ is coded. Turn off the car, and restart, and check to see if your results are as expected!

12. Open up the /WORK/ folder, open the FSW_PSW.MAN file, select all, delete, save and exit.

Viola! Thats it. You are now an expert on coding individual features!

Now what do you do if you screwed it up or something is behaving funny and you want to go back to original settings. Or you cant remember all the stuff you changed, or don’t like the results.

To load up the ORIGINAL factory defaults if you mess up.

Go to your /WORK/ folder. Open FSW_PSW.MAN, select all, delete, save & exit.

Load NCS Expert

Select “Expertmode” profile

Hit “VIN/ZCS/FA” to load your Chassis and Vehicle order info

Hit BACK

Hit PROCESS ECU

Select the chassis, then module you F’d up on. For example “LSZ”

On Pre-02 cars It will say “LSZ” and underneath “SG_Codieren” along with some files LSZ.Cxx, LSZ.PRG, etc etc. SG_CODIEREN is the correct job you want.

On Post-02 cars It will say “LSZ” and underneath “SG_Codieren” along with some files LSZ.Cxx, LSZ.PRG, etc etc. Hit CHANGE JOB, Select “FA_WRITE” Job.

“xx” is usually the specific Coding index used in your default module, its a number. think of this like “firmware version”.

These files are basically from your /DATEN/ folder and contain the proper coding information specific to your car. How does NCS know which files to use? Because it knows by looking at your VIN and VO, then selects the correct files. NCS will then basically read these files, then read your VO and re-write the proper codes, features, activate, deactivate everything to your factory settings.

The job is SG_Codieren or FA_Write because you will WRITE your original settings back in.

Hit EXECUTE JOB.

Viola, your original data is re-written and your car will work again. Hopefully.

http://www.obdii365.com/service/how-to-solve-ncs-expert-vin-is-faulty-coapi-2000-97060.html

How to Reset & Relearn E60 BMW Automatic Transmission with INPA

BWM E60 automatic transmission reset and relearn by using BMW INPA K+DCAN cable.
It is a reset method of learning function.

Especially when there is something wrong with a large displacement car
There seems to be improvement in some cases. (Physical breakdown is excluded)

inpa-reset-e60-transmission-1

Launch INPA and select GS 19

inpa-reset-e60-transmission-2

Select F6

inpa-reset-e60-transmission-3

Reset complete with F3
inpa-reset-e60-transmission-4

www.obdii365.com

 

BMW E60 Coding by NCS Expert and INPA K+DCAN Cable

In this blog you will know how to do BMW E60 coding by NCS Expert software and cheap INPA K+DCAN Cable! Check below screenshots to code BMW Control Units step by step!

 

NCS Expert & INPA K+DCAN BMW Coding Success Steps

Step 1

Use the BMW INPA K+DCAN Cable to connect car with laptop via the BMW E60 OBD2 port.

BMW-INPA-K-DCAN-Cable-BMW-E-Series-Coding

Open BMW NCS Expert Coding software.

Click “File” then choose “Load File”.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-1

Select “Default Profile” and click “OK”.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-2

Step 2

Press the F1 button “VIN/ZCS/FA”

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-3

Then press the F3 button “ZCS/FA f.ECU” and select BMW chassis “E60”.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-4

Choose ECU: CAS ECU or LMA ECU.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-5

Step 3

It will show BMW E60 car VIN number, check it then press F6 button to back.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-6

Check if it show “get coded” then press F3 button “Process car” and F4 button “Process ECU”.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-7

Step 4

Now just select the ECU control unit you want to do coding.

For example, BMW E60 6BMOT, click “OK” to continue.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-8

It will show the selected ECU information, click “OK”.

Check if it show the selected ECU +”get coded” then press the F3 button “Execute job”.

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-9

And wait it complete, it will show “Coding ended”.

BMW Coding by NCS Expert and $13.99 INPA K+DCAN USB Interface done!

bmw-e60-coding-ecu-control-unit-by-ncs-expert-inpa-cable-10

http://blog.obdii365.com/2017/06/19/bmw-e60-coding-guide-by-ncs-expert/

Reset BMW E9x Transmission via INPA Step by Step

I am trying to reset automatic transmission adaptations on BMW E92 335i 2007 via INPA K+DCAN cable and software, but i am stuck at the step as indicated by the picture.

inpa

I downloada gs19.ipo file to do my reset as I have the alpina and it wouldn’t work so now it does but I got this message:

“nicht zusammenpassende versionen fehlfunktion ist moglich” which translated says

“Mismatched versions malfunction is possible”

 

I search around forums and finally get some clues from Alex Fiehl. Big thanks to Alex who helped solved my problem.

 

There are reset jobs/functions in Tool32 that I find is more reliable. Just be prepared to follow the proper “re-learning” procedures afterwards. Check detail guide below:
Automatic transmissions are fickle beasts which can be astronomically expensive if not maintained. Throw in the fact that it’s a BMW, and the need for regular maintenance becomes quite clear. Unfortunately, a fluid and filter change is not as easy as it used to be.

When hard parts are replaced in a transmission or the fluid is changed, resetting the transmission’s adaptations may become necessary to restore shift quality. The ZF 6-speed automatic used in many E90-based vehicles like the 335i, X1, and 135i (among others) is an expensive transmission, and fluid replacement w/adaptation reset can be a great way to extend the life of it. This article should apply to any E-series vehicle that uses the ZF 6-Speed “Steptronic” Automatic.
When should I reset adaptations?
-When the fluid is changed
-When the software is updated (i.e. Alpina B3 Flash)
-When hard parts are replaced inside the transmission
Warning: If you have the capability of resetting transmission adaptations with INPA, I urge you not to do it unless you have the time and roadways to complete the relearn process exactly as described. This procedure will cause the transmission to shift poorly at a detriment to the gearbox if the relearn is not performed immediately and properly. It is better to change the fluid and NOT reset adaptations, than to reset them and not perform the proper relearn procedure.

To interface with your BMW you will need a BMW INPA K+DCAN Cable, which is a USB to OBD-II interface cable. We won’t be coding any modules or doing intensive flashing, so even a budget cable is likely to work, though.

 

Software Installation
To get INPA (as well as other coding features not needed in this article) BMW Standard Tools must be installed. Here are details instructions on how to install it:

How to Set up BMW Standard Tools 2.12 on Windows 7

 

Resetting Adaptations
Turn the vehicle’s ignition on but do not start the car by pressing the start button twice. Plug in the K+DCAN adapter to the vehicle and laptop. Execute INPA. When INPA is loaded, the battery and ignition bubbles should be filled in to indicate it has established communication with the vehicle.
Press shift+F8 for E90 based vehicles:

reset-bmw-transmission-inpa-1

Select Transmission, then select GS19:

reset-bmw-transmission-inpa-2

Press F6 Activate:

reset-bmw-transmission-inpa-3

Press F3 to reset transmission adaptation values:

reset-bmw-transmission-inpa-4

After pressing F3 the software should confirm the adaptations are reset and you can begin the process of relearning.

 

Relearning Adaptations
The most important part of resetting transmission adaptations is the re-learn process. Refer to the chart below to see which re-learn procedure your vehicle needs after its transmission adaptations are reset. Your vehicle’s build date will be on the sticker in the driver’s door jamb.

reset-bmw-transmission-inpa-5

Relearn Procedures:

Software A

Software+A

Software N

Software+N

Software P

Software+P

Software T

Software+T

http://blog.obdii365.com/2017/02/25/reset-bmw-e92-transmission-via-inpa-kdcan/

BMW Coding & Programming via INPA or Rheingold?

Between INPA and ISTA/D (Rheingold), which one is better and which one should be used for bmw E/F series diagnosis/coding/programming? Here are professional tips by experienced users.

INPA and ISTA/D (Rheingold), which one better?

ISTA/D (aka Rheingold) is the current dealership diagnostic software for all Exx and Fxx cars. ISTA/D is the replacement for older dealership DIS diagnostic software. Likewise, ISTA/P is the replacement for older delaership SSS Progman programming software. ISTA/P & ISTA/D are designed to be used with an ICOM Interface, and with full ICOM-A-B-C, you can connect to older cars. The ICOM “C” Connection is for the older BMW ADS 20-pin round “Pacman” connector in Engine Bay. You can find versions of ISTA/D with an ICOM Emulator builtin, that allows you to use it with an ENET Interface for Fxx cars and a DCAN Interface for Exx cars. I don’t know for sure, as I do not do any Exx work, but I doubt ICOM Emulator would work for older ADS connector.

INPA (interpreter for test procedures) is older factory floor diagnostic software, designed to run test procedures. While INPA can be set for English User Interface, most of the Test Procedures, which can be difficult to find, are in German.

Between the two, ISTA/D is simply a better option. It has a modern interface, is 100% English (or available in a multiple other languages), and is complete in that it does not require additional Test Procedures.

You can have ISTA/P & ISTA/D installed on a laptop aside INPA, WinKFP, and INPA without any issues.

INPA and Rheingold, how to choose for different BMW cars?

All Rheingold versions have native support for Ediabas 7.x, this option just needs to be activated from istagui config file. I can check the parameter later. This means that INPA K+DCAN can be used directly with Rheingold, as long as the Ediabas (which comes with BMW Standard Tools) is configured for this interfaces. Setting for Ediabas.ini can be found in Rheingold settings, under VCI tab (if the config file has been configured correctly). If the interface works with INPA or Tool32, then it works with Rheingold too.

ADS interface is not supported, as Rheingold requires Ediabas 7.x, and only Ediabas 6.x and older has ADS support. So to use Rheingold with ADS cars, ICOM is mandatory. ADS cars are E36, E34, beginning of E38 production and all chassis models that are older than these. E39, E46 and later E38, and all chassis models made after these are equipped with K-line or D-CAN, so K+DCAN cable (combinated interface that has both K-line and D-CAN) is good for these cars. F-series cars can use K+DCAN for diagnosis and ENET for diagnosis + coding and programming.

There are 20-pin connectors in engine compartment on all cars made approximately before year 2000, even if they have OBD-2 connector too. If there are both of these connectors available, then 20-pin must be used as OBD-2 is then connected only to DME/DDE and EGS. 20-pin connector type is K-line or ADS, depending on the chassis model. If it is K-line, then K+DCAN and obd-20pin adapter can be used.

There is also ADS interface available, it can be used with INPA on ADS cars. It can be found from E-bay, and it is called Tiny ADS. This ADS thing talks directly to COM-port i/o memory addresses, so laptop must have native COM port. USB-COM adapter will not work, period. Of course ICOM can handle these cars via ethernet connection, even with INPA. To configure ICOM to work with Ediabas, I-tool radar is used to check ICOM ip address and then EasyConnect can be used to configure ediabas and to lock the ICOM.

Note: How to activate Ediabas support in Rheingold:

Open ISTAGUI.exe.config with notepad
find line with parameter BMW.Rheingold.OperationalMode
change it to this:
inpa-coding-software

Which software for E/F series diagnosis, coding, programing?

If you want meaningful Diagnosis in English, for both E-Series and F-Series cars, you need ISTA/D (Rheingold) and you can request it here:
http://www.obdii365.com/wholesale/v201612-bmw-icom-software.html

For Coding, you need different Tools, NCS Expert / SP-Daten for E-Series and E-Sys / PSdZData for F-Series.

All Diagnosis and Coding can be done with cheap DCAN Cable for E-Series and cheap ENET Cable for F-Series.

For Programming (Flashing ECU’s with new Firmware), then you need ISTA/P for for both E-Series and F-Series cars, or you can use WinKFP for E-Series and E-Sys for F-Series. For E-Series Programming, you will need an ICOM, but for F-Series Programming, you can use ENET Cable.

Attachment:
BMW E F series coding options available in INPA & E-SYS

http://www.obdii365.com/service/inpa-and-ista-which-better-for-bmw-coding-programming-75825.html

BMW INPA 5.0.2 Windows XP Installation Guide

BMW INPA Windows XP installation guide… Here you go…The inpa ediabas software provided and the procedures proposed are intended for personal, educational and experimental use.

 

Note: this how-to guide here especially for Windows XP users only

For users with Windows Vista, Win 7 (32/64bit), Win 8, Win10, please go to

BMW INPA Download &  Install on Windows XP Vista Win7 Win8 Win10

 

bmw inpa / ediabas interface: INPA K+DCAN usb cable

The version 2016 cable is great, designed with the FT232RQ chip and a switch to turn LEFT is for 7 pin or RIGHT for 8 pin (8 pin for K-LINE communication (old DCAN cables cannot do it) for BMW from 1998 to 2008)

k+dcan-inpa-cable-switch

k+dcan cable software: INPA 5.0.2

 

Running system: Windows xp

 

k+dcan usb interface software installation:

Step 1: Delete ALL versions of INPA-ADS from your computer or remane all INPA-ADS folders.

For example: remane INPA into “_INPA”, EDIABAS into “_EDIABAS” and so on.

 

Step 2: Open folder Step_1\ in the root of the CD-disk comes with the inpa cable

Copy folder EC-APPS onto disk С:\

 

Step 3: Run file Step_1\NFS\Entpackt\disk1\SETUP.EXE

While installing, choose User Mode

Further choose in opening windows:

  1. Parametrieren einer neuen Konfiguration ohne Daten
  2. 2. OBD
  3. Kein API-TRACE
  4. Kein IFH-TRACE
  5. Komfort (.IPO)

! RE-BOOT YOUR Computer !

 

Step 4: Run file Step_2\INSTALL\Instprog.exe

  1. Choose ENGLISH, press Continue, then press Continue again
  2. While choosing the HDD disk for initial setup

DO NOT change the location C:\.

INPA installation must be on drive С:\ ONLY !

  1. Choose configuration BMW Group Rectification programs UK, press Continue.
  2. Activate all spare boxes with : EDIABAS 6.4.3 – UPDATE, INPA 5.0.1 – UPDATE,

NCS Expert 3.0.8 – Complete

  1. Press Continue.

 

Step 5: Run file Step_3\INSTALL\Instprog.exe

  1. Choose ENGLISH, press Continue, then Continue again
  2. While choosing the HDD disk for initial setup.

DO NOT change the location C:\.

INPA installation must be on drive С:\ ONLY !

  1. Choose configuration BMW Group Rectification programs UK, press Continue.
  2. Activate all spare boxes with: INPA 5.0.1 – UPDATE, NCS Expert 3.0.8 – UPDATE
  3. Press Continue.

 

Step 6: Find the file С:\EC-APPS\INPA\CFGDAT\ named inpa.ini

and replace it with the file inpa.ini that is in the root directory of CD-disk given.

 

Step 7: Plug the Adapter into spare USB-port and install drivers manually from the folderDriver_D_CAN_USB using Driver Wizard of your Windows XP-Service Pack-2

 

Step 8: Use following pictures for help.

how-to-install-inpa-on-windows-xp-1

Step 9: In Advanced field change number of COM-port to the value from 2 to 4.

Also change the value of Latency Timer from 16 to 1. Remember the number of the COM-port choosen !

how-to-install-inpa-on-windows-xp-2

 

Step 10: In the file EDIABAS.INI “Interface = STD:OBD” must be chosen

(That is default parameter after installing from CD-disk given. Check the parameter if you use another version of INPA !)

 

Step 11: In the file C:\Windows\OBD.INI put the number of USB-COM-port to the value that you remembered in the step_3

 

Step 12: Run from CD-disk a file Driver_D_CAN_USB\OBDSetup.exe

 

Step 13: RE-BOOT your Computer !

 

Step 14: Use the following order of using K+DCAN USB cable adapter:

– Plug the Adapter into spare USB-port

– Plug the Adapter into OBD-II connector of BMW

– Turn the Ignition into ON position

– Rune the soft INPA with file С:\EC-APPS\INPA\BIN\inpaload.exe

– Choose the model of BMW and type of modul you want to see

– Close the soft and disconnect the Adapter from USB-port each time you change the car connected

 

N.B.:

K+dcan adapter is already configured to work with BMW both K-line and CAN-bus.

Modes of configuration file D-CAN.exe, that is on the CD-disk given in the folder

_D_CAN_USB as follows:

 

BMW INPA Cable Configuration:

For configuration interface:

Connect USB cable

Run D-CAN.EXE and setup CAN BUS mode.

LED should OFF

Don’t use USB Extender cable, directly connect interface to computer.

www.obdii365.com

How to install BMW INPA on WinXP Win7 Win8 Win10

BMW INPA Ediabas 5.0.2 download, inpa 5.06 download, inpa 6.4.7 download here…and install it on Windows XP/ Vista  or Windows 7/ 8/ 10 (32bit or 64bit), to get it work with K+DCAN USB cable.

 

 

INPA download

INPA 5.0.2 download (tested OK)

Inpa v5.0.2 Ediabas v6.4.7.rar

INPA 5.0.6.rar

INPA/ediabas 6.4.3 full.rar

ediabas 6.4.7 inpa 5.0.1.iso

More: INPA Ediabas download

 

BMW inpa cable

Basically, there are two methods for users to get the INPA K+DCAN usb cable, to buy a complete one or simply build one yourself. Read the following to get it.
One way is to build a cable yourself. Cost for this would probably range anywhere between 10 to 20 bucks. You will need to solder a bit but it’s nothing too serious if you follow the instructions to the letter.

Its actually very simple that any average person can do that has access to a drill and a soldering gun.

Tools needed..
1. Small philip screwdriver to take the D-can cover off
2 Radio Shack micro on/off switch (can be two prongs or three) and some wire 24 guage.
3. Soldering gun
4. Some type of glue gun or glue adhesive
5. Drill bit 5/16 to make hole in the D-can cover

Locate pin 8 which will have a number on the side of the board. One side will have the digit 1 and the other digit 8

Once you locate pin 8, thats the pin we will be using as well as the next one over. Connect each pin 7 and 8 with a separate wire and then use the soldering gun and connect each wire to the micro on/off switch… If you bought a 2 prong on/off switch connect it to each side, but if you bought a switch with three prongs, connect the middle and one of the ends, doesnt matter which one. At the end there will be one prong end not used…Neatly place the wires snug so that the D-can cover can be closed without anything preventing it to make a closed seal and your done. Screw in the 4 philip head screws in their respected holes. Note which postion is on and which is off by some type of label on the outside of the cover…SImple! Note on my first pic, I have a switch with 3 prongs, but I snipped off the 3rd one just to make it easier to solder…

k+dcan-inpa-cable-switch

k+dcan-cable-switch

k+dcan-cable-pins

k+dcan-cable-connection

Modified-k+dcan-cable

I modified my cable with a switch and have 7 and 8 bridged to work with a 2004 E46. INPA and Dis 44 work perfect but I cant get Progman to work. Progman starts to reads the FA/ZCS after you choose the car model and then after awhile it says it requires an Edic/Icom cable connection. What needs to be done to make connection with Progman SSS V32?? Do I need to change anything in the Ediabas configuration. I know my modified cable works fine now that I modified it because Dis 44 and INPA wasn’t communicating before I modified the cable. Thanks for the help. I am stumped as I want to code the car for my brother-in-law. I actually can use Dis 44 as I already went into the CKM coding menu, but Progman is much better to help him choose his features he wants as its pretty much offers a checklist with dots!

 

Took a pic of my success with my modified D-can cable connected to E46 using Progman. My brother-in-law had no idea he had so many features that were not turn on…He also turn off his daytime running lights which he hated!

K+DCAN-cable-bmw-E46

(NOTE: this diy guide is from cn555ic at e90post.com, the professionals have not tried, put it here )
But if you are not interested in building one, buy a dedicated BMW cable instead. This is a site that has been confirmed working by some of E-series friends: http://www.obdii365.com/wholesale/bmw-inpa-k-can-with-ft232rq-chip.html .. I wouldn’t recommend other sites, although they may work, problem is that they have not been confirmed working yet. Functions of k+dcan cable at obdii365 has been tested for years (many discussion in forums).
The version 2016 cable is great, designed with the FT232RQ chip and a switch to turn LEFT is for 7 pin or RIGHT for 8 pin (8 pin for K-LINE communication (old DCAN cables cannot do it) for BMW from 1998 to 2008)
the chips and switch on the cable….

k+dcan-inpa-cable-switch-pcb (1)k+dcan-inpa-cable-switch-pcb (2)

 

INPA installation guide…Here you go…

Here, inpa installation guides for Windows XP, Windows Vista 32bit, Windows 7 32, Windwos 7 64bit, Windows 8, Windows 10 users. (click on the Operation System to get the how-to guide directly).

 

Note: INPA 5.0.2 is verified to work XP systems without any issues. For others, you need luck!

 

 

How to install inpa on windows xp

Inpa installation video made by obdii365.com officially

I’ve used this install method without fault on umpteen machines now and not had to amend any registry settings or anything, its worked first time every time this way..

 

there is a myth you have to use com port 1 with INPA this is total cobblers! you can use any com port number you like as long as the INPA OBD.ini file port selection matches your actual com port setting on the vagcom interface you have set..

 

First things to do is Download the 326MB version of BMW INPA from a torrent site or anyware you can get it ( and extract it to a folder on your machine..

 

you also may need to download the FDTI VCP (virtual com port) driver for windows XP for the Vagcom USB interface from the FDTI website, unzip it to a folder and copy this folder to the 326MB INPA installation software folder so you know where it is and for any future installations…

 

Virtual COM Port Drivers

 

  1. Insert your modded OBD-II-USB vagcom cable into your usb-port

-once it is detected by windows and prompts for the driver (at this point windows may find the drivers for you depending on the vagcom type) point it towards your FDTI vcp driver folder in the INPA folder if windows fails to find the drivers…

It will then install the drivers (it will probably go thru this process twice just repeat the process)

In the windows Device Manager, you should now see [Ports COM & LPT] ->> “USB Serial Port (ComX)

right click this and click properties/port settings /advanced.

at the top change your port number to your selection( if you do not wish to move or force a device on COM1 to another port because its already being used just select an unused port usually COM2 is unused) just remember your port selection for the INPA\install.

Now change the transmit and receive settings in the drop down boxes to 2048 for both transmit and receive

Now change the latency setting from 16 to 1

Ok the changes and exit

The usb vagcom cable is now setup.

 

  1. Always use SAME USB-port from now on.

 

  1. Installing INPA

you must copy and paste your downloaded complete INPA installation software folder to your C drive.

in your INPA folders click programmisation then double click setup.

It should default to English so ok this.

Click next till you get to the selection for software to install.

Select or deselect in options boxes but as a minimum select INPA ,EDIABAS and NCS expert if you want it.

Click next you will be asked to backup and restore (I declined this , unticked the box and skipped it all)

Make sure quick launch and desktop icons are ticked.

Click next.

Now select STD-OBD in drop down box (should be by default).

Click next.

Now select the com port number you selected earlier from the drop down box and tick the USB to serial adaptor box.

Click next and install (if it ask for backup and recovery just click skip to these prompts if you wish)

Finish install

Reboot

Now go to C/ediabas/hardware/OBD/OBDsetup.exe

Double click OBD setup.exe

If all is well you should get a black DOS box up with various settings shown with a full house of ok’s on them, you may get the start one saying warning instead of an ok if you have selected an alternative com port just ignore it)

press any key to exit if the list is ok.

Reboot

Go to C/ediabas/bin..

Find the OBD.ini or OBD file and double click

Your settings will be dispayed make sure they read as below

PORT= COM? (your com choice entered and set earlier)

HARDWARE=USB

RETRY=ON

UBAT=OFF (type this command in manually in this position)

Exit and save

Right click andCopy the amended OBD.ini file and paste it into your C/windows folder

Now go back to the INPA \install folder on C drive.

Open C/INPA folder/REFERENZ/INSTALL.

Double click instprog.exe

Ok the german writing page

Select English and continue.

At destination drive page make sure C drive is selected and continue.

Now select BMW “GROUP RECTIFICATION PROGRAMME UK” from the list and click continue

Now select the following:

Ediabas tick update box

INPA tick update box

NCS expert expert tick complete box

click continue

Tick the box “delete the old NCS expert “

Click install

double check that C:\EDIABAS\BIN has been added to the path string in enviromental variables (right click my computer/properties/advanced/enviromental variables and select path in the list, click edit check its there and exit without changing anything)

 

That’s it. you should be done and ready to get diagnosing

 

Always use the SAME USB port on your laptop when using the software…

 

PS if you want to do recoding with NCS expert (highly doubtful like its in german and impossible) you need ignition sensing which you dont get with a Vagcom but you can flip the FDTI chip (FT232RL chipset) on the interface with Mprog software to fake the batt and ignition sensing so you can encode…

 

 

bmw inpa windows vista 32bit

here is my successful INPA install method for Vista (i have been told it works for WIN7 32 bit too)….

 

  1. Firstly again open up your £7 Vagcom interface by removing the 4 x phillips screws on it

Get yaself a fine soldering iron and with a blob of solder,solder pins 7 and 8 together on it and put it back together…

 

there is a myth you have to use com port 1 with INPA this is total cobblers! you can use any com port number you like as long as the INPA OBD.ini file port selection matches your actual com port setting on the vagcom interface you have set..

 

First things to do is Download the 326MB version of BMW INPA from a torrent site or anyware you can get it or just PM me If you want a known good working version to download, i have uploaded it zipped with WinRar with the FDTI drivers included just extract it to a folder on your machine…

 

IF YOU HAVE YOUR OWN COPY you also may need to download the FDTI VCP (virtual com port) driver for some windows OS’s for the Vagcom USB interface from the FDTI website, unzip it to a folder and copy this folder to the 326MB INPA installation software folder so you know where it is and for any future installations…

 

Virtual COM Port Drivers

 

.NOTE THIS INSTALL METHOD IS FOR WINDOWS VISTA 32 bit ONLY!

 

Insert your modded OBD-II-USB vagcom cable into your usb-port

-once it is detected by windows and prompts for the driver if it does not find the driver then point it towards your FDTI vcp driver folder in the INPA folder…

It will then install the drivers (it will probably go thru this process twice just repeat the process)

In the windows Vista Device Manager (computer/system properties/device manager), you should now see [Ports COM & LPT] ->> “USB Serial Port (ComX)

right click this and click properties/port settings /advanced.

at the top change your port number to your selection( if you do not wish to move or force a device on COM1 to another port because its already being used just select an unused port usually COM2 is unused) just remember your port selection for the INPA\install.

Now change the transmit and receive settings in the drop down boxes to 2048 for both transmit and receive

Now change the latency setting from 16 to 1

Ok the changes and exit

The usb vagcom cable is now setup.

 

  1. Always use SAME USB-port from now on.

 

  1. Installing INPA

you must Copy and paste your downloaded complete INPA installation software folder to your C drive.

In your INPA folders double click the programmisation folder- then right click the setup icon and select “Properties/Compatibilty mode select XP service pack 2 and tick the box, click the apply button and exit now double click the setup icon and begin the setup.

It should default to English so ok this.

Click next till you get to the selection for software to install.

Select or deselect in options boxes but as a minimum select INPA ,EDIABAS and NCS expert if you want it.

Click next you will be asked to backup and restore (I declined this , unticked the box and skipped it all)

Make sure quick launch or desktop icons are ticked.

Click next.

Now select STD-OBD in drop down box (should be by default).

Click next

Select Com port number (you selected earlier) in the drop down box, tick the USB serial adaptor box

 

Click next and install (if it ask for backup and recovery just click skip to these prompts if you wish)

Finish install and Reboot

 

Now go to C/ediabas/hardware/OBD/OBDsetup.exe

Double click OBD setup.exe

If all is well you should get a black DOS box up with various settings shown with a full house of ok’s in Vista this will be full of errors and missing OK’s we shall address this later with a registry edit..

press any key to exit the list.

Reboot

Go to C/ediabas/bin..

Find the OBD.ini or OBD file and double click

Your settings will be dispayed make sure they read as below

PORT= COM? (your com choice entered and set earlier)

HARDWARE=USB

RETRY=ON

UBAT=OFF (type this command in manually in this position)

Exit and save

Right click and Copy the amended OBD.ini file and paste it into your C/windows folder

 

Now go back to the INPA \install folder on C drive.

Open C/INPA folder/REFERENZ/INSTALL.

Right click Instprog.exe/Properties/Compatibilty select windows XP service pack 2 and tick box and apply and exit.

Double click the instprog.exe and install

Ok the german writing page

Select English and continue.

At destination drive page make sure C drive is selected and continue.

Now select BMW “GROUP RECTIFICATION PROGRAMME UK” from the list and click continue

Now select the following:

Ediabas tick update box

INPA tick update box

NCS expert expert tick complete box

Click continue

Tick the box “delete the old NCS expert”

Click install

Double check that C:\EDIABAS\BIN has been added to the path string in enviromental variables.. (Computer/System Settings/Adavanced System Settings/Environmental Variables” click edit check its there and exit without changing anything)

 

You can now test INPA on your car it will work with the INPA diags only and you will get error warnings with Ediabas running because of the OBDsetup command errors earlier,to address this copy and paste the following below into a notepad folder, save the file to your desktop and name the file “serial.reg” and select all files and save…

 

  1. COPY and PASTE all registry data below…

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Serial]

“ErrorControl”=dword:00000000

“Group”=”Extended base”

“Start”=dword:00000002

“Tag”=dword:00000001

“Type”=dword:00000001

“ForceFifoEnable”=dword:00000001

“RxFIFO”=dword:00000008

“PermitShare”=dword:00000000

“LogFifo”=dword:00000000

“TxFIFO”=dword:00000008

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Serial\Parameters]

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Serial\Enum]

“0”=”Root\\LEGACY_SERIAL\\0000″

“Count”=dword:00000001

“NextInstance”=dword:00000001

“INITSTARTFAILED”=dword:00000001

 

You must copy and paste all the above including the windows registry bit or it will not execute to the registry later.

 

You now need to backup the registry just in case so you can restore it if need be…

Click the windows icon start button bottom left on desktop and type in regedit in the small box and press enter to access the registry

Click file then Export and name the file something of your choice and select ALL in the export range box and save it to somewhere safe..

 

Now double click the serial.reg file and apply it to the registry (right click the file and open with registry editor if it opens in notepad by default)

 

Go back to to C/ediabas/hardware/OBD/OBDsetup.exe

Double click setup the blackbox should be clear of errors (you may get 1 if you have selected an alternative port number other than COM1 ignore it)

 

You now should be good to go with full functions and no error messages when using your INPA…

 

 

inpa installation windows 7 32bit

This DIY was tested with Windows 7 Home Premium Service Pack 1 (SP1) running on a circa 2008 Lenovo S10 netbook with a K+DCAN cable from one stop electronics.com. My netbook is used solely for coding and as such this DIY assumes that your computer is dedicated to this purpose as well.

 

I recommend starting with a fresh 32-bit Windows 7 installation in order to collect the necessary INPA 5.0.2 configuration files that you will need after installing BMW Standard Tools 2.12. I suggest disabling Windows Update automatic updates during the Windows 7 installation process. After entering your product key, the following screen will pop up security message.

 

Select “Ask me later”, this will prevent Windows 7 from automatically installing any updates.

If your installing from pre-SP1 Windows 7 media, I highly recommend that you manually install two Microsoft updates:

System Update Readiness Tool (KB947821):
http://www.microsoft.com/en-us/downl…s.aspx?id=3132

Windows 7 Service Pack 1 (KB976932):
http://www.microsoft.com/en-us/downl…s.aspx?id=5842

During testing pre-SP1 Windows 7 no longer displayed a mouse pointer after successfully installing EDIABAS & WinKFP and rebooting the system.

INPA 5.0.2 can be found here:

INPA-EDIABAS full English Edition

Installation Guide

Follow steps 2 through 6 of the installation guide. During the EDIABAS & WinKFP install (step 3), select Windows XP (this is not mentioned in the installation guide.) For all other selections, accept the default and click Weiter which is German for “further.”

 

The very first time you attempt to install EDIABAS & WinKFP (step 3), regsvr32 will fail to register two Windows ActiveX controls. This is normal, upon re-installation everything will work properly.

 

Click on OK and then click on the large red circle with a white X at the bottom of the screen to see the second regsvr32 error.

 

Click on OK to acknowledge the second error.

 

Press any key to exit the EDIABAS OBD setup program. Don’t be concerned about any registry key warnings, this installation of EDIABAS will never be used.

 

When prompted to reboot, select Nein for “No” and then click on Beenden or “End” to exit the installation program. Go to Control Panel and uninstall the program.

 

Once you have uninstalled the program, reinstall it. On the second attempt, the ActiveX controls will register properly.

 

This time, select Ja for “Yes” and reboot.

 

Even with SP1 installed, on occasion the system will no longer display a mouse pointer after rebooting the system at this point. If this happens, depress the Windows logo key (on some keyboards it may have an icon of a house instead) to display the Start menu. Depress the right arrow key once and then depress Enter to initiate a proper shutdown. When powered back on, the system should have a functional mouse pointer.

Continue with steps 4-6 in the installation guide.

At the completion of step 5, the Windows Program Compatibility Assistant may appear. Click on “This program installed correctly.”

 

At this point you could optionally install the latest EDIABAS/INPA update (ES-76) from FAL’s EA-90X distribution. I don’t recommend doing so as the latest INPA scripts are in German and not necessary for coding. Installation of the ES-76 update is outside of the scope of this DIY.

You now have the base INPA scripts and configuration files that you’ll need to get the latest version of INPA (5.0.6) up and running. Copy the the INPA CFGDAT and SGDAT folders to removable media for safe keeping. They are located in C:\EC-APPS\INPA.

If your curious, INPA 5.0.2 is operable at this point. If you were to install the K+DCAN drivers from Windows Update, set the cable to COM1, etc. the battery and ignition clamps are working properly.

 

That’s cool, but INPA 5.0.2 and friends are not totally compatible with the latest SP Daten files (i.e. 50.2), so let’s move on to installing BMW Standard Tools 2.12.

Links to BMW Standard Tools 2.12 and NCS Expert profiles can be found in this post:
http://www.e90post.com/forums/showpo…postcount=4476

SP Daten 50.2 can be found in this thread:
http://www.e90post.com/forums/showthread.php?t=882353

Blow away your previous installation of Windows and start over with a fresh install. INPA 5.0.2 and friends made changes to the Windows registry, etc. Now that we have the two folders needed to bootstrap INPA 5.0.6, it’s best to reinstall Windows. If your installing from pre-SP1 Windows 7 media, don’t forget to install the System Update Readiness Tool (KB947821) and Windows 7 Service Pack 1 (KB976932.) In addition, because this will hopefully be your final re-installation of Windows  I suggest that you manually install one additional Microsoft update:

Microsoft .NET Framework 4.5.1:
http://www.microsoft.com/en-us/downl….aspx?id=40779

When the K+DCAN cable is initially plugged in, Windows will indicate that the device driver was not successfully installed.

 

Click on the white box circled above when it appears to change the driver update settings.

 

Click on “Change setting.”

 

Select “Always install the best driver software from Windows Update” then click on “Save Changes.”

 

Windows Update will install the latest FTDI drivers needed for the one stop electronics.com K+DCAN cable. Notice that the FTDI driver has defaulted to USB Serial Port COM3. You need to change this to COM1. Click on “Close.”

 

Click on the Windows Start button to display the Start menu. In the Start Search box type the following command and depress Enter to launch Device Manager:

Code:

mmc devmgmt.msc

 

When Device Manager opens, click on the arrow to the left of “Ports (COM & LPT)” to expand the Ports device tree. Double-click on “USB Serial Port (COM3)” to open the device properties.

 

Click on the “Port Settings” tab and then click on the “Advanced” button to display the Advanced Settings for COM3.

 

Change the COM Port Number to COM1 and the Latency Timer to 1 msec and click “OK.”

 

The USB Serial Port should be set to COM1. Close Device Manager.

Install BMW Standard Tools 2.12. Accept the defaults and click “Next.”

 

When prompted to select additional tasks, de-select the “Execute backup and restore wizard” selections under Data backup. You don’t have an existing installation of BMW Standard Tools to backup. Click “Next.”

 

Click “OK” to acknowledge that the backup wizard has been deactivated.

 

When the Hardware Interface Settings screen appears, select “USB to serial adapter” then click “Next.”

 

Click “Finish” to complete the BMW Standard Tools setup and restart your computer.

Please note: This section of the DIY could be improved for neophyte Windows users. It assumes that you understand command line syntax. In this context, X: denotes an unknown drive letter (i.e. the USB thumb drive that you saved your INPA CFGDAT and SGDAT folders to.) For example, if in Windows Explorer under Computer your USB thumb drive is denoted as Drive E:, then you should use E: instead.

Code:

C:\Users\808>copy E:\CFGDAT\*.ENG C:\EC-APPS\INPA\CFGDAT /v14 file(s) copied.

If you chose to store the CFGDAT folder in another folder named MyStuff, then you would have to include MyStuff in the source path.

Code:

C:\Users\808>copy E:\MYSTUFF\CFGDAT\*.ENG C:\EC-APPS\INPA\CFGDAT /v14 file(s) copied.

The drive letter and path to the source file(s) is dependent on where you stored the files.

Click on the Windows Start button to display the Start menu. In the Start Search box type the following command. Right click on the Windows Command Processor (cmd) under Programs and select Run as administrator.

Code:

cmd

When the User Account Control dialog box appears, select Yes to allow the Windows Command Processor to make changes to your computer.

Copy the Windows ActiveX control MSFLXGRD.OCX to C:\WINDOWS\SYSTEM32 and manually register it.

 

Copy the Windows ActiveX control RICHTX32.OCX to C:\WINDOWS\SYSTEM32 and manually register it.

 

Overwrite the INPA initialization file in the C:\EC-APPS\INPA\CFGDAT folder with the INPA.INI from your saved CFGDAT folder.

Code:

C:\>copy X:\CFGDAT\INPA.INI C:\EC-APPS\INPA\CFGDAT /v /y1 file(s) copied.

Copy the INPA scripts and configuration files from your saved CFGDAT and SGDAT folders.

Code:

C:\>copy X:\CFGDAT\*.ENG C:\EC-APPS\INPA\CFGDAT /v14 file(s) copied.C:\>copy X:\SGDAT\*.IPO C:\EC-APPS\INPA\SGDAT /v468 file(s) copied.C:\>copy X:\SGDAT\*.SRC C:\EC-APPS\INPA\SGDAT /v11 file(s) copied.C:\>copy X:\SGDAT\*.TXT C:\EC-APPS\INPA\SGDAT /v2 file(s) copied.

Copy the group files from the SP Daten E89 folder to C:\EDIABAS\ECU.

Code:

C:\>copy X:\E89\ECU\*.GRP C:\EDIABAS\ECU /v80 file(s) copied.

Import your daten files into WinKFP using this guide (steps 2-8):
WinKFP Import.pdf

Create a C:\NCSEXPER\DATEN\E89 folder and copy the contents of the E89\DATEN folder into it.

Code:

C:\>mkdir C:\NCSEXPER\DATEN\E89C:\>copy X:\E89\DATEN\*.* C:\NCSEXPER\DATEN\E89 /v430 file(s) copied.

Copy the contents of the E89\SGDAT folder to C:\NCSEXPER\SGDAT.

Code:

C:\>copy X:\E89\SGDAT\*.* C:\NCSEXPER\SGDAT /v224 file(s) copied.

Go to the E89\DATEN directory and execute the LADEN.BAT script.

Code:

C:\>cd X:\E89\DATENX:\E89\DATEN>laden.bat

You’ll receive errors at the end of the script due to the missing C:\EC-APPS\CARSERVER directory, ignore them.

Install the patched 32-bit NCS Expert from this thread:
http://www.e90post.com/forums/showthread.php?t=832476

Example:

Code:

rename C:\NCSEXPER\BIN\NCSEXPER.EXE NCSEXPER.OLDrename C:\NCSEXPER\CFGDAT\NCSEXPER.TXT NCSEXPER.GERcopy NCSEXPER.EXE C:\NCSEXPER\BIN /vcopy NCSEXPER.TXT C:\NCSEXPER\CFGDAT /v

Copy the NCS Expert profiles to the C:\NCSEXPER\PFL folder.

Example:

Code:

copy *.PFL C:\NCSEXPER\PFL /v

Your done, enjoy!

 

Source: http://obd365.blogrip.com/2016/03/08/install-bmw-standard-tools-2-12-on-win7-32bit/ (guides with pictures)

 

 

bmw inpa windows 7 64bit

  1. Buy a cable
    I purchased a USB cable from china, it came with software but I didn’t use it and instead used online resources that I downloaded for which I’ll provide links. The cable I purchased is a USB to OBD2 connector that plugs into your BMW to the right hand side of the steering wheel, in the foot-well area.This is the specific cable that I purchased and that I can confirm works:

http://www.obdii365.com/wholesale/bmw-inpa-k-can-with-ft232rq-chip.html

 

  1. Download the software

There are many sources on the internet for INPA/EDIABAS, some seem to work, others do not – I used these specific downloads and they worked perfectly:

 

** UNFORTUNATELY THE DOWNLOAD LINKS ARE NO LONGER AVAILABLE – BUT I WILL SEE WHAT I CAN DO **

 

If for any reason the above links are missing/broken, PM me and I’ll see what I can do. Thank you to whomever is hosting the above files and I hope that you do not mind me providing these links.

 

  1. Setup/Configure your OBD2 USB Cable

Put the DVD that arrived with the cable into the DVD drive on your PC.

Plug in the cable into a USB port on your computer, you must ONLY use this USB port from here-on for this cable. If your computer is connected to the internet it should automatically search and install in the USB cable drivers. If your computer does NOT automatically detect the cable, you may need to use ‘Device Manager’ to manually update/select the driver.

Once installed, go to Control Panel -> System -> Then click on the Hardware tab, then click on Device Manager.

Locate the entry ‘USB Serial Port’ in the ‘Ports’ section of Device Manager. It should read ‘USB Serial Port (COMX)’.

Right-click on the above and select ‘Properties’, then click on the ‘Port Settings’ Tab and then click on ‘Advanced’.

Change the ‘Com Port Number’ entry to ‘COM1’.

Change the ‘Latency Timer (msec)’ to ‘1’.

Click on ‘OK’ and close all the windows, restart your PC to confirm all the changes.

 

  1. Install INPA/EDIABAS 6.4.3 and 4.4.7

Extract the contents of the downloaded file ‘INPA-6.4.3-full.rar’ and you’ll find a .NRG file. This is a CD image that you’ll need to either burn to a CD or extract to a folder using a tool such as ISOBuster.

Once extracted, go into the following folder ‘/REFERENZ/INSTALL/’, right-click on ‘INSTPROG.exe’ and select ‘Properties’, click on the Compatibility tab and change the dropdown to Windows XP SP3 as the Compatibility Mode, also tick ‘Run As Administrator’, then click ‘Ok’, then double-click the file to run the installation.

Select ‘English’ as the language and click ‘Next’.

Select ‘Next’ until asked for ‘Configuration’, scroll to ‘BMW Group Rectification Programs UK’, click ‘Next’.

Tick the option ‘Complete’ for all of the options shown.

Select ‘Next’ and allow the installation to start.

After a minute or so, installation will complete, close the Window.

 

  1. Verify environment variables

Go into Control Panel -> System -> Advanced System Settings.

Select ‘Environment Variables’ and then verify that the System Variables ‘TMP’ and ‘TEMP’ both contain the path ‘C:\EDIABAS\Bin’ within the ‘Value’ string – for instance “C:\Windows\Temp;C:\EDIABAS\Bin”.

 

  1. Prepare Installation Files

Extract the contents of the downloaded file ‘INPA_502_Updated.rar’.

You’ll use the contents of this archive during the next three steps.

 

  1. Install BMW Tools

From the above extracted file set, find the file ‘Step 1_ Install BMW Tools.exe’, right-click on it and select ‘Properties’.

Click on the Compatibility tab and change the dropdown to Windows XP SP3 as the Compatibility Mode, also tick ‘Run As Administrator’, then click ‘Ok’

Double-click on the above file to start the installation.

Set the Destination Path C:\BMW Tools (Don’t change this path) -> ‘Install’ -> ‘OK’.

Select ‘English’ -> ‘Continue’ -> ‘Continue’.

Select ‘C:’ -> ‘Continue’.

Select ‘Skip’ -> ‘Next’

Accept the defaults for programs to update, then click ‘Next’.

Select ‘Com1’, ‘OBD’ and ‘USB to Serial Adapter’ -> ‘Continue’ -> ‘Continue’.

The installation will begin and complete.

 

  1. Install INPA/EDIABAS 6.4.7 and 5.0.2

From the above extracted file set, double-click the file ‘Step 2_ Install INPA.exe’.

The Destination Path should be ‘C:\temp’, leave as it is and click ‘Next’.

Choose ‘English’ and select ‘Continue’ and ‘Continue’.

Select ‘C:\’ and then ‘Continue’.

Select ‘BMW Group Rectification Programs UK’ and click ‘Continue’.

Tick ‘Update’ for all options where not grayed out, then ‘Continue’.

Select ‘OBD’, then ‘Continue’ and ‘Continue’.

The installation will begin and complete.

 

  1. Install OBD Setup

From the above extracted file set, double-click the file ‘Step 3_Final Update.exe’.

The Destination Path should be left as it is, then select ‘Install’.

Select ‘Yes to all’.

Once completed, the window will close itself.

 

  1. Complete Installation

From the above extracted file set, double-click the file ‘serial port.reg’.

When prompted, select ‘Yes’ and ‘Yes’. You will receive confirmation that your registry has been updated.

Locate the file ‘C:\EDIABAS\Bin\obd.ini’ and copy this file into your Windows folder.

Edit the file ‘C:\EC-APPS\INPA\CFGDAT\INPA.INI’ in Notepad, locate the section that starts with ‘//F3’, remove the slashes at the beginning of the three lines of text, and amend any instance of ‘F10’ to ‘E46’.

 

Reference:

http://blog.obdii365.com/2016/10/01/inpa-5-02-and-ediabas-6-4-7-win7-installation/

 

 

bmw inpa windows 8

writing this to help others achieve INPA on their Windows 8.1 64bit laptop.
I’ve done it, verified it works.

FYI The installation of the first package will be in C:\ so you know

I’ll be hosting it on my dropbox for a little, if someone can mirror it, I would be grateful.

First download this INPA package.

https://www.dropbox.com/s/mn6n4bhej8…_INPA.rar?dl=0

unzip, go to programinstallation\setup.exe , run it in xp compatability mode press next all the way through then reboot
once rebooted go back into the unzipped folder, go to referenz2006 and then run the exe in that folder. choose english and then UK preferences , only update the first two. complete it.
No need for reboot

Next you need the e39.eng and e39.ger files to place in your INPA\CFGDAT

https://www.dropbox.com/s/ufov0h935y…FGDAT.rar?dl=0

this is CFGDAT zip , take the e39.eng e39.ger from this and place it in the folder above.

here is the e39 sp daten files. replace the ECU folder in the ediabas folder , replace the daten CFGDAT and SGDAT in the NCSEXpert folder with the ones from the zip.

https://www.dropbox.com/s/w8v1b8ysm2x7t5v/E39.rar?dl=0

Go into INPA\CFGDAT and double click inpa.ini , change any of the lines you wish to represent which F button it corresponds with “E39” for all three lines . FYI our S62 engine is hidden nicely under shift + f9 for old models under e52. You can also use the e39 profile under Shift + f9 for old models if you don’t want to edit your INI file
Example :
F6 = E39
F6_Text = E39
F6_ARCHIV = SGBD_E39

save it close it run inpa enjoy!

Feedback needed incase i missed a step, thanks!

Edit: If i’m missing any files let me know, i sort of want to revive the whole INPA tutorials since there aren’t any written for 8.1

 

EIDT: If the error pops up when try to program:

[22:21:59.916] [2014-07-01] [<WinKFP Tool] 2089 PABD/CABD 06FLASH Programmieren 2538

[22:21:59.916] [2014-07-01] [<WinKFP Tool] switching programming mode failed 10FLASH, DIAGNOSE_MODE (ECUPM): ERROR_ECU_SECURITY_ACCESS_DENIED__SECURITY_ACCESS_ REQUESTED

 

[22:22:07.279] [2014-07-01] [<WinKFP Tool] 2089 PABD/CABD 06FLASH Programmieren 2812

[22:22:07.279] [2014-07-01] [<WinKFP Tool] switching programming mode failed 10FLASH, DIAGNOSE_MODE (ECUPM): ERROR_ECU_CONDITIONS_NOT_CORRECT_OR_REQUEST_SEQUEN CE_ERROR

 

[22:22:07.328] [2014-07-01] [<WinKFP Tool] 2089 Error COAPI2.CPP coapiRunCabd 6

[22:22:07.328] [2014-07-01] [<WinKFP Tool] switching programming mode failed SG_PROGRAMMIEREN

 

[22:22:07.329] [2014-07-01] [<WinKFP Tool] 2089 Error COAPIKF.CPP coapiKfProgSgD2 19

[22:22:07.329] [2014-07-01] [<WinKFP Tool] switching programming mode failed

 

SOLVED…

just in-case someone else stumbles upon this with the same problem.

Check your settings, in device manager, set com port to 1 and latency to 1. check your ediabase.ini is set to Interface =STD:OBD

check your obd.ini is set to Port=Com1

Hardware=USB

 

then reboot. I had all those setting correct and the cable was communicating through IPNA. The reboot fixed it. the alpina b3 flash is the titties!

 

 

bmw inpa windows 10

Note: It’s a customer solution! Try on your own risk

install the drivers for INPA K+D-CAN cable (version with FTDI FT232RL chip only)

disconnect from the Internet because it is possible that the drivers are installed from Windows Update (if you want to use the latest home FTDICHIP then disconnect or reinstall)

why run the executable CDM 21216_setup.exe; It is compatible with 64-bit versions of Windows 7,

If necessary, you can download the latest version according to the OS on the site FTDICHIP
http://www.ftdichip.com/Drivers/VCP.htm

This is an interface / cable VCP (Virtual COM Port) so there are two features and therefore an installation in 2 phases if done manually

1 – Cable driver
2 – VCP driver

if using the automatic executable (.exe) offered on the site, then the 2 self install a result it’s easier and without going through the Device Manager =>
then plug the INPA cable into a USB port

NOTE WELL PORT IDENTIFY THIS CAR ALONE WILL WORK AFTER SETTING IT WILL THEREFORE ALWAYS CONNECT THE CABLE ON THE PORT

in Device Manager there will be a new entry: “COM and LPT ports” / sérial USB Port (COM3) eg for now

Then you must configure the port that will emulate the virtual COM port 9 (eg. Default for Ediabas 7.3 patched) but it’s tune to your install

Open Device Manager, choose COM Ports / USB serial port / port settings / advanced / set “COM 9” and the latency to “1”

finally install BMW Standard Tools, all versions are not compatible with win 7 and 64-bit architectures, so use the BMW STD Tools version 2.12, which includes a recent version INPA 5.0.6 and 7.3.0 Ediabas.

 

Here go cases… Running inpa software on BMW E46, E90

INPA on BMW E46

Purpose: reset BMW E46 airbag light

Tools for use:

The E46 is before 2000 without the OBD2 port and the DLC port is a round 20 pin connector whileINPA cable has only 16 pin connector, so I need a 20 pin to 16 pin connector

INPA-K-DCAN-BMW-E46-airbag-reset-DLC-port-1

The DLC port location on BMW E46:

bmw-dlc

Test procedure:

Run INPA software on WIN XP. Turn on the ignition and click the “F2” button. And choose “Body” section then “Airbag”.

INPA-K-DCAN-BMW-E46-airbag-reset-3

Go to the Error Memory: click the “F4” button.

INPA-K-DCAN-BMW-E46-airbag-reset-4

Go to clear error memory: click the “F2” button.

INPA-K-DCAN-BMW-E46-airbag-reset-5

Error was cleared!

reset BMW E46 airbag light successfully!

INPA-K-DCAN-BMW-E46-airbag-reset-6

inpa bmw e90

Purpose: Code BMW E90 (2008) Injector

Tools to use: k+dcan cable

Test process:

connect the INPA cable with my E90 N54 via OBD port

run INPA software. And pressed F9 on the keyboard to select vehicle model E90

BMW-INPA-software-1

select Engine option -> MSD80 concerning option

BMW-INPA-software-2

press F9 system diagnostic

BMW-INPA-software-3

press [shift+F4] EOL injector option

BMW-INPA-software-4

The interface of MSD80 injector coding program, Check the injector parameters

BMW-INPA-software-5

copy and paste the injector code and pressed OK to continue

Notice that the injector code are stamped onto the injector in white, there will be 2 rows of 3 numbers, for example, here: 582 227

BMW-INPA-software-6

BMW-INPA-software-7

Finally check the injector value and press [clear] to reset it.

http://blog.obdii365.com/2017/01/18/bmw-inpa-download-install-on-windows-xp-vista-7-8-10/

Change BMW Navigation Display Language by Ncs expert

This is step-by-step guide on how to use BMW INPA K+DCAN cable to change E60 navigation language, running with bmw software inpa, ncs expert and ncs dummy.

 

Purpose:

to change bmw navigation display language

 

Car:

BMW E60 LCI ANNEE 2007

 

To change the navigation language for free:

Only Italian, Dutch, English available in iDrive menu if using this method

bmw-e60-navigation-language-change-1

bmw-e60-navigation-language-change-2

bmw-e60-navigation-language-change-3

bmw-e60-navigation-language-change-4

bmw-e60-navigation-language-change-5

bmw-e60-navigation-language-change-6

Using K+DCAN cable to change E60 navigation language display:

First: check the battery and ignition status in INPA

Connect K+DCAN cable to the car and car

inpa-cable-check-igintion-1

(the port is close to the left front door, near the the steering wheel)

Run INPA on Windows xp system

inpa-cable-check-igintion-2

Check the battery and ignition is on

inpa-cable-check-igintion-3

Then quit inpa software

 

Next, Run NCS Expert

Go to the menu bar, select File-> Load file

ncs-expert-change-navigation-language-1

Select Revtor’s NCS Expert Profile

ncs-expert-change-navigation-language-2

Click on FG/ZCS/FA (F1)

ncs-expert-change-navigation-language-3

Then ZCS/FA.. (F3)

ncs-expert-change-navigation-language-4

Select E60, then CAS

ncs-expert-change-navigation-language-5

ncs-expert-change-navigation-language-6

Click on Zuruck (F6), and get the info

ncs-expert-change-navigation-language-7

Then click on SG bearbeiter (F4)

Then CAPPL

ncs-expert-change-navigation-language-8

ncs-expert-change-navigation-language-9

ncs-expert-change-navigation-language-10

Then click on SG auslesen (F4), and get the new info

ncs-expert-change-navigation-language-11

ncs-expert-change-navigation-language-12

Then, run Run Ncs Dummy

Select module (it’s read by ncs expert)

ncsdummy-navi-language-setup-1

Browse for FSW/PSW or Nettodate trace 1 (it’s PSW_PSW.TRC)

ncsdummy-navi-language-setup-2

Page down for SPRACHEN – Languages

ncsdummy-navi-language-setup-3

Here, take French. Select FSW_PSW.MAM

ncsdummy-navi-language-setup-4

Then close NcsDummy and will pop up message: trace manipulation file “FSW_PSW.MAM” is not empty. It’s recommended to empty this file after coding. Do you want to empty the file?

Click on Cancel

get the Job Name info

ncsdummy-navi-language-setup-5

Click on Job andern (F2) in NcsDummy

Select the job name

ncsdummy-navi-language-setup-6

ncsdummy-navi-language-setup-7

Click on Job ausfuhrer (F3)

ncsdummy-navi-language-setup-8

ncsdummy-navi-language-setup-9

Click on Zuruck (F6) and close the interface

 

Finally, Check the navigation language

it’s French as the setup just now

bmw-e60-navi-language-change-1

bmw-e60-navi-language-change-2

http://blog.obdii365.com/2016/11/18/change-bmw-navigation-language-by-ncs-expert-k-dcan/

INPA K+DCAN with FT232RQ Chip & Switch

Some BMW INPA K+DCAN USB interface user reported that the INPA cable build with FT232RL chip failed to diagnose K-line BMW. The new BMW INPA K+DCAN INPA Ediabas cable with FT232RQ chip and switch has newly rolled out to solve this issue.

The new BMW INPA Ediabas cable works on BMW with 8 pin and with K-LINE protocol.

Interface USB OBD2 for BMW – INPA/Ediabas – K+DCAN allows full diagnostic of BMW from 1998 to 2008 (all functions as in OMNITEC interface). Build in 2 lines K and D-Can magisterial.

BMW INPA K+CAN Features:

1. Read and delete errors
2. Adaptations
3. Driver programming
4. Applu coding
– And others…

BMW INPA K+CAN Supports Protocols

* Fast magisterial D-CAN and PT-CAN (500 kbit/s)
* Slow magisterial K-CAN (100 kbit/s)
* Standard BMW protocol (BMW OBD interface).

D-CAN for

* E60, E61 od 03/2007
* E83 od 09/2006
* E81, E87 od 03/2007
* E90, E91, E92, E93 od 03/2007
* E70 (new model X5)
* R56 (new model MINI)

PT-CAN, K-CAN – fully switchable speed of magisterial CAN – you can diagnose driver without any car

Protocol “BMW OBD interface” for Older Cars

* From 1995 to 1998 (don’t need K-line).
* From 1998 to 03/2008 (all models)

New INPA cable PCB picture attached:

How to install BMW Standard Tools 2.12 on Win7 32bit

Here is a very very detail instruction on how to set up BMW Standard Tools 2.12 on Windows 7×86 (32-bit). The guide helped successfully coded my 2009 E92.

This DIY describes how to capture the latest English metric INPA scripts and configuration files from INPA 5.0.2 and manually integrate them along with SP Daten 50.2 for a fully functional installation of BMW Standard Tools 2.12. This approach is necessary for 3 reasons. 1) BMW Standard Tools includes INPA, but it does not contain any INPA scripts or configuration files. 2) The latest INPA scripts are in German which is why we preserve the English scripts from INPA 5.0.2. 3) The latest SP Daten files are German metric and do not work properly with INPA 5.0.2 and friends.

BMW Standard Tools 2.12 includes INPA 5.0.6 for diagnostics, NCS-Expert 4.0.1 for coding, WinKFP 5.3.1 for flash reprogramming, and a host of other BMW Group plant support tools. The software was not intended to be used by your neighborhood BMW dealer. There is also a development release of BMW Standard Tools which includes PAFMaker, SWE-Generator, XBD-Generator, Muster-PABD, P-SGBD, etc. and supports Vector CAN interfaces. The development release is outside the scope of this DIY.

The software is complicated and requires a significant effort to understand. If your technically astute, comfortable with Microsoft Windows administrative tasks, and want to learn to manually install the software and integrate the SP Daten files on which it depends, this is the right DIY for you.

This DIY is not intended to be the “easy button.” If you want a mixture of BMW software, third-party software and data files of unknown origins pre-configured for you because your in a rush to try your new cable, look elsewhere. There are even forum members who can assist you remotely for a “donation.”

I am not an expert, nor did I provide the software. ECU coding and flash reprogramming come with inherent risks, there is always the possibility of catastrophic failure. Your car should always be attached to a microprocessor controlled charger that adapts to the cars current draw and supplies constant, clean power. (i.e. Don Schumacher Racing INC-700A) Please refer to the OSS applications documentation (page 8) for BMW Group recommended charger specifications:

If you understand the inherent risks and agree with the above disclaimer, proceed with caution.

TESTED USE CASES

INPA 5.0.6:

  • MSD80 / MSD81 fuel injector volume calibration
  • Register new battery and reset histogram
  • Read and clear MSD80 / MSD81 history memory
  • Display plant, dealer, and backup integration levels
  • Display UIF data for all control modules (module name and address, ZB number, VIN number, date of last flash)
  • Display gearbox control unit (TCU) analog values (engine/gearbox temperature, turbine speed, accelerator pedal angle, etc.)

NCS-Expert 4.0.1:

  • Battery retrofit (flooded to AGM); updated VO and default coded CAS
  • Enable digital speedometer
  • Enable fog lights to remain on when high beams are flashed
  • Disable door chime when ignition is off and key fob is inserted
  • E92 corner bulb delete

WinKFP 5.3.1:

  • Flash reprogramming of ZF 6HP21 TCU

Rheingold ISTA 3.40.30/3.41.10:

  • Leverages BMW Standard Tools 2.12 EDIABAS interface for vehicle diagnosis, no ISIS workshop server required (outside the scope of this DIY)

KNOWN LIMITATIONS

INPA

  • MEVD17.2 DME and N55 engine not supported, E90 German language development script required (outside the scope of this DIY)
  • DDE 7.3 and M57 engine not supported, E90 German language development script required (outside the scope of this DIY)
  • 2009+ electronic fuel pump control module (EKPM3) not supported (HW-NR 7276383), F30 German language development script required (outside the scope of this DIY)
  • GS40 DCT gearbox control unit (TCU) not supported, German language development script required (outside the scope of this DIY)
  • Language variant and version mismatch errors will be displayed and can be safely ignored. When you integrate the German metric ECU description files and group files from the SP Daten, the language variants do not match and the ECU description files are newer than anticipated.

This DIY was tested with Windows 7 Home Premium Service Pack 1 (SP1) running on a circa 2008 Lenovo S10 netbook with a INPA K+DCAN cable from one stop electronics.com. My netbook is used solely for coding and as such this DIY assumes that your computer is dedicated to this purpose as well.

BMW-stanard-tool-win7-32bit-1

I recommend starting with a fresh 32-bit Windows 7 installation in order to collect the necessary INPA 5.0.2 configuration files that you will need after installing BMW Standard Tools 2.12. I suggest disabling Windows Update automatic updates during the Windows 7 installation process. After entering your product key, the following screen will appear:

BMW-stanard-tool-win7-32bit-2
Select “Ask me later”, this will prevent Windows 7 from automatically installing any updates.

If your installing from pre-SP1 Windows 7 media, I highly recommend that you manually install two Microsoft updates:

System Update Readiness Tool (KB947821):
http://www.microsoft.com/en-us/downl…s.aspx?id=3132

Windows 7 Service Pack 1 (KB976932):
http://www.microsoft.com/en-us/downl…s.aspx?id=5842

During testing pre-SP1 Windows 7 no longer displayed a mouse pointer after successfully installing EDIABAS & WinKFP and rebooting the system.

INPA 5.0.2 can be found here:

INPA-EDIABAS full English Edition

Installation Guide

Follow steps 2 through 6 of the installation guide. During the EDIABAS & WinKFP install (step 3), select Windows XP (this is not mentioned in the installation guide.) For all other selections, accept the default and click Weiter which is German for “further.”

BMW-stanard-tool-win7-32bit-3

The very first time you attempt to install EDIABAS & WinKFP (step 3), regsvr32 will fail to register two Windows ActiveX controls. This is normal, upon re-installation everything will work properly.

BMW-stanard-tool-win7-32bit-4

Click on OK and then click on the large red circle with a white X at the bottom of the screen to see the second regsvr32 error.

BMW-stanard-tool-win7-32bit-5

Click on OK to acknowledge the second error.

BMW-stanard-tool-win7-32bit-6

Press any key to exit the EDIABAS OBD setup program. Don’t be concerned about any registry key warnings, this installation of EDIABAS will never be used.

BMW-stanard-tool-win7-32bit-7

When prompted to reboot, select Nein for “No” and then click on Beenden or “End” to exit the installation program. Go to Control Panel and uninstall the program.

BMW-stanard-tool-win7-32bit-8

Once you have uninstalled the program, reinstall it. On the second attempt, the ActiveX controls will register properly.

BMW-stanard-tool-win7-32bit-9

BMW-stanard-tool-win7-32bit-10

This time, select Ja for “Yes” and reboot.

BMW-stanard-tool-win7-32bit-11

Even with SP1 installed, on occasion the system will no longer display a mouse pointer after rebooting the system at this point. If this happens, depress the Windows logo key (on some keyboards it may have an icon of a house instead) to display the Start menu. Depress the right arrow key once and then depress Enter to initiate a proper shutdown. When powered back on, the system should have a functional mouse pointer.

Continue with steps 4-6 in the installation guide.

At the completion of step 5, the Windows Program Compatibility Assistant may appear. Click on “This program installed correctly.”

BMW-stanard-tool-win7-32bit-12

At this point you could optionally install the latest EDIABAS/INPA update (ES-76) from FAL’s EA-90X distribution. I don’t recommend doing so as the latest INPA scripts are in German and not necessary for coding. Installation of the ES-76 update is outside of the scope of this DIY.

You now have the base INPA scripts and configuration files that you’ll need to get the latest version of INPA (5.0.6) up and running. Copy the the INPA CFGDAT and SGDAT folders to removable media for safe keeping. They are located in C:\EC-APPS\INPA.

If your curious, INPA 5.0.2 is operable at this point. If you were to install the K+DCAN drivers from Windows Update, set the cable to COM1, etc. the battery and ignition clamps are working properly.

BMW-stanard-tool-win7-32bit-13

BMW-stanard-tool-win7-32bit-14

That’s cool, but INPA 5.0.2 and friends are not totally compatible with the latest SP Daten files (i.e. 50.2), so let’s move on to installing BMW Standard Tools 2.12.

Links to BMW Standard Tools 2.12 and NCS Expert profiles can be found in this post:
https://mega.co.nz/#!HBxi3CTa!AyhnTQTrMv6kQ3E0OJ8CTCuPU1tHfRVQ2wYF5H8J4ek
SP Daten 50.2 can be found in this thread:
https://mega.co.nz/#F!nshRWaLA!NbXQSw7903FIt0JdU81zCA
Blow away your previous installation of Windows and start over with a fresh install. INPA 5.0.2 and friends made changes to the Windows registry, etc. Now that we have the two folders needed to bootstrap INPA 5.0.6, it’s best to reinstall Windows. If your installing from pre-SP1 Windows 7 media, don’t forget to install the System Update Readiness Tool (KB947821) and Windows 7 Service Pack 1 (KB976932.) In addition, because this will hopefully be your final re-installation of Windows  I suggest that you manually install one additional Microsoft update:

Microsoft .NET Framework 4.5.1:
http://www.microsoft.com/en-us/downl….aspx?id=40779

When the K+DCAN cable is initially plugged in, Windows will indicate that the device driver was not successfully installed.

BMW-stanard-tool-win7-32bit-15

Click on the white box circled above when it appears to change the driver update settings.

BMW-stanard-tool-win7-32bit-16

Click on “Change setting.”

BMW-stanard-tool-win7-32bit-17

Select “Always install the best driver software from Windows Update” then click on “Save Changes.”

BMW-stanard-tool-win7-32bit-18

Windows Update will install the latest FTDI drivers needed for the K+DCAN cable. Notice that the FTDI driver has defaulted to USB Serial Port COM3. You need to change this to COM1. Click on “Close.”

BMW-stanard-tool-win7-32bit-19

Click on the Windows Start button to display the Start menu. In the Start Search box type the following command and depress Enter to launch Device Manager:

Code:
mmc devmgmt.msc

BMW-stanard-tool-win7-32bit-20

When Device Manager opens, click on the arrow to the left of “Ports (COM & LPT)” to expand the Ports device tree. Double-click on “USB Serial Port (COM3)” to open the device properties.

BMW-stanard-tool-win7-32bit-21

Click on the “Port Settings” tab and then click on the “Advanced” button to display the Advanced Settings for COM3.

BMW-stanard-tool-win7-32bit-22

Change the COM Port Number to COM1 and the Latency Timer to 1 msec and click “OK.”

BMW-stanard-tool-win7-32bit-23

The USB Serial Port should be set to COM1. Close Device Manager.

Install BMW Standard Tools 2.12. Accept the defaults and click “Next.”

BMW-stanard-tool-win7-32bit-24

When prompted to select additional tasks, de-select the “Execute backup and restore wizard” selections under Data backup. You don’t have an existing installation of BMW Standard Tools to backup. Click “Next.”

BMW-stanard-tool-win7-32bit-25

Click “OK” to acknowledge that the backup wizard has been deactivated.

BMW-stanard-tool-win7-32bit-26

When the Hardware Interface Settings screen appears, select “USB to serial adapter” then click “Next.”

BMW-stanard-tool-win7-32bit-27

Click “Finish” to complete the BMW Standard Tools setup and restart your computer.

Please note: This section of the DIY could be improved for neophyte Windows users. It assumes that you understand command line syntax. In this context, X: denotes an unknown drive letter (i.e. the USB thumb drive that you saved your INPA CFGDAT and SGDAT folders to.) For example, if in Windows Explorer under Computer your USB thumb drive is denoted as Drive E:, then you should use E:instead.

Code:
C:\Users\808>copy E:\CFGDAT\*.ENG C:\EC-APPS\INPA\CFGDAT /v
14 file(s) copied.

If you chose to store the CFGDAT folder in another folder named MyStuff, then you would have to include MyStuff in the source path.

Code:
C:\Users\808>copy E:\MYSTUFF\CFGDAT\*.ENG C:\EC-APPS\INPA\CFGDAT /v
14 file(s) copied.

The drive letter and path to the source file(s) is dependent on where you stored the files.

Click on the Windows Start button to display the Start menu. In the Start Search box type the following command. Right click on the Windows Command Processor (cmd) under Programs and select Run as administrator.

Code:
cmd

BMW-stanard-tool-win7-32bit-28

When the User Account Control dialog box appears, select Yes to allow the Windows Command Processor to make changes to your computer.

Copy the Windows ActiveX control MSFLXGRD.OCX to C:\WINDOWS\SYSTEM32 and manually register it.

BMW-stanard-tool-win7-32bit-29

Copy the Windows ActiveX control RICHTX32.OCX to C:\WINDOWS\SYSTEM32 and manually register it.

BMW-stanard-tool-win7-32bit-30

Overwrite the INPA initialization file in the C:\EC-APPS\INPA\CFGDAT folder with the INPA.INI from your saved CFGDAT folder.

Code:
C:\>copy X:\CFGDAT\INPA.INI C:\EC-APPS\INPA\CFGDAT /v /y
1 file(s) copied.

Copy the INPA scripts and configuration files from your saved CFGDAT and SGDAT folders.

Code:
C:\>copy X:\CFGDAT\*.ENG C:\EC-APPS\INPA\CFGDAT /v
14 file(s) copied.
C:\>copy X:\SGDAT\*.IPO C:\EC-APPS\INPA\SGDAT /v
468 file(s) copied.
C:\>copy X:\SGDAT\*.SRC C:\EC-APPS\INPA\SGDAT /v
11 file(s) copied.
C:\>copy X:\SGDAT\*.TXT C:\EC-APPS\INPA\SGDAT /v
2 file(s) copied.

Copy the group files from the SP Daten E89 folder to C:\EDIABAS\ECU.

Code:
C:\>copy X:\E89\ECU\*.GRP C:\EDIABAS\ECU /v
80 file(s) copied.

Import your daten files into WinKFP using this guide (steps 2-8):
WinKFP Import.pdf

Create a C:\NCSEXPER\DATEN\E89 folder and copy the contents of the E89\DATEN folder into it.

Code:
C:\>mkdir C:\NCSEXPER\DATEN\E89
C:\>copy X:\E89\DATEN\*.* C:\NCSEXPER\DATEN\E89 /v
430 file(s) copied.

Copy the contents of the E89\SGDAT folder to C:\NCSEXPER\SGDAT.

Code:
C:\>copy X:\E89\SGDAT\*.* C:\NCSEXPER\SGDAT /v
224 file(s) copied.

Go to the E89\DATEN directory and execute the LADEN.BAT script.

Code:
C:\>cd X:\E89\DATEN
X:\E89\DATEN>laden.bat

You’ll receive errors at the end of the script due to the missing C:\EC-APPS\CARSERVER directory, ignore them.

Install the patched 32-bit NCS Expert

Example:

Code:
rename C:\NCSEXPER\BIN\NCSEXPER.EXE NCSEXPER.OLD
rename C:\NCSEXPER\CFGDAT\NCSEXPER.TXT NCSEXPER.GER
copy NCSEXPER.EXE C:\NCSEXPER\BIN /v
copy NCSEXPER.TXT C:\NCSEXPER\CFGDAT /v

Copy the NCS Expert profiles to the C:\NCSEXPER\PFL folder.

Example:

Code:
copy *.PFL C:\NCSEXPER\PFL /v

Your done, enjoy!

BMW-stanard-tool-win7-32bit-31

BMW-stanard-tool-win7-32bit-32

BMW-stanard-tool-win7-32bit-33

BMW-stanard-tool-win7-32bit-34

BMW-stanard-tool-win7-32bit-35

www.obdii365.com