Initial Inspection and Diagnostic Overview
COMMUNICATION NETWORKInspection and Verification
1. Verify the customer concern.
2. Visually inspect the following for obvious signs of electrical damage.
3. If an obvious cause for an observed or reported concern is found, correct the cause (if possible) before proceeding to the next step.
NOTE: Make sure to use the latest IDS or equivalent tester software release.
4. If the cause is not visually evident, connect the IDS or equivalent tester to the DLC.
NOTE:
- The vehicle communication module (VCM) LED prove-out confirms power and ground from the DLC are provided to the VCM.
- If the IDS or equivalent tester does not communicate with the VCM:
- Check the VCM connection to the vehicle.
- Check the IDS or equivalent tester connection to the VCM.
- See PINPOINT TEST 7: NO MODULE/NETWORK COMMUNICATION - NO POWER TO THE DIAGNOSTIC TOOL3, to diagnose no power to the IDS or equivalent tester. Pinpoint Test 7: No Module/Network Communication - No Power to the Diagnostic Tool
- During the network test, the IDS or equivalent tester will first attempt to communicate with the PCM, after establishing communication with the PCM, the IDS or equivalent tester will then attempt to communicate with all other modules on the vehicle.
5. Carry out the network test.
- If the network test passes, retrieve and record the continuous memory DTCs and proceed to Step 6.
- If the network test fails, see SYMPTOM TROUBLESHOOTING CHART - COMMUNICATIONS NETWORK, to identify the module not communicating. Symptom Related Diagnostic Procedures
6. If the DTCs retrieved are related to the concern, go to that module's Diagnostic Trouble Code (DTC) Index. For all other DTCs, see DIAGNOSTIC TROUBLE CODE (DTC) INDEX - B, C AND U CODES.
7. If no DTCs related to the concern are retrieved, see SYMPTOM TROUBLESHOOTING CHART - COMMUNICATIONS NETWORK. Symptom Related Diagnostic Procedures