Ok so now that I've determined the yellow connector is fine and nothing is wrong with the wiring or connection to the airbag, is my next likely culprit the SRS module?
can these become bricked with hard codes just from someone forgetting to disconnect the battery before unplugging the airbag? since its showing the F0 control unit fault also, that is my conclusion, but more insight is always appreciated.

Give me some history on your problem. What tool did you scan it with? PA Soft 1.4, Foxwell or ???. Screenshots would be helpful. I have never had any SRS issues so I am not experienced but I'm sure we collectively figure this out.

If you have a way to reset (sounds like yes) the standard procedure to check if the problem Is in the part is to swap with a common part eg passenger and driver airbag. I think that they are mirror not identical but the plug should be the same. If the problem swaps sides it’s the bag if not it’s wiring or the module


Sent from my iPhone using Tapatalk Pro

Ok, this all started after I got my exterior door handle on the drivers door fixed by a "mechanic"

Airbag light was not on before he did this.

Went to pick it up after he fixed it, drove off, then about 5 minutes on my way home looked down and saw the airbag light was on. Called him back and told him that my airbag light was on now. He told me to come back in the next day, and he will try to see whats up. Went back in, he plugs it into his laptop and runs what looked to me like the PA Soft BMW scanner software. Used the same looking scanner I purchased just recently. Looked up the errors, and I'm not 100% certain on this, but i'm like 99.9999999999% pretty sure I remember seeing the same code faults that I am getting now. Didn't offer me any help after that, told me he didn't know what the problem was, and that I should probably just take it to the BMW dealer in Spokane. Felt like i was just being told to get lost, because I was basically getting this work done for free as part of my buying the car, they agreed to fix the door handle at no cost to me. And now the airbag issue popped up after he fixed my door handle issue, and I felt like he woouldn't own up to his mistake of not disconnecting the battery before unplugging the side airbag.

So about a month later after he left me in the dust, I venture to Spokane, because I found a recall on my steering wheel, something involving the airbag, and so i scheduled an appt to get the recall done. YAY, here's my opportunity to get this resolved, or so i thought. BMW Dealer should MOST CERTAINLY be able to fix my problem RIGHT???! Get there, they run the diagnostic, and tell me that its the seat occupancy sensor that's causing my airbag light...and they want a ridiculous amount of money to fix it. So i gave up. Until now, since i can scan for the codes myself, and have found that there is NO code for the passenger seat occupancy mat. So I'm basically just really confused, don't trust anybody but myself to fix this, but also don't know enough to pin down what my issue is.

I'm currently using the PA Soft BMW Scanner 1.4, and i just acquired a AC808 SRS reset tool, that shows me the same codes as BMW scanner software, but will not reset the airbag light. Again, BMW scanner shows the fault as YELLOW, not red. When I attempt to clear the codes in the BMW Scanner software, the progress bar flashes yellow a bunch of times, but then the codes come right back. Same with the AC808 tool. Attempting to clear the codes doesn't do anything, SRS light on dash doesn't blink like its even trying to clear them, and the scanner just does nothing and takes me back to the FA menu to scan for the codes again. Have tried all day yesterday, and this morning, all sorts of different ways, with no success.

Ok, take a moment and go back out with PA Soft 1.4 and get some actual screenshots. Open up the software and go to the SRS module and scan it first and then get some exact codes. Then go to the live data button and grab that screenshot and then go to coding data and grab that screenshot and post them up and let's see what is exactly going on.

SRS Module Scan

https://farm1.staticflickr.com/354/1...89a190c3_o.jpg

Live Data

http://i.imgur.com/OjuUj.jpg

Coding Data

http://i.imgur.com/2EZYN.jpg

Here's what I'm getting. I just now noted that my passenger seat occupancy sensor says it was occupied, but when i did the live data scan, the seat wasn't occupied.

Couple of things.
1. The internal control module fault is troubling
2. Passenger seat is status is showing as occupied

For a quick test, deselect the IC4 Side airbag front left door and send (write) that configuration and rescan. Also, check those seat belt errors and make sure they go away or show plugged in when connected.

I did as you suggested, now its showing me 2 side airbag errors, and can't clear them either now, even after switching it back on, and rewriting and rescanning! This definitely makes me think its the module in the center console now.

Also, for the passenger occupancy sensor. I think there maybe something up with it too. While live data scanning, the sensor showed occupied. I went and pushed on the seat cushion briefly, and it went from occupied to not occupied. I then sat in the seat, and it recognized me, i got out, and it went to not occupied. Maybe it is on the fritz as well.

Check to make sure the write function worked by restarting the program and pulling the config. It does seem like it may be the central control unit but no explanation why it failed after having work done on the left front door. You can also turn off the seat occupancy sensor from the menu as well.

I did make sure it writing correctly, restarted it and it showed up as changed.

I've seen a lot of posts from different forums on this issue, and some say that these codes can get stuck in the control unit after an airbag is unplugged while the battery is connected. I don't know enough about these control units, so i can't say for certain mine is necessarily bad, just stuck with some codes that have errored the control unit and not allow it to be cleared. Can anyone with experience with this issue chime in? Is sending it to get reset a good next step?