2.15.2018

BMW Programming with ICOM ISTA/P, not ISTA+

There are different systems for vehicle diagnosis (ISTA) and programming (ISTA/P) used. This means it was necessary to change systems several times when repairing a vehicle using software.

ISTA+ has been expanded so that all the required programming functions for the series F, G and I are integrated.

E-series vehicles still have to be programmed using ISTA/P!

The functions relevant for programming can be accessed via the following menus:
ista-programming-1
Vehicle treatment
  • Software update o Comfort – as per the suggested measures plan
o Advanced – with broadened scope
o Additional software (range of functions is not active yet)

  • Control unit replacement o Before exchange (preparation) – control unit read-out for the exchange
o After exchange (subsequent evaluation) – control unit configuration after exchange

  • Vehicle modification o Retrofit
o Conversion
o Conversion (only coding)
o Backfitting
o Immediate measures
ista-programming-2
So, what for E series coding/programming?

For Exx- Series:
Interface = K+DCAN Cable (OBDII to USB) or ICOM
ECU Data Files = SP-Daten
NCS Expert = Coding Software
WinKFP = Programming (Flashing) Software
EDIABAS = Low-Level ECU Communication Software used by NCS Expert & WinKFP

For Coding, you need NCS Expert / SP-Daten for E-Series
All Diagnosis and Coding can be done with a cheap K+Dcan cable

For Programming (Flashing ECU’s with new Firmware), then you need ISTA/P for for E-Series, or you can use WinKFP for it. And you will need a BMW ICOM cable (ICOM A2/ICOM A3 or ICOM Next)

YOU HAVE TO KNOW before you buy ICOM A2 or ICOM A3 or ICOM Next:

ICOM NEXT vs the old ICOM

-> much faster in BMW F and G series ..
-> supports gigabit Ethernet too to be future proof, there currently is not gigabit Ethernet protocol defined yet for autos. Also it has USB3.0 instead of USB2.0 and a better wifi card.

So, Icom next a works much better.

ICOM NEXT A vs ICOM A2

-> more stable during programming
-> be necessary for the future Gbit cars
-> faster start-up times and high throughput
-> through high-performance,low-power ARM SoC
-> improved handling
-> more flexible OBD cable
-> lighted button for logs
In sum, Icom next wins!

ICOM A3 vs ICOM NEXT

Both of these have the same hardware. None of them are clones of anything also. A3 is fully china version of ICOM, there is no original version looking like this crap. NEXT is just looking as genuine NEXT, but with old A1/A2 hardware inside, like A3.

I recommend buying an Icom next. It is priced roughly at 500 euro. Take in consideration that you will probably work on cars that are worth 30-40k euro or maybe more and if your chinese icom fails you even once, you will be spending a lot of money on a bricked ecu.

ICOM A vs ICOM A2 vs ICOM A3

Modified ICOM A2 for vehicles with OBD access receives a significantly more powerful processor and more storage capacity. And robust aluminium case will help to avoid damage when using in harsh environments. It works better in cooling, runs faster and works more stable, not easier broken than older ICOM A.

ICOM A3 can program all units for all BMW series expect media system, and work more stable and has stronger compatibility than ICOM A2, A1.


In short, ICOM NEXT A+B+C works perfect; it’s the best option.

2.12.2018

Free Download and Install BMW E-series Coding Tool SP-Daten

Here’s little tutorial on BMW E-series coding programs installation.

Disclaimer: The document was translated from Korean. You are at your risk.

Part I. Required files

1. INPA
2. BMW Coding Pack
3. BMW Coding Tool
→ Download E_coding.zip
Unpack and use
4. SP-DATEN
→ Download and use the data file for BASE and car  https://mega.nz/#F!ukQzzBwb!bH9cRXpvW4xiTLr-N10CjQ

! iAJg_VqYENXBCaGLS-AvFvhPSNEae2mp-aWtuYOHGv8 (E_coding.zip decryption key)

Part II. Install the INPA program

1. Materials
(1) Coding required cable: BMW INPA K+DCAN cable
(2) Programs required for coding: INPA / NCS Expert
(3) Own vehicle information file (SP-Daten, SP-Daten capacity of 30 ~ 40GB per vehicle)

