• Code: SC665-01
• Description: FFC set detection (Error between IPU and BCU) The HORUS port on the BCU is used for FFC connection detection to detect FFC (harness) disconnection and loose connection between BCU and IPU. By checking the "H" or "L" status of this port, the connection status can be checked. • Normal condition (Connector connected): "H" at the HORUS port on the BCU. • Abnormal condition (Connector not connected): "L" at the HORUS port on the BCU. Details: • When a connector is disconnected, the voltage level becomes "L" level (0V level) because there is a pull-down resistor in the BCU.
• 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-02
• Description: FFC set detection (Error between BCU and IOB) The HORUS port on the BCU is used for FFC connection detection to detect FFC (harness) disconnection and loose connection between BCU and IOB. By checking the voltage level of the AD terminal, the connection status can be checked. Details: • When the harness between BCU and IOB becomes disconnected, the number of parallelly connected resistors changes and therefore the voltage input to the AD terminal changes.
• Causes: • FFC harness between BCU and IOB broken • FFC harness between BCU and IOB not connected fully • BCU damaged • IOB damaged
• Remedy: • Replace the FFC harness between BCU and IOB. • Reconnect the FFC harness between BCU and IOB. • Replace the BCU board. • Replace the IOB.

• Code: SC665-03
• Description: FFC set detection (Error between IOB and PFB) The HORUS port on the BCU is used for FFC connection detection to detect FFC (harness) disconnection and loose connection between IOB and PFB. By checking the voltage level of the AD terminal, the connection status can be checked. Details: • When the harness between IOB and PFB becomes disconnected, the number of parallelly connected resistors changes and therefore the voltage input to the AD terminal changes.
• Causes: • FFC harness between IOB and PFB broken • FFC harness between IOB and PFB not connected fully • BCU damaged • IOB damaged • PFB damaged
• Remedy: • Replace the FFC harness between IOB and PFB. • Reconnect the FFC harness between IOB and PFB. • Replace the BCU board. • Replace the IOB. • Replace the PFB.

• Code: SC665-04
• Description: IOB does not start The IOB_WAKE signal of the IOB and the PFB is not "WAKE". (Occurs when either 2 Vodkas in the IOB or 3 Vodkas in the PFB are in the reset status. Details: • Detected when IOB_WAKE signal from the 2 Vodkas on the IOB (PIB function, FSB function) and 3 Vodkas on the FSB stay in the WAKE status. • IOB_WAKE signal is output from 5 Vodkas as explained above and if at least one of them is "WAKE", IOB_WAKE is not canceled.
• Causes: • IOB damaged • PFB damaged • BCU defective • Harness between BCU and IOB: Ground fault • Harness between IOB and PFB: Ground fault • PSU5V not output
• Remedy: • Replace the harness between IOB and PFB. • Replace the harness between BCU and IOB. • Replace the IOB. • Replace the PFB. • Replace the BCU board. • Replace the PSU.

• Code: SC669
• Description: EEPROM Communication Error. Received a error notification during EEPROM communication and does not resume after 3 retries.
• Causes: • Electrical noise • EEPROM not connected fully • EEPROM not installed • EEPROM damaged • BCU damaged
• Remedy: • Cycle the machine 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.