[Previous][Next]
Code No. U1000: OSS CAN timeout
cautionIf diagnostic trouble code No.U1000 is stored in the auto A/C controller assembly (A/C-ECU), diagnose the CAN main bus line.
cautionWhenever the ECU is replaced, ensure that the communication circuit is normal.
 
 
 
 
TROUBLE JUDGMENT
The auto A/C controller assembly (A/C-ECU) receives air conditioning control-related signals from the OSS via the CAN bus lines. If the ECU cannot receive any of the air conditioning control-related signals from the OSS, diagnostic trouble code U1000 will be stored.
 
 
 
COMMENTS ON TROUBLE SYMPTOM
Current trouble
  • Connector(s) or wiring harness in the CAN bus lines between the OSS and the auto A/C controller assembly (A/C-ECU), the power supply system to the OSS, the OSS itself, or the auto A/C controller assembly (A/C-ECU) may be faulty.
Past trouble
  • Carry out diagnosis with particular emphasis on connector(s) or wiring harness in the CAN bus lines between the auto A/C controller assembly (A/C-ECU) and the OSS, and the power supply system to the OSS. For diagnosis procedures, refer to "How to treat past trouble" (Refer to GROUP 00 - How to Treat Past Trouble ).
    noteFor a past trouble, you can not find it by the scan tool MB991958 CAN bus diagnostics even if there is any failure in CAN bus lines. In this case, refer to GROUP 00, How to Cope with Intermittent Malfunction and check the CAN bus lines. You can narrow down the possible cause of the trouble by referring to the diagnostic trouble code, which is stored regarding the CAN communication-linked ECUs (Refer to GROUP 54C - CAN Bus Line Diagnostic Flow ).
    cautionIf the ignition switch is turned to the ON position without starting the engine, diagnostic trouble code U1000 (past trouble) may be stored in the auto A/C controller assembly (A/C-ECU) after three minutes.
 
 
 
PROBABLE CAUSES
  • Damaged wiring harness or connectors
  • Malfunction of the OSS
  • Malfunction of the auto A/C controller assembly (A/C-ECU)
 
 
 
 
DIAGNOSIS
STEP 1. Using SCAN tool MB991958, diagnose the CAN bus lines.
Use the scan tool MB991958 to diagnose the CAN bus lines.
Is the check result normal?
Go to Step 2.
Repair the CAN bus lines (Refer to GROUP 54C Troubleshooting ). On completion, go to Step 6.
 
STEP 2. Check whether the DTC is stored.
Check whether the OSS-related diagnostic trouble code is stored.
Is the diagnostic trouble code stored?
Diagnose the OSS. (Refer to GROUP 42B Troubleshooting ).
Go to Step 3.
 
STEP 3. Check whether the DTC is stored again.
Check if a diagnostic trouble code, which relates to CAN communication-linked systems below, is stored.
  • ETACS-ECU
    U0100: OSS-related time-out diagnostic trouble code
Is the diagnostic trouble code stored?
Go to Step 4.
Go to Step 5.
 
STEP 4. Check whether the diagnostic trouble code is stored again.
Recheck if the diagnostic trouble code is stored.
(1) Erase the diagnostic trouble code.
(2) Ignition switch: LOCK (OFF) to ON
(3) Check if the diagnostic trouble code is stored.
Is the diagnostic trouble code stored?
Replace the OSS, and then go to Step 6.
A poor connection, open circuit or other intermittent malfunction in the CAN bus line between the OSS and auto A/C controller assembly (A/C-ECU) (Refer to GROUP 00 - How to Cope with Intermittent Malfunction ).
 
STEP 5. Check whether the diagnostic trouble code is stored again.
Recheck if the diagnostic trouble code is stored.
(1) Erase the diagnostic trouble code.
(2) Ignition switch: LOCK (OFF) to ON
(3) Check if the diagnostic trouble code is stored.
Is the diagnostic trouble code stored?
Replace the auto A/C controller assembly (A/C-ECU), and then go to Step 6.
A poor connection, open circuit or other intermittent malfunction in the CAN bus line between the OSS and the auto A/C controller assembly (A/C-ECU) (Refer to GROUP 00 - How to Cope with Intermittent Malfunction ).
 
STEP 6. Check whether the diagnostic trouble code is stored again.
Recheck if the diagnostic trouble code is stored.
(1) Erase the diagnostic trouble code.
(2) Ignition switch: LOCK (OFF) to ON
(3) Check if the diagnostic trouble code is stored.
Is the diagnostic trouble code stored?
Return to Step 1.
The procedure is complete.