I'd like some actual tips/advice from someone who really knows the airbag system(s) and faults in Minis.

2013 R56 S Coupe, ~109K on the clock.

My airbag icon keeps coming back. I clear it (Foxwell Elite) but the OG problem remains. As the pics below show, the airbag icon shows in the central info center screen along with the seatbelt icon (both red); the airbag icon shows in the tach on the steering column; pass airbag off warning in upper console at startup; the Mini's warning explanation mentions a fault in the passenger-restraint system... (see pic). I would also note that although the airbag icon in the tach looks red in the pic, it shows as orange when the engine is running.

I search out the codes on my Foxwell and get a fault for the ACSM-MRS (crash module). Note: the car hasn't been in any accidents that might blow the airbag(s).

The particular code I'm getting is 9418 - "ACSM/MRS: Belt-force limiter, front passenger"; also states "not present". This tells me that the ACSM is not getting a signal from the belt-force tensioner (which I've found is part of the actual seatbelt spool in the door frame).

So: would y'all agree that the problem is not likely the ACSM, but the seatbelt itself? Is it possible (likely?) that the signal wire - from or at the seatbelt spool - has been damaged? Previous owner had some subwoofer wiring running under the door frame and past where the seatbelt spool would be.

Further, if it is just the seatbelt spool/limiter, is that a basic plug-n-play R&R?

TIA,

 

Do you have the factory service manual or equivalent for your Mini?

 

Nope.

 

Here are some relevant sections of the manual that may help you pinpoint the problem.

 

You may also find this AI-generated information helpful.

 

I’ve read recently that if the seat is removed/reinstalled and the car started without correctly connecting the wiring back to the bottom of the seat, it can trigger the airbag light. Cheap fix if all it was is the connection. It may be worth your time to take a look to confirm.

 

The seat is probably coming out either way, so unplug and re-plug are on the menu.

Maybe, I responded to your post(s) but it doesn't appear here. I was thanking you for the info and the pics helped me understand that the limiter is in the seatbelt spool, and the tensioner is in the hip receptacle - two different things in two different places. As my error code explanation definitely says "limiter", I'll be opening up the interior panel(s) and see if something's unplugged or needs replacing. If, after that, the ACMS/MRS module still isn't getting a signal from the limiter, it's module replacement time.

 

 

Maybe, I'm wondering how much you know about these restraint systems, as you seemed knowledgeable so far. With that caveat...

Do you know why the ACSM system has a delay before pushing the warning icon(s)? In other words, when I reset my airbag light it takes some time for the light to come back on under normal driving with no passenger. So why the delay? Is it time? Miles driven? Number of startups? Miles and [higher] speeds?

