April 21, 2018
1.BMW Enet cable
2. Laptop with E-Sys and E-Sys Launcher installed
3. Attach the FSCGen file (unzip it to C: \)
2. After cable connection (①), go to next screen by FSC_Extend ②
3. Enter 0x63 (③), click Identity (④), confirm that HU_NBT is coming up (⑤)
4. Enter 0xDE (⑥) and 0x1 (⑦) as shown below, then press StoreFSC (FSC Save, ⑧)
5 Click Read button (⑩) and press SAVE button to save as DE, fsc
6. Copy the attached file to 'C: \' and copy the above saved DE.fsc to C: \ FSCgen, then run the window command window and type 'cd \' to move to the root directory Then, enter 'cd FSCGEN' to go to FCSGen, which is the directory saved above.
7. Enter 'nbt, exe DE.fsc 0xA6 0x28 *******' (where ******* is the chassis number of your car)
8. This will launch the program in the command window and generate the system code.
Remember this code and use it in your navigation updates to update your navigation on your own.
The vehicles that can be updated in this way are only available for vehicles with the H-NBT and later F series. The E Series can not be updated this way, and the navigation is actually annoying, but using WoW navigation or teeming is good for mental health.
Download E-sys 3.26.1 to generate BMW FSC code
April 20, 2018
April 13, 2018
Purpose:write/code VIN after FRM2 update
Software:NCS expert, Tool32, WinKFP
Tutorial:Upgraded to FRM2 – how do i code it?
The basic steps are:
1. Install FRM2
2. Change FRM2 VIN to yours. Flash FRM2 withWinKFPcomfort mode with your VIN. Or use Tool32 to change VIN as above.
2.5. Verify VIN change with Tool32.
3. Copy CAS VO (FA) to FRM with NCSexpert.
4. Change date with NCSexpert.
5. Code to default with NCSexpert.
Exact instructions for each step are discussed and available in the following parts.
It’s very simple.
1. Open Tool32
2. Plug in cable
3. Press F3 and choose the FRM87.prg or whatever FRM you have (see from INPA uif)
4.Select job c_fg_schrieben
5. Enter your FULL VIN (including checksum) into arguments field
6. Execute job
You can check the VIN using job ‘c_fg_lesen’
Once done use NCS EXPERT to copy your CAS FA string to FRM / change date then code to default with expertmode.
Btw, when you enter your VIN you must use FULL VIN. Which is VIN number with a checksum at the end. You can see you full VIN inNCS expertwhen you do any coding.
Note: Step 2 means you won’t need to use Tool32 at WinKFP can set VIN also…
The basic steps:
1) Remove FRM, install FRM2.
2) Use WinKFP to program the module, make sure to enter your VIN-number before programming.
3) Switch to NCS-EXPERT. Get your Vehicle Order from the CAS module (as we are unsure of what the FRM2 module contains.
4) Write the Vehicle Order to module "FRM” using job "FA_WRITE”
5) Go back to the main menu (or restart ncs-expert) and get the vehicle order from the "NFRM” module. Make sure NFRM returns YOUR VIN and YOUR VO. We want the VIN (FG) and VO (FA) to be the same in both CAS and NFRM.
6) You now need to do the trick described by 4711 a couple of posts back, i.e. change the production date in the VO to at least #0307. If you don’t do this, ncs-expert will not list NFRM (=FRM2) in the "Process ECU”-list and you won’t be able to code it. Change the VO using the "Enter FA” option – remove your production date and enter #0307 (meaning march 2007).
7) Now click "Process ECU” and select "NFRM”
Then just code to default with expert mode.
Reference: Youtube video – E90 VIN change with NCS Expert
Here lists possible solutions from users to help those with error "Programming is not possible”when using BMW ISTA+.
Error message:I get message after reading all ECU’s
"Programming is not possible”
If I click this message away I can just continue.
I have:bin, binx64, host, hostx64
But which files/maps must be located in map PSdZ?
Try it with the BLP data so the folder "data”under C / Rheingold / PSdZ / data ..
Of course, in the Reg also specify that the data is available but still as you have made everything on "false” ..
you unpack the BLP under C / Rheingold / PSdZ / and you get the folder "data” ..
So C / Rheingold / PSdZ / data ..
"Product Version” = "220.127.116.1135”
"Main Product Version” = "4.10”
"Data version” = "10/04/31”
"Logistic Base Version” "10/04/30”
"SWIData” = "04/10/30”
"BMW.Rheingold.Programming.Enabled” = "True”
"BMW.Rheingold.Programming.PsdzDataPath” = ".. \\ .. \\ .. \\ \\ PSdZ data_swi”
If it doesn’t work, try the following solution. It works for someone in earlier version.
In earlier versions this worked:
Have not tried on latest.
P.S. BLP must be installed normally into data folder. No need to create any empty folders.
Still had psdz path set to data_swi. You must adjust it to be data instead of data_swi when no sdp installed. Then it should not complain and work. BLP data MUST be installed in all cases.
Create empty folders
Windows Registry Editor Version 5.00
Directory of c:\Rheingold\PSdZ
06-Apr-18 22:13 <DIR> .
06-Apr-18 22:13 <DIR> ..
29-Mar-18 19:35 <DIR> bin
29-Mar-18 19:35 <DIR> binx64
06-Apr-18 22:13 <DIR> data
16-Mar-18 09:25 <DIR> data_swi
29-Mar-18 19:35 <DIR> host
29-Mar-18 19:35 <DIR> hostx64
Directory of c:\Rheingold\PSdZ\data_swi
16-Mar-18 09:25 <DIR> .
16-Mar-18 09:25 <DIR> ..
16-Mar-18 09:52 <DIR> psdzdata
Directory of c:\Rheingold\PSdZ\data
06-Apr-18 22:13 <DIR> .
06-Apr-18 22:13 <DIR> ..
06-Apr-18 22:13 <DIR> psdzdata
April 10, 2018
- replace the used engine module to F11 2012, because the original was totally dead after incorrect power connection during chip-tuning and remained forever in the parking lot.as a consequence of the lack of communication on the table with the processor in the boot mode.
BMW ICOM A2/ICOM Nextemulator withISTA-D ISTA-Pprogramming software
1. Readout of the immo CAS4 data
2. After reading the data, it became clear that CAS4 EWS5 crypto.
3. Next decode CAS4 memory to obtain the synchronization code.
4. Entry of received synchronization code into the new-used DDE741 engine ecu.
5. Change of three VIN codes in the new-used engine control unit.
6. Zeroing the mileage in the new-used engine controller because the mileage in it was 116335km, and in the car 227140km.
March 31, 2018
The friend who made this is called Dr.GINI.
The advantage of this program is that can be used on both E-series and F-series.
–ECU: Use in Expert menu
–EDIABAS: EDIABAS installation file
–INTERFACES: EDIABAS.INI file for each interface
–MAPS: Latest lookup.xml file for map updates
–setup Dr.GINI EN Basic.exe: B021 installation file based on B020
-Convenient to use ICOM in Interface
Delete Fault Code
Deleting fault code of module is very fast and quick
In the functional window, click 1.Identification 2.Read Errors at the bottom
You don’t have to turnRheignoldto try to delete the fault code.
on the right side.
March 23, 2018
Download BMW old USB diagnostic interface software
(Note: This is only for old customers. This software is useless without proper USB device)
- v140-1012.zip(Alt link) - with USB drivers up to Windows 7 (custom VID&PID)
ZIP SHA256: bba2239bafbaf4d98b10e2e51cbba93738ec15a9dcf53627e94dc3ddada2424f
- v140-1012f.zip(Alt link) - with USB drivers up to Windows 8 (default FTDI VID&PID)
ZIP SHA256: 5770284d029e927647383f3c1f31a2af9968301b5218035de62738037383853e
- v140-1012f_10.zip(Alt link) - with USB drivers up to Windows 10 (default FTDI VID&PID)
ZIP SHA256: 65aa90565950cfbae31ee937f76ff1b58810cb8c0ce3a9cdfa2b08584ffc358b
- v210_62b.zip(Alt link) - with USB drivers up to Windows 8 (default FTDI VID&PID)
ZIP SHA256: 2f5a9a3e3e09bb78a332b36c32c50f3d1699af7aab837b53ec64cdec613ba336
- v210_62b_10.zip(Alt link) - with USB drivers up to Windows 10 (default FTDI VID&PID)
ZIP SHA256: f59e12f0fe5d9c280e48e16bdd0f8a34ca991fa08ea9f53b7a2ee6e5ccde1f86
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):
30 queries taking 0.0806 seconds, 108 records returned.
Powered by Minx 1.1.6c-pink.