Stored Lost Communication DTCs

STORED LOST COMMUNICATION DTCS





For complete wiring diagram refer to the wiring section.

WHEN MONITORED
- With the ignition on
- Battery voltage between 10 and 16 volts
- IOD fuse installed
- FCM is configured correctly

SET CONDITION
Bus messages not received from for approximately 2 to 5 seconds.

POSSIBLE CAUSES
- CAN B bus circuits open or shorted
- DTCs related to battery voltage, ignition, or VIN messages
- FCM not configured correctly
- Power or ground from the reporting module
- Module that set this DTC
- Previous service performed within the last 100 key cycles (fuse/relays removed, wiring service, battery disconnect)
- Low battery/jump start condition
- IOD fuse was removed during shipping
- Check for related TSBS

DIAGNOSTIC TEST

1. VERIFY DTC IS STORED

NOTE:
- Stored faults may indicate a customer perceived intermittent condition.
- Ensure the IOD fuse is installed and battery voltage is between 10 and 16 volts before proceeding. With the scan tool, read stored DTCs.

Q: Is this DTC stored?

YES: Go To 2
NO: Diagnose the active DTC. Refer to the table of contents for a list of the symptoms. Perform BODY VERIFICATION TEST - VER 1. Body Verification Test

2. CHECK THE ENVIRONMENTAL DATA
With the scan tool, read the lost of communication environmental data.

Q: Does the lost of communication environmental odometer data match up to any of the previous service procedures listed in the possible causes or are their any stored CAN B or C hardware electrical, battery, ignition voltage, VIN missing/mismatch, FCM configuration DTCs present with match environmental data?

YES: These DTCs may have been the result of other service procedures performed. Clear DTCs. Perform BODY VERIFICATION TEST - VER 1. Body Verification Test
NO: Go To 3

3. VERIFY INTERMITTENT LOST COMMUNICATION DTC-WIRING CONCERNS
Turn the ignition on.
With the scan tool, select Network Diagnostics.

Q: Is there more than one ECU with stored DTCs "Logged Against" the module and one or more lost communication DTCs stored in the offending module?

YES: Verify if the vehicle was recently in for this type of service. Otherwise, visually inspect the related wiring harness for chafed, pierced, pinched, and partially broken wires and the wiring harness connectors for broken, bent, pushed out, and corroded terminals. Repair as necessary.
NO: Go To 4

4. VERIFY INTERMITTENT LOST COMMUNICATION DTC- OFFENDING MODULE
Turn the ignition on.
With the scan tool, select Network Diagnostics.

Q: Is there more than one ECU with stored DTCs "Logged Against" the module and NO lost communication DTCs stored in the offending module?

YES: Check for TSB related to this offending module.
NO: Go To 5

5. VERIFY INTERMITTENT LOST COMMUNICATION DTC- REPORTING MODULE
Turn the ignition on.
With the scan tool, select Network Diagnostics.

Q: Is there ONLY ONE ECU with stored DTCs "Logged Against" the module?

YES: Check for TSB related to the module that set this DTC.
NO: Verify if the vehicle was recently in for this type of service. Otherwise, visually inspect the related wiring harness for chafed, pierced, pinched, and partially broken wires and the wiring harness connectors for broken, bent, pushed out, and corroded terminals. Repair as necessary.