Been asked MANY times before, OBD2 connection

ProjectPuma

Help Support ProjectPuma:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

craig26283

Member
Joined
Apr 6, 2011
Messages
32
Location
Glasgow
Hello!

I'm failing to get my 2001 Puma connected to my OBD2 device, this is the very one...

http://www.ebay.co.uk/itm/OBD2-ELM3...231?pt=LH_DefaultDomain_3&hash=item1e8f46616f

It supports the Puma protocol, which I discovered by searching these very forums.

I have read about problems connecting to earlier Pumas, but I assumed mine would be past that.

My Clio DCi connects no problems, via my phone (torque or touchscan) or laptop.

With the Puma it lights up and tries through all different protocols then fails to connect.

Any ideas?

Thanks
 
craig26283 said:
I have read about problems connecting to earlier Pumas, but I assumed mine would be past that.
The main problem is actually getting crap Ebay OBDII readers to connect to the protocols they claim.

Here is what I use on my '97 Puma - http://www.ebay.co.uk/itm/390665722455?ru=http%3A%2F%2Fwww.ebay.co.uk%2Fsch%2Fi.html%3F_from%3DR40%26_sacat%3D0%26_nkw%3D390665722455%26_rdc%3D1" onclick="window.open(this.href);return false;

The Android Torque pro app allows use of a USB lead these days.
 
^^That's a good one.

The bluetooth version I have is equally as good but obviously cableless:
http://www.ebay.co.uk/itm/NEW-OBD2-ELM327-V1-5-Bluetooth-Car-Scanner-Android-Torque-Auto-Scan-Tool-OBD-II-/331206015268?pt=LH_DefaultDomain_3&hash=item4d1d6ab924" onclick="window.open(this.href);return false;

I've used to to fault find BMWs, Fiats, Fords, Audis, Vauxhalls so I know it's a good one.
 
I have that one Dal, and it doesn't work in either my '97 car or my neighbour's 2000 one despite claiming to support the Ford protocol. Having said that, a lot of them look the same but don't have the same internals. It does work on all the other cars I've tried it on though.
 
Weird, it worked on our Thunder. *confused*

Unless it's the "pick and mix" of ebay quality control as Frank suggests?

As long as it's ELM327 it should work.

https://en.wikipedia.org/wiki/ELM327" onclick="window.open(this.href);return false;

Pirate clones[edit]

Typical cheap ELM327 clone from china without label on the controller
The 1.0 version of the ELM327 did not implement copy protection, and the PIC code was copied[6][7] and widely sold in devices claiming to contain an ELM327 device. Problems have been reported[8] with Chinese clones, partially due to bugs inherent in the early code. These clones frequently advertise the "ELM327" name more prominently than brand-name devices that may contain a real ELM327.

Although these pirate clones may contain the ELM327 v1.0 code, they may falsely report the version number as the current version provided by the genuine ELM327, and in some cases report an as-yet non-existent version.[9] The actual function of these pirate clones is nonetheless limited to the function of the original ELM327 v1.0, with inherent deficiencies.
 
The other point to consider is the OBDII RS232 socket connector itself. As with other multipin connectors, like SCART, these are prone to poor contact connections. Using Contact Cleaner helps a lot, but even then wiggling the connector around may still be necessary.

People forget that prior to USB connectors that getting stuff connected could be a problem. If getting a PS1 connected to a TV with a SCART indoors could be a problem, then people really should expect the same on a 15+ year old car that is kept in a garage or in the road.

Clean and wiggle. :)
 
I did clean the contacts very carefully, but it still refused to work. The adopter was working and trying to communicate with my car, but couldn't find the protocol. On my neighbours car, it didn't even do the LED light run through when you connect it.

As you say Dal, there are so many clones that look all the same on the outside but the revisions are not the same. It seems very pot luck!

Shame as it could give me a clue as to my lack of power if the thing worked!

Sorry, I've hijacked this haven't I... :oops:
 
The Arch Bishop said:
Shame as it could give me a clue as to my lack of power if the thing worked!:
We are talking about seven quid! If you dropped your KFC when you left the place, would you just not eat that evening? Same thing.

You know which one to get and that it works on a R reg - http://www.projectpuma.com/viewtopic.php?p=338968#p338968" onclick="window.open(this.href);return false; Just dig deep and get another one. ;)
 
If it'd gotten that bad, I'd have probably eaten my own hands by the time I'd gone in there to eat (although it would explain why I'd have dropped it).

It's not a case of 'digging deep', I'm just getting fed up of buying numerous dongles to find that they don't work on the Puma. The last one I bought was recommended as it could read J1850 protocol and that didn't work. I've just tried a more up to date one that my neighbour bought. Again, torque can talk to the reader, the reader can't talk to the ECU.

