Lan Connect Operation Details
1. Connect the LAN cable to ICOM A1/ICOM A2, another side to laptop LAN port
2. Connect OBDII cable to car OBDII Port; sometimes you might need the external OBDII cable.
3. Insert the USB KEY to laptop USB Port and power on the laptop
4. Input the password: BMW ICOM (all Capital letters) and press “Enter” to continue.
5. Wait the software well loaded (The red letters disappear and the offline day appears)

6. Choose ISTA/D or ISTA/P to enter the diagnostic or programming software.
7. For ISTA/D Choose [Vehicle identification] and choose read out vehicle data or start vehicle
test to diagnostic with cars.

8. For ISTA/P choose [Create new session], then choose the free icom, it will read out all the
vehicle’s information and modules one by one.

Wireless Connection Details
1. Power on the router firstly, till the green LED is flashing on the router. (Important)
2. Connect the ICOM A1/ A2 to car OBDII port via the OBDII cable and make the ignition on.
3. Wait till the ICOM A1/ A2 WLAN LED is light up and flashing (around 10 seconds or so)
4. Insert the USB KEY to laptop USB Port and power on the laptop
5. Input the password: BMW ICOM (all Capital letters) and press “Enter” to continue.
6. Wait the software well loaded (The red letters disappear and the offline day appears)
7. Choose ISTA/D or ISTA/P to enter the diagnostic or programming software.
8. For ISTA/D Choose firstly, then choose [VCI Config], check the IP address like this:
192.168.1.100 / 255.255.255.255
9. The interface type must choose [HO-ICOM/ENET direct connection], click save and close the
window.

10. Choose [Identification] then choose [Read Out Vehicle data], then choose [Start Vehicle
Test].

11. At the popup screen, please confirm the IP address is [192.168.1.100] and choose [ICOM],
and then system will read out all the car information and modules one by one.

NOTICE:
1. All the internal settings are well configured, please DO NOT change settings, this might lead
the software not working.
2. Switch between LAN and WLAN, you need plug off the OBDII cable from car and re-plug in
(Make the ICOM A1/A2 multiplexer restart)
3. Please keep your laptop/ Routers with stable power when using.
4. If you cannot diagnostic with cars by WLAN, please make sure the router is powered on and
restart the laptop to try.
5. All operations must base on the software well loaded! (red letter disappear and offline day
appear)

Just fully retrofitted cruise control to my BMW ‘2010 E87 today – its was definitely the easiest retrofit i’ve done on the car – took all of 1 hour to install.

Model: BMW e87 2010

Tools: BMW ICOM A2 emulator (i used the clone)

together with working NCS Expert and Tool32

Partially code cruise control retrofit:

I’ve partially coded it and i tested the cruise control and it is working as it should but i’m getting errors.

Here’s what i did:

i coded the car using NCSExpert to update the vehicle order ($540 for CC), writing that to CAS and FRM and then coding each individual module (the only one that failed was the MULF – which i guess is expected because thats for the bluetooth…?)

After i did that i shut off the car, removed key, put key back in and started the car and took the car for a drive to test the cruise control and it worked but so many errors…The DSC, DBC (dynamic brake control), FTM (flat tyre monitoring) and restraint system failure (this one i think is my fault because i broke the ground wire for the air bag )

Fully code cruise control retrofit:

the basic process on coding the retrofit:
NCS Expert:
Using NCSEXPERT update the car’s “Vehicle Order” (VO) by adding option “$540” and “FA_WRITE” the new VO to the CAS and NFRM module. Next select Job “SG_Codieren” to code each (all) the modules in the car individually. For me only the 2MULF module failed (this would make sense because its only the bluetooth module).

Tool32:
Open Tool32, File->Choose “Load SGBD Group file”, open DSC_87.prg (for my 2010 e87 it was this), find job “lenkwinkel dsc abgleichen” and double click. If it worked correctly, a new results window will appear, look for where it says “status/job status” and if it’s says ok, close tool32 and disconnect the OBD cable and start the car.

So yeah in summary – i managed to sort out the errors (so many errors… DSC, DBC, FTM and restraint system failure). All i had to do was use OBD2 Scanner to calibrate the steering angle sensor.

Here is WinKFP setup/installation tutorial, based on the E60 daten from ISTA/P 2.39. This assumes you have installed INPA/Ediabas and WinKFP and they are running correctly. This was done on a WinXP 32 bit system by OBD2TOOL.

