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

Inspect the vehicle to ensure that all engine components are connected. Reassemble and reconnect components as necessary.

If there are any existing diagnostic trouble codes that have not been repaired, go to Trouble Code (TC) Tests perform DTC TEST and follow the path specified.

After all diagnostic trouble codes have been repaired, return to TEST VER-5A and run the monitor for the previously repaired OBD-II trouble code.

1. Connect the DRBIII (or equivalent Scantool), to the data link connector.
2. Ensure the fuel tank has at least a quarter tank of fuel.
3. Turn the air conditioning off.
4. The proper way to verify that the trouble code has been repaired is to allow the powertrain control module to run the monitor. The technician can see the monitor run using the Scantool. The enabling conditions must be met before the powertrain control module will run the monitor. The enabling conditions for the covered OBD-II codes can be found under Trouble Code Descriptions.

- Read the enabling conditions for the trouble code that was repaired. The enabling conditions are different for each OBD-II code.

5. With the Scantool, monitor the pre-test enabling conditions until all conditions have been met. Once the enabling conditions have been met, monitor the appropriate OBD-II monitor with the Scantool.
6. If the repaired OBD-II trouble code has reset or was seen in the OBD-II monitor while on the road test, the repair is not complete. Check for any related Technical Service Bulletins and return to Trouble Code (TC) Tests, DTC TEST.
- If another trouble code has set, return to Trouble Code (TC) Tests, DTC TEST and follow the path specified for that trouble code.
- If there are no trouble codes, the repair was successful and is now complete.