Pinpoint Test I : U3003:1C
NOTE:
DTC U3003:1C may be stored in the module memory due to past battery charging or vehicle jump starting events.
- I1 CHECK FOR BATTERY VOLTAGE DIAGNOSTIC TROUBLE CODES (DTCS) SET IN OTHER MODULES
- Ignition ON.
- Retrieve the Continuous Memory Diagnostic Trouble Codes (CMDTCs) from all modules.
Do any charging system Diagnostic Trouble Codes (DTCs) set in more than one module?
Yes For gas engines, REFER to: Charging System . No GO to I2 - I2 CHECK THE BATTERY VOLTAGE
- Turn off all the interior/exterior lights and accessories.
- Start and run the engine at approximately 2, 000 rpm for 3 minutes while monitoring the battery voltage.
Does the battery voltage rise to 15.5 volts or higher?
Yes For gas engines, REFER to: Charging System . No GO to I3 - I3 RECHECK FOR DTC (DIAGNOSTIC TROUBLE CODE) U3003:1C
- Engine OFF.
- Ignition ON.
- Clear the HUD module Continuous Memory Diagnostic Trouble Codes (CMDTCs).
- Using a diagnostic scan tool, perform the HUD module self-test.
Is DTC U3003:1C present?
Yes GO to I4 No The system is operating normally at this time. The DTC may have been set previously during battery charging or while jump starting the vehicle. - I4 CHECK FOR CORRECT HUD (HEAD UP DISPLAY) OPERATION
- Ignition OFF.
- Disconnect and inspect HUD module connector 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 HUD module connector 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 HUD module. REFER to: Head Up Display (HUD) Module . 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.