'05 Acura TSX DTC 54-50

Tutti57 wrote: Thanks for looking into that. The front or rear door sills? My codes did indicate 1st and 2nd, so we will have to see what that means.

Front sills, I believe. I hate the way Honda designated these sensors. :silly:

I had some time before work today so I fished out the passenger side sensor which was under the sill, as directed. I couldn't get the car in the garage to get the scope on it so I'll try that on the other side. I hooked up my scan tool to see if any of the codes went away and I was having trouble with the tool and now it won't power up, so I'm sending it out to Launch to fix. Of course just a few months outside of warranty, so this is going to cost me.

So mad that my tool crapped out right now. I need to get another back up.

Sent from my Moto G Play using Tapatalk

Welp, I replaced the right side impact sensor and the code is still there. I'm going to contact the company who cleared the module to see if that gets me any where.




Sent from my Moto G Play using Tapatalk

Crap. Now I'm really starting to wonder if this module is set up for the wrong vehicle. Let us know what the module company says?

Also, really sucks to hear about your Launch. I've had to send the Modis off a couple times, so I know what it's like to be without your scanner. :silly:

Tyler wrote: Crap. Now I'm really starting to wonder if this module is set up for the wrong vehicle. Let us know what the module company says?

Also, really sucks to hear about your Launch. I've had to send the Modis off a couple times, so I know what it's like to be without your scanner. :silly:

Yeah, that's what I'm thinking too. It would explain the odd behavior.

They said those aren't hard codes and I should be able to delete them, but I can't. They also asked if I replaced the sensor and I said i did. Their final question was the module part number. I sent them what it should be but have to take the dash partially back apart to get the number off what is on there now.

Sent from my Moto G Play using Tapatalk

Tyler wrote: Crap. Now I'm really starting to wonder if this module is set up for the wrong vehicle. Let us know what the module company says?

Also, really sucks to hear about your Launch. I've had to send the Modis off a couple times, so I know what it's like to be without your scanner. :silly:

A side not about my scanner - it was very weird and the second time this has happened. It sort of froze up and when I tried to power down, the screen went black and appeared to be off but now I seems like it never was. I can volume down and it vibrates like it went to vibrate mode but the screen is still black. The first time this happened I shipped it out and they said they charged it and it was fine. Obviously I tried this with different chargers and everything. This time, I didn't send it out right away and after a couple of days I tried powering it up for the hell of it, I got the low battery display. I charged it up and now it's fine. I'm thinking that when it freezes up like that it just won't shut down and when the battery dies it's all good again. Weird but I'm glad I didn't ship it out for repairs!

Sent from my Moto G Play using Tapatalk

I asked the company if it could be set up for a different car and they said...

"No if that was the case it would read" can't communicate with unit. Sometimes it happens that once plugged into the vehicle it will acquire new hard codes and needs to be cleared again.it rarely happens but appears to be the case with yours. I will need he unit back to have it reprogrammed."

...so I'm sending it back to them.

Sent from my Moto G Play using Tapatalk

I wonder how a module could 'acquire' new hard codes? I'm not saying that's BS, necessarily, because I know that SRS modules play by somewhat different rules than others. Mostly just wondering about the module's programmed logic. :huh:

Tyler wrote: I wonder how a module could 'acquire' new hard codes? I'm not saying that's BS, necessarily, because I know that SRS modules play by somewhat different rules than others. Mostly just wondering about the module's programmed logic. :huh:

Could I have not followed a specific procedure putting it back in? All I did was disconnect the neg battery terminal.

Sent from my Moto G Play using Tapatalk

Tutti57 wrote:

Tyler wrote: I wonder how a module could 'acquire' new hard codes? I'm not saying that's BS, necessarily, because I know that SRS modules play by somewhat different rules than others. Mostly just wondering about the module's programmed logic. :huh:

Could I have not followed a specific procedure putting it back in? All I did was disconnect the neg battery terminal.

Sent from my Moto G Play using Tapatalk

I just got the module back from the company for the second time. They assured me that there were no codes in it and I am getting the same three popping up. Maybe there is another sensor and the one I replaced wasn't one of the bad ones. I have to figure out what this 1st and 2nd sensor nonsense is. The wire diagram only shows 4 impact sensors, so the numbers are weird.

I forgot to mention last time that my scantool says codes have been deleted, then the light instantly comes back on and now I can't communicate with the module. I can with others but now I can't with the srs. I wonder if I got a bad used module.

Sent from my Moto G Play using Tapatalk

Tutti57 wrote:

Tutti57 wrote:

Tyler wrote: I wonder how a module could 'acquire' new hard codes? I'm not saying that's BS, necessarily, because I know that SRS modules play by somewhat different rules than others. Mostly just wondering about the module's programmed logic. :huh:

Could I have not followed a specific procedure putting it back in? All I did was disconnect the neg battery terminal.

Sent from my Moto G Play using Tapatalk

I just got the module back from the company for the second time. They assured me that there were no codes in it and I am getting the same three popping up. Maybe there is another sensor and the one I replaced wasn't one of the bad ones. I have to figure out what this 1st and 2nd sensor nonsense is. The wire diagram only shows 4 impact sensors, so the numbers are weird.

I forgot to mention last time that my scantool says codes have been deleted, then the light instantly comes back on and now I can't communicate with the module. I can with others but now I can't with the srs. I wonder if I got a bad used module.

Sent from my Moto G Play using Tapatalk

