E85 used SIM85 coding with NCSExpert / ISTA-P

[Hansdampf]

Hey guys,

need your help in order to get this issue sorted. Read many threads over and over again, just can't find any useful help.

Situation: E85 Z4 year 2003 needs to be fitted used Airbag module SIM85

What I allready did, is flashing correct Dataset and VIN with ISTA-P. Flashing was OK, but coding failed.

Then I tried

• coding with NCSExpert, but it keeps failing, because of "Der Codierindex folgender Steuergeräte ist für diesen Codierauftrag nicht zulässig: SIM 05", meaning, the coding index is not used for this action.

• Then I tried it with expert mode, so I could change die coding index manually from SIM_E85.C01 to SIM_E85.C05 --> still the same error message

• Coding read and write is throwing the same error message

• Using Kernfunktionen/Basicfunctions, coapiReadNettoDataFromSg and coapiReadSgGetFswPsw is running fine, I get the correct .TRC file
  But trying to write any coding to the controll unit just keeps failing.....

• Re-flashing with WinKFP does not change anything.

Any ideas, how to get the job done?

Thank you so much in advance, appriciate any help,
Hans

 

[bigwinn]

Paging

enuff_zed

for input too

Step one Hans, have you got winkfp in your software bundle?

The process is usually

Winkfp- flash the module and code bin
NCS expert next
Tool 32 to align system time

 

[bigwinn]

Also- this step by step guide is the basis of how most code modules to cars at the mo- worth a read as it’s definitive

https://z4-forum.com/forum/viewtopic.php?t=115539

 

[enuff_zed]

Also- this step by step guide is the basis of how most code modules to cars at the mo- worth a read as it’s definitive

https://z4-forum.com/forum/viewtopic.php?t=115539

Tbf Stuart, that’s the thread he initially asked on
I was going to suggest exactly the same though. Use the instructions that are linked in that thread if possible. As most of us use those steps it will be easier to assist once we can see exactly what step you get stuck on.
One quick question though: is your replacement SIM85 definitely a compatible part number for the original?

 

[enuff_zed]

Reading it over a few times to understand it better: when I do it I use INPA purely to check fault codes and clear them. All the work is done simply by using WinKFP, NCS Expert and Tool32.
I have even been to garages to code for them as they have been trying with ISTA and failing!

 

[Street]

I’d be interested in what steps you’re taking to setup NCSExpert before coding.

You select the e85 chassis, pull the VO from the light module, pick your sim85 module then read it.
Does that all sound familiar?
Can you post photos of the job just before running it?

Also have to managed to code a module before or is this the first time? I’ve once had an issue where the previous owner had obviously tried by swapping out with the wrong part number. I blindly followed trying to replace like for like parts without cross referencing the vin.

 

[Hansdampf]

Thx for your answers so far!

• Yes, I do have the Standard BMW tools like WinKFP and I used it

@Street:

• Yes, I select e85 chassis, pull VO from Lightmodule (also tried to pull it from dashboard....but does not change anything)

• Allready coded modules before....without issue

• Coding of SIM85 just keeps failing, while other modules on that car can be coded like usual

• Regarding wrong partnumber, I also hat that suspision in mind. But I double checked it with ETK, it's the right module. Even ISTA-P is fine with the module

What else could be the problem?

 

[enuff_zed]

Thx for your answers so far!

• Yes, I do have the Standard BMW tools like WinKFP and I used it

@Street:

• Yes, I select e85 chassis, pull VO from Lightmodule (also tried to pull it from dashboard....but does not change anything)

• Allready coded modules before....without issue

• Coding of SIM85 just keeps failing, while other modules on that car can be coded like usual

• Regarding wrong partnumber, I also hat that suspision in mind. But I double checked it with ETK, it's the right module. Even ISTA-P is fine with the module

What else could be the problem?

Possibly a bad replacement module?

 

[Hansdampf]

@enuff_zed: I thought about that, too. But besides coding, it's behavior is completly normal....Flashing with WinKFP works fine, Tool32 works fine on the module, Reingold/ISTA no problems, too. No strange DTCs entries....only two entries that should be easyly solved by coding to the vehicle.

