[808AWD325xi]

It's been two years since I posted my original DIY based on Windows 7 x86 (32-bit.) In my opinion, Windows 7 x86 will always be the reference platform for BMW Standard Tools 2.12. However, the Windows operating system continues to evolve and since the Windows 8 train wreck is behind us, I decided it was time to update my DIY for Windows 10 x64 (64-bit.) Because Windows 10 was never qualified by the BMW Group, it should be considered an experimental platform.

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.

The software is complicated and requires a significant effort to understand. If you're 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."

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 German metric SP Daten files for a fully functional installation of BMW Standard Tools 2.12. The tools themselves will mostly be in English, however, certain output (i.e. diagnostic trouble code descriptions) will be in German.

This approach is necessary for three reasons:

• BMW Standard Tools 2.12 includes INPA 5.0.6, but it doesn't contain any INPA scripts or configuration files which are necessary for proper operation
• The latest INPA scripts are in German which is why we preserve the English metric scripts from INPA 5.0.2
• The latest SP Daten files are German metric and do not work properly with INPA 5.0.2 and friends

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 the BMW Group recommended charger specifications:
http://www.e90post.com/forums/attach...mentid=691959&

THIS DIY IS PROVIDED “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL I BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DIY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

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

HIGH LEVEL OVERVIEW

• Install a temporary copy of Windows (suggest skipping product key input)
• Install INPA 5.0.2 and save SGDAT and CFGDAT folders to a USB thumb drive for later use
• Re-install a fresh copy of Windows (the INPA 5.0.2 installation process made Windows registry changes and installed programs that are not applicable to modern Windows variants)
• Install BMW Standard Tools 2.12
• Copy INPA scripts and configuration files from the saved CFGDAT and SGDAT folders
• Import SP Daten files with WinKFP and by manually copying files
• Install WinKFP profiles

Please note: Part of the WinKFP import process integrates the SGBD (Steuergeräte Beschreibungsdatei a.k.a. ECU description files (*.PRG) which EDIABAS depends upon. INPA and friends communicate with the car via EDIABAS. That process doesn't only impact WinKFP, it impacts all tools ability to communicate. The DIY was not constructed in such a way to be performed in piece parts, there are strict interdependencies. Don't assume that just because you don't intend to use a particular tool (i.e. WinKFP) that portions of this DIY can be skipped.

TESTED USE CASES

INPA 5.0.6:

• MSD80 / MSD81 fuel injector volume calibration
• Display ZF 6HP automatic gearbox control unit (TCU) analog values (gearbox fluid temperature, turbine speed, etc.)
• Display the UIF (User Information Field) data for all installed modules
• Display the name, SGBD file, group file, and part number for all installed modules
• Display plant, dealer, and backup integration levels

Tool32 4.0.3:

• ZF 6HP automatic gearbox control unit (TCU) program and data flash signature verification
• Display ZF 6HP automatic gearbox control unit (TCU) flash reference data

KNOWN LIMITATIONS

INPA 5.0.6:

• MSD80/MSD81 DME boost pressure control (E90->Engine->MSD80-><F5>status analog/digital-><Shift>+<F4>boost pressure control) and intake pipe model (E90->Engine->MSD80-><F5>status analog/digital-><Shift+<F1>intake pipe model) menus do not work correctly, E90 German language development script required (outside the scope of this DIY)
• 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)
• GS40 DCT gearbox control unit (TCU) not supported, German language development script required (outside the scope of this DIY)
• 2009+ electronic fuel pump control module (EKPM3) not supported (P/N 7276383), F30 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 10 Home and a K+DCAN cable from one-stop-electronics.com. If you purchased a cable from Amazon or eBay, your mileage may vary. A faulty cable can cause a myriad of issues. If you don't own a one-stop-electronics cable, I kindly request that you not clutter this thread with questions and issues related to unproven cables.



I recommend starting with a fresh Windows 10 installation in order to collect the necessary INPA 5.0.2 scripts and configuration files that you will require once you have installed BMW Standard Tools 2.12.

When installing Windows 10, I suggest disabling as many of its controversial data collection tools as possible...caveat emptor !!





On this screen, make sure that you scroll down to access the error and diagnostic data collection setting.





The INPA 5.0.2 download is packaged in a RAR archive. I recommend first downloading the open source 7-Zip archive manager to extract its contents.
http://www.7-zip.org/

Downloading and installing 7-Zip is self explanatory:


