Airbag ECU Programming Help *Solved*

[colb]

At step 23 you have systemzeit_lessen (write) which is read not write I think it should be systemzeit_schriben which is (write) so the data gets written to the module. I have been trying to change the Vin number on a used main module using all the software I have but the module dosn't come up as an option, think I need an older Daten file.

 

[gornlordunoboggle]

I agree system_lessen does seem like its not what to use. The only thing I've dared trying outside of the guide was entering 1 in the argument box for system_schriben but it says is "no communication with module" in the note pad text box. i found some other accounts of this happening to people.. I heard ISTA might be able to do the system start time for the air bag modules and i'm going to try this next I'll update if its successful.

 

[Ali0191]

I recently went through and used TomRs guide. I slightly updated it on this thread:

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

My update was mainly because I clearly had a different version of the software so the steps were different wording etc. but I used the lessen line and it worked.

 

[gornlordunoboggle]

quick stupid question. when you say type 1 in the argument box what ive been doing is putting "1" in the box. Is that right or am i actually meant to select the first drop down option 55aa?

 

[gornlordunoboggle]

When i run systemziet_lessen with 1 it seems fine the text box shows OKAY in it which i interpret as good. but when i run systemzeit_starten I get the yellow box tint in the box below arguement "job info gelesen" & ERROR ECU CONDITIONS NOT CORRECT OR REQUEST SEQUENCE ERROR in the text box.

 

[gornlordunoboggle]

Gentlemen! I have done it! NO AIR BAG LIGHT ON THE DASH!
now I can give back to community for others who the current guide isn't enough.

I wish Id wrote more down and took more pictures since this is gonna be a bit patchy but I promise its fairly intuitive and it worked.


first here is what I read about how the system time error works for the air bag module. It needs to have a higher time then all the satellites so if you're in TOOL32 I'd recommend resetting the 4 satellites modules (SBSL /SBSR / STVL / STVR) and not touching the SIM module system time since you want it as high as you can get it. Even if that turns out to be bad advice (I reset all 4 satellites and the sim in my frustration) The following will get you out of it.

Here's how I did it. I followed the guide entirely (and a bit extra...when it wasn't enough) but you can probably skip to this once you reach the TOOL 32 steps / or not should work either way.

