OBD2 Port Not Communicating with Scanner
#31
10-20-2019, 10:00 AM
ZackMan
Apologies "buzz-out" is UK colloquial term for "continuity check" i.e. using a multimeter on a low ohms range e.g. 0-200 Ohms (you meter may even have a buzzer!)
"DLC" is the Datalink connector (the connector that pushes into the vehicle) so "DLC-2" is Data Link Connector pin 2.
"D" is the 26-Way D-Type Connector that screws into your Tech2, "D-4" is 26-Way D-Type pin 4.
So if you look at the ends of the cable connectors, the pins are numbered as per my sketch.
So detach your TECH2's cable and check the following:-
Your TECH2 should have come with a 12V Power Supply that plugs-in just to the right of the 26-Way D-Type, its a standard 12V jack. If you don't have a PSU one from a PC monitor, just check its 12V.
Connect scope probe tip to DLC-2 and ground clip to either DLC-4 or DLC-5, set the scope to DC, 1V/Division and 200uS/Division. If you can set the scope to "free run" or "continuous" just to prove there is activity then set it to "DC Triggered" with a trigger level of around +1V to +2V. On the TECH2 select the function I mentioned before (even if your vehicle doesn't have AS) and you should see a signal the moment you hit the key.
If the signal looks similar to the one I posted, then its safe to assume your TECH2 is working OK.
When you say "The scanner is operational and can scan all protocols but cannot link to any of them" do you get a communications error? If so make sure you have selected the correct "Model Year" not the year the truck was 1st bought e.g. my model year is 2005 but was bought in 2006. I noticed that I get the same issue when the wrong year is selected.
Keep us posted..
Apologies "buzz-out" is UK colloquial term for "continuity check" i.e. using a multimeter on a low ohms range e.g. 0-200 Ohms (you meter may even have a buzzer!)
"DLC" is the Datalink connector (the connector that pushes into the vehicle) so "DLC-2" is Data Link Connector pin 2.
"D" is the 26-Way D-Type Connector that screws into your Tech2, "D-4" is 26-Way D-Type pin 4.
So if you look at the ends of the cable connectors, the pins are numbered as per my sketch.
So detach your TECH2's cable and check the following:-
- DLC-2 connects to D-4
- DLC-4 connects to both D-8 and D-9
- DLC-5 connects to D-2
- DLC-16 connects to both D-17 and D-18
Your TECH2 should have come with a 12V Power Supply that plugs-in just to the right of the 26-Way D-Type, its a standard 12V jack. If you don't have a PSU one from a PC monitor, just check its 12V.
Connect scope probe tip to DLC-2 and ground clip to either DLC-4 or DLC-5, set the scope to DC, 1V/Division and 200uS/Division. If you can set the scope to "free run" or "continuous" just to prove there is activity then set it to "DC Triggered" with a trigger level of around +1V to +2V. On the TECH2 select the function I mentioned before (even if your vehicle doesn't have AS) and you should see a signal the moment you hit the key.
If the signal looks similar to the one I posted, then its safe to assume your TECH2 is working OK.
When you say "The scanner is operational and can scan all protocols but cannot link to any of them" do you get a communications error? If so make sure you have selected the correct "Model Year" not the year the truck was 1st bought e.g. my model year is 2005 but was bought in 2006. I noticed that I get the same issue when the wrong year is selected.
Keep us posted..
#32
10-20-2019, 10:53 AM
oceanbrave,
The issue was with the “model year” on the Tech2. I was selecting model year 2006 which is the year of the H2 but it was built 09/05. I then selected model year 2005 and all links are now communicating.
Your excellent examples and screen shots were a real education for me and I truly appreciate your time and expertise.
Thanks to all who responded. Your thoughts and recommendations were a great boost.
The issue was with the “model year” on the Tech2. I was selecting model year 2006 which is the year of the H2 but it was built 09/05. I then selected model year 2005 and all links are now communicating.
Your excellent examples and screen shots were a real education for me and I truly appreciate your time and expertise.
Thanks to all who responded. Your thoughts and recommendations were a great boost.
Thread
Thread Starter
Forum
Replies
Last Post