Pinpoint Test L : U0100: 00
- Refer to Module Communications Network
for schematic and connector information.
Normal Operation and Fault Conditions
The PAM communicates with the PCM on the HS-CAN1.
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition PAM U0100: 00 Lost Communication With ECM/PCM "A": No Sub Type Information A CM DTC that sets in the PAM when the PAM is unable to communicate with the PCM. Possible Sources
- Communication concern
- PCM
- PAM
- L1 VERIFY THE SCAN TOOL COMMUNICATES WITH THE PCM (POWERTRAIN CONTROL MODULE)
- Connect the diagnostic scan tool.
- Check that a vehicle session can be established using the scan tool.
Can a vehicle session be established?
Yes GO to L2 No REFER to: Communications Network . - L2 CHECK THE PAM (PARKING ASSIST CONTROL MODULE) CONTINUOUS MEMORY DIAGNOSTIC TROUBLE CODES (CM DTCS)
- Ignition ON.
- Using a diagnostic scan tool, perform the PAM self-test.
- Clear the Diagnostic Trouble Codes (DTCs).
- Wait 10 seconds.
- Repeat the PAM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to Diagnostic Trouble Code (DTC) Chart in this information. No GO to L3 - L3 PERFORM THE PCM (POWERTRAIN CONTROL MODULE) SELF-TEST
- Using a diagnostic scan tool, perform the PCM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). Refer to the appropriate Engine Information for the procedure. No GO to L4 - L4 RECHECK THE PAM (PARKING ASSIST CONTROL MODULE) DIAGNOSTIC TROUBLE CODES (DTCS)
- Using a diagnostic scan tool, clear the PAM Diagnostic Trouble Codes (DTCs).
- Ignition OFF.
- Ignition ON.
- Wait 10 seconds.
- Using a diagnostic scan tool, perform the continuous memory self-test.
- Check the PAM Diagnostic Trouble Codes (DTCs).
Is DTC U0100: 00 still present?
Yes GO to L5 No The system is operating correctly at this time. The DTC may have set due to high network traffic or an intermittent fault condition. - L5 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 PCM or PAM. 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
- 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 L6 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 PCM or PAM. If recent service history is found:
- L6 CHECK FOR CORRECT PCM (POWERTRAIN CONTROL MODULE) OPERATION
- Ignition OFF.
- Disconnect and inspect the PCM 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 PCM connectors and all 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, Refer to PCM Guided Routine Testing . 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.