Pinpoint Test F: Lost Communication With Another Module
- Refer to FOUR WHEEL DRIVE SYSTEMS
for schematic and connector information. Refer to MODULE COMMUNICATION NETWORK
for schematic and connector information.
Normal Operation and Fault Conditions
The AWD module expects to receive network data from other modules on HS-CAN1. The AWD will set a DTC when it has not received messages from a module for more than 10.5 seconds. Other modules that require data from the suspect module may set lost communication DTC.
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition AWD U0100:00 Lost Communication With ECM/PCM 'A': No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0101:00 Lost Communication with TCM: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0121:00 Lost Communication With Anti-Lock Brake System (ABS) Control Module 'A': No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0126:00 Lost Communication With Steering Angle Sensor Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0137:00 Lost Communication With Trailer Brake Control Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0138:00 Lost Communication with All Terrain Control Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0140:00 Lost Communication With Body Control Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0146:00 Lost Communication With Serial Data Gateway 'A': No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0151:00 Lost Communication With Restraints Control Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0155:00 Lost Communication With Instrument Panel Cluster (IPC) Control Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0164:00 Lost Communication With HVAC Control Module 'A': No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. AWD U0212:00 Lost Communication With Steering Column Control Module: No Sub Type Information This DTC sets when the AWD has not received messages from the suspect module for more than 10.5 seconds. Possible Sources
- Suspect module
- Battery voltage concern
- FD-CAN +
- FD-CAN -
- F1 CHECK FOR LOST COMMUNICATION DTC (DIAGNOSTIC TROUBLE CODE) IN OTHER MODULES
- Enter the following diagnostic mode: Run all CMDTC.
Do any other modules on the vehicle also have a Lost Communication DTC with the suspect module?
Yes REFER to: Controller Area Network (CAN) Module Communications Network . No GO to F2 - F2 REVIEW CMDTC (CONTINUOUS MEMORY DIAGNOSTIC TROUBLE CODE) FOR LOW VOLTAGE DTC (DIAGNOSTIC TROUBLE CODE)
- Review all module CMDTC for low voltage DTC.
Do any modules have low voltage DTC set?
Yes Resolve all vehicle voltage concerns. REFER to: Charging System - 2.3L EcoBoost (199kW/270PS) . REFER to: Charging System - 2.7L EcoBoost (238kW/324PS) . No GO to F3 - F3 INSPECT FD-CAN (FLEXIBLE DATA RATE CONTROLLER AREA NETWORK) CONNECTORS
- Refer to MODULE COMMUNICATION NETWORK for schematic and connector information. DISCONNECT and INSPECT the FD-CAN connectors between the AWD and the suspect module.
- Repair:
- 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.
- Connect all connectors. Make sure each connector 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 TSB, GSB, SSM, or FSA. If a service article exists for this concern, DISCONTINUE this test and FOLLOW the service article instructions. If no service articles address this concern, INSTALL a new suspect module. 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.