Connect SuperMini ELM327 OBD II Step 3: Put the key in Contact Step 4: Turn Bluetooth On and find 'OBDII' Step 5: Turn GPS On Step 6: Go to Torque Application Step 7: Wait until the phone is.
Is my vehicle equipped with OBD-2?On Board Diagnostics, OBD-II, is required on all automobiles and light trucks in the United States from 1996 onward. OBD-II is a set of specifications for monitoring and reporting on engine performance in modern automobiles. Diesel (compression ignition) vehicles were not required to support OBD until 2004. Some pre-2001 petrol vehicles and pre-2004 diesel vehicles have a 16-pin connectors but they may not be OBD-II or EOBD compliant. Where is an OBD II connector?Locating your OBD-II connector can be a difficult task as vehicle manufacturers tend to hide away the socket. Usually OBD-2 connector is located on the driver's side of the passenger compartment near the center console. Sometimes it's located in the driver's foot well, under the steering wheel, behind panels in the dashboard fascia and the central area between the driver's seat and the passenger seat.
Some connectors have been located behind ashtrays, under the passenger seat and even over by the passengers door.OBD-2 connector must have pins 4, 5 for ground connections and pin 16 for 12 volt power supply from the vehicle battery.What is OBD DTC?Prior to OBD, auto manufacturers did not standardize DTC's (diagnostic trouble code). OBD-I begins standardized DTC's OBD-II adds specific tests to determine the vehicles emission performance OBD-III adds more features, and is in the regulatory development phase.If the vehicle's onboard diagnostic system detects a malfunction, a DTC corresponding to the malfunction is stored in the vehicle's computer, as well as realtime data from the sensors connected to the on-board computer. In addition, the OBD-II interface provides a means to clear the DTC's once maintenance has been completed.
A service technician can retrieve the DTC, using a scan tool, and take appropriate action to resolve the malfunction. Prior to the advent of digital powertrain control modules, which is the technical enabler for the OBD feature, repairing a vehicle relied solely upon the technicians skill and service literature from the auto manufacturer. OBD-II connector specificationsThe OBD-II specification provides for a standartized hardware interface - the female 16-pin (2x8) J1962 connector.
Unlike the OBD-I connector, which was found under the hood of the vehicle, the OBD-II connector is located on the driver's side of the passenger compartment near the center console.Refer to related pinouts for vendor-specific OBD-2 pinouts.
This article needs additional citations for. Unsourced material may be challenged and removed.Find sources: – ( June 2009) On-board diagnostics ( OBD) is an 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 ' 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 (DTCs) which allow one to rapidly identify and remedy malfunctions within the vehicle. Contents.History. 1968: introduces the first on-board computer system with scanning capability, in their models. 1978: On-board computers begin appearing on consumer vehicles, largely motivated by their need for real-time tuning of systems.
Simple OBD implementations appear, though there is no standardization in what is monitored or how it is reported. 1980: implements a proprietary interface and for testing of the (ECM) on the vehicle assembly line. The 'assembly line diagnostic link' protocol broadcasts at 160. Implemented on California vehicles for the 1980 model year, and the rest of the United States in 1981. In most cases, the ECM (Engine Control Module) can be made to display DTCs (Diagnostic Trouble Code(s)) as a flashing pattern on the CEL (Check Engine Lamp) or MIL (Malfunction Indicator Lamp). 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 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 with signaling. This protocol is defined in GM XDE-5024B. 1988: The recommends a standardized diagnostic connector and set of diagnostic test signals.
1991: The (CARB) requires that all new vehicles sold in in 1991 and newer vehicles have some basic OBD capability. These requirements are generally referred to as 'OBD-I', though this name is 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 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 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 makes mandatory for all gasoline (petrol) vehicles sold in the European Union, starting in MY2001 (see Directive 98/69/EC ). 2003: The makes mandatory for all diesel cars sold in the European Union. 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.Standard interfaces ALDL.
Main article:GM's (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 is 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 used a 6 position Metripack 280 diagnostic jack. The GM Europe and used a 10 position Metripack 280 diagnostic jack.ALDL was not a standard. It was actually extremely fragmented. The information exchange changed with each (aka, ). (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 on-board 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 on-board 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, 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 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.
However, the DTCs of some OBD-I cars are interpreted in different ways. 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 engine computers are equipped with 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 used on some vehicles in 1994 and 1995. OBD 1.5 is a colloquialism. 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 (although they have two ), and have a subset of the OBD-II codes implemented. Type B female connectorThe 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's groove is interrupted in the middle. This prevents the insertion of a type A male plug into a type B female socket while allowing a type B male plug to be inserted into 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. Main article:OBD-II provides access to data from the (ECU) and offers a valuable source of information when troubleshooting problems inside a vehicle. The 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.
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. Individual manufacturers often enhance the OBD-II code set with additional proprietary DTCs.Diagnostic services Here is a basic introduction to the OBD according to ISO 15031-5:.
Service $01 is used to identify what powertrain information is available to the scan tool. Service $02 displays Freeze Frame data. Service $03 lists the emission-related 'confirmed' diagnostic trouble codes stored. It displays exact numeric, 4 digit codes identifying the faults. Service $04 is used to clear emission-related diagnostic information. This includes clearing the stored pending/confirmed DTCs and Freeze Frame data.
Service $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. Service $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. Service $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.
Service $08 could enable the off-board test device to control the operation of an on-board system, test, or component. Service $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. Service $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 dealership tools to vehicle telematic devices.Hand-held scan tools.
Simple, rugged multi-brand handheld scannerA 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 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 tuningMobile device-based tools and analysis. Typical simple USB KKL Diagnostic Interface without protocol logic for signal level adjustment.A -based OBD analysis tool that converts the OBD-II signals to serial data (USB or serial port) standard to PCs. The software then decodes the received data to a visual display. Many popular interfaces are based on the or STN 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 flexibilityThe extent that a PC tool may access manufacturer or vehicle-specific diagnostics varies between software products as it does between hand-held scanners.Data loggers. TEXA OBD log.
Small data logger with the possibility to read out the data later on PC via USB.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.
Monitoring of driver behaviour by operators.Analysis of vehicle 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.
Retrieved 4 November 2016. Retrieved 4 November 2016. McCord, Keith (2011). Retrieved 4 November 2016. (PDF).
Retrieved 4 November 2016. 刘立媛. Retrieved 4 November 2016. 1 August 2016.
Retrieved 4 November 2016. Retrieved 4 November 2016. Archived from on 5 March 2016.
Retrieved 10 April 2016. CS1 maint: Archived copy as title.
(PDF). Archived from (PDF) on 26 June 2011. Retrieved 12 March 2011. CS1 maint: Archived copy as title. Peter Gargano. Retrieved 4 November 2016.
Retrieved 4 November 2016. (PDF). Retrieved 4 November 2016. Retrieved 4 November 2016.
Retrieved 4 November 2016. Retrieved 4 November 2016. 1994 Corvette Service Manual, Book 2. General Motors Corporation. December 1993. Pp. 6E3–A–166: 6E3–A–223.
1994 Corvette Service Manual, Book 2. General Motors Corporation. 14 January 2006. Retrieved 4 November 2016.
^. Retrieved 4 November 2016. ^. Retrieved 4 November 2016. Publications Office of the European Parliament. Publications Office of the European Parliament.
Retrieved 4 November 2016. Australian Government ComLaw. Australian Government ComLaw. (PDF). Retrieved 4 November 2016. Retrieved 4 November 2016.
Retrieved 4 November 2016. 1 April 2012.
Retrieved 4 November 2016. Archived from on 3 October 2009. Retrieved 28 September 2009. CS1 maint: Archived copy as title. Bright, Peter (15 May 2010). Ars Technica.
Retrieved 23 Aug 2012. Koscher, Karl (May 2010). 2010 IEEE Symposium on Security and Privacy.:. Retrieved 24 Feb 2016. Marks, Paul (17 July 2013).
New Scientist. Retrieved 5 November 2013. ^. Retrieved 4 November 2016. Van den Brink, Rob.
Archived from (PDF) on 23 August 2014. Retrieved 5 August 2015. Travers, Jim (7 May 2015). Consumer Reports. Retrieved 29 May 2015.
Titcomb, James (6 July 2012). London: Daily Mail. Retrieved 23 August 2012. Torchinsky, Jason (6 July 2012).
Retrieved 28 August 2012. Fowler, Steve (September 14, 2012). Auto Express.
Retrieved 20 April 2017.Notes. Birnbaum, Ralph and Truglia, Jerry. Getting to Know OBD II.
New York, 2000. International. On-Board Diagnostics for Light and Medium Duty Vehicles Standards Manual. Pennsylvania, 2003.External links. Center for Automotive Science and Technology at Weber State University. OBD information for repair technicians, vehicle owners, and manufacturers.
Manufacturer Specific OBD-II diagnostics pinouts and compatibility information. Is My Car OBD2 Compatible and Supported by OBD Scanner/Software?