OBD II (Onboard Diagnostics second generation) is a government mandated system for monitoring emission failures. All 1996 and newer model year passenger cars and light trucks in the U.S. are OBDII-equipped, but the first applications were actually introduced back in 1994 on a limited number of vehicle models (see box). What makes OBDII different from all the self-diagnostic systems that proceeded it is that OBDII is strictly emissions oriented. In other words, it will illuminate the Malfunction Indicator Lamp (MIL) anytime a vehicle's hydrocarbon (HC), carbon monoxide (CO), oxides of nitrogen (NOX) or evaporative emissions exceed 1.5 times the federal test procedure (FTP) standards for that model year of vehicle. That includes anytime random misfires cause an overall rise in HC emissions, anytime the operating efficiency of the catalytic converter drops below a certain threshold, anytime the system detects air leakage in the sealed fuel system, anytime a fault in the EGR system causes NOX emissions to go up, or anytime a key sensor or other emission control device fails. In other words, the MIL light may come on even though the vehicle seems to be running normally and there are no real driveability problems. The main purpose of the MIL lamp on an OBDII-equipped vehicle, therefore, is to alert motorists when their vehicles are polluting so they will get their emission problems fixed. But as we all know, motorist are very good at ignoring warning lamps, even when steam is belching from under the hood or the engine is making horrible noises. That is why regulators want to incorporate OBDII into existing and enhanced vehicle emissions inspection programs. If the MIL lamp is found to be on when a vehicle is tested, it does not pass even if its tailpipe emissions are within acceptable limits. WHY OBDII? The problem with most vehicle inspection programs is that they were developed back in the 1980s to identify "gross polluters." The tests were designed primarily to measure idle emissions on carbureted engines (which are dirtiest at idle), and to check for only two pollutants: unburned hydrocarbons (HC) and carbon monoxide (CO). The pass/fail cut points that were established for the various model years were also made rather lenient to minimize the number of failures. Consequently, a lot of late model vehicles that should not be passing an emissions test are getting through anyway. Efforts to upgrade vehicle inspection programs to the new I/M 240 standards stalled because of a lack of public and political support. I/M 240 requires "loaded-mode" emissions testing on a dyno while the vehicle is driven at various speeds following a carefully prescribed driving trace. The tailpipe gases are then analyzed to check not only total HC and CO emissions (in grams rather than parts per million or percent), but also oxides of nitrogen (NOX). The total emissions for the entire 240-second driving cycle is averaged for a composite emission score that determines whether or not the vehicle passes the test. Also included is an evaporative purge flow test to measure the flow rate of the canister purge valve, and an engine off pressure test of the evaporative emission control system to check the fuel tank, lines and cap for leaks. The I/M 240 program was to have been required in most areas of the country that do not meet national ambient air quality (NAAQ) standards. But after the program faltered in Maine, many states balked and only some went ahead with the I/M 240 program. The cost and complexity of the I/M 240 program combined with less than enthusiastic public acceptance doomed it from the start. So most states are now using a simple OBD II plug-in test to check emissions compliance on 1996 and newer cars and trucks. HISTORY OF ONBOARD DIAGNOSTICS The origins of OBDII actually date back to 1982 in California, when the California Air Resources Board (ARB) began developing regulations that would require all vehicles sold in that state starting in 1988 to have an onboard diagnostic system to detect emission failures. The original onboard diagnostic system (which has since become known as OBDI) was relatively simple and only monitored the oxygen sensor, EGR system, fuel delivery system and engine control module. OBDI was a step in the right direction, but lacked any requirement for standardization between different makes and models of vehicles. You still had to have different adapters to work on different vehicles, and some systems could only be accessed with costly "dealer" scan tools. So when ARB set about to develop standards for the current OBDII system, standardization was a priority: a standardized 16-pin data link connector (DLC) with specific pins assigned specific functions, standardized electronic protocols, standardized diagnostic trouble codes (DTCs), and standardized terminology. Another limitation of OBDI was that it could not detect certain kinds of problems such as a dead catalytic converter or one that had been removed. Nor could it detect ignition misfires or evaporative emission problems. Furthermore, OBDI systems would only illuminate the MIL light after a failure had occurred. It had no way of monitoring progressive deterioration of emissions-related components. So it became apparent that a more sophisticated system would be required. The California Air Resources Board eventually developed standards for the next generation OBD system, which were proposed in 1989 and became known as OBDII. The new standards required a phase-in starting in 1994. The auto makers were given until the 1996 model year to complete the phase-in for their California vehicles. Similar standards were incorporated into the federal Clean Air Act in 1990 which also required all 49-state vehicles to be OBDII equipped by 1996 — with one loophole. The OBDII systems would not have to be fully compliant until 1999. So some 1996 OBDII systems may lack one of the features normally required to meet the OBDII specs, such as the evaporative emissions purge test. EARLY OBDII APPLICATIONS 1994 vehicles equipped with the early OBD II systems include Buick Regal 3800 V6, Corvette, Lexus ES3000, Toyota Camry (1MZ-FE 3.0L V6) and T100 pickup (3RZ-FE 2.7L four), Ford Thunderbird & Cougar 4.6L V8, and Mustang 3.8L V6. 1995 vehicles with OBDII include Chevy/GMC S, T-Series pickups, Blazer and Jimmy 4.3L V6, Ford Contour & Mercury Mystique 2.0L four & 2.6L V6, Chrysler Neon, Cirrus and Dodge Stratus, Eagle Talon 2.0L DOHC (nonturbo), and Nissan Maxima and 240 SX. Not all of these early applications were fully OBDII compliant, but they did include the major diagnostic features of current systems. OBDII HARDWARE CHANGES Don't think for a moment that OBDII is just a fancier version of self-diagnostic software. It is that and much, much more. OBDII-equipped vehicles typically have: Twice the number of oxygen sensors as non-OBDII vehicles (most of which are heated O2 sensors). The additional O2 sensors are located downstream of the catalytic converter. More powerful powertrain control modules, with either 16-bit (Chrysler) or 32-bit (Ford & GM) processors to handle up to 15,000 new calibration constants that were added by OBDII. Electronically Erasable Programmable Read Only Memory (EEPROM) chips that allows the PCM to be reprogrammed with revised or updated software changes using a terminal link or external computer. A modified evaporative emission control systems with a diagnostic switch for purge testing, or an enhanced EVAP system with a vent solenoid, fuel tank pressure sensor and diagnostic test fitting, More EGR systems with a linear EGR valve that is electronically operated and has a pintle position sensor. Sequential fuel injection rather than multiport or throttle body injection. Both a MAP sensor and MAF sensor for monitoring engine load and airflow. DIAGNOSTIC EQUIPMENT FOR OBD II To work on an OBDII-equipped vehicle, you must have an OBD II compliant scan tool. Many scan tools made prior to 1996 are not OBD II compatible and cannot be upgraded with a simple cartridge change. You need a hardware adapter for these older scan tools or a newer scan tool that is OBD II compatible. Dealer technicians don't have it any better. GM requires a Tech 2 scan tool for its 1996 and newer vehicles. The Tech 2 scan tool has a 9 parameter screen display, a 5 parameter freeze option for scrolling, bar graph and line chart capabilities, current data capture and the ability to store two snapshots (of data, not your wife and kids). Likewise, Chrysler has its DRB III tool, and Ford has its New generation Star tester for OBDII-equipped vehicles from 1994 and up. If you are looking for a good reference book on OBDII, GM has an excellent training manual "On-Board Diagnostics Generation Two" P/N 16030.02-1. The book costs $20 and is available through Mascotech Marketing Services, 1972 Brown Road, Auburn Hills, MI 48326 (1-800-393-4831). THE MALFUNCTION INDICATOR LAMP (MIL) Most technicians are pretty familiar with the operation of the "Check Engine" or "Malfunction Indicator Lamp" (MIL) on late model vehicles. But on OBDII-equipped vehicles, it may seem like the MIL lamp has a mind of its own. On 1996 General Motors J-, N- and H-body cars, several rental fleets have encountered problems with the MIL lamp coming on because motorists and fleet personnel have not been using the correct refueling procedure when filling the fuel tank with gas. On these cars, the OBDII system applies vacuum to the evaporative emissions control system to check for air leakage. If the gas cap is not tight or the tank is filled while the key is on or the engine is idling, it can trigger a false P0440 code causing the MIL light to come on. GM is advising its dealers and fleet customers to reflash the EEPROM with revised OBDII programming that waits to check the evaporative emissions system until the vehicle is in motion. Bad gas has also been causing some false MIL lights. When the vehicle is diagnosed, the te…

Fonte: AA1Car.com