Click on the 7-Zip icon on the Windows taskbar to bring 7-Zip to the foreground (in focus) and then click Install.




INPA 5.0.2 can be found here (this site is located in China and download speeds are very slow):
http://www.sinodownloads.com/down/do...pa%20k+can.rar

If you are using the Firefox browser, you may receive a warning similar to the one below. Don't panic.


Per Norton Safe Web (https://safeweb.norton.com/), six files on the site were found to be infected. INPA 5.0.2 is not amongst them:


Once the RAR archive 350517-inpa k+can.rar is downloaded, right click on the file. Click on 7-Zip and then I suggest clicking on Extract to "350517-inpa k+can\". 7-Zip will create a folder in the same location as the RAR archive with the same name. In this example, the RAR archive was downloaded to my Downloads folder (C:\Users\[Username]\Downloads\).



7-Zip extracted the contents of the RAR archive to the folder C:\Users\[Username]\Downloads\350517-inpa k+can\.



Navigate to the folder C:\Users\[Username]\Downloads\350517-inpa k+can\inpa\. Copy the 01_Step1, 02_Step_2, and 03_Step_3 folders to the root of your C: drive (C:\). This is necessary as the old (circa Windows 95) InstallShield 5.50.126.0 (SETUP.EXE) used to install the software has trouble with long filenames and deep folder hierarchies.





Navigate to the folder C:\Users\[Username]\Downloads\350517-inpa k+can\inpa\01_Step1\. Copy the EC-APPS folder to the root of your C: drive. (C:\)



Navigate to the folder C:\01_Step1\NFS\Entpackt\disk1\. Double-click on the SETUP.EXE file to begin the installation process.



When this screen appears, be sure to select Windows XP. For all other selections, accept the default and click Weiter which is German for "further."



regsvr32 will fail to register two Windows ActiveX controls.



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.



Bring the OBDSetup.exe window into focus by clicking on it. Notice the blue lines around the edge which indicate it is in focus. Press any key to exit OBDSetup.exe. 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.



Navigate to the folder C:\02_Step_2\INSTALL\. Double-click on the Instprog.exe file to continue the installation process.



Click OK.



Select English and click Continue.



Click Continue.



Click Continue.



Select BMW Group Rectification programs UK and click Continue.



Under EDIABAS 6.4.3, select Update, under INPA 5.0.1, select Update, and under NCS expert 3.0.8, select Complete. Verify that the language is set to English metric. Click Continue.



Click Continue.



The archive contents will be extracted.



Click End.



Close the File Explorer window.



Navigate to the folder C:\03_Step_3\INSTALL\. Double-click on the Instprog.exe file to continue the installation process.



Click OK.



Select English and click Continue.



Click Continue.



Click Continue.



Select BMW Group Rectification programs UK and click Continue.



Under INPA 5.0.1, select Update, under NCS expert 3.0.8, select Update. Verify that the language is set to English metric. Click Continue.



Click Continue.



The archive contents will be extracted.



Click End.



Close the File Explorer window.



Navigate to the folder C:\Users\[Username]\Downloads\350517-inpa k+can\inpa\. Copy the INPA.INI file to the INPA CFGDAT folder located in C:\EC-APPS\INPA\CFGDAT and overwrite the existing file.




You now have the 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 a USB thumb drive. They are located in the folder C:\EC-APPS\INPA. You will need these two folders to complete the BMW Standard Tools 2.12 installation process. Once you have these two folders, you will never need to install INPA 5.0.2 again.



ADDITIONAL FILES NEEDED TO COMPLETE THE REMAINDER OF THE INSTALLATION PROCESS

A link to BMW Standard Tools 2.12 can be found in xxxjecxxx's NCS-Expert DIY (1st. post):
http://www.e90post.com/forums/showthread.php?t=451145

A link to the English 32-bit version of NCS-Expert can be found in GenePoole's thread (1st. post):
http://www.e90post.com/forums/showth...3#post13879183

The NCS-Expert profiles are attached to this post:
http://www.e90post.com/forums/showpo...postcount=4476

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

I suggest downloading the above mentioned files and saving them to the same USB thumb drive that you copied the INPA CFGDAT and SGDAT folders to.

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 you have the two folders needed to bootstrap INPA 5.0.6, it's best to reinstall Windows.

Once Windows has been reinstalled, prepare to plug in your K+DCAN cable. From this point on, it is important that you always plug the K+DCAN cable into the same USB port as originally inserted prior to each use.

When the K+DCAN cable is initially inserted for the first time, ensure that your system has Internet network connectivity. Windows Update will silently install the latest FTDI drivers needed for the K+DCAN cable to function properly.

Depress the Windows logo key to display the Start menu. In the Start menu search box type the following and depress Enter to launch Device Manager:

device

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 USB Serial Port properties.



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



Change the COM Port Number to COM1 and the Latency Timer to 1 msec and click OK. Click OK again to close the USB Serial Port properties.



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



In this example, Standard_Tools_Setup_2.12.exe was copied from a USB thumb drive to my Downloads folder (C:\Users\[Username]\Downloads\). Right click on the file and select Troubleshoot compatibility.



Click Try recommended settings.



Click Test the program...



Click OK.



Click Next to begin the installation. For all other selections, accept the default 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. Click Next.



When prompted to restart, select No, I will restart the computer later. Click Finish to return to the Program Compatibility Troubleshooter.



Click Next.



Select Yes, save these settings for this program.



Select Close the troubleshooter.



Restart your system.

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 File Explorer under This PC your USB thumb drive is denoted as Drive E:, then you should use E: instead.

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.

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.

Depress the Windows logo key to display the Start menu. In the Start menu search box type the following and right click on the Command Prompt Desktop app. Select Run as administrator to open a Command Prompt window:

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:

C:\WINDOWS\system32>copy C:\EDIABAS\BIN\MSFLXGRD.OCX . /v
C:\WINDOWS\system32>regsvr32 MSFLXGRD.OCX

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

C:\WINDOWS\system32>copy C:\EDIABAS\BIN\RICHTX32.OCX . /v
C:\WINDOWS\system32>regsvr32 RICHTX32.OCX

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

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.

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.

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):
http://www.e90post.com/forums/attach...4&d=1487104475

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

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.

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.