Some context...
When I bought the Mini, it had no warning lights, and none came up for six months or so. I took it to the local Mini dealership for an affordable oil change - everything went fine. But after a few days, maybe a week, the airbag icon came on. I called Mini back to see if they'd done anything with the OBDII system other than resetting the oil change mileage - like, did they plug into the into the OBDII port for anything? They said no, they didn't plug it in, just reset via the steering wheel stalk; but they allowed me to bring it back in for a look at no charge (since I had recently been there). They had it for a few days (and because it was a free diagnosis, they weren't making much of an effort) but their search - what they told me - was aiming at the ACSM module itself (under the E-brake). They were supposedly tearing into the center console when I told them I wanted the car back - I wasn't interested in them replacing the ACSM if that was the actual problem.

I then purchased a Foxwell Elite, BMW codes on it, etc. The fault code I got (as you see above) was about the ACSM not getting a signal from the belt limiter. No idea if the Mini dealership tech discovered this or not. They gave the car back to me without the code(s) cleared, just as I brought it in.

I mention all of this because after clearing the code for the first time, it seemed like more than a week of driving before the code/icon came back, and every time I reset it, it now comes back within ten minutes or so of driving (to work in the morning, on the highway). What is the ECM or ACSM searching for until it decides to throw the airbag icon and code? Why is there a delay? In other words, why wouldn't the code re-post immediately, all things being the same as before I cleared the code? Is the ACSM trying and trying and trying to get a signal from the spool/limiter, but then gives up and send out the warning icon?

I just unbolted the pass seat and tipped it back to see that all wiring and plugs look fine (I did not unplug anything, including the battery). I also dug into the B-pillar to see if there was any wiring issue coming from the seatbelt spool - no, it's still got its plug on the top of it (blue and white wires, as I recall). I pressed on and wiggled all wire connections and then reset the ACSM with my Foxwell. The warning didn't trigger on my first drive, but I'm not optimistic. Maybe by the time you read this it will have come back on. Or if I'm real lucky, the entire problem is just a loose plug and I just solved it.

Anyway, if you have any ideas you could shoot my way I would further appreciate it.

Thanks!

 

Regarding my knowledge of the Mini restraint system, I only know as much as what is found in the factory service manual, which refers to the system as the multiple restraint system (MRS) rather than the ACSM.

I interpret the varying delays in triggering the dash airbag light to indicate that the issue is intermittent rather than constant. Ignore what I have written below if after you reseated the automatic reel connector, the airbag warning light no longer turns on.

On the other hand, if after reseating the automatic reel connector, the airbag warning light eventually returned, next try unplugging the automatic reel connector for the passenger seat belt to see if the dash airbag light triggers immediately whenever you insert the key or start the engine. If so, you might consider replacing the automatic reel for the passenger seat belt.

 

And after posting that long diatribe of questions, I did go out and take her for a test run - after wiggling, but not disconnecting - the connectors. I would have, but was not able to "unplug"? that reel wire connector - I didn't want to force it off and maybe break it, not knowing what kind of connector it is. However...

After my test run, with the seat still unbolted but still connected (underseat cable) I am happy to say that the code did not come back - yet. I drove for about an hour, away and R/T, and no codes or icons. So maybe the cause was simply a connector not making 100% contact. I bolted the seat back down, but didn't reassemble the B-pillar in case the "fix" doesn't hold. I'll take her out again tomorrow and if I still get no codes, I'll consider the matter solved and put everything back in its place(s).

Thanks so much for your input on this issue!
GA

 

Good luck!!!!

 

When I purchased my '09 project car the airbag light was on. I hate troubleshooting airbag systems!!! Here's what I learned during the process. When I scanned the system, there was a code "internal failure" associated with the airbag module. What I also leaned is that if you purchase a used one on eBay with the same part number, it's a plug and play process (no programming required.) I replaced the module and the light's been off ever since (2 years plus now). Later, I found a very nice set of sport seats in a salvage yard. I got the seats for cheap, so I swapped them out. Immediately, the airbag light was on. So, I scanned the system again, and there were two codes for the seat belt tensioners. It turns out the seat belt tensioners are coded to the car; if you replace a tensioner, it must be coded for it to work properly. So, I swapped out the tensioners from the old seats an installed them on the new seats, cleared the codes, and all is well. So if you have a failure of the airbag module (well in my case), the module will give your the "internal failure.) fault.

Last week I had a 2000 Toyota Tundra in the shop with airbag light on. I downloaded the DTCs and talked to the owner. He recently had the seat out for upholstery repair, but he didn't disconnect the battery when he pulled the seat. Always disconnect the battery! I consulted the All Data pinpoint tests, and was amazed that it actually worked. The Toyota instructions directed the tech to disconnect the connector under the seat that goes to the tensioner (2 wire harness). I pulled the seat, and checked the tensioner to see if I had a change of state with the seal belt connected and with it disconnected (I did), Next the tech data says to connect a jumper wire between the two pins on the vehicle side harness, and then connect the negative side to ground for a certain amount of time. Lastly, reconnect the connector, and clear the codes. Amazingly, it worked. I even called the owner back after a couple of days to make sure his airbag light was still off.

 

Thanks for this info. This is the first I've heard of a replacement ACSM *not* needing to be re-coded. Nor have I heard that the seatbelt buckle/receiver (the "tensioner") needs to be coded when replaced. Still, I really don't think either of those are my problem. If my ACSM is actually "bad", what code/error message would come up? The generic ACSM fault does come up in a module scan, then further shows the fault is that it's not getting the limiter signal.

My code specifically says the ACSM is not getting a signal from the passenger "belt-force limiter" (not present, as shown in pic above). That could be a single internal issue with the ACSM (unlikely, but possible), a disconnected/broken wire or plug from the seatbelt spool (limiter), or the seatbelt spool (limiter) itself, I don't know.

What I also don't know is if the seat mat/sensor is working properly or not; would it throw a code if not, or would it just constantly assume an adult person was sitting there? When working properly, if no one's sitting there, does the ACSM system even check the passenger SRS system components? If the seat sensor is bad/broken/defective - reading positive when no one's sitting there, or if it's not defective and a person *is* sitting there - is this the only time the ACSM would check for the belt-force limiter in the shoulder harness spool? Or does the ACSM need a signal from the spool/limiter *all* of the time, regardless of anyone in the passenger seat or not?

So if I replace the seatbelt spool (limiter) and the ACSM was/is the problem, wasted repair and money. If I think the seat weight sensor/mat is bad, I could use one of those $60 bypass plugs from eBay, but the limiter/spool may still be a problem if the ACSM still isn't getting a signal from it. I just find it very unlikely that the belt-force limiter in the shoulder harness spool has "gone bad" when there's no history of an accident that might've triggered it. Following those two spool wires (blue and white) is virtually impossible, as they come down the door jamb and join into the main harness that goes forward to the passenger footwell.

As it sits right now, I have the seat bolted back down properly and fully plugged in; all plugs and wires under the seat look OEM and good. I have the bottom of the shoulder harness (anchor) unbolted, and the inner panel partly off so I can get my hand in there to wiggle what I believe is the plug/wires at the top of the spool assembly - but I can't get the plug off at this angle, and I don't want to break it since I can't tell how it connects.

I can still clear the ACSM fault and it will stay clear for fifteen minutes or so, then the airbag icon comes on again and we start all over - no matter what the situation is in the passenger seat. I've had the seat belt buckled and unbuckled, stuff on the seat, nothing on the seat, yanked hard on the shoulder harness (so it locks) to maybe jar something loose, had the seat unbolted (but not unplugged) and laid back, thinking gravity may have an effect on the sensor/mat (this actually worked for over an hour's drive but the fault came back the next time I drove it).

