Looks like we both have same problem. Check this;
Which protocol is this?
Hi All,
Bought ElmScan scan tool and maybe did not do enough homework and found that my car, Toyota Wish JDM (Missing Pin 5 in DLC) is incompatible. Did a bit of searching and found that Pin 5 is actually the signal ground. Any idea where I can find this signal ground so that I can tap to it?
Thanks in advance for any help rendered :-)
dragonz
Looks like we both have same problem. Check this;
Which protocol is this?
Just use pin 4, they are the same (they are usually tied together anyway..)
Hi dragonz,
Let me know if it works for you. I am also interested in buying ElmScan.
Thanks
AG
pin 4 and pin 5 are "virtually" the same. in the car connector, they are usually connected together. just try... but only if you have good manual skills! connecting as i described won't damage anything, but if you mess out something you can seriously damage your car/the scanner... so do at your own risk!
Hi Gip,
I tried and got a signal and boy was I happy. But my happiness was shortlived
as I'm using digimoto ver 4.02 and the serial error message was "BUS Error". So i don't know if the software was the culprit.
But guess what, that was not the end of it coz i left the connection as it is when i shut down the engine. To my horror, the engine refused to start after repeated tries. So I unplugged the OBDII connector and the enging sprung to life
![]()
After Digimoto 5 is released, maybe I would try again but chance is that I will go to a tuner garage and check with them if the "connection" is valid but this would mean at my next servicing in about 2 months time. Meanwhile I will wait for the release 5.
Aghazi bro, guess u have to wait then...![]()
Doesn't the placement of the pins signify the protocol that is being used? And thus, if your pin placement is different on the OBD connector than it is on the OBD reader you bought, wouldn't it be safe to assume that the protocol may be different as well? If the protocol is different, then swapping a couple of pins to make a connection won't help... and judging by the "BUS Error" you are seeing, it seems the reader may be for a different protocol...
The fact that your engine wouldn't start with the reader plugged in is another big clue... having the pins different in the connectors between two different protocols prevents you from making connections that shouldn't be made, when you plug in the wrong type of reader. Just hope you didn't damage anything in the process...
But don't take it from me! here's a quote from a real, live newbie:
eegeek.netOriginally Posted by Viscouse
well, since all the pins of a specific protocol are in there, the protocol should be implemented.. using the protocol-dedicated pins for a different purpose would be a violation of the standard...
The various pin layouts are shown here. It is important to remember that the presence of the socket (even with pins) does not necessarily indicated OBD2 compliance. The age of the vehicle has a significant amount to do with it i.e. 1996 on US, 2001 on Europe (2004 on for diesel).
Hope this helps,
Gareth
Bookmarks