Pinpoint Test I : DTC (Diagnostic Trouble Code) U0199:00
WARNING: This page is about a different car, the 2018 Ford F-250 Super Duty. However, it is still accessible from the selected car via links, so may be relevant.
- 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 normally 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 DDM pass the network test?
Yes GO to I3 No REFER to: Communications Network . - I3 PERFORM THE SODL (SIDE OBSTACLE DETECTION CONTROL MODULE LH) OR SODR (SIDE OBSTACLE DETECTION CONTROL MODULE RH) SELF-TEST
- Using a diagnostic scan tool, check the SODL or SODR Continuous Memory Diagnostic Trouble Codes (CMDTCs).
Are any Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to SODL and SODR DTC Chart . No GO to I4 - I4 CHECK THE DDM (DRIVER DOOR MODULE) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, perform the DDM self-test.
Are any Diagnostic Trouble Codes (DTCs) present?
Yes REFER to: Communications Network . No GO to I5 - I5 RECHECK THE SODL (SIDE OBSTACLE DETECTION CONTROL MODULE LH) OR SODR (SIDE OBSTACLE DETECTION CONTROL MODULE RH) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, clear the SODL or SODR Diagnostic Trouble Codes (DTCs).
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the continuous memory self-test.
- Check the SODL or SODR Diagnostic Trouble Codes (DTCs).
Is DTC U0199:00 present?
Yes GO to I6 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. - I6 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 DDM, SODL or SODR. If recent service history is found:
- verify correct replacement module was installed
- HVBOM 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
- if a new replacement module is installed, PERFORM PMI using as-built data
- 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 I7 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 DDM, SODL or SODR. If recent service history is found:
- I7 CHECK FOR CORRECT DDM (DRIVER DOOR MODULE) OPERATION
- Ignition OFF.
- Disconnect and inspect all DDM connectors and related in-line connectors.
- 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 DDM connectors and related in-line connectors. 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 Technical Service Bulletins (TSBs). If a TSB exists for this concern, DISCONTINUE this test and FOLLOW TSB instructions. If no Technical Service Bulletins (TSBs) address this concern, INSTALL a new DDM. Refer to: Driver Door Module (DDM) . No The system is operating correctly at this time. Concern may have been caused by a loose or corroded connector. ADDRESS the root cause of any connector or pin issues.