OBD2 Port Not Working Properly

[Fatcat]

imma just cut straight to the chase, i used to be able to scan my car with my Foxwell scanner but out of nowhere it just stopped connecting, at first I thought it was just a faulty update so I tried it with another OBD2 scanner which is older and more basic. power works and it lights up but it just says no codes detected (I have a misfire so I know that's a lie) if you unplug and replug enough it'll connect using kwp2000 protocol and it'll show my misfire. ECU has been changed before could that be the problem?

how can I even diagnose what's wrong? and my biggest question is how did this even happen out of nowhere?

[andrewwynn]

The obd connectors are known to break and will give you the symptoms you describe.

[Fatcat]

Originally Posted by andrewwynn

The obd connectors are known to break and will give you the symptoms you describe.

What breaks, specifically the pins? I assume it's the connection pins, where it won't communicate well with the scanner unless you really jam it in, but I want to hear other people's opinions. Also, what do you recommend I do?

[EODguy]

Originally Posted by Fatcat

What breaks, specifically the pins? I assume it's the connection pins, where it won't communicate well with the scanner unless you really jam it in, but I want to hear other people's opinions. Also, what do you recommend I do?

Mine was a cracked obd2 block and it allowed the pins to slide back when plugging in the cable. The cracks were small and not visible on mine until a cable was plugged in caused them to show, of course I found that out by pulling the block and sticking my plug into it..

Sent from Embassy network using Tapatalk

[Fatcat]

Originally Posted by EODguy

Mine was a cracked obd2 block and it allowed the pins to slide back when plugging in the cable. The cracks were small and not visible on mine until a cable was plugged in caused them to show, of course I found that out by pulling the block and sticking my plug into it..

Sent from Embassy network using Tapatalk

I have yet to check the OBD2 Port, but I've noticed when I take the connector out of the scanner and put it back in a couple of times (as the OBD2 port is still plugged in the car) it connects. Could this still be from a bad OBD2 port? because it connects after a few tries on the scanner not the Port on the car itself

[EODguy]

Originally Posted by Fatcat

I have yet to check the OBD2 Port, but I've noticed when I take the connector out of the scanner and put it back in a couple of times (as the OBD2 port is still plugged in the car) it connects. Could this still be from a bad OBD2 port? because it connects after a few tries on the scanner not the Port on the car itself

I had the exact same symptoms. There's no guarantee it's the same for yours, but disconnect the block and plug something in to it and look and see if any of the squares "spread" due to cracks (a Bluetooth dongle is best for maneuverablity)

Sent from Embassy network using Tapatalk

[Fatcat]

Originally Posted by EODguy

Mine was a cracked obd2 block and it allowed the pins to slide back when plugging in the cable. The cracks were small and not visible on mine until a cable was plugged in caused them to show, of course I found that out by pulling the block and sticking my plug into it..

Sent from Embassy network using Tapatalk

how do you pull out the block? Sorry for all these questions im trying to learn.

[andrewwynn]

Looks like it's held in with clips (snap in). The repair guide for r/r the trim says to remove the electrical connector and then remove the obd port.

You can likely just release the port and pull it out if you can reach up inside and squeeze the clips. That way still attached to test. I don't know what magic button you need to press on the electrical connector the guide didn't say but you can look for a YouTube video.

[Fatcat]

Thank you very much I will check it out whenever i can