Pinpoint Test F: U0140:00
WARNING: This page is about a different car, the 2021 Ford F-150. However, it is still accessible from the selected car via links, so may be relevant.
- Normal Operation and Fault Conditions
The PACM communicates with the BCM over the HS-CAN1.
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition PACM U0140:00 Lost Communication With Body Control Module: No Sub Type Information Sets on-demand and in continuous memory in the PACM module if data messages received from the BCM are missing for 5 seconds or longer. Possible Sources
- Communication concern
- BCM
- PACM concern
- F1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to F2 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. - F2 CHECK THE COMMUNICATION NETWORK
- Using a diagnostic scan tool, perform the network test.
Does the BCM pass the network test?
Yes GO to F3 No - F3 PERFORM THE PACM (PEDESTRIAN ALERT CONTROL MODULE) SELF-TEST
- Using a diagnostic scan tool, perform the PACM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to DTC Chart: PACM. No GO to F4 - F4 PERFORM THE BCM (BODY CONTROL MODULE) SELF-TEST
- Using a diagnostic scan tool, perform the BCM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to the appropriate DTC Chart. No GO to F5 - F5 RECHECK THE PACM (PEDESTRIAN ALERT CONTROL MODULE) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, clear the PACM Diagnostic Trouble Codes (DTCs).
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the continuous memory self-test.
- Check the PACM Diagnostic Trouble Codes (DTCs).
Is DTC U0140:00 still present?
Yes GO to F6 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. - F6 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 BCM or PACM module. 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 F7 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 BCM or PACM module. If recent service history is found:
- F7 CHECK FOR CORRECT BCM (BODY CONTROL MODULE) OPERATION
- Ignition OFF.
- Disconnect and inspect the BCM 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 BCM 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 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 BCM. REFER to: Body Control Module (BCM) . 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.