February 05, 2018
8 pin for K-LINEcommunication (old DCAN cablescannot do it) for BMW from 1998 to 2008
- Use an adapter (such as the one sold by One Stop electronics) which internally bridges pins 7 & 8 or…
- 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.
February 01, 2018
All running on XP and also tried on Win7 x64
INPAis working fine. Battery and ignition both ON
When runningNCS 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
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
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.
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.
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 YOURNCS EXPERTFOLDER YOU SHOULD SEE A FILE:
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
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 YOUJUST SELECTEDTO 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 inlatersteps.
** 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?? becauseNCS expertonly 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..
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 useNCS Dummythat 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.
AUTOMATIC HEADLIGHT CONTROL
BRAKE LIGHT ERROR REPORTING
DAYTIME RUNNING LIGHTS
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 PROCESS ECU
Select the chassis, then module you F'd up on. For example "LSZ"
On Pre-02 carsIt 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 carsIt 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.
January 24, 2018
- Vehicle identification for specific vehicle management
- Information research for repair and maintenance
- Guided troubleshooting
- Software repair
- Software Update
- Control Unit Replacements
- Retrofits / conversions
- Minimum system configuration is now hard coded into the program, although the standalone versions have this check removed.
- 2.2Ghz CPU – 2 core minimum, core i5 or i7 recommended
- 4GB RAM, 8GB recommended
- Minimum 20+GB HDD free space for ISTA+ Diagnostics with ONE language, and minimum 100GB for Programming Data.
- This version has hardware check removed, however, future versions MAY not have this feature. A faster system is required.
- This version discusses included English Databases only. If more required, add to SQLiteDBs folder, which will need more space.
- Visual C++ Redistributable Packages for Visual Studio 2013
- .NET Framework 4.6
- From the Mega site, download and run the following two registry files: o Ista-prog-x64.reg
- Also run the following registry fixes from the C:\Rheingold folder (scroll all the way to the bottom to see these files):
January 22, 2018
This is the screen.
Maybe you've seen this error at least once you useISTA-P
Most likely EDIABAS or PSDZ errors.
1. Exit ISTA-P first and exit the program.
2. Disconnect ICOM connected to OBD terminal of vehicle.
3. Remove the battery terminal of the vehicle for about 10 minutes.
4. Reconnect the vehicle battery terminal.
5. Turn on ignition of the vehicle.
6. Connect ICOM to OBD terminal of vehicle.
7. Run ISTA-P Loader to select ICOM.
8. Run the ISTA-P program.
If you do this, most of the work will be done.
(Assuming that EDIABAS and the rest of the programs are in place)
If the same error is repeated in other ICOMs as described above,
Most of them are EDIABAS, so try patch,
If you still have symptoms, you will need to reinstallISTA-PBMW Diagnostics, Programming, etc.
January 15, 2018
***************** How to backup *****************
1. How to backup with SVT
Read SVT actual from VCM -> Save
1-1. How to recover the whole
Load -> Code
2. How to get backup by module
Read SVT -> Read Coding Data by Module -> C: EsysData / CAF -> Copy and Paste Same CAFD.ncd file into folder you want to save
Read Coding Data If a new window pops up, you can save it without closing it.
2-1 How to recover by module
Read SVT -> Read Coding Data by Module -> Replace with saved CAFD.ncd file into C: EsysData / CAF -> Code FDL
3. How to get a backup of all modules at once
Read SVT -> Root SVT -> Read Coding Data -> C: EsysData / CAF -> Copy and Paste All CAFD File into folder you want save
3-1 How to recover all modules at once
Read SVT -> Root SVT -> Read Coding Data -> Replace with saved CAFD.ncd file into C: EsysData / CAF -> Code FDL
It is often called the factory reset when an error occurs.
Therefore, it is recommended to set the backup as default.
At this time, the meaning of the code is not the meaning of the original, but it is more likely that it means that the coding values are reset to factory reset.
If an error occurs, you can erase it with a scanning device that can be scanned or erase the fault code using BMWHAT or useBMW ENET cableE-sys software.
January 10, 2018
836 Electronic immobilizer control unit (EWS-3)
Plug connector Electronic immobilizer control unit (EWS)
Pin assignments at plug connector X1659
|Description/Signal type||Connection/Measuring notes|
Activation, drive-away protection
DDE control unit, DME control unit
Signal, ring coil ignition lock
Signal, gearshift position L2
Gear position switch
|10E||Voltage supply terminal30||
|12E||Signal, ring coil ignition lock||
|13E / A||
K-bus signal line
Instrument cluster (IKE)
p.04 – DME / DDE
p.05 – coil
p.06 – + 12v (EGS) – necessary if the EWS is coded under the ACP
p.09 – GND
p.10 – + 12v (30)
p.ll – + 12v ( R)
p.12 – coil
p.13 – K-bus – when connecting "on the table”, pull up to + 12v with a resistor of 4.7-10 kOhm
p.01 – Vss GND)
p.02 – Vdd (+
5v)p.03 – ModA
p.05 – E-clamp
p.17 – Reset
p.20 – RxD
p.21 – TxD
p.22 – ModB
p. 25 – Vss (GND)
p.26 – Vdd (+ 5v)
EWS-3 BMWTNR 8.380.138 HW: 01 SW: 03
|In600:||0F 3F 01 02 03OA00 05FF FF FF FF FF FF FF FF||
B600-B60F – Fault codes
|B610:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 04 FE||B61E – Fault code number|
88 38 01 38 01 81 81 07 32 97 06 55 F0 00 F0 FF
B620-B62A – ID EWS
|B630||FF FF 00 40 FF 0A 01 0A 0A F8 10 38 00 19 5C 24||B63B-B640 – Password|
|B640:||14 C3 04 9E AB 07 F8 F5 B2 F2 AD 47 93 64 A0 El||B641-B657 – KEY 0|
|B650:||98 DB 41 OF EC 05 02 00 C3 04 9E 26 B6 01 DE 96||B658-B66E – KEY 1|
84 0E DA 6A FC 21 6D B2 0F 9A 23 6A CE FC 00 C3
B66F-B685 – KEY 2
|B670:||04 52 36 EB 49 88 FF 64 25 EC 66 1F 02 A3 E6 89|
|B680:||B7 D6 E7 D9 11 00 C3 04 49 C6 D3 6D F1 8B FE 5B||B686-B69C-KEY 3|
18 0B 5A 66 F7 99 B5 1E 67 46 31 C7 00 02 04 EB
B69D-B6B3 – KEY 4
|B6A0:||8A 6F B6 38 55 OS 76 FF FF FF FF FF FF FF FF FF|
|B6B0:||FF FF FF FF 02 04 64 5EA0 39 38 21 0D AE FF FF||
|B6C0:||FF FF FF FF FF FF FF FF FF FF FF 02 04 57 9E CA||B6CB-B6E1 – KEY 6|
|B6D0:||9E 63 28 DD 3E FF FF FF FF FF FF FF FF FF FF FF|
|B6E0:||FF FF 02 04 80 68 FOR 81 A9 F8 D6 F5 FF FF FF FF||B6E2-B6F8 – KEY 7|
|B6F0:||FF FF FF FF FF FF FF FF FF 02 04 60 F3 7E 5E 34||B6F9-B70F-KEY 8|
|B700:||91 C9 D0 FF FF FF FF FF FF FF FF FF FF FF FF FF|
02 04 B4 53 00 E0 11 41 EA 60 FF FF FF FF FF FF
B710-B726 – KEY 9
|B720:||FF FF FF FF FF FF FF 00 01 4A 44 02 01 8C 00 00||B729-B72B – Odometer 1|
|B730:||00 2B FF FF FF FF FF 20 2C A3 4D 18 10 01 00 B6||B737-B744 – FGSTNR|
|B740:||03 10 82 06 59 FF FF FF FF FF FF FF FF FF FF FF|
|B750:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF|
|B760:||FF FF FF FF FF FF FF 53 61 00 00 32 00 01 08 00||B767-B77A – Coding|
|B770:||04 80 14 04 45 00 00 7F E7 F6 56 FF FF FF FF FF|
|B780:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF|
|B790:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF|
|B7A0:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF|
|B7B0:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF|
|B7C0:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF|
|B7D0:||FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF||B7E4-B7E6 – Date of prog.|
|B7E0:||FF FF FF FF 05 09 97 FF 4A 44 02 19 44 00 00 19||B7E8-B7EA – Odometer 2|
|B7F0:||44 5D 00 00 19 44 5D FF FF FF FF FF FF FF FF FF||B7EB-B7F6 – DME Code|
Odometer: 148554 km (read from right to left – 02444A (hex) – convert to DEC)
Used keys – KEY 0 – KEY 3 (sign – the presence of changing code)
In the controller dump
B640: .. SZ 04 9E AB 07 F8 F5 B2 F2 AD 47 93 64 E1
B650: 98 D8 41 OF EU 05 02 00 .. .. .. .. .. .. .. ..
– NW 04 – header (key is adapted)
– 9E AV 07 F8 F5 B2 F2 AD – permanent key code (8 bytes)
– 47 93 64 E1 98 D8 41 OF EU 05 02 – changing code (12 bytes)
B6B0: .. .. .. .. 02 04 64 5E A0 39 38 21 0D AE FF FF
B6C0: FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. ..
– 02 04 – header (key not adapted)
– 64 5E AO 39 38 21 0D AE – permanent key code
– FF FF FF FF FF FF FF – FF code is missing (the key was not used)
January 03, 2018
December 27, 2017
Model example:BMW F10 USA 535i 2011
(Credit to GermancaraTVO. You are at your risk)
Xprog m box ecu programmer
BMW ENET cableand E-sys coding software
From beginning to end - reset (mileage, VIN) => coding. Quickly and specifically according to the case. Finally - a happy owner!
The real mileage before zeroing - 75103 km (according to VIN the meter lived earlier)
Next, disassemble the meter to get the proper access to the elements with which I will work
Next comes theXprog-mprogrammer, by means of which I gain access to the meter's memory and do zeroing.
Now with us on the table a ready to program / coding counter in the car withE-sys
Actually, the issue of coding for a specific car
And the end result without any kind of errors
December 25, 2017
On the BMW F10, it is possible to code Internet / BMW Live with 6VC Combox and 609 Nav by disabling BMW Assist and using a fake VIN with factory 614 Internet written to Combox, and then updating BMW Services.
I detailed that process here:
Change your VO as follows:
– 612 (or 633 or 639 if present)
+ 614 (Required but already present)
VO CODE HU_CIC
VO CODE CMB_MEDIA
FDL CODE CMB_MEDIA:
– TELEMATIK_VIN = Coding_VIN
FDL CODE CMB_MEDIA:
Use modified VO with VIN that has factory options 614 and 615 as explained below:
it is very simple to write a VIN to the Combox inE-Syscoding software
Spend time in Tool32, CMEDIA.prg and E-Sys trying to figure it out.
First you must code CMB_MEDIA / TELEMATIK_VIN = Coding VIN using your real FA VIN. Then, open your FA up in the FA-Editor, change the VIN, Caluclate FP just to make sure there are no problems with it, and then save the FA with a new name, i.e. FA_VIN_FAKE. Lastly, go to the coding module, and under Vehicle Order load your new FA_VIN_FAKE, activate FA, and then FDL code CMB_MEDIA. Lastly, read CMB_MEDIA coding data, and verify the new VIN in brackets. In the attached picture, you can see my Combox and Head Unit are showing two different VIN’s.
Afterwards, either shut down E-Sys, or load your original FA back and activate it before coding anything else. DO NOT code anything else with this FA, and DO NOT write this FA to the car.
For Internet and BMW Live to work, you need a VIN with factory options 614 and 615.
*** Use only to FDL Code CMB_MEDIA; DO NOT write this FA to the Car
1) Enable Data Transfer Option Under Phone
2) Enable Bluetooth Data Tethering on Phone
3) Under Connected drive; Update services (should show BMW Live and Internet services)
4) Go to BMW Live and Internet and make sure it it working
After it is working:
Use original VO with car VIN:
FDL CODE CMB_MEDIA:
– TELEMATIK_VIN = MOST_VIN
Read CMB_MEDIA and verify Short VIN in brackets [xxxxxxx] is car VIN.
DO NOT update services again or you will loose BMW Live and Internet.
*** If you do not return the Combox VIN to car VIN, you will encounter problems with future dealer programming, as the Combox will not be recognized, and programming will hault.
All done with aBMWENETcablewith Esys. $11 did all.
December 14, 2017
- RheingoldISTA + Standalone: v4.09.13
- SQLiteDBs: v4.09.12
30 queries taking 0.0769 seconds, 106 records returned.
Powered by Minx 1.1.6c-pink.