OBD2 interface problem

Reply Subscribe

Thread Tools

Search this Thread

Feb 12, 2010 | 12:12 PM

MikeLex

Thread Starter

Lead Lap

Joined: Jan 2010

Posts: 409

Likes: 5

From: NY

OBD2 interface problem

I got a new ELM327 USB OBD2 interface, which is unable to communicate with the ECU of my 98ES. I believe the problem is on the vehicle side, rather than in the tool. Have anyone already had this type of problem?

Feb 12, 2010 | 10:06 PM

Lexmex

CL Community Team

Joined: Apr 2004

Posts: 17,329

Likes: 210

From: Miami, Florida

What kind of software are you trying to use with it?

Feb 13, 2010 | 05:17 AM

MikeLex

Thread Starter

Lead Lap

Joined: Jan 2010

Posts: 409

Likes: 5

From: NY

Quote:

Originally Posted by Lexmex

What kind of software are you trying to use with it?

In my 94 Camry I've been using the scantool_net v. 1.13 (freeware) and a ELM327 USB clone made in China. It works wonders. On my 98 ES, however, this system fails. I thought the culprit might be interface, so I ordered an updated one (less than 10 bucks, by the way) to no avail. I also tried the ProScan V. 5.6 (software) and as a result it opens the port, detects the interface but it is unable to initialize it.

Feb 13, 2010 | 06:18 AM

Lexmex

CL Community Team

Joined: Apr 2004

Posts: 17,329

Likes: 210

From: Miami, Florida

I ended up getting an ELMScan5 Compact for like about $59 on Amazon and it works fine with scantool and even Digimoto for my RX300, that's got to have similar ECM firmware given your 98 and my 99 have a similar but not 100% the same 1MZFE engine. I have read elsewhere on other forums about issues involving those USB Clones. A friend of mine who lived in Mexico City got one of those clones and it would not work on a 2003 Toyota Camry (that was the first model year for Toyota down there), despite my OBD2 scanner working and of course Toyota's factory scanner.

Feb 13, 2010 | 11:50 AM

MikeLex

Thread Starter

Lead Lap

Joined: Jan 2010

Posts: 409

Likes: 5

From: NY

Thanks, Lexmex!

Feb 14, 2010 | 01:31 PM

frohboy33

Driver

Joined: Dec 2009

Posts: 67

Likes: 0

From: ND

Anybody know what protocol the ES uses? I just ordered one of these off of ebay and now I'm worried it wont work after reading this. I thought I had read somewhere thats its the ISO 9141 protocol.

Feb 15, 2010 | 03:35 AM

MikeLex

Thread Starter

Lead Lap

Joined: Jan 2010

Posts: 409

Likes: 5

From: NY

Quote:

Originally Posted by frohboy33

Anybody know what protocol the ES uses? I just ordered one of these off of ebay and now I'm worried it wont work after reading this. I thought I had read somewhere thats its the ISO 9141 protocol.

The vehicle’s ECM uses ISO 9141–2 protocol for communication. The terminal arrangement of the connector complies with SAE J1962 and matches the ISO 9141–2 format. For some reason (firmware?), however, the interface I bought is unable to communicate with the ECM, as it was supposed to do. Here is the list of supported protocols according to its manufacturer:

SAE J1850 PWM (41.6 kbaud)
SAE J1850 VPW (10.4 kbaud)
ISO 9141-2 (5 baud init, 10.4 kbaud)
ISO 14230-4 KWP (5 baud init, 10.4 kbaud)
ISO 14230-4 KWP (fast init, 10.4 kbaud)
ISO 15765-4 CAN (11 bit ID, 500 kbaud)
ISO 15765-4 CAN (29 bit ID, 500 kbaud)
ISO 15765-4 CAN (11 bit ID, 250 kbaud)
ISO 15765-4 CAN (29 bit ID, 250 kbaud)

Supported Software :
Scantool_net113win
EasyOBDII
OBD2Spy
ScanMaster-ELM