Powertrain Verification Test - Ver 5A

VERIFICATION TEST VER-5A

Applicability - All

1. Road Test For OBD II

2. Note: If the PCM has been changed and the correct VIN and mileage have not been programmed, a DTC will be set in the ABS and Airbag modules. In addition, if the vehicle is equipped with a Sentry Key Immobilizer Module (SKIM), Secret Key data must be updated to enable starting.

3. For ABS and Airbag Systems: ACTION: Enter correct VIN and mileage in PCM. Erase codes in ABS and Airbag modules.

4. For SKIM Theft Alarm: ACTION:

5. Connect the DRB III to the Data Link Connector.

6. Go to Theft Alarm, SKIM, Misc. and place SKIM in secured access mode, by using appropriate PIN code for vehicle.

7. Select Update Secret Key data. Data will be transferred from SKIM to PCM.

8. Inspect the vehicle to ensure that all engine components are connected.

9. If there are any existing DTC's that have not been repaired, return to the symptom list and restart diagnostic testing and follow the path for that symptom.

10. After all DTC's have been repaired, return to the symptom list and repeat diagnostic testing for this system and run the appropriate monitor for the previously repaired OBD II trouble code.

11. Connect the DRB III to the Data Link Connector.

12. Ensure the fuel tank has at least a quarter tank of fuel.

13. Turn off all accessories.

14. The proper way to verify an OBD II DTC repair is to allow the PCM to run the appropriate monitor(s) and increment a global good trip, misfire or fuel system Good Trips depending on code repaired. The technician can see the monitor using the DRB III.

15. The enabling conditions must be met before the PCM will run the monitor. Read the enabling conditions on the DRB III monitor Pretest screen.

16. With the DRB III, monitor the pretest enabling conditions until all conditions have been met. Once the enabling conditions have been met, monitor the appropriate OBD II monitor.

17. If the repaired OBD II DTC has reset or was seen in the OBD II monitor while on the road test, the repair is not complete. Check for any Technical Service Bulletins or flash updates and return to the symptom list. Restart diagnostic testing for that symptom.

18. If another trouble code has set, return to the symptom list, restart diagnostic testing, and follow the path specified for that symptom.

19. If the monitor ran, the good trip counter incremented and there are no new trouble codes, the repair was successful and is now complete.

20. Erase any DTC's.