Buyer Note:

OBD EOBD JOBD EOBD2 OBD II compliant

In 1996 in the United States, a Federal Law came into force requiring all US-sold cars to be OBD2 compliant. Most OBD2 tools are therefore advertised as working with all cars from 1996.

The OBD2 Federal Law applied only to cars sold in the US.

In the UK and the rest of Europe, our equivalent law (European On-Board Diagnostics, or EOBD) did not come into force, and more importantly, was not fully implemented by our car manufacturers, until 2001 for petrol cars (2003/4 for diesels).

Due to this it is difficult to know exactly what European vehicles are OBD2 compliant before the above dates and we recommend checking with your dealer before purchasing equipment for cars manufactured before 2001 Petrol and 2004 Diesel.

Even where a seemingly identical car may have been sold in Europe and the US before 2001, from our own testing and research, it is rarely the case that the European model will be OBD2 / EOBD compliant.
Please Confirm OBD II compliant Car ,then BID
 
OBD II Pc interface cable.

Supports all legislated OBD protocols:

ISO15765-4 (CAN)

  • ISO14230-4 (Keyword Protocol 2000)

  • ISO9141-2 (Asian, European, Chrysler vehicles)

  • J1850 VPW (GM vehicles)

  • J1850 PWM (Ford vehicles)

Introduction

If your car's Check Engine Light is on, you need this device.  interface is a pc device for reading and erasing trouble code in  your vehicles. It can also display live data for your vehicle., competitive in price and easy to use.

 

Features:
The program lets you perform the following operations:

Read diagnostic trouble codes, both generic and manufacturer-specific, and 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
• 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...
 
Upcoming Features:
• Data graphing and logging
• Freeze Frame data
• Continuous and Non.

Applications

Even if you don't repair the vehicle yourself, knowing the Diagnostic Trouble Code number before taking the vehicle in for repair the less likely you will be ripped off. Once the vehicle is repaired, the Diagnostic Trouble Code(s) can be erased and the Check Engine light extinguished using this scan tool.

In area that requires 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 extinguishes 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. Since our scanner is a portable device, the buyer, can connect the scan tool to the vehicle and in a few seconds determine if the vehicle has detected a problem. Remember, not all Diagnostic Trouble Codes illuminate the Check Engine light and a scan tool are the only way to obtain the information.

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 as shown below, 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 I have three different OBD II communications protocols in use.

The big scanner consoles costing thousands of dollars include the decoding software and firmware for all three protocols in their units, making them universal. Less expensive units, for home or small shop use, are usually customized for a specific communications protocol. Be sure the scanner you are using suits the protocol of your car.

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.

If your vehicle has this style connector, but doesn't have these pins populated, you probably have a pre-OBDII vehicle. To add some confusion, even having the connector with the contacts shown above is not a guarantee of OBD II compliance. This style connector has been seen on some pre-1996 vehicles which were not OBD II compliant.

Payment : PAYPAL only
Shipping : AIRMAIL need 7-14 Work days.

Warranty ,1 year,  30 days return  item ,full refund.