Pinpoint Test Ag : U0233:00
WARNING: This page is about a different car, the 2018 Lincoln Navigator. However, it is still accessible from the selected car via links, so may be relevant.
- AG1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to AG2 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. - AG2 CHECK THE COMMUNICATION NETWORK
- Using a diagnostic scan tool, perform the network test.
Does the SODR pass the network test?
Yes GO to AG3 No REFER to: Communications Network . - AG3 CHECK FOR NON-NETWORK SODR (SIDE OBSTACLE DETECTION CONTROL MODULE RH) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, perform the SODR self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to: Blind Spot Information System . No GO to AG4 - AG4 CHECK FOR NON-NETWORK PDM (PASSENGER DOOR MODULE) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, perform the PDM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to DTC Chart: PDM . No GO to AG5 - AG5 RECHECK THE PDM (PASSENGER DOOR MODULE) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, clear the Diagnostic Trouble Codes (DTCs).
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the PDM self-test.
Is DTC U0233:00 still present?
Yes GO to AG6 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. - AG6 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 SODR and the PDM. 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 AG7 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 SODR and the PDM. If recent service history is found:
- AG7 CHECK FOR CORRECT SODR (SIDE OBSTACLE DETECTION CONTROL MODULE RH) OPERATION
- Disconnect and inspect all the SODR 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 SODR 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, INSTALL a new SODR. REFER to: Side Obstacle Detection Control 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.