Bluetooth Wireless OBD2 Reader

Bluetooth OBDII ELM 327 Code Reader Tool with No Wire.

• Connect to your computer without the need to run wires or get tangled in cords.
• The ultimate solution for in-vehicle laptop users!
• Computer with Bluetooth Required or you must buy a bluetooth USB adapter.
• Wireless Interface, Read & Clear Generic and Manufacturer Specific Codes, Monitor Status, and Retrieve VIN Data! CANBUS Support!

(Note: may not be compatible with some VW, Audi, Porsche and Subaru vehicles)

Even if you don't repair your vehicle yourself, knowing the Diagnostic Trouble Code number before taking the vehicle in for repair is good knowledge to have. Once the vehicle is repaired, the Diagnostic Trouble Code(s) can be erased and the Check Engine light turned off using this scan tool.

In areas that require a smog test, an illuminated Check Engine light fails the emission test, even if the repaired vehicle might otherwise pass inspection. This OBD II Scan Tool turns off the Check Engine light.

Another highly useful application for the scan tool is purchasing used vehicles. Used vehicles can have all sorts of expensive mechanical or electrical problems. Remember, not all Diagnostic Trouble Codes illuminate the Check Engine light and a scan tool is the only way to obtain the information.

This tool supports all OBD II protocols:

n SAE J1850 PWM

n SAE J1850 VPW

n ISO 9141-2

n ISO 14230 (KWP2000)

n CANBUS

WHAT IS CAN?

Controller Area Network (or CAN) is the newest automotive communication protocol. CAN Protocol is around 50 times the speed of the older protocols.

CAN was used in some cars starting in 2003, and is said to be the only protocol that will be used after 2007.

The Bluetooth ELM327 is the newly developed wireless scan tool. It supports all OBD-II protocols

Supported Features Include:

n Data graphing and logging

n Freeze Frame data

n Continuous and Non-Continuous Oxygen Sensor test results

n Works with all OBD-II compliant vehicles

n Wireless (Bluetooth)

n Software included for Palm, PDA

n Software included for Windows PC

n Software included for Windows Smartphone

n Supports ISO 9141, KWP2000

n Supports SAE J1850

n Supports CAN bus

Functions:
n Read diagnostic trouble codes, both generic and manufacturer-specific, and display their meaning (over 3000 generic code definitions in the database).

n Clear trouble codes and turn off the MIL ("Check Engine" light)

n Display current sensor data, including:

Engine RPM
Calculated Load Value
Coolant Temperature
Fuel System Status
Vehicle Speed
Short Term Fuel Trim
Long Term Fuel Trim
Intake Manifold Pressure
Timing Advance
Intake Air Temperature
Air Flow Rate
Absolute Throttle Position
Oxygen sensor voltages/associated short term fuel trims
Fuel System status
Fuel Pressure
Many others...

Available Software - This tool comes with some software, but many other software titles can be downloade for free. Some include:
Scantool.net
GM Mode 22 Scan Tool by Terry
OBD Gauge for PalmOS and Pocket PC by Dana Peters
OBD Logger by Jonathan Senkerik
OBD-II ScanMaster by Wladimir Gurskij (ScanMaster 3.52 - local copy) obd2crazy.com
OBD2 Scantool by Ivan Andrewjeski
OBDII for ELM322 by David Huffman
pyOBD by Donour Sizemore for MacOSX and Linux
RDDTC by Pete Calinski
Real Scan by Brent Harris
ScanTest for Pocket PC by Ivan Ganev aka a-ser
wOBD by WDT

....many others!

Does My Car Have OBD-II?
All cars and light trucks built and sold in the United States after January 1, 1996 were required to be OBD II equipped. In general, this means all 1996 model year cars and light trucks are compliant, even if built in late 1995.

Two factors will show if your vehicle is definitely OBD II equipped:
1) There will be an OBD II connector located under or around the dashboard, and
2) There will be a note on a sticker or nameplate under the hood: "OBD II compliant".
Where is the connector located?
The connector must be located within three feet of the driver and must not require any tools to be revealed. Look under the dash and behind ashtrays.

The Three Flavors of OBD II
While the parameters, or readings, required by OBD II regulations are uniform, the auto manufacturers had some latitude in the communications protocol they used to transmit those readings to scanners. Naturally, each felt they had the one true way, so we have three different OBD II communications protocols in use.

What Communications Protocol does my vehicle use?
As a rule of thumb, GM cars and light trucks use SAE J1850 VPW (Variable Pulse Width Modulation). Chrysler products and all European and most Asian imports use ISO 9141 circuitry. Fords use SAE J1850 PWM (Pulse Width Modulation) communication patterns.
There are some variations among captive imports such as the Cadillac Catera, a German Opel derivative, which uses the European ISO 9141 protocol.

On 1996 and later vehicles, you can tell which protocol is used by examining the OBD II connector:

J1850 VPW--The connector should have metallic contacts in pins 2, 4, 5, and 16, but not 10.
ISO 9141-2--The connector should have metallic contacts in pins 4, 5, 7, 15, and 16.
J1850 PWM--The connector should have metallic contacts in pins 2, 4, 5, 10, and 16.

n Install supplied or other software on computer

nTurn the vehicle ignition off

n Locate the 16-pin Data Link Connector and plug the cable into the connector

n Turn the ignition on (needn't start the engine) and press enter

n The scanner will now search for the specific protocol for your vehicle

n Follow On-Screen Prompts and Menus!

Download application Torque for your android phone to use the product in your car with your phone. Get the app free from your app store on your phone.