Pinpoint Test Aa: U0212:00
- Normal Operation and Fault Conditions
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition PAM U0212:00 Lost Communication With Steering Column Control Module: No Sub Type Information Sets in continuous memory in the PAM if data messages received from the SCCM through the GWM are missing for 5 seconds or longer. Possible Sources
- Communication concern
- SCCM
- PAM
- AA1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to AA2 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. - AA2 CHECK THE COMMUNICATION NETWORK
- Using a diagnostic scan tool, perform the network test.
Does the SCCM pass the network test?
Yes GO to AA3 No REFER to: Communications Network . - AA3 PERFORM THE PAM (PARKING ASSIST CONTROL MODULE) SELF-TEST
- Using a diagnostic scan tool, perform the PAM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to DTC Chart: PAM in this information. No GO to AA4 - AA4 PERFORM THE SCCM (STEERING COLUMN CONTROL MODULE) SELF-TEST
- Using a diagnostic scan tool, perform the SCCM self-test.
Are any non-network Diagnostic Trouble Codes (DTCs) present?
Yes REFER to: Steering Wheel and Column Electrical Components . No GO to AA5 - AA5 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 U0212:00 present?
Yes GO to AA6 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. - AA6 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 SCCM or PAM. 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
- 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 AA7 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 SCCM or PAM. If recent service history is found:
- AA7 CHECK FOR CORRECT SCCM (STEERING COLUMN CONTROL MODULE) OPERATION
- Ignition OFF.
- Disconnect and inspect the SCCM 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 SCCM 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 SCCM. REFER to: Steering Column Control Module (SCCM) . 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.