Brand New OBD II OBD2 Check Engine Code Reader

Vehicle Coverage

Fit 1996+ ALL OBD-II Car ( include CAN)

Introduction

If your car's Check Engine Light is on, you need this device. Code reader is a handy device for reading and erasing trouble code in  your vehicles. It can also display live data for your vehicle. It is small in size, robust in design, competitive in price and easy to use. This is a stand alone unit, it does not need a laptop computer to operate.

By simply connecting code reader with the diagnostic socket, the user will be able to read the trouble code. The trouble code description will be displayed directly on the screen, no need for search it in the user's manual. Each code will be continuously displayed until the [PREVIOUS] or [NEXT] key is pressed. This is a important advantage to compare with the old type trouble code reading tools.

This item can support all OBD2 protocols,

Features

• With large LCD display: the trouble code description will be displayed directly on the screen, no need for search it in the user's manual

• Each code will be continuously displayed until the [↑] or [↓] key is pressed. This is an important advantage to compare with the old type trouble code reading tools

• With extension cable, comfortable for operation

• With live data or data stream function

• Support all OBD2 protocols: OBD-I, OBD-II, EOBD, JOBD, and CAN-BUS

• With professional mode

• With large DTC database

• Powered via diagnostic connector, no additional power is needed

• Plug and play, ease to use

• Turn off check engine light

• High reliable and accurate

Main Functions

• Display DTC descriptions in text mode

• Read DTC

• Erase DTC

• Data Stream

• Freeze Frame Data

• Oxygen Sensor Test

• On Board Monitor

• Request Control Test

• ECU Information

Some of the systems the U381 will monitor

• Misfire
• Fuel System
• Comprehensive components (ccm)
• EGR System
• Oxygen sensor
• Catalyst
• Evaporative
• O2 Sensor heater
• Secondary air
• Heated Catalyst
• A/C System
• many more...

Specifications

• Port: 16-pin OBD II socket

• Display: LCD

• Power: Directly supplied by diagnostic socket

• Protocol: OBD-I, OBD-II, EOBD, JOBD, and CAN-BUS

Package Includes

• One scanner with 16PIN Extension Cable

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.