2. INPA program installation
(1) INPA / K + D CAN drive installation
If you unzip it, there are three folders in Step 1, 2, 3, and there are installation instructions, a description PDF document,
1) Copying the entire EC-Apps under the 01_Step1 directory to C: /
2) Run NFS / Entpackt / disk1 / SETUP.exe under the directory 01_Step1
Install
If not, copy all of these NFS directories to C: / and install them)
Note 1. In Windows 8.1 32bit, copy the file under disk1 to C; /
NTVDM automatically download and run)
Note 2. If the program fails to install again after the installation fails, copy the previously copied C: / EC-Apps
Clear all and copy again
Select Window XP on the screen
The remaining selection values
User mode / Parametrienen einer neuen Configuration ohen Dafer / OBD / KeinApi-Trace / Kein IFH-TRACE / Komfor (.IPO) selection
The first time you install regsvr32, the two * .ocx files will fail to register, but if you uninstall and reinstall the program you just installed from the control panel, the ocx file will be registered normally.
In particular, the message “The program is not installed properly” appears on Windows 7/8. Select the program installed correctly ”
3) Run INSTALL / Instprog.exe under the directory 02_Step2
(Copy and run under C: \ temp, but not on other drives)
Select “ENGLISH” on the screen, press Continue / Continue and never change the folder or drive to install.
In the Configuration window
Select “Bmw Group Rectification programs UK” → Continue
EDIABAS 6.4.3 → Update
INPA 5.0.1 → Update
NCS Expert 3.0.8 → Check Complete → Continue
4) INSTALL / Instprog.exe under the 03_Step3 directory
(Copy and run under C: \ temp, but not on other drives)
3) in the same way
Old verstion delete → Yes
5) Overwrite inpa.ini under c: / EC-APPS / INPA / CFGDAT with inpa.ini in the INPA folder.
3. Cable connections and port settings
(1) Plug OBD cable into USB port and select manual drive installation
1) Install it as a drive under the drive under the INPA folder, and when installed, recognize USB Serial Port
2) In the USB Serial Port property, set Port Setting / Advanced / Com Port No. 1, Response Time 1
(2) Run Drive_D_CAN_USB / OBDSetup.exe under INPA directory and reboot
INPA installation complete
(3) Confirmation of installation: Execute c: /EC_Apps/INPA/BIN/inpaload.exe and Battery / Ignition
If you see two black dots on the installation succeeded
bmw-coding-tool


Part III. Installing BMW Standard Tool from BMW Coding Pack

1. When unzipping, four folders with numbers 1 ~ 4 are created, and BMW Standard Tool 2.12 installation
(Be sure to run the program under \ BMW Coding Pack \ folder)
(1) Before running the program, open the Compatibility tab in the properties of the installation file
→ Change Compatibility by selecting Windows XP Service Pack 3
(2) Installation file Click “English” in English / German selection window.
(All installation programs will be deleted when English is selected)
(3) Select German / Weiter (Next) “Ich akzeptieredie Vereinbarung”
→ Press “Weiter” 3 times to set the directory (set to 4 folders default) and add 1 folder
(4) Zus? Zliche Aufgaben ausw? Len
→ Check out two of the above four check boxes: “Datensicherung” (data backup)
(Leave the other two checked and press the next one to pop up a popup window)
(5) Leave the STD: OBD default value on the next Hardware Interface screen
(6) COM port number checked in Device Manager 1 Select “COM1” and then USB auf Serial
Adapter Check
(7) Click Next and then click Installer to start the installation
Select “Ignore” if error screen appears and select “Ignore” if error screen appears (error 2)
2. When the installation is complete, go to the 3-UPDATE folder and add three folders (EC-APPS, EDIABAS,
NCSEXPER) whole
Copy to C: \ → Overwrite existing file with latest English version)
3. After copying the update file, copy the “BMW Coding Shorcuts” folder 4 to the desktop


Part IV. Installing BMW Coding Tools and SP_DATEN

1. Unzip the file into C: / windows / system, C: / windows / system32, C: / windows / Syswow64
Copy comdlg32.ocx, mscomctl.ocx under BMW Coding Tool folder
2. Open a command window in administrator mode and type
(Enter the Windows program app and right-click command to run as administrator)
“Regsvr32 comdlg32.ocx”, “regsvr32 mscomctl.ocx” → After registry registration succeeded
Close the command window and run BMW Coding Tools
install-bmw-coding-tool
3. Press the “Select SP-source” button on the right “SP daten” to find your vehicle information daten file
Select ah Select
4. Click the “UPdate SP-source” button on the right “SP daten” to link and copy the daten file
5. Down the received dummy profile (NCExpert Profile / NCSDUMMY4.PFL) to c: / NCSEXOER / PFL
copy
All programs for E series coding installation is complete.
It is not easy. You must follow each one step by step.  Keep the order …

2.11.2018

BMW Ncs Expert Software CABD Error Solution

When I go to work today, I open my laptop and connect BMW K+Dcan cable to my car, but I get an error when I try to read another module other than CAS of ECU module…
I have a problem with the ncs expert program, but I do not really know where the problem is.
Error:
Ncs-Expert-Software-Error-CABD
“Ncs Expert Error in CABD! Look at CABLERR and ERROR.LOG!
COAPI-2000: EDIABAS or SGBD error
SYS-0005: OBJECT FILE NOT FOUND.”

