On-Board Diagnostics (OBD) II Regulatory Update Mobile Source Control Division California Air Resources Board April 25, 2002 Sacramento, California.

  • Published on

  • View

  • Download


On-Board Diagnostics (OBD) II Regulatory UpdateMobile Source Control Division California Air Resources BoardApril 25, 2002Sacramento, CaliforniaOBD II BackgroundAdopted in 1989 On every 1996 and newer vehicle.Monitors virtually every emission related componentIlluminates warning light and stores fault info for repair techniciansStatus of OBD IIOn 100 million vehicles in the U.S. Over 3 trillion miles coveredFeedback indicates program is workingChart10.440. miles%Percentage of Cars With High MileageSheet119952001>100k44%60%>125k27%50%>150k17%41%Sheet2Sheet3LEV II and OBD II ProgramsLEV II program targets near zero fleet emissions for useful life (120k miles) Certification and In-Use Compliance programs verify useful life standardsOBD II program targets high mileage vehicles beyond useful lifeReasons for Proposed ChangesKeep pace with technology Areas for improvementProper OBD II performance is critical for I/MStronger enforcement neededOutlineTechnical requirements/revisionsRevisions affecting I/M and repair techniciansMalfunction thresholdsEnforcement strengtheningNOx Catalyst MonitoringCurrently, only HC conversion efficiency monitoredLEV II program requires 75% NOx reduction from LEV I programNOx conversion efficiency now needs to be monitoredNOx Catalyst MonitoringProposalPhase-in for LEV II vehicles2007 and subsequent model years 1.75 x HC or NOx standard (2.5x for SULEVs)2005 and 2006 model years3.5 x NOx standardWill refine existing catalyst monitoring approachCold Start Strategy and Secondary Air System MonitoringMost emissions occur at cold startMany emission control components and strategies affect catalyst warm-upPropose monitoring during warm-up 2006-2008 phase-in Additional Technical RevisionsDiesel catalyst and particulate matter (PM) trap monitoringMisfire monitoringVariable valve timing (VVT) Most changes required for 2005 and newer vehicles.OutlineTechnical requirements/revisionsRevisions affecting I/M and repair techniciansMalfunction thresholdsEnforcement strengtheningStandardization changesOBD II standardization requirementsScan tool communication, connector, fault codes, etc.Necessary in I/MHelp technicians make effective repairs Changes to help I/M programsEPA requires OBD II system in state I/M programs Improvements include:Electronic VINReadiness statusConnector locationCommunication ProtocolScan tools talk to vehicles via standardized protocolsController Area Network (CAN) protocolallowed in 2003 and required in 2008More data at faster ratesPhase-out of current protocolsHeavy-duty/medium duty communication protocol (J1939)Verification of Standardized RequirementsTesting of production vehiclesVerify compliance with standardized features necessary for I/M testingRequired for 2005 and newer vehiclesOutlineTechnical requirements/revisionsRevisions affecting I/M and repair techniciansMalfunction thresholdsEnforcement strengtheningMonitoring ThresholdsMajor OBD II monitors calibrated to 1.5 x standardIndustry wants higher levels for LEV II program vehiclesMonitoring Thresholds (cont.)LEV II/ULEV II standards do not necessitate less stringent thresholdsProposed thresholds necessary to achieve LEV II emission benefitsProduction vehicles already meet requirementsFlexibility to revise thresholds if necessarySULEV Monitoring ThresholdsProposed SULEV threshold of 2.5 x standard Accounts for current emission measurement technologyAllows same levels of individual component deterioration as ULEV IThree manufacturers selling SULEVs meeting these thresholdsNMOG ThresholdNMOG two11.51.511.51.512.58.25StandardStaff Proposed ThresholdIndustry ThresholdEmission StandardThreshold x StandardNOx11.51.511.56.428571428612.522.5Emission StandardProposed ThresholdIndustry ThresholdEmission StandardThreshold (x Standard)NOx ThresholdNox two0.30.450.450.070.1050.450.020.050.45StandardARB g/mile standardIndustry g/mile standardEmission StandardThreshold (x Standard)NOx ThresholdSheet1ARBIndustryBaselineARBIndustryARBIndustryBaselineARBIndustryNMOGthresholdthreshold??x Std??x StdNOxthresholdthreshold??x Std??x StdULEV I0.0550.0830.0831. II0.0550.0830.0831. ThresholdNMOG two11.51.511.51.512.58.25StandardProposed ThresholdIndustry ThresholdEmission StandardThreshold (x Standard)NMOG ThresholdsNOx11.51.511.56.428571428612.522.5Emission StandardStaff Proposed ThresholdIndustry ThresholdEmission StandardThreshold x StandardSheet1ARBIndustryBaselineARBIndustryARBIndustryBaselineARBIndustryNMOGthresholdthreshold??x Std??x StdNOxthresholdthreshold??x Std??x StdULEV I0.0550.0830.0831. II0.0550.0830.0831. Effectiveness of ThresholdsProposed thresholds are cost-effective:~ $5 per pound for 120k-230k milesIncludes costs to consumers and the emission benefit Industrys proposed thresholds:$4.75 to $6.50 per poundnearly 9 tons per day fewer emission reductionsOutlineTechnical requirements/revisionsRevisions affecting I/M and repair techniciansMalfunction thresholdsEnforcement strengtheningOBD II-Specific EnforcementEnforcement testing since 1994 model yearEnforced under OBD II and tailpipe proceduresExisting procedures not adequateOBD II Compliance and Enforcement Three Major ImprovementsIncrease in required testingStandardized method for measuring in-use performanceOBD II-specific enforcement proceduresProduction Vehicle Evaluation-Monitoring RequirementsIdentify defects earlyEvery diagnostic testedTesting early in productionProduction Vehicle Evaluation-Standardization RequirementsEnsure vehicles properly communicate OBD II informationDevelopment of Gold Standard test equipment Monitoring FrequencyStandardize method to measure frequencySoftware tracks how often monitoring occursMinimum frequency equates to detection within two weeksEnforcement RegulationSection 1968.5 is OBD II specific enforcement proceduresDetailed enforcement procedures to be followed by staffAddresses shortcomings of using tailpipe proceduresApplies to 2004 and subsequent model yearsEnforcement Procedures/CriteriaEstablishes specific testing proceduresDefines sampling and testing proceduresDefines criteria for determining compliance Eliminates provision to offset OBD II non-compliance with over-compliance on tailpipe emissions Enforcement -Remedial ActionCriteria to determine appropriate remedial actionRemedial action varies from nothing up to recall and finesMandatory recall if a major monitor is non-functional SummaryLEV II program fleet has near zero emissions.Fleet must be maintained at near zero emissions for entire lifeProposed changes are feasible and necessaryProposed enforcement regulation necessary for an effective OBD II program


View more >