A detailed reference for understanding pass/fail criteria in OBD tests during Smog Check inspections, and troubleshooting vehicles with OBD testing complexities. Essential information for technicians working with code obd.
On this page:
A. Introduction to OBD Testing
B. Revision History of OBD Standards
C. OBD Test Pass/Fail Standards for Smog Check Inspections
D. Troubleshooting OBD Communication Issues: Vehicles of Interest
E. Addressing Permanent Diagnostic Trouble Codes (PDTCs)
F. BAR-97 EIS Specific Vehicle Information
A. Introduction to OBD Testing
This guide serves as an in-depth reference, offering a summary of the criteria that determine pass or fail outcomes in the On-Board Diagnostic (OBD) test segment of a Smog Check inspection. Furthermore, it provides crucial instructions for diagnosing vehicles known to present challenges during OBD testing. This document supersedes the previous “Smog Check OBDII Reference (Testability Issues),” formerly known as Appendix J, and is vital for anyone working with Code Obd and vehicle diagnostics.
It is important to note the following:
B. Revision History of OBD Standards
| Version | Section | Description of Changes | Date of Revision |
|---|---|---|---|
| 1.0 | N/A | Original document created. | 09/01/2015 |
| 2.0 | F | Added Section F: BAR-97 Vehicles of Interest, detailing specific models and years. | 01/22/2016 |
| 2.1 | C, E | Incorporated Permanent Diagnostic Trouble Code (PDTC) standards and introduced Section E: PDTC Vehicles of Interest for detailed PDTC information. | 04/26/2019 |
| 3.0 | E | Converted the reference guide to HTML format for improved accessibility. Table 3 was renamed to Table 3a, and Table 3.5 to Table 3b for clarity. Updated troubleshooting guidance for Chrysler, Dodge, Freightliner, Jeep, Mercedes, and Ram vehicles in Table 6, focusing on code obd related issues. | 09/08/2020 |
| 3.1 | D | Added 2020 and 2021 Ford Escape and Lincoln Corsair models (non-hybrid), excluding Type S trim levels, to the list of vehicles with OBD test considerations. | 12/21/2020 |
| 3.2 | D | Included the 2021 Ford Bronco Sport (all gasoline engines, non-hybrid) and 2020–2021 Ford E Series (all gasoline engines). Removed 2021 E/F 350 Cutaway & E/F 450 Stripped Chassis from the list. | 05/21/2021 |
| 3.3 | D | Added 2021 and 2022 Ford E 350 models (all gasoline engines, non-hybrid). Removed the 2020 – 2021 Ford E Series entry for better specificity. | 07/14/2021 |
| 3.4 | D | Revised the guidelines for 2020, 2021 Ford Escape and Lincoln Corsair models based on updated information. | 09/08/2021 |
| 4.0 | N/A | Introduced modified software standards to the OBD testing process. Updated the overall formatting of the reference for better readability. | 09/10/2021 |
| 4.1 | D | Added 2021, 2022 Ford E450 models to the vehicles requiring specific OBD testing considerations. | 09/21/2021 |
| 4.2 | D | Refined the guidance for 2020-2021 Ford Escape/Lincoln Corsair, 2021 Ford Bronco Sport, and 2021-2022 Econoline E-Series vehicles, particularly in relation to code obd diagnostics. | 02/10/2022 |
| 4.3 | C, D | Clarified the number of incomplete monitors permissible for 2007 and newer diesel vehicles, changing from “any two” to “Particulate Filter and NMHC.” Added information regarding vehicles exhibiting exhaust gas sensor and NOx aftertreatment system monitor readiness issues. | 07/05/2023 |
| 4.4 | D, F | Updated the lists for 2020-2022 Escape, 2021-2022 Bronco Sport, 2021-2023 E350, E450, F-650, F-750, and 2020-2022 Corsair models. Added 2020-2022 F-53 Motorhome, F-59 Commercial Stripped Chassis, and included a link to SSM 50974 for further details on code obd related software updates. | 09/11/2023 |
| 4.5 | D | Updated information for 2019 Chevrolet Express and 2014–2016 Dodge Ram ProMaster. Included a GMC Savana recall notice related to OBD system issues. | 11/02/2023 |
| 4.6 | D | Updated the section on 2015–2019 Ford Transit vehicles, focusing on specific OBD test concerns. | 11/08/2023 |
| 4.7 | D | Further updated the 2019 Chevrolet Express and GMC Savana, 2014-2016 Dodge Ram ProMaster, and 2015-2019 Ford Transit entries with the latest OBD testing information. | 11/23/2023 |
| 4.8 | D | Added 2010-2015 Dodge/Ram 2500/3500 6.7L diesel and updated 2011-2014 Dodge/Ram 3500 6.7L diesel sections with refined OBD diagnostic insights. | 12/23/2023 |
| 4.9 | E | Expanded Section E to include Chrysler 200, 300, Pacifica, Town and Country; Dodge Avenger, Caliber, Challenger, Charger, Grand Caravan, Dakota, Dart, Durango, Journey, Nitro; Jeep Cherokee, Commander, Grand Cherokee, Liberty, Patriot/Compass, and Wrangler; Ram 1500, 2500, 3500, and Promaster models, specifically addressing Permanent Diagnostic Trouble Codes. | 01/24/2024 |
| 5.0 | D | Revised 2017, 2018, and added 2019 Jaguar models. Updated 2017-2018 Land Rover and added 2018, 2019 Velar, highlighting dealer recalls for NOx aftertreatment readiness issues in 2.0 and 3.0 liter diesel engines. | 03/14/2024 |
| 6.0 | D | Introduced 2025 and newer Ford Explorer models and included OBD Test bypass information for OBDonUDS vehicles, a significant update for handling advanced code obd systems. | 09/21/2024 |
| 7.0 | D | Edited the 2015–2019 Ford Transit (diesel) section and added 2013-2016 Ford F Series Super Duty 6.7L (diesel), focusing on Exhaust Gas Sensor readiness bypass protocols for these models. | 10/05/2024 |
C. OBD Test Pass/Fail Standards for Smog Check Inspections
Understanding the pass/fail standards for the OBD test is crucial for accurate Smog Check inspections. This section details the readiness monitor standards, malfunction indicator lamp (MIL) standards, communication standards, permanent diagnostic trouble code (PDTC) standards, and modified software standards that dictate the outcome of an OBD test. A thorough grasp of these standards is essential for anyone working with code obd and vehicle emission systems.
Readiness Monitor Standards
Readiness monitors are integral self-tests within a vehicle’s OBD system, designed to confirm the operational status of emission control systems. While many vehicles automatically complete these monitors during typical driving conditions, some vehicles may encounter difficulties due to specific design requirements or driving patterns that don’t meet the necessary operating parameters. Vehicle owner’s manuals sometimes include procedures for completing these monitors, but often, this drive cycle information is exclusive to the Original Equipment Manufacturer (OEM) or found in specialized repair service literature.
Completing drive cycles requires specific vehicle operation conditions such as speed, temperature, pressure, and engine load. Due to these specific requirements, performing certain drive cycles in normal traffic may be challenging, making dynamometer equipment a valuable tool. Furthermore, monitor completion relies on properly functioning components. A vehicle may fail to complete a monitor until a comprehensive diagnosis and repair of the components that enable the monitor to function are carried out. It’s also important to remember that readiness monitors must be rerun after any repair work, such as disconnecting the vehicle’s battery or replacing emission-related components. These factors are critical when addressing code obd issues related to readiness monitors.
The following table outlines the permissible number of incomplete OBD readiness monitors that still allow a vehicle to pass the OBD test portion of a Smog Check inspection.
| Model Year | Fuel Type | Number of Incomplete Monitors Allowed to Pass OBD Test1 |
|---|---|---|
| 1996-1999 | Gas2 | Any one3 |
| 2000 and newer | Gas2 | Evaporative system3 |
| 1998-2006 | Diesel | Zero |
| 2007 and newer | Diesel | Particulate Filter and Non-Methane HydroCarbon (NMHC)4 |
1 Implemented May 4, 2015.
2 “Gas” includes gasoline, propane, natural gas (CNG, LNG, LPG).
3 The misfire, fuel, and comprehensive component continuous monitors are disregarded during an OBD test on “gas” vehicles.
4 Implemented July 5, 2023.
Malfunction Indicator Lamp Standards
The Malfunction Indicator Lamp (MIL), often referred to as the “Check Engine” light, plays a critical role in OBD testing. The MIL standards for BAR-97 and OIS inspections are outlined below. These standards are essential when interpreting code obd related to the MIL.
| Vehicle | Pass/Fail | Standard |
|---|---|---|
| All with OBDII | Pass | MIL illuminates when the key is turned to the ‘on’ position with the engine off (KOEO). |
| All with OBDII | Pass | MIL turns off once the engine is running (KOER). |
| All with OBDII | Fail | MIL fails to illuminate when the key is in the ‘on’ position with the engine off (KOEO). |
| All with OBDII | Fail | MIL remains illuminated when the engine is running (KOER). |
Communication Standards
Failure to establish communication with a vehicle’s OBD system during a Smog Check can occur for various reasons. These can range from physical issues like a damaged OBD connector or wiring, to more complex problems such as interference from aftermarket stereo systems, or incorrect responses from the vehicle’s transmission computer instead of the engine computer. Invalid data transmission from the vehicle can also lead to communication failures. These communication issues are often the first hurdle when diagnosing code obd problems.
The communication standards for the OBD test portion of BAR-97 and OIS inspections are detailed in the table below.
| Vehicle | BAR-97/OIS | Standard |
|---|---|---|
| All with OBDII | BAR-97 | Vehicle successfully communicates with the BAR-97 testing equipment. |
| All with OBDII | OIS | Vehicle communicates with the OIS and accurately transmits all required data.1 |
1 Required data typically includes information from OBD addresses: Mode $01 PID $00, Mode $01 PID $01. Mode $01 PID $00 provides data on supported parameters, while Mode $01 PID $01 returns MIL status, diagnostic trouble codes (DTCs), and monitor status.
Permanent Diagnostic Trouble Code Standards
Permanent Diagnostic Trouble Codes (PDTCs) were introduced into BAR-OIS Smog Check inspections on July 1, 2019. PDTCs are similar to regular Diagnostic Trouble Codes (DTCs) but differ significantly in their behavior. Unlike standard DTCs, PDTCs cannot be cleared by simply using a scan tool or disconnecting the vehicle’s battery. They are designed to remain until the OBD II system itself verifies that the underlying issue has been resolved. Understanding PDTCs is crucial when working with code obd in modern vehicles.
PDTCs can only be cleared by the vehicle’s OBD II system after it confirms that the previously detected fault is no longer present. This ensures that emission-related issues are genuinely fixed and not just temporarily masked. The standards related to PDTCs for the OBD test portion of an OIS inspection are outlined below.
| Model Year | BAR-97/OIS | Standard |
|---|---|---|
| 1996-1999 | BAR-97 | Not applicable. |
| 2000-2009 | OIS | Not applicable. |
| 2010 and newer 1 | OIS | Vehicles fail the Smog Check if a PDTC is present. 2,3,4,5 |
1 It’s important to note that some 2010 vehicles may not support PDTCs and therefore will not be subjected to the PDTC check.
2 A vehicle storing a PDTC will fail the PDTC check, regardless of whether the MIL is currently commanded ON or OFF.
3 The presence of a PDTC will be ignored if the vehicle has completed at least 15 warm-up cycles and has been driven a minimum of 200 miles since its OBD information was last cleared, as determined by Mode $01 PID $30 and $31.
4 BAR is aware of certain vehicles that experience issues with properly clearing specific PDTCs. BAR is collaborating with the California Air Resources Board (CARB) to ensure these known issues are addressed by vehicle manufacturers. Until a resolution is available, these codes will be disregarded by BAR-OIS. Further information can be found in Permanent Diagnostic Trouble Code Vehicles of Interest.
5 Vehicle manufacturers have issued extended warranties, recalls, and repair campaigns for some vehicles that have difficulties clearing PDTCs. These vehicles are listed under Permanent Diagnostic Trouble Code Vehicles of Interest. If one of these vehicles fails due to a PDTC, advise the vehicle owner to consult their dealer for repairs covered under these programs.
Modified Software Standards
A modified software check was incorporated into the BAR-OIS Smog Check inspection on July 19, 2021. Software that has been approved through a California Air Resources Board (CARB) Executive Order should not cause a vehicle to fail the modified software check. This measure is in place to ensure vehicles comply with emissions standards and that any software modifications are legitimate and approved. Detecting modified software is becoming increasingly important in code obd diagnostics and emission control.
Vehicles identified as having illegally modified software will fail the Smog Check inspection. The Vehicle Inspection Report (VIR) will indicate “Modified Software” as the overall inspection result. Once a vehicle is restored to an OEM-approved or CARB-approved software configuration, it can be retested at any licensed Smog Check station, unless BAR directs otherwise, in which case the vehicle may need to be taken to a Referee or STAR station. Consumers who wish to dispute inspection results can contact the Smog Check Referee at (800) 622-7733.
D. Troubleshooting OBD Communication Issues: Vehicles of Interest
This section provides a detailed list of gasoline, flex-fuel (model year 2000 and newer), and diesel vehicles (model year 1998 and newer) that have known issues related to the OBD test portion of an OIS inspection. These issues encompass a range of problems, including but not limited to: failure to communicate with the vehicle’s OBD system, incomplete readiness monitors, OBD test incompatibility, and false Malfunction Indicator Lamp (MIL) illumination. Understanding these vehicle-specific issues is crucial for technicians effectively diagnosing code obd problems and performing Smog Checks.
In many instances, the OIS inspection system is programmed to automatically accommodate vehicles with known design anomalies, allowing for a smoother inspection process. However, in other cases, the vehicle may require specific repairs or software updates to resolve the underlying issues. The table below provides a comprehensive guide to these vehicles, their specific issues, potential causes and remedies, and instructions for inspectors to handle these situations effectively.
| Make | Year | Model Engine (L); Fuel Type | Issue | Cause and Possible Remedy | Instruction to Inspector |
|---|---|---|---|---|---|
| Audi | 2000-2004 | A4 & A6 | Fail for no OBD communication. No response or Only Transmission Control Module responds to DADs requests. ABS and/or brake lamp illuminated in instrument panel cluster. | A broken ground bond wire within the ABS module is often the cause, leading to diagnostic communication problems across the ABS module, ECM, and TCM. Diagnose and repair according to Audi Technical Service Bulletin (TSB) #A45-15-10. | This issue likely indicates a vehicle malfunction. Repair as per TSB and then retest the vehicle’s OBD system. |
| BMW | 6/1/99 – 7/31/00 | 323i Sedan | May not pass inspection due to oxygen sensors readiness monitor not setting, being reported as not fitted, or not supported. | This issue is often due to a DME Software error. Reprogramming the DME with updated software is typically required to resolve this. | Inspect the DME “programmed control unit” number as listed in TSB #SI B12 16 16. Follow the instructions provided in the TSB for reprogramming if necessary. |
| BMW | 9/3/99 – 7/31/00 | 323iT Touring | May not pass inspection due to oxygen sensors readiness monitor not setting, being reported as not fitted, or not supported. | A DME Software error is the likely cause. Update the DME software to the latest version to rectify this issue. | Refer to TSB #SI B12 16 16 and check the DME “programmed control unit” number. Implement the TSB instructions for software reprogramming. |
| BMW | 6/1/99 – 7/29/00 | 323Ci Coupe | May not pass inspection because the oxygen sensors readiness monitor may not set, or is reported as not fitted or not supported. | This is usually attributed to a DME Software error. Reprogramming the DME with the correct software version should resolve the problem. | Consult TSB #SI B12 16 16 and verify the DME “programmed control unit” number. Adhere to the TSB guidelines for software update procedures. |
| BMW | 6/23/99 – 7/29/00 | 323 Cic Convertible | May fail inspection due to oxygen sensors readiness monitor issues: not set, not fitted, or not supported. | A DME Software error is commonly responsible. Reprogramming the DME with the updated software is the recommended solution. | Check the DME “programmed control unit” number against TSB #SI B12 16 16. Follow the TSB instructions for DME reprogramming. |
| BMW | 2000 | M52 (TU) engine | May not pass inspection because of oxygen sensors readiness monitor not set, not fitted, or not supported. | This problem is typically caused by a DME Software error. Updating the DME software is necessary for correction. | Verify the DME “programmed control unit” number using TSB #SI B12 16 16. Proceed with DME software reprogramming as per the TSB. |
| BMW | 2000 | Fail for readiness. Vehicle may not set oxygen sensor readiness monitor. | A software error within the ECM is the cause. Reflash the ECM according to Recall #00E-A01. Refer to BMW bulletin #SI B 12 15 99, dated November 2000, for detailed instructions. | The vehicle requires an ECM reflash. Perform the ECM reflash as per the recall to ensure the oxygen sensor monitor sets correctly. | |
| BMW | built 3/98 – 7/99 | 323i, 323iA, 328i, 328iA | Fail for readiness. Vehicle may not set oxygen sensor readiness monitor. | An ECM software error is the underlying issue. Reflash the ECM as per Recall #00E-A01. See BMW bulletin #SI B 12 15 99, dated November 2000, for specific details. | Vehicle requires ECM reflash. Reflash the ECM according to the recall to enable the oxygen sensor monitor. |
| BMW | built 2/99 – 7/99 | 328iC, 328iCA, 323iC, 323iCA, 528i, 528iA, 528iT, 528iAT | Fail for readiness. Vehicle may not set oxygen sensor readiness monitor. | A software error in the ECM is the reason. Reflash the ECM based on Recall #00E-A01. Consult BMW bulletin #SI B 12 15 99, from November 2000, for detailed steps. | ECM reflash is needed. Reflash the ECM as per the recall to ensure the oxygen sensor monitor functions. |
| BMW | built 9/98 – 7/99 | Z3 roadster 2.3 | Fail for readiness. Vehicle may not set oxygen sensor readiness monitor. | The issue stems from a software error in the ECM. Reflash the ECM following Recall #00E-A01. Refer to BMW bulletin #SI B 12 15 99, issued in November 2000, for instructions. | Vehicle needs an ECM reflash. Perform the reflash as per the recall so the oxygen sensor monitor will set. |
| BMW | built 4/99 – 7/99 | Z3 roadster coupe/ roadster 2.8 | Fail for readiness. Vehicle may not set oxygen sensor readiness monitor. | An ECM software error is the root cause. Reflash the ECM according to Recall #00E-A01. See BMW bulletin #SI B 12 15 99, dated November 2000, for specifics. | ECM reflash is required. Reflash the ECM as per recall instructions to ensure the oxygen sensor monitor sets. |
| BMW | 2001-2003 | Z3 M Roadster/coupe with S54 engine | Fail for no communication when ignition switched off/on. OBD communication is always possible with BMW DIS or GT1 tester. | A Voluntary Emissions Recall Campaign was initiated to reprogram the engine control units (DME) on all affected vehicles. See Bulletin #SI B12 11 06 dated October 2007 for details. | Follow the OIS prompts carefully. Try connecting/disconnecting the DAD when the key is off as instructed by the OIS. |
| BMW | 2000-2003 | Z8 & M5 with S62 engine | Fail for no communication when ignition switched off/on. OBD communication is consistently achievable with BMW DIS or GT1 tester. | A Voluntary Emissions Recall Campaign is in place to reprogram the engine control units (DME) on all affected vehicles. Refer to Bulletin #SI B12 11 06 dated October 2007 for more information. | Adhere to OIS prompts during testing. Attempt to connect/disconnect the DAD with the key off, as guided by the system. |
| BMW | From series intro. up to 8/27/2004 | M3 with S54 engine | Fail for no communication when ignition switched off/on. OBD communication remains available with BMW DIS or GT1 tester. | A Voluntary Emissions Recall Campaign was launched to address this by reprogramming the engine control units (DME) on all affected vehicles. See Bulletin #SI B12 11 06 from October 2007 for specifics. | Comply with OIS prompts during the test. Follow instructions to connect/disconnect the DAD when the key is off. |
| BMW | 2003 | M3 | Failure to set EGR monitor. | A malfunctioning thermostat is a potential cause. | This indicates a likely vehicle fault. Diagnose the thermostat and related systems, repair as necessary, and then retest the OBD system. |
| BMW | 2007 | 328i | Engine dies during OBD Test and won’t restart. | This issue may be related to keyless ignition systems. Separate the vehicle and key fob by ensuring the wireless key fob is out of range for 20+ minutes. Then, attempt to restart. | Test the vehicle normally. BAR-OIS will not request Cal ID or CVN in these cases. If the issue is keyless ignition related, the vehicle should recover after sitting for 20+ minutes with the key fob away. |
| Chevrolet | 1998-2005 | DIESEL C/K2500 & C/K3500 (including Silverado and Suburban), G30, G3500 (including Sport Van, Express Cut-Away & Cargo), P30 | Federal diesel vehicle over 8,500 GVWR is not OBD-II certified. | Federal diesel vehicles exceeding 8,500 lbs GVWR in these years were not designed to meet OBD-II or Federal OBD standards. | Conduct the test normally. BAR-OIS is programmed to ignore incomplete continuous monitors on these vehicles. If communication fails, use the bulb check result for the overall OBD Test outcome if the analyzer provides this option. |
| Chevrolet | 1999-2005 | 3500 W35042 (box truck) [GVWR 10,001 – 14,000] (diesel) [Federal certified] | Vehicle is not equipped with OBD II. | OBD systems were not installed in federally certified vehicles of this type during these model years. | OIS is programmed to bypass the OBD functional test for these specific vehicles. |
| Chevrolet | 2000-2002 | S-10 (2WD), 2.2L I-4 (E85) | Monitors won’t set on certain flex fuel models, VINs listed below: YGMXT02.2121 YGMXT02.2122 1GMXT02.2122 2GMXT02.2122 YGMXT02.2121 YGMXT02.2122 (VIN 8th digit: 5) | System monitors are disabled for operation on fuel blends greater than E15 for O2 Sensor Heater, Secondary Air, and Catalyst. For blends over E10, the Evaporative leak check is disabled. A desensitized O2 Sensor monitor is implemented, reporting faults only during operation with E15+ blends. | OIS is set to ignore all 11 readiness monitors for these models due to their flex-fuel characteristics and monitor management. |
| Chevrolet | 2000-2005 | Suburban, Silverado, Express, Avalanche (gasoline) [Federal certified] | A message may appear during the OIS OBD II test: “Unable to confirm this Vehicle’s OBD II requirements. Does this vehicle have OBD II?” | Federally certified vehicles from this period may not be fully certified to OBD II standards despite having OBD capabilities. | Check the under-hood emission label to ascertain the vehicle’s OBD certification status. Input the correct result into OIS and follow the system prompts. OIS may indicate that a BAR-97 test is required for vehicles without full OBDII certification. |
| Chevrolet | 2001 | Silverado / Tahoe C/K 1500 | Failure to set secondary air system monitor. | This could be due to an air injection problem. Inspect the check valve(s), vacuum line, pump, and air passages for faults. | Diagnose the secondary air system thoroughly. Repair any identified issues and then retest the vehicle. |
| Chevrolet | 2002 | Silverado C/K 2500HD (diesel) | Failure to set EGR monitor. | This model has a difficult drive cycle for setting the EGR monitor, making it challenging to complete under normal conditions. | OIS was reprogrammed on 10/13/2016 to accommodate this issue by allowing the EGR monitor to remain incomplete for this specific vehicle. |
| Chevrolet | 2001-2002 | Cavalier CNG First VIN digit “3” (built in Mexico) | Failure to set CAT monitor. | This is a known vehicle design anomaly specific to these CNG models built in Mexico. | OIS was reprogrammed on 02/11/2015 to address this by allowing any one monitor to be incomplete during the OBD test for these vehicles. |
| Chevrolet | 2019 | Express 2.8L (diesel) [California certified] | Exhaust Gas Sensor monitor will not complete. A Particulate Matter sensor fault might not set a DTC or illuminate the MIL. | The Engine Control Module (ECM) may not correctly process diagnostic information from the exhaust Particulate Matter (PM) sensor. Dealers are instructed to reprogram the ECM as per Emission Recall N232408230 to fix this. | Vehicle requires an ECM reflash. Ensure the recall is performed by a dealer and then retest the vehicle to verify the fix. |
| Chrysler | 1999-2000 | Town & Country with 3.0L engine built after 12/1/1998 | EGR Monitor will not complete at high altitude. | A reflash is available to correct this. Confirm all systems are functioning correctly, then erase and reprogram the PCM according to TSB 18-03-00. | Vehicle needs a PCM reflash. Repair as per the TSB, run the necessary monitors, and then retest the vehicle. |
| Chrysler | 2000 | Town and Country 3.3L V-6 (E-85) | Readiness monitors will not set on certain flex fuel models, VINs listed below: WCRXT03.32BP (VIN 8th digit: G) | All monitors are disabled for operation on fuel blends exceeding E30 and during ethanol fuel content learning phases. | OIS is programmed to ignore all 11 readiness monitors for these specific flex-fuel models due to their unique monitor management system. |
| Chrysler | 2003 | PT Cruiser 2.4 liter DOHC 16v turbocharged (sales code EDV) with 5- spd manual G288 trans (sales code DDD) | Failure to set catalyst monitor. | This is due to a PCM software error. The dealer must reprogram the PCM. The emissions warranty for this issue has been extended to lifetime. Diagnose and repair as described in TSB #18-112-16. Possible repair payment reimbursement may be available; see warranty D-16-26. | Vehicle necessitates a PCM reflash. Repair according to the TSB and then retest. Inform the customer about the lifetime warranty and potential reimbursement. |
| Chrysler | 2010 built prior to 2/20/2010 | 300, Charger, Challenger 3.5L (5 speed automatic transmission) | Fail for monitor readiness, Or MIL illumination: P0456, P0452, P1115. | A reflash is available to address these issues. Refer to Chrysler TSB #18-008-10 for details and the correct procedure. | Vehicle requires a reflash. Perform the repair as per the TSB and then retest to ensure all monitors are set and the MIL issue is resolved. |
| Dodge | 1998-2002 | Ram Truck 5.9L (Cummins diesel) [California certified] | Some continuous monitors will not complete. | This is a vehicle design anomaly inherent to these models. | Test normally. BAR-OIS is programmed to allow one incomplete continuous monitor for these vehicles due to their design limitations. |
| Dodge | 1998-2006 | Ram 2500, Ram 3500 (diesel) [Federal certified] | Federal diesel vehicle over 8,500 GVWR is not OBD-II certified. | Federal diesel vehicles over 8,500 lbs GVWR from these years were not manufactured to comply with OBD-II or Federal OBD standards. | Conduct the OBD test as usual. BAR-OIS will ignore incomplete continuous monitors. If the vehicle fails to communicate, use the bulb check result as the OBD Test outcome if the analyzer provides this option. |
| Dodge | 1999-2000 | Caravan with 3.0L engine built after 12/1/1998 | EGR Monitor will not complete at high altitude. | A reflash is available to rectify this. Verify all systems are functioning correctly, then erase and reprogram the PCM following TSB 18-03-00. | Vehicle needs a PCM reflash. Repair according to the TSB, run the monitors to completion, and then retest. |
| Dodge | 2003 | Dakota, Durango and Ram Trucks with 4.7L engine [California or 50 state certified] | Catalyst monitor readiness status shows as not supported. | This is a vehicle fault. Repair as per TSB #18-032-10, which includes a lifetime warranty for this specific issue. | Test normally. OIS is programmed to ignore unsupported monitors, so the ‘not supported’ status for the catalyst monitor will not cause a failure. |
| Dodge | 2003 | Ram Truck 5.9L (Cummins diesel) [California certified] | MIL light is commanded on, but check engine light is not illuminated and no DTCs are stored. | This is a vehicle design anomaly. Recall campaign #K01 for an ECM reflash applies specifically to California certified vehicles to address this issue. | Test normally. OIS is programmed to ignore MIL Command if no DTCs are present on this vehicle. Advise the motorist about Recall Campaign #K01 if their vehicle is California certified. |
| Dodge | 2003-2004 | 25004X2 and Sprinter 35004X2 (diesel) [2003 Federal certified] [2004 Federal certified] | Federal diesel vehicle over 8,500 GVWR is not OBD-II certified. | Federal diesel vehicles over 8,500 lbs GVWR in these years were not built to comply with OBD-II or Federal OBD standards. | Perform the OBD test normally. BAR-OIS will disregard incomplete continuous monitors. In case of communication failure, use the bulb check result for the overall OBD Test outcome if the analyzer offers this option. |
| Dodge | 2004-2005 built after 12/7/2003 | Ram Truck 5.9L (Cummins diesel) [California certified] | Comprehensive component monitor will not complete. | This is a vehicle design anomaly. A re-flash is available as per TSB #18-030-10, with a lifetime warranty provided under TSB #18-003-11. | Test as usual. OIS allows one incomplete readiness monitor. Inform the vehicle owner about the available fix with a lifetime warranty as per TSB #18-003-11. |
| Dodge | 2004-2006 | 2500 3500 Sprinter (diesel) | EGR/VVT monitor will not complete. | This issue is due to an ECU software error affecting the EGR/VVT monitor’s operation. | Test normally. OIS is programmed to ignore the EGR/VVT monitor for these specific vehicles due to the known software issue. |
| Dodge | 2005 | Ram Truck 5.9L (Cummins diesel) [Federal certified] | Misfire and Comprehensive Components monitors will not complete. | This is a vehicle design anomaly inherent to these models. | Test normally. OIS is programmed to ignore both the misfire and comprehensive component monitor readiness for these specific vehicles. |
| Dodge | 2006-2007 | Ram Truck 5.9L, 6.7L (Cummins diesel) [California certified] | Fuel System and Comprehensive Components monitors will not complete. | Recall campaign #K01, involving an ECM reflash, addresses this issue but applies only to California certified vehicles. | Test normally. OIS ignores fuel and comprehensive component monitor readiness for these vehicles. Advise the motorist of Recall Campaign #K01 if their vehicle is California certified. |
| Dodge | 2006-2007 | Ram Truck with 5.9L (ETC or ETH) built after 1/1/06, [Federal Certified], Cab Chassis with 6.7L (ETJ) built before 1/11/07 (Cummins diesel) [Federal certified] | Fuel System and Comprehensive Components monitors will not complete. | TSB #18-017-10, providing an ECM reflash, is available for Federal certified vehicles to resolve this. | Test normally. OIS is set to ignore fuel and comprehensive component monitor readiness. Inform the vehicle owner about TSB #18-017-10 if their vehicle is Federal certified. |
| Dodge | 2010 built before 2/20/10 | 300, Charger, Challenger 3.5L (5 speed automatic transmission) | Evaporative monitor will not set. | The Evaporative leak detection monitor may not reach a ‘ready’ status under normal driving conditions. | Test normally. Inform the consumer about TSB #18-008-10 Revision A, which may offer a solution to this issue. |
| Dodge/Ram | 2010-2015 | 2500 & 3500 6.7L (diesel) [California certified] | NOx after-treatment monitor will not complete. | This is a vehicle design anomaly specific to these models. | Test normally. BAR-OIS temporarily allows the NOx after-treatment monitor to be incomplete until a vehicle manufacturer remedy becomes available. |
| Dodge/Ram | 2014 | ProMaster 2500 & 3500 High 3.0L (diesel) [California certified] | Exhaust Gas Sensor monitor will not complete. | This is a vehicle design anomaly. Dealers are required to perform Recall V97 and ZC0 to address this issue. | Vehicle requires a reflash. Ensure the recalls are performed by a dealership and then retest the vehicle to confirm resolution. |
| Dodge/Ram | 2015 | ProMaster 1500, 2500, & 3500 High & Standard 3.0L (diesel) [California certified] | Exhaust Gas Sensor monitor will not complete. | This is a vehicle design anomaly. Dealers are mandated to carry out Recall V97 to correct this. | Vehicle requires a reflash. Perform the specified recall at a dealership and then conduct a retest to ensure the issue is resolved. |
| Dodge/Ram | 2016 | ProMaster 2500 & 3500 High 3.0L (diesel) [California certified] | Exhaust Gas Sensor monitor will not complete. | A vehicle design anomaly is the cause. Dealers are instructed to perform Recall V97 to rectify this. | Vehicle requires a reflash. Have the recall performed at a dealership and then retest the vehicle to verify the fix. |
| Ford | 1998-2003 | Truck 7.3L (diesel) | Engine could shut off when requesting Mode $09 data with aftermarket scan tool. | This is a vehicle design anomaly that can cause engine shutdown under specific conditions. | Test normally. OIS is programmed to skip the Mode $09 data request on these vehicles to prevent this issue. |
| Ford | 1998-2004 | F250, F350, E350, E450, E Super Duty, Econo Commercial S- Duty, Econo RV S- Duty (diesel) [Federal certified] | Federal diesel vehicle over 8,500 GVWR is not OBD-II certified. | Federal diesel vehicles exceeding 8,500 lbs GVWR from these years were not designed to comply with OBD-II or Federal OBD standards. | Conduct the OBD test as usual. BAR-OIS will ignore incomplete continuous monitors. If communication fails, use the bulb check result as the OBD Test outcome if your analyzer offers this option. |
| Ford | 2000-2004 | F250, F350, E350, Excursion (gasoline) [Federal certified] | A message may appear during the OBD II test: “Unable to confirm this Vehicle’s OBD II requirements. Does this vehicle have OBD II?” | Federally certified vehicles of these models may not be fully certified to OBD II standards despite having OBD capabilities. | Inspect the under-hood emission label to determine the vehicle’s OBD certification status. Input the correct type into OIS and follow the system prompts. OIS might indicate that a BAR-97 test is needed for vehicles without OBDII certification. |
| Ford | 2003 | Focus | Fail for readiness. | Monitors may be particularly difficult to complete on this model, requiring specific conditions. | This indicates a potential vehicle issue. Reflash the PCM as per TSB #06-7-5. Then, test normally to see if the monitors can now be set. |
| Ford | 2004 | E350 Super duty 5.4 (gas) | Failure to set CAT monitor. | This is a vehicle design anomaly. Recall #15E06, dated 1/13/2016, may be applicable. Reflash the ECM to ensure the CAT monitor sets correctly. | Vehicle requires an ECM reflash. Repair as per the recall instructions and then retest the vehicle to confirm the CAT monitor issue is resolved. |
| Ford | 2011 | Edge, Explorer 3.5L & 3.7L | Vehicle fails for readiness. Some vehicles do not set readiness monitors. | Some vehicles may clear OBD-II diagnostic data on every engine start or incorrectly report the VIN, leading to readiness monitor issues. Reprogram or update the vehicle’s calibration. Perform a monitor drive cycle after updating. | Consult Ford Emission Recall #13E04 to check applicability. The owner must ensure the recall is performed if needed and all monitor drive cycles are completed before Smog Check testing. |
| Ford | 2013-2016 | F series, Super Duty 6.7L (diesel) | Exhaust Gas Sensor monitor will not complete. | After replacing the DOC or DPF, the EGS monitor will not run until the degreening strategy completes, which can take 6,000 to 10,000 miles of driving. | Test normally. OIS will ignore the incomplete EGS monitor on specific VINs provided by Ford where the DOC or DPF were replaced after January 1, 2022. This accommodation expires on 10/8/2025. Other vehicles are currently under investigation. |
| Ford | 2015-2019 | Transit 3.2L (diesel) | Exhaust Gas Sensor monitor will not complete. | Similar to the F-Series Super Duty, after DOC or DPF replacement, the EGS monitor requires a degreening strategy completion of 6,000 to 10,000 miles. | Test normally. OIS will ignore the incomplete EGS monitor for certain VINs from Ford, specifically when the DOC or DPF were replaced post-January 1, 2022. This is valid until 10/8/2025. Ongoing investigations are being conducted for other vehicles. |
| Ford | 2020-2022 | Escape; all engines; Gasoline and hybrid | Might not communicate with BAR-OIS. | This communication issue is a design problem. A software update is available to resolve it. | Test normally. If the vehicle fails the OBD test due to no communication, direct the owner to a Ford dealership for a software update. The issue may be related to the gateway module software—see SSM 50974 for more details. Similar messaging will be displayed on the OIS during inspection and printed on the VIR for consumers. |
| Ford | 2021-2022 | Bronco Sport; all engines; Gasoline (not hybrid) | Might not communicate with BAR-OIS. | A design issue is causing communication problems. A software update is available to correct this. | Test normally. If the vehicle fails the OBD test for lack of communication, advise the vehicle owner to visit a Ford dealership for a software update. This issue may be due to gateway module software—refer to SSM 50974. Corresponding messages will appear on the OIS during the inspection and on the VIR. |
| Ford | 2021-2023 | E350, E450; all engines; Gasoline (not hybrid) | Might not communicate with BAR-OIS. | A design issue is the root cause. A software update is available from Ford to fix this. | Test normally. Should the vehicle fail the OBD test because of no communication, instruct the vehicle owner to take it to a Ford dealership for a software update. The problem may be related to the gateway module software—see SSM 50974. Similar messages will be shown on the OIS and printed on the VIR. |
| Ford | 2025 and newer | Explorer (2.3L) AWD, RWD. Test Group SFMXT02.34K2. | Fail for no OBD communication. | These vehicles use OBDonUDS (OBD over UDS protocol), which is incompatible with DAD 1.0 units. | Cal-VIS software is programmed to skip the OBD test for these vehicles until DAD 2.0 units are BAR certified and available for use. |
| Freightliner | 1998-2004 | M Line Walk In Van [GVWR 6,001-14,000] (diesel) [Federal certified] | Vehicle is not equipped with OBD II. | OBD was not a requirement for federally certified vehicles in this GVWR range during these years. | OIS is programmed to skip the OBD functional test for these vehicles as they are not equipped with OBD II systems. |
| Freightliner | 2004-2006 | Sprinter (diesel) | EGR/VVT monitor will not complete. | An ECU software error is preventing the EGR/VVT monitor from completing its cycle. | Test normally. OIS will ignore the EGR/VVT monitor status for these vehicles due to the known ECU software issue. |
| GM | 2000 – 2008 | Various models, and Silverado 1500 | OIS prompts for no vehicle voltage. | Lack of power at the vehicle’s OBDII connector (DLC pin 16) is indicated. A blown fuse is a likely cause. | Use auxiliary DAD cables or a power supply as instructed by the DAD manufacturer to provide power to the OBD system and proceed with the test. |
| GM | 2015-2017 | All gasoline powered | Fail for readiness. | The post catalyst oxygen sensor monitor will not run until after a 1,000-mile catalyst break-in period. See Bulletin #15-NA-010 for more details. | Inspect the vehicle’s mileage. If it’s under 1,000 miles, advise the owner to return after reaching this mileage or send the vehicle to a Referee for inspection. |
| GMC | 1998-2005 | DIESEL C/K2500 & C/K 3500 (including Suburban and Sierra), Savana G3500, Workhorse P30 Forward Cntl | Federal diesel vehicle over 8,500 GVWR is not OBD-II certified. | Federal diesel vehicles over 8,500 lbs GVWR in these years were not designed to meet OBD-II or Federal OBD standards. | Perform the OBD test normally. BAR-OIS will disregard incomplete continuous monitors. If communication fails, use the bulb check result for the OBD Test outcome if the analyzer supports this. |
| GMC | 1999-2005 | W3500 W35042 (box truck) [GVWR 10,001 – 14,000] (diesel) [Federal certified] | Vehicle is not equipped with OBD II. | OBD was not required for federally certified vehicles in this GVWR range during these model years. | OIS is programmed to skip the OBD functional test for these vehicles as they lack OBD II systems. |
| GMC | 2000-2002 | Sonoma (2WD), 2.2L I-4 (E85) | Monitors wont set on certain flex fuel models, VINs listed below: YGMXT02.2121 YGMXT02.2122 1GMXT02.2122 2GMXT02.2122 YGMXT02.2121 YGMXT02.2122 (VIN 8th digit: 5) | System monitors are disabled for operation on fuel blends greater than E15 (O2 Sensor Heater, Secondary Air, Catalyst) and E10 (Evaporative leak check). A desensitized O2 Sensor monitor is active, reporting faults only with E15+ blends. | OIS ignores all 11 readiness monitors for these flex-fuel models due to their specific monitor calibration for ethanol blends. |
| GMC | 2000-2005 | Sierra, Yukon, Savana (gasoline) [Federal certified] | A message may appear during the OIS OBD II test stating, “Unable to confirm this Vehicle’s OBD II requirements. Does this vehicle have OBD II?” | Federally certified vehicles from this era may not be fully OBD II certified, despite having some OBD functionalities. | Check the under-hood emission label to confirm OBD certification status. Enter the correct type into OIS and follow the prompts. OIS might indicate a BAR-97 test is needed if the vehicle lacks full OBDII. |
| GMC | 2002 | Sierra C/K 2500HD (diesel) | Failure to set EGR monitor. | The EGR monitor drive cycle for this model is particularly difficult to complete under normal driving conditions. | OIS was reprogrammed on 10/13/2016 to address this by allowing the EGR monitor to be incomplete for this specific vehicle model. |
| GMC | 2019 | Savana 2.8L (diesel) [California certified] | Exhaust Gas Sensor monitor will not complete. A Particulate Matter sensor fault may not set DTC or illuminate MIL. | The ECM might not properly process diagnostic data from the exhaust Particulate Matter (PM) sensor. Dealers are required to reprogram the ECM as per Emission Recall N232408230. | Vehicle requires an ECM reflash. Ensure the recall is performed at a dealership and then retest the vehicle to confirm the issue is resolved. |
| GMC | 2022 | Sierra K2500 SLT 6.6L (diesel) [California certified] | Exhaust Gas Sensor monitor will not complete. | This issue is due to a vehicle design anomaly affecting the Exhaust Gas Sensor monitor. | Test normally. BAR-OIS temporarily allows the Exhaust Gas Sensor monitor to be incomplete until a permanent remedy is provided by the manufacturer. |
| Hyundai | 2002 | Sonata | Fail for readiness. | Monitors are notably difficult to complete on this model. Performing the drive cycle two times may be necessary. | Run the specified drive cycle as detailed in TSB #02-36-030. If monitors still do not set, further diagnosis may be required. |
| Hyundai | 2003 | Tiburon | Will not communicate with generic OBD test equipment. | Pin 5 in the DLC is not grounded, which is necessary for communication with generic OBD tools. Ground pin 5 by jumping it to pin 4 in the DLC as per the TSB. | Test normally on OIS, which is designed to handle this. If using generic OBD test equipment, perform recall campaign #057 and Hyundai TSB #03-01-003-01 to address the grounding issue. |
| Infiniti | 2000 -2001 | I30 | Failure to set catalyst monitor. | The OBD catalyst code may only be visible with an OEM scan tool, not generic tools. | Test the catalyst system using appropriate diagnostic equipment. Replace the catalyst if it is found to be defective. |
| Infiniti | 2000 -2001 | I30 | Fail for readiness. | This vehicle model has difficulty completing all readiness monitors during normal driving conditions. | Perform the specified drive cycle to attempt to set the readiness monitors. This may require specific driving conditions as outlined in service information. |
| Isuzu | 1998-2005 | NPR [GVWR 10,001- – 14,000] (diesel) [Federal certified] | Vehicle is not equipped with OBD II. | OBD was not mandated for federally certified vehicles in this GVWR range during these model years. | OIS is programmed to skip the OBD functional test for these vehicles as they are not equipped with OBD II systems. |
| Isuzu | 2000-2002 | Hombre (2WD) 2.2L I-4 (E85) | Monitors wont set on certain flex fuel models, VINs listed below: YGMXT02.2121 YGMXT02.2122 1GMXT02.2122 2GMXT02.2122 YGMXT02.2121 YGMXT02.2122 (VIN 8th digit: 5) | System monitors are disabled for operation on fuel blends > E15 (O2 Sensor Heater, Secondary Air, Catalyst) and > E10 (Evaporative leak check). A desensitized O2 Sensor monitor is implemented, reporting faults only with E15+ blends. | OIS ignores all 11 readiness monitors for these flex-fuel models due to their specific monitor strategies for higher ethanol blends. |
| Jaguar | 2017 | Jaguar XE, XF, & F-Pace 2.0L (diesel) [California certified] Test Group HJLXJ02.0STY | NOx Aftertreatment System monitor will not complete. | This is a vehicle design anomaly. Dealer recall H444 was issued to address this. | Test normally. If the vehicle fails the OBD test due to an incomplete NOx aftertreatment monitor, direct the owner to a Jaguar dealership for a software update under recall H444. |
| Jaguar | 2018 | Jaguar XE, XF, F-Pace & Rover Velar 2.0L (diesel) [California certified] Test group JJLXJ02.0STY | NOx Aftertreatment System monitor will not complete. | Vehicle design anomaly. Dealer recall H444 has been issued to correct this. | Test normally. If OBD test failure is due to an incomplete NOx aftertreatment monitor, advise the vehicle owner to visit a Jaguar dealership for a software update under recall H444. |
| Jaguar | 2019 | Jaguar XE, XF, & F-Pace 2.0L (diesel) [California certified] Test group KJLXJ02.0STY | NOx Aftertreatment System monitor will not complete. | Vehicle design anomaly. Dealer recall H444 is available to address this issue. | Test normally. If the vehicle fails the OBD test because of an incomplete NOx aftertreatment monitor, guide the owner to a Jaguar dealership for a software update covered by recall H444. |
| Jeep | 2005-2006 | Wrangler | O2 sensor, O2 heater, and catalyst readiness monitors may indicate not ready. | This is a vehicle design anomaly. TSB #25-005-13 Rev. A provides a wiring modification to resolve readiness issues. | OIS is programmed to allow an incomplete O2 heater monitor for these models due to this known issue. |
| Jeep | 2010-2011 | Wrangler 3.8L | Failure to set Oxygen sensor monitor. PCM not running monitor frequently enough. | Recall L34 (manual transmission) through 9/10/2010 and Recall L35 (automatic transmission) through 3/26/2011 were issued to address this. OEM drive cycle may also be ineffective. | Reflash the PCM as per TSB 18-027-10. A special drive cycle may be needed to set the O2 monitor: coast from 70 to 30 mph three times, then pull over and restart the engine. |
| Kia | 2009 | Borrego LX/EX 3.8L | Fail for readiness. Vehicle may not set EGR monitor. | This vehicle has inherent difficulties in completing the EGR monitor drive cycle, making it challenging under normal conditions. | OIS was reprogrammed on 12/7/2017 to accommodate this by allowing the EGR/VVT monitor to be incomplete for this specific model. |
| Land Rover | 2017 | Discovery, Range Rover, Range Rover Sport 3.0L (diesel)[California certified] Test group HJLXT03.0GTR | NOx Aftertreatment System monitor will not complete. | Vehicle design anomaly. Dealer recall N808 was issued to address this. | Test normally. If OBD test failure is due to an incomplete NOx aftertreatment monitor, direct the vehicle owner to a Land Rover dealership for a software update under recall N808. |
| Land Rover | 2018 | Velar 2.0L (diesel) [California certified] Test group JJLXJ02.0STY | NOx Aftertreatment System monitor will not complete. | Vehicle design anomaly. Dealer recall N808 is available to correct this. | Test normally. If the vehicle fails the OBD test because of an incomplete NOx aftertreatment monitor, advise the owner to visit a Land Rover dealership for a software update covered by recall N808. |
| Land Rover | 2019 | Velar 2.0L (diesel) [California certified] Test group KJLXJ02.0STY | NOx Aftertreatment System monitor will not complete. | Vehicle design anomaly. Dealer recall N808 has been issued to resolve this. | Test normally. If the vehicle fails the OBD test due to an incomplete NOx aftertreatment monitor, refer the vehicle owner to a Land Rover dealership for a software update under recall N808. |
| Lexus | 2007 | RX400 Hybrid | Fail for oxygen sensor (air/fuel) monitor readiness. Air conditioning readiness monitor mistakenly set to supported instead of unsupported. | This is related to an Air Fuel monitor issue. A software update is available at no charge under Lexus campaign FLD, detailed in TSB #L-SB-0027-15. | If the vehicle fails due to an incomplete oxygen sensor monitor, inform the owner that a recall may be required. Check recall status at https://www.toyota.com/recall. |
| Lincoln | 2011 | MKX 3.5L & 3.7L | Vehicle fails for readiness. Some vehicles do not set readiness monitors. | Some vehicles may clear OBD-II diagnostic data upon each engine start or report an incorrect VIN, causing readiness monitor problems. Reprogram or update the vehicle’s calibration. Perform a monitor drive cycle afterward. | Consult Ford Emission Recall #13E04 for applicability. The owner must ensure the recall is performed, if applicable, and all monitor drive cycles are completed before Smog Check testing. |
| Lincoln | 2020-2022 | Corsair; all engines; Gasoline and hybrid | Might not communicate with BAR-OIS. | Design issue causing communication failures. A software update is available to rectify this. | Test normally. If the vehicle fails the OBD test due to no communication, direct the vehicle owner to a Ford dealership for a software update. The issue may stem from the gateway module software—see SSM 50974. Similar messages will be displayed on OIS and printed on the VIR. |
| Mazda | 2000 | MPV | Failure to set Catalyst monitor. | This may indicate a need for a new catalyst and/or oxygen sensor. Diagnosis and repair are necessary. | This likely points to a vehicle malfunction. Diagnose the catalyst and oxygen sensor system, perform necessary repairs, and then retest the vehicle. |
| Mazda | 2002-2003 | B3000 (2WD) 3.0L V-6 (E-85) | Readiness monitors will not set on certain flex fuel models. | Monitors are disabled for operation on fuel blends >E10 (Catalyst). A desensitized evaporative leak/purge check monitor is active for detecting gross leaks with blends >E75 (monitor is fully compliant up to E75 blends). | OIS is programmed to ignore all 11 readiness monitors for these flex-fuel models because of their specific monitor calibration for ethanol content. |
| Mazda | 2003-2004 | Mazda 6 | Some vehicles may experience false MIL illumination during inspection, accompanied by multiple U-code DTCs during the OBDII test, such as U1900-ABS, U2516-ABS, U1900-FF-IC, U2516-FF-IC, U0073-FF- PCM, U0073-FF-TCM, U0100-FF-TCM. | The PCM is sensitive to OBD tool connection or disconnection when the ignition is in the “On” position or when the engine is running. See Mazda Service Bulletin #01-002/05 dated 01/13/2005. Erase trouble codes and ensure tool disconnection only when the ignition is off. | Reset the monitors. Connect and disconnect the DAD to the vehicle only when the key is in the off position to avoid triggering false codes. |
| Mazda | 2005 | Mazda 6 (with 2.3 only) | Some vehicles may experience false MIL illumination during inspection with multiple U-code DTCs during OBDII test, including U1900-ABS, U2516-ABS, U1900-FF- IC, U2516-FF-IC, U0073-FF- PCM, U0073-FF-TCM, U0100-FF-TCM. | PCM sensitivity to OBD tool connection/disconnection with the ignition in the “On” position or engine running is the cause. Refer to Mazda Service Bulletin #01-002/05 Dated 01/13/2005. Clear trouble codes and disconnect the tool only with the ignition off. | Reset monitors. Always connect and disconnect the DAD to the vehicle when the key is off to prevent false MIL illumination and U-codes. |
| Mazda | 2003-2005 | Mazda 6 – 2.3 engine non PZEV (built May 20, 2002 – July 2, 2005) Mazda 6 – 3.0 engine (built May 16, 2002 – August 23, 2004) | Some vehicles may exhibit false MIL illumination during inspection, leading to a test failure despite the vehicle having no actual problem. | PCM sensitivity to OBD tool connection or disconnection while the ignition is “On” or engine is running. See TSB #01-024/05. For vehicles within VIN range, reprogram PCM and TCM. Or, Emission Recall TSB #1303F to Reprogram PCM may be applicable to certain VINs. | Follow OIS prompts carefully. Always connect and disconnect the DAD when the key is off to avoid false failures. |
| Mitsubishi Fuso | 1998-2004 | FE639/FG639 [GVWR 10,001 –14,000] (diesel) [Federal certified] | Vehicle is not equipped with OBDII. | OBD was not required for federally certified vehicles in this GVWR range during these years. | OIS is programmed to skip the OBD functional test as these vehicles do not have OBDII systems installed. |
| Mitsubishi | 2000-2001 | Montero, Montero Sport, Diamante, 3000GT Mirage, Galant, Expo/Expo LRV, and Eclipse models (except 2.0L non—turbo 420A engine models). | Fail for monitor readiness. | Some monitors on these models are inherently difficult to complete under normal driving conditions. | Follow the recommended drive cycles detailed in the Mitsubishi service manual to attempt to set the monitors. |
| Nissan | 1999-2007 | UD1200, [GVWR 10,001-14,000] (Diesel) [Federal certified] | Vehicle is not equipped with OBDII. | OBD was not required for federally certified vehicles in this GVWR range during these years. | OIS was programmed on 2/26/2016 to skip the OBD functional test for these vehicles due to the absence of OBDII systems. |
| Nissan | 2000-2001 | Maxima | Failure to set catalyst monitor. | The OBD catalyst code might only be detectable with an OEM scan tool, not with generic OBD tools. | Test the catalyst system using OEM-level diagnostic equipment. Replace the catalyst if it is found to be defective. |
| Nissan | 2000-2006 | All models | Fail for monitor readiness. | Incomplete monitors are common during normal driving with these models. Follow the drive cycle specific to the year, make, model, engine, certification, and transmission. Run the entire drive pattern even if only one monitor is unset. | Follow the drive cycle procedure. Refer to the owner’s manual for the specific drive cycle required to achieve monitor readiness. |
| Plymouth | 1999-2000 | Voyager with 3.0L engine built after 12/1/1998 | EGR Monitor will not complete at high altitude. | A reflash is available to correct this. Confirm all systems are functioning correctly, then erase and reprogram the PCM as per TSB 18-03-00. | Vehicle requires a PCM reflash. Repair according to TSB, run monitors, and then retest to ensure EGR monitor completion. |
| Plymouth | 2000 | Voyager 3.3L V-6 (E-85) | Readiness monitors will not set on certain flex fuel models, VINs listed below: WCRXT03.32BP (VIN 8th digit: G). | All monitors are disabled for operation on fuel blends >E30 and during ethanol fuel content learning. | OIS ignores all 11 readiness monitors for these specific flex-fuel models due to their unique monitor management strategies for ethanol blends. |
| Suzuki | 2001 | Aerio | Fail for monitor readiness. | Monitors can be particularly difficult to complete on this model, often requiring specific conditions. | Follow the recommended drive cycle. See OBD Clearinghouse or Suzuki service information for the correct procedure. |
| Suzuki | 2004 | Forenza | Fail for monitor readiness. | Monitors can be challenging to complete, often necessitating specific driving patterns. | Follow the drive cycle as detailed in OBD Clearinghouse or Suzuki service information to attempt to set the monitors. |
| Toyota | 2000-2006 | All models | Fail for monitor readiness. | Monitors can be difficult to complete on these models under normal driving conditions. | Follow the specific drive cycles provided in Toyota service information to achieve monitor readiness. |
| Toyota | 2003-2004 | 4 Runner | Vehicle Stability Control (VSC) light may illuminate if CAN protocol is attempted with an aftermarket scan tool. | The vehicle may lose stability control calibration when CAN protocol communication is attempted via aftermarket tools. Follow the service procedure to reset the zero-point calibration. | OIS is programmed not to attempt communication via CAN protocol on these vehicles to prevent triggering VSC issues. |
| Toyota | 2007 | Highlander Hybrid | Fail for oxygen sensor (air/fuel) monitor readiness. | Air Fuel monitor issue. Perform software update to vehicle at no charge per Toyota Special Service Campaign F0P, dated August 20, 2015, and TSB #0042-15. The air conditioning readiness monitor is also mistakenly set to supported instead of unsupported. | If the vehicle fails due to an incomplete oxygen sensor monitor, advise the owner that a recall may be necessary. Check recall status at https://www.toyota.com/recall. |
| Volvo | 2000 | S40 / V40 | Failure to set Comprehensive, Oxygen sensor, and Catalyst monitors. | A defective ECM is often the cause of these monitor setting failures. | Send to a Referee for inspection only if comprehensive, oxygen sensor, and catalyst monitors are unset. If any other failures are present, they must be repaired before the Referee inspection. |
| Volvo | 2004-2006 | S40, V50 | Air conditioning readiness monitor mistakenly set to supported instead of unsupported. | Vehicle design anomaly. The A/C monitor status reporting is incorrect due to vehicle design. | OIS is programmed to ignore the A/C monitor status for these vehicles due to this known reporting anomaly. |
| Volvo | 2005-2007 | XC90 | Air conditioning readiness monitor mistakenly set to supported instead of unsupported. | Vehicle design anomaly. The A/C monitor status is incorrectly reported as supported due to design issues. | OIS is programmed to ignore the A/C monitor status for these models because of this known reporting anomaly. |
| VW | 2000-2005 | Passat | May fail for no OBD communication. No response or Only Transmission Control Module responds to DADs requests. ABS and/or brake lamp illuminated in instrument panel cluster | A broken ground bond wire in the ABS module can cause diagnostic communication issues affecting the ABS module, ECM, and TCM. Diagnose and repair according to VW TSB #45 15 01, dated September 21, 2015. | This usually indicates a broken vehicle. Repair as per the VW TSB and then retest the OBD system to ensure communication is restored. |
E. Addressing Permanent Diagnostic Trouble Codes (PDTCs)
This section lists vehicles known to have issues with Permanent Diagnostic Trouble Codes (PDTCs). PDTCs, unlike regular DTCs, cannot be cleared with a scan tool or by disconnecting the battery; they self-clear only when the vehicle’s system verifies the repair. Certain vehicles are known to exhibit problems where PDTCs do not clear even after the fault is corrected. This can lead to unnecessary failures during Smog Checks. Understanding these vehicle-specific PDTC issues is vital for technicians working with code obd and emissions compliance.
For the vehicles listed below, BAR-OIS is programmed to ignore specific PDTCs to prevent unwarranted failures. However, it’s crucial to verify if the listed PDTCs are indeed related to the known issues before assuming they should be ignored in other diagnostic contexts. Always refer to the latest service information and technical service bulletins for the most accurate and up-to-date guidance when diagnosing and repairing vehicles with code obd concerns.
| Make | Year | Model Engine (L); Fuel Type | Issue | Cause and Possible Remedy | Instructions to Inspector |
|---|---|---|---|---|---|
| Audi | 2010 | Q7; 3.0 (TDI/diesel) | Permanent Fault Codes P0087, P0088, and P053F will not clear if present. | Currently, there is no known remedy available from the manufacturer to resolve the non-clearing issue for these specific PDTCs. | Test normally. BAR-OIS is programmed to ignore these specific codes during the Smog Check to prevent a false failure. |
| Audi | 2011-2012 | Q7; 3.0 (TDI/diesel) | Permanent Fault Codes P0087, P0088, P053F, P064A, P2635, and P0230 will not clear if present. | As of now, no remedy has been issued by the manufacturer to address the persistent nature of these PDTCs on these models. | Test normally. BAR-OIS is configured to ignore these fault codes during the Smog Check to avoid unwarranted failures due to non-clearing PDTCs. |
| Chrysler | 2011-2015 | 200; 2.4, 3.6 | Permanent Fault Codes will not clear. | A reflash is available to correct this issue as per Recall V51. This update is designed to fix the non-clearing PDTC problem. | Reflash the vehicle’s computer with the software update provided under Recall V51. After reflashing, retest the vehicle to ensure the PDTC issue is resolved. |
| Chrysler | 2010-2014 | 300; 3.6, 5.7, 6.4 | Permanent Fault Codes will not clear. | A software reflash is available under Recall V51 to address and resolve the issue of PDTCs not clearing on these models. | Perform the reflash as described in Recall V51. Following the update, conduct a retest to confirm that the permanent fault codes now clear as expected. |
| Chrysler | 2017 | Pacifica Hybrid | Vehicle fails for PDTC C2200 or B22A9-00. | Reflash modules using the procedures outlined in TSB 08-005-21 and 08-006-21. These TSBs provide specific instructions for software updates to resolve these PDTC issues. | Reflash the necessary modules according to TSB 08-005-21 and 08-006-21. After applying the updates, retest the vehicle to verify that the PDTC issue is resolved and the codes no longer cause a failure. |
| Chrysler | 2018 | Pacifica Hybrid | Vehicle fails for PDTC C2200 or B22A9-00. | Implement module reflashes as per TSB 08-008-21 and 08-009-21. These technical service bulletins contain software update procedures to fix the PDTC problem. | Reflash the modules following the guidelines in TSB 08-008-21 and 08-009-21. Once the updates are complete, retest the vehicle to ensure the PDTC related failure is resolved. |
| Chrysler | 2019 | Pacifica Hybrid | Vehicle fails for PDTC C2200 or B22A9-00. | Apply module reflashes according to TSB 08-011-21 and 08-012-21. These TSBs detail the software updates required to fix the PDTC issue. | Reflash the modules as per TSB 08-011-21 and 08-012-21. After the reflash process, retest the vehicle to confirm that the PDTC issue is corrected and the vehicle passes the test. |
| Chrysler | 2011-2015 | Town and Country; 3.6 | Permanent Fault Codes will not clear. | A reflash is available via Recall V51 to correct the issue of permanent fault codes that do not clear on these models. | Perform the reflash as specified in Recall V51. After the update is installed, retest the vehicle to ensure the PDTCs now clear properly. |
| Dodge | 2011-2014 | Avenger | Permanent Fault Codes will not clear. | A reflash is available under Recall V51 to address and fix the issue of permanent fault codes not clearing. | Apply the reflash as described in Recall V51. Following the software update, retest the vehicle to verify that the PDTCs now clear correctly. |
| Dodge | 2011-2012 | Caliber; 2.0, 2.4 | Permanent Fault Codes will not clear. | Recall V51 provides a reflash to resolve the problem of permanent fault codes that persist and do not clear. | Perform the reflash according to Recall V51. After the reflash, retest the vehicle to confirm that the PDTCs now clear as expected. |
| Dodge | 2011-2015 | Challenger; 3.6, 5.7, 6.4 | Vehicle fails for Permanent Fault Code U0140. | A reflash is available through Recall V51 to address the issue causing Permanent Fault Code U0140 and prevent test failures. | Reflash the vehicle using the software update from Recall V51. Once updated, retest the vehicle to ensure that Permanent Fault Code U0140 is resolved and no longer causes a failure. |
| Dodge | 2011-2014 | Charger; 3.6, 5.7, 6.4 | Vehicle fails for Permanent Fault Code U0140. | Recall V51 offers a reflash to fix the issue that leads to Permanent Fault Code U0140 and subsequent test failures. | Apply the reflash as detailed in Recall V51. After the reflash, retest the vehicle to verify that Permanent Fault Code U0140 is no longer present and the vehicle passes the test. |
| Dodge | 2011-2015 | Grand Caravan; 3.6 | Permanent Fault Codes will not clear. | A reflash is available via Recall V51 to correct the issue of permanent fault codes that do not clear on these models. | Execute the reflash as per Recall V51. Following the update, retest the vehicle to confirm that the PDTCs now clear as designed. |
| Dodge | 2010-2011 | Dakota; 3.7, 4.7 | Permanent Fault Codes will not clear. | Recall V51 provides a reflash to resolve the issue of permanent fault codes that do not clear on these vehicles. | Implement the reflash as described in Recall V51. After the update, retest the vehicle to ensure that the PDTCs now clear correctly. |
| Dodge | 2013 | Dart; 2.0 | Vehicle fails for Permanent Fault Code U0140. | Reflashes are available through both Recall V50 and V51 to address the issue causing Permanent Fault Code U0140. | Reflash the vehicle using software updates from both Recall V50 and V51. After applying both reflashes, retest the vehicle to ensure that Permanent Fault Code U0140 is resolved. |
| Dodge | 2013 | Dart; 2.4 | Permanent Fault Codes will not clear. | A reflash is provided through Recall V51 to correct the problem of permanent fault codes that do not clear on these models. | Apply the reflash as specified in Recall V51. Following the update, retest the vehicle to verify that the PDTCs now clear properly. |
| Dodge | 2014-2015 | Dart; 2.0, 2.4 | Permanent Fault Codes will not clear. | A reflash is available via Recall V51 to address the issue of permanent fault codes that do not clear on these models. | Perform the reflash as per Recall V51. After the update, retest the vehicle to ensure that the PDTCs now clear as designed. |
| Dodge | 2011-2014 | Durango; 3.6, 5.7 | Vehicle fails for Permanent Fault Code U0140. | Recall V51 offers a reflash to address and resolve the issue causing Permanent Fault Code U0140, which leads to test failures. | Apply the reflash as detailed in Recall V51. Following the reflash, retest the vehicle to confirm that Permanent Fault Code U0140 is no longer present and the vehicle passes inspection. |
| Dodge | 2011-2015 | Journey; 2.4, 3.6 | Permanent Fault Codes will not clear. | A reflash is available through Recall V51 to correct the issue of permanent fault codes that do not clear on these vehicles. | Execute the reflash as described in Recall V51. After the update, retest the vehicle to ensure that the PDTCs now clear correctly. |
| Dodge | 2010-2011 | Nitro; 3.7, 4.0 | Permanent Fault Codes will not clear. | Recall V51 provides a reflash to fix the issue of permanent fault codes that do not clear on these models. | Implement the reflash as per Recall V51. Following the update, retest the vehicle to confirm that the PDTCs now clear as expected. |
| Ford | 2011-2014 | Mustang; 3.7 & 5.0 (gasoline) | Vehicle fails for Permanent Fault Code P0315. | The vehicle is not self-clearing the permanent fault code P0315, leading to persistent failures. | Refer the motorist to a Ford dealership for Customer Satisfaction Program 17N01. This program is specifically designed to address and resolve the issue with Permanent Fault Code P0315. |
| Freightliner | 2014-2015 | Sprinter 2500 Sprinter 3500 (diesel) | Vehicle fails for Permanent Fault Codes P202A, P203A, P208A, P20B9, P20BD, P20BE or P20FA. | The vehicle is not self-clearing these specific permanent fault codes, causing potential issues during inspections. | Test normally. BAR-OIS is programmed to ignore these particular codes during the Smog Check to prevent false failures due to the non-clearing PDTCs. |
| Jeep | 2014-2015 | Cherokee; 2.4, 3.2 | Vehicle fails for Permanent Fault Code U0140. | A reflash is available via Recall V51 to address and resolve the issue causing Permanent Fault Code U0140 and subsequent test failures. | Reflash the vehicle using the software update from Recall V51. After the update, retest to ensure that Permanent Fault Code U0140 is resolved and no longer causes a failure. |
| Jeep | 2010 | Commander; 5.7 | Permanent Fault Codes will not clear. | A reflash is available through Recall V51 to correct the issue of permanent fault codes that do not clear on these models. | Apply the reflash as described in Recall V51. Following the update, retest the vehicle to verify that the PDTCs now clear as designed. |
| Jeep | 2010-2015 | Grand Cherokee; 3.6, 5.7, 6.4 | Permanent Fault Codes will not clear | Recall V51 provides a reflash to fix the issue of permanent fault codes that do not clear on these vehicles, leading to potential test failures. | Perform the reflash according to Recall V51. After the reflash, retest the vehicle to ensure that the PDTCs now clear as expected. |
| Jeep | 2014-2017 | Grand Cherokee (diesel) | Vehicle fails for Permanent Fault Code P1D30. | The vehicle is not self-clearing permanent fault code P1D30, which can cause inspection failures. | Test normally. BAR-OIS is programmed to ignore this specific code during the Smog Check to prevent false failures due to this non-clearing PDTC. |
| Jeep | 2010-2012 | Liberty; 3.7 | Permanent Fault Codes will not clear | Recall V51 offers a reflash to address and resolve the issue of permanent fault codes that do not clear on these models. | Execute the reflash as per Recall V51. Following the update, retest the vehicle to confirm that the PDTCs now clear correctly. |
| Jeep | 2011-2015 | Patriot / Compass; 2.0, 2.4 | Permanent Fault Codes will not clear | A reflash is available through Recall V51 to correct the issue of permanent fault codes that do not clear on these vehicles. | Implement the reflash as described in Recall V51. After the update, retest the vehicle to ensure that the PDTCs now clear as designed. |
| Jeep | 2010-2015 | Wrangler; 3.6, 3.8 | Permanent Fault Codes will not clear | Recall V51 provides a reflash to fix the issue of permanent fault codes that do not clear on these models, potentially causing inspection failures. | Apply the reflash as specified in Recall V51. Following the update, retest the vehicle to verify that the PDTCs now clear properly. |
| Mercedes | 2010-2013 | 350 Bluetec | Vehicle fails for Permanent Fault Codes P203D, P20B6, P20BD or P20BE | The vehicle is not self-clearing these particular permanent fault codes, leading to potential issues during inspections. | Test normally. BAR-OIS is programmed to ignore these specific codes during the Smog Check to prevent false failures caused by these non-clearing PDTCs. |
| Mercedes | 2014-2015 | Sprinter 2500 Sprinter 3500 (diesel) | Vehicle fails for Permanent Fault Codes P202A, P203A, P208A, P20B9, P20BD, P20BE or P20FA. | The vehicle is not self-clearing these permanent fault codes, which can cause unwarranted failures during inspections. | Test normally. BAR-OIS is programmed to ignore these fault codes during the Smog Check to prevent false failures resulting from these non-clearing PDTCs. |
| Ram | 2010-2014 | 1500; 3.6, 3.7, 4.7, 5.7 | Vehicle fails for Permanent Fault Code U0140. | Recall V51 offers a reflash to address and resolve the issue causing Permanent Fault Code U0140, preventing test failures. | Reflash the vehicle using the software update from Recall V51. After the update, retest to ensure that Permanent Fault Code U0140 is resolved and no longer causes a failure. |
| Ram | 2013 | 1500; 3.6, 5.7 | Permanent Fault Codes will not clear. | A reflash is available through Recall V50 to correct the issue of permanent fault codes that do not clear on these models. | Perform the reflash as per Recall V50. Following the update, retest the vehicle to confirm that the PDTCs now clear as designed. |
| Ram | 2014-2017 | 1500 (diesel) | Vehicle fails for Permanent Fault Code P1D30. | The vehicle is not self-clearing permanent fault code P1D30, which can lead to failures during inspections. | Test normally. BAR-OIS is programmed to ignore this specific code during the Smog Check to prevent false failures due to this non-clearing PDTC. |
| Ram | 2010-2015 | 2500; 5.7, 6.4 | Permanent Fault Codes will not clear. | Recall V51 provides a reflash to fix the issue of permanent fault codes that do not clear on these models, which may lead to inspection failures. | Apply the reflash as specified in Recall V51. Following the update, retest the vehicle to verify that the PDTCs now clear properly. |
| Ram | 2011-2015 | 3500 Cab Chassis; 5.7, 6.4 | Permanent Fault Codes will not clear. | A reflash is available via Recall V51 to correct the issue of permanent fault codes that do not clear on these models. | Execute the reflash as described in Recall V51. After the update, retest the vehicle to ensure that the PDTCs now clear correctly. |
| Ram | 2013-2015 | 3500 Pickup; 5.7, 6.4 | Permanent Fault Codes will not clear. | Recall V51 offers a reflash to address and resolve the issue of permanent fault codes that do not clear on these models, potentially causing inspection failures. | Implement the reflash as described in Recall V51. Following the update, retest the vehicle to confirm that the PDTCs now clear as expected. |
| Ram | 2014 | Promaster; 3.6 | Permanent Fault Codes will not clear. | A reflash is available through Recall V50 to correct the issue of permanent fault codes that do not clear on these models. | Reflash the vehicle as per Recall V50. After the update, retest the vehicle to ensure that the PDTCs now clear as designed. |
| Volkswagen | 2010 | Touareg; 3.0 (TDI/diesel) | Permanent Fault Codes P20B5, P0087, P0088, and P053F will not clear if present. | Currently, there is no manufacturer remedy available to address the issue of these PDTCs not clearing. | Test normally. BAR-OIS is programmed to ignore these specific codes during the Smog Check to prevent a false failure result. |
| Volkswagen | 2011-2012 | Touareg; 3.0 (TDI/diesel). | Permanent Fault Codes P20B5, P0087, P0088, P053F, P064A, P2635, and P0230 will not clear if present. | As of now, no remedy has been issued by the manufacturer to fix the persistent nature of these PDTCs on these models. | Test normally. BAR-OIS is configured to ignore these fault codes during the Smog Check to avoid unwarranted failures due to non-clearing PDTCs. |
F. BAR-97 EIS Specific Vehicle Information
This section is dedicated to vehicles from model years 1996-1999 that have known monitor readiness issues when undergoing the OBD test portion of a BAR-97 EIS inspection. In many of these cases, the BAR-97 EIS system is specifically programmed to accommodate vehicles with certain design anomalies, ensuring that these vehicles are not unfairly penalized during inspections. Understanding these nuances is crucial for technicians dealing with older vehicles and code obd within the BAR-97 EIS framework.
The following table details vehicles with known issues, the nature of these issues, potential causes and remedies, and specific instructions for inspectors conducting BAR-97 EIS inspections. This information is essential for accurately assessing older vehicles and understanding how the BAR-97 EIS system handles specific code obd scenarios.
| Make | Year | Model Engine (L); Fuel Type | Issue | Cause and Possible Remedy | Instructions to Inspector |
|---|---|---|---|---|---|
| BMW | 1996 | 7-Series, 8-Series 5.0L, 5.4L | Monitors difficult to complete. | The monitors on these models are known to be challenging to complete under standard driving conditions. | EIS is programmed to ignore the readiness status for these specific BMW models due to the known difficulty in completing monitors. |
| Chrysler | 1996 | Cirrus, Concord, LHS Sebring Convertible | All monitors reset to incomplete upon every ignition key-off. | Recall campaign #678 specifically applies to California certified vehicles originally sold in California to address this issue. TSB #18-005-01 (with a lifetime warranty) is applicable to both federal certified vehicles and California certified vehicles initially sold in northeast states. | Ensure compliance with the recall campaign or TSB. Once the recall or TSB measures are implemented, test the vehicle as normal. |
| Chrysler | 1996 | Concord, LHS, New Yorker, Sebring, Town & Country 2.0L, 2.4L, 2.5L, 3.3L, 3.5L | Monitors difficult to complete. | The monitors on these Chrysler models are known to be challenging to complete under typical driving conditions. | EIS is programmed to ignore the readiness status for these specific Chrysler models because of the recognized difficulty in achieving monitor completion. |
| Chrysler | 1998-1999 | Town & Country 3.3L Flex Fuel | Monitors may not function correctly when ethanol is detected in the fuel by the vehicle’s system. | The monitor behavior is affected by ethanol presence due to the flex-fuel design of these models. | Test as normal. The EIS system is designed to accommodate the monitor variations in flex-fuel vehicles. |
| Dodge | 1996 | Stratus, Intrepid, Neon | All monitors reset to incomplete upon every ignition key-off. | Recall campaign #678 applies to California certified vehicles originally sold in California to correct this. TSB #18-005-01 (with lifetime warranty) is for federal certified and California certified vehicles initially sold in northeast states. | Ensure the vehicle complies with the recall or TSB. After implementing the recall or TSB fix, proceed with normal testing. |
| Dodge | 1996 | Avenger, Stratus 2.0L manual | Monitors difficult to complete. | The monitors on these Dodge models with a 2.0L manual transmission are known to be challenging to complete. | EIS is programmed to ignore the readiness status for these specific Dodge models due to the recognized difficulty in monitor completion. |
| Dodge | 1996 | Stealth 3.0L | All monitors reset to incomplete upon every ignition key-off. | These vehicles are not reflashable, making a software fix for the monitor reset issue impossible. | EIS is programmed to ignore readiness status for these specific Dodge Stealth models as a permanent accommodation due to their design limitations. |
| Dodge | 1998-1999 | Caravan 3.3L Flex Fuel | Monitors may not function as expected when ethanol is detected by the vehicle’s fuel system. | Monitor function is influenced by ethanol content due to the flex-fuel capability of these models. | Test as normal. The EIS system is designed to accommodate the monitor variations inherent in flex-fuel vehicles. |
| Eagle | 1996 | Vision | All monitors reset to incomplete upon every ignition key-off. | Recall campaign #678 is applicable to California certified vehicles originally sold in California. TSB #18-005-01 (with lifetime warranty) covers federal certified and California certified vehicles initially sold in northeast states. | Verify compliance with the TSB. Once the TSB measures are implemented, test the vehicle as normal. |
| Eagle | 1996-1997 | Talon 2.0L | Monitors difficult to complete. | Monitors on these Eagle Talon 2.0L models are known to be challenging to complete under standard driving conditions. | EIS is programmed to ignore readiness status for these Eagle Talon models because of the recognized difficulty in achieving monitor completion. |
| Ford | 2020-2022 | F-53 Motorhome, F-59 Commercial Stripped Chassis; Gasoline (not hybrid) | May fail for no OBD communication. | Design issue causing potential communication failures during OBD testing. A software update is available to address this. | Test normally. If the vehicle fails the OBD test due to no communication, direct the owner to a Ford dealership for a software update related to the gateway module—see SSM 50974. |
| Ford | 2021-2023 | F-650, F-750; all engines; Gasoline (not hybrid) | May fail for no OBD communication. | Design issue leading to potential communication failures during OBD testing. A software update is available to resolve this. | Test normally. If the vehicle fails the OBD test because of no communication, advise the vehicle owner to visit a Ford dealership for a software update concerning the gateway module—refer to SSM 50974. |
| Hyundai | 1996 | Accent 1.5L Elantra 1.8L Sonata 2.0L | Monitors difficult to complete. | Monitors on these early Hyundai models are known to be challenging to complete under normal driving conditions. | EIS is programmed to ignore readiness status for these Hyundai models due to the recognized difficulty in achieving monitor completion. |
| Hyundai | 1997-1998 | Sonata 2.0L, 3.0L | Monitors difficult to complete. | Monitors on these Hyundai Sonata models are known to be challenging to complete under standard driving conditions. | EIS is programmed to ignore readiness status for these Hyundai Sonata models due to the known difficulty in monitor completion. |
| lnfiniti | 1996 | All models | Catalyst and evaporative system monitors are difficult to complete. | Catalyst and evaporative system monitors on all 1996 Infiniti models are known to be particularly difficult to complete. | Follow the specific drive cycle for each vehicle model as detailed in TSB #ITB98-011F, June 7, 2013, to attempt monitor completion before testing. If monitors are still incomplete, test as normal as EIS will accommodate. |
| Kia | 1996 | Sephia Sportage | Monitors difficult to complete. | Monitors on these early Kia models are known to be challenging to complete under normal driving conditions. | EIS is programmed to ignore readiness status for these Kia models because of the recognized difficulty in monitor completion. |
| Lexus | 1996-1999 | All models | Monitors can be difficult to complete. | Monitors on all Lexus models from 1996-1999 may be challenging to complete under typical driving conditions. | Follow the specific drive cycles detailed in Lexus service information to attempt monitor completion. If monitors remain incomplete, test as normal, as EIS is designed to accommodate. |
| Mercedes-Benz | 1996 | C220, E320, C280, S320, SL320 | The MIL illuminates when a scan tool is connected to the DLC. Trouble codes are not stored. | If the OBD II connector is used as the RPM source during the Smog Check, the MIL will illuminate falsely. | Do not connect the OBD II connector until the analyzer specifically prompts for the OBD II functional test. Use a conventional contact or non-contact method to obtain an RPM signal to avoid false MIL illumination. |
| Mitsubishi | 1996-1997 | All Models | Monitors difficult to complete. | Monitors on all Mitsubishi models from 1996-1997 are known to be challenging to complete under normal driving conditions. | EIS is programmed to ignore readiness status for these Mitsubishi models due to the recognized difficulty in monitor completion. |
| Mitsubishi | 1998 | Eclipse (all), Galant 2.4L, Mirage, Montero Sport 2.4L | Monitors difficult to complete. | Monitors on these Mitsubishi models are known to be challenging to complete under typical driving conditions. | EIS is programmed to ignore readiness status for these specific Mitsubishi models because of the recognized difficulty in achieving monitor completion. |
| Mitsubishi | 1998 | 3000GT, Diamante, Galant 2.3L, Montero, Montero Sport 3.0L | Some monitors are difficult to complete. | Certain monitors on these Mitsubishi models are known to be challenging to complete under standard driving conditions. | Follow the recommended drive cycles provided in the Mitsubishi service manual to attempt to complete these monitors before testing. |
| Mitsubishi | 1999 | All models | Some monitors are difficult to complete. | Certain monitors on all 1999 Mitsubishi models may be challenging to complete under normal driving conditions. | Follow the recommended drive cycles in the Mitsubishi service manual to attempt to complete monitors. If monitors remain incomplete, test as normal, as EIS is designed to accommodate. |
| Nissan | 1996 | Sentra 1.6L and 2.0L manual, 200SX 1.6L, 240SX 2.4L, Maxima 3.0L, Pickup 2.4L | Monitors difficult to complete. | Monitors on these Nissan models are known to be challenging to complete under typical driving conditions. | EIS is programmed to ignore readiness status for these Nissan models due to the recognized difficulty in monitor completion. |
| Nissan | 1996-1997 | All models | Catalyst and evaporative system monitors are difficult to complete. | Catalyst and evaporative system monitors on all 1996-1997 Nissan models are known to be particularly difficult to complete. | Follow the specific drive cycle for each model as per Nissan TSB #NTB98-018G, June 7, 2013, to attempt monitor completion prior to testing. If monitors are still incomplete, test as normal as EIS will accommodate. |
| Nissan | 1999 | All models | Monitors can be difficult to complete. | Monitors on all 1999 Nissan models may be challenging to complete under normal driving conditions. | Follow the drive cycle in the owner’s manual to attempt to achieve readiness. If monitors remain incomplete, test as normal, as EIS is designed to accommodate. |
| Plymouth | 1996 | Breeze, Neon | All monitors reset to incomplete upon every ignition key-off. | Recall campaign #678 is applicable to California certified vehicles originally sold in California. TSB #18-005-01 (with lifetime warranty) is for federal certified and California certified vehicles initially sold in northeast states. | Verify compliance with the recall or TSB. After implementing recall or TSB measures, test the vehicle as normal. |
| Plymouth | 1998-1999 | Voyager 3.3L Flex Fuel | Monitors may not function as expected when ethanol is detected by the vehicle’s system. | Monitor function is affected by ethanol content due to the flex-fuel design of these models. | Test as normal. The EIS system is designed to accommodate monitor variations in flex-fuel vehicles. |
| Saab | 1996-1998 | 900 2.3L (B234 with Motronic 4.1) | Monitors difficult to complete. | Monitors on Saab 900 2.3L models (B234 with Motronic 4.1) are known to be challenging to complete. | EIS is programmed to ignore readiness status for these Saab models due to the recognized difficulty in monitor completion. |
| Saab | 1996-1998 | All models | Catalyst and evaporative system monitors are difficult to complete. | Catalyst and evaporative system monitors on all 1996-1998 Saab models are known to be particularly difficult to complete. | Follow Saab Service Instruction No. 248-9037, which describes the correct drive cycle for monitor completion. Comply with the TSB and then test as normal. |
| Subaru | 1996 | All models | Readiness cleared at key-off. | Readiness status is reset to cleared every time the ignition is turned off on these Subaru models. | EIS is programmed to ignore readiness status for all 1996 Subaru models due to this design characteristic. |
| Toyota | 1996-1999 | All models | Monitors can be difficult to complete. | Monitors on all Toyota models from 1996-1999 may be challenging to complete under normal driving conditions. | Follow the specific drive cycles detailed in Toyota service information to attempt monitor completion. If monitors remain incomplete, test as normal, as EIS is designed to accommodate. |
| Toyota | 1996-1997 | Tercel, Paseo | Evaporative system monitor will never complete or is unsupported. | The evaporative system monitor on these Toyota Tercel and Paseo models either never completes or is not supported by the vehicle’s OBD system. | The EIS allows any one monitor to be incomplete. Test as normal, knowing the evaporative system monitor may not be ready. |
| VW | 1997-1999 | Passat | May fail for no OBD communication. No response or Only Transmission Control Module responds to DADs requests. ABS and/or brake lamp illuminated in instrument panel cluster. | A broken ground bond wire in the ABS module can cause diagnostic communication issues affecting the ABS module, ECM, and TCM on these VW Passat models. Diagnose and repair according to VW TSB #45 15 01, dated September 21, 2015. | This typically indicates a broken vehicle. Repair the ground bond wire as per the VW TSB and then retest the OBD system to ensure communication is restored. |
| Volvo | 1996-1998 | All models | Monitors difficult to complete. | Monitors on all Volvo models from 1996-1998 are known to be challenging to complete under normal driving conditions. | Follow the recommended drive cycles in Volvo Service Bulletin 25-19 to attempt monitor completion. EIS is programmed to ignore readiness status if monitors remain incomplete after drive cycles. |
