E85 used SIM85 coding with NCSExpert / ISTA-P

Stef82FR said:
Hello i was thinking the same...this is not the first module i code. What i see is that these modules should be compatible but when i have a look at the HIS file in NCS expert, it appears it is not...you can't go from my original std to the one i bought...even if compatible in real-oem. I ran through a lot of forum and this issue of index is documented in several places...and I never seen a fix.

So to summarize my conclusion is that you can replace a 6928570 by a 6935920 or a 6965147 . But not with a 6938264 a 6939811 or a 6962767 : two different chains of compatibility contrary to what real-oem describes. At least it is not possible with the standard procedure winkfp+ncsexpert.
Click to expand...
They should all end up as a 2767 when coded. I have proved to myself that once you reach 2767 you cannot use an earlier one, but had no issues upgrading any of those to 2767………. So far
 
Then how have you done it? It started like that for me: it has been upgraded automatically to 767. But impossible to code it for this story of different index. I tried also with ISTA-P and it failed... it is a nightmare really :)
 
Stef82FR said:
Then how have you done it? It started like that for me: it has been upgraded automatically to 767. But impossible to code it for this story of different index. I tried also with ISTA-P and it failed... it is a nightmare really :)
Click to expand...
Ah I don’t use ISTA. I use INPA, WinKFP, NCS Expert and Tool32
 
Same for me. I tried ISTA-P after as i was not succeeding with these tools. The good thing is that i learnt a lot on winkfp and ncsexpert! Even if not successful..
 
Stef82FR said:
Hi, I tried and it was not working. I tried several things including some profile customization within NCS expert. At the end i successfully read the module , with C05 standard. But after still impossible to write the modified file inside after exporting from NCS dummy.

At the end i tried again to flash with winkfp and there was an issue... during the flash process.... the module is bricked now... I could try to find a bin file to write again the eeprom with bmwscanner as it can still communicate apparently...but don't know where to find a clone file to write the eeprom.
Click to expand...
you can just select the daten zb number from the winkfp and flash again using 6965147

You HAVE to hook to a battery tender before and during the flash to keep the voltage above 12V or the process will fail.

If you are interested I could take a look using remote anydesk.

My experience of coding a new SGM module on E60 is, flash winkfp with new VIN, factory coding it using nscexpert, start time link with airbag system using tool32.

Shouldn't be too different on E85.


1766381130464.png
 
Last edited:
enuff_zed said:
They should all end up as a 2767 when coded. I have proved to myself that once you reach 2767 you cannot use an earlier one, but had no issues upgrading any of those to 2767………. So far
Click to expand...
No, it's not what from the HIS file says

;Zusbauhistorie vom 26.04.2005 12:58

;SG-TYP: SIM85

;ZB-ALT ZB-NEU FREIKENNUNG

;--------------------------'

6935920,6965147,00,HK

6928570,6935920,00,HK

6938263,6939810,00,HK

6939810,6962766,00,HK

6927552,6938263,00,HK

6928953,6935919,00,HK

6935919,6965146,00,HK

6939811,6962767,00,HK

6938264,6939811,00,HK

6933933,6938264,00,HK
 
From daten file, at least your manufacture year has to be newer than 2003/10 to be able to code SIM_CI_05, you can simply change the manufacture date in NSCexpert VO to #1003 and code it.

A #0902 A_SERIE V_SERIE2 V_SERIE PTO GM5_CI_03 GM5_CI_04
>>> SBSL_CI_02 SBSR_CI_02 //Serie, 09.2002

A #0303 A_SERIE V_SERIE2 V_SERIE PTO GM5_CI_03
>>> GM5_CI_04 SBSL_CI_02 SBSR_CI_02 STV_US //Massnahmen zum 03.2003

A #1003 OKTOBER03 A_SERIE V_SERIE2 V_SERIE PTO
>>> GM5_CI_03 GM5_CI_04 SBSL_CI_02 SBSR_CI_02 STV_US
>>> SBSL_CI_04 SBSR_CI_04 SIM_CI_02 SIM_CI_03 SIM_CI_04
>>> SIM_CI_05 //Massnahmen zum Oktober 2003

A #0404 APRIL04 OKTOBER03 A_SERIE V_SERIE2 V_SERIE PTO
>>> GM5_CI_03 GM5_CI_04 SBSL_CI_02 SBSR_CI_02 STV_US
>>> SBSL_CI_04 SBSR_CI_04 SIM_CI_02 SIM_CI_03 SIM_CI_04
>>> SIM_CI_05 //Massnahmen zum April 2004

A #1004 OKTOBER04 APRIL04 OKTOBER03 A_SERIE V_SERIE2 V_SERIE PTO
>>> GM5_CI_03 GM5_CI_04 SBSL_CI_02 SBSR_CI_02 STV_US
>>> SBSL_CI_04 SBSR_CI_04 SIM_CI_02 SIM_CI_03 SIM_CI_04
>>> SIM_CI_05 //Massnahmen zum Oktober 2004
 
ivanchen1211 said:
No, it's not what from the HIS file says

;Zusbauhistorie vom 26.04.2005 12:58

;SG-TYP: SIM85

;ZB-ALT ZB-NEU FREIKENNUNG

;--------------------------'

6935920,6965147,00,HK

6928570,6935920,00,HK

6938263,6939810,00,HK

6939810,6962766,00,HK

6927552,6938263,00,HK

6928953,6935919,00,HK

6935919,6965146,00,HK

6939811,6962767,00,HK

6938264,6939811,00,HK

