obd2 pin assignments

OBD 2 Pinout Explained

On-Board Diagnostics II, or OBD2, is a self-diagnostic and reporting system in modern vehicles. It consists of an Electronic Control Unit, several sensors, and indicator lights. The sensors inspect the various subsystems within the vehicle and report any faults and abnormalities to the ECU.

Of course, simply reporting faults would be pointless if there was no way to read the errors and act on them. Hence, the ECU generates Diagnostic Trouble Codes and stores them for inspection by external OBD scanners . These codes are accessed through an OBD2 connector plugged into the 16-pin OBD port.

Consequently, repair technicians can analyze the error codes using a scan tool attached to the other end of the connector.

Are you confused by the various terminology thrown about? Read on to learn what an OBD2 connector is and its purpose in your vehicle.

What is the OBD2 Connector for?

The OBD2 connector is one end of the adapter cable plugged into your vehicle’s OBD port . It is a communication interface that allows you to transmit information between a diagnostic scan tool and the vehicle’s OBD2 system.

OBD2 connectors come in two flavors; wired and wireless. As the name suggests, the wired connector must be physically attached to the scan tool through the cable. On the other hand, wireless OBD2 connectors interface with the scan tool using Bluetooth or WiFi.

The OBD2 connector is designed to read and translate real-time diagnostic information from the Electronic Control Unit (ECU). As such, you can tell what is wrong with the vehicles from the error codes received through the connector. Furthermore, it allows you to use scan tools to reprogram and repair the various subsystems within the vehicle. Recently, remote diagnostic systems have become increasingly popular.

OBD2 Port Pinout Types

There are two major types of OBD2 connectors. Type A connectors have a 12V output voltage and are commonly found in small vehicles such as cars. However, type B connectors are usually found in medium-sized and heavy vehicles. Moreover, they have an output power supply of 24V.

Baud rate is the rate of information transfer in serial communication channels. A rate of 24,000 bauds means the port can transfer up to 24,000 bits per second. Type A connectors have an approximate baud rate of 500,000 bauds, while type B connectors have a maximum baud rate of 250,000.

The higher the baud rate, the shorter the length of the adapter cable. As such, it is not uncommon to find type B connectors with longer cables than type A connectors. Nevertheless, you should note that this is not a reliable method of distinguishing between the two cable types.

OBD2 Pinout Explanation

OBD2 connectors are typically 16-pin ports, each pin serving a distinct purpose. Some pins use standard protocols defined by the Society of Automotive Engineers and the International Organization for Standardization. Other pins are left to the manufacturer’s discretion.

The table below gives a quick overview of each pin in a generic OBD2 connector.

Each of these pins is explained in-depth below.

SAE J1850 PWM (Pulse Width Modulation)

• Bus positive pin (2) and bus negative pin (10) of the protocol.
• It uses variable pulse width modulation at 41.6 kb/s.
• It is common in Ford vehicles.
• Pulse Width Modulation changes the analog signal to digital in a square wave.

Controller Area Network (CAN)

• It is a network of independent controllers.
• It is headless; no host computer.
• It uses a bus communication protocol.

SAE J1850 VPW

• Commonly used in General Motors vehicles
• It operates variable pulse width at 10.4 kb/s.
• Pins 2, 4, 5, and 16 have SAE J1850 VPW.
• General Motors developed the Variable Pulse Width encoding method.
• VPW is better than the PWM scheme.
• It is an old protocol
• Mostly used in European vehicles, some Asian vehicles, and Chrysler.
• It uses asynchronous serial communication at 0.4 kb/s.
• It is optional on pins 7 and 15 (pins 4, 5, and 16 are must-haves).
• This protocol represents voltage logic in 0 or 1 form. Logic 0 represents low voltage and Logic 1 represents high voltage. Each bit of information is 96 us long.

ISO 14230 KWP2000

• It operates at 10.4 kb/s and is used for serial asynchronous communication.
• This protocol is most common in Europe and Chrysler vehicles.
• This protocol is used in Asian vehicles having pin 7 K-line.
• It is optional in pin 15.
• KWP is Keyword Protocol. It is a communication protocol that is applied to the OBD system.

ISO 15765-4 CAN (SAE J2480)

• ISO 15765-4 CAN is available in vehicles built in 2008 or later in the US.
• Pins 4, 5, 6, 14, and 16 support this protocol.
• OBD2 protocol consists of 4 variants.
• It works on a 2-wire communication method.
• It can handle up to 1 Mbps.

Main Car Manufacturers OBD2 Connector Pinouts

OBD2 ports are standardized to work with any commercially available scan tool. However, several pins, including 1, 3, 8, and 9 are not required for standard communication. As a result, vehicle manufacturers encode these pins to transmit information specific to each vehicle's make and model.

Furthermore, the standardized pins encode different types of data to be decrypted by the scan tool. Finding specific information about each vehicle manufacturer can be difficult and confusing. Luckily, we have compiled a spreadsheet of the OBD2 pinouts of some popular car manufacturers. Simply click on the name of the brand you're interested in to see its OBD2 pin layout.

Audi OBD2 connector pinout

Acura OBD2 connector pinout

BMW OBD2 connector pinout

Crysler OBD2 connector pinout

Ford OBD2 connector pinout

GM OBD2 connector pinout

Honda OBD2 connector pinout

Hyundai OBD2 connector pinout

Infinity OBD2 connector pinout

KIA OBD2 connector pinout

Lexus OBD2 connector pinout

Mazda OBD2 connector pinout

Mercedes Benz OBD2 connector pinout

Mitsubishi OBD2 connector pinout

Nissan OBD2 connector pinout

Renault OBD2 connector pinout

Subaru OBD2 connector pinout

Toyota OBD2 connector pinout

Volkswagen OBD2 connector pinout

Volvo OBD2 connector pinout

• 4.8 overall rank based on 386 + Reviews
• Requirements: Windows, macOS, Linux, Android and Raspberry Pi.
• 10.45MB Size.
• Version 6.1.15025 . ( 19 Feb, 2024 ).
• Pricing starts $14 per month billed annually
• USB over network
• Remote Vehicle Diagnostics
• OBD2 pinout

OBD2 Connector Pinout, Types & Codes(Explained)

Last updated on March 23rd, 2024 at 11:01 am

OBD2 is an onboard diagnostic system present in cars that collect data from a vehicle. To collect this data, the cars must have an OBD port installed in them. Using an OBD connecter, a technician may collect this data and analyze the errors in the car. But, to see how all of this works, let us first understand what an OBD port and connector is.

Table of Contents

What is an obd2 port.

It is a 16-pin OBD port present in your car that is used by the technician to find faults in the car. The technician connects an OBD2 connector to this port that converts the error data into readable format. This error data is gathered by the OBD2 system installed in the car.

What is an OBD2 connector?

The OBD2 connector is one end of the OBD2 cable that goes to the OBD2 port of the car. The other end of the cable connects to the OBD2 scanner . This way the OBD2 adaptor cable reads the error codes from the OBD2 system and displays them on the scanner.

Sometimes this OBD2 connector comes attached to a Bluetooth scanner. Using this Bluetooth scanner, you can check data wirelessly from a laptop, mobile, etc.

It is used to get real-time data information and onboard diagnostics results. Each manufacturer uses its own OBD-II Diagnostic Link Connector (DLC) which is the main connector through which all subsystems are tuned, reprogrammed & diagnosed.

OBD2 connector pinout

OBD connector has 16 pins in a trapezoidal shape. The following diagram shows the picture of an OBD2 connector pinout.

The table below describes each pin:

What are the types of OBD2 connectors?

There are two types of OBD2 connectors used in a vehicle, i.e., Type A and Type B.

Type A vs. Type B

• Type A is commonly found in cards, while Type B is common in heavy & medium vehicles.
• Both A & B types have similar OBD2 pinouts, but the output power supply is different: 12V for type A and 24V for type B.
• There is a difference in the Baud Rate. The cars use approximately 500K, while most heavy-duty vehicles use 250K.

Now let’s discuss these pins in a bit more detail.

SAE J1850 PWM

• SAE J1850 PWM protocol with connector pins 2 & 10.
• It produces a signal by pulse width modulation. It performs at the speed of 41.6 kb/sec and is mostly found in Ford vehicles.
• Pins 2, 4, 5, 10, and 16 should be of this type.
• PWM stands for Pulse Width Modulation. In PWM, an analog signal is changed into a digital signal in a different wave-like square wave.

SAE J1850 VPW

• For GM vehicles, SAE J1850 VPW is commonly used.
• It operates at a speed of 10.4 kb/sec by the variable pulse width.
• Pins 2, 4, 5, and 16 have SAE J1850 VPM. At pin no. 10 there is a difference between VPW and PWM is that this OBD2 protocol.
• VPM-It was developed by General Motors and it is an encoding method. It stands for Variable Pulse Width and its signal rate is 10.4 Kbps.
• VPM is more beneficial than the PWM scheme.
• Old protocol
• Mostly used in European vehicles. Also in some Asian vehicles & in Chrysler.
• Its running speed is 10.4 kb/sec and it uses serial communication asynchronously.
• It is optional pins 7& 15 (pins 4, 5, and 16 are must-haves).
• ISO stands for International Organization for Standardization. This protocol represents voltage in a logic 0 or 1 form. Logic 0 represents low voltage and logic 1 represents high voltage. In this, each bit of information is 96 us long.

