Communications Network - Troubleshooting

--
COMMUNICATIONS NETWORK - TROUBLESHOOTING - HYBRID

Inspection and Verification

1. Verify the customer concern.

2. Visually inspect 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 scan tool software release.

NOTE: The vehicle communication module (VCM) LED prove-out confirms power and ground from the DLC are provided to the VCM.

4. If the cause is not visually evident, connect the scan tool to the DLC.If the scan tool does not communicate with the VCM:

- Check the VCM connection to the vehicle.
- Check the scan tool connection to the VCM.
- See - Pinpoint Test 17: No Power To The Scan Tool.


NOTE: During the network test, the scan tool will first attempt to communicate with the PCM, after establishing communication with the PCM, the scan tool will then attempt to communicate with all other modules on the vehicle.

1. Carry out the network test.

- If the network test passes, retrieve and record the continuous memory DTCs and GO to the next step.
- If the network test fails, see - Symptom Troubleshooting Chart to identify the module not communicating.

2. If the DTCs retrieved are related to the concern, go to -- DTC Chart - Communications Network. Follow the non-network DTC diagnostics (B-codes, C-codes, P-codes) prior to the network DTC diagnostics (U-codes). For all other DTCs, see -- Diagnostic Trouble Code (DTC) Chart - B, C, P And U Codes.

3. If no DTCs related to the concern are retrieved, see - Symptom Troubleshooting Chart.