Pinpoint Test Ah : DTC U0253:00
- AH1 VERIFY THE CUSTOMER CONCERN
- Ignition ON.
- Verify there is an observable symptom present.
Is an observable symptom present?
Yes GO to AH2. No The system is operating normally at this time. The DTC may have been set due to high network traffic or an intermittent fault condition. - AH2 CHECK FOR LOST COMMUNICATION DTCs
- Ignition ON.
- Using a diagnostic scan tool, clear all CMDTCs.
- Ignition OFF.
- Wait at least 10 seconds.
- Ignition ON.
- Using a diagnostic scan tool, retrieve all CMDTCs.
Is DTC U0253:00 set in any audio system module?
Yes GO to AH3. No The system is operating normally at this time. The DTC may have been set due to high network traffic or an intermittent fault condition. - AH3 CHECK THE AUDIO SYSTEM MODULES FOR BATTERY VOLTAGE OUT-OF-RANGE DTCs
- Using a diagnostic scan tool, perform the self-test for the following modules:
- ACM
- APIM
- Audio DSP Module
Are any low or high voltage DTCs recorded in any module?
Yes For DTC U3003:16, GO to Pinpoint Test AJ . For DTC U3003:17, GO to Pinpoint Test AK . No GO to AH4. - Using a diagnostic scan tool, perform the self-test for the following modules:
- AH4 CHECK FOR DTC U0253:00 SET IN MULTIPLE MODULES
- Review the recorded results from the self-test.
Is DTC U0253:00 set in more than one audio system module?
Yes GO to AH5. No Refer to DTC chart . - AH5 CHECK FOR CORRECT APIM OPERATION
- Ignition OFF.
- Disconnect and inspect the APIM connector.
- Repair:
- Corrosion (clean module pins or install new connectors or terminals)
- Damaged or bent pins (install new terminals or pins)
- Pushed-out pins (install new pins as necessary)
- Reconnect the APIM connector. Make sure it seats and latches correctly.
- Operate the system and determine if the concern is still present.
Is the concern still present?
Yes CHECK OASIS for any applicable TSBs. If a TSB exists for this concern, DISCONTINUE this test and FOLLOW TSB instructions. If no TSBs address this concern, Refer to APIM HARDWARE 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.