• Code: SC664-02
• Description: ASIC on the BCU SRAM Program Expansion Error. Write Error to ASIC on the BCU SRAM (write result error)
• Causes: • Electrical Noise. • Hardware defection
• Remedy: • Replace the imaging BCU and paper transport BCU. • Check the harness.

• Code: SC664-03
• Description: ASIC on the BCU SRAM Program Expansion Error. ASIC on the BCU Program Startup Error
• Causes: • Electrical Noise. • Hardware defection
• Remedy: • Replace the imaging BCU and paper transport BCU. • Check the harness.

• Code: SC665-01
• Description: BCU-IPU Connection Error The machine checks the FFC (Flat Flexible Cable) connections at the HORUS module on the BCU to see whether the connections are "H" or "L" to determine whether the connections are correct and secure. • The check returns an "H" is the connection is secure, and returns an "L" if the connection is not secure. • This SC is issued if the check returns an "L".
• Causes: • FFC harness between BCU and IPU broken • FFC harness between BCU and IPU not connected fully • BCU damaged • IPU damaged
• Remedy: • Replace the FFC harness between BCU and IPU. • Reconnect the FFC harness between BCU and IPU. • Replace the BCU board. • Replace the IPU.

• Code: SC665-04
• Description: IO ASIC Does Not Start The IO ASIC start-up signal is checked every 10 milliseconds. The SC is issued when the IO ASIC start-up signal is not detected although 3 seconds elapsed.
• Causes: BCU defective
• Remedy: Replace the BCU board.

• Code: SC669-01 ... SC669-26
• Description: EEPROM Communication Error. Received an error notification during EEPROM communication and does not resume after 3 retries.
• Causes: • Electrical noise. • EEPROM damaged.
• Remedy: • Turn the power off/on. • Replace the EEPROM.

• Code: SC669-36
• Description: EEPROM: Verify Error The machine receives an error notification during EEPROM (BCU) communication and does not resume after 2 retries.
• Causes: Electrical noise
• Remedy: Turn the power off/on.

• Code: SC669-37
• Description: EEPROM: Failure Detection Error The machine receives an error notification during EEPROM (BCU) communication and does not resume after 2 retries.
• Causes: • Electrical noise • EEPROM damaged
• Remedy: • Turn the power off/on. • Replace the EEPROM on the BCU.

• Code: SC670-00
• Description: Engine start up error. Case 1 • /ENGRDY signal was not asserted when the machine was turned on or returned from energy saver mode. • /IPURDY signal was not asserted when the machine was turned on or returned from energy saver mode. • EC response was not received within specified time from power on. • PC response was not received within specified time from power on. • SC response was not received within specified time from power on. • Writing to Rapi driver failed (the other party not found through PCI). Case 2 • Unexpected down status was detected after /ENGRDY assertion.
• Causes: Case 1 • Engine board does not start up. Case 2 • Engine board reset unexpectedly.
• Remedy: Check the connection between the engine board and the controller board. • If it is always reproduced, replace the engine board. If the problem persists, consider replacing the controller board or other boards between them. • If reproducibility is low, multiple causes are to be considered, such as software, engine board, controller board, and PSU.