1.  Unpack the V2.39 ISTA daten folders for SP-daten-E60 somewhere on your harddrive.
2.  Open WinKFP, then choose “Import/Export” in the main menu, and pick “Import” then “PABD”
3.  Browse to your unpacked daten folder and drill down to “sgdat”. [base]\SP-daten-E60\sgdat\. Hit CTRL-A to select all files, then click “Import”
4.  Now select again “Import/Export” in the main menu, and pick “Import” then “P-SGBD” and, like step 3, browse to your unpacked daten folder and drill down to “ecu”. [base]\SP-daten-E60\ecu\. Hit CTRL-A to select all files, then click “Import”
5.  Now select again “Import/Export” in the main menu, and pick “Import” then “Assembly Line Data”
6.  Browse to your unpacked daten folder and drill down to “data”. [base]\SP-daten-E60\data\ and make sure “data” is highlighted and select “OK”
7.  Depending on how big the data are, you may have to wait awhile. Go get a sandwich. Don’t abort. SP-daten-E89 took 10 minutes or more on my laptop and the program appeared frozen for several minutes. Eventually, it should return control.
8.  Open the regular file explorer and browse to your unpacked daten folder and drill down to “gdaten”. [base]\SP-daten-E60\data\gdaten\

Hit CTRL-A to select all files, then CTRL-C to copy all files to clipboard. Now browse to your NFS folder (usually C:\EC-APPS\NFS\ or just C:\NFS\ depending on your installation) then browse down to “data\gdaten” and hit CTRL-V to paste the copied files. If there are files already in this directory, overwrite them with the files you copied.

Now exit WinKFP and, if desired, backup your NFS dir and EDIABAS\ECU dir so you don’t have to go through this again.

9.  Run WinKFP. You may see a message like this:

Don’t panic. For some reason there are some lines in some of the BMW Diagnostic Tool SGIDC.AS2 files that are too long for WinKFP. SGIDC.AS2 is an ASCII text file and can be edited with notepad or another editor. Just load it up (you may have to add a .txt extension and remove it after editing) find the line specified in the box above and put a semi-colon in front of it (“comment” it out) or remove it completely. I don’t know if it is ever needed or if it should be truncated or what, but I’ve never run across any bad behavior by removing it.

Do this again if there are other long lines in the file; you can easily determine this as most lines will all be the same length and the problem lines will be twice as long or longer.

If all went well, you should have all the files needed to program ECUs with WinKFP.

Btw, I plugged those numbers in and I get “Assembly identification number not found in files determined by xxkfconf.da2”

I’d go the “Update ZUSB” route. Click “Comfort Mode” then “Update ZUSB” (F3). Select your ECU Family from the list (I’d guess “SBSL65”, “SBSR65” for the first two, but I don’t know about DDE. My DME/DDE is MSV70 which doesn’t seem to match).

After selecting the ECU Family, enter your VIN and hit OK. Now hit “Done” which goes back a screen, then you have a new option: “Prog ZB Update”. Select it and, if you have the right ECU family, you should get a box like this:

If you don’t have the correct ECU family, then I don’t think you’ll get this far, but don’t take my word for that. Try selecting something you know you don’t have and see if it gives you anything.

Entering: 7832868 – my bmw ECU part number into ZUSB brings up nothing but an error: Error 704:

Error on determining the ZB number!

The errors are because you input the wrong ZUSB (DME assembly number). It wants the DME firmware version, also called ZUSB (called Assembly Number in INPA). But doing that is not normally necessary.

Are you just updating your current DME? If yes, you do not need to input your current ZUSB.

Just do this:

– Choose “Comfort mode”.

– Choose “Update ZUSB”

– Select your DME type (MSS54 for your M3).

– Choose “Enter VIN” and enter your full VIN.

– Choose “Done” and it will go back one page.

– Choose “Prog. ZB-Update” and it will display both your current ZUSB and a proposed update ZUSB.

– Choose “Yes” to begin programming.

Starting the ISTA Client

How to start the ISTA Client
1  Double-click the symbol on the Windows desktop (if displayed)  ; or
2  or
3  Open the application in the program file by selecting “Start – All Programs – ISTA – ISTA Client”;
4  or
5  Open the application by selecting the corresponding entry on the central start page on the ISID.
After selection, the start mask appears (Chapter 3.1). A list of news will be displayed. You can set the display period in Administration.

If the date has changed since the last time the system was activated, the BMW Diagnostic Software “ISTA usage notes” will be displayed. After reading the note, close the popup window by clicking the “Continue” button. You can initiate an identification procedure from the start mask.

Checking the operations list

After you have selected the “Identification” menu from the start mask, the workshop system switches to the “Operations list” tab.

Each identification session generates a “procedure” that is automatically initiated and administered by the workshop system for vehicle identification. At the end of the session an operation is closed via a popup. The user can thus choose whether he wants to terminate or interrupt the operation. Depending on the option selected, an operation is concluded via a popup, assigned a status (“terminated”, “interrupted”) and entered into the operations list for a certain period. Saved procedures can be reopened from the operations list Additional information is available in Chapter 3.2.1.1.

The selection of an existing procedure is not suitable for the “Short introduction” provided here. Therefore change to the “Read out vehicle data” tab.

Selecting a vehicle

There are four options for initiating vehicle identification (Chapter 3.2):
*   by selecting an operation
*   by entering a vehicle identification number
*   by reading out the vehicle data, or
*   by selecting basic features.