• Code: SC652-00
• Description: Remote service ID2 mismatching
• Causes: There was an authentication mismatch between ID2 for @Remote, the controller board, and NVRAM. • Used controller board installed • Used NVRAM installed (such action is not allowed.)
• Remedy: • If this occurs during RC Gate installation: Check the validity of the certificate and the NVRAM, check the machine serial number, write the common certificate, and then begin installation again. • If this occurs after RC Gate installation: Clear the RC Gate install status, check the validity of the certificate and the NVRAM, check the machine serial number, write the common certificate, and then begin installation again.

• Code: SC653-00
• Description: Incorrect remote service ID2
• Causes: ID2 stored in the NVRAM has either of the following problems. • Number of characters is not 17. • Includes a character that cannot be printed. • All spaces • NULL
• Remedy: Replace the NVRAM. Clear the RC Gate install ationstatus, write the common certificate, and then begin installation again.

• Code: SC669
• Description: EEPROM communication error
• Causes: An error is notified during EEPROM669 - 1 ID error during EEPROM OPEN 669 - 2 Channel error during EEPROM OPEN 669 - 3 Device error during EEPROM OPEN 669 - 4 Communication interrupted error during EEPROM OPEN 669 - 5 Communication timeout error 669 - 6 Not operating error during EEPROM OPEN 669 - 7 Buffer full during EEPROM OPEN 669 - 8 No error code during EEPROM OPEN 669 - 9 ID error 669 - 10 No error code during EEPROM Close 669 - 11 ID error during EEPROM data write 669 - 12 Channel error during EEPROM data write 669 - 13 Device error during EEPROM data write 669 - 14 Communication interrupted error during EEPROM data write 669 - 15 Communication timeout error 669 - 16 Not operating error during EEPROM data write 669 - 17 Buffer full during EEPROM data write 669 - 18 No error code during EEPROM data write 669 - 19 ID error during EEPROM data read 669 - 20 Channel error EEPROM data read 669 - 21 Device error during EEPROM data read 669 - 22 Communication interrupted error during EEPROM data read 669 - 23 Communication timeout error 669 - 24 Not operating error during EEPROM data read 669 - 25 Buffer full during EEPROM data read 669 - 26 No error code during EEPROM data read • Electromagnetic noise • EEPROM error
• Remedy: • Turn the main power OFF and then ON. • Replace the BICU

• Code: SC669-36
• Description: EEPROM communication error
• Causes: The EEPROM data has been transferred to the SRAM twice in succession, but the two sets of transferred data do not match. 669 - 36 EEPROM SRAM OPEN: Verified error • Electromagnetic noise • EEPROM error
• Remedy: • Turn the main power OFF and then ON.

• Code: SC670-00
• Description: Engine start up error
• Causes: • 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. • The EC response from the engine was not received within the specified time after turning on the power. • The PC response from the engine was not received within the specified time after turning on the power. • The SC response from the engine was not received within the specified time after turning on the power (MFP models only). • Writing to Rapi driver failed (the other party not found through PCI). • Case 2 • Unexpected down status was detected after /ENGRDY assertion. • 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 this problem always occurs, replace the engine board. If the problem persists, consider replacing the controller board or other boards between them. • If this problem occasionally occurs, multiple causes are to be considered, such as the software, engine board, controller board, and PSU.

• Code: SC672-10
• Description: Controller start up error
• Causes: The controller and control panel failed to establish communication when the power was turned on. • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector is loose, broken, or defective • Controller's late response
• 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
• Causes: After the machine was powered on, communication between the controller and the operation panel was not established, or data transmission failed after a normal startup. • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector is loose, broken, or defective • Controller's late response
• 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
• Causes: Communication with controller was interrupted after a normal startup. • Controller stalled • Board installed incorrectly • Controller board defective • Operation panel connector is loose, broken, or defective • Controller's late response
• Remedy: • Turn the main power off/on. • Check the connection of the controller board. • Replace the controller board. • Check the control panel harness.