C:\>cd /d 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. When the cmd.exe dialog box appears, click on Continue.



Install the patched 32-bit NCS Expert.

Example:

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:

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

Copy the NFS INFO.GER file to avoid a nuisance error in WinKFP.

Example:

cd C:\EC-APPS\NFS\DATA\GDATEN
copy INFO.GER INFO.ENG /v

Your done, enjoy! If you found this DIY useful, please click on the Appreciate button at the bottom of this post.

[808AWD325xi]

Here my answers to some Frequently Asked Questions, in no particular order. I will update this FAQ over time. This is not intended to replace, but rather augment official BMW Group documentation.

1. What are integration levels? (Also referred to as I-level, I-step, and I-stage)

During development of a given chassis (i.e. E90) and subsequent upgrades and/or fixes, integration levels are defined. An integration level is a defined vehicle configuration from an electrical standpoint (hardware and software) that is validated by BMW. There are three integration level states:

• Plant -- the integration level of the vehicle when it left the factory
• Dealer -- the current integration level
• Backup -- the last integration level

The integration level designation is comprised of the system reference, SOP date (SOP=Start Of Production) and the I-level.

Example: "E89X-13-07-501"

E89X: System reference
13: Year of introduction
07: Month of introduction
501: I-level of the system reference

2. How do I determine the current integration level of my vehicle?

You can display your current (dealer) integration level with INPA...E90 -> Select E90 -> Functional Jobs -> <Shift> + <F2> Vehicle data:


3. Do I need a newer SP Daten to code my vehicle?

That depends upon your current integration level. Integration levels correlate to Progman (older) and ISTA/P software versions (current.) Your integration level tells you the minimum SP Daten needed to code your car. Google bmw group ista/p version and i-level overview and examine a chart. Here is an example from ISTA/P P3.57.0:


Example: If your integration level is "E89X-13-07-501" you would need SP Daten 50.0 at a minimum to code your vehicle. You can always use a newer SP Daten if you wish, but it's not necessary.

4. I'm not sure which SP Daten I have. How I can determine which integration level it supports?

The supported integration level can be found in the KMM database. With Windows Notepad, open the file E89\kmmData\kmm_ETM.txt. This is an example from SP Daten 51.1:

#$This file has been signed. Do not edit.$#
# Erstellt und freigegeben durch VT-T-1 \ Produktmanagement Teile
# KMM Datei E89X zur Datenfreizeichnung E89X-13-07-505_45 Version  Stand 02.09.2013, 10:07:18 / HO

5. How do I determine the part number of an installed module?

