• Code: SC669-36
• Description: EEPROM SRAM OPEN: Verified error
• Causes: Received a error notification during EEPROM communication and doesnot resume after 3 retries. • Electrical noise • EEPROM not connected fully • EEPROM not installed • EEPROM damaged • BCU damaged
• Remedy: • Turn the power off/on • Reconnect the EEPROM • Replace the EEPROM • Replace 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.

• Code: SC672-10
• Description: Controller start up error After the machine was powered on, communication between the controller and the operation panel was not established.
• Causes: • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector loose, broken, or defective • Controller late
• Remedy: • Turn the main power off/on. • Check the connection of the controller board. • Replace the controller board. • Check the control panel harness.

• Code: SC672-11
• Description: Controller start up error After the machine was powered on, communication between the controller and the operation panel was not established, or communication with controller was interrupted after a normal startup.
• Causes: • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector loose, broken, or defective • Controller late
• Remedy: • Turn the main power off/on. • Check the connection of the controller board. • Replace the controller board. • Check the control panel harness.

• Code: SC672-12
• Description: Controller start up error Communication with controller was interrupted after a normal startup.
• Causes: • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector loose, broken, or defective • Controller late
• Remedy: • Turn the main power off/on. • Check the connection of the controller board. • Replace the controller board. • Check the control panel harness.

• Code: SC672-13
• Description: Controller start up error The operation panel detected that the controller is down.
• Causes: • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector loose, broken, or defective • Controller late
• Remedy: • Turn the main power off/on. • Check the connection of the controller board. • Replace the controller board. • Check the control panel harness.

• Code: SC672-99
• Description: Controller start up error The operation panel software ended abnormally.
• Causes: • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector loose, broken, or defective • Controller late
• Remedy: • Turn the main power off/on. • Check the connection of the controller board. • Replace the controller board. • Check the control panel harness.

• Code: SC687
• Description: PER Not Received Error Unable to receive the PER command from the controller.
• Causes: • Electrical noise • Controller board defective
• Remedy: • Turn the power off/on • Replace the controller Board