Pinpoint Test Bn: Lost Communication With A Module
- Normal Operation and Fault Conditions
REFER to: Controller Area Network (CAN) Module Communications Network - System Operation and Component Description .
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition IPC U0100:00 Lost Communication With ECM/PCM "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the PCM through the GWM are missing for 5 seconds or longer. IPC U0103:00 Lost Communication With Gear Shift Control Module A: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the GSM through the GWM are missing for 5 seconds or longer. IPC U0111:82 Lost Communication With Battery Energy Control Module "A": Alive/Sequence Counter Incorrect/Not Updated Sets in continuous memory in the IPC if data messages received from the BECM through the GWM are missing for 5 seconds or longer. IPC U0121:00 Lost Communication With Anti-Lock Brake System (ABS) Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the ABS module through the GWM are missing for 5 seconds or longer. IPC U0136:82 Lost Communication With Differential Control Module - Rear: Alive/Sequence Counter Incorrect/Not Updated Sets in continuous memory in the IPC if data messages received from the DCMR through the GWM are missing for 5 seconds or longer. IPC U013F:00 Lost Communication With Pedestrian Alert Control Module: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the PACM through the GWM are missing for 5 seconds or longer. IPC U0140:00 Lost Communication With Body Control Module: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the BCM through the GWM are missing for 5 seconds or longer. IPC U0146:00 Lost Communication With Serial Data Gateway "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the GWM are missing for 5 seconds or longer. IPC U0151:00 Lost Communication With Restraints Control Module: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the RCM through the GWM are missing for 5 seconds or longer. IPC U0159:00 Lost Communication With Parking Assist Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if parking assist data messages received from the IPMA through the GWM are missing for 5 seconds or longer. IPC U0193:00 Lost Communication With "Digital Audio Control Module A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the ACM are missing for 5 seconds or longer. IPC U0198:00 Lost Communication With Telematic Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the TCU are missing for 5 seconds or longer. IPC U0212:00 Lost Communication With Steering Column Control Module: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the SCCM through the GWM are missing for 5 seconds or longer. IPC U0212:82 Lost Communication With Steering Column Control Module: Alive/Sequence Counter Incorrect/Not Updated Sets in continuous memory in the IPC if data messages received from the SCCM through the GWM are missing for 5 seconds or longer. IPC U0232:00 Lost Communication With Side Obstacle Detection Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if side obstacle detection data messages received from the IPMA through the GWM are missing for 5 seconds or longer. IPC U0233:00 Lost Communication With Side Obstacle Detection Control Module "B": No Sub Type Information Sets in continuous memory in the IPC if side obstacle detection data messages received from the IPMA through the GWM are missing for 5 seconds or longer. IPC U023A:00 Lost Communication With Image Processing Module A: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the IPMA through the GWM are missing for 5 seconds or longer. IPC U023A:82 Lost Communication With Image Processing Module A: Alive/Sequence Counter Incorrect/Not Updated Sets in continuous memory in the IPC if data messages received from the IPMA through the GWM are missing for 5 seconds or longer. IPC U023B:00 Lost Communication With Image Processing Module B: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the HCM through the GWM are missing for 5 seconds or longer. IPC U0253:00 Lost Communication With Accessory Protocol Interface Module: No Sub Type Information Sets in continuous memory in the IPC if data messages received from the APIM are missing for 5 seconds or longer. IPC U0293:00 Lost Communication With Hybrid/EV Powertrain Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the PCM (HEV) through the GWM are missing for 5 seconds or longer. IPC U0293:82 Lost Communication With Hybrid/EV Powertrain Control Module "A": Alive/Sequence Counter Incorrect/Not Updated Sets in continuous memory in the IPC if data messages received from the PCM (HEV) through the GWM are missing for 5 seconds or longer. Possible Sources
- Communication concern
- Battery voltage concern
- CAN module fault determined by a lost communication DTC being set
- GWM
- IPC
- BN1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to BN2 No CLEAR the DTC. The system is operating normally at this time. The DTC may have been set due to high network traffic or an intermittent fault condition. - BN2 CHECK THE COMMUNICATION NETWORK
- Using a diagnostic scan tool, perform the network test.
Do all modules pass the network test?
Yes GO to BN3 No REFER to: Controller Area Network (CAN) Module Communications Network . - BN3 CHECK THE IPC (INSTRUMENT PANEL CLUSTER) CONTINUOUS MEMORY DIAGNOSTIC TROUBLE CODES (CMDTCS)
- Using a diagnostic scan tool, perform the IPC self-test.
- Clear the Diagnostic Trouble Codes (DTCs).
- Wait 10 seconds.
- Repeat the IPC self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to Diagnostic Trouble Code (DTC) Chart . No GO to BN4 - BN4 PERFORM THE SELF-TEST
- Determine which lost communication Diagnostic Trouble Codes (DTCs) set during the IPC self test.
- Using a diagnostic scan tool, perform the self-test for the module(s) that set a lost communication fault in the IPC.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to the Master DTC Chart. No GO to BN5 - BN5 CHECK THE GWM (GATEWAY MODULE A) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, check the GWM Continuous Memory Diagnostic Trouble Codes (CMDTCs).
Are any Diagnostic Trouble Codes (DTCs) set?
Yes REFER to: Controller Area Network (CAN) Module Communications Network . No GO to BN6 - BN6 RECHECK THE IPC (INSTRUMENT PANEL CLUSTER) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, clear the IPC Diagnostic Trouble Codes (DTCs).
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the continuous memory self-test.
- Check the IPC Diagnostic Trouble Codes (DTCs).
Are any lost communication Diagnostic Trouble Codes (DTCs) still present?
Yes GO to BN7 No The system is operating correctly at this time. The DTC may have set due to high network traffic or an intermittent fault condition. - BN7 CHECK FOR OTHER CAUSES OF COMMUNICATION NETWORK CONCERNNOTE: If new modules were installed prior to the DTC being set, the module configuration can be incorrectly set during the PMI or the PMI may not have been carried out.
- CHECK the vehicle service history for recent service actions related to the module(s) in question, GWM or IPC. If recent service history is found:
- verify correct replacement module was installed
- vehicle parts build may be used to verify correct part fitment
- verify the configuration of replacement module was correct
- re-configure module using as-built data if prior configuration is suspect
- verify the module was not obtained from a like vehicle and installed into customer vehicle
- return the swapped module to source vehicle and obtain new replacement module
- verify correct replacement module was installed
- Operate the system and determine if the observable symptom is still present.
Is the observable symptom still present?
Yes GO to BN8 No The system is operating correctly at this time. The concern may have been due to incorrect parts replacement procedures or incorrect module configuration. - CHECK the vehicle service history for recent service actions related to the module(s) in question, GWM or IPC. If recent service history is found:
- BN8 CHECK FOR CORRECT OPERATION OF THE MODULE IN QUESTION
- Ignition OFF.
- Disconnect and inspect the module connector(s).
- 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
- Reconnect the module connector(s). Make sure they (it) seat(s) and latch(es) correctly.
- Operate the system and determine if the concern is still present.
Is the concern still present?
Yes CHECK OASIS for any applicable service articles: 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 module in question. REFER to the appropriate removal and installation procedure. 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.