Pinpoint Test BG: U0232:00, U0533:00 Or U0533:82
- Normal Operation and Fault Conditions
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition IPC U0232:00 Lost Communication With Side Obstacle Detection Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the SODL through the GWM are missing for 5 seconds or longer. IPC U0533:00 Invalid Data Received From Side Obstacle Detection Control Module "A": No Sub Type Information Sets in continuous memory in the IPC if data messages received from the SODL through the GWM are missing or invalid for 5 seconds or longer. IPC U0533:82 Invalid Data Received From Side Obstacle Detection Control Module "A": Alive/Sequence Counter Incorrect/Not Updated Sets in continuous memory in the IPC if the IPC receives invalid side obstacle network data from the SODL through the GWM. Possible Sources
- Communication concern
- GWM concern
- SODL
- IPC concern
- BG1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to BG2 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. - BG2 CHECK THE COMMUNICATION NETWORK
- Using a diagnostic scan tool, perform the network test.
Does the SODL pass the network test?
Yes GO to BG3 No - BG3 PERFORM THE IPC (INSTRUMENT PANEL CLUSTER) SELF-TEST
- Using a diagnostic scan tool, perform the IPC self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to Diagnostic Trouble Code (DTC) Chart . No GO to BG4 - BG4 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) recorded?
Yes No GO to BG5 - BG5 PERFORM THE SODL (SIDE OBSTACLE DETECTION CONTROL MODULE LH) SELF-TEST
- Using a diagnostic scan tool, perform the SODL self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to BLIND SPOT INFORMATION SYSTEM . No GO to BG6 - BG6 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).
Is DTC U0232:00, U0533:00 or U0533:82 still present?
Yes GO to BG7 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. - BG7 CHECK FOR OTHER CAUSES OF COMMUNICATION NETWORK CONCERNNOTE: If new modules were installed prior to the DTC being set, the module configuration may 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 SODL, 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 BG8 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 SODL, GWM or IPC. If recent service history is found:
- BG8 CHECK FOR CORRECT SODL (SIDE OBSTACLE DETECTION CONTROL MODULE LH) OPERATION
- Ignition OFF.
- Disconnect and inspect the SODL connector.
- 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 SODL connector. Make sure it seats and latches 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 SODL. 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.