E85 used SIM85 coding with NCSExpert / ISTA-P
- Thread starter Hansdampf
- Start date
Attleborough, Norfolk
Good morning to all.
As many of you, I´m locked at the same point with the replacement of my central airbag module. In my case, the original part number is 6935920 and the second hand one that I´ve bought, is 6938264.
I´ve no problems with the winkfp part of the process. I can flash the unit and write the vin of my car w/o issues. From this point, the unit is shown as 6962767. But, when I get to the ncs part, I´ve the same message on the screen that some of you and I can´t follow with the process.
It seems that, first versions of the unit (my car is 2003 and has the first reference available) have problems to be replaced with others olders than 6965147.
I have now installed, Ista+, Inpa, Winkfp, Ncs Expert, etc... and have the possibility to install Ista-P.
Any kind of help will be wellcomed.
As many of you, I´m locked at the same point with the replacement of my central airbag module. In my case, the original part number is 6935920 and the second hand one that I´ve bought, is 6938264.
I´ve no problems with the winkfp part of the process. I can flash the unit and write the vin of my car w/o issues. From this point, the unit is shown as 6962767. But, when I get to the ncs part, I´ve the same message on the screen that some of you and I can´t follow with the process.
It seems that, first versions of the unit (my car is 2003 and has the first reference available) have problems to be replaced with others olders than 6965147.
I have now installed, Ista+, Inpa, Winkfp, Ncs Expert, etc... and have the possibility to install Ista-P.
Any kind of help will be wellcomed.
After many hours of searching, reading and making tests in my own car with a 6938264, the conclusion that I take is that, there are two groups of units and they are not compatible between them.
In the first group we´d have the following references: 6928570, 6935920 and 6965147.
The secong group we´d have these others: 6933933, 6938264, 6939811 and 6962767.
In fact, when you update de ZUSB number with Winkfp, you can choose the 6965147 option for the first, and the 6962767 for the second.
The other thing that make me think this is that, the 6965147, is still available on BMW as a spare part.
In the first group we´d have the following references: 6928570, 6935920 and 6965147.
The secong group we´d have these others: 6933933, 6938264, 6939811 and 6962767.
In fact, when you update de ZUSB number with Winkfp, you can choose the 6965147 option for the first, and the 6962767 for the second.
The other thing that make me think this is that, the 6965147, is still available on BMW as a spare part.
Montauban
Hi everybody,
I experienced exactly the same issue, trying to replace my old SIM85 module by another one : blocked at coding level because of the index : since may, anybody has finally found the fix? The references are fully compatible both way according to real-oem. The new one is giving errors linked to passenger airbag deactivation key (which is not installed on my car)
I experienced exactly the same issue, trying to replace my old SIM85 module by another one : blocked at coding level because of the index : since may, anybody has finally found the fix? The references are fully compatible both way according to real-oem. The new one is giving errors linked to passenger airbag deactivation key (which is not installed on my car)
ivanchen1211
Member
Have you tried flashing using WINKFP and write your VIN code in (input VIN before the flash begin)?
ivanchen1211
Member
Did you use factory coding profile?
And if you choose codierdaten lesen, will it work(show coding ended)?
And if you choose codierdaten lesen, will it work(show coding ended)?
ivanchen1211
Member
Try this:
flash the ZB file corresponding to your car VO, then do factory coding using factory profile
you can check using real oem or just simply look at your VIN number
For example WBA"BT32"060LS23055
;Fahrzeugzuordnung (Auftrags-Steuerdatei) vom 26.04.2005 12:58
;TAIS-Abfragedatum (ab) 12.05.2005
FZG;LA;SA;ZB_NR;SE_VS
BT11;;;6962767;SE
BT11;;;6965147;SE
BT12;;;6962767;SE
BT12;;;6965147;SE
BT31;;;6962767;SE
BT31;;;6965147;SE
BT32;;;6962767;SE
BT32;;;6965147;SE
BT33;;;6962766;SE
BT33;;;6965146;SE
BT51;;;6962767;SE
BT51;;;6965147;SE
BT52;;;6962767;SE
BT52;;;6965147;SE
BT53;;;6962766;SE
BT53;;;6965146;SE
BT91;;;6962767;SE
BT92;;;6962767;SE
BT93;;;6962766;SE
BU11;;;6962767;SE
BU12;;;6962767;SE
BU31;;;6962767;SE
BU32;;;6962767;SE
BU33;;;6962766;SE
BU51;;;6962767;SE
BU52;;;6962767;SE
BU53;;;6962766;SE
BZ11;;;6962767;SE
BZ12;;;6962767;SE
DU51;;;6962767;SE
DU52;;;6962767;SE
DU53;;;6962766;SE
DU91;;;6962767;SE
DU92;;;6962767;SE
DU93;;;6962766;SE
flash the ZB file corresponding to your car VO, then do factory coding using factory profile
you can check using real oem or just simply look at your VIN number
For example WBA"BT32"060LS23055
;Fahrzeugzuordnung (Auftrags-Steuerdatei) vom 26.04.2005 12:58
;TAIS-Abfragedatum (ab) 12.05.2005
FZG;LA;SA;ZB_NR;SE_VS
BT11;;;6962767;SE
BT11;;;6965147;SE
BT12;;;6962767;SE
BT12;;;6965147;SE
BT31;;;6962767;SE
BT31;;;6965147;SE
BT32;;;6962767;SE
BT32;;;6965147;SE
BT33;;;6962766;SE
BT33;;;6965146;SE
BT51;;;6962767;SE
BT51;;;6965147;SE
BT52;;;6962767;SE
BT52;;;6965147;SE
BT53;;;6962766;SE
BT53;;;6965146;SE
BT91;;;6962767;SE
BT92;;;6962767;SE
BT93;;;6962766;SE
BU11;;;6962767;SE
BU12;;;6962767;SE
BU31;;;6962767;SE
BU32;;;6962767;SE
BU33;;;6962766;SE
BU51;;;6962767;SE
BU52;;;6962767;SE
BU53;;;6962766;SE
BZ11;;;6962767;SE
BZ12;;;6962767;SE
DU51;;;6962767;SE
DU52;;;6962767;SE
DU53;;;6962766;SE
DU91;;;6962767;SE
DU92;;;6962767;SE
DU93;;;6962766;SE
ivanchen1211
Member
delete everything in this file, make this file blank C:\NCSEXPER\WORK\FSW_PSW.MAN
then try the default profile in the second, go SIM85 and try execute SG_CODIEREN
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.
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.
Well, I’ve worked my way through all this thread and having done many airbag module recoding jobs now I have to say I’m at a loss to know why you are all getting so deeply into it? If you follow the guide promulgated on the forum it is actually fairly straightforward. No need for all this manipulation of files etc.
Am I missing something? Is there some extra issue cropping up?
I’ve only done about 30 so far but never had all this grief.
Are you all over complicating the issue? Would going back to basics and following the guide at least give us some idea what the problem is? It seems to have gone so far off track as to be impossible to work out.
Am I missing something? Is there some extra issue cropping up?
I’ve only done about 30 so far but never had all this grief.
Are you all over complicating the issue? Would going back to basics and following the guide at least give us some idea what the problem is? It seems to have gone so far off track as to be impossible to work out.
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.
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.