OBD-II repair engine manager systems
OBD-II is an improvement over OBD-I inside both capability plus standardization.
The OBD-II specification delivers for a standardized hardware interface—the woman 16-pin J1962 connector.
The EOBD laws are the European similar of OBD-II, plus apply with all passenger vehicles of category M1
OBD-II (96 On) Engine Management Systems
OBD-II (96 On) Engine Management Systems by John H HaynesGet other OBD II technical manuals hereThis manual takes the mystery out of Second-Generation On-Board Diagnostic Systems allowing you to understand your vehicles OBD-II sytem plus what to do when the Check Engine light comes on from reading the code to diagnosing and fixing the problem. Includes a comprehensive list of computer codes. Computer-controlled car repair made easy! For all car and light truck models manufactured since 1996. - Understand your vehicle s On-Board Diagnositic system - How to deal with that Check Engine light--from reading the code to diagnosing and fixing the problem - Comprehensive computer codes list Diagnostic tools: - Powertrain management fundamentals - OBD-II monitors explained - Generic trouble codes that cover all models! - Manufacturer-specific trouble code
OBD-II
OBD-II by Al SantiniGet other OBD II technical manuals hereFor the first time there is a resource that offers complete extensive coverage of OBD-II and encompasses everything you need to know to succeed as a technician in the field! This exciting new offering combines coverage of the design of OBD-II its role in state emission testing failures diagnosis and repair and the setting of readiness monitors for a total learning solution. OBD-II: Functions Monitors and Diagnostic Techniques provides technicians with a solid working knowledge of the purpose and functions of the OBD-II by beginning with an overview of the technology and its role in on-the job tasks. Using this as a foundation more advanced topics are addressed including the extremely high-powered diagnostic abilities involving the various scanner modes as well as the hows and whys of setting readiness monitors. With numerous practical examples and an emphasis on world-wide vehicle coverage that does not limit explanations to specific manufacturers this book will prepare readers for success in the industry.
The OBD-II specification delivers for a standardized hardware interface—the woman 16-pin J1962 connector. Unlike the OBD-I connector, that was occasionally found beneath the bonnet of the car, the OBD-II connector is necessary with be inside 2 feet of the steering wheel. SAE J1962 defines the pinout of the connector as:
The EOBD laws are the European similar of OBD-II, plus apply with all passenger vehicles of category M1 initial registered in EU associate states because January 1, 2001 for petrol engined vehicles plus because January 1, 2004 for diesel engined vehicles.
For newly introduced models, the regulation dates used per year earlier - January 1, 2000 for petrol plus January 1, 2003 for diesel.
For passenger vehicles with a Gross Car Weight rating of better than 2500 kg as well as for light commercial cars, the regulation dates used from January 1, 2002 for petrol models, plus January 1, 2007 for diesel models.
The technical implementation of EOBD is basically the same because OBD-II, with all the same SAE J1962 diagnostic link connector plus signal protocols being utilized.
With Euro V plus Euro VI emission specifications, EOBD emission thresholds is lower than past Euro III plus IV.
The ADR 79/01 2005) standard is the Australian similar of OBD-II.
It applies with all cars of category M1 plus N1 with a Gross Car Weight rating of 3500 kg or less, registered from unique inside Australia plus yielded because January 1, 2006 for petrol engined vehicles plus because January 1, 2007 for diesel engined vehicles.
For newly introduced models, the regulation dates used per year earlier - January 1, 2005 for petrol plus January 1, 2006 for diesel.
The ADR 79/01 standard was supplemented by the ADR 79/02 standard that imposed tighter emissions restrictions, appropriate with all cars of class M1 plus N1 with a Gross Car Weight rating of 3500 kg or less, from July 1, 2008 for fresh models, July 1, 2010 for all models.
The technical implementation of the standard is basically the same because OBD-II, with all the same SAE J1962 diagnostic link connector plus signal protocols being utilized.
OBD-II provides access with information within the engine control device plus provides a useful source of info whenever troubleshooting difficulties inside a car. The SAE J1979 standard defines a system for requesting different diagnostic information along with a list of standard parameters which may be accessible within the ECU. The different parameters which are accessible are addressed by "parameter identification numbers" or PIDs that are defined inside J1979. For a list of standard PIDs, their definitions, as well as the formula with convert raw OBD-II output with meaningful diagnostic units, see OBD-II PIDs. Manufacturers are not needed with apply all PIDs indexed inside J1979 plus they are authorized with include proprietary PIDs which are not indexed. The PID request plus information retrieval program provides access with real time performance information and also flagged DTCs. For a list of generic OBD-II DTCs recommended by the SAE, see Table of OBD-II Codes. Individual producers frequently enhance the OBD-II code set with extra proprietary DTCs.
Below is a simple introduction with the OBD correspondence protocol according with ISO 15031:
Mode $01 is selected to find what powertrain info is accessible with the scan tool.
Mode $02 displays Freeze Frame information.
Mode $03 lists the emission-related "confirmed" diagnostic trouble codes stored. It exhibits actual numeric, 4 digit codes identifying the faults.
Mode $04 is employed with clear emission-related diagnostic info. This involves clearing the stored pending/confirmed DTCs plus Freeze Frame information.
Mode $05 displays the oxygen sensor monitor screen as well as the test results gathered regarding the oxygen sensor.
There are ten numbers accessible for diagnostics:
$01 Rich-to-Lean O2 sensor threshold voltage
$02 Lean-to-Rich O2 sensor threshold voltage
$03 Lower sensor voltage threshold for switch time measurement
$04 High sensor voltage threshold for switch time measurement
$05 Rich-to-Lean switch amount of time in ms
$06 Lean-to Rich change amount of time in ms
$07 Minimum voltage for test
$08 Maximum voltage for test
$09 Time between voltage transitions inside ms
Mode $06 is a Request for On-Board Monitoring Test Results for Continuously plus Non-Continuously Monitored System. There are usually a minimal value, a maximum value, along with a present value for every non-continuous monitor.
Mode $07 is a Request for emission-related diagnostic trouble codes recognized throughout present or last completed driving cycle. It allows the outside test equipment to get "pending" diagnostic trouble codes recognized throughout present or last completed driving cycle for emission-related components/systems. This really is chosen by service technicians following a car repair, plus following clearing diagnostic info to find test results following a single driving cycle with determine when the repair has fixed the condition.
Mode $08 may allow the off-board test device with control the surgery of a on-board program, test, or component.
Mode $09 is employed with retrieve car info. Among others, the following info is available:
VIN: Car ID
CALID: ID for the program installed found on the ECU
CVN: Number selected with check the integrity of the car software. The producer is responsible for determining the way of calculating CVN, e.g. utilizing checksum.
In-use performance counters
Gasoline engine : Catalyst, Primary oxygen sensor, Evaporating program, EGR program, VVT program, Secondary air program, plus Secondary oxygen sensor
Diesel engine : NMHC catalyst, NOx reduction catalyst, NOx absorber Particulate matter filter, Exhaust fuel sensor, EGR program, VVT program, Increase stress control, Fuel program.
Mode $0A lists emission-related "permanent" diagnostic trouble codes stored. As per CARB, any diagnostic trouble codes which is commanding MIL about plus stored into non-volatile memory shall be logged because a lasting mistake code.
A PC-based OBD analysis tool which converts the OBD-II data with serial information standard with PCs or Macs. The software then decodes the received information with a graphic show. Many common interfaces are based found on the ELM or STN1110 OBD Interpreter ICs, both of that read all five generic OBD-II protocols. Many adapters today employ the J2534 API permitting those to access OBD-II Protocols for both vehicles plus pickups.
Additionally with the functions of the handheld scan tool, the PC-based tools mostly offer:
Large storage ability for information logging plus alternative functions
Higher resolution screen than handheld tools
The ability with utilize numerous software programs adding flexibility
The extent a PC tool will access maker or vehicle-specific ECU diagnostics varies between software treatments because it does between handheld scanners.