"Only" Coding makes problems. Tried with BMW Scanner 1.4, coding index is read fine as 05. Tried with with Abrites, it says, no coding index can be retrieved.

At the end of the day, I'd guess some strange problem in the coding files used in NCSExpert. But I tried with two different laptops/installations, always ends up with the same error.

 

[enuff_zed]

@enuff_zed: I thought about that, too. But besides coding, it's behavior is completly normal....Flashing with WinKFP works fine, Tool32 works fine on the module, Reingold/ISTA no problems, too. No strange DTCs entries....only two entries that should be easyly solved by coding to the vehicle.

"Only" Coding makes problems. Tried with BMW Scanner 1.4, coding index is read fine as 05. Tried with with Abrites, it says, no coding index can be retrieved.

At the end of the day, I'd guess some strange problem in the coding files used in NCSExpert. But I tried with two different laptops/installations, always ends up with the same error.

I understand what you are saying, but you are getting closer to only one remaining common factor, the SIM85.
If you could get another to try, you can remove the coin holder behind the handbrake and reach through to unplug the wires and the fibre-optics. They will pull though and you can attach a module with it resting on top of the console. If it works, then you can look at installing it properly once it is coded.

 

[Street]

Sounds like you know what’s going on so like the other guys I’m edging towards a faulty unit as well. I don’t know how the flash memory blocks are indexed or structured but perhaps a block is corrupt and only shows up when trying to read or write from it.

A complete long shot however; the part number I failed to code was 6938264. I tried two replacements so the chance of hardware failure was low. As soon as I switched to an alternative compatible number it all fell into place like normal. To this day have no idea why.

 

[Hansdampf]

@enuff_zed, @Street: many thx for your thoughts....I'm totally with you, a faulty unit is pretty rare, but still can happen. But those units are hard to get, that's why I was hoping for some magician pointing me to something I did not realize...

I need to talkt to customer how to handle that one...I'll keep you postet, how things ended up.

 

[enuff_zed]

@enuff_zed, @Street: many thx for your thoughts....I'm totally with you, a faulty unit is pretty rare, but still can happen. But those units are hard to get, that's why I was hoping for some magician pointing me to something I did not realize...

I need to talkt to customer how to handle that one...I'll keep you postet, how things ended up.

I would definitely suggest putting the VIn into Realoem to check you do in fact have the correct number fitted. This will also give you the list of exchangeable options which may widen your search.

 

[ponzy]

Following as i am experiencing the same error message at the same part of the process, but have minimal experience with coding, so can only follow the suggested crib sheet. Scared to try anything else in case i make it worse !!!

 

[ponzy]

googled a bit last night found someone changing a LCM in a X5 and he had the same error, the conclusion for error was that NCS thinks that the LCM, in his case, is not compatible with the vehicle order.

 

[enuff_zed]

googled a bit last night found someone changing a LCM in a X5 and he had the same error, the conclusion for error was that NCS thinks that the LCM, in his case, is not compatible with the vehicle order.

But I’m sure you confirmed you had the correct part number?

 

[ponzy]

Yes, original faulty sim, part number 6935920. Purchase a used unit part number 6939811,after edit vin and flash process using WinKFP, as per crib sheet, its now given it a part number 6962767 it also gives the physical hardware number as 6939811 which can be seen via INPA Ive checked with realoem and all seem exchangeable.

 

[Hansdampf]

Interesting post....do you have exaclty the same error message? "Der Codierindex folgender Steuergeräte ist für diesen Codierauftrag nicht zulässig: SIM 05"

 

[Street]

I dont think the saftey control module is going to be an option on the vehicle order. Maybe a 'SV63A Airbag deactivation' has been added to try and bypass the issue. Grasping at straws here though as the Safety module does more than airbags. I've never found a way to 'code out' airbags on the pre facelift.

 

[Hansdampf]

Even if vehicle order does not fit the module to be coded, I'd expect at least to be able to read the coding. But even that does not work the usual way, only via basic functions.