SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC622-00
| D
| 1st paper bank communication error |
Detected an error when connecting the communication line. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC623-00 | D | 2nd paper bank communication error |
Detected an error when connecting the communication line. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC624-00 | D | 3rd paper bank communication error |
Detected an error when connecting the communication line. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC641-00 | D | Engine to controller communication error (No response) |
The controller sent a data frame by RAPI protocol, but there was no response after trying 3 times, once every 100ms. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC641-01 | D
| Engine serial communication error (Time-out) |
No response over the specified time. | ||
SC641-02 | D | Engine serial communication error (Retry-over) |
When commands are sent in the normal mode, communication fails over the upper limit numbers (3 times) of command byte retry. | ||
SC641-03 | D | Engine serial communication error (Download Error) |
In the download command mode or download data mode, a communication error is returned from the engine. | ||
SC641-04 | D | Engine serial communication error (UART Error) |
UART receive errors (Break condition, Framing, Parity or Overrun error) are detected. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC645-01
| C | ID tag connection error (Toner cartridge) |
An error is notified during EEPROM communication and the machine does not recover after two retries. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
| ||
SC645-02 | C | ID tag connection error (PCDU) |
An error is notified during EEPROM communication and the machine does not recover after two retries. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC667-01
| D
| Master device mode setting error |
When the machine starts or returns from the energy saver mode, a CPU mode setting error is detected. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC669-01 | D | EEPROM communication error: ID error during EEPROM OPEN |
SC669-02 | D | EEPROM communication error: Channel error during EEPROM OPEN |
SC669-03 | D | EEPROM communication error: Device error during EEPROM OPEN |
SC669-04 | D | EEPROM communication error: Communication interrupted error during EEPROM OPEN |
SC669-05 | D | EEPROM communication error: Communication timeout error |
SC669-06 | D | EEPROM communication error: Not operating error during EEPROM OPEN |
SC669-07 | D | EEPROM communication error: Buffer full during EEPROM OPEN |
SC669-08 | D | EEPROM communication error: No error code during EEPROM OPEN |
SC669-09 | D | EEPROM communication error: ID error |
SC669-10 | D | EEPROM communication error: No error code during EEPROM Close |
SC669-11 | D | EEPROM communication error: ID error during EEPROM data write |
SC669-12 | D | EEPROM communication error: Channel error during EEPROM data write |
SC669-13 | D | EEPROM communication error: Device error during EEPROM data write |
SC669-14 | D | EEPROM communication error: Communication interrupted error during EEPROM data write |
SC669-15 | D | EEPROM communication error: Communication timeout error |
SC669-16 | D | EEPROM communication error: Not operating error during EEPROM data write |
SC669-17 | D | EEPROM communication error: Buffer full during EEPROM data write |
SC669-18 | D | EEPROM communication error: No error code during EEPROM data write |
SC669-19 | D | EEPROM communication error: ID error during EEPROM data read |
SC669-20 | D | EEPROM communication error: Channel error EEPROM data read |
SC669-21 | D | EEPROM communication error: Device error during EEPROM data read |
SC669-22 | D | EEPROM communication error: Communication interrupted error during EEPROM data read |
SC669-23 | D | EEPROM communication error: Communication timeout error |
SC669-24 | D | EEPROM communication error: Not operating error during EEPROM data read |
SC669-25 | D | EEPROM communication error: Buffer full during EEPROM data read |
SC669-26 | D | EEPROM communication error: No error code during EEPROM data read |
SC669-36 | D | EEPROM communication error: Verification error |
SC669-37 | D | EEPROM communication error: Error Detection |
An error is notified during EEPROM communication and the machine does not recover after three retries. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC670-00
| D
| Engine startup error |
Engine board does not start up. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC670-01
| D
| ASIC device mode setting error |
When the machine starts or returns from the energy saver mode, an ASIC mode setting error is detected. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC672 |
| Controller startup error |
SC672-00 | D | After the machine was powered on, communication between the controller and the operation panel was not established, or communication with the controller was interrupted after a normal startup. |
SC672-10 | D | After the machine was powered on, communication between the controller and the operation panel was not established. |
SC672-11 | D | After the machine was powered on, communication between the controller and the operation panel was not established, or communication with the controller was interrupted after a normal startup. |
SC672-12 | D | Communication with the controller was interrupted after a normal startup. |
SC672-13 | D | The operation panel detected that the controller is down due to other reason that shown in SC672-00 to -12. |
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC672-20
| D
| Controller startup error |
After the machine was powered on, communication between the controller and the operation panel was not established, or communication with the controller was interrupted after a normal startup. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC672-21
| D
| Controller startup error |
After the machine was powered on, communication between the controller and the operation panel was not established, or communication with the controller was interrupted after a normal startup. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC672-99
| D
| Controller startup error |
The operation panel software ended abnormally. | ||
| ||
Power cycle the machine. |
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC673-01 | D | Operation panel Flair communication error (Smart Operation Panel) |
System application (MonitorService) error occurred | ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC673-10 | D | Operation panel Flair communication error (Smart Operation Panel) |
The Smart Operation Panel is communicating with the main machine (this is called “flair communication”), and there was no response from the main machine. | ||
This SC is detected when the controller cannot respond to the notification from the monitoring service module (operation panel). | ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC681-01 | D | Device ID is not identified (toner cartridge): Device ID error (Incorrect ID) |
SC681-06 | D | Device ID is not identified (toner cartridge): Channel error |
SC681-11 | D | Device ID is not identified (toner cartridge): Device ID error (No ID chip) |
SC681-16 | D | Device ID is not identified (toner cartridge): Communication error |
SC681-21 | D | Device ID is not identified (toner cartridge): Communication timeout |
SC681-26 | D | Device ID is not identified (toner cartridge): The device has stopped its operation |
SC681-27 | D | Device ID is not identified (toner cartridge): The device has stopped its operation |
SC681-28 | D | Device ID is not identified (toner cartridge): The device has stopped its operation |
SC681-29 | D | Device ID is not identified (toner cartridge): The device has stopped its operation |
SC681-31 | D | Device ID is not identified (toner cartridge): The requested buffer is full |
SC681-36 | D | Device ID is not identified (toner cartridge): SRAM OPEN: Verification error |
| An error is notified during the ID identification after three retries. | |
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC682-01 | D | Device ID is not identified (PCDU): Device ID error (Incorrect ID) |
SC682-06 | D | Device ID is not identified (PCDU): Channel error |
SC682-11 | D | Device ID is not identified (PCDU): Device ID error (No ID chip) |
SC682-16 | D | Device ID is not identified (PCDU): Communication error |
SC682-21 | D | Device ID is not identified (PCDU): Communication timeout |
SC682-26 | D | Device ID is not identified (PCDU): The device has stopped its operation |
SC682-27 | D | Device ID is not identified (PCDU): The device has stopped its operation |
SC682-28 | D | Device ID is not identified (PCDU): The device has stopped its operation |
SC682-29 | D | Device ID is not identified (PCDU): The device has stopped its operation |
SC682-31 | D | Device ID is not identified (PCDU): The requested buffer is full |
SC682-36 | D | Device ID is not identified (PCDU): SRAM OPEN: Verification error |
| An error is notified during the ID identification after three retries. | |
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC687-00 | D | PER receipt failure |
Even though 120 seconds have elapsed after RAPI-PES (request for image transfer) is issued, a RAPI-PER receipt is not received from the controller board. | ||
| ||
Power cycle the machine to see if the error reoccurs. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power off/on after each step.
|