ISO 14230 KWP2000

• It operates at 10.4 kb/s. It is used for serial asynchronous communication.
• This protocol is most common in Europe and commonly in Chrysler. This protocol used in Asian vehicles having pin 7 Kline & pin 15 is optional.
• KWP is Keyword Protocol. It is used for communication protocol which is applied on the OBD system.

ISO 15765-4 CAN (SAE J2480)

• ISO 15765-4 CAN is available in vehicles that were built in 2008 or later in the US.
• Pins 4, 5, 6, 14, and 16 support this protocol.
• OBD2 protocol consists of 4 variants.
• It works on a 2-wire communication method.
• It can handle up to 1 Mbps.

CAN – stands for controller area network

• It refers to a network of independent controllers.
• The communication happens without a host computer.
• It uses a broadcast type of bus communication protocol.

What is an OBD2 code?

Whenever a problem is detected in a vehicle using the OBD, the system shows it as an error code. This code is called a Diagnostic Trouble Code (DTC).

If we try to interpret it, we can understand the cause of the problem. For example , a car shows the P0200 code, which means that there is a possible injector circuit issue. Now, this error can be pinpointed & can be fixed before the actual breakdown.

How to read OBD2 DTC codes?

OBD provides diagnoses for various systems such as powertrain, chassis, body, etc. By careful reading the letters & numbers, a fault can be found & fixed easily. Here the code is simplified as follows:

The first character

It is a letter that denotes the vehicle’s part that has a fault.

P  – Powertrain.

• It includes the vehicle’s engine, transmission, and other associated accessories.

U  – Network & Vehicle Integration

• It is managed by an onboard computer system.
• Parts are usually found in the compartment area of passengers in the vehicle.

C  – Chassis.

• Consists of mechanical functions & systems example, braking, steering, and suspension.

The second character

It is a number that can be ‘0’, ‘1’, ‘2’, or ‘3’.

‘0’, ‘2’, or ‘3’

• standardized (SAE) code or generic code
• Manufacturer specific code

The third character

It is a number or a letter that shows the system in the vehicle that has a fault.

0  – Emission controls: fuel and air metering

1  – Fuel & air metering

2  – Injector circuit: Fuel & air metering

3  – Ignition systems/misfiring

4  – Auxiliary emission control system

5  – Speed Control & idle control systems

6  – Computer and output circuit system

7  – Transmission system

A-F  – Hybrid codes

Final: The fourth and fifth character

It is a two-digit number that defines the exact problem & can be any number between 0 and 99.

Where is the OBD2 port located in a car?

Since OBD port or diagnostic port location varies from manufacturer to manufacturer, it is usually found on the driver’s side under the dashboard. In some vehicles, it can be found near the center console section in a vehicle. In old models, this port can be found near the handbrake or in the trunk.

Once this port is found, we can easily plug the reader which establishes a connection between the vehicle and the diagnostic device.

Best OBD2 connector- our recommendation

2 thoughts on “OBD2 Connector Pinout, Types & Codes(Explained)”

Absolutely great post!

Very straightforward and helpful!

I’m considering buying the obd2 scanner. Your post helped me a lot.

Thanks for sharing.

Can I charge the battery through the OBD connection? ,I think pin 16

Leave a Comment Cancel reply

Continue to site >>>

ODB-II Connector

[Click the image to enlarge it]

OBD2 Connector Pinout Configuration

What is an obd-ii connector.

OBD stands for Onboard Built-in Diagnosis . As the name suggests it is a diagnosis system that is built into all modern cars (after 1996) which has a computer based application that monitors the performance of your car through your speed, mileage, fuel emission data etc.. Apart from this it also measures some of the important vital parameters of an Engine. This complete system is called as an ECU ( Engine Control Unit ).

This OBD connector is meant to be used only by the service guy to monitor the health of your Car and provide diagnosis. Apart from this it is also controls the warning lights on your Cars dashboard. 

How to use the OBD-II Connector with Arduino/Raspberry Pi?

It is a federal law to modify or tamper with the OBD system of your car, but if your engine failure light has gone in your Car and you want to diagnose the problem by yourself then it is pretty much easy to use connectors like ODB-II to connect between your Car and a microcontroller or microprocessor. Once you get all the vital details of your car into a development platform like Arduino or Raspberry Pi then the application is limitless.

The OBD port can found on the dashboard near the steering wheel of every car. The position of the port varies based on the manufacturer and is normally hidden in a blind spot for aesthetic reasons. Once you find the port hook up the connector and connect the other end to STN1110 OBD UART board. Then the UART board is connected to a computer where the communication takes place through the Tx, Rx and Ground pins and normal data type will be with 9600 baud rate in which there will be 8-data bits and 1 stop bit with no parity. We can then use any serial communication software like putty or even Arduino to speak with the car though AT commands. Each AT command has a specific task to perform or returns a specific value. You can learn more about interfacing through the sparkfun hookup tutorial which explains how the connection should be made and initiated.

Related Post

Are you 18 come in and don't be shy, join 20k+subscribers.

We will never spam you.

Be a part of our ever growing community.

Capable of supporting up to 32 GT/s without altering design

3M™ TwinAx High Speed Cable Solutions: Thin, low profile cable with extremely tight bend radii

Advantech's WISE-750 vibration PHM gateway is developed to perform predictive maintenance.

Industrial plating option with enhanced durability for a variety of harsh environments

ECS-3215MV-327KE compact 32.768 kHz MultiVolt oscillators offers low 1.3 µA current consumption.

Hammond’s modern 1556 series enclosures are designed for circuit boards and IoT equipment

Optimized with highly sensitive cap touch sensors, extensive peripheral circuits and 125℃ operation

KEMET's automotive PCB-mount relays unique structure offers high performance and productivity

OBD II Connector Pinout Diagrams

Determine which ecm protocol your car has with these obd ii connector pinout diagrams.

OBDII compliant vehicles can use up to five different protocols and multiple OBDII connector pinout variations.

• SAE J1850 PWM • SAE J1850 VPW • ISO9141-2, • ISO14230-4 (KWP2000), and • ISO 15765-4/SAE J2480

Each protocol has some required pins and some optional pins. So you can tell which protocol your vehicle has by looking at the diagrams below.

ISO15765-4 (CAN-BUS) is mandatory for all 2008 and later vehicles sold in the US. This protocol uses pins 6 and 14. There are four variants of ISO15765 however and they can sometimes be confused as different protocols. They’re not; they’re just variations of ISO15765-4 and differ only in identifier length and their bus speeds

• ISO 15765-4 CAN (11 bit ID,500 K baud)
• ISO 15765-4 CAN (29 bit ID,500 K baud)
• ISO 15765-4 CAN (11 bit ID,250 K baud)
• ISO 15765-4 CAN (29 bit ID,250 K baud)

Let’s start with an overview of the connector

Overview of the OBDII Connector Pinout Diagram

SAE J1850 PWM OBDII Connector Pinout Diagram

This protocol was used mostly on Ford vehicles. It uses pins 1 and 2. The communication signal is differential and it’s bit rate is 41.6kB/sec.

SAE J1850 PWM protocol MUST have pins 2 and 10

J1850 VPW OBDII Connector  Diagram

This protocol was used mostly on GM vehicles. It uses pin 1. The communication bit rate is 10.4 kB/sec

J1850 VPW protocol MUST have pin 2

ISO9141/14230 Connector Diagram

This older protocol was used on European vehicles between 2000 and 2004. It uses uses pin 7 and optionally 15.

ISO9141/14230 must have pin 7 and may or may not have pin 15. This is an option for the carmaker

ISO15765 (CAN) OBDII Connector Pinout Diagram

ISO15765-4 (CAN-BUS) is mandatory for all 2008 and later vehicles sold in the US. This protocol uses pins 6 and 14. There are four variants of ISO15765 however and they can sometimes be confused as different protocols. They’re not; they’re just variations opf ISO15765-4 and differ only in identifier length and their bus speeds

ISO15765 (CAN) must have pins 6 and 14

©, 2022 Rick Muscoplat

• OBD II Information

Your shopping cart is empty!

• Documentation - Technical Resources

OBD-II J1962 Connector Pinout

Sae j1962 (obd-ii) type "a" connector (12v), sae j1962 (obd-ii) type "b" connector (24v), information.

• Delivery Information
• Privacy Policy
• Terms & Conditions

Customer Service

• Gift Vouchers
• Order History

Powered By OpenCart DashLogic © 2024

Just added to your cart

Obd2 explained - a simple intro [2023].

Need a simple, practical intro to OBD2?

In this guide we introduce the On Board Diagnostic (OBD2) protocol incl. the OBD2 connector, OBD2 parameter IDs (PID) and the link to CAN bus.

Note: This is a practical intro so you will also learn how to request and decode OBD2 data, key logging use cases and practical tips.

