LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Jeep >> 2001 >> Cherokee Limited, 4WD >> Repair and Diagnosis >> Engine Performance >> System >> Engine Controls - Self-Diagnostics >> Verification Tests >> Fuel System/Misfire Monitor Verification Test
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Fuel System/Misfire Monitor Verification Test

NOTE: If replacing Powertrain Control Module (PCM), the correct vehicle mileage and Vehicle Identification Number (VIN) must be programmed into PCM to prevent Diagnostic Trouble Codes (DTC) from being stored in Anti-Lock Brake System (ABS) module and Air Bag Control Module (ACM). If replacing PCM and vehicle is equipped with a Smart Key Immobilizer Module (SKIM), secret key data must also be updated to enable engine starting.
  1. Inspect vehicle to ensure all engine components are connected. Reassemble and reconnect components as necessary. If any DTCs have not been diagnosed, perform appropriate diagnostic test. See DTC MESSAGES & CODES  table under DIAGNOSTIC TROUBLE CODE DEFINITIONS. If all DTCs have been diagnosed and repaired, go to next step.
  2. Connect scan tool to Data Link Connector (DLC), if not previously done. Ensure fuel tank is at least 1/4 full. Ensure A/C is off. Go to next step.
  3. If repair procedure did not include replacing PCM, or PCM has been replaced and has already been programmed, go to next step. If PCM has been replaced but has not been programmed, program PCM and clear DTCs. See PROGRAMMING  . After PCM has been programmed, go to next step.
  4. Ensure misfire detection is enabled if a misfire DTC was repaired. Low fuel level or an unlearned adaptive numerator can disable the misfire monitor. If PCM has been replaced or disconnected during testing, the adaptive numerator must be relearned in order for misfire monitor to run.
  5. Using scan tool, monitor SIMILAR CONDITIONS and attempt to duplicate conditions during which vehicle was operating at when DTC was set. If conditions can be duplicated, GOOD TRIP counter will change to one or more. If conditions cannot be duplicated, clear DTCs. If OBD-II monitor failed after running, repair is not complete. Check for technical service bulletins that apply to symptom. Go to TROUBLE SHOOTING - NO CODES article for diagnosis by symptom.
  6. If repaired DTC has reset, proceed to appropriate DTC test. See DTC MESSAGES & CODES  table under DIAGNOSTIC TROUBLE CODE DEFINITIONS. If monitor ran and GOOD TRIP counter changed to one or more, repair was successful and test is now complete.
scientia non olet · About LEMON Manuals