![]() |
Code of Federal Regulations (Last Updated: July 5, 2024) |
![]() |
Title 40 - Protection of Environment |
![]() |
Chapter I - Environmental Protection Agency |
![]() |
SubChapter C - Air Programs |
![]() |
Part 86 - Control of Emissions from New and in-Use Highway Vehicles and Engines |
![]() |
Subpart S - General Compliance Provisions for Control of Air Pollution From New and In-Use Light-Duty Vehicles, Light-Duty Trucks, and Heavy-Duty Vehicles |
§ 86.1806-04 - On-board diagnostics.
-
Link to an amendment published at 79 FR 23708, Apr. 28, 2014.
This §86.1806-04 includes text that specifies requirements that differ from §86.1806-01. Where a paragraph in §86.1806-01 is identical and applicable to §86.1806-04 this may be indicated by specifying the corresponding paragraph and the statement “[Reserved]. For guidance see §86.1806-01.”
(a)-(g). [Reserved]. For guidance see §86.1806-01.
(h) Reference materials. The OBD system shall provide for standardized access and conform with the following Society of Automotive Engineers (SAE) standards and/or the following International Standards Organization (ISO) standards. The following documents are incorporated by reference, see §86.1:
(1) SAE material. (i) SAE J1850 “Class B Data Communication Network Interface,” (Revised, May 2001) shall be used as the on-board to off-board communications protocol. All emission related messages sent to the scan tool over a J1850 data link shall use the Cyclic Redundancy Check and the three byte header, and shall not use inter-byte separation or checksums.
(ii) Basic diagnostic data (as specified in §§86.094-17(e) and (f)) shall be provided in the format and units in SAE J1979 “E/E Diagnostic Test Modes—Equivalent to ISO/DIS 15031-5:April 30, 2002”, (Revised, April 2002).
(iii) Diagnostic trouble codes shall be consistent with SAE J2012 “Diagnostic Trouble Code Definitions—Equivalent to ISO/DIS 15031-6:April 30, 2002”, (Revised, April 2002).
(iv) The connection interface between the OBD system and test equipment and diagnostic tools shall meet the functional requirements of SAE J1962 “Diagnostic Connector—Equivalent to ISO/DIS 15031-3:December 14, 2001” (Revised, April 2002).
(v) All acronyms, definitions and abbreviations shall be formatted according to SAE J1930 “Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms” Equivalent to ISO/TR 15031-2:April 30, 2002”, (Revised, April 2002).
(vi) All equipment used to interface, extract and display OBD-related information shall meet SAE J1978 “OBD II Scan Tool” Equivalent to ISO 15031-4:December 14, 2001”, (Revised, April 2002).
(vii) As an alternative to the above standards, heavy-duty vehicles may conform to the specifications of the SAE J1939 series of standards (SAE J1939-11, J1939-13, J1939-21, J1939-31, J1939-71, J1939-73, J1939-81).
(2) ISO materials. Copies of these materials may be obtained from the International Organization for Standardization, Case Postale 56, CH-1211 Geneva 20, Switzerland.
(i) ISO 9141-2 “Road vehicles—Diagnostic systems—Part 2: CARB requirements for interchange of digital information,” (February 1, 1994) may be used as an alternative to SAE J1850 as the on-board to off-board communications protocol.
(ii) ISO 14230-4:2000(E) “Road vehicles—Diagnostic systems—KWP 2000 requirements for Emission-related systems”, (June 1, 2000) may also be used as an alternative to SAE J1850.
(iii) ISO 15765-4.3:2001 “Road Vehicles-Diagnostics on Controller Area Network (CAN)—Part 4: Requirements for emission-related systems”, (December 14, 2001) may also be used as an alternative to SAE J1850.
(i) [Reserved]. For guidance see §86.1806-01.
(j) California OBDII compliance option. For light-duty vehicles, light-duty trucks, and heavy-duty vehicles weighing 14,000 pounds GVWR or less, demonstration of compliance with California OBD II requirements (Title 13 California Code of Regulations §1968.2 (13 CCR 1968.2)), as modified, approved and filed on April 21, 2003, shall satisfy the requirements of this section, except that compliance with 13 CCR 1968.2(e)(4.2.2)(C), pertaining to 0.02 inch evaporative leak detection, and 13 CCR 1968.2(d)(1.4), pertaining to tampering protection, are not required to satisfy the requirements of this section. Also, the deficiency provisions of 13 CCR 1968.2(i) do not apply. The deficiency provisions of paragraph (i) of this section and the evaporative leak detection requirement of paragraph (b)(4) of this section apply to manufacturers selecting this paragraph for demonstrating compliance. In addition, demonstration of compliance with 13 CCR 1968.2(e)(16.2.1)(C), to the extent it applies to the verification of proper alignment between the camshaft and crankshaft, applies only to vehicles equipped with variable valve timing.
(k) [Reserved]. For guidance see §86.1806-01.
(l) Thresholds for California OBD II Compliance Option. For the purposes of complying with the provisions set forth above in paragraph (j), vehicles certified to Tier 2 standards shall utilize multiplicative factors from the California vehicle type (i.e. LEV II, ULEV II) corresponding to the Tier 2 to which the vehicles are certified. Vehicles certified to Tier 2, Bin 4 emissions standards shall utilize the Tier 2 Bin 4 emission standards and the CARB ULEV II multiplicative factors to determine the appropriate OBD malfunction threshold for all pollutants except NOX, for which they shall utilize that CARB SULEV II multiplicative factors. Vehicles certified to Tier 2, Bin 3 emissions standards shall utilize the Tier 2 Bin 3 emission standards and the CARB ULEV II multiplicative factors to determine the appropriate OBD malfunction threshold for all pollutants except NOX, for which they shall utilize that CARB SULEV II multiplicative factors. Vehicles certified to Tier 2, Bin 2 emissions standards shall utilize the Tier 2 Bin 2 emission standards and the CARB SULEV II multiplicative factors to determine the appropriate OBD malfunction threshold. Vehicles certified to Tier 2 Bin 7 or higher shall utilize the CARB LEV II multiplicative factors to determine the appropriate OBD malfunction threshold.
[68 FR 35799, June 17, 2003, as amended at 70 FR 75410, Dec. 20, 2005; 71 FR 51488, Aug. 30, 2006]