You can display the part numbers of all installed modules (and lots of other useful information) with INPA...E90 -> Select E90 -> Functional Jobs -> <F2> Identification:


In some instances, if you search for the part number on RealOEM, it will provide the complete BMW part number.

Example: The part number for my MSD81 DME is 7616431. RealOEM shows that the full part number is 12-14-7-616-431.

6. I want to flash reprogram a module in comfort mode with the WinKFP tool. After pressing <F2> Choose ZUSB or <F3> Update ZUSB, I don't know which ECU family to select. I don't see my module listed...HELP!

Determine the part number of the module you want to flash with WinKFP and then open the file C:\EC-APPS\NFS\DATA\GDATEN\HWNR.DA2 with Windows Notepad and search (Ctrl-F) for the part number. The ECU family name will be in the last column under SG type.

Example: The part number for my EGS module is 7591971. When I search the HWNR.DA2 file, I see that the ECU family name is GKE215:

7591971,0000000,0000000,GKE215

Now when I highlight the GKE215 ECU family in WinKFP, I can see that I have the 2009 & 2010 Alpina B3 flashes available; ZB numbers 7603537 and 7615835:


7. How do I determine the ZB number of the software that my module is currently programmed with?

Display the UIF (User Information Field) data for all installed modules with INPA...E90 -> Select E90 -> Functional Jobs -> <F3> User information field:


The UIF data is only accurate IF UIF writes were enabled in WinKFP when the module was last flashed. If UIF writes were not enabled, then the UIF data is stale.

8. When flash reprogramming a module with WinKFP, do you recommend enabling UIF writes?

No, absolutely not. The UIF data is used by various BMW tools to validate the vehicles integration level. If you flash various modules on an ad-hoc basis with UIF writes enabled, the vehicles configuration will no longer align with any defined integration levels as validated by BMW. This could create a myriad of problems should you ever need to have the vehicles software updated by a BMW dealership.

9. I was told that if I disable UIF writes in WinKFP prior to performing the Alpina B3 transmission flash BMW won't know that I flashed the transmission. Is that true?

No, BMW can easily identify the fact that you flashed the transmission. Even if UIF writes were disabled. When you flashed the transmission with WinKFP, reference data was written to the TCU. Run Tool32 and open the SGDB file C:\EDIABAS\ECU\GS19D.PRG. Execute the job daten_referenz_lesen to display the reference data:


ZB numbers map to WinKFP .0PA files (data set files for program) and .0DA files (data set files for data.) The programming data and logistics files for the TCU are stored in the C:\EC-APPS\NFS\DATA\GKE215 folder. The .0DA file that correlates with your ZB number contains the reference data. Open the GKE215.DAT logistics file with Windows Notepad and search (Ctrl-F) for the ZB number that you used to flash the transmission.

Example: The transmission was flashed with ZB 7603537. Here is an excerpt from the GKE215.DAT file:

7603537,0000000,7591971,A,7603538DA,0FFFFFFFFFD,000,1 8

We see that the .0DA file used to flash the transmission was A7603538.0DA. Open the .0DA file in Windows Notepad to display the reference data.

Here are the first few lines from the A7603538.0DA file:

;============================================
;Austausch-Datei Daten
;============================================
;
;;ZL_System:        GS19.11.0
;;ZL_Projekt:       HZ
;;ZL_Referenz:      0479SA0T641Z1HZ57
;

Notice that the reference data matches what was displayed in Tool32. It is conclusive evidence that the transmission was flashed with ZB 7603537.

10. Why are the various data files collectively referred to as a SP Daten?

SP is an acronym for Servicepakets, which translates to Service Package in English. Daten is German for Data.

11. What programming language are INPA scripts written in?

PABS, an acronym for Prüfablaufbeschreibungssprache, which is German for test sequence description language. PABS is a proprietary, C-like language.

Use of the term script is a misnomer. PABS is not a scripting language, it is a programming language. The compiled source code (IPO file) is executed by the INPA runtime environment and is not interpreted.

[808AWD325xi]

Reserved for future use.

[808AWD325xi]

Reserved for future use...

[808AWD325xi]

Reserved for future use..........

[matteblue3er]

This is a painfully long way to install these tools.

Why don't you just use the BMW Standard Tools 2.12 installer? You don't need to pre-install Ediabas or WinKFP. It does everything for you.

Then you just copy your ECU, daten, config, profile, and scripts to their respective directories and your done.

