SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC621-01 | D | Finisher communication error |
SC621-02 | D | Mailbox communication error |
| ||
| ||
Check if the SC occurs by turning the main power OFF then ON. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC622-01 | D | Paper tray 1 communication error for Paper Feed Unit PB3250 |
SC622-11 | D | Paper tray 1 communication error for Paper Feed Unit PB3240 |
SC622-12 | D | Paper tray 1 communication error for Paper Feed Unit PB3240 |
SC622-31 | D | Paper tray 1 communication error for LCIT PB3260 |
| ||
| ||
Check if the SC occurs by turning the main power OFF then ON. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC623-00 | D | Paper tray 2 communication error |
During superposition of 1-tray PFU - 2-tray PFU, 2-tray PFU - side LCIT, and LCIT - side LCIT,
| ||
| ||
Check if the SC occurs by turning the main power OFF then ON. If the SC occurs again, do the following steps. Check if the SC reoccurs by cycling the power after each step.
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC663-01 | D | Reset Detection: Imaging IOB: Software hang-up occurs |
SC663-02 | D | Reset Detection: Imaging IOB: Power ON reset occurs |
SC663-03 | D | Reset Detection: Imaging IOB: Software reset occurs |
SC663-11 | D | Reset Detection: Paper Transport IOB: Software hang-up occurs |
SC663-12 | D | Reset Detection: Paper Transport IOB: Power ON reset occurs |
SC663-13 | D | Reset Detection: Paper Transport IOB: Software reset occurs |
SC is displayed when unexpected reset from Imaging IOB/Paper Transport IOB is detected while standby/operation. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC664-01 | D | VODKA1 (Paper Transport Vodka) access permission error to VODKA SRAM |
SC664-02 | D | VODKA1 (Paper Transport Vodka) write error to VODKA SRAM |
SC664-03 | D | VODKA1 (Paper Transport Vodka) VODKA program launch error |
SC664-11 | D | VODKA2 (Imaging Vodka) access permission error to VODKA SRAM |
SC664-12 | D | VODKA2 (Imaging Vodka) write error to VODKA SRAM |
SC664-13 | D | VODKA2 (Imaging Vodka) VODKA program launch error |
The machine detects the communication error between VODKA and SRAM when starting up, or recovery from energy saver mode. | ||
The following board defects (Parts implementation defect, solder scrap,
| ||
-01 to 03
-11 to 13
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-01 | D | Connection Error (BCU - IPU) |
The machine detects the communication error between BCU and IPU (No FFC connection) when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-02 | D | Connection Error (BCU – Imaging IOB) |
The machine detects the communication error between BCU and Imaging IOB (No connection) when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-03 | D | Connection Error (Paper Transport IOB – Imaging IOB) |
The machine detects the communication error between Imaging IOB and Paper Transport IOB (No connection) when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-04 | D | IOB does not start up |
The IOB does not start up when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-05 | D | Master Device Communication Error |
The machine detects the communication error between CPU and Slave1 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-06 | D | IPU and IOB signal Communication Error |
The machine detects the communication error between CPU and Slave1 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-07 | D | IPU signal Communication Error |
The machine detects the communication error between CPU and Slave device when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-08 | D | IOB signal Communication Error |
The machine detects the communication error between CPU and Slave1 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-11 | D | Vodka1 Communication Error |
The machine detects the communication error between CPU and Vodka1 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-12 | D | Vodka2 Communication Error |
The machine detects the communication error between CPU and Vodka2 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-41 | D | Macaron1 Communication Error |
The machine detects the communication error between CPU and Macaron1 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC665-42 | D | Macaron2 Communication Error |
The machine detects the communication error between CPU and Macaron2 when starting up, or recovery from energy saver mode. | ||
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC667-01 | D | Master Device Mode Setting Error |
The machine detects the CPU mode error when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC667-10 | D | Slave1 Device Mode Setting Error |
The machine detects the Slave1 mode error when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC667-11 | D | Slave2 Device Mode Setting Error |
The machine detects the Slave2 mode error when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC667-40 | D | Macaron1 Mode Setting Error |
The machine detects the Macaron1 mode error when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC667-41 | D | Macaron2 Mode Setting Error |
The machine detects the Macaron2 mode error when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC668-01 | D | Vodka1 Version Setting Error |
The machine detects the version settings error in Vodka1 when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC668-02 | D | Vodka2 Version Setting Error |
The machine detects the version settings error in Vodka2 when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC668-03 | D | Vodka1,2 Version Setting Error |
The machine detects the version settings error in both Vodka 1 and Vodka2 when starting up, or recovery from energy saver mode. | ||
One or more of the following boards may be defective (incorrect or defective components, scraps of solder, etc.):
| ||
|
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC669 | EEPROM Communication Error | |
SC669-01 | D | EEPROM OPEN: ID error |
SC669-02 | D | EEPROM OPEN: Channel error |
SC669-03 | D | EEPROM OPEN: Device error |
SC669-04 | D | EEPROM OPEN: Communication abort error |
SC669-05 | D | EEPROM OPEN: Communication timeout error |
SC669-06 | D | EEPROM OPEN: Operation stopped error |
SC669-07 | D | EEPROM OPEN: Buffer full |
SC669-08 | D | EEPROM OPEN: No error code |
SC669-09 | D | EEPROM CLOSE: ID error |
SC669-10 | D | EEPROM CLOSE: No error code |
SC669-11 | D | EEPROM Data write: ID error |
SC669-12 | D | EEPROM Data write: Channel error |
SC669-13 | D | EEPROM Data write: Device error |
SC669-14 | D | EEPROM Data write: Communication abort error |
SC669-15 | D | EEPROM Data write: Communication timeout error |
SC669-16 | D | EEPROM Data write: Operation stopped error |
SC669-17 | D | EEPROM Data write: Buffer full |
SC669-18 | D | EEPROM Data write: No error code |
SC669-19 | D | EEPROM Data read: ID error |
SC669-20 | D | EEPROM Data read: Channel error |
SC669-21 | D | EEPROM Data read: Device error |
SC669-22 | D | EEPROM Data read: Communication abort error |
SC669-23 | D | EEPROM Data read: Communication timeout error |
SC669-24 | D | EEPROM Data read: Operation stopped error |
SC669-25 | D | EEPROM Data read: Buffer full |
SC669-26 | D | EEPROM Data read: No error code |
SC669-36 | D | Verification error |
SC669-37 | D | Error Detection |
The TD sensor cannot be recovered after retrying N*1 times for EEPROM communication error. (*1 SC669-01 to 26: 3, SC669-36: 2, SC669-37: 1) | ||
| ||
|
No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
681-** | D | Toner bottle: ID Chip Communication error |
When error notification was received during communication with the tag and operation is not resumed after N*1 retries. *1 See the detailed table below. | ||
| ||
Turn the main power off, and then do the following.
|
SC681 Details
No. | Detail | Causes | Retry |
---|---|---|---|
01 - 04 | Invalid device ID | Noise, Incorrect connection, Malfunction | 3 |
06 - 09 | Channel error | Noise, Incorrect connection, Malfunction | 3 |
11 - 14 | Device Error | Noise, Incorrect connection | 3 |
16 - 19 | Communication error (interrupted) | Noise, Incorrect connection | 3 |
21 - 24 | Communication timeout | Noise, Incorrect connection, Malfunction | 3 |
26 - 29 | Device stops (logically) | Noise, Incorrect connection, Malfunction | 3 |
31 - 34 | Full of buffer (request) | Noise, Incorrect connection, Malfunction | 3 |
36 - 39 | Verification error | Noise, Incorrect connection | 2 |
- If the last digit of the SC’s branch number (-**) is:
1 or 6, then do the above steps for K
2 or 7, then do the above steps for M
3 or 8, then do the above steps for C
4 or 9, then do the above steps for Y
No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC682-** | D | TD sensor communication error |
TD sensor cannot be recovered after retrying N*1 times for an ID chip communication error. *1 See the detailed table below. | ||
| ||
Turn the main power off, and then do the following.
|
SC682 Details
No. | Description | Cause | Retry |
---|---|---|---|
01 - 04 | Invalid device ID | Noise, Incorrect connection, Malfunction | 3 |
06 - 09 | Channel error | Noise, Incorrect connection, Malfunction | 3 |
11 - 14 | Device Error | Noise, Incorrect connection | 3 |
16 - 19 | Communication error (interrupted) | Noise, Incorrect connection | 3 |
21 - 24 | Communication timeout | Noise, Incorrect connection, Malfunction | 3 |
26 - 29 | Device stops (logically) | Noise, Incorrect connection, Malfunction | 3 |
31 - 34 | Full of buffer (request) | Noise, Incorrect connection, Malfunction | 3 |
36 - 39 | Verification error | Noise, Incorrect connection | 2 |
SC No. | Type | Error Name/Error Condition/Major Cause/Solution |
---|---|---|
SC687-00 | D | PER Not Received Error |
Unable to receive the PER command from the controller. | ||
Communication error | ||
Replace the BCU. |