I will buy the one you recommended, however, if it doesn't work, you have to let my 3 year old eat a greasy KFC inside your car. Deal? She's a bit clumsy though... :p
 
The Arch Bishop said:
It's not a case of 'digging deep', I'm just getting fed up of buying numerous dongles to find that they don't work on the Puma
I know, I recognised that weary tone of despair...I've been like that myself over stuff.

The Arch Bishop said:
I will buy the one you recommended, however, if it doesn't work, you have to let my 3 year old eat a greasy KFC inside your car. Deal? She's a bit clumsy though... :p
Let's hope it works or that young lady is off on a trip to Croatia, as it was Wild E. Coyote who recommended it to me. :)
 
The Arch Bishop said:
Nope - same as the others. Cannot connect to the ECU. I'm off down KFC...
Hmm, that model works on my R reg 1.7. Maybe your RS232 socket connection? About the only variable left.

On the plus side, if ever you decide to open a small OBD reader shop, then at least you're already stocked and good to go.

I'm off to KFC-proof my motor against infant attack. :p
 
Frank said:
The Arch Bishop said:
Nope - same as the others. Cannot connect to the ECU. I'm off down KFC...
Hmm, that model works on my R reg 1.7. Maybe your RS232 socket connection? About the only variable left.

On the plus side, if ever you decide to open a small OBD reader shop, then at least you're already stocked and good to go.

I'm off to KFC-proof my motor against infant attack. :p
I wouldn't worry, even she won't eat KFC! I can only think that the water ingress I has damaged the socket beyond just pin corrosion.
 
Dal said:
^^That's a good one.

The bluetooth version I have is equally as good but obviously cableless:
http://www.ebay.co.uk/itm/NEW-OBD2-ELM327-V1-5-Bluetooth-Car-Scanner-Android-Torque-Auto-Scan-Tool-OBD-II-/331206015268?pt=LH_DefaultDomain_3&hash=item4d1d6ab924" onclick="window.open(this.href);return false;

I've used to to fault find BMWs, Fiats, Fords, Audis, Vauxhalls so I know it's a good one.

Wonderful, have ordered this one now :)

Will report back when it arrives!
 
Frank said:
craig26283 said:
I have read about problems connecting to earlier Pumas, but I assumed mine would be past that.
The main problem is actually getting crap Ebay OBDII readers to connect to the protocols they claim.

Here is what I use on my '97 Puma - http://www.ebay.co.uk/itm/390665722455?ru=http%3A%2F%2Fwww.ebay.co.uk%2Fsch%2Fi.html%3F_from%3DR40%26_sacat%3D0%26_nkw%3D390665722455%26_rdc%3D1" onclick="window.open(this.href);return false;

The Android Torque pro app allows use of a USB lead these days.

And I have just ordered this one!
 
I am reviving this topic as I am having issues reading OBD2 from the Puma.

I have an unotec bluetooth scanner, which supposedly accepts the following protocols:
-SAE J1850 PWM(41.6Kbaud)
-SAE J1850 VPW(10.4Kbaud)
-ISO9141-2(5 baud init,10.4Kbaud)
-ISO14230-4 KWP(5 baud init,10.4 Kbaud)
-ISO14230-4 KWP(fast init,10.4 Kbaud)
-ISO15765-4 CAN(11bit ID,500 Kbaud)
-ISO15765-4 CAN(29bit ID,500 Kbaud)
-ISO15765-4 CAN(11bit ID,250 Kbaud)
-ISO15765-4 CAN(29bit ID,250 Kbaud)
-SAE J1939 CAN(29bit ID,250*Kbaud)
-USER1 CAN(11*bit ID,125*Kbaud)
-USER2 CAN(11*bit ID,50*kbaud)

I understand that the highlighted one is the Puma protocol.

This works fine on other cars, but when in the puma, the software can connect to it, but not retrieve data (can't find the protocol).

I liked the Unotec as it is relatively small, so I can leave it plugged in and it transmits to my tablet or smartphone (on other cars), whereas the ones posted above are larger.

Mine:
adaptador-obd-ii-diagnostico-automovil.jpg


@Dal: does your bluetooth version work with the older Pumas (1.7, registered in 98, built in 11/97)?

Is there any kind of extension cable that any of you know of that would allow me to place the scanner somewhere that is not going to get kicked everytime I get in (mines LHD)?
 
JAC said:
Is there any kind of extension cable that any of you know of that would allow me to place the scanner somewhere that is not going to get kicked everytime I get in (mines LHD)?
If you look at "How I Fitted My ScanGauge II", you'll see how I moved the OBD II connector, so it didn't stick out when connected:
http://www.projectpuma.com/viewtopic.php?f=51&t=7082" onclick="window.open(this.href);return false;
 

Latest posts

Back
Top