I just did a W10 install for someone. I had to run the 2.12 install in compatibility mode but it works just fine.

[808AWD325xi]

Originally Posted by matteblue3er

This is a painfully long way to install these tools.

Why don't you just use the BMW Standard Tools 2.12 installer? You don't need to pre-install Ediabas or WinKFP. It does everything for you.

Then you just copy your ECU, daten, config, profile, and scripts to their respective directories and your done.

I just did a W10 install for someone. I had to run the 2.12 install in compatibility mode but it works just fine.

This DIY uses the BMW Standard Tools 2.12 installer. It doesn't assume that the reader has the requisite INPA scripts, SP Daten, NCS-Expert profiles, etc. Therefore, it explains how to obtain the English metric scripts from INPA 5.0.2 prior to installing BMW Standard Tools 2.12.

The remainder of the DIY is as you described...

[Nitrousbird]

Nice. I used your old guide for my Win7 32 bit installation. I just ordered a new Surface Pro and intend for that to be my new coding rig as well.

Since I already have the SGDAT and CFGDAT folders from when I did my Win7 install, can I just reuse them?

[808AWD325xi]

Originally Posted by Nitrousbird

Nice. I used your old guide for my Win7 32 bit installation. I just ordered a new Surface Pro and intend for that to be my new coding rig as well.

Since I already have the SGDAT and CFGDAT folders from when I did my Win7 install, can I just reuse them?

You can absolutely reuse your INPA CFGDAT and SGDAT folders. There is no need to re-install INPA 5.0.2 again. Just skip to the step where you plug in the K+DCAN cable.

Be sure to stop by and let us know how the Surface Pro works in tablet mode !!

[Nitrousbird]

Originally Posted by 808AWD325xi

You can absolutely reuse your INPA CFGDAT and SGDAT folders. There is no need to re-install INPA 5.0.2 again. Just skip to the step where you plug in the K+DCAN cable.

Be sure to stop by and let us know how the Surface Pro works in tablet mode !!

Sweet. That will save me some time.

I should have it installed in about a week. I'm interested to see how well it works with a touch screen.

[devildogae]

Awesome write-up, bookmarked this thread...

[808AWD325xi]

Originally Posted by Nitrousbird

Sweet. That will save me some time.

I should have it installed in about a week. I'm interested to see how well it works with a touch screen.

I messed around very briefly with a tablet running Windows 8 (ugh.) If I recall correctly, I needed to use the on-screen keyboard (osk) to depress the function keys in INPA.

Originally Posted by devildogae

Awesome write-up, bookmarked this thread...

Thanks devildogae !!

[t7wakim]

Thank you for this clear and well explained tutorial! However, is it compatible with V55 SP-Daten instead of V50.2?

[808AWD325xi]

Originally Posted by t7wakim

Thank you for this clear and well explained tutorial! However, is it compatible with V55 SP-Daten instead of V50.2?

Yes, a newer Daten should work fine.

[t7wakim]

Is it possible to update INPA to support F series? Alot of people on YouTube demonstrate diagnosing F series cars using INPA 5.0.6. Is this easy to do?

[808AWD325xi]

Originally Posted by t7wakim

Is it possible to update INPA to support F series? Alot of people on YouTube demonstrate diagnosing F series cars using INPA 5.0.6. Is this easy to do?

Yes, there is an INPA update floating around on the net from 2007 that supports some F-Series; F01, F02, F07, F10, F11, F25, and F30. It supports E90s with the N55 engine as well. All of the INPA scripts are German metric...

Google INPA FXX. You will also need an ENET cable.

None of this is easy per se, but if you invest the time to understand the tools and how they function, it's relatively easy.

[tryingtobebest]

I am incredibly mad right now, I AM PISSED, I READ the first post to just about this line:

Originally Posted by 808AWD325xi

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 you have the two folders needed to bootstrap INPA 5.0.6, it's best to reinstall Windows.

Once Windows has been reinstalled...