I'm actually thinking that the sensor I put in is bad. I'm going to try swapping another one tomorrow to see if that helps. I was able to clear the codes and after a couple of cycles they came back. Maybe I'll be able to get the scope on it.

Sent from my Moto G Play using Tapatalk

Boy. I finally found the problem. So annoyed. It's the wrong module. This one is for a 2004 and mine is a 2005, different part #. I'll get the right one in and post the results but I'm pretty sure it will be settled then.

Sent from my Moto G Play using Tapatalk

Wait, so... It had the wrong module in it the whole time? Or they sent you the wrong one? :huh:

I mean, I'm happy for you either way! I wonder what the wiring differences are between the two. I'll look that up when I get home.

Tyler wrote: Wait, so... It had the wrong module in it the whole time? Or they sent you the wrong one? :huh:

I mean, I'm happy for you either way! I wonder what the wiring differences are between the two. I'll look that up when I get home.

I don't even know now. I bought a used one that said it fit 2004- like 2009 and now when I look up the part number that's on, it it comes up as a 2004 and I have a 2005. It looks like the part numbers are different but I see tons of listings grouping all of the years together and can't find anything with the part number I'm seeing on the OEM Acura parts website.

Before I realized this I unplugged the right front sensors and got a code for no signal. Then I moved a "bad" sensor to the other side that doesnt have a code and the fault didn't move, which is weird.

I'm going to look at a diagram to compare the two years.

Here is what I have now.



Sent from my Moto G Play using Tapatalk

Tutti57 wrote:

Tyler wrote: Wait, so... It had the wrong module in it the whole time? Or they sent you the wrong one? :huh:

I mean, I'm happy for you either way! I wonder what the wiring differences are between the two. I'll look that up when I get home.

I don't even know now. I bought a used one that said it fit 2004- like 2009 and now when I look up the part number that's on, it it comes up as a 2004 and I have a 2005. It looks like the part numbers are different but I see tons of listings grouping all of the years together and can't find anything with the part number I'm seeing on the OEM Acura parts website.

Before I realized this I unplugged the right front sensors and got a code for no signal. Then I moved a "bad" sensor to the other side that doesnt have a code and the fault didn't move, which is weird.

I'm going to look at a diagram to compare the two years.

Here is what I have now.

Sent from my Moto G Play using Tapatalk

Damn, the diagrams look the same. I don't know what is up with these part numbers.

Sent from my Moto G Play using Tapatalk

Tutti57 wrote:

Tutti57 wrote:

Tyler wrote: Wait, so... It had the wrong module in it the whole time? Or they sent you the wrong one? :huh:

I mean, I'm happy for you either way! I wonder what the wiring differences are between the two. I'll look that up when I get home.

I don't even know now. I bought a used one that said it fit 2004- like 2009 and now when I look up the part number that's on, it it comes up as a 2004 and I have a 2005. It looks like the part numbers are different but I see tons of listings grouping all of the years together and can't find anything with the part number I'm seeing on the OEM Acura parts website.

Before I realized this I unplugged the right front sensors and got a code for no signal. Then I moved a "bad" sensor to the other side that doesnt have a code and the fault didn't move, which is weird.

I'm going to look at a diagram to compare the two years.

Here is what I have now.

Sent from my Moto G Play using Tapatalk

Damn, the diagrams look the same. I don't know what is up with these part numbers.

Sent from my Moto G Play using Tapatalk

A little more info. My part number was replaced by this one, so I don't think it would be an issue.



Sent from my Moto G Play using Tapatalk

I have had it with this one!

Summary to catch everyone up, including what I just did today with it.

Car had a srs module internal fault code

Replaced srs module with used unit

Paid to have hard codes cleared

Now have 3 impact sensor internal fault codes

Replaced front right side sensor with 3 different sensors (all used) code does not go away, come right back after clearing

Swapped "bad" side sensor to the front left and the code did not love with it. Odd. Only thing about this is that the sensor was not bolted in and I don't know if there is some grounding needed there.

Installed another used module and still have the 3 impact sensor codes

When I pull the harness off of the side sensor the code changes to a no signal from impact sensor

At one point after pulling the sensor harness and clearing the codes a single new one came up opd system internal fault

I initialized that part with my scan tool and codes are gone until I key on again, then the 3 impact codes come back.

I hate that I'm using used parts here to have that factor in but these damn things are expensive!

The only other thing I can think of is that the srs module has three plugs in it and 4 slots. I don't remember there being 4 connectors but I'm going to look at the diagram again to see if I can figure that out.

Thoughts?


Sent from my Moto G Play using Tapatalk

Tutti57 wrote: I have had it with this one!

Summary to catch everyone up, including what I just did today with it.

Car had a srs module internal fault code

Replaced srs module with used unit

Paid to have hard codes cleared

Now have 3 impact sensor internal fault codes

Replaced front right side sensor with 3 different sensors (all used) code does not go away, come right back after clearing

Swapped "bad" side sensor to the front left and the code did not love with it. Odd. Only thing about this is that the sensor was not bolted in and I don't know if there is some grounding needed there.

Installed another used module and still have the 3 impact sensor codes

When I pull the harness off of the side sensor the code changes to a no signal from impact sensor

At one point after pulling the sensor harness and clearing the codes a single new one came up opd system internal fault

I initialized that part with my scan tool and codes are gone until I key on again, then the 3 impact codes come back.

I hate that I'm using used parts here to have that factor in but these damn things are expensive!

Thought?


Sent from my Moto G Play using Tapatalk

Sent from my Moto G Play using Tapatalk

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

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.