best OBD II scanner for 2003 Accord or newer Hondas

I'm thinking of buying a scanner for my 2003 4cyl Accord LX but also
want to be able to use it on any newer Hondas I might buy. Any
recommendations for a non-mechanic ?

Also, on the 2003 Accord, where will this plug in? Thanks.

 

I'm using a ScanGaugeII. Little pricey for what it does as a OBD II
Scanner, but also can be left plugged in for real-time system monitoring.

Plug should be in the drivers side footwell tucked up under the dash. On my
2001 it is closest to the left kick-panel.

 

I'm using a ScanGaugeII. Little pricey for what it does as a OBD II
Scanner, but also can be left plugged in for real-time system monitoring.

Plug should be in the drivers side footwell tucked up under the dash. On my
2001 it is closest to the left kick-panel.

 

I wonder why they just don't put a USB interface in the cars already,
then distribute a program that would read the codes and dive directly
into the troubleshooting of the code based on the car ID.

 

I wonder why they just don't put a USB interface in the cars already,
then distribute a program that would read the codes and dive directly
into the troubleshooting of the code based on the car ID.

 

car manufacturers fought a common obd standard tooth and nail. its
existence is one of the few instances where government actually got it
right and could see that fully proprietary coding would be the ultimate
in lock-in device and end up costing the consumer up the wazoo. it
would also put all the independent repair shops out of business
overnight, which is ultimately why we have what we have today.

but the car manufacturers still don't like it. the intent of obd has
been diluted with all the tier two codes, the "proprietary" codes, which
are completely inconsistent. iow, manufacturers, with constant lobbying
and back-door influence, want to make it difficult and more expensive
for a mom & pop garage to exist, and keep the vehicle coming back to the
dealer. you can expect that trend to continue - the nature of politics,
influence and business interests being what they are, a fully
"universal", accessible-by-anyone software interface will simply never
exist.

 

car manufacturers fought a common obd standard tooth and nail. its
existence is one of the few instances where government actually got it
right and could see that fully proprietary coding would be the ultimate
in lock-in device and end up costing the consumer up the wazoo. it
would also put all the independent repair shops out of business
overnight, which is ultimately why we have what we have today.

but the car manufacturers still don't like it. the intent of obd has
been diluted with all the tier two codes, the "proprietary" codes, which
are completely inconsistent. iow, manufacturers, with constant lobbying
and back-door influence, want to make it difficult and more expensive
for a mom & pop garage to exist, and keep the vehicle coming back to the
dealer. you can expect that trend to continue - the nature of politics,
influence and business interests being what they are, a fully
"universal", accessible-by-anyone software interface will simply never
exist.

 

I suspect the reason is that they don't WANT a widely distributed program
out there that can do that.

 

I suspect the reason is that they don't WANT a widely distributed program
out there that can do that.

 

It is the same reason they don't include shop manuals or free lifetime
maintainance with every car. They have no motivation to do so.

 

It is the same reason they don't include shop manuals or free lifetime
maintainance with every car. They have no motivation to do so.

 

Google and you will find programs and interface cables to allow your laptop
to read the OBD-II codes.They aren't free,however.


for starters; http://www.thinkythings.org/obdii/

it has links to some commercial products.


--
Jim Yanik
jyanik
at
localnet
dot com

 

Google and you will find programs and interface cables to allow your laptop
to read the OBD-II codes.They aren't free,however.


for starters; http://www.thinkythings.org/obdii/

it has links to some commercial products.


--
Jim Yanik
jyanik
at
localnet
dot com

 

I use one of the laptop interfaces and I really like it. There is free
software available, although the free stuff is all generic OBDII. I rely on
it more for the live data than for codes, but it has been adequate, and has
helped me diagnose some tough ones. The one I bought was called ProScan, but
any of the elm interfaces work the same. It's a pretty inexpensive tool and
works pretty well.

 

I bought a commercial product from EASE Diagnostics for my 03 Accord
Sedan in 2004. IIRC it was about $250 for everything, e.g., interface
device, PC cables & software. It wasn't until I looked just now that I
saw they call their software "Scan Tool", so I'm guessing it's the same
product that Jim just described. Since 2004 I had to buy a Serial to USB
adapter because my new laptop doesn't have a serial port.

Don't know about their current pricing, but it runs flawlessly and has
been very helpful, e.g., when a had a failing O2 sensor.

http://www.obd2.com/scantool/scantool.htm

 

Maybe it will require an act of congress.....

 

Maybe it will require an act of congress.....

 

I'm aware of those products (snide Google remark notwithstanding), but I did
not get the impression the OP was asking that question. It does appear from
his question that he is not aware the port on all cars since 1995 is in fact
standardized.

 

but it's not usb standard. and the codes are not all standardized either.

 

For the budget-conscious, consider jumping terminals 4 and 9 of the
OBDII Data Link Connector and counting flashes of CEL, per
http://hondatuning.info/how-to-read-diagnostic-trouble-codes-dtcs-without-an-obdii-scan-tool/.

The same method may be used to read ABS and SRS codes when the ABS
light or SRS light is on.