Run Test Modules To Completion (07 12 07)

RUN TEST MODULES TO COMPLETION

TECHNICAL SERVICE BULLETIN

SUBJECT

Run Test Modules to Completion 

INFORMATION

In cases where multiple faults are set in a control module, the test module often runs through each of the fault codes sequentially within the same test module.

This means that more than one repair may need to be completed.

Exiting the test module to perform the first repair means that any additional repairs that follow later in the test module will be missed. Furthermore, if the first repair is a programming fix, this will result in any remaining fault codes being deleted as part of the programming process, making it impossible to go back to the test module for additional diagnosis.

As an example for ELV issues, the CAS (Car Access System) often has multiple stored faults (e.g., A112 and A116). The test module first diagnoses fault A112 and recommends a programming repair, together with a diagnosis/programming authorization code.* If the test module is allowed to continue, A116 is then diagnosed and a steering column replacement is required with an additional diagnosis authorization code.* Both repairs need to be performed. However, if the test module is terminated after the A112 diagnosis, the need to replace the steering column would be overlooked.

* Example only - the actual results of the test module vary.

As a general rule, it is most important  to fully complete diagnosis test modules without terminating before completion.

A completed test module is shown (1). Pressing the green arrow (2) exits the test module and returns the user to the Diagnosis Test Plan list.

Never "Quick delete" before starting a test module because test plans will not run if the faults have been deleted.

Additionally, if programming repairs are to be carried out, complete any other diagnosis before starting the programming session.

WARRANTY INFORMATION

For information only.