The problem is that the file version of daten is old …
And I ran INPA to see if the value was correct …

Result:
version do not match
Malfunction possible
SGBD version:3.000 (in INPA)
SGBD version:7.050
INPA version: 1.030
Ncs-Expert-Software-Error-CABD-2
inpa also gives an error message … ㅡ.
There’s a connection to the car, but something went wrong to proceed.
And just came home and found the latest version of daten and downloaded it once.
I want to test it by connecting directly to the car, but I have to endure it again next weekend.
It was a little hard to find, but I must be satisfied that I found the daten file for E89 …
This is the first time you have completed coding. It takes more time than I thought …
For reference, I found that the daten version for e89 (e90) is 47.1 …
If you unzip the downloaded sp-daten file, there are 3 folders besides daten, cfgdat, ecu, sgdat …
I updated it all …
Below is the header part of the e89at.000 file …
// Auftragsdatei: E89AT.000
// -350-
// Erstverw.Klog .: 61.35
// Ident-Nummer: 6 933 698.5
DATUM 31.05.2012
//
// Kurzz. Datum Name
// Bearbeiter: EE-82 Obrman
// Geprueft:
// Verantwortlicher:
// Verantwortlicher:
//
// Bayerische Motoren Werke Aktiengesellschaft
// Wiedergabe sowie Vervielfaeltigung dieser Unterlage, Verwertung und
// Mitteilung ihres Inhalts nicht gestattet, soweit nicht ausdruecklich
// ZugStanden. Zuwiderhandlungen verpflichten zu Schadenersatz. Alle
// Rechte fuer den Fall der Patenterteilung oder Gebrauchsmuster-
// Eintragung vorbehalten.
//
//
// Verteiler:
// EE-82
// TD-433
// TI-430
//
// Aenderungsdokumentation:
// NAEL- Zeichn. xmal /
// Nr. Index Seite Kurzbeschreibung Datum Name
//
//
//
DATEINAME E89AT.000
//
Disclaimer: Thanks to blitzguy providing the solution. You are at your risk.
http://www.obdii365.com/producttags/bmw-icom-next.html

2.10.2018

How to Find BMW E-series ZB Number when Flash Module

This post will show you how to easily find the ZB number when flashing an E -series module.

Programs:
The programs used for Ecu Flashing are Winkfp (E-series), E-sys (F-series) and ISTA-P (ALL).

Definition of Flashing:
Flashing an ecu means to write new software to a module (ecu).
The purpose of flashing can be updated to a later (newer) software version.
You know! (Update to latest version data)

ZB Number: The assembly identification number and easily program data set.
Winkfp needs to know zb number for flashing.
The ZB number of each module can be found easily through INPA software. Below is the method.

1. Select INPA to select the model. (ex .: F4 E60, F8 E90)
inpa-find-zb-number-1
2. Select Chassis → Functional Jobs.
inpa-find-zb-number-2
3. Select the F3 User Information Field (UIF).
inpa-find-zb-number-3
4. In the UIF contents, each module is visible and the middle ZB No. is displayed. It is a 7-digit number,
Flashing in Winkfp.
inpa-find-zb-number-4

2.08.2018

(02.2018) ISTA+ 4.09.33 Standalone SQLiteDB's Download Free

(Feb. 07th, 2018) Free download ISTA+ 4.09.33 Standalone and SQLiteDB’s on Mega.

ISTA 4.09.33 the standalone version
HW checks removed and includes separate link for the NOFASTA patch.

Standalone 4.09.33
RheingoldSessionController_NOFASTA.dll

ISTA 4.09.33 installation files on Mega:
https://mega.nz/#F!pb5U0ATC!Oadp9zVx3SDpcjbQZQM-pw
Files:
BMW_ISPI_ISTA-META_4.09.33.xml
BMW_ISPI_ISTA-APP_4.09.33.21392.msi
BMW_ISPI_ISTA-META_SDP_4.09.30b.xml
BMW_ISPI_ISTA-DATA_DELTA_de-DE_4.09.30.istapackage
BMW_ISPI_ISTA-DATA_DELTA_en-GB_4.09.30.istapackage
BMW_ISPI_ISTA-DATA_DELTA_4.09.30.istapackage
BMW_ISPI_ISTA_DELTA-SDP_4.09.30.istapackage
BMW_ISPI_ISTA-BLP_4.09.30.istapackage
bmw-icom-ista-4-09-33
Password: NOT required!
Security: Unknown – TRY ON YOUR OWN RISK!!!!

Installation tutorial:

