My OBD2 won't communicate with my truck but Autozone's does

My

$21 Ancel AD310 Classic Enhanced Universal OBD II Scanner Car Engine Fault Code Reader CAN Diagnostic Scan Tool-Black

Ancel AD310 scanner bombs out about half way through attempting to connect with my 1999 Toyota Tacoma SR5 4WD truck. I took it (truck) to Autozone and their scanner worked flawlessly. Also, I tried my scanner on my other vehicle, a 1996 Lincoln Town Car and it works fine. I changed the 10amp fuse in the fuse box under the hood. I can't figure this out. If Autozone's scanner works that tells me that there are no issues with the trucks wiring and if my scanner works on my Town Car that tells me that the scanner is working ok. What could be preventing the scanner from connecting to my truck?

 

Poor connection between your device and the truck .

Might be some corrosion might be how the pins and sockets mesh

Your device works on your other vehicle Auto Zones connects to your Truck

Logic says it is in the connection.

 

Not familiar with the handheld models but is it possible it doesn't support the protocol?

 

that scanner is an entry level scanner and as such, it probably doesnt have the communication protocol that your Tacoma uses. I looked on the Ancel website and they dont list anything in the specifications tab. OBDII is a “general standard” interface but the function of the pins and the software is different sometimes from year to year and manufacturer to manufacturer.


couldn't find this when I originally posted.

https://www.scantool.net/blog/which...tly, ISO15765-4/SAE J2480 (a "flavor" of CAN).

 

i have scangauge II and works perfectly.

 

i hav

I have the same model for a few years now it connects fine to my OBII vehicles. it worked for my 2017 Ford F550 with the Can systems.

Then I have had to do some cleaning and replacing of pins over the years.

It lives in the Truck I have never had a code trip I could not read.

It is a simple code reader of course it does not read ABS or Transmission codes nor real time data.

 

I Realize I’m posting in a 3 year old thread but came across this issue today on my own and had been troubleshooting. I have had this Ancel for a while and it’s worked in my 99 4Runner and in my crawler w a 5vz and 97 4Runner Ecm. It will not however connect to my 99 5vz Tacoma. Fuses good, connections appear good. Truck functions normally I don’t suspect an ECM issue. Just curious what the difference is. Port has power and screen cycles through protocols attempting to connect but can’t sync up with the truck for some reason. Times out after maybe 4 different protocols over 30 seconds then presents a failure message. Going to fiddle with it a bit tmrw.

 

Just my 2 cents worth...

Not all scan tools are compatable with all vehicles, thats just how it is. Even professional level scan tools have issues, case in fact. I am working on a few project cars, one is a 2005 BMW 330Ci and the other is an 2003 Jeep Cherokee. My Snap On Verus misidentified the BMW, using the auto ID feature, on the BMW. It stated that it had the 2.5 motor when I know it has the 3.0. The same tool did not pick up the Crankshaft position sensor code on Jeep but my older Snap On Solus Edge worked correctly on both. I reached out to some people here on the board and they confirmed that sometimes certain tools just dont work on certain brand vehicles. I am glad that I had a feeling to switch tools to verify what my gut was telling me otherwise I might have gone down a different diagnostic path and who knows how much time that would have wasted. I tried both OBDII and manufacturer specific scan too. By the way, my BlueDriver got both diagnostics right, that is a $100 tool vs the thousands into the Snap On ones. Dont get me wrong, the Snap On scan tool(s) are great and they do things that the $100 tool cant, like synch the cam position sensor to the crank sensor on the Jeep which was part of the problem.