6933933,6938264,00,HK
Click to expand...
Ah what would I know eh?
Your list is not in order. Follow it through, each time you try to update it shows you a new number. Then find that number and see what it takes you too.
As I tried to say, if you use WINKFP it will always update to 2767. You can try it by putting in any of the other numbers instead. It will still give a message saying it’s about to update to 2767.
 
enuff_zed said:
Ah what would I know eh?
Your list is not in order. Follow it through, each time you try to update it shows you a new number. Then find that number and see what it takes you too.
As I tried to say, if you use WINKFP it will always update to 2767. You can try it by putting in any of the other numbers instead. It will still give a message saying it’s about to update to 2767.
Click to expand...
It's a daisy chain, dude... once the number on the right does not show up on the left, it is the final version.
For example, ZB number 6935919 shows up on the right and left, the right besides it is 6965146 and 6965146 doesn't show up on the right, that means it does not have next chain version. If your ZB number is 6935919 winkfp will ask you to upgrade to 6965146. That's why in winkfp and daten there is a 6965146 option, and 6965146 does not update to version 2767. (Unless you manually select it and flash)

This method apply to all E-chassis BMW daten files.
1766397076688.png
1766397092845.png

;Zusbauhistorie vom 26.04.2005 12:58

;SG-TYP: SIM85

;ZB-ALT ZB-NEU FREIKENNUNG

;--------------------------'

6935920,6965147,00,HK

6928570,6935920,00,HK

6938263,6939810,00,HK

6939810,6962766,00,HK

6927552,6938263,00,HK

6928953,6935919,00,HK

6935919,6965146,00,HK

6939811,6962767,00,HK

6938264,6939811,00,HK

6933933,6938264,00,HK
 
ivanchen1211 said:
It's a daisy chain, dude... once the number on the right does not show up on the left, it is the final version.
For example, ZB number 6935919 shows up on the right and left, the right besides it is 6965146 and 6965146 doesn't show up on the right, that means it does not have next chain version. If your ZB number is 6935919 winkfp will ask you to upgrade to 6965146. That's why in winkfp and daten there is a 6965146 option, and 6965146 does not update to version 2767. (Unless you manually select it and flash)

This method apply to all E-chassis BMW daten files.
View attachment 288408
View attachment 288409

;Zusbauhistorie vom 26.04.2005 12:58

;SG-TYP: SIM85

;ZB-ALT ZB-NEU FREIKENNUNG

;--------------------------'

6935920,6965147,00,HK

6928570,6935920,00,HK

6938263,6939810,00,HK

6939810,6962766,00,HK

6927552,6938263,00,HK

6928953,6935919,00,HK

6935919,6965146,00,HK

6939811,6962767,00,HK

6938264,6939811,00,HK

6933933,6938264,00,HK
Click to expand...
Fine.
In the UK, using WINKFP it takes you to 2767 every time.
I will leave you to it…….. dude 😉
 
ivanchen1211 said:
You sound like the Z4 is only sold in UK. I live outside UK and so does many others lol
Click to expand...
No I don’t. I was making it clear that my experience is with UK cars, hence the reason that there may be differences with what we have both experienced.
I don’t want to confuse you with wrong info
 
Hi Guys
first thank you for time trying to help me. First point about the P/N : indeed according to His file the new module i was trying to install could only end in 767. As for manufacturing date, i tried also to change the date : the original one is 0902, and impossible to put something later than 0303, even trying to cheat with some option codes. And then obviously this is why i can't install 767 with C05 version

Regarding the failed flash : yes my car was linked to a charger but for some reason it failed around 80%. I can't no more connect to the module with winkfp I have some errors (i will take a screenshot). I tried to write again the module in bmwscanner as i had a backup file...but it only ends in 2048 errors 😬. Not sure the module is completely dead as it communicates in bmwscanner and INPA but some datas appear clearly corrupted like VIN and so on. But for example i still have the right hw version. I would like to find a mean to repair it at least to sell it. I am searching now another used module compatible with 147 family.
 
Have to say every time I’ve tried to do anything module based to the car (DME and airbag etc) if I’ve had it connected to a charger it doesn’t work

I only code now with no charger attached and a well charged battery
 
It fully blocked coding of DME

It interfered with the first stage of an airbag coding 4 times until I disconnected then it worked

Could be coincidence but I don’t do it now
 
Stef82FR said:
You think charger can disturb winkfp flash?
Click to expand...
Yes. I agree. Disconnect the charger. @bigwinn and I were scratching our heads for ages on a DME flash until we worked that out.
I’m confused with all the talk of changing dates? All I’ve ever done is let WinKFP sort it out for me.
 
Stef82FR said:
Hi Guys
first thank you for time trying to help me. First point about the P/N : indeed according to His file the new module i was trying to install could only end in 767. As for manufacturing date, i tried also to change the date : the original one is 0902, and impossible to put something later than 0303, even trying to cheat with some option codes. And then obviously this is why i can't install 767 with C05 version

Regarding the failed flash : yes my car was linked to a charger but for some reason it failed around 80%. I can't no more connect to the module with winkfp I have some errors (i will take a screenshot). I tried to write again the module in bmwscanner as i had a backup file...but it only ends in 2048 errors 😬. Not sure the module is completely dead as it communicates in bmwscanner and INPA but some datas appear clearly corrupted like VIN and so on. But for example i still have the right hw version. I would like to find a mean to repair it at least to sell it. I am searching now another used module compatible with 147 family.
Click to expand...
You can't delete #0902 and add #1003? In this stage you don't have to write vo into the lcm or ews, just have to go straight to SIM85 ECU and code it
 
You must log in or register to reply here.
Back
Top Bottom