Learn below why this has become the #1 OBD2 tutorial .

You can also watch our OBD2 intro video above - or get the PDF

In this article

What is obd2, the obd2 connector.

• OBD2 vs CAN bus
• History & future
• PIDs & raw frames

How to log OBD2 data?

• OBD2 logging use case examples

In short, OBD2 is your vehicle's built-in self-diagnostic system.

You've probably encountered OBD2 already:

Ever noticed the malfunction indicator light on your dashboard?

That is your car telling you there is an issue. If you visit a mechanic, he will use an OBD2 scanner to diagnose the issue.

To do so, he will connect the OBD2 reader to the OBD2 16 pin connector near the steering wheel.

This lets him read OBD2 codes aka Diagnostic Trouble Codes (DTCs) to review and troubleshoot the issue.

The OBD2 connector lets you access data from your car easily. The standard SAE J1962 specifies two female OBD2 16-pin connector types (A & B).

In the illustration is an example of a Type A OBD2 pin connector (also sometimes referred to as the Data Link Connector, DLC).

A few things to note:

• The OBD2 connector is near your steering wheel, but may be hidden behind covers/panels
• Pin 16 supplies battery power (often while the ignition is off)
• The OBD2 pinout depends on the communication protocol
• The most common protocol is CAN (via ISO 15765), meaning that pins 6 (CAN-H) and 14 (CAN-L) will typically be connected

OBD2 connector - type A vs. B

In practice, you may encounter both the type A and type B OBD2 connector. Typically, type A will be found in cars, while type B is common in medium and heavy duty vehicles.

As evident from the illustration, the two types share similar OBD2 pinouts, but provide two different power supply outputs (12V for type A and 24V for type B). Often the baud rate will differ as well, with cars typically using 500K, while most heavy duty vehicles use 250K (more recently with support for 500K).

To help physically distinguish between the two types of OBD2 sockets, note that the type B OBD2 connector has an interrupted groove in the middle. As a result, a type B OBD2 adapter cable will be compatible with both types A and B, while a type A will not fit into a type B socket.

Does my car have OBD2?

In short: Probably!

Almost all newer cars support OBD2 and most run on CAN (ISO 15765). For older cars, be aware that even if a 16 pin OBD2 connector is present, it may still not support OBD2 . One way to determine compliance is to identify where & when it was bought new :

Link between OBD2 and CAN bus

On board diagnostics, OBD2, is a ' higher layer protocol ' (like a language). CAN is a method for communication (like a phone).

In particular, the OBD2 standard specifies the OBD2 connector, incl. a set of five protocols that it can run on (see below). Further, since 2008, CAN bus ( ISO 15765 ) has been the mandatory protocol for OBD2 in all cars sold in the US.

What is the ISO 15765 standard?

ISO 15765 refers to a set of restrictions applied to the CAN standard (which is itself defined in ISO 11898 ). One might say that ISO 15765 is like "CAN for cars" .

In particular, ISO 15765-4 describes the physical, data link layer and network layers, seeking to standardize the CAN bus interface for external test equipment. ISO 15765-2 in turn describes the transport layer (ISO TP) for sending CAN frames with payloads that exceed 8 bytes. This sub standard is also sometimes referred to as Diagnostic Communication over CAN (or DoCAN). See also the 7 layer OSI model illustration.

OBD2 can also be compared to other higher layer protocols (e.g. J1939 , CANopen ).

The five OBD2 protocols

As explained above, CAN bus today serves as the basis for OBD2 communication in the vast majority of cars through ISO 15765.

However, if you're inspecting an older car (pre 2008), it is useful to know the other four protocols that have been used as basis for OBD2. Note also the pinouts, which can be used to determine which protocol may be used in your car.

• ISO 15765 (CAN bus) : Mandatory in US cars since 2008 and is today used in the vast majority of cars
• ISO14230-4 (KWP2000) : The Keyword Protocol 2000 was a common protocol for 2003+ cars in e.g. Asia
• ISO9141-2 : Used in EU, Chrysler & Asian cars in 2000-04
• SAE J1850 (VPW) : Used mostly in older GM cars
• SAE J1850 (PWM) : Used mostly in older Ford cars

Below we list some of the most relevant SAE/ISO standards related to OBD2:

SAE J1962 : This standard defindes the physical connector used for the OBD2 interfacing, i.e. the OBD2 connector. The standard describes both the vehicle OBD2 connector and the connector used by the external test equipment (e.g. an OBD2 scanner or OBD2 data logger). In particular, the standard dictates the location and access to the OBD2 connector.

SAE J1979 : The SAE J1979 standard describes the methods for requesting diagnostic information via the OBD2 protocol. It also includes a list of standardized public OBD2 parameter IDs (OBD2 PIDs) that automotive OEMs may implement in cars (though they are not required to do so). Vehicle OEMs may also decide to implement additional proprietary OBD2 PIDs beyond those outlined by the SAE J1979 standard.

SAE J1939 : The J1939 standard describes the data protocol used for heavy-duty vehicle communication. While OBD2 PID information is only available on-request by OBD2 test equipment, the J1939 protocol is used in most heavy-duty vehicles as the basic means for communicating CAN traffic - meaning data is broadcast continuously.

ISO 11898 : This standard describes the CAN bus data link layer and physical layer, serving as the basis for OBD2 communication in most cars today

ISO 15765-2 : The ISO-TP standard describes the 'Transport Layer', i.e. how to send data packets exceeding 8 bytes via CAN bus. This standard is important as it forms the basis for Unified Diagnostic Services (UDS) communication, which relies on sending multiframe CAN data packets.

ISO 14229 : This describes UDS communication in detail

It can be useful to compare the OBD2 protocol vs. other request/response protocols on CAN.

In our intro to Unified Diagnostic Services (UDS) we compare UDS vs. OBD2, WWH-OBD and OBDonUDS.

In our intro to CCP/XCP on CAN we compare the CAN Calibration Protocol (CCP) and the Universal Measurement and Calibration Protocol (XCP) on CAN vs. UDS.

OBD2 is generally focused on emission control, while UDS is focused on diagnostics and read/write access to ECUs - primarily for production-stage vehicles. CCP and XCP are focused on measurement and calibration of ECUs within prototype vehicle ECUs and they are less oriented towards diagnostics.

OBD2 history

OBD2 originates from California where the California Air Resources Board (CARB) required OBD in all new cars from 1991+ for emission control purposes.

The OBD2 standard was recommended by the Society of Automotive Engineers (SAE) and standardized DTCs and the OBD connector across manufacturers ( SAE J1962 ).

From there, the OBD2 standard was rolled out step-by-step :

• 1996: OBD2 made mandatory in USA for cars / light trucks
• 2001: Required in EU for gasoline cars
• 2003: Required in EU also for diesel cars (EOBD)
• 2005: OBD2 was required in US for medium duty vehicles
• 2008: US cars must use ISO 15765-4 (CAN) as OBD2 basis
• 2010: Finally, OBD2 was required in US heavy duty vehicles

OBD2 future

OBD2 is here to stay - but in what form?

Two potential routes may radically change OBD2:

In today's world of connected cars, OBD2 tests can seem cumbersome: Manually doing emission control checks is time-consuming and expensive.

The solution? OBD3 - adding telematics to all cars .

Basically, OBD3 adds a small radio transponder (as in e.g. bridge tolls) to all cars. Using this, the car vehicle identification number (VIN) and DTCs can be sent via WiFi to a central server for checks.

Many devices today already facilitate transfer of CAN or OBD2 data via WiFi/cellular - e.g. the CANedge2 WiFi CAN logger.

This saves cost and is convenient, but it is also politically a challenge due to surveillance concerns.

The OBD2 protocol was originally designed for stationary emission controls.

Yet, today OBD2 is used extensively for generating real-time data by 3rd parties - via OBD2 dongles , CAN loggers etc. However, the German car industry is looking to change this :

OBD has been designed to service cars in repair shops. In no way has it been intended to allow third parties to build a form of data-driven economy on the access through this interface "

- Christoph Grote, SVP Electronics, BMW (2017)

The proposal is to "turn off" the OBD2 functionality while driving - and instead collect the data in a central server. This would effectively put the manufacturers in control of the ' automotive big data '.

The argumentation is based in security (e.g. removing the risk of car hacking ), though many see it as a commercial move . Whether this becomes a real trend is to be seen - but it may truly disrupt the market for OBD2 3rd party services.

OBD2 parameter IDs (PID)

Why should you care about OBD2 data?

Mechanics obviously care about OBD2 DTCs (maybe you do too), while regulatory entities need OBD2 to control emission.

But the OBD2 protocol also supports a broad range of standard parameter IDs (PIDs) that can be logged across most cars.

This means that you can easily get human-readable OBD2 data from your car on speed, RPM, throttle position and more.

In other words, OBD2 lets you analyze data from you car easily - in contrast to the OEM specific proprietary raw CAN data.

