2004 E85 Airbag Module Replaced/Programmed new codes

Etonic

Member
First time posting, but this car is driving me nuts.

The main airbag modulle SIM85 got wet and was replaced. The new module had the same part # as the original and showed a VIN Mismatch.
Using all the guides I reprogrammed the new module - OE# was 6939810 and the corresponding ZUSB was 6962766 in WinKFP. The module was programmed and VIN updated and the time was restarted - shows no codes.

I still had the airbag light on and now I get fault codes for the L and R Satellite sensors (9897 and 9917). Since I didn't have these with the original program 6939810, do I need to update the satellites? Or do I have bigger issues?

I pulled the left sensor and it did not look like it had gotten wet and pins were pristine.

Any help would be appreciated!
 
9897 I’ve not seen before and shows as:

EAM parameter inconsistent

9917 is the generic ‘control unit fault’
 
I’m assuming those codes won’t reset?
You do get a lot of codes when you’re changing the SIM85 which have to be cleared but these are usually for timeouts.
The chances that both satellites failed is fairly low.
It could be that the replacement SIM85 has an issue. The other two feed back through that.
It could also be that they already had faults but you couldn’t see those as again, the obd reader looks at them via the SIM85.
 
I can reset the satellite codes, but they come right back.

The SIM85 shows no codes, correct VIN and updated ZUSB number. The only codes in the airbag system are in the L and R B-pillar Satelite sensors (both of those show the correct VIN and I can see their info). The odd part is before I coded the replacment main module, all I had was a VIN mis-match code in the main module.

Orginal ZUSB was 6939810 and the corresponding ZUSB was 6962766 in WinKFP.

The original main module got wet and had some white corrosion on the connector, but it was not crazy bad. My next step would be to check the pins on the main module connector...but I don't think its the issue.

I am using the BMW Tools, a Launch scanner, and a Thinkcar scanner. All show basically the same info.

This really has me scratching my head.
 
Etonic said:
I can reset the satellite codes, but they come right back.

The SIM85 shows no codes, correct VIN and updated ZUSB number. The only codes in the airbag system are in the L and R B-pillar Satelite sensors (both of those show the correct VIN and I can see their info). The odd part is before I coded the replacment main module, all I had was a VIN mis-match code in the main module.

Orginal ZUSB was 6939810 and the corresponding ZUSB was 6962766 in WinKFP.

The original main module got wet and had some white corrosion on the connector, but it was not crazy bad. My next step would be to check the pins on the main module connector...but I don't think its the issue.

I am using the BMW Tools, a Launch scanner, and a Thinkcar scanner. All show basically the same info.

This really has me scratching my head.
OK, so what I was trying to say was, the satellite modules feed back through the SIM85. Until that is correctly set up in the car it may well be that the satellites are not seeing it properly and therefore cannot transmit any info back to it.

So, if the original SIM85 was faulty, then it may not have been passing on any issues from the satellites that already existed.
If the new module has a fault somewhere then that may cause the same problem.

Have you checked and thoroughly cleaned the electrical connector to the SIM85? The pins in the plug are hollow and incredibly small. Any corrosion inside them is almost invisible and extremely difficult to remove.
 
OK, the connector has continuity in all pins (measured at pin to wire).

I'm attaching pics of the scan tool data.
 

Attachments

  • IMG_20250403_145550159_HDR.jpg
    IMG_20250403_145550159_HDR.jpg
    147.4 KB · Views: 667
  • IMG_20250403_145603354_HDR.jpg
    IMG_20250403_145603354_HDR.jpg
    205.7 KB · Views: 667
  • IMG_20250403_145624191_HDR.jpg
    IMG_20250403_145624191_HDR.jpg
    175.2 KB · Views: 667
  • IMG_20250403_145647442.jpg
    IMG_20250403_145647442.jpg
    138.3 KB · Views: 667
  • IMG_20250403_145752929_HDR.jpg
    IMG_20250403_145752929_HDR.jpg
    221.8 KB · Views: 667
  • IMG_20250403_145849536_HDR.jpg
    IMG_20250403_145849536_HDR.jpg
    191.6 KB · Views: 667
  • IMG_20250403_150003379_HDR.jpg
    IMG_20250403_150003379_HDR.jpg
    119.1 KB · Views: 667
  • IMG_20250403_150039965_HDR.jpg
    IMG_20250403_150039965_HDR.jpg
    179.6 KB · Views: 667
  • IMG_20250403_150249146_HDR.jpg
    IMG_20250403_150249146_HDR.jpg
    95.8 KB · Views: 667
I can see you have SBSL/R hardware numbers ending in 299 and 300

Did you get the central module that matches the set? 6962766

Stuart
 
The original SIM85 module was part# 6939810. I purchased the same part# and programmed the corresponding ZUSB which was 6962766 in WinKFP. 6962766 is the updated version 6939810 according to BMW.

Before coding to 6962766 I only had the VIN mismatch error in the main module.
 
Do you still have the original SIM85? Try slaving that back in and see what happens with the SBSL and SBSR. It will show whether it’s the new SIM85 causing the problem.
You should be able to pull the connectors through with the coin holder removed rather than take the console apart again
 
The original main module (SIM85) got wet and is DOA.

From Real OEM
65776939810
Safety information module
From:04/01/2004To:08/25/2005 (ENDED)Weight:373.910 kgPrice:$370.13
Supersedes:
65776938263(10/01/2003 — 06/07/2011), Exchangeable retrospectively65776927552(09/01/2003 — 09/12/2003), nonexchangeable retrospectively65776965146(12/07/2004 — ), Exchangeable retrospectively65776935919(03/25/2003 — 02/15/2005), Exchangeable retrospectively65776928953(09/02/2002 — 03/08/2005), Exchangeable retrospectively65776928519(09/02/2002 — 07/01/2002), Exchangeable retrospectively65776924885(09/02/2002 — 05/22/2002), Exchangeable retrospectively65776926781(09/02/2002 — 04/23/2002), Exchangeable retrospectively65776924603(09/02/2002 — 03/18/2002)

Should I try to re-program to 65776965146?
 
Etonic said:
UPDATE: Reprogrammed both B-pillar modules to the updated ZUSB and its now happy. Thanks for all responses.
Well that’s a first! Never had to do that before.
Glad you’re sorted
 
Back
Top Bottom