Verification Test VER-5A - Road Test For OBD-II Trouble Codes

Related Image:

If the PCM has been replaced, do the following:

Important 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, Airbag, and SKIM modules. In addition, if the vehicle is equipped with a Sentry Key Immobilizer Module (SKIM), Secret Key data must be updated to enable starting.

For ABS and Airbag Systems:
ACTION:
1. Enter correct VIN and Mileage in the PCM.
2. Erase ABS and Airbag module codes.

For SKIM Theft Alarm:
ACTION:
1. Connect the DRB to the data link connector.
2. Go to Engine, Misc.., and place the SKIM in secured access mode, by using the appropriate PIN code for this vehicle.
3. Select update the Secret Key data, to be transferred from the SKIM to the PCM (this is required to allow the vehicle to start with the new PCM).
4. If three attempts are made to enter secured access mode using an incorrect PIN, secured access mode will be locked out for one hour. To exit this lock out mode, leave the ignition key in the Run/Start position for one hour. Ensure all accessories are turned off. Also monitor the battery state and connect a battery charger if necessary.

Continue Below

If the PCM has not been replaced, do the following:
All trouble codes should be repaired before continuing, if not, return to DTC-TEST and follow suggested test. After all DTCs are repaired, return to VER-5A and continue.
1. Connect the DRBIII to the data link connector.
2. Ensure the fuel tank is at least 1/4 full.
3. Turn off all accessories.

Note:
The best way to verify an OBD II DTC repair is to allow the PCM to run the appropriate "Trip" and increment a Good Trip which verifies that the repair was successful.

A component DTC will require 2 minutes of engine run time without any DTCs to increment Good Trip.

A monitor DTC, other than a Fuel Rich/Lean, LDP, Purge Flow or misfire DTC, will require using the DRB pre-test screens to allow the technician to meet the requirements to run that monitor.

A misfire or fuel Rich/Lean DTC will require using the Similar Conditions window to attempt to duplicate the operating conditions when the DTC was set to verify the repair.

The Purge Flow monitor will require using the Help screen (F1) on the DRB III when in the monitor screen.

The LDP monitor will require using VER-6A to verify repair.

If this verification procedure is being performed after a Component CODE repair, do the following:
4. After the ignition has been off for at least 10 seconds, restart the vehicle and run 2 minutes.
5. Did Starts since set and a Good Trip change to one or more? If yes, repair is complete, go to step 7; otherwise continue with step 6.
6. Look for any new DTCs set during the test. If there are new DTCs, return to DTC-TEST and follow suggested path.
7. If the Good Trip counter changed to one or more, the repair was successful.
8. Erase Trouble Codes.
9. Disconnect the DRB.

If this verification procedure is being performed after a MONITOR TROUBLE CODE repair, do the following:
4. With the DRB III, monitor the pre-test enabling conditions until all conditions have been met to run the appropriate monitor. Run the appropriate monitor for the repaired DTC.
5. If the repaired OBDII trouble code has reset, or the OBDII monitor failed after running, the repair is not complete. Check for any technical service bulletins or flash updates and return to DTC TEST.
6. If a new DTC has set, return to DTC TEST and follow the path specified for that code.
7. If the monitor ran, and the Good Trip counter changed to one or more, the repair was successful.
8. Erase Trouble Codes.
9. Disconnect the DRB.

If this verification procedure is being performed after a FUEL RICH/LEAN or MISFIRE TROUBLE CODE repair, do the following:
4. With the DRB III, monitor the Similar Conditions to attempt to duplicate the conditions that the vehicle was operating at when the code was set. If the conditions can be duplicated, the Misfire Good Trip counter will change to one or more. If the conditions cannot be duplicated continue with step 8.
5. If the repaired OBDII trouble code has reset, or the OBDII monitor failed after running, the repair is not complete. Check for any technical service bulletins or flash updates and return to DTC TEST.
6. If a new DTC has set, return to DTC TEST and follow the path specified for that code.
7. If the monitor ran, and the Good Trip counter changed to one or more, the repair was successful.
8. Erase Trouble Codes.
9. Disconnect the DRB.