Suggestion: you need luck with ISTA+ 4.09.33 as it’s not tested yet by professionals that safety is unknown. And luck also is needed because of the uneasy installation. Hope the installation guide is helpful but note that it would be kind of different from versions, in terms of steps. If you’re not good at this, just buy a cheap HDD or SSD with software inside. A lot of Chinese have crack software with internal disk. Jut buy it with relief.

Look here: 2017.12 BMW ICOM Software HDD ISTA-D 4.08.12 ISTA-P 3.63.0.400 with Engineering Software
bmw-icom-ista-4-08-1
bmw-icom-ista-4-08-2
bmw-icom-ista-4-08-3
bmw-icom-ista-4-08-4
bmw-icom-ista-4-08-5
bmw-icom-ista-4-08-6
bmw-icom-ista-4-08-7
bmw-icom-ista-4-08-8
bmw-icom-ista-4-08-9

Tested 100% and confirmed to work
They offer professional tech support – that’s the most important for newbies!

2.04.2018

K+DCAN cable with switch pin 7&8: What, Why, How to use?

What is K+DCAN cable with switch:

It’s a BMW K+Dcan usb cable, the 2018 version.
In detail… Look here:
inpa-k-dcan-cable-with-switch-1

inpa-k-dcan-cable-with-switch-2

inpa-k-dcan-cable-with-switch-3
A new switch is added, compared to the traditional Dcan cable.
the switch on this cable to LEFT is for 7 pin, to RIGHT for 8 pin
8 pin for K-LINE communication (old DCAN cables cannot do it) for BMW from 1998 to 2008
Upload images…
Traditional Dcan cable:
New K+Dcan cable with a switch pin 7 &8 and FT232RQ chip:

Why do you need K+Dcan pin 7&8?

I assume the reasons being that on DCAN cars one pin is used for a ethernet connection and the other to the K data line – on K line cars, both pins are connected to K data lines and that creating a switch mode circuit would cost more than the interface is worth. The 2 most sensible options are both hardware-related:-

  1. Use an adapter (such as the one sold by One Stop electronics) which internally bridges pins 7 & 8 or…

  1. Mount a small switch on the OBD plug end of your adapter, which can bridge (for K line) or separate (for DCAN) the connection between pins 7 & 8.

How to use/switch/connect to K-Line or Dcan pin 7&8?

Q: So you have to physically connect (K-Line) or disconnect (DCAN) pin 7&8?
A: Yes, I think connection by soldering is a bad option as it limits the usefulness of the interface, I have an adapter but consider a switch to be a better option.

Q: Is there anything else to do for switching from K-Line to DCAN then disconnecting pin 7&8? Unfortunately I don’t have a DCAN model available.
A: As soon as you connect the interface to the car and your computer, run DCAN.exe to configure the comms rate. I have only used my K+DCAN interface with DCAN cars.

Q: Is it necessary to do so every time I want to use DCAN or is the interface staying in DCAN mode once I ran DCAN.exe?
A: You only need to run it when you are switching between modes. If you run it the first time you connect to a DCAN car, your computer will retain the settings.

Q: How do I switch back to K-Line? Just by connecting the two pins or is further action on the computer required?
A: Earlier e39 had both the OBD port in the cabin and the round 20 pin connector under the hood.

The OBD port only allowed access to limited modules, I think only the DME in fact.

I always switch my K+D CAN adapter between K and D CAN protocols as I need to, depending on the car that I’m connecting to.
I use the DOS version of the DCAN utility. As mentioned if you only use the adapter on the e39, run the utility once and set the adapter to K CAN and leave it at that.

In fact thinking about it I use the same adapter for INPA, DIS and ISID.

With these K+DCAN cables there are two subtle different versions, one with pin 8 enabled, one with it disabled. The one with it disabled is ideal for e90 newer than 03/07 & that era, these leads often come with a black adapter to re-enable the pin 8 (by just tying it to pin 9) so it will also be suitable for e46/e39/e63 etc. The ones with pin 8 active are just older versions of the cable. Worst cast scenario you just need to modify the cable & stuck a switch on it to toggle pin 8 on/off as needed.

Finally there are a lot of rubbish adapter cables out there. Finding a good one can be tricky.

Q: I have a 2003 E39 so there is no OBD1 anymore. How do you switch the modes physically? Do you use such a adapter to connect Pin 7&8?
A: If you don‘t plan to use the cable on any cars that have DCAN(2007+) then you can pop open the case and solder a jumper between them. When you do this the DCAN functionality will no longer work though.

Where to download & How to install BMW INPA software for K+Dcan cable:

Look here:
How to install INPA software on Windows XPWindows Vista 32bitWindows 7 32Windwos 7 64bitWindows 8Windows 10 users.
(click on the Operation System to get the how-to guide directly).

1.31.2018

NCS Expert VIN is faulty COAPI-2000 (many solutions)

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