KM - that looks interesting- I shudder to look for the price
I am trying to find a decent explaination of OBDII, manufacturer specific codes, vag-com, 'hex codes' and a few other things.
I get that OBD-II is a standardized hardware (plug/wiring) and software (communication protocol) currently enforced on all cars...
(...until OBDIII comes out and the conspiracy theorists' heads blow up
So you can get a standard OBDII reader, and it will read the codes from any make-model, from 1997 - present. but it'll own read the designated OBDII codes.
OR, you can buy a VW/audi car and get a VAG-com - which has a hardware (dongle) and software component (VCDS software). These 2 things read OBDII codes AND VW-specific codes. AND can access VW specific modules (ABS module, airbag module, transmission module...)
***so is there a 2nd communication protocol used by VAG-COM ? or does it use the same wires/signals/voltages that OBDII uses ?
And then, if you buy a newer VW, Ross Tech (makers of the VAG-COM) tell you to buy the "USB+HEX" dongle- becuase the newer cars use "Hex-codes" or something.
***Are the Hex codes a new communication protocol, or still the same wires/voltages/handhaking as OBD-II ? If ross-tech is trying to sell a new dongle, then the protocol/voltages/handshaking better be different...
Then the guys on the Subaru board (I own a 2001 Outback, see the machine shop thread for more arguing
say just to buy a vag-com and use some Rom/Raider other software. This makes me think that subaru uses the OBD-II protocol and hardware for its stuff also..but VCDS doesnt have/support the lookup tables necessary for Subarus - this makes sense.
I just want a tool that can see as much factory info as possible on a 2001 outback, a 2009 Kia minivan, and any 2000- volkswagen that I might buy in the future. Would your gizmo (above) do this ?
-John