I'm .

 

For anyone still following along, or anyone in the future digging for answers on this topic, here's an update:
I'm back where I started.

Though I have alleviated most potential causes, the airbag icon/code still kicks on after the same (approximately) amount of driving time after the code has been cleared. The code, shown above, states the belt-force limiter is the issue; my Foxwell NT510 Elite is showing confusing information. "Not Present" in that column. But... during my deep-dive into other assorted parts and voltage configurations, a second code (for the tensioner/seatbelt latch) came up, and both codes showed as "Present". So I don't know how to decipher what the Foxwell is telling me: either the error code is present or it's not, or the signal from the part is present or it's not. That second code cleared and stayed away after re-connecting the shoulder harness spool (limiter) plug, btw.

Process:
I have now removed and re-installed the passenger shoulder harness spool (where the belt-force limiter resides). No change.
I have re-coded the existing ACSM with the Foxwell. No change.
I discovered that some previous owner had installed a *****-Brand battery, so that was replaced and an Interstate battery was installed and registered. No change.
I have tested and re-coded the passenger seat pressure-sensing mat. No change.
I have turned ON the passenger airbag deactivation switch, so the ACSM should bypass that part of the SRS. No change. (Again, the Foxwell is confusing as to whether turning this switch ON means that DEACTIVATION is occurring, and not the other way around.) My Mini didn't come with the option to turn this off at the dashboard end with the key.

I'm down to two options at this point: replace the ACSM, and re-code it necessary. And hope.
Or just blow it all off and get an eBay bypass kit. If I believe the ACSM is the problem, then this should be a solid workaround. However, I'm not okay with workarounds for safety issues so this would be my last option. But if that damn shoulder harness belt-force limiter is really the problem after all, that problem may still arise after the bypass is installed.

I'll post again when this has been fixed.

 

