Right-Angle OBD2 16Pin to DB9 Serial Port Adapter Cable
Free Shipping Within The United States!
This adapter cable is compatible with all OBD II compliant vehicles. All 1996 and newer vehicles (cars and light trucks) sold in the United States must be OBD II compliant and this includes all domestic, Asian and European vehicles.
A few of 1994 and 1995 model year gasoline vehicles are OBD II compliant. Please check the Vehicle Emissions Control Information (VECI) Label which is located under the hood or by the radiator of most vehicles. If the vehicle is OBD II compliant, the label will designate "OBD II Certified". Additionally, Government regulations mandate that all OBD II compliant vehicles must have a 16-pin Data Link Connector (DLC).
If your vehicle is OBD II compliant, it must have a 16-pin DLC under the dashboard, and the Vehicle Emission Control Information Label located on the inside of the hood on most vehicles must state that the vehicle is OBD II compliant.
- High quality OBD2 to DB9 serial port adapter cable
- For connecting your diagnostic interface and your vehicle with OBD Ⅱ compliant
- Length: About 100 cm / 3 ft.
- OBD Ⅱ Plug: 16-pin male to car
- 9-pin DB9 female to your diagnostic interface
|OBD II 16 Pin Connector||DB9 Connector|
|Chassis Ground||4||1, 2|
|Signal Ground||5||1, 2|
|CAN High J-2284||6||3|
|CAN Low J-2284||14||5|
|ISO 9141-2 K Line||7||4|
|ISO 9141-2 L Line||15||8|
The cable is also directly compatible with our PiCAN2 and PiCAN2 with SMPS (Switch Mode Power Supply), the CAN Bus interface boards for the Raspberry Pi. However, before using the cable with the SMPS version, please assure that the J1939 Battery voltage does not exceed 12 VDC. Otherwise, you may destroy the board.
The OBD-II standard specifies the type of diagnostic connector and its pinout, the electrical signalling protocols available, and the messaging format. It also provides a candidate list of vehicle parameters to monitor along with how to encode the data for each. There is a pin in the connector that provides power for the scan tool from the vehicle battery, which eliminates the need to connect a scan tool to a power source separately. However, some technicians might still connect the scan tool to an auxiliary power source to protect data in the unusual event that a vehicle experiences a loss of electrical power due to a malfunction. Finally, the OBD-II standard provides an extensible list of DTCs. As a result of this standardization, a single device can query the on-board computer(s) in any vehicle. This OBD-II came in two models OBD-IIA and OBD-IIB. OBD-II standardization was prompted by emissions requirements, and though only emission-related codes and data are required to be transmitted through it, most manufacturers have made the OBD-II Data Link Connector the only one in the vehicle through which all systems are diagnosed and programmed. OBD-II Diagnostic Trouble Codes are 4-digit, preceded by a letter: P for engine and transmission (powertrain), B for body, C for chassis, and U for network.
Automotive Diagnostic Systems: Understanding OBD-I & OBD-II
For more than 30 years, cars and trucks have carried onboard diagnostics (OBD), which monitor and adjust major systems, including engine, drivetrain, fuel, and more. Many think that repairing or tuning the current system (OBD- II) is a black art or a computer science, and that there is no way to diagnose and fix computer control-system problems at home with affordable tools. But, that is simply not true.
OBD expert, tuner, and author Keith McCord explains system architecture, function, and operation. He shows you how to use a hand-held scanner, connect it to the port connector in the car, and interpret the data. But most importantly, he shows you a practical, analytical, and methodical process for tackling a problem, so you can quickly trace its actual source and fix the root cause and not just the symptom. Automotive Diagnostic Systems includes definitions of diagnostic trouble codes and a table of common DTCs.
McCord reveals the intricacies of diagnosing the system, the importance of fixing component DTCs first, one- and two-trip codes, how the PCM erases DTCs, and how you can have DTCs stored in memory with no MIL on, among many other common issues. As a result, you learn how to resolve a range of common OBD-II problems, such as engine misfires, shorts and opens, out-of-tune fuel trims, dead catalysts, emissions leaks, low voltages, failed oxygen sensors, and much more. But it also covers fuel injectors, ignition systems, chassis sensors, and various other sensors and actuators.