In principle it is simple to log the raw CAN frames from your car. If you e.g. connect a CAN logger to the OBD2 connector, you'll start logging broadcasted CAN bus data out-the-box. However, the raw CAN messages need to be decoded via a database of conversion rules (DBC) and a suitable CAN software that supports DBC decoding (like e.g. asammdf ). The challenge is that these CAN DBC files are typically proprietary, making the raw CAN data unreadable unless you're the automotive OEM.

Car hackers may try to reverse engineer the rules, though this can be difficult. CAN is, however, still the only method to get "full access" to your car data - while OBD2 only provides access to a limited subset of data.

OBD2 data logging works as follows:

• You connect an OBD2 logger to the OBD2 connector
• Using the tool, you send 'request frames' via CAN
• The relevant ECUs send 'response frames' via CAN
• Decode the raw OBD2 responses via e.g. an OBD2 DBC

In other words, a CAN logger that is able to transmit custom CAN frames can also be used as an OBD2 logger.

Note that cars differ by model/year in what OBD2 PIDs they support. For details, see our OBD2 data logger guide.

CANedge OBD2 data logger

The CANedge lets you easily log OBD2 data to an 8-32 GB SD card. Simply specify what OBD2 PIDs you wish to request, then connect it to your car via an OBD2 adapter to start logging. Process the data via free software/APIs and our OBD2 DBC .

Raw OBD2 frame details

To get started recording OBD2 data, it is helpful to understand the basics of the raw OBD2 message structure. In simplified terms, an OBD2 message is comprised of an identifier and data . Further, the data is split in Mode, PID and data bytes (A, B, C, D) as below.

Identifier: For OBD2 messages, the identifier is standard 11-bit and used to distinguish between "request messages" (ID 7DF) and "response messages" (ID 7E8 to 7EF). Note that 7E8 will typically be where the main engine or ECU responds at.

Length: This simply reflects the length in number of bytes of the remaining data (03 to 06). For the Vehicle Speed example, it is 02 for the request (since only 01 and 0D follow), while for the response it is 03 as both 41, 0D and 32 follow.

Mode: For requests, this will be between 01-0A. For responses the 0 is replaced by 4 (i.e. 41, 42, … , 4A). There are 10 modes as described in the SAE J1979 OBD2 standard. Mode 1 shows Current Data and is e.g. used for looking at real-time vehicle speed, RPM etc. Other modes are used to e.g. show or clear stored diagnostic trouble codes and show freeze frame data.

PID: For each mode, a list of standard OBD2 PIDs exist - e.g. in Mode 01, PID 0D is Vehicle Speed. For the full list, check out our OBD2 PID overview . Each PID has a description and some have a specified min/max and conversion formula.

The formula for speed is e.g. simply A, meaning that the A data byte (which is in HEX) is converted to decimal to get the km/h converted value (i.e. 32 becomes 50 km/h above). For e.g. RPM (PID 0C), the formula is (256*A + B) / 4.

A, B, C, D: These are the data bytes in HEX, which need to be converted to decimal form before they are used in the PID formula calculations. Note that the last data byte (after Dh) is not used.

OBD2 request/response example

An example of a request/response CAN message for the PID 'Vehicle Speed' with a value of 50 km/h can be seen in the illustration.

Note in particular how the formula for the OBD2 PID 0D (Vehicle Speed) simply involves taking the 4th byte (0x32) and converting it to decimal form (50).

In some vehicles (e.g. vans and light/medium/heavy duty vehicles), you may find that the raw CAN data uses extended 29-bit CAN identifiers instead of 11-bit CAN identifiers.

In this case, you will typically need to modify the OBD2 PID requests to use the CAN ID 18DB33F1 instead of 7DF. The data payload structure is kept identical to the examples for 11-bit CAN IDs.

If the vehicle responds to the requests, you'll typically see responses with CAN IDs 18DAF100 to 18DAF1FF (in practice, typically 18DAF110 and 18DAF11E). The response identifier is also sometimes shown in the ' J1939 PGN ' form, specifically the PGN 0xDA00 (55808), which in the J1939-71 standard is marked as 'Reserved for ISO 15765-2'.

We provide an OBD2 DBC file for both the 11-bit and 29-bit responses, enabling simple decoding of the data in most CAN software tools.

The 10 OBD2 services (aka modes)

There are 10 OBD2 diagnostic services (or modes) as described in the SAE J1979 OBD2 standard. Mode 1 shows Current Data and is used for looking at real-time parameters like vehicle speed, RPM, throttle position etc. Other modes are e.g. used to show/clear diagnostic trouble codes (DTCs) and show freeze frame data.

Manufacturers do not have to support all diagnostic services - and they may support modes outside these 10 services (i.e. manufacturer specific OBD2 services).

OBD2 data logging - use case examples

OBD2 data from cars and light trucks can be used in various use cases:

Logging data from cars

OBD2 data from cars can e.g. be used to reduce fuel costs, improve driving, test prototype parts and insurance

Real-time car diagnostics

OBD2 interfaces can be used to stream human-readable OBD2 data in real-time, e.g. for diagnosing vehicle issues

Predictive maintenance

Cars and light trucks can be monitored via IoT OBD2 loggers in the cloud to predict and avoid breakdowns

Vehicle blackbox logger

An OBD2 logger can serve as a 'blackbox' for vehicles or equipment, providing data for e.g. disputes or diagnostics

Do you have an OBD2 data logging use case? Reach out for free sparring!

Below we outline the most common OBD2 analyzer categories:

OBD2 scanners: Used as car diagnostic tools in static reading/clearing of DTCs by e.g. mechanics. An OBD2 scan tool is typically used in diagnosing vehicle issues e.g. indicated by an activated MIL. Various types exist and some private persons use low cost variants as simple car code readers for self-diagnosing their car health.

Bluetooth OBD2 dongles: Many OBD2 bluetooth dongles exist, which let you view car data directly on your smartphone via an app. Typically OBDII bluetooth dongles are low cost and easy-to-use, though also limited in terms of their usability outside the bluetooth-to-app visualization purpose. The purpose of an OBD2 bluetooth dongle is typically to monitor personal driving behavior and vehicle health.

OBD2 interfaces: Provide real-time OBD2 data to a PC via USB streaming. OBD2 interfaces are typically used in advanced car diagnostics and OEM vehicle development. Further, CAN interfaces that support OBD2 requests can be useful as part of reverse engineering proprietary CAN bus parameters.

OBD2 loggers: Used to log OBD2 data from a car to an SD card - ideal for e.g. blackbox use cases or prototype field tests by automotive OEMs. As an example, the CANedge1 lets you log CAN bus data, as well as request OBD2 data by sending custom frame requests to the CAN bus.

WiFi OBD2 logger: WiFi OBD2 loggers and WiFi OBD2 dongles enable the automated transfer of OBD2 data via WiFi to a server/cloud. WiFi OBD2 loggers are typically used for OBD2 telematics use cases, where car fleet data needs to be collected automatically and visualized via OBD2 data dashboards. For example, the CANedge2 lets you log CAN/OBD2 data and auto-push it via a WiFi accces point to your own server. The data can be processed in free software tools and e.g. visualized in Grafana dashboards .

3G/4G OBD2 logger: Similar to the WiFi OBD2 loggers, LTE OBD2 loggers let you collect OBD2 data to an SD card and offload it to your own server. But instead of supporting WiFi connectivity, these devices directly connect via 3G/4G - see for example the CANedge3 .

The CANedge3 makes it easy to log OBD2 data to an SD card - and upload it via 3G/4G to your own server (self-hosted or cloud).

For more intros, see our guides section - or download the 'Ultimate Guide' PDF.

Need to log/stream OBD2 data?

Get your OBD2 data logger today!

Recommended for you

OBD2 DATA LOGGER: EASILY LOG & CONVERT OBD2 DATA

CANEDGE2 - PRO CAN IoT LOGGER

CAN BUS INTERFACE: STREAMING OBD2 DATA WITH SAVVYCAN

• Choosing a selection results in a full page refresh.
• Press the space key then arrow keys to make a selection.

Tuned Tech Your car blog

Unlock Your Car’s Secrets: Obd2 Pinouts Explained

Table of contents, key takeaways, obd2 pinout basics, manufacturer discretion pins, specific vehicle pinouts, what are some common obd2 diagnostic trouble codes and what do they indicate, can obd2 scanners be used to diagnose non-engine related issues in a vehicle, are there any risks associated with using aftermarket obd2 scanners or software, how does the obd2 system differ from earlier onboard diagnostics systems, can obd2 data be used to improve fuel efficiency or track driving habits.

The Onboard Diagnostics II (OBD2) pinout is a fundamental aspect of modern vehicle diagnostics. With 16 pins, the OBD2 connector provides a way for mechanics and car enthusiasts to read and interpret data from a vehicle’s engine control unit. While some pins are standardized across all vehicles sold in the US since 1996, others are at the discretion of the manufacturer.

Understanding the OBD2 pinout can help one unlock some of the car’s secrets and diagnose problems that may not be apparent through other means. This article aims to provide a comprehensive overview of the OBD2 pinout and how it can be used for onboard diagnostics. We will cover the basics of OBD2 pinouts, including the standardized pins and their functions, as well as the manufacturer discretion pins and specific vehicle pinouts.

