[DaanBMW]

Originally Posted by 808AWD325xi

No, that is not what I am saying...you are misinterpreting what you are seeing in a binary (.IPO).

I sure am (plus that IPO wasn't for my DME, which is MSV80). I would like to understand it though... What is the logic/connection here ? The code you posted above said for deletion byte_1 / 2 / 3 = 1 . So this makes the 111, i.e. 0x6F in hex ? So where are the others coming from, and why the middle ? 0xFF;0x6F;0xFF = 255;111;255

Originally Posted by 808AWD325xi

For MSD80, MSD81, and MSD85, the proper arguments to the ADAP_SELEKTIV_LOESCHEN job are 0xFF;0xEF;0xFF. That deletes all adaptations except for the battery.

For MSV80, which I believe is the DME that you have, the proper arguments are 0xFF;0x6F;0xFF.

EDIT:
For MSV70, the proper arguments are 0xFF;0x6F;0x7F.

Where are you looking to get the correct codes ? I seems to me like you have access to the actual commands that are built from Tool32 ? Is this somewhere in the SP daten files, or ?

[808AWD325xi]

Originally Posted by DaanBMW

I sure am (plus that IPO wasn't for my DME, which is MSV80). I would like to understand it though... What is the logic/connection here ? The code you posted above said for deletion byte_1 / 2 / 3 = 1 . So this makes the 111, i.e. 0x6F in hex ? So where are the others coming from, and why the middle ? 0xFF;0x6F;0xFF = 255;111;255

There are 3 bytes, it's a 24-bit bitmask. As previously mentioned, each bit represents a specific adaptation; idle, knocking, O2 sensors, etc.

1 clears, 0 retains.

Originally Posted by DaanBMW

Where are you looking to get the correct codes ? I seems to me like you have access to the actual commands that are built from Tool32 ? Is this somewhere in the SP daten files, or ?

I understand PABS, the BMW programming language used to write INPA scripts.

The job arguments, as you already know, can be found in the script binaries.

We're really off topic for this thread.

[808AWD325xi]

Erratum:

• The link that I provided in this step had been broken:

Originally Posted by 808AWD325xi

[...]
Import your daten files into WinKFP using this guide (steps 2-8):
http://www.e90post.com/forums/attach...8&d=1375758759
[...]

Attached is the guide. The original post has been updated with a new link.

[nabilishes]

After installing INPA i got the battery and ignition to turn solid black circle which means cable is functioning.

However, i am getting this error when i go to E90>Engine>MSD80 for N43>F1 SGBDInfo
Error:
ApiCheckJobStatu: Error #95 SYS-0005:OBJECT FILE NOT FOUND. API job error or no such result. Continue script processing?

I updated the DATEN Files using V54 E89 btw.

[808AWD325xi]

Originally Posted by nabilishes

After installing INPA i got the battery and ignition to turn solid black circle which means cable is functioning.

However, i am getting this error when i go to E90>Engine>MSD80 for N43>F1 SGBDInfo
Error:
ApiCheckJobStatu: Error #95 SYS-0005:OBJECT FILE NOT FOUND. API job error or no such result. Continue script processing?

I updated the DATEN Files using V54 E89 btw.

Most likely you're missing SGBD files from the C:\EDIABAS\ECU folder.

Refer to the FAQ (FAQ.PDF) in the C:\EDIABAS\DOKU\ENGLISH folder for more details.

My guess is that you either did not successfully copy the group files or did not properly import the P-SGBD files with WinKFP (step 4 in the guide below):

Originally Posted by 808AWD325xi

[...]
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
[...]

[mattoak]

So if I follow this process exactly, I should be able to code using NCS Expert on windows 10 64-bit?

And read codes with INPA, etc.

[mattoak]

Originally Posted by BimmerGeeks

Yes.

And has it been confirmed that you absolutely must reinstall windows in order to get it to work after installing the first version?

What if I install the first version on a dummy PC, just to get the required data files and then only do the final install on my actual coding laptop I plan on using instead? Anyone ever try that?

[putango]

Originally Posted by 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.

Very Nice! Thank you so much

[nabilishes]

What is the latest SP-Daten files available? Can anyone PM me latest SP-Daten files?

[808AWD325xi]

Originally Posted by nabilishes

What is the latest SP-Daten files available? Can anyone PM me latest SP-Daten files?

SP daten 61.2 is the latest. However, the E89X (E81, E82, E84, E87, E88, E89, E90, E91, E92, E93) I-level (E89X-16-11-500) hasn't changed since 60.0.

SP daten 60.0 or later is currently the latest for E89X vehicles.

[nabilishes]

Originally Posted by 808AWD325xi

SP daten 61.2 is the latest. However, the E89X (E81, E82, E84, E87, E88, E89, E90, E91, E92, E93) I-level (E89X-16-11-500) hasn't changed since 60.0.

SP daten 60.0 or later is currently the latest for E89X vehicles.

Thanks for the info. I managed to get Rheingold 4.04.12 and it includes ISTA-P 3.61.0.500. In Folder ISTA-P>BMW>Services>data>ecudata>(lots of daten folders including E89). Can i use these Daten files for my INPA?

If i were to install Rheingold, would the installation overwrite my current INPA/WinFKP/EDIABAS ecu and SP-Daten files(installed using BMW Standard Tools)?

[808AWD325xi]

Originally Posted by nabilishes

Thanks for the info. I managed to get Rheingold 4.04.12 and it includes ISTA-P 3.61.0.500. In Folder ISTA-P>BMW>Services>data>ecudata>(lots of daten folders including E89). Can i use these Daten files for my INPA?

You're welcome. Yes, those are the SP daten files.

Originally Posted by nabilishes

If i were to install Rheingold, would the installation overwrite my current INPA/WinFKP/EDIABAS ecu and SP-Daten files(installed using BMW Standard Tools)?

Earlier versions of Rheingold (3.XX.XX) did not overwrite the EDIABAS folder. But I haven't installed ISTA on the same system as BMW Standard Tools in quite sometime, so I can't really say for sure.

I doubt it would touch BMW Standard Tools (INPA, WinKFP, etc.), but it could possibly overwrite the C:\EDIABAS folder.

If you found this information useful, please click on the Appreciate button at the bottom of this post.

[temelj]

UPDATE: These tools don't work as expected!
Mike's Easy BMW Tools

The idea was that these tools would take out the hassle of installing INPA 5.0.2 and then a windows re-install and so on.

The issue with the tools is that BMW Coding Tools need manual registration of the included OCX ActiveX controls using regsvr32 in command line.
It is missing a file too.
INPA worked (to a degree!).
NCS Expert does not have the EXPERT Profile for coding. Only the ncs dummy profile.
I got BMW Coding tool to work and updated a later daten version for E89 and E60. INPA worked to a degree for E89, not so well for E60 (could only read error codes pretty much).
NCS Expert was completely busted.

Long story short: I would follow the OPs suggestions.

I noticed the OP has made it clear that he isn't endorsing other sources, and is talking about the ones he's found that do work. That's also very acceptable.

In theory:
- one other solution to not having to re-install windows is to take a snapshot of your REGISTRY (regedit) before you start the INPA installation, copy the files around as the OP suggested, but instead of Re-Installing windows: Re-import the original registry changes.

To simplify this step - one could use tools like RegShot to help out identify what has changed in the registry and "undo" one by one as required. (SAFER approach)

The other suggestion would be that if someone does follow the OPs instructions, to take a copy of the necessary INPA files, create a ZIP and share it. That way we could skip the step to re-install windows.

NOTE:
If you have ISTA-P and ISTA+ (ISTA/D) from Rheingold, Installing the Mike's easy tools also buggers up those

[mattoak]

I just installed BMW tools 2.12.0 from the start which gave me the latest versions of the files. Then I manually installed the activex controls and then copied over files from the previous INPA, EDIABAS, and Daten 50.2 that I found by pilfering through this forum and other BMW forums. I actually ended up with a couple sets of the same version of files and had to randomly pick one. That's where I am now and I'm about to test it, however I have to figure out how how to use all these tools! Hopefully it works! If not I'll try the other sets of the 5.0.2 files. If that doesn't work I'll bbe back. Will update with the result if I remember.

[Jimmeh]

Originally Posted by 808AWD325xi

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&

First off, I really appreciate you putting together this guide. Going through the steps right now. I was wondering if its possible to not use a charger if the car is on while performing the coding (I'm only looking to change some battery settings and register it). I'm new to coding so apologies if this is standard knowledge.

[808AWD325xi]

Originally Posted by Jimmeh

First off, I really appreciate you putting together this guide. Going through the steps right now. I was wondering if its possible to not use a charger if the car is on while performing the coding (I'm only looking to change some battery settings and register it). I'm new to coding so apologies if this is standard knowledge.

No worries. For coding, a power supply really isn't required assuming that a you have a healthy, charged battery. Just don't take so long that you kill your battery...

[nabilishes]

I read that when coding (also when clearing ERROR with INPA) if the battery drops to the lower 11Vs, the FRM module could get bricked. If i were to connect a battery charger what are the recommended ratings voltage and current. Is battery charger with 12V and 6/8A okay?

[808AWD325xi]

Originally Posted by nabilishes

I read that when coding (also when clearing ERROR with INPA) if the battery drops to the lower 11Vs, the FRM module could get bricked. If i were to connect a battery charger what are the recommended ratings voltage and current. Is battery charger with 12V and 6/8A okay?

Yeah, FRM3 modules in particular are sensitive to low voltage conditions.

A link to the the BMW Group recommended charger specifications can be found in the first post of this thread.

I recommend something like the Don Schumacher Racing INC-700A which adapts to the cars current draw and supplies constant, clean power.

[ninja_zx11]

Originally Posted by nabilishes

I read that when coding (also when clearing ERROR with INPA) if the battery drops to the lower 11Vs, the FRM module could get bricked. If i were to connect a battery charger what are the recommended ratings voltage and current. Is battery charger with 12V and 6/8A okay?

Yes that's true.I only realized when i was just scanning my E60 with engine off and after that car started to throw weird error messages like fuel cap open.Then i re-scanned it with engine running and got rid of that error.So proper battery voltage is important even if you are just scanning.

The cheapest way is to connect it to another vehicle with engine running with jumper cables.

[nabilishes]

Originally Posted by ninja_zx11

Yes that's true.I only realized when i was just scanning my E60 with engine off and after that car started to throw weird error messages like fuel cap open.Then i re-scanned it with engine running and got rid of that error.So proper battery voltage is important even if you are just scanning.

The cheapest way is to connect it to another vehicle with engine running with jumper cables.

I was about to ask the same thing! i believe that would be the cheapest option without having to buy a new battery charger.

When coding with WinFkp or NCSexpert is it okay to let the engine running, or best let it at the IGNITION ON with battery charger attached to the front hood terminals?

[lalaura]

Any one used switch mode DCAN cable?
http://www.obd2express.co.uk/wholesa...expressuk.html i'm using

How do I switch back to K-Line? Just by connecting the two pins or is further action on the computer required?

[Katkarot]

As per 808AWD325xi, he said disable UIF write in WinKFP. I should have the following 4 UIF Options unchecked in WinKFP?

UIF write after data
UIF write after program
UIF write in expert mode
UIF write in comfort mode