Airbag ECU programming missing IPO file

J

JL-ZiZi

New member
Hi All,

Very new to the forum but I am having some issues programming a replacement b-pillar airbag module to the car using WinkfP.

I have followed the instructions and gotten my SPN-Daten file from mac27040's very helpful thread: https://z4-forum.com/forum/viewtopic.php?f=2&t=111706

However once I have input the ZUSB number and VIN of the car or after I select the correct family for the B-pillar module I am hit with a 106 error code. It seems that Wink cannot find the correct IPO file (SBSL85.IPO) for the ECU family in the daten files in the SGDAT folder.

Just wondering if anyone has had any experience with this or know where I can find he IPO file that it is looking for? Photos attached


Any help is extmely appreciated.
 
Hi,
Insterad of using the part number of your module, look at the .his files as explained in the guide. Find your number, then look to see what the latest one is and select that in the WinKFP window.
 
happy new year Z'sters!!!!
I need help with my SBSL ecu. I started with the dash light. iNPA pointed at the sbsl. I could clear the error and the light would go away but come back right away. I purchased a used ecu, same part number 6931287. Flashed it and added the Vin with winkfp. My zusb wasn't on the list so I selected what I thought was the correct new number, 6948085. Im not sure if I interpreted the his file correctly but it looked like it went from my on to another one and then to 6948085. Long story short, now I have errors 9895 communication malfunction and 9878 rear seatbelttensioner interruption. Other airbag ecus are now throwing errors but I'm guessing it's related to the comm issue with sbsl. Any suggestions?
 
I’m not at home until tomorrow to check the numbers but 1287 doesn’t ring a bell?
Are you UK based?
If the other module codes say timeout don’t worry about them. They will clear once the SBSL is sorted.
Also bear in mind your car doesn’t have rear seats so the second code is a generic one which is more likely to suggest the module is a dud
 
Just remembered I have my inpa laptop with me and the .his files on notepad.
Found 1287.
Considering the software always works it out for itself then I can only suggest you try it with 8087?
Another option is to use SBL64, select 4366 and let it work it out for itself.
If nothing works then probably need to try another module.
 
Just noticed your pic and it’s a US-spec car so unless you want to fly me out there……… 🤣
 
Yup I the US of A, down south in Elvis' home area. I guess I can't fly you here but more than welcome if you wanna come over and visit. I'll try your suggestions
 
KathsZ said:
no luck, need to find another module
Click to expand...
Damn!
I had one other random thought................ where did you get the replacement module from?
In my previous dabbling with these I've noticed that if you look at the software using NCS Expert/Dummy, it shows options in the satellite modules for passenger or driver seat functions. There are a couple of differences: occupancy sensor and steering wheel airbag/dash airbag for example.
So, if by any chance you bought one from the UK (RHD), it may give you problems.

While I'm on that train of thought (and this is something it has never occurred to me to do before) ,I wonder if it's possible to use NCS to code out the rear seatbelt check? Not sure it'll solve your problem though as you may still have that communication error.

Definitely worth checking the plug is all clean and no damaged pins too.
 
You must log in or register to reply here.
Back
Top Bottom