Whether you are a DIY mechanic or just curious about how your car works, this article will provide you with the information needed to understand the OBD2 pinout and how it can be used to diagnose problems with your vehicle.

• OBD2 pinout is essential for vehicle diagnostics and helps diagnose hidden problems.
• Standardized pins for OBD2 connector include 2, 4, 5, 6, 7, 10, 14, 15, 16, while manufacturer discretion pins include 1, 3, 8, 9, 11, 12, 13.
• Pinouts vary between vehicles, and accurate pinout information is crucial for efficient diagnostics.
• Pinout configuration is essential for effective troubleshooting and helps select the appropriate diagnostic tool.

The 16-pin OBD2 connector used for onboard diagnostics in vehicles has standard pins that are consistent across all 1996+ vehicles sold in the US. These standard pins include 2, 4, 5, 6, 7, 10, 14, 15, and 16.

The manufacturer discretion pins, on the other hand, are used for different purposes in different cars. Pin 1 is typically used for a battery positive power pin, while pins 3, 8, 9, 11, 12, and 13 are used for various functions such as chassis ground, signal ground, and manufacturer-specific inputs and outputs.

It is important to note that GM started using the GM-LAN pinout from 2004, and low-speed CAN bus is used for some IC, RFA, and other units in GM vehicles.

Honda, Nissan, BMW, Ford, and GM OBD2 pinouts are provided in the updated list, which also includes ISO 9141 and CAN protocols used in different vehicles.

By understanding the pinout information and protocols used in their vehicle, individuals can unlock their car’s secrets and diagnose any issues that may arise.

Manufacturer discretion pins on OBD2 connectors have varying functions depending on the vehicle make and model, and their usage is determined by the manufacturer. These pins, which include pins 1, 3, 8, 9, 11, 12, and 13, can be used for a variety of purposes such as communication with custom modules, additional sensors, or even diagnostic functions that are specific to the vehicle.

For example, some manufacturers may use pin 1 for communication with the engine control module, while others may use it for communication with the transmission control module. It is important to note that the functions of manufacturer discretion pins are not standardized, and their usage can vary greatly between different vehicles.

Therefore, it is necessary to refer to the specific pinout diagram for a particular make and model to determine the function of each manufacturer discretion pin. Additionally, it is essential to exercise caution when using these pins, as improper usage can lead to damage to the vehicle or its systems.

Different vehicles utilize varying pinouts for their OBD2 connectors, with Honda, Nissan, BMW, Ford, and GM having their own unique pinout configurations. The Honda pinout, for example, has pins 1 and 2 dedicated to communication with the engine control module (ECM), while the Ford pinout uses pin 3 for communication with the powertrain control module (PCM).

The Nissan pinout, on the other hand, uses pin 5 for communication with the airbag module, while the BMW pinout has pin 16 dedicated to communication with the on-board diagnostics (OBD) system. It is essential to understand the specific pinout configuration for a particular vehicle to diagnose and troubleshoot any issues effectively.

The pin descriptions and usage for each pin in the pinouts can be found in the table of contents provided in the article. Understanding the pinout configuration can also help in selecting the appropriate diagnostic tool for the vehicle’s make and model. Therefore, it is crucial to research and obtain accurate pinout information for a specific vehicle to ensure efficient and effective diagnostic procedures.

Frequently Asked Questions

Common OBD2 diagnostic trouble codes include P0300 for random/multiple cylinder misfire, P0171 for lean fuel mixture, and P0420 for catalytic converter efficiency below threshold. These codes indicate specific issues with the vehicle’s engine or emissions system.

OBD2 scanners can be used to diagnose non-engine related issues in a vehicle depending on the protocols and capabilities of the scanner. However, the range of diagnostic tests may be limited and specialized equipment may be required for certain systems such as airbags or ABS.

The use of aftermarket OBD2 scanners or software may pose some risks, such as the potential for inaccurate readings, damage to the vehicle’s system, and security vulnerabilities. It is important to use reputable brands and ensure compatibility with the vehicle’s make and model.

The OBD2 system differs from earlier onboard diagnostics systems in its standardization of a 16-pin connector and use of standardized protocols for communication between the vehicle and diagnostic tools. This allows for easier and more efficient detection and analysis of vehicle problems.

OBD2 data can be used to improve fuel efficiency and track driving habits through the analysis of various vehicle parameters such as speed, acceleration, and engine load. This information can be used to optimize driving behavior and identify mechanical issues that affect fuel economy.

Related posts:

ISO and KWP Protocol Pins  

If pins 5, 7, 16 and, optionally, 15 are populated, the vehicle supports ISO or KWP.

VPW Protocol Pins  

If pins 2, 5 and 16 are populated, the vehicle supports VPW.

PWM Protocol Pins  

If pins 2, 5, 10 and 16 are populated, the vehicle supports PWM.

Auterra OBD II Scan Tools, Performance Meters and Data Loggers

Copyright Auterra, LLC All Rights Reserved.  |  Contact Us   |  About Us   |  Home

OBD2 connector

• OBD-II info
• COVID-19 INFO

OBD-II connector pinout

Obd-ii connector pinout for doip (ethernet), connector location.

Cookies: Our site uses cookies in order to deliver better content. By continuing you accept these cookies .

AutoPi Cloud Demo - Try for FREE

For developers, for individuals, individuals, autopi cloud, demo environment, autopi mini new, compare devices, autopi tmu cm4, autopi tmu socketcan, by business solution view all, asset tracking, big data project, keyless entry, docker integration, iot gateway, by industry, commercial trucking, car leasing, utility management, vehicle research, supply chain logistics, green transportation, connected car services, heavy equipment management, emergency services, automotive cybersecurity, public transportation, mobility as a service, car insurance policy, oem integration, electric vehicles, documentation, what can i build, more resources, contact support, schedule a demo, get in touch, online demo.

Ultimate OBD2 Guide: Understanding Vehicle Diagnostics

Updated at 16 Feb, 2023

— From novice to expert, our OBD2 guide dives deep into car diagnostic systems. Empower yourself with the know-how to troubleshoot vehicle issues.

Welcome to our simple guide on the OBD2 system. OBD2 became mandatory in all newer cars from 1996, and in the United States in 2021 -  282 million vehicles were registered.  So you can imagine how many of today's vehicles are depending on this system for diagnostics. Dive in with us as we uncover its many attributes.

If you're a developer, whether novice or expert, or manage a fleet of vehicles, you understand the importance of consistent maintenance to ensure smooth operations. But, are you familiar with OBD2 and its functionality?

The OBD2 system tracks your vehicle's health and pinpoints problems that might be the cause.

This guide will walk you through everything you need to know about OBD2, highlighting its main features, information, and its key elements.

What is OBD2?

In short, OBD2, or OBD-II, is a diagnostics system found in today's cars and trucks.

It's like the vehicle's health check mechanism, consistently monitoring different parts and systems. When it system detects a potential problem, a light will pop up on your dashboard as an alert.

The OBD2 system gathers crucial information from various sensors throughout the vehicle. The car's engine control unit (ECU) , acting as the vehicle's brain, processes this information to pinpoint issues. This could range from problems with the engine, exhaust emissions, or even fuel efficiency.

For example, if you've ever noticed your fuel consumption becoming less efficient, the OBD2 might identify a faulty oxygen sensor as the culprit, signaling you to address the issue before it worsens.

This is the car's way of telling you, that there is a problem within its system, by showing you the malfunction indicator light on your dashboard.

Experience the Future of Automotive Technology with Our Versatile, OBD2-Ready Device - Explore Insightful Vehicle Data Today.

How Does OBD2 Work?

OBD2 gathers information from sensors located in your car's engine and other systems.

When it detects an issue, it produces diagnostics trouble codes (DTC). These codes can be read using a OBD2 scanner or vehicle telematics device , helping you understand and fix any vehicle performance hitches.

You connect the telematics device to the OBD2 port, typically found under the car's dashboard, but can be found in other areas as well ( seen in the image below ).

This port has a standard design that lets the diagnostics device communicate with the car's main computer ( CAN bus ) and fetch the DTCs.

How Does OBD2 logs data?

The OBD2 system continuously monitors various parameters within the vehicle. As it collects data, it compares this information to pre-set standards.

If any discrepancies or anomalies are detected, the system flags these as potential issues, translating them into DTCs. These codes are then stored within the onboard computer, ready to be accessed by diagnostic tools.

How to Use an OBD2 Scanner?

Using an OBD2 scanner is a straightforward process that involves a few simple steps, i.e., you have an OBD2 scanner.

Here's a basic overview of how to use an OBD2 scanner.

Locate the OBD2 port: The OBD2 port is often found under the dashboard on the driver's side of the vehicle. The most common places are seen in the image below.

Turn on the ignition: Turn the key to the "On" position, but do not start the engine. This will enable the OBD2 system to connect with the scanner.

Connect the scanner: Connect the OBD2 scanner to the port. Depending on the make and model of the vehicle, you might need additional cables or adapters.

