Pinpoint Test I: Side Obstacle Detection Control Module Communication Faults - Multiple DTC'S
- Normal Operation and Fault Conditions
REFER to: Lane Keeping System - System Operation and Component Description .
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition IPMA U0232:00 Lost Communication With Side Obstacle Detection Control Module "A": No Sub Type Information A continuous memory DTC that sets in the IPMA if data messages received from the SODL through the GWM are missing 5 seconds or longer. IPMA U0233:00 Lost Communication With Side Obstacle Detection Control Module "B": No Sub Type Information A continuous memory DTC that sets in the IPMA if data messages received from the SODR through the GWM are missing 5 seconds or longer. IPMA U024E:00 Lost Communication With Side Obstacle Detection Control Module "C": No Sub Type Information A continuous memory DTC that sets in the IPMA if data messages received from the SODCMC through the GWM are missing 5 seconds or longer. IPMA U024F:00 Lost Communication With Side Obstacle Detection Control Module "D": No Sub Type Information A continuous memory DTC that sets in the IPMA if data messages received from the SODCMD through the GWM are missing 5 seconds or longer. IPMA U0533:86 Invalid Data Received From Side Obstacle Detection Control Module "A": Signal Invalid A continuous memory DTC that sets in the IPMA if invalid data messages received from the SODL through the GWM. IPMA U0534:86 Invalid Data Received From Side Obstacle Detection Control Module "B": Signal Invalid A continuous memory DTC that sets in the IPMA if invalid data messages received from the SODR through the GWM. IPMA U054F:86 Invalid Data Received From Side Obstacle Detection Control Module "C": Signal Invalid A continuous memory DTC that sets in the IPMA if invalid data messages received from the SODCMC through the GWM. IPMA U0550:86 Invalid Data Received From Side Obstacle Detection Control Module "D": Signal Invalid A continuous memory DTC that sets in the IPMA if invalid data messages received from the SODCMD through the GWM. Possible Sources
- Communication concern
- GWM
- SODL
- SODR
- SODCMC
- SODCMD
- I1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to I2 No CLEAR the DTC. The system is operating correctly at this time. The DTC may have been set due to high network traffic or an intermittent fault condition. - I2 CHECK THE COMMUNICATION NETWORK
- Using a diagnostic scan tool, perform the network test.
Does the SODL, SODR, SODCMC or SODCMD pass the network test?
Yes GO to I3 No REFER to: Controller Area Network (CAN) Module Communications Network . REFER to: Ethernet Module Communications Network . - I3 PERFORM THE IPMA (IMAGE PROCESSING MODULE A) SELF-TEST
- Using a diagnostic scan tool, perform the IPMA self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to the IPMA DTC Chart. No GO to I4 - I4 CHECK THE GWM (GATEWAY MODULE A) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, check the GWM Diagnostic Trouble Codes (DTCs).
Are any Diagnostic Trouble Codes (DTCs) present?
Yes REFER to: Controller Area Network (CAN) Module Communications Network . REFER to: Ethernet Module Communications Network . No GO to I5 - I5 PERFORM THE SODR (SIDE OBSTACLE DETECTION CONTROL MODULE RH) OR SODL (SIDE OBSTACLE DETECTION CONTROL MODULE LH) OR SODCMC (SIDE OBSTACLE DETECTION CONTROL MODULE C) OR SODCMD (SIDE OBSTACLE DETECTION CONTROL MODULE D) MODULE SELF-TEST
- Using a diagnostic scan tool, perform the SODL module, SODR module, SODCMC or SODCMD self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to: Blind Spot Information System . No GO to I6 - I6 RECHECK THE IPMA (IMAGE PROCESSING MODULE A) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, clear the IPMA Diagnostic Trouble Codes (DTCs).
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the continuous memory self-test. Check the IPMA Diagnostic Trouble Codes (DTCs).
Is DTC U0232:00, U0233:00, U024E:00, U024F:00, U0533:86, U0534:86, U054F:86 OR U0550:86 still present?
Yes GO to I7 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. - I7 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 PMI or the PMI may not have been carried out.
- Check the vehicle service history for recent service actions related to the SODL, SODR, SODCMC, SODCMD and the IPMA. If recent service history is found:
- verify correct replacement module was installed
- HVBOM may be used to verify correct part number
- 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 I8 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, SODR, SODCMC, SODCMD and the IPMA. If recent service history is found:
- I8 CHECK FOR CORRECT SODL (SIDE OBSTACLE DETECTION CONTROL MODULE LH), SODR (SIDE OBSTACLE DETECTION CONTROL MODULE RH), SODCMC (SIDE OBSTACLE DETECTION CONTROL MODULE C) AND SODCMD (SIDE OBSTACLE DETECTION CONTROL MODULE D) OPERATION
- Disconnect and inspect all the SODL, SODR, SODCMC or the SODCMD connectors.
- Repair:
- corrosion (install new connectors or terminals - clean module pins)
- damaged or bent pins - install new terminals pins
- pushed-out pins - install new pins as necessary
- Reconnect the SODL, SODR, SODCMC AND SODCMD connectors and make sure they seat and latch 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, replace suspect module:INSTALL a new SODL, REFER to: Side Obstacle Detection Control Module . INSTALL a new SODR, REFER to: Side Obstacle Detection Control Module . INSTALL a new SODCMC, REFER to: Side Obstacle Detection Control Module C (SODCMC) . INSTALL a new SODCMD, REFER to: Side Obstacle Detection Control Module D (SODCMD) . 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.