LEMON Manuals: Even more car manuals for everyone
Home >> Dodge and Ram >> 2002 >> Ram Van B2500, Van Cargo, 5.9 Z >> Repair and Diagnosis >> Engine Performance >> System >> Engine Controls - Self-Diagnostics >> Verification Tests >> Powertrain Verification Test VER-6

Powertrain Verification Test VER-6

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 Controller Anti-Lock Brake (CAB) module and Air Bag Control Module (ACM).
  1. Inspect vehicle to ensure all engine components are connected. Reassemble and reconnect components as necessary. Go to next step.
  2. If any DTCs have not been diagnosed, perform appropriate diagnostic test. See DIAGNOSTIC TROUBLE CODE DEFINITIONS . After all DTCs have been diagnosed and repaired, perform LDP DEALER TEST MODE under SYSTEM TESTS using DRBIII®. Go to next step.
  3. If repair procedure included replacing PCM, go to next step. If repair procedure did not include replacing PCM, go to step  7.
  4. If Powertrain Control Module (PCM) was replaced, the correct vehicle mileage and Vehicle Identification Number (VIN) must be programmed into PCM to prevent Diagnostic Trouble Codes (DTC) from being stored in Controller Anti-Lock Brake (CAB) module and Air Bag Control Module (ACM). If vehicle is equipped with a Sentry Key Immobilizer Module (SKIM), secret key data must be updated to enable start.
  5. For ABS and air bag systems, enter correct vehicle mileage and Vehicle Identification Number (VIN). Erase any DTC in ABS and air bag modules.
  6. For SKIM theft alarm, using DRBIII®, select THEFT ALARM, SKIM, then MISC. Place SKIM in secured access mode by using appropriate PIN code for this vehicle. Select UPDATE SECRET KEY DATA. Data will be transferred from SKIM to PCM.
  7. LDP DEALER TEST MODE has been added to DRBIII® to verify repairs to LDP system. A DRBIII® software program was written which causes PCM to run LDP monitor as part of this test. Test failures will be indicated through a stored DTC.
  8. LDP monitor test mode is a useful way to run a total system performance test. Use this test to verify any type of LDP system repair.
  9. Software program makes temporary changes to operating mode of PCM. For this reason, it is critical that test not be interrupted. PCM's left in this mode as result of interrupted test will illuminate the MIL for 8-10 miles of driving with no DTCs stored.
  10. Erasing DTCs will not change this condition.
  11. If a vehicle is found to be stuck in the mode described above, LDP DEALER TEST should be re-run in it's entirety so that the software program in the DRBIII® can restore the PCM operating mode.
  12. Note similarity to LDP monitor screen found under OBD-II monitors. Failure modes are fewer in this system test than OBD-II LDP monitor. System test only stores small leak DTC to indicate problem with system. No other type of failure mode indication given.
  13. System test failure may have been, for example, due to a large leak, but the PCM will set the small leak DTC to indicate failures that occurred as part of the system test.
  14. Connect DRBIII® to Data Link Connector (DLC), if not already connected. Engine running, turn off all accessories.
    15. NOTE: While test is being performed, PCM must see RPM, minimum MAP, no vehicle speed and minimum TP Sensor value (at idle in Park).
  15. Using DRBIII® in SYSTEM TESTS, perform LDP MONITOR TEST and follow instructions on scan tool display. If another DTC has set, proceed to appropriate DTC test. See DIAGNOSTIC TROUBLE CODE DEFINITIONS . If the OBD-II monitor ran successfully and the good trip counter changed to one or more, repair is complete. If the OBD-II monitor did not run successfully and/or the Good Trip Counter did not change to one or more, check for Technical Service Bulletins (TSB) that apply to symptom. Go to appropriate TROUBLE SHOOTING - NO CODES article for diagnosis by symptom.
scientia non olet · About LEMON Manuals