On-board diagnostics (OBD) is an automotive term referring to a vehicle's self-diagnostic and reporting capability. OBD systems give the vehicle owner or repair technician access to the status of the various vehicle subsystems. The amount of diagnostic information available via OBD has varied widely since its introduction in the early 1980s versions of on-board vehicle computers. Early versions of OBD would simply illuminate a malfunction indicator light or "idiot light" if a problem was detected but would not provide any information as to the nature of the problem. Modern OBD implementations use a standardized digital communications port to provide real-time data in addition to a standardized series of diagnostic trouble codes, or DTCs, which allow one to rapidly identify and remedy malfunctions within the vehicle.
Maps, Directions, and Place Reviews
History
- 1968: Volkswagen introduces the first on-board computer system with scanning capability, in their fuel-injected Type 3 models.
- 1978: Datsun 280Z On-board computers begin appearing on consumer vehicles, largely motivated by their need for real-time tuning of fuel injection systems. Simple OBD implementations appear, though there is no standardization in what is monitored or how it is reported.
- 1980: General Motors implements a proprietary interface and protocol for testing of the Engine Control Module (ECM) on the vehicle assembly line. The 'assembly line diagnostic link' (ALDL) protocol broadcasts at 160 bit/s Implemented on California vehicles for the 1980 model year, and the rest of the United States in 1981. Most owners can read DTCs (Diagnostic Trouble Code(s)) by commanding the ECM (Engine Control Module) to flash the CEL (Check Engine Lamp) or MIL (Malfunction Indicator Lamp) on and off. A PC based Software package called WinALDL will listen to the CLCC (Closed Loop Carburetor Control) and early CLC EFI datastreams over a fairly easy to construct interface cable that converts the 160 baud TTL serial data being transmitted by the ECM to RS232 or USB serial data but there is not much information transmitted by these early ECMs.
- 1986: An upgraded version of the ALDL protocol appears which communicates at 8192 bit/s with half-duplex UART signaling. This protocol is defined in GM XDE-5024B.
- 1988: The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and set of diagnostic test signals.
- 1991: The California Air Resources Board (CARB) requires that all new vehicles sold in California in 1991 and newer vehicles have some basic OBD capability. These requirements are generally referred to as "OBD-I", though this name is not applied until the introduction of OBD-II. The data link connector and its position are not standardized, nor is the data protocol.
- ~1994: Motivated by a desire for a statewide emissions testing program, the CARB issues the OBD-II specification and mandates that it be adopted for all cars sold in California starting in model year 1996 (see CCR Title 13 Section 1968.1 and 40 CFR Part 86 Section 86.094). The DTCs and connector suggested by the SAE are incorporated into this specification.
- 1996: The OBD-II specification is made mandatory for all cars manufactured in the United States to be sold in the United States.
- 2001: The European Union makes EOBD mandatory for all gasoline (petrol) vehicles sold in the European Union, starting in MY2001 (see European emission standards Directive 98/69/EC).
- 2003: The European Union makes EOBD mandatory for all diesel cars sold in the European Union
- 2008: All cars sold in the United States are required to use the ISO 15765-4 signaling standard (a variant of the Controller Area Network (CAN) bus).
- 2008: Certain light vehicles in China are required by the Environmental Protection Administration Office to implement OBD (standard GB18352) by July 1, 2008. Some regional exemptions may apply.
- 2010: HDOBD (heavy duty) specification is made mandatory for selected commercial (non-passenger car) engines sold in the United States.
Diagnose Connection Problems Video
Standard interfaces
ALDL
GM's ALDL (Assembly Line Diagnostic Link) is a General Motors proprietary onboard diagnostic interface that started with the late 1970s and early 1980s CLCC (Closed Loop Carburetor Control) and early GM EFI systems. There's an appearance of standardization because the diagnostic jack didn't change over the years ALDL was utilized by GM. GM North America used a proprietary 12 position Metripack 280 diagnostic jack. GM Australia Holden used a 6 position Metripack 280 diagnostic jack. The GM Europe Opel and Vauxall used a 10 position Metripack 280 diagnostic jack. ALDL was not a standard. It was actually extremely fragmented. The information exchange changed with each powertrain control module (aka PCM, ECM, ECU). A PCM integrates transmission and engine control on one Processing unit. ECM/ECU are engine control only with a separate TCM (Transmission Control Module) if needed. While ALDL is the closest thing to standard onboard diagnostics prior to 1991 ALDL was not a standard. ALDL was even fragmented within GM brands, models, and model years. Trim levels in the same model year, division, and nameplate can use different communications. Different versions presented differences in diagnostic jack pin-outs, data protocols, and data rates (this is the reason for the ?Mask? files needed for aftermarket software communication). Earlier versions used 160 bit/s, while later versions went up to 8192 bit/s and used bi-directional communications to the PCM or ECM/TCM.
ALDL on 1991 and later California emissions GM vehicles met the 1991 and later California OBD I communication standard. This does not mean that ALDL is OBD I. OBD I was an early 1990s California-only mandate, not a United States federal mandate. It was not used on non-California emissions vehicles.
Some Asian, European, and North American diagnostic ports are sometimes incorrectly referred to as ALDL. A small number of vehicles manufactured before 1996 from other manufacturers used the GM Delphi Electronics engine and powertrain controllers; however, these used a modified ALDL communication protocol. Most did not and there was not a homogeneous name for these other proprietary diagnostic protocols and interface ports. Ford EEC, Toyota DLC, Chrysler, Nissan, Volkswagen, and others used their own onboard Diagnostics protocols and connectors, and are also not OBD I compliant outside California.
M-OBD
Multiplex OBD or M-OBD is an OBD variant protocol used by Toyota, prior to OBD-II compliance. Toyota's DLC3 (Data Link Connector 3) is the standard 16-pin OBD-II connector, but a proprietary cable and software is required as generic OBD-II cables and software will not interface with it. The bus + line is SIL (Pin 7)
OBD-I
A 1991 and later California standard. It is not a USA Federal standard. The regulatory intent of OBD-I was to encourage auto manufacturers to design reliable emission control systems that remain effective for the vehicle's "useful life". The Diagnostic Trouble Codes (DTCs) of OBD-I vehicles can usually be found without an expensive 'scan tool'. Each manufacturer used their own diagnostic link connector (DLC), DLC location, DTC definitions, and procedure to read the DTCs from the vehicle. DTCs from OBD-I cars are often read through the blinking patterns of the 'Check Engine Light' (CEL) or 'Service Engine Soon' (SES) light. By connecting certain pins of the diagnostic connector, the 'Check Engine' light will blink out a two-digit number that corresponds to a specific error condition. The DTCs of some OBD-I cars are interpreted in different ways, however. Cadillac (gasoline) fuel-injected vehicles are equipped with actual on-board diagnostics, providing trouble codes, actuator tests and sensor data through the new digital Electronic Climate Control display. Holding down 'Off' and 'Warmer' for several seconds activates the diagnostic mode without the need for an external scan tool. Some Honda engine computers are equipped with LEDs that light up in a specific pattern to indicate the DTC. General Motors, some 1989-1995 Ford vehicles (DCL), and some 1989-1995 Toyota/Lexus vehicles have a live sensor data stream available, however, many other OBD-I equipped vehicles do not. OBD-I vehicles have fewer DTCs available than for OBD-II equipped vehicles.
OBD-1.5
OBD 1.5 refers to a partial implementation of OBD-II which General Motors used on some vehicles in 1994 and 1995. OBD 1.5 is a slang term. GM did not use the term OBD 1.5 in the documentation for these vehicles; they simply have an OBD and an OBD-II section in the service manual. Most of these 1994 & 1995 vehicles were simply 8196 baud ALDL serial data on the #9 vendor option terminal of the J1962 Jack that was formally adopted for OBD II starting in 1996.
For example, the 94-95 Corvettes have one post-catalyst oxygen sensor (although they have two catalytic converters), and have a subset of the OBD-II codes implemented. For a 1994 Corvette the implemented OBD-II codes are P0116-P0118, P0131-P0135, P0151-P0155, P0158, P0160-P0161, P0171-P0175, P0420, P1114-P1115, P1133, P1153 and P1158.
This hybrid system was present on the GM H-body cars in 94-95, W-body cars (Buick Regal, Chevrolet Lumina ('95 only), Chevrolet Monte Carlo ('95 only), Pontiac Grand Prix, Oldsmobile Cutlass Supreme) in 94-95, L-body (Chevrolet Beretta/Corsica) in 94-95, Y-body (Chevrolet Corvette) in 94-95, on the F-body (Chevrolet Camaro and Pontiac Firebird) in 95 and on the J-Body (Chevrolet Cavalier and Pontiac Sunfire) and N-Body (Buick Skylark, Oldsmobile Achieva, Pontiac Grand Am) in 95 and 96 and also on '94-'95 Saab vehicles with the naturally aspirated 2.3.
The pinout for the ALDL connection on these cars is as follows:
GM used at least two (#9 & #12) of what became seven "Vendor Option" terminals (1, 8, 9, 11, 12, 13) along with #4 Chassis Ground and #16 Battery Power in the formally accepted J1962 Jack. While OBD II interfaces will not communicate with these controllers they will not be damaged by plugging into these jacks either. Rumors persist of hybrids that had the GM ALDL #9-Vendor Option & GM OBD II #2-J1850 Bus+ serial data terminals populated. This writer has no proof that these exist.
An OBD 1.5 compatible scan tool is required to read codes generated by OBD 1.5.
Additional vehicle-specific diagnostic and control circuits are also available on this connector. For instance, on the Corvette there are interfaces for the Class 2 serial data stream from the PCM, the CCM diagnostic terminal, the radio data stream, the airbag system, the selective ride control system, the low tire pressure warning system, and the passive keyless entry system.
An OBD 1.5 has also been used on Mitsubishi cars of '95 '97 vintage, some 1995 Volkswagen VR6's and in the Ford Scorpio since 95.
Codes retrieved are still 2 digit codes which still require an ALDL scan tool, a laptop and USB-ALDL interface with a properly pinned J1962 ALDL plug, or a GM Tech II. Flash codes can be retrieved on 1994-1995 Corvettes by shorting #12-Vendor Option to #4 Chassis Ground.
OBD-II
OBD-II is an improvement over OBD-I in both capability and standardization. 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 list of standardized DTCs. As a result of this standardization, a single device can query the on-board computer(s) for these parameters in any vehicle. OBD-II standardization was prompted to simplify diagnosis of increasingly complicated emissions equipment, and though only emission-related codes and data are required to be transmitted through it according to U.S. legislation, most manufacturers have made the OBD-II Data Link Connector the main connector in the vehicle through which all systems are diagnosed and reprogrammed. 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. Manufacturers may also add custom data parameters to their specific OBD-II implementation, including real-time data requests as well as trouble codes.
OBD-II diagnostic connector
The SAE J1962 specification provides for two standardized hardware interfaces, called type A and type B. Both are female, 16-pin (2x8), D-shaped connectors, and both have a groove between the two rows of pins. But type B has the groove interrupted in the middle, so you can't plug a type A male connector into a type B socket. You can, however, mate a type B male plug in a type A female socket.
The type A connector is used for vehicles that use 12V supply voltage, whereas type B is used for 24V vehicles and it is required to mark the front of the D-shaped area in blue color.
SAE J1962 defines the pinout of the connector as:
Unlike the OBD-I connector, which was sometimes found under the hood of the vehicle, the OBD-II connector is required to be within 2 feet (0.61 m) of the steering wheel (unless an exemption is applied for by the manufacturer, in which case it is still somewhere within reach of the driver).
EOBD
The EOBD (European on board diagnostics) regulations are the European equivalent of OBD-II, and apply to all passenger cars of category M1 (with no more than 8 passenger seats and a Gross Vehicle Weight rating of 2500 kg or less) first registered within EU member states since January 1, 2001 for petrol (gasoline) engined cars and since January 1, 2004 for diesel engined cars.
For newly introduced models, the regulation dates applied a year earlier - January 1, 2000 for petrol and January 1, 2003 for diesel.
For passenger cars with a Gross Vehicle Weight rating of greater than 2500 kg and for light commercial vehicles, the regulation dates applied from January 1, 2002 for petrol models, and January 1, 2007 for diesel models.
The technical implementation of EOBD is essentially the same as OBD-II, with the same SAE J1962 diagnostic link connector and signal protocols being used.
With Euro V and Euro VI emission standards, EOBD emission thresholds will be lower than previous Euro III and IV.
EOBD fault codes
Each of the EOBD fault codes consists of five characters: a letter, followed by four numbers. The letter refers to the system being interrogated e.g. Pxxxx would refer to the powertrain system. The next character would be a 0 if complies to the EOBD standard. So it should look like P0xxx.
The next character would refer to the sub system.
- P00xx - Fuel and air metering and auxiliary emission controls.
- P01xx - Fuel and air metering.
- P02xx - Fuel and air metering (injector circuit).
- P03xx - Ignition system or misfire.
- P04xx - Auxiliary emissions controls.
- P05xx - Vehicle speed controls and idle control system.
- P06xx - Computer output circuit.
- P07xx - Transmission.
- P08xx - Transmission.
The following two characters would refer to the individual fault within each subsystem.
EOBD2
The term "EOBD2" is marketing speak used by some vehicle manufacturers to refer to manufacturer-specific features that are not actually part of the OBD or EOBD standard. In this case "E" stands for Enhanced.
JOBD
JOBD is a version of OBD-II for vehicles sold in Japan.
ADR 79/01 & 79/02 (Australian OBD standard)
The ADR 79/01 vehicle standard (Australian Design Rule 79/01 - Emission Control for Light Vehicles, 2005) is the Australian equivalent of OBD-II. It applies to all vehicles of category M1 and N1 with a gross Vehicle Weight rating of 3500 kg or less, registered from new within Australia and produced since January 1, 2006 for petrol (gasoline) engined cars and since January 1, 2007 for diesel engined cars. For newly introduced models, the regulation dates applied a year earlier - January 1, 2005 for petrol and January 1, 2006 for diesel. The ADR 79/01 standard was supplemented by the ADR 79/02 standard which imposed tighter emissions restrictions, applicable to all vehicles of class M1 and N1 with a gross vehicle weight rating of 3500 kg or less, from July 1, 2008 for new models, July 1, 2010 for all models. The technical implementation of this standard is essentially the same as OBD-II, with the same SAE J1962 diagnostic link connector and signal protocols being used.
OBD-II signal protocols
There are five signaling protocols that are permitted with the OBD-II interface. Most vehicles implement only one of the protocols. It is often possible to deduce the protocol used based on which pins are present on the J1962 connector:
- SAE J1850 PWM (pulse-width modulation -- 41.6 kbit/s, standard of the Ford Motor Company)
- pin 2: Bus+
- pin 10: Bus-
- High voltage is +5 V
- Message length is restricted to 12 bytes, including CRC
- Employs a multi-master arbitration scheme called 'Carrier Sense Multiple Access with Non-Destructive Arbitration' (CSMA/NDA)
- SAE J1850 VPW (variable pulse width -- 10.4 kbit/s, standard of General Motors)
- pin 2: Bus+
- Bus idles low
- High voltage is +7 V
- Decision point is +3.5 V
- Message length is restricted to 12 bytes, including CRC
- Employs CSMA/NDA
- ISO 9141-2. This protocol has an asynchronous serial data rate of 10.4 kbit/s. It is somewhat similar to RS-232; however, the signal levels are different, and communications happens on a single, bidirectional line without additional handshake signals. ISO 9141-2 is primarily used in Chrysler, European, and Asian vehicles.
- pin 7: K-line
- pin 15: L-line (optional)
- UART signaling
- K-line idles high, with a 510 ohm resistor to Vbatt
- The active/dominant state is driven low with an open-collector driver.
- Message length is Max 260Bytes. Data field MAX 255.
- ISO 14230 KWP2000 (Keyword Protocol 2000)
- pin 7: K-line
- pin 15: L-line (optional)
- Physical layer identical to ISO 9141-2
- Data rate 1.2 to 10.4 kbit/s
- High signal voltage level: +12V (min/max 9.60 to 13.5)
- Message may contain up to 255 bytes in the data field
- ISO 15765 CAN (250 kbit/s or 500 kbit/s). The CAN protocol was developed by Bosch for automotive and industrial control. Unlike other OBD protocols, variants are widely used outside of the automotive industry. While it did not meet the OBD-II requirements for U.S. vehicles prior to 2003, as of 2008 all vehicles sold in the US are required to implement CAN as one of their signaling protocols.
- pin 6: CAN High
- pin 14: CAN Low
- CANH signal voltage level: 3.5V (min/max 2.75 to 4.50)
- CANL signal voltage level: 1.5V (min/max 0.5 to 2.25)
All OBD-II pinouts use the same connector, but different pins are used with the exception of pin 4 (battery ground) and pin 16 (battery positive).
OBD-II diagnostic data available
OBD-II provides access to data from the engine control unit (ECU) and offers a valuable source of information when troubleshooting problems inside a vehicle. The SAE J1979 standard defines a method for requesting various diagnostic data and a list of standard parameters that might be available from the ECU. The various parameters that are available are addressed by "parameter identification numbers" (parameter IDs or PIDs) which are defined in J1979. For a list of basic PIDs, their definitions, and the formula to convert raw OBD-II output to meaningful diagnostic units, see OBD-II PIDs. Manufacturers are not required to implement all PIDs listed in J1979 and they are allowed to include proprietary PIDs that are not listed. The PID request and data retrieval system gives access to real time performance data as well as flagged DTCs. For a list of generic OBD-II DTCs suggested by the SAE, see Table of OBD-II Codes. Individual manufacturers often enhance the OBD-II code set with additional proprietary DTCs.
Mode of operation
Here is a basic introduction to the OBD communication protocol according to ISO 15031:
- Mode $01 is used to identify what powertrain information is available to the scan tool.
- Mode $02 displays Freeze Frame data.
- Mode $03 lists the emission-related "confirmed" diagnostic trouble codes stored. It displays exact numeric, 4 digit codes identifying the faults.
- Mode $04 is used to clear emission-related diagnostic information. This includes clearing the stored pending/confirmed DTCs and Freeze Frame data.
- Mode $05 displays the oxygen sensor monitor screen and the test results gathered about the oxygen sensor. There are ten numbers available for diagnostics:
- $01 Rich-to-Lean O2 sensor threshold voltage
- $02 Lean-to-Rich O2 sensor threshold voltage
- $03 Low sensor voltage threshold for switch time measurement
- $04 High sensor voltage threshold for switch time measurement
- $05 Rich-to-Lean switch time in ms
- $06 Lean-to Rich switch time in ms
- $07 Minimum voltage for test
- $08 Maximum voltage for test
- $09 Time between voltage transitions in ms
- Mode $06 is a request for on-board monitoring test results for continuously and non-continuously monitored system. There are typically a minimum value, a maximum value, and a current value for each non-continuous monitor.
- Mode $07 is a request for emission-related diagnostic trouble codes detected during current or last completed driving cycle. It enables the external test equipment to obtain "pending" diagnostic trouble codes detected during current or last completed driving cycle for emission-related components/systems. This is used by service technicians after a vehicle repair, and after clearing diagnostic information to see test results after a single driving cycle to determine if the repair has fixed the problem.
- Mode $08 could enable the off-board test device to control the operation of an on-board system, test, or component.
- Mode $09 is used to retrieve vehicle information. Among others, the following information is available:
- VIN (Vehicle Identification Number): Vehicle ID
- CALID (calibration identification): ID for the software installed on the ECU
- CVN (calibration verification number): Number used to verify the integrity of the vehicle software. The manufacturer is responsible for determining the method of calculating CVN(s), e.g. using checksum.
- In-use performance counters
- Gasoline engine: catalyst, primary oxygen sensor, evaporating system, EGR system, VVT system, secondary air system, and secondary oxygen sensor
- Diesel engine : NMHC catalyst, NOx reduction catalyst, NOx absorber particulate matter filter, exhaust gas sensor, EGR system, VVT system, boost pressure control, fuel system.
- Mode $0A lists emission-related "permanent" diagnostic trouble codes stored. As per CARB, any diagnostic trouble codes that is commanding MIL on and stored into non-volatile memory shall be logged as a permanent fault code.
OBD applications
Various tools are available that plug into the OBD connector to access OBD functions. These range from simple generic consumer level tools to highly sophisticated OEM dealership tools to vehicle telematic devices.
Hand-held scan tools
A range of rugged hand-held scan tools is available.
- Simple fault code readers/reset tools are mostly aimed at the consumer level.
- Professional hand-held scan tools may possess more advanced functions
- Access more advanced diagnostics
- Set manufacturer- or vehicle-specific ECU parameters
- Access and control other control units, such as air bag or ABS
- Real-time monitoring or graphing of engine parameters to facilitate diagnosis or tuning
Mobile device-based tools and analysis
Mobile device applications allow mobile devices such as cell phones and tablets to display and manipulate the OBD-II data accessed via USB adaptor cables, bluetooth or WiFi adapters plugged into the car's OBD II connector. A number of new devices allow the vehicle's OBD port to stream data directly to the Internet via a cellular connection.
PC-based scan tools and analysis platforms
A PC-based OBD analysis tool that converts the OBD-II signals to serial data (USB or serial port) standard to PCs or Macs. The software then decodes the received data to a visual display. Many popular interfaces are based on the ELM or STN11x0 OBD Interpreter ICs, both of which read all five generic OBD-II protocols. Some adapters now use the J2534 API allowing them to access OBD-II Protocols for both cars and trucks.
In addition to the functions of a hand-held scan tool, the PC-based tools generally offer:
- Large storage capacity for data logging and other functions
- Higher resolution screen than handheld tools
- The ability to use multiple software programs adding flexibility
The extent that a PC tool may access manufacturer or vehicle-specific ECU diagnostics varies between software products as it does between hand-held scanners.
Data loggers
Data loggers are designed to capture vehicle data while the vehicle is in normal operation, for later analysis.
Data logging uses include:
- Engine and vehicle monitoring under normal operation, for the purpose of diagnosis or tuning.
- Some auto insurance companies offer reduced premiums if OBD-II vehicle data loggers or cameras are installed - and if the driver's behaviour meets requirements. This is a form of auto insurance risk selection
- Monitoring of driver behaviour by fleet vehicle operators.
Analysis of vehicle black box data may be performed on a periodic basis, automatically transmitted wirelessly to a third party or retrieved for forensic analysis after an event such as an accident, traffic infringement or mechanical fault.
Emission testing
In the United States, many states now use OBD-II testing instead of tailpipe testing in OBD-II compliant vehicles (1996 and newer). Since OBD-II stores trouble codes for emissions equipment, the testing computer can query the vehicle's onboard computer and verify there are no emission related trouble codes and that the vehicle is in compliance with emission standards for the model year it was manufactured.
In the Netherlands, 2006 and later vehicles get a yearly EOBD emission check.
Driver's supplementary vehicle instrumentation
Driver's supplementary vehicle instrumentation is installed in a vehicle in addition to that provided by the vehicle manufacturer and intended for display to the driver during normal operation. This is opposed to scanners used primarily for active fault diagnosis, tuning, or hidden data logging.
Auto enthusiasts have traditionally installed additional gauges such as manifold vacuum, battery current etc. The OBD standard interface has enabled a new generation of enthusiast instrumentation accessing the full range of vehicle data used for diagnostics, and derived data such as instantaneous fuel economy.
Instrumentation may take the form of dedicated trip computers, carputer or interfaces to PDAs, smartphones, or a GPS navigation unit.
As a carputer is essentially a PC, the same software could be loaded as for PC-based scan tools and vice versa, so the distinction is only in the reason for use of the software.
These enthusiast systems may also include some functionality similar to the other scan tools.
Vehicle telematics
OBD II is no longer only used by professionals and hobbyists to repair vehicles. OBD II information is commonly used by vehicle telematics devices that perform fleet tracking, monitor fuel efficiency, prevent unsafe driving, as well as for remote diagnostics and by pay-as-you-drive insurance. Although originally not intended for the above purposes, commonly supported OBD II data such as vehicle speed, RPM, and fuel level allow GPS-based fleet tracking devices to monitor vehicle idling times, speeding, and over-revving. By monitoring OBD II DTCs a company can know immediately if one of its vehicles has an engine problem and by interpreting the code the nature of the problem. OBD II is also monitored to block mobile phones when driving and to record trip data for insurance purposes.
Standards documents
SAE standards documents on OBD-II
- J1962 - Defines the physical connector used for the OBD-II interface.
- J1850 - Defines a serial data protocol. There are two variants- 10.4 kbit/s (single wire, VPW) and 41.6 kbit/s (two wire, PWM). Mainly used by US manufacturers, also known as PCI (Chrysler, 10.4 kbit/s), Class 2 (GM, 10.4 kbit/s), and SCP (Ford, 41.6 kbit/s)
- J1978 - Defines minimal operating standards for OBD-II scan tools
- J1979 - Defines standards for diagnostic test modes
- J2012 - Defines standards trouble codes and definitions.
- J2178-1 - Defines standards for network message header formats and physical address assignments
- J2178-2 - Gives data parameter definitions
- J2178-3 - Defines standards for network message frame IDs for single byte headers
- J2178-4 - Defines standards for network messages with three byte headers*
- J2284-3 - Defines 500 kbit/s CAN Physical and Data link layer
- J2411 - Describes the GMLAN (single-wire CAN) protocol, used in newer GM vehicles. Often accessible on the OBD connector as PIN 1 on newer GM vehicles.
SAE standards documents on HD (heavy duty) OBD
- J1939 - Defines a data protocol for heavy duty commercial vehicles
ISO standards
- ISO 9141: Road vehicles -- Diagnostic systems. International Organization for Standardization, 1989.
- Part 1: Requirements for interchange of digital information
- Part 2: CARB requirements for interchange of digital information
- Part 3: Verification of the communication between vehicle and OBD II scan tool
- ISO 11898: Road vehicles -- Controller area network (CAN). International Organization for Standardization, 2003.
- Part 1: Data link layer and physical signalling
- Part 2: High-speed medium access unit
- Part 3: Low-speed, fault-tolerant, medium-dependent interface
- Part 4: Time-triggered communication
- ISO 14230: Road vehicles -- Diagnostic systems -- Keyword Protocol 2000, International Organization for Standardization, 1999.
- Part 1: Physical layer
- Part 2: Data link layer
- Part 3: Application layer
- Part 4: Requirements for emission-related systems
- ISO 14320 no data
- ISO 15031: Communication between vehicle and external equipment for emissions-related diagnostics, International Organization for Standardization, 2010.
- Part 1: General information and use case definition
- Part 2: Guidance on terms, definitions, abbreviations and acronyms
- Part 3: Diagnostic connector and related electrical circuits, specification and use
- Part 4: External test equipment
- Part 5: Emissions-related diagnostic services
- Part 6: Diagnostic trouble code definitions
- Part 7: Data link security
- ISO 15765: Road vehicles -- Diagnostics on Controller Area Networks (CAN). International Organization for Standardization, 2004.
- Part 1: General information
- Part 2: Network layer services ISO 15765-2
- Part 3: Implementation of unified diagnostic services (UDS on CAN)
- Part 4: Requirements for emissions-related systems
Security issues
Researchers at the University of Washington and University of California examined the security around OBD, and found that they were able to gain control over many vehicle components via the interface. Furthermore, they were able to upload new firmware into the engine control units. Their conclusion is that vehicle embedded systems are not designed with security in mind.
There have been reports of thieves using specialist OBD reprogramming devices to enable them to steal cars without the use of a key. The primary causes of this vulnerability lie in the tendency for vehicle manufacturers to extend the bus for purposes other than those for which it was designed, and the lack of authentication and authorization in the OBD specifications, which instead rely largely on security through obscurity. The National Highway Traffic Safety Administration has demonstrated the ability to take over certain functions through wires to the car's control center.
Source of the article : Wikipedia
EmoticonEmoticon