2005 E85 BMW Z4 AIRBAG LIGHT
- Thread starter dabiggsy
- Start date
Ireland
Yeap that little dot next to the KM is a tamper dot. It shows that the mileage and VIN dont match between the Light switch and Cluster. You're right as well, the light switch was probably replaced at some point and not realligned.
That cluster has seen better days
Back to your issue though, if the VIN pulling from the cluster is correct thats not your headache.
I'd honestly be looking for a replacement SIM85. The corrosion on the plug isn't a good sign. I know its an expense but it seems like you're starting from a position where you have no idea what the previous person did. You can always resell if its not the issue.
That cluster has seen better days
Back to your issue though, if the VIN pulling from the cluster is correct thats not your headache.
I'd honestly be looking for a replacement SIM85. The corrosion on the plug isn't a good sign. I know its an expense but it seems like you're starting from a position where you have no idea what the previous person did. You can always resell if its not the issue.
Ah yes I see it there in the picture, would'nt have spotted that looking at the clsuter during the day. Didnt even know that was a thing. So do i need to program the lightswitch module or what step would be taken there or if its not related to the airbag wahtsoever then that can be left for another day 
yeah it may have to be a new SIM, its just the car can read it and communicate with it so that should mean it works to an extent. The fact that the airbag light can be cleared off the dash is someting too, when i first tried to clear codes a few weeks ago that airbag light would never clear, was always there.
Id love to know what the previous person did so I could have a starting point, nightmare.
Maybe im doing something wrong, im not sure.
When i flashed and reprogrammed with WINKFP and NCSEXPERT i would go to INPA and the fault code would incorrect system time, then i would do the process on Tool32 and reset system time and scan again but it the error would be incorrect chasis again.
Cars are just too confusing and over complicated. I guarantee even though the faults I have are all coming up under the 3 airbag modules, its probably got nothihgn to do with them and everything to do with something else
Even if i get a replacement module (which at the moment i cant) id just be afraid id still have this same issue but maybe im wrong. That step up converter fault seems to be intermittent, it hasnt come back since id posted about it last week.
yeah it may have to be a new SIM, its just the car can read it and communicate with it so that should mean it works to an extent. The fact that the airbag light can be cleared off the dash is someting too, when i first tried to clear codes a few weeks ago that airbag light would never clear, was always there.
Id love to know what the previous person did so I could have a starting point, nightmare.
Maybe im doing something wrong, im not sure.
When i flashed and reprogrammed with WINKFP and NCSEXPERT i would go to INPA and the fault code would incorrect system time, then i would do the process on Tool32 and reset system time and scan again but it the error would be incorrect chasis again.
Cars are just too confusing and over complicated. I guarantee even though the faults I have are all coming up under the 3 airbag modules, its probably got nothihgn to do with them and everything to do with something else
Even if i get a replacement module (which at the moment i cant) id just be afraid id still have this same issue but maybe im wrong. That step up converter fault seems to be intermittent, it hasnt come back since id posted about it last week.
Attleborough, Norfolk
As you already have the light module I would get that correctly coded first, as it may be causing the confusion. The car checks the airbag modules and says they don’t match the light module. Once that is coded with the correct vin then the tamper dot will disappear and hopefully your airbag vin issues will resolve themselves. Once that’s done you can look at the more costly option of replacing the SIM85 if needed.
I have previously used Scanner 1.4 to code the LCM but it may need Street to explain it using INPA etc
I have previously used Scanner 1.4 to code the LCM but it may need Street to explain it using INPA etc
I think i will give that a whack before changing modules , bank isnt looking to healthy at the moment
Appreciate those pointers from both of you, defintelly gives me something else to try and cross my fingers
Throwing random ideas out.. I noticed on your WinKFP screen you seem to be using something like an ICOM and not a D-Can cable??
Once you’ve done the first flash and before coding with NCS, try and read the details on the SIM85 with INPA. The VIN should look horrible with all funny characters. (First time I did it I scared the life out of myself thinking I’d killed it).
It would confirm if you are managing to flash the boot sector.
The viewable vin is only set in the user fields later in the process when you use NCSExpert.
Once you’ve done the first flash and before coding with NCS, try and read the details on the SIM85 with INPA. The VIN should look horrible with all funny characters. (First time I did it I scared the life out of myself thinking I’d killed it).
It would confirm if you are managing to flash the boot sector.
The viewable vin is only set in the user fields later in the process when you use NCSExpert.
Hope it works. The tamper dot encourages me that my theory regarding the vin may be correct.I think i will give that a whack before changing modules , bank isnt looking to healthy at the moment
Appreciate those pointers from both of you, defintelly gives me something else to try and cross my fingers
If it works then come back and talk to me about modules as I may have what you need
Yes i have a loan of an ICOM from a friend , maybe that is something have done worng? Is this process not possible with an ICOM? I imagined it was as everything was saying "coding ok" or "programming ok".
So after flashing go to INPA and where abouts will i be able to view the VIN from there? I dont think my INPA allows me to view the vin
I am tempted to go outside now in the cold as I need to return this ICOM tomorrow morning before work
I have an ICOM and I don’t think it should make a difference. I have to use the ICOM when coding F series cars.
I was just trying to pick out something different as you seem to be following the process correctly.
If it’s a boot sector issue it might also explain why the light comes back on after cycling the ignition.
I was just trying to pick out something different as you seem to be following the process correctly.
If it’s a boot sector issue it might also explain why the light comes back on after cycling the ignition.
I’m really skeptical that your Light switch is related. The KOMBI is the hub for the KBUS.
Save messing around trying to code that, you could just unplug it for now. I’ve never had an airbag light with no light switch present. (These are Z4’s though and they reserve the right to change the rules)
Save messing around trying to code that, you could just unplug it for now. I’ve never had an airbag light with no light switch present. (These are Z4’s though and they reserve the right to change the rules
)
My point was that the IKE and LCM are both on the KBus and the chances of all three airbag modules losing their vin is surely unlikely so they must be picking up the wrong one from somewhere?I’m really skeptical that your Light switch is related. The KOMBI is the hub for the KBUS.
Save messing around trying to code that, you could just unplug it for now. I’ve never had an airbag light with no light switch present. (These are Z4’s though and they reserve the right to change the rules
We know the LCM is holding the wrong vin and therefore irrespective of the airbag issue it needs sorting. So surely just do that first and see what’s left?
I would assume once it is corrected the airbag modules will need to be straightened out again but then should hopefully retain the correct vin as there is nothing on the kbus to upset them any more.
Yeah that’s fair , all the programming and flashing seemed to have no problem whatsoever.
I tried coding the ALSZ just there the same way I would do with the airbag (not sure if it’s different) but I don’t even see an ALSZ or LSZ module in Winkfp so not sure what to do there. It doesn’t come up in the list of ECUs.
Here is some images of the wrong vin on INPA for the LSZ module and the part number
That’s the error I get when I try search it by ZB number. Cannot be found. I tried even setting SP dates files as E46 and still same. Is there a different way to code these modules?
I tried coding the ALSZ just there the same way I would do with the airbag (not sure if it’s different) but I don’t even see an ALSZ or LSZ module in Winkfp so not sure what to do there. It doesn’t come up in the list of ECUs.
Here is some images of the wrong vin on INPA for the LSZ module and the part number
That’s the error I get when I try search it by ZB number. Cannot be found. I tried even setting SP dates files as E46 and still same. Is there a different way to code these modules?
Attachments
I dont see aything in the ECU family list that looks anything like the above module. even searching the ZB number it gives me that error, is there certain SP Daten files i need to have? I think ive tried V68, V70 and V71, maybe i need newer or older ?
Will have another loan of the ICOM cable this weekend touch wood, dont have it for the week so no way of checking the car unitl the weekend, have to do a lid lock cable on the A4 convertible i have too. Spent all my money on cars that dont work and cost me a fortune , i guess im no different to everyone else
of course its rare and the most expensive one Just to bring this thread back to life as this problem is still ongoing.
Been busy with work so haven’t had time to check out the problem more. Just came back in after putting the new SIM85 module in.
93DB step up converter fault is gone. So that previous module I had was probably dead.
I am getting these faults now.
SIM85 incorrect chasis number 93AB
(I am clearly not doing this whole Winkfp , NCS job properly or my files/software are outdated and not good)
SBSL 9886 again another coding related fault with the incorrect chasis fault.
SBSR resistance too low for pill (I broke the shorting tab, I know about this one)
Resistance too low thorax, knee airbag fault on driver side.
I am scratching my head.
Any help is appreciated.
Been busy with work so haven’t had time to check out the problem more. Just came back in after putting the new SIM85 module in.
93DB step up converter fault is gone. So that previous module I had was probably dead.
I am getting these faults now.
SIM85 incorrect chasis number 93AB
(I am clearly not doing this whole Winkfp , NCS job properly or my files/software are outdated and not good)
SBSL 9886 again another coding related fault with the incorrect chasis fault.
SBSR resistance too low for pill (I broke the shorting tab, I know about this one)
Resistance too low thorax, knee airbag fault on driver side.
I am scratching my head.
Any help is appreciated.
Attachments
I was just out at the car tonight. I reset my laptop and redownloaded all the BMW tools again. Flashed SBSL, SBSR and SIM module. Coded all on NCS. Went to INPA and only code i had on all 3 modules was system time ( this was the first time I had seen this ).
I set system time in SBSL, SBSR and then SIM last.
Went on to INPA again and cleared faults in all 3 modules and airbag light went off. I thought i had done it. I let the car sit with ignition off again for about 30 seconds before turning on igntion and airbag light still wouldnt go off after a few seconds.
Checked INPA and faults on all 3 modules are the Incorrect chassis number faults again...
Its like as soon as the car goes to sleep it just forgets everything.
ive checked all 3 modules on Tool32 and all have the correct VIN. Only thing i noticed was when i checked SBSR and SBSL for communication test, they are "N.I.O" so theyre not communicating. Fibre optic cable has a red dot so its working. Main module is communicating. Im not really sure what to do.
I set system time in SBSL, SBSR and then SIM last.
Went on to INPA again and cleared faults in all 3 modules and airbag light went off. I thought i had done it. I let the car sit with ignition off again for about 30 seconds before turning on igntion and airbag light still wouldnt go off after a few seconds.
Checked INPA and faults on all 3 modules are the Incorrect chassis number faults again...
Its like as soon as the car goes to sleep it just forgets everything.
ive checked all 3 modules on Tool32 and all have the correct VIN. Only thing i noticed was when i checked SBSR and SBSL for communication test, they are "N.I.O" so theyre not communicating. Fibre optic cable has a red dot so its working. Main module is communicating. Im not really sure what to do.