I found the software for ISTA P. (It can had for free but I bought it for 15 euro's from the top result on google and it had decent download speed its a massive file so make sure you're hardwired or have fast wifi (50-60gigs) Extraction and installation takes another couple hours and there's a lengthy pdf to follow to install it correctly. (this took me 3 days of on and off work to get the computer ready)
Once you achieve that use your DCAN connector and load it up with create session (its very slow). It asked if i had replaced modules i said yes - it asked me what modules I had replaced. I chose SIM (air bag control module)
It will create a 3 step plan for you of "initialize & 2 more steps." (i'm so sorry I cant remember) I attached a battery charger and started the action plan. (wish i remembered what the button said but it was fairly intuitive.) It was again very slow but it eventually came "shut the ignition off and remove the key". This is where you will learn as I did, that it cant tell you've done this and the screen will not progress. eventually I pushed terminate and turned the key back on. This was not as scary as I thought since its finished the programming and this was part of the erase fault codes step. It may say "fault codes still present" this is fine just continue.
Eventually you'll reach the results screen and Unless you're truly unlucky, it will say it was a great success and the air bag light will not be on your dash anymore!

 

[Simonsen]

Hi all well it looks like i need to recode my B pillar module , Question is do i need 3 different programs ?:
- Inpa
- WinKFP
- tool 32
just looking at ebay to buy winkfp with cable.

 

[BumpyZ4]

You can download for free from numerous places on the web an entire software suite that includes all of those programs. I downloaded "Mike's Easy BMW Tools Package" off of Bimmerfest.com. It comes with everything you need.

 

[E60NZ]

**Cautionary Tale**

I have a 05 E60 and had the airbag problem and I followed the guide completely. Everything went well up until the ISTA-P part.
It asked if I had replaced modules, I said yes, checked the ones I changed, accepted the action plan and it started doing its thing.
Then it asked me to remove the keys and as soon as I did that, it started updating CAS module...
But by that time, it was already too late and yes you guessed it.. CAS was bricked...
No dash lights and engine wouldn't crank.

Now, if you are at the part where ISTA-P is formulating the action plan, do yourself a huge favor and uncheck/remove all modules that you haven't replaced from the action plan.

However, if you have bricked your CAS like I did, all hope is not lost. There is still a way to recover it. There are a bunch of tutorials out there on how to reset CAS via NCS expert or ISTA-P. I tried everything and nothing worked.

But this did. Alright, here is what to do:

First, we need to check if a connection can be established with the car.
Open INPA. At this stage, it will show battery off and ignition off. Do not panic my friend (well not yet!)
Turn the cabin light on and off, or open/close the car door.
You will hear a faint noise coming from the car.
Wait for 2 seconds and then read the UIF field.
If you see that CAS module has a VIN of 0000000, you can smile a little as you are probably going to be able to recover your CAS.
If it says something along the lines of "no communication could be established". Unplug your negative terminal, unplug BST, wait for a few mins, then plug everything back in and repeat the above process.
Okay, now note the ZB number in the CAS row.
Also, check the programming state, most probably, it will be 12. That just means, incomplete flash and it is good sign.
Now take the keys out of the ignition. Launch WinKFP. Comfort mode > Enter ZUSB > Type in the ZB number that you just noted.
Press ok on the pop-up screen.
Enter your VIN, click OK.
Ensure that protocol being used is BMW-FAST and Boot sector update is Activated.
Now open/close your car door again, wait for the noise, wait 2 seconds and then hit program.
It will say, ECU can be programmed 1 time, say yes/ok.
Then the update will start and within 2-3 minutes your car will be revived.

Now opening/closing car door may sound stupid but trust me it is the most important part of the process.
What it does is, it wakes the car up for around a 30 second window and we need to make the most of that window.
Also, CAS can only be updated with your keys out of the ignition. Please do NOT leave them in.

Any questions about the process, please feel free to ask. I will try to answer to the best of my ability.
And NO I cannot help with any other programming questions, sorry.

And obviously, no guarantee it will definitely work for you, just because it worked for me.
You may end up making your bad situation worse, so proceed at your own risk.

Good luck!

 

[enuff_zed]

A very comprehensive explanation thank you.
However, I’ve done a few now and ISTA-P is not required at any point in the process?

 

[E60NZ]

I was following @gornlordunoboggle's guide (one of the above comments), which has ISTA-P step to circumvent Tool32 issue.

 

[enuff_zed]

Ah ok. Well too late for you now but hopefully anyone else reading this will now know to follow the other route and save themselves the troubles you encountered.

 

[Domingo]

I need to change a defective Right Pillar Module on a Z4 E85 from 2004.
Regarding the given INPA error Messages the Main SIM85 Airbag Module is ok.

I have 3 questions:
1. I bought a used pillar module with the exact same part number as the original one (6940300). This part has been discontinued and now superceeded by partnumber 6962888. My SP Daten files do not contain the old original part number as ZUSB but I can select the successor. Unfortunately I‘m unable to get that much older SP Daten from 2004 for the older ZUSB, but I read about updating the ZUSB with WinKFP feature „ZUSB Update“ is a possible way. Can someone confirm I can reprogramm the VIN on a discontinued module with older part number with the available newer one using the WinKFP function „ZUSB Update“? Will it work to write a new VIN to a module with the old part number and using the newer ZUSB in WinKFP?

2. In the process of coding the new VIN into the pillar module I get the WinKFP window to select the right control unit family and the ZUSB number. There I have to choose „Verbauort“ (on the most right side of that dialog). I have 2 options, one is called „Unverbaut“ the next is just a dash „-“. Does anybody know the difference of these 2 and what I need to select here?

3. I read that after reprogramming the pillar module I need to restart system time (systemzeit_starten) using Tool32. Do I need to send this command to the swapped pillar module or to the main control unit (SIM85) or to both separately (if to both, in what order)?

May be someone with more experience can help with this.
Thx

 

[enuff_zed]

I need to change a defective Right Pillar Module on a Z4 E85 from 2004.
Regarding the given INPA error Messages the Main SIM85 Airbag Module is ok.

I have 3 questions:
1. I bought a used pillar module with the exact same part number as the original one (6940300). This part has been discontinued and now superceeded by partnumber 6962888. My SP Daten files do not contain the old original part number as ZUSB but I can select the successor. Unfortunately I‘m unable to get that much older SP Daten from 2004 for the older ZUSB, but I read about updating the ZUSB with WinKFP feature „ZUSB Update“ is a possible way. Can someone confirm I can reprogramm the VIN on a discontinued module with older part number with the available newer one using the WinKFP function „ZUSB Update“? Will it work to write a new VIN to a module with the old part number and using the newer ZUSB in WinKFP?

2. In the process of coding the new VIN into the pillar module I get the WinKFP window to select the right control unit family and the ZUSB number. There I have to choose „Verbauort“ (on the most right side of that dialog). I have 2 options, one is called „Unverbaut“ the next is just a dash „-“. Does anybody know the difference of these 2 and what I need to select here?

3. I read that after reprogramming the pillar module I need to restart system time (systemzeit_starten) using Tool32. Do I need to send this command to the swapped pillar module or to the main control unit (SIM85) or to both separately (if to both, in what order)?

May be someone with more experience can help with this.
Thx

Welcome to the forum.
1. Put the number of your replacement module into Realoem and use that to find the latest part number that supercedes it. That is the part number you need to code your module to.
For 2, and 3, use this link:
https://docs.google.com/document/d/1LdQXN4JM8V0-s6Xa_E9ZeMlkED_i9vpm/edit

This should take you through the process quite easily.

Setting system time using Tool32 is clearly explained in there too.

 

[Domingo]

Welcome to the forum.
1. Put the number of your replacement module into Realoem and use that to find the latest part number that supercedes it. That is the part number you need to code your module to.
For 2, and 3, use this link:
https://docs.google.com/document/d/1LdQ ... i9vpm/edit

This should take you through the process quite easily.

Setting system time using Tool32 is clearly explained in there too.

Thx for the warm welcome…
I already have the latest part number and also found that latest number in the WinKFP ECU family. So I can select it there. Just wanted to know if it’s possible and the right way to use this ZUSB Update Feature of WinKFP to recode a new VIN with the latest part number into a module with an older one. But if I understand you correctly the answer is yes .

And I also have read the great mentioned Google Drive document.
As far as I understand it, it describes swapping the main ECU only (SIM85). If only the SIM is changed it‘s clear that restarting system time should be done on that module. In my case I just change the right pillar module (SBSR85). The SIM is not being swapped. Is restarting system time then needed on the pillar module only or does this always have to be done on the main SIM ECU? Or on both (SIM and SBSR)!
The Google doc also doesn‘t say anything specific about the correct selection of „Verbauort“ (Unverbaut or the „-“ dash) when choosing the ZUSB before coding the VIN.
Do you know anything about this special part of the process?

Many thanks for your help…

 

[enuff_zed]

Welcome to the forum.
1. Put the number of your replacement module into Realoem and use that to find the latest part number that supercedes it. That is the part number you need to code your module to.
For 2, and 3, use this link:
https://docs.google.com/document/d/1LdQ ... i9vpm/edit

This should take you through the process quite easily.

Setting system time using Tool32 is clearly explained in there too.

Thx for the warm welcome…
I already have the latest part number and also found that latest number in the WinKFP ECU family. So I can select it there. Just wanted to know if it’s possible and the right way to use this ZUSB Update Feature of WinKFP to recode a new VIN with the latest part number into a module with an older one. But if I understand you correctly the answer is yes .

And I also have read the great mentioned Google Drive document.
As far as I understand it, it describes swapping the main ECU only (SIM85). If only the SIM is changed it‘s clear that restarting system time should be done on that module. In my case I just change the right pillar module (SBSR85). The SIM is not being swapped. Is restarting system time then needed on the pillar module only or does this always have to be done on the main SIM ECU? Or on both (SIM and SBSR)!
The Google doc also doesn‘t say anything specific about the correct selection of „Verbauort“ (Unverbaut or the „-“ dash) when choosing the ZUSB before coding the VIN.
Do you know anything about this special part of the process?

Many thanks for your help…

I believe you just select Unverbaut.
The document does explain that it works for SIM85, SBSL and SBSR.
The process for any one of the three is the same. You simply select the correct file when you do the system time. (sim85, sbsl85 or sbsr85)

 

[Domingo]

I believe you just select Unverbaut.
The document does explain that it works for SIM85, SBSL and SBSR.
The process for any one of the three is the same. You simply select the correct file when you do the system time. (sim85, sbsl85 or sbsr85)

Thx dude, I will give it a try. My new (used) satellite module will arrive in 2 weeks.
Appreciate your helping…

 

[Domingo]

One more question…
Another user told me it should be enough to reprogram the new VIN and after that I just need to start system time and everything should work. That would skip using NCS as mentioned in the google doc. Can I really skip the NCS part?
If NCS is needed, step 14 and 15 tells something about reading the ECU („ReadECU“ in step 14 and this „coapiReadSgGetFswPsw“ in step 15).
Does this mean, reading something out of the original (broken) module and then writing that data back to the new one? Someone explained the process as first read out and save the programming from the old ecu using NCS and then plug in the new ecu to write these saved data back in there. But the Google doc says the process „codes to default“ (although it tells something about reading stuff out of the ecu?). May be I don‘t misinterpret the button and function namings.
But unnecessary question if VIN recoding and starting system time is really enough and NCS is not needed at all…

 

[enuff_zed]

Yes you do need the NCS part. Do it all on the new module. I’m no expert and don’t 100% understand why so I’ll give you the IT Luddite version.
It seems that you take the info from the new module and it goes to your laptop. This of course is the info from when it was in the last car. Then you simply put it back in again, but on its way it introduces itself to the car and takes in the updated details of its new home.

 

[Jollygiant]

Yes you do need the NCS part. Do it all on the new module. I’m no expert and don’t 100% understand why so I’ll give you the IT Luddite version.
It seems that you take the info from the new module and it goes to your laptop. This of course is the info from when it was in the last car. Then you simply put it back in again, but on its way it introduces itself to the car and takes in the updated details of its new home.

A bit like when you start a new job and you have to Hi to people in reception on your way though to your orifice just in case you need them!