OBD II All Protocol Diagnostic Scanner Interface
|This four protocol OBD-II scanner
interface provides USB interface between a PC & PDA and vehicles OBD-II
- J1850 PWM (Pulse Width Modulation)
- J1850 VPW - (Variable Pulse Width
- ISO9141-2 protocols (EOBD)
- ISO14230-4 protocols
- J2284 CAN Bus
- many Daimler-Chrysler Corporation vehicles
- many European vehicles
- most Japanese vehicles.
- most GM / GMH vehicles.
- some Mazda vehicles
- most Ford vehicles.
- Supports both K and L lines
- retrieve error codes
- retrieve engine operating conditions
(temp, rpm, speed etc)
- real time data logging to a PC
- bi-colour led for shows the current logic
- powered from car battery over OBD2
- connects to PC via USB
Due to the inclusion of all four OBDII
protocols you can be assured that you will be able to read OBDII data from
appropriately equipped vehicles without having to determine which interface
type you need. Modern USB connection ensures simple and speedy data
The interface can be used in conjunction with
our free software to turn your laptop or desktop computer into a fairly
sophisticated automotive diagnostic system. The included software has a
built-in database of more than 3000 trouble codes, and allows you to read
and erase stored trouble codes and oxygen test results, turn off the MIL
("Check Engine" light), and display real-time sensor data.
The circuitry utilises a central interpreter
for the four standard on-board diagnosis (OBD-II) equipped vehicle using a
USB connection, to convert between a the OBDII data streams and standard
ASCII characters for a robust connection to PC or PDA.
The OBD-II bus activity LED's help
troubleshoot problems on the vehicle side.
Interface and Software Features
The hardware interface provides a number of
features and capabilities. You can even request proprietary codes if you have
them available. However the hardware relies on the appropriate software on the
PC to request and display this information.
- Read diagnostic trouble codes, both generic
- Display their meaning (over 3000 generic code
definitions in the database).
- Clear trouble codes and turn off the MIL
("Check Engine" light)
- Display current sensor data, including:
- Engine RPM
- Calculated Load Value
- Coolant Temperature
- Fuel System Status
- Fuel Pressure
- Vehicle Speed
- Short Term Fuel Trim
- Long Term Fuel Trim
- Intake Manifold Pressure
- Timing Advance
- Intake Air Temperature
- Air Flow Rate
- Absolute Throttle Position
- EGR status
- Catalytic Converter temperature
- Time / distance since ECU reset
- ECU voltage
- Oxygen sensor voltages/associated short term
- Data graphing and logging
- Freeze frame data
- Continuos and non continuos oxygen sensor
- Many others...... vehicle dependant
provided with this interface is shareware, freeware, or demonstration versions.
Neither PDA or PC are included.
The circuitry inside the OBD-II interface
supports the four protocols defined by OBD-II. This interface will NOT
support ALDL interface used by some pre-standard GM cars and light trucks. If
you are interested in the ALDL interface, eitehr check out those interfaces on
this site or email us. There's a guide to
Protocol does my vehicle use? in our Articles section
For European emission related standards, EOBD
starting in year 2000 is the equivalent of OBD-II (ODB-2) in the USA. In
Australia for most light vehicles after 2004 are compliant with one of the standards. Diesel engines typically need to be post 2003 for OBD-II
facilities - some even post 2006
Check with this
website or to
here to find out which OBD-II
standard your car uses, as well as locating the OBD-II data link connecter for each vehicle. Can't find the connector, there's a guide to
connector locations in our FAQ section. However if your vehicle
is NOT listed, this does not mean it is not OBD-II compliant. As long as it is a standard OBD-II type, this interface will work.