- Strategy Based Diagnosis

Strategy Based Diagnostics
The strategy based diagnostic is a uniform approach to repair all Electrical/Electronic (E/E) systems. The diagnostic flow can always be used to resolve an E/E system problem and is a starting point when repairs are necessary. The steps below are defined to instruct the technician how to proceed with a diagnosis.

1. Verify the Customer Concern

To verify the customer concern, the technician should know the normal operation of the system.

2. Preliminary Checks

Conduct a thorough visual inspection, review the service history, detect unusual sounds or odors, and gather diagnostic trouble code information to achieve an effective repair.

3. Service Information System Check(s). Computers and Control Systems / System Diagnostic Tables contains System Checks where a system may not be supported by one or more DTCs. System checks verify proper operation of the system. This will lead the technician in an organized approach to diagnostics. Testing and Inspection

4. Check Technical Service Bulletins.

5. Service Diagnostics

5.1. DTC Stored - Follow the designated Diagnostic Trouble Code (DTC) chart exactly to make an effective repair. Testing and Inspection

5.2. Symptom, No DTC - Select the symptom from the Symptom Tables in Computers and Control System and follow the diagnostic paths or suggestions to complete the repair, or refer to the applicable component/system check. Testing and Inspection

5.3. No Published Diagnostics - Analyze the complaint and develop a plan for diagnostics. Utilize the wiring diagrams and theory of operation. Combine technician knowledge with efficient use of the available service information.

5.4. Intermittent - Conditions that are not always present are intermittent. To resolve intermittents, perform the following steps:

5.4.1 Observe history DTCs, DTC modes and freeze frame data.

5.4.2 Evaluate the symptoms and conditions described by the customer.

5.4.3 Use a check sheet or other method to identify the circuit or electrical system component.

5.4.4 Follow the suggestions for intermittent diagnosis found in Symptoms. - Intermittent Malfunctions

5.4.5 The Tech 1, Tech 2 and Fluke 87 have data capturing capabilities that can assist in detection of intermittents.

5.5. Vehicle operates as designed/No trouble found.

5.6. Search vehicle histories for similar cases. Combine technician knowledge with efficient use of the available service information.

5.6.1. This condition exists when the vehicle is found to operate normally.

5.6.2. The condition described by the customer may be normal. Verify against another vehicle that is operating normally.

5.6.3. The condition may be intermittent. Verify the complaint under the conditions described by the customer before releasing the vehicle.

6. Re-examine the Concern.

When the complaint cannot be successfully found or isolated, a reevaluation is necessary. The complaint should be re-verified and could be intermittent or normal as per 5.3 or 5.5 above.

7. Repair and Verification Tests.

After isolating the cause, the repairs should be made. Then validate for proper operation and verify that the symptom has been corrected. This may involve road testing or other methods to verify the complaint has been resolved.