'05 Acura TSX DTC 54-50

Tyler wrote: I see three connectors at the SRS module - A, B, C. I've looked at the '04, '05 and 06, and all the pins we're concerned about seem to be consistent. I DID notice that the OPDS has four connectors, and had weight sensors added in '06.

Mostly just trying to figure why it'd suddenly throw the OPDS code in there.

I read something about the opds needing to be initialized if there are certain parts being changed. I thought maybe the different module prompted that issue because that code is gone now that I initialized it.

Sent from my Moto G Play using Tapatalk

I got a little more info on this one tonight while the family was out of the house. It is responding so oddly to the tests.

- Mitchell says that the codes indicate either bad module or sensors and that after module replacement opds needs to be initialized, so I started there. No change.

- I had two other used rear sensors, so I tried both of them on one of the sides, no change.

- scope showed "wake up pulses" but nothing after that, just like the impact sensor did in one of Paul's videos. I thought for sure that i just need to bite the bullet and put new sensors in BUT...

- I unplugged one of the bad side sensors and the code changed to no signal. I unplugged a "good" side sensor and nothing changed. What the hell? I put the bad sensor in the good sensor harness and again nothing changed! Very weird. I wanted to completely swap the sensors side to side but I have to take the driver's seat out to get to that one and this test was weird enough for me to call it a night.

- next I think I want to scope a good front sensor and see what that does.

Does anyone have an explanation for any of this or have a different direction I should be going in?

It seems like the wiring is good since I'm getting a signal on the scope with key on and at least one side is responding to me unplugging the sensor. Not sure what to make of that "good" side not responding though.





Sent from my Moto G Play using Tapatalk

Anyone want to take a swing at this one with me?

Sent from my Moto G Play using Tapatalk

Man I've been swinging at this one, and I still got nothing. :lol: It's like that brake rotor that you've been taking baseball swings at with your biggest hammer, and it still won't come loose. :lol:

I unplugged one of the bad side sensors and the code changed to no signal. I unplugged a "good" side sensor and nothing changed. What the hell? I put the bad sensor in the good sensor harness and again nothing changed! Very weird.

This module still isn't working correctly. Remind me - are we still on the module that you had sent out?

Tyler wrote: Man I've been swinging at this one, and I still got nothing. :lol: It's like that brake rotor that you've been taking baseball swings at with your biggest hammer, and it still won't come loose. :lol:

I unplugged one of the bad side sensors and the code changed to no signal. I unplugged a "good" side sensor and nothing changed. What the hell? I put the bad sensor in the good sensor harness and again nothing changed! Very weird.

This module still isn't working correctly. Remind me - are we still on the module that you had sent out?

Ha, seriously! This is actually another used one I bought. I didn't send this one out, after I installed it, those same three codes popped up.

Sent from my Moto G Play using Tapatalk

Tutti57 wrote:

Tyler wrote: Man I've been swinging at this one, and I still got nothing. :lol: It's like that brake rotor that you've been taking baseball swings at with your biggest hammer, and it still won't come loose. :lol:

I unplugged one of the bad side sensors and the code changed to no signal. I unplugged a "good" side sensor and nothing changed. What the hell? I put the bad sensor in the good sensor harness and again nothing changed! Very weird.

This module still isn't working correctly. Remind me - are we still on the module that you had sent out?

Ha, seriously! This is actually another used one I bought. I didn't send this one out, after I installed it, those same three codes popped up.

Sent from my Moto G Play using Tapatalk

So where would you go next?

Sent from my Moto G Play using Tapatalk

To the bar for a stiff drink! :lol:

I think I'd be trying a different scanner, just to make sure the codes are legit. But, the shop I work for owns an Autel, so that's a quick/easy thing. Finding another scanner that'll read SRS codes may be tougher. Perhaps see if a local shop would be willing to read your codes for a small fee? Forgive me if you've done this already! :blush:

I'm dwelling on this while I'm here at home, I'll get back on later.

Tyler wrote: To the bar for a stiff drink! :lol:

I think I'd be trying a different scanner, just to make sure the codes are legit. But, the shop I work for owns an Autel, so that's a quick/easy thing. Finding another scanner that'll read SRS codes may be tougher. Perhaps see if a local shop would be willing to read your codes for a small fee? Forgive me if you've done this already! :blush:

I'm dwelling on this while I'm here at home, I'll get back on later.

Ha, I'm going to get to that after my kids get to bed! Good thought and I did try that. I bought an Autel as a backup when my lunch got flakey on me recently. Same codes...



Sent from my Moto G Play using Tapatalk

Tutti57 wrote:

sebastianshaw wrote: Try to use the -REMOVED- :whistle: Happens once in a while

What do you mean?

Sent from my Moto G Play using Tapatalk

Thanks for reporting this. I've removed the b.s. spam message. Hate stupid crap like this. sebastianshaw
Another post like this and you'll be banned from this forum.

Nevermind "sebastianshaw" nhas been banned from this website. Thanks for helping me police this guys.