Just for clarification...Over time, your Foxwell NT510 scan tool has detected active fault codes for both the front passenger seat belt limiter and the front passenger seat belt tensioner. Currently, the scan tool is only detecting an active fault code for the tensioner. Is this correct?

 

No, the belt-force limiter (in the shoulder harness spool) has been the culprit all along. The only time the tensioner (the seatbelt receptacle) code came up was when the limiter was unplugged (by mistake - it fell off it's perch and tugged the plug loose, unbeknownst to me when I pulled the codes that time), and it was only then that the Foxwell showed both codes, and both showed "present" in that 2nd column (as opposed to "not present" for the previous code readings for the limiter). Once I plugged the limiter back in and hung it back up, I cleared all codes (again) and the tensioner code has not come back - and the limiter code again shows "not present".

I just returned from a couple of errands. The cleared limiter code came back after around ten minutes of driving, as I expected (this is now the normal behavior for the code). While I continued driving, I again cleared the code and expected it to return in another ten minutes or so - it didn't. I went around 14 more minutes, shut the car off (at Costco), came back out, started it and went over to the gas station; shut it off, started it again. Went to the grocery store, shut it off, started it again to come home. Got all the way home - still no code. The amount of time after clearing the code at the beginning of my errands totaled around 25 minutes (ran my stopwatch during all engine-on time). So, there's no consistent time or conditions that trigger the code, just the kinda usual ten minutes - but not always.

With all of this screwy behavior from the ACSM, I'm coming around to the likelihood that it's "bad" (whatever that means for an ACSM). I still haven't eyeballed the ACSM itself; it's possible that this is just a loose plug into the module, though I seriously doubt that. It's a PITA to get the console up and out, so I've been avoiding that, but I think the time has come...

 

My 2 cents --> Based on your collective posts and this recent clarification, I still lean toward an intermittent internal problem with the passenger seat belt limiter.

 

Update: replaced the belt-force limiter (along with the entire shoulder seatbelt spool) - no change. The ACSM is next...

 

Dang!

 

Update, but not a positive one. No matter what steps I take, the code/icons return after around ten minutes of driving. The Foxwell still shows "present" or "not present" (randomly) regarding the belt-force limiter code when the code/icon comes up (see pic at top of thread). Often, it lets me clear the code immediately, sometimes it returns immediately again on start-up, sometimes it doesn't return for ten minutes or so; sometimes the Foxwell says the code is cleared, but the icons remain on the dash. After some time driving back home (icons still on dash), I can again clear the codes with the Foxwell and the icons disappear. This pattern repeats every time I take her out for a drive after changing one particular (possible) repair/fix factor.

All of this leads me to believe that the problem is an intermittent short to/from the limiter: sometimes the ACSM sees the belt-force limiter, sometimes it doesn't; I suppose the code gets thrown if/when the ACSM doesn't see the limiter (after some pre-designated period of time) but then the Foxwell might see it as "present" by the time I read the code. Again, completely random.

This is where I am.
I dug out the ACSM from under the center console and E-brake. There's a little bit of shmutz on the top of it, but it's not at all dirty or corroded. I unplugged the two harnesses; both looked very good and the plug holes in the module look clean and brand new. If the ACSM is "bad", then it's a broken solder joint inside it. Possible, I suppose.

I have finally ordered/bought a replacement ACSM - same part number, it looks brand new in the seller's pics. If I plug this new module in and the code remains, then I'll know for sure that there's a wiring short between the ACSM and the limiter. And at that point I'll hand it off to a Mini electrician to suss it out. Yes, it will be costly, but at least no parts will be needed. I can chase wire short issues myself, but I've run out of patience with this. Besides, the only pin-outs for the ACSM I could find don't show a wire for the limiter itself (yes, it has a pin-out for the tensioner/receptacle), so the limiter wire routing may be tied to some other harness or sensor - a Mini specialist will know how to read that schematic.

Fingers crossed for the new ACSM being the fix, but I'm not optimistic. Onward...

 

Good luck!

 

For anyone keeping score, the Mini is winning - and I'm still losing.

Replacing the ACSM was no improvement. Proper replacement part/module, same part number, coded to the VIN, etc. I did actually drive it for over an hour with no code/icon popping up, but next morning, fifteen minutes into some driving errands, the code/icons returned (broke my heart.) So whatever the problem is, it isn't the belt-force limiter or the ACSM/MRS. Further, I don't know why the problem seems intermittent - nothing happened to it to create a "loose wire" or bad connection situation, and there's no consistency with the code related to rough roads or driving. It's gotta be something else.

Of note: I can not turn ON the passenger airbag switch. The Foxwell is confusing as to what turns it on or off, but no matter: if I'm driving with no passenger, but with the passenger seatbelt snapped in, the overhead "Passenger Airbag Off" warning light stays lit.

Also of note: it seems the belt-force limiter doesn't have a direct wire to the ACSM. So what is driving this fault code? I searched the ACSM pin-out schematic, but there seems to be a pin only for the tensioner (seatbelt receptacle). So maybe the limiter is part of the tensioner signal wiring...? Remember, as stated above, when the limiter became unplugged, I got two codes: one each for the limiter and for the tensioner (though the tensioner wasn't unplugged). And if the tensioner was "bad", wouldn't I get a code for the tensioner? This is why people start doing drugs.

