thread closure/
@enuff_zed came to the rescue with a compatible replacement SBSL - 6933985. The swap with the old module was easy - disconnected the battery, removed the two bits of plastic trim, slid the seat all the way forward and pulled the carpet back to access the modules' three bolts.
I already had Standard Tools (BimmerGeeks) with INPA v5.0.6 and ISTA+ v4.32.15 installed. To programme the module with a new VIN and system time, I followed
this guide co-edited by
@TomR, from
this thread, with these
E85 SP-Daten files. I say followed, I got stuck at the first hurdle - updating the VIN using the module's ZUSB in WinKFP. A huge and very special thanks goes to
@Street for helping me out with the procedure and confirming some points. For anyone else stumbling across this thread in the future, here is what I learned:
- The ZUSB number is the same as the part number written on the SBSL module itself (i.e. 6933985).
- My version of WinKFP used the term 'ECU' as opposed to 'ZUSB' on the buttons. This is fine, the
F1 - F8 buttons issue the same commands.
- In
Comfort mode,
F4 - Enter VIN did not show up for me, I had to activate this under
Configuration and check
UIF write in comfort mode.
- As per the aforementioned guide, WinKFP couldn't identify my ZUSB (ECU) family by my ZUSB number so I followed the alternative method within the guide. I opened the SBSL85.HIS file in C:\EC-APPS\NFS\DATA\SBSL85. This listed my ZUSB number in both the ZB-NEU and ZB-ALT columns. Hence, I followed the guide's instructions:
A4. Select 'Update ZUSB' (in my case this said 'Update ECU')
A5. Select the correct family for your module
A6. Enter your full VIN and then click done
A7. Double check that the module your going to flash it's safe to flash with your cable and the battery needs to be connect to another power source
A8. Click on Prog. ZB-Update
At this point I kept receiving an "Error 209 UIF can not be read" with many COAPI error entries stating "ECU does not answer [...] No response from controlunit".
After many hours of battling and not wishing to stray too far in fear of bricking my newly acquired module, I reached out to
@Street who advised that I should instead select
F2 - Choose Custom File and then select any ZUSB number within the list. I selected 6948087 as this was listed within the ZB-NEU column next to my part number (i.e. 6933985,6948087,00,HL).
(I am still not sure whether it matters which ZUSB number is selected as long as it's within the HIS file alongside your actual part number. If someone could confirm, that would be great?)
This worked and the module was flashed with my VIN (and presumably with this different ZUSB?).
- Finally, it's possible to start the system time within ISTA+ and not have to use Tool32. I can't quite remember the procedure off-hand but it was only a couple mouse clicks.
That is me done. Thank you once again to ALL that have helped me diagnose and clear the airbag light. I'm always reluctant to replace sensors and write them off as faulty. More often than not, they actually flag a fault further down the line (e.g. in this case, with the pre-tensioner). However, in this case, it really was the sensor at fault as per all forum advice.
/thread closure
Attleborough, Norfolk
. I've created a 
.