Read the Diagnostic Trouble Codes (DTCs): Once the scanner is connected, follow the instructions by the manufacturer to read the DTCs from the car's onboard computer. The scanner may also display other relevant information, such as sensor reading and real-time data.

Interpret the results: After reviewing the DTCs, use the scanner's manual or internet resources to interpret the data. With each code, the scanner should offer a summary of the problem. Remember, that some codes may need additional testing or examination to determine the main cause of the problem .

Clear the codes: After identifying the issue, use the scanner to clear the DTCs. This will reset the system and turn off the dashboard's check engine light. Remember, that just clearing the codes without addressing the underlying problem may result in the check engine light returning . This is how you reset DTC codes .

Overall, using an OBD2 scanner may assist car owners and mechanics in diagnosing and addressing any performance issues with a vehicle. You might save money on repairs and ensure your vehicle is functioning at peak performance by routinely checking the diagnostics using an OBD2 scanner.

OBD2 and CAN bus Connection

The OBD2 diagnostics act as a higher layer protocol, while the CAN serves as its communication method. The OBD2 standard defines a distinct connector, encompassing five main protocols.

Notably, since 1996, the CAN bus has been an essential OBD2 protocol for all vehicles in the U.S. By 2001, Europe mandated all cars to be OBD2 compliant, and this became a requirement in Australia and New Zealand starting 2006.

Is My Car OBD2 Compatible?

When it comes to determining if your vehicle is equipped with an OBD2 (On-Board Diagnostics II) system, the key factors to consider are not where your car was manufactured or initially purchased. Instead, compatibility hinges on the model year and specific regulations applicable to the country where the vehicle was sold new. Below, we simplify the process of figuring out your car's OBD2 status, so you can easily understand what to look for.

If your car is newer than 1996 in the US, or 2001 in the EU, then your car is most likely OBD2 compatible.

Please note: This list serves as a simplified guide. Vehicle compatibility with OBD2 can be influenced by specific models or manufacturer practices. Always consult your vehicle's manual or contact the dealership for the most accurate information.

The five OBD2 signal protocols

Diving into the world of car diagnostics, think of the OBD2 system as the main artery of communication in your vehicle. But here’s the twist: not all cars speak the same language. Picture five dialects under the OBD2 umbrella, each with its own flair and rules. It's like choosing the right fuel for your ride; picking the correct OBD2 protocol is key for smooth chats between your car and the diagnostic gear, shining a light on the car's health.

Why so many, you ask? It’s a mix of history’s favorites and the needs of now, blending old-school cool with modern tech. Coming up, we’ve got a neat snapshot of these five communication styles. Our table’s packed with the need-to-knows — from pin setups to voltage vibes — making it easier for you to get the gist of your car's internal conversations and how it gets along with diagnostic tools.

SAE J1850 PWM

Primarily used in Ford vehicles, this protocol communicates at 41.6 kbps, using Pulse Width Modulation to ensure reliable data transmission between the vehicle's systems and diagnostic tools.

SAE J1850 VPW

Favoured by General Motors, it operates at speeds of 10.4/31.6 kbps with a Variable Pulse Width, offering a unique method for data exchange that enhances diagnostic efficiency.

A choice for Chrysler, European, and Asian vehicles, this protocol facilitates asynchronous serial communication at 10.4 kbps, similar to RS-232, but with automotive-specific signal levels for broad compatibility.

ISO 14230 KWP2000

Also known as the Keyword Protocol 2000, it extends the capabilities of ISO 9141-2 by offering speeds up to 10.4 kbps and supports a wide range of vehicle diagnostic operations, especially in Chrysler, European, and Asian models.

ISO 15765 CAN

The backbone of modern vehicle diagnostics, this protocol is mandatory for all vehicles sold in the US from 2008 onwards. Operating at 250 kbit/s or 500 kbit/s, it leverages the CAN bus system for high-speed, robust data communication across the vehicle's network.

Gain Immediate Insights with Your Own OBD2 Scanner - Don't Wait, Discover the Power of Instant Insights Now!

The OBD2 Connector and Pinout