And thought hey, it looks like a very clean install! So yesterday i followed your steps precisely and clearly till the sentence mention above!!( BUT NOW, i have no idea if im able to install inpa on this laptop ever again!

MAN, you should put this line somewhere in the very beginning of the post that windows HAS to be reinstalled, im using my laptop for tuning only and currently it has a collection of already setup and WORKING tuning soft for my GTR!!!! I CANT REINSTALL windows, well i can but i really don't want to!

Dont get me wrong, its one of the greatest step by steps, but just god damn!((((


EDIT:

Downloadable links:

Originally Posted by 808AWD325xi

The NCS-Expert profiles are attached to this post:
http://www.e90post.com/forums/showpo...postcount=4476

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

Are not working for me, the place where they loadet to either not working for me or you have to register to! Look into it!

[808AWD325xi]

Originally Posted by tryingtobebest

I am incredibly mad right now, I AM PISSED, I READ the first post to just about this line:

Originally Posted by 808AWD325xi

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 you have the two folders needed to bootstrap INPA 5.0.6, it's best to reinstall Windows.

Once Windows has been reinstalled...

Originally Posted by tryingtobebest

And thought hey, it looks like a very clean install! So yesterday i followed your steps precisely and clearly till the sentence mention above!!( BUT NOW, i have no idea if im able to install inpa on this laptop ever again!

Apparently you overlooked the high level overview earlier in the thread. Bold typeface added for emphasis...

HIGH LEVEL OVERVIEW

• Install a temporary copy of Windows (suggest skipping product key input)
• Install INPA 5.0.2 and save SGDAT and CFGDAT folders to a USB thumb drive for later use
• Re-install a fresh copy of Windows (the INPA 5.0.2 installation process made Windows registry changes and installed programs that are not applicable to modern Windows variants)
• Install BMW Standard Tools 2.12
• Copy INPA scripts and configuration files from the saved CFGDAT and SGDAT folders
• Import SP Daten files with WinKFP and by manually copying files
• Install WinKFP profiles

Originally Posted by tryingtobebest

MAN, you should put this line somewhere in the very beginning of the post that windows HAS to be reinstalled, im using my laptop for tuning only and currently it has a collection of already setup and WORKING tuning soft for my GTR!!!! I CANT REINSTALL windows, well i can but i really don't want to!

Originally Posted by tryingtobebest

Dont get me wrong, its one of the greatest step by steps, but just god damn!((((

Thanks...

Originally Posted by tryingtobebest

EDIT:

Downloadable links:

Originally Posted by 808AWD325xi

The NCS-Expert profiles are attached to this post:
http://www.e90post.com/forums/showpo...postcount=4476

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

Originally Posted by tryingtobebest

Are not working for me, the place where they loadet to either not working for me or you have to register to! Look into it!

I looked into it...the links work fine.

[tryingtobebest]

Hey, wondering what if i clean up my windows as good as i can *(without reinstalling it) and continue with plugging inn DCan etc...??

I cant believe that in this and in your Win7 write up you are following same scenario of saving two particular folders, cant you upload them (this two folders) somewhere (if they are identical for all users) in zip/rar format? That people can easily download them without hassle of reinstalling windows?

One more, in the last part of this write up:

Originally Posted by 808AWD325xi

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

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

Do you HAVE TO do it through CMD? Or manually is fine?

Also, if i have newer SP-Daten for E89 of lets say 2.55.0 (or 2.54) will this version of Inpa support/be compatible with them? Or should I use older (50.2/51.2) just because they are proven?

Originally Posted by matteblue3er

This is a painfully long way...

Why don't you ...

Then you just copy your ECU, daten, config, profile, and scripts to their respective directories and ...

From all 4 of this ^ Im aware of SPDaten and Profile, where to get the other two?

[808AWD325xi]

Originally Posted by tryingtobebest

Hey, wondering what if i clean up my windows as good as i can *(without reinstalling it) and continue with plugging inn DCan etc...??

It should work...your mileage may vary...

Originally Posted by tryingtobebest

I cant believe that in this and in your Win7 write up you are following same scenario of saving two particular folders, cant you upload them (this two folders) somewhere (if they are identical for all users) in zip/rar format? That people can easily download them without hassle of reinstalling windows?

I don't redistribute software. Perhaps you overlooked this as well:

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."

Originally Posted by tryingtobebest

Do you HAVE TO do it through CMD? Or manually is fine?

Any method of copying the files to the proper folders will work.

Originally Posted by tryingtobebest

Also, if i have newer SP-Daten for E89 of lets say 2.55.0 (or 2.54) will this version of Inpa support/be compatible with them? Or should I use older (50.2/51.2) just because they are proven?

A newer daten should work fine.

[DMA]

Awesome write up thanks for taking the time to put this together.

[Chris_Rav]

So this install does not support the N55 engine in my LCI e92?