I have one more trick up my sleeve before bowing down to the eBay gods for the passenger seat occupancy mat emulator (around $60), but I would be very surprised if that was the solution. If that doesn't correct the problem, I'm gonna have to eat ~$1,000 to take it to the Mini $tealer$hip: HUNDREDS of DOLLARS per hour. HUNDREDS...

But I will figure this out, and when I do I'll post the solution here for posterity.

Weekend update: my "one more trick" didn't pan out (a possible short in the "Passenger Airbag Off" light in the overhead console); all wires were okay. The light, however, still stays on if the passenger seatbelt is fastened (with no passenger). Not sure what's supposed to happen in this circumstance. Anyway, I just ordered a passenger seat mat emulator and I'll have to try it out next weekend.

 

November 22, 2025 update.
Bought, received and installed the seat mat bypass kit from an eBay seller. Not that I was thinking this would solve anything, but I had nothing to lose at this point, just another $55, right?

It didn't change a thing.

 

Dagnabbit!

I just did an AI search for code 9418 . Maybe you've already done the same. Is any of what you read below worth pursuing?

------------------------------
To fix the ASCM (Advanced Crash Safety Module) fault code 9418 on a 2013 R56 Mini Cooper, you should primarily inspect the side impact sensor wiring and connectors for corrosion or loose pins, and then clear the code using a diagnostic scan tool. This code typically indicates an issue with a side impact sensor or its wiring, likely due to a poor connection.

Step-by-Step Fix
Locate and Inspect Connectors: The side impact sensor connectors are often located near the doors or under the seats. Inspect these yellow connector blocks for any signs of corrosion, loose pins, or water ingress.

Clean Connectors: Disconnect the suspect connectors and use an electrical contact cleaner to clean the contacts thoroughly. Ensure they are dry before reconnecting them.

Reconnect: Plug the connectors back in securely. Wiggling the wires slightly after reconnection can sometimes help confirm a good connection.

Clear the Fault Code: Use a diagnostic scanner capable of reading and clearing SRS/airbag codes to erase the stored fault from the system memory. Inexpensive OBD airbag scan tools are available, or a professional mechanic can perform this for you.

Verify the Fix: After clearing the code, turn the ignition off for a few seconds, then back on. The airbag warning light should turn off and remain off. If it persists, re-scan for codes to ensure no other faults are present and that the root cause was fully addressed.
------------------------------

The front passenger side impact sensor on a 2013 Mini Cooper (R56) is located inside the door panel of the front passenger door. There is also a second set of side impact sensors located in the B-pillar on the passenger side.

Location Details:
Front Door Sensor: This sensor is positioned within the passenger front door cavity. To access it, you will likely need to remove the interior door panel.
B-Pillar Sensor: Another sensor is located in the B-pillar (the vertical pillar between the front and rear doors) on the passenger side.