The OBD2 connector allows for easy data retrieval from your vehicle. The AutoPi TMU male connector pinout ( here's how it looks like ) is designed to interface with the female OBD2 16-pin (2x8) J1962 connector, which is a universal hardware interface.

Unlike OBD1 connector, often found near the hood, the OBD2 connector is commonly positioned within 2 feet (0.61m) of the steering wheel. Below is a detailed image of the OBD2 female connector pinout.

Quick overview of the OBD2 Port pinouts

The OBD2 port features a configuration of 16 pins, each tailored for a unique role within the system:

Pins 4 and 5 serve a fundamental purpose: they provide grounding to ensure safe and accurate data transmission.

For direct communication with the vehicle's main computer system, pins 2 and 10 come into play, specifically communicating with the SAE J1850 BUS+.

Central to many diagnostics processes, pins 6 and 14 are essential. They establish a connection to the CAN bus, a crucial communication channel outlined by the ISO 15765-4 standard.

Where Can I Find the OBD2 Port?

Generally, you will find the OBD2 port under the dashboard panel and near the steering wheel.

If you're wondering, "Where exactly is my OBD2 port?", then we have made an image below that gives a clear representation.

Most often, it's located beneath the dashboard and the steering wheel, as indicated by numbers 1-3 in the illustration. However, certain car models might have the port in alternative locations, as highlighted by numbers 4-9 in the depiction.

In this Youtube video, we have showcased how to find the OBD2 port and how to connect your AutoPi TMU device to the OBD2 port (Skip to 0:24).

History and the difference between OBD1 and OBD2

The history of On-board Diagnostics goes back to the 1960s when several organizations started discussing the necessity of having the OBD to detect emission failures.

Specifically, the organizations that supported it were the California Air Resources Board (CARB), the International Organization for Standardization (ISO), the Environmental Protection Agency (EPA), and the Society of Automotive Engineers (SAE).

In 1982, CARB began developing regulations requiring all vehicles to have an OBD port.

Up until recently, the UN commissioned the ISO to develop the WWH-OBD standard, however, it is currently being defined. More on this subject will come out soon.

1968: VW introduced the first OBD computer system with scanning capability.

1975: Datsun began using onboard computers in consumer vehicles.

1980: GM implemented an interface and protocol to test the Engine Control Module (ECM).

1988: CARB required all vehicles sold in California from 1988 and newer, to have a simple OBD capability as a minimum.

1994: CARB pushed the requirement further and issued the OBD2 specification in all vehicles sold in California from 1996.

1996: All cars sold in the US needed to be OBD2 compatible.

2001: EU made it mandatory for manufacturers to include OBD2 in all gasoline vehicles sold in the EU.

2004: EU made it mandatory for manufacturers to include OBD2 in all diesel vehicles sold in the EU.

2006: All vehicles manufactured in Australia and New Zealand were required to be OBD2 compatible.

2008: All vehicles sold in the US were required to use the signaling standard ISO 15765-4 (CAN).

OBD1 vs. OBD2

OBD, or OBD1, was used during the earlier years of the car manufacturing industry and was used to connect to the console of a car, while OBD2 (OBD-II) was introduced in car models produced in the early 1990s, and is remotely connected to the vehicle.

OBD2 is an advanced version of OBD1 and offers better signaling protocols and messaging formats. Furthermore, it provides better results for vehicle parameters when used in the emission control system.

How AutoPi Can Contribute To Your OBD2 Project

Elevate your OBD2 project with the cutting-edge AutoPi device . This versatile device not only seamlessly communicates with your car's ECUs and the intricate CAN bus system but also effortlessly plugs into the OBD2 port, serving as the nerve center for your automotive diagnostics.

With AutoPi, dive into advanced OBD2 data logging capabilities. Connect our robust OBD2 logger to your vehicle's OBD2 connector and embark on a data journey. Send "request frames" to solicit information, and receive detailed "response frames" through the CAN network, unlocking a treasure trove of diagnostic insights.

But why stop there? Decode the complex language of raw OBD2 responses with tools like the OBD2 DBC, transforming cryptic data into actionable insights. The AutoPi device goes a step further, allowing the use of a CAN logger to dispatch custom CAN frames, doubling as a sophisticated OBD2 logger.

Remember, compatibility is key. Vehicles differ in the model/year-specific OBD2 PIDs they support. With AutoPi, you're equipped to navigate these variations, ensuring a smooth and efficient diagnostic process across a wide range of vehicles.

Choose AutoPi device for your OBD2 project, and harness the power of smart, seamless, and sophisticated vehicle diagnostics. Unleash the full potential of your automotive endeavors with AutoPi.

OBD2 data at your fingertips

Other posts you will like

MF4 (MDF4) Explained: A Simple Guide to the ASAM File Format

Uncover the essentials of MF4 (MDF4) in our concise guide. Learn how this ASAM file format enhances automotive data management, aligning with ASAP2 st ...

Visualizing CAN Bus: The Ultimate Infographic Guide

Explore CAN Bus with our infographic: A clear, visual guide to vehicle communication networks, making complex tech accessible.

What is a Fleet Vehicle? Essential Tips for Buying Used

Discover the fundamentals of fleet vehicles and gain insightful tips on buying used ones. Transform your understanding to make informed purchases.

STILL HAVE QUESTIONS?

Get in touch with us – We're ready to answer any and all questions.

* Mandatory fields

Email our engineers

We are here to help!

E-MAIL OUR ENGINEERS

E-mail us at [email protected] or use the form below. We will get back to you ASAP.

OBDII Bus Description

OBD2 [On-Board Diagnostics II] defines a communications protocol and a standard connector to acquire data from passenger cars. OBD was required by U.S. EPA on all gasoline powered cars and light duty trucks manufactured for the U.S. after 1996 to help monitor/inspect vehicle emissions [as required by the Clean Air Act Amendments of 1990]. OBDII is the second generation of the OBD specification. The first generation OBD monitored fewer emission related components, was not calibrated to a specific level of emission performance, and was not as fell defined. Any passenger cars and truck produced after 1996 uses the OBD II standard. The OBD-II standard allows for multiple electrical interfaces, which complicates the hardware used to interface with the vehicle. OBDII will light a warning lamp called a MIL (malfunction indicator lamp), also known as the "check engine" light on the dash. A scan-tool may also be used to probe the OBDII connector OBDII data as defined by the SAE J1979 standard. The warning light may come on for any number of reasons and manufacturers recommend having the vehicle serviced as soon as possible. However; the Check Engine light could also come on for such simple reasons as filling the tank while the vehicle is running, or leaving the gas cap off. It may take up to three days for the light to go back off, after coming on for a missing gas cap. Main OBDII page . The OBD II interface is located in the cab, and must be located with in a certain area within the cab.

OBDII pinout, Signal Assignments

• Bus positive Line of SAE-J1850
• Chassis ground
• Signal ground
• CAN high (ISO 15765-4 and SAE-J2234)
• K line of ISO 9141-2 and ISO 14230-4
• Bus negative Line of SAE-J1850
• CAN low (ISO 15765-4 and SAE-J2234)
• L line of ISO 9141-2 and ISO 14230-4
• Battery voltage

The pinout assignment of unspecified pins is left to the vehicle manufacturer's discretion.

Engine Diagnostic Products , Scanners, Code Readers and so on.

J1962 - describes the standardized 16-pin trapezoidal connector. The male plug is use to connect to your car computer and the female is for making an extension cable or some other device

The J1850 VPW single wire protocol, used by GM may be found on an OBDII bus, if so the connector will have contacts in pins 2, 4, 5, and 16, with no contact in pin 10. The J1850 PWM two wire protocol, used by Ford may be found on an OBDII bus, if so the connector will have contacts in pins 2, 4, 5, and 10, with no contact in pin 16. The ISO 9141-2 single wire protocol, used by Chrysler may be found on an OBDII bus, if so the connector will have contacts in pins 4, 5, 7, 15 and 16. The protocol and command set is fixed by SAE J1979, so they are the same for all three protocols, only the electrical layers are changed. The CAN Bus may also be found on the OBDII bus

J1850 bus Description

The J1850 bus is used for diagnostics and data sharing applications in vehicles. The J1850 bus takes two forms; A 41.6Kbps Pulse Width Modulated (PWM) two wire differential approach, or a 10.4Kbps Variable Pulse Width (VPW) single wire approach. The single wire approach may have a bus length up to 35 meters (with 32 nodes). A high resides between 4.25 volts and 20 volts, a low is any thing below 3.5 volts. High and low values are sent as bit symbols (not single bits). Symbols times are 64uS and 128uS for the single wire approach. The ISO 9141-2 single-wire asynchronous interface operates at 10.4kbps

OBDII Related Standards

J1962 - SAE (Society of Automotive Engineers) standard defining the physical connector used for the OBDII interface. J1850 - SAE standard for the Class B Communications Network Interface (standard defines the actual J1850 signaling and timings) J1939, ISO 11898 J1978 - SAE standard for OBD II scan tools J1979 - SAE standard for diagnostic test modes J2012 - SAE standard for EPA emission test report format. J2178-1 - SAE standard for Class B Communications Network Message: Detailed Header Formats and Physical Address Assignments J2178-2 - SAE standard for Class B Communications Network Message: Data Parameter Definitions J2178-3 - SAE standard for Class B Communications Network Message: Frame IDs for Single Byte Forms of Headers J2178-4 - SAE standard for Class B Communications Network Message: Message Definitions for Three Byte Headers Code of Federal Regulations [CFR]: 40 CFR; 86.094-17h

OBDII Cable Assemblies

OBDII to DB15 pin Cable Female OBDII to 2x2 pin Cable Right Angle Male OBDII to DB-9pin Cable Male OBDII to DB9-pin Cable right angle Male OBDII to Male DB9-pin Cable Male OBDII to Male DB15-pin Cable Male OBDII to Female OBDII Cable BMW to Female OBDII Cable

Acronyms: DLC: Data link connector DTC: Diagnostic trouble code ECM: Engine control module MIL: Malfunction indicator light OBD: On-board diagnostics OBD-II: Second generation on-board diagnostics PCM: Power-train control module

OBD Definitions and Terms

{Back to OBDII Bus Index}

Home /   OBD Diagnostics /   How to Use an OBD2 Pin Adapter

How to Use an OBD2 Pin Adapter

If you’re having problems with your car’s OBD port, you might want to know how to resolve this problem. You can use an OBD-adapter to connect to your car’s diagnostic port. There are various types of adapters available, and you may also want to learn about CAN bus, DLC, and VPW protocol. Below are some examples of OBD-adapter types. You should be able to find the right one for your car by reading the following.

OBD-adapter

An OBD-adapter with OBD2 pins is an important device when you are connecting your car to a diagnostic scanner . Most cars use a J1962 connector. This type of connector uses a different power supply than a normal cigarette lighter. Heavy duty vehicles use 250K baud, while cars typically use 500K. Type B adapters fit either type of socket.

The OBD-adapter can connect to a variety of diagnostic tools, including a PC-based OBD analysis tool. These interfaces convert the OBD-II signals to serial data, which can then be decoded. The popular interfaces use the ELM327 or STN OBD Interpreter ICs to read all five generic OBD-II protocols. Others use the J2534 API to access other protocols.

OBD-II is a higher standard than OBD-I. It specifies the type of diagnostic connector, electrical signalling protocols, messaging format, and candidate list of vehicle parameters. It also specifies how data is encoded, as well as the method of connecting a diagnostic cable to a computer. OBD-II connectors can also be used with Bluetooth scanners. Bluetooth scanners can read data wirelessly, enabling you to read real-time onboard diagnostic results.

The OBD port is located on the dashboard near the steering wheel on every car. While the exact location varies from manufacturer to manufacturer, it is normally a blind spot. The connector connects to a STN1110 OBD UART board. During normal communication, the pins connect to a computer. Each pin has a unique function and the data link connector and data protocol is vendor specific. The CAN protocol is the most common in the US and Europe, but some Asian vehicles are equipped with OBD-II.

If you are having trouble with your CAN bus network, you can use a DMM to determine whether the terminating resistors are bad or faulty. The resistance value of these resistors should be at least 60 ohms. If the diagnosis is still not clear, you can also use a breakout box to monitor the network communication. If your CAN network is not working, you should check the circuitry of all the modules to find the problem. Check if the modules have a good power and ground, or if they have software issues. If all is well, the module is not faulty, but you can re-program the bus to fix the problem.

In addition to the multimeter, you can also use a Sparkfun shield to connect to the CAN network. The CAN bus line is connected to the Sparkfun shield. You can also use an OBD scanner to measure the voltage and current of the CAN network. It is important to check the CAN bus lines with a multimeter before you begin the project. Make sure the CAN bus lines are correctly connected to the Sparkfun shield and Arduino.

The CAN bus has two types of connectors: CAN High and CAN Low. The latter is usually used for diagnostic purposes. The OBD2 connector is also compatible with CAN bus. The pinouts for the two are similar, although CAN connectors are easier to install. When installing your CAN bus, be sure to read all manuals and follow manufacturer’s instructions. This will help you avoid any errors or issues with the communication.

Using a diagnostic scan tool is one of the best ways to test the DLC. It has multiple communication types, including CAN, OBD, and LIN. For example, you can check the voltage of the DLC on pins 6 and 14. Also, if your BOB has a ground indicator, you should check pin# 6 with an ohmmeter to ensure that the resistance is 60 ohms.

A DLC has five pins. The first two are located under the instrument panel. The fifth pin is for the battery voltage. This pin is referred to as the dynamic test. A DLC should show a voltage drop of.2 volts or less when tested. Alternatively, you can use a DLC breakout box to perform the test. A DLC can be found on most automobiles. Its use can help prevent faulty cars.

OBD-II diagnostic connectors are available on most cars, and they are located under the dashboard near the driver’s seat. These standardized connectors are used to download trouble codes and diagnose malfunctions on cars. This port is usually left unused. Vehicle tracking systems utilize diagnostic codes to track a car or vehicle. Plug a GPS tracker into the DLC port and the system will collect vehicle tracking data.

VPW protocol

VPW, or Variable Pulse Width, is one of the signal protocols that are required by OBD2/EOBD legislation. This legislation requires automotive vehicle manufacturers to provide access to the data bus via a standard 16-pin SAE J1962 connector. The purpose of the databus is to support emission control system testing and diagnostics. The two most common types of VPW are PWM and DPWM.

J1850-VPW is the standard for the pin that most GM cars use. However, most cars made after 2006 use the CAN bus. If you need to connect to this interface, make sure you purchase an OBD tool that supports the VPW protocol. In addition to OBD2 protocol, it also supports ISO, KWP, and PWM protocols. To be able to use them, you’ll need vendor-specific software.

VPW is another standard for communication on the OBD2 system. It operates at a speed of 10.4 kbps. In Europe and the US, it’s common to use a 10-bit communication protocol. The Variable Pulse Width protocol is used for most vehicles in Asia. The ISO 15765-4 CAN standard is available for 2008+ vehicles. You’ll be able to find OBD2 scan tools using a compatible scanner.

VPW uses differential signals to transmit data from one vehicle to another. PIDs in the OBD2 pin are typically HEX codes, but may have an additional data byte, if applicable. The OBD2 data payload structure is similar to that of a CAN ID. In addition to PIDs, OBD2 also supports a wide variety of standard parameter IDs.

PID request

To read the PID in a car, you can use the ODB2 pin and perform a PID request. The PID request is usually a 4-byte response. Each bit specifies one of the next 32 PIDs and indicates whether the device supports it. The first byte, A, contains two pieces of information. Bit A7 indicates whether the MIL is illuminated, and bits A6 through A0 specify the number of diagnostic trouble codes (DTCs) present in the ECU.

The service 02 and 01 are essentially the same. Both of them report a snapshot of data that was taken when the last diagnostic trouble code was set. The PID request for service 02 returns a zero if there is no snapshot. If the data returned is a zero, the PID request for the pin will have no meaning. Bit-Encoded-Notation (BEN) is used to identify the data byte.

If you are using the OBD-II interface, make sure you have the corresponding system settings set up. For example, you must enable GPS. If you have it enabled, it will send the data to the OBD-II port. If not, make sure to check the box next to the system option. To enable GPS, go to System > Administration, and select Send to Client. Once you’re done, you should be able to configure the PID request.

VPW data retrieval system

The VPW data retrieval system uses a 16-pin connector that was mandated by the OBD2/EOBD legislation. The data bus is used to test and diagnose the powertrain control module (PCM) in automobiles. Currently, VPW data retrieval systems are mostly used by Ford and General Motors. Each version has its own distinct advantages and disadvantages.

The OBD2 port allows for many data retrieval capabilities. Besides status information, OBD2 can also retrieve Diagnostic Trouble Codes, Powertrain and Emission Control Systems. It also supports Vehicle Identification Number (VIN) and Calibration Identification Number (CIN) data. This data allows mechanics to analyze the vehicle’s status and detect problems early on. They can then recommend the appropriate repair work and service.

Related Posts:

Leave a reply Cancel reply

Total Car Diagnostics helps fellow home car owners, mechanics, technicians, garage shops, engineers, ECU programmers and auto repair centers — to significantly cut down on maintenance, repair costs, time, money, energy… and all other frustrating headaches involved with dealing with vehicles — by providing cost-effective advice, tools and recommendations.

Home | About Us | Contact | Terms of Service | Privacy Policy | Tuning Disclaimer | Affiliate Program | Shop

Address: Byron Bay, NSW, 2481, Australia.

© Copyright 2023 by Total Car Diagnostics. All Rights Reserved.

New to EFILive Service Desk? Register for an account

Pin assignments - knowledgebase / flashscan v2 / flashscan v2 hardware configuration - efilive service desk.

• Download PDF

Copy to Clipboard

Pin assignments.

• AJ Andrew Jensen
• Last updated: Feb 24, 2023 by Andrew Jensen

FlashScan V2/AutoCal V2 Pin Assignments

FlashScan V2 Serial

AutoCal V2 Serial

Bench Harness Pin Assignments

Flashscan v2 obdii cable pin assignments, rj-45 cable plug   , vehicle obdii connector pin assignments.

7 of 10 people found this page helpful

Add a comment

Please log in or register to submit a comment.

Related Content

• AutoCal V2 Hardware Specification
• FlashScan V2 Hardware Specification
• Connecting FlashScan V2
• Connecting AutoCal V2

• Forum Listing
• Marketplace
• Advanced Search
• General Mercedes-Benz Forums
• General Mercedes-Benz

OBD2 diagnostics

• Add to quote

As per your PM Dont know as I have not tried. Ask Oztds as he is experimentiing with obd2, or wait a few days and see if he replies to your post. Bazzle  

All I can offer is that I am using a multiplexor, the same as I used for my previous 38pin connector, and it seems to work. Additionally the MB STAR system diagnostics printout I received on delivery of my present (newer) SLK shows the pin number next to each diagnostic item. So I presume that switching of the comms lines (ie. the K line) is required to access all the diagnostic information and that the multiplexor performs this function. On top of physical switching there must also be some software address selection and protocol compliance on the CAN buses to elicit responses from the various modules. Just switching won't be enough. This is all supposition based on observation. I haven't had cause to do any more than use what I have - ie. the CarSoft 2.4 via the multiplexor. Others have used various leads and paper clips to probe the pins on the 38 pin connector, but I haven't seen anyone do this on the OBDII. This could be done I suppose as CarSoft has a provision to manually run the various tests without the mux. I don't know whether this assists progress on your question. What do you have and what are you trying to achieve?  

No picture shown... I've not come across this problem before. Presumably there is a problem code that initiated the warning light? But then you probably can't read it. Need to fudge pin 13 - never seen an OBDII breakout box though. Perhaps best to get a service centre to look.  

Ah, fantastic quotes, oztds: “Perseverance is more prevailing than violence; and many things which cannot be overcome when they are together yield themselves up when taken little by little." - Plutarch. "None are so hopelessly enslaved as those who falsely believe they are free." - Johann Wolfgang von Goethe Question: Where to buy the Star diagnostics? Can ebay ones be trusted. I haven't the big bread. I'm in Sweden. (not too far from China)...  

• ?            
• 696.4K members

Top Contributors this Month

DLC pin signals assignment

Mercedes obd ii diagnostic connector pinout.

• Ask a question

Mercedes-Benz OBD-2 compatibility list

Note that list is not 100% complete!

OBD-2 protocols:

1996-2000 : ISO-9141

2000 - 2002 : ISO 9141 or KWP 2000

2003 - 2007 : KWP 2000 or CAN

after 2007 : CAN

Some OBD-II cables schemes:

OBD-2 ISO 9141-2 (14230-4, KWP2000) simple serial cable OBD-2 J1850 PWM, J1850 VPW serial ELM327 cable OBD-2 universal ISO 15765-4 CAN, SAE J1850 PWM, SAE J1850 VPW, ISO 9141-2, ISO 14230-4 and SAE J1939 diagnostic cable

• Mercedes-Benz A140 (1999+) , A150 (2005+) , A160 (1998+) , A170 (2002+) , A180 (2008+) , A190 (1999+) , Actros (2007+) , Atego (2007+)
• Mercedes-Benz B170 (2007+) , b180 (2010+) , B200 (2006+)
• Mercedes-Benz C180 (2000+) , C180K (2009+) , C200 (2001+) , C200 coupe (2003+) , C200T (2001+) , c220 (1998+) , C230 (1998+) , C240 (2000+) , C270 (2003+) , C320 (2001+) , C350 (2008+) , CL500 (2002+) , CLK (1998+) , CLK 230 (1999+) , CLK 270 (2003+) , CLK 320 (2002+) , CLK 500 (2003+) , CLK230 (2000+) , CLS (2005+) , cls500 (2006+)
• Mercedes-Benz E200CDI (2004+) , E200CGI (2010+) , E200K (2001+) , E220 (2000+) , E240 (2004+) , E270 (2003+) , e280 (2004+) , E320 (1995+) , E55AMG (2003+)
• Mercedes-Benz G320CDI (2007+)
• Mercedes-Benz ML (2000+) , ML 270 (2000+) , ML 320 (1999+) , ML 400 (2003+) , ML 55 amg (2003+) , ML270 (2003+) , ML320 (1999+) , ML350 (2006+) , ML55 AMG (2003+)
• Mercedes-Benz S203 (2003+) , S211 (2004+) , S320 (1999+) , S400 (2003+) , S500 (2005+) , SL280 (2001+) , SL350  (2003+) , SL500 (1999+) , SLK (2000+) , SLK170 (2001+) , SLK200 (1998+) , SLK230 (2004+) , Sprinter (2001+) , Sprinter 313 (2008+) , Sprinter 315 (2007+) , Sprinter 316 (2010+) , Sprinter/NCV3 (2007+)
• Mercedes-Benz V220 (1999+) , Vaneo (2002+) , Viano (2005+) , Vito (2000+)
• OBD II diagnostic interface pinout