Pinpoint Test E: Lost Communication With Suspect Module
- Refer to Wiring Diagrams Two Wheel Drive/Four Wheel Drive Systems
for schematic and connector information. Refer to Wiring Diagrams Module Communications Network
for schematic and connector information.
Normal Operation and Fault Conditions
The TCCM communicates directly on the HS-CAN2 network with the ATCM, ABS module, and GWM. The TCCM communicates with the PCM, TCM, and BCM on the HS-CAN1 network via the GWM. The TCCM communicates with the IPC on the HS-CAN3 network via the GWM.
The TCCM sets a DTC for lost communication when it has not received messages from the suspect module for more than 5 seconds with ignition in RUN and battery voltage in range. Other modules that require data from the suspect module may also set a lost communication DTC if the fault is common to both receiving modules.
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition TCCM U0100:00 Lost Communication With ECM/PCM "A": No Sub Type Information Sets in continuous memory in the TCCM if powertrain data messages received from the PCM over the HS-CAN are missing for longer than 5 seconds with ignition in RUN and battery voltage in range. TCCM U0101:00 Lost Communication with TCM: No Sub Type Information Sets in continuous memory in the TCCM if powertrain data messages received from the TCM over the HS-CAN are missing for longer than 5 seconds with ignition in RUN and battery voltage in range. TCCM U0121:00 Lost Communication With Anti-Lock Brake System (ABS) Control Module "A": No Sub Type Information Sets in continuous memory in the TCCM if ABS module data messages received from the ABS module over the HS-CAN are missing for longer than 5 seconds. TCCM U0138:00 Lost Communication with All Terrain Control Module: No Sub Type Information Sets in continuous memory in the TCCM if data messages received from the Terrain Management module through the GWM are missing for 5 seconds or longer. TCCM U0140:00 Lost Communication With Body Control Module: No Sub Type Information Sets in continuous memory in the TCCM if data messages received from the BCM through the GWM are missing for 5 seconds or longer. Possible Sources
- Communication concern
- Battery voltage concern
- Network fault
- Intermittent network traffic jam
- PCM, TCM, ABS, ATCM, BCM, IPC
- E1 VERIFY THE SCAN TOOL COMMUNICATES WITH THE PCM (POWERTRAIN CONTROL MODULE)
- Ignition ON.
- Connect a diagnostic scan tool.
- check that a vehicle session can be established using a diagnostic scan tool.
Can a vehicle session be established?
Yes GO to E2 No CHECK the module communications network, module does not respond to the scan tool. REFER to: Controller Area Network (CAN) Module Communications Network . - E2 CHECK THE ATCM (ALL TERRAIN CONTROL MODULE) CONTINUOUS MEMORY DTC (DIAGNOSTIC TROUBLE CODE)S
- Using a diagnostic scan tool, perform the ATCM self-test.
- Clear the DTCs.
- Wait 10 seconds.
- Repeat the ATCM module self-test.
Is DTC U0100?
Yes GO to E3 No The system is operating correctly at this time. The DTC may have been set due to high network traffic or an intermittent fault condition. - E3 RETRIEVE THE RECORDED DTC (DIAGNOSTIC TROUBLE CODE) S FROM THE PCM (POWERTRAIN CONTROL MODULE) KOEO (KEY ON, ENGINE OFF) SELF-TEST
- Using a diagnostic scan tool, perform the PCMKOEO self-test.
Are any DTCs recorded?
Yes DIAGNOSE and REPAIR all suspect module DTC, REFER to: 2.7L EcoBoost Electronic Engine Controls . REFER to: 3.3L Duratec-V6 Electronic Engine Controls . REFER to: 3.5L EcoBoost (BM)Electronic Engine Controls . REFER to: 3.5L V6 PowerBoost (CN) Electronic Engine Controls . REFER to: 5.0L 32V Ti-VCT Electronic Engine Controls . REFER to: 3.0L Power Stroke Diesel Electronic Engine Controls . REFER to: 3.5L V6 PowerBoost (CN) Electric Powertrain Control . No GO to E4 - E4 RETRIEVE THE RECORDED DTC (DIAGNOSTIC TROUBLE CODE) S FROM THE AWD (ALL-WHEEL DRIVE) MODULE SELF-TEST
- Using a diagnostic scan tool, perform the ATCM self-test.
Is DTC P0562:00 or P0563:00 recorded?
Yes REFER to: Controller Area Network (CAN) Module Communications Network . No GO to E5 - E5 CHECK FOR DTC (DIAGNOSTIC TROUBLE CODE) S U0100 SET IN OTHER MODULES
- Using a diagnostic scan tool, clear all DTCs.
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the continuous memory self-test.
- Retrieve the CMDTCs from all modules.
Are any of the DTCs U0100 set in other modules on the network?
Yes GO to E6 No GO to E7 - E6 CHECK FOR CORRECT PCM (POWERTRAIN CONTROL MODULE) OPERATION
- Ignition OFF.
- Disconnect and inspect all PCM connectors.
- Repairs:
- corrosion (install new connector or terminals - clean module pins)
- damaged or bent pins - install new terminals/pins
- pushed-out pins - install new pins as necessary
- Reconnect the PCM connectors. Make sure they seat and latch correctly.
- Operate the system and verify the concern is still present.
Is the concern still present?
Yes CHECK OASIS for any applicable TSB. If a TSB exists for this concern, DISCONTINUE this test and FOLLOW TSB instructions. If no TSB address this concern, Refer to PCM GUIDED ROUTINE TESTING
Internet Explorer version 11 or greater is required to perform this Pinpoint Test. . REFER to: REMOVAL AND INSTALLATION .No The system is operating correctly at this time. The concern may have been caused by module connections. ADDRESS the root cause of any connector or pin issues. - E7 CHECK FOR CORRECT ATCM (ALL TERRAIN CONTROL MODULE) OPERATION
- Ignition OFF.
- Disconnect and inspect the ATCM connector.
- Repair:
- Reconnect the ATCM connector. Make sure it seats and latches correctly.
- Operate the system and verify the concern is still present
Is the concern still present?
Yes CHECK OASIS for any applicable TSBs. If a TSB exists for this concern, DISCONTINUE this test and FOLLOW TSB instructions. If no TSBs address this concern, INSTALL a new AWD module. REFER to: All Terrain Control Module (ATCM) - Vehicles With: Center Console . REFER to: All Terrain Control Module (ATCM) - Vehicles Without: Center Console . No The system is operating correctly at this time. The concern may have been caused by module connections. ADDRESS the root cause of any connector or pin issues.