SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC620-01

D

ADF Communication Error

SC620-02

D

ADF Communication Error

  

Communication error between the main machine and ADF connected with ASAP.

SC620-01: A BREAK was detected after a successful connection.

SC620-02: Communication timeout after a successful connection.

Details:

  • SC is issued when an error is detected after ADF connection was recognized at power-on.
  • There will be no response either, if the ADF was not connected at power-on. In this case, however, SC is not issued and functions that do not use the ADF (copying from the exposure glass) are available.
  • SC620-02: SC is issued when a non-compliant ADF is connected (ADF model code is different from the specification).

  • ADF connection fault

  • ADF defective

  • BICU defective

  • Electrical noise on the line

  • SC620-02: Connection of a non-compliant ADF (ADF model code is different from the specification.)

  • Check ADF cable connection.

  • Replace the ADF.

  • Replace the BICU.

  • SC620-02: Replace the ADF to the correct model.
SC No.LevelError Name/Error Condition/Major Cause/Solution
SC620-03DADF Communication Error
  The CIS initialization completion command is not received after waiting for the prescribed time.

  • ADF connection fault

  • ADF defective

  • BICU defective

  • Electrical noise on the line

  • Check ADF cable connection.

  • Replace the ADF.

  • Replace the BICU.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC621-00

D

Finisher/mail box communication error

Detected an error when connecting the communication line.

Received a communication error notification from the URAT.

  • Finisher control board defective.

  • BICU or IOB defective

  • Connection fault between finisher and main machine.

  • Reconnect the Finisher/mail box interface cable.

  • Replace the BICU or replace the finisher/mail box

  • Turn the main power off/on.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC622-00

D

Paper bank communication error.

Communication error between main machine and paper bank/LCIT.

  • Paper bank control board defective.

  • BICU or IOB defective

  • Paper bank-main machine connection fault.

  • Reconnect the paper bank connection cable. /Replace the BICU./Replace the paper bank.

  • Turn the main power off/on.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC625-00

D

TDCU communication error.

ASAP communication protocol error

  • A BREAK signal was detected at power-on.

  • Non-response (100 ms) was detected 3 times consecutively during normal operation.

  • NAK was received 3 times before ACK was received during normal operation.

  • A BREAK signal was detected during normal operation.

  • IOB defective

  • Replace the IOB.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC626-01

D

DUB communication error at power-on

SC626-02

D

DUB communication error during normal operation

SC626-03

D

DUB BREAK detection during normal operation

  

ASAP communication protocol error

  • A BREAK signal was detected at power-on.

  • Non-response (100 ms) was detected 3 times consecutively during normal operation.

  • NAK was received 3 times before ACK was received during normal operation.

  • A BREAK signal was detected during normal operation.

  • DUB defective

  • PFB defective

  • Harness between DUB and PFB broken

  • Connecter between DUB and PFB disconnected

  • Unintended electrical noise

  • Replace the DUB.

  • Replace the PFB.

  • Replace the harness between DUB and PFB.

  • Replace the connector between DUB and PFB.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC626-04

D

TSB communication error at power-on

SC626-05

D

TSB communication error during normal operation

SC626-06

D

TSB BREAK detection during normal operation

  

ASAP communication protocol error

  • A BREAK signal was detected at power-on.

  • Non-response (100 ms) was detected 3 times consecutively during normal operation.

  • NAK was received 3 times before ACK was received during normal operation.

  • A BREAK signal was detected during normal operation.

  • TSB defective

  • IOB defective

  • Harness between TSB and IOB broken

  • Connecter between TSB and IOB disconnected

  • Unintended electrical noise

  • Replace the TSB.

  • Replace the IOB.

  • Replace the harness between TSB and IOB.

  • Replace the connector between TSB and IOB.

SC No.LevelError Name/Error Condition/Major Cause/Solution
SC645-01CTonner Supply: ID Chip Communication Error (K)
SC645-02CTonner Supply: ID Chip Communication Error (M)
SC645-03CTonner Supply: ID Chip Communication Error (C)
SC645-04CTonner Supply: ID Chip Communication Error (Y)






Errors defined in I2C communication.

Details:

  • SC is issued when the I2C communication cannot be done between the BICU and ID chip.
  • SC is issued when opening the bus, closing the bus, reading the bus, and writing the bus.
  • Toner supply unit set error
  • ID chip defective
  • Harness broken
  • BICU damaged
  • IOB damaged
  • TSB damaged
  • TCB damaged
  • Unintended noise

  • Set the toner supply unit again.

  • Replace the ID chip.

  • Fix the harness.

  • Replace the BICU.

  • Replace the IOB.

  • Replace the TSB.

  • Replace the ID chip connector board.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC664-01

D

VODKA SRAM program expansion error

SC664-02

D

SC664-03

D

  

VODKA1

SC664-01: VODKA SRAM access permission error (Write permission denied)

SC664-02: VODKA SRAM write error (write result abnormal)

SC664-03: VODKA program startup error

  • Electric noises and hardware defect

  • IOB replacement, harness check

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC664-11

D

VODKA SRAM program expansion error

SC664-12

D

SC664-13

D

  

VODKA2

SC664-11: VODKA SRAM access permission error (Write permission denied)

SC664-12: VODKA SRAM write error (write result abnormal)

SC664-13: VODKA program startup error

  • Electric noises and hardware defect

  • IOB replacement, harness check

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC664-21

D

VODKA SRAM program expansion error

SC664-22

D

SC664-23

D

  

VODKA3

SC664-21: VODKA SRAM access permission error (Write permission denied)

SC664-22: VODKA SRAM write error (write result abnormal)

SC664-23: VODKA program startup error

  • Electric noises and hardware defect

  • IOB replacement, harness check

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC664-31

D

VODKA SRAM program expansion error

SC664-32

D

SC664-33

D

  

VODKA4

SC664-31: VODKA SRAM access permission error (Write permission denied)

SC664-32: VODKA SRAM write error (write result abnormal)

SC664-33: VODKA program startup error

  • Electric noises and hardware defect

  • IOB replacement, harness check

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC664-41

D

VODKA SRAM program expansion error

SC664-42

D

SC664-43

D

  

VODKA5

SC664-41: VODKA SRAM access permission error (Write permission denied)

SC664-42: VODKA SRAM write error (write result abnormal)

SC664-33: VODKA program startup error

  • Electric noises and hardware defect

  • IOB replacement, harness check

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC665-02

D

FFC set detection (Error between BICU and IOB)

The HORUS port on the BICU is used for FFC connection detection to detect FFC (harness) disconnection and loose connection between BICU and IOB. By checking the voltage level of the AD terminal, the connection status can be checked.

Details:

  • When the harness between BICU and IOB becomes disconnected, the number of parallelly connected resistors changes and therefore the voltage input to the AD terminal changes.

  • FFC harness between BICU and IOB broken

  • FFC harness between BICU and IOB not connected fully

  • BICU damaged

  • IOB damaged

  • Replace the FFC harness between BICU and IOB.

  • Reconnect the FFC harness between BICU and IOB.

  • Replace the BICU.

  • Replace the IOB.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC665-03

D

FFC set detection (Error between IOB and PFB)

The HORUS port on the BICU 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.

  • FFC harness between IOB and PFB broken

  • FFC harness between IOB and PFB not connected fully

  • BICU damaged

  • IOB damaged

  • PFB damaged

  • Replace the FFC harness between IOB and PFB.

  • Reconnect the FFC harness between IOB and PFB.

  • Replace the BICU.

  • Replace the IOB.

  • Replace the PFB.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC665-04

D

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.

  • IOB damaged

  • PFB damaged

  • BICU defective

  • Harness between BICU and IOB: Ground fault

  • Harness between IOB and PFB: Ground fault

  • PSU5V not output

  • Replace the harness between IOB and PFB.

  • Replace the harness between BICU and IOB.

  • Replace the IOB.

  • Replace the PFB.

  • Replace the BICU board.

  • Replace the PSU.

SC No.

Level

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-27

D

EEPROM Device detection: ID error

SC669-28

D

EEPROM Device detection: Channel error

SC669-29

D

EEPROM Device detection: Device error

SC669-30

D

EEPROM Device detection: Communication abort error

SC669-31

D

EEPROM Device detection: Communication timeout error

SC669-32

D

EEPROM Device detection: Operation stopped error

SC669-33

D

EEPROM Device detection: Buffer full

SC669-34

D

EEPROM Device detection: No error code

SC669-36DSRAM expansion verify error
SC669-37DMalfunction detection error
  

Received an error notification during EEPROM communication and does not resume after 3 retries.

  • Electrical noise

  • EEPROM not connected fully

  • EEPROM not installed

  • EEPROM damaged

  • BICU damaged

  • Cycle the machine off/on.

  • Reconnect the EEPROM.

  • Replace the EEPROM.

  • Replace the BICU.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC681

 

Toner Cartridge: ID Chip Communication Error

SC681-01

D

Toner Supply: ID Chip Communication Error (K_Invalid Device ID)

SC681-02

D

Toner Supply: ID Chip Communication Error (M_Invalid Device ID)

SC681-03

D

Toner Supply: ID Chip Communication Error (C_Invalid Device ID)

SC681-04

D

Toner Supply: ID Chip Communication Error (Y_Invalid Device ID)

SC681-05

D

Toner Supply: ID Chip Communication Error (K_Channel error (e.g. bus disconnection))

SC681-06

D

Toner Supply: ID Chip Communication Error (M_Channel error (e.g. bus disconnection))

SC681-07

D

Toner Supply: ID Chip Communication Error (C_Channel error (e.g. bus disconnection))

SC681-08

D

Toner Supply: ID Chip Communication Error (Y_Channel error (e.g. bus disconnection))

SC681-09

D

Toner Supply: ID Chip Communication Error (K_Device Error (No ID chip))

SC681-11

D

Toner Supply: ID Chip Communication Error (M_Device Error (No ID chip))

SC681-12

D

Toner Supply: ID Chip Communication Error (C_Device Error (No ID chip))

SC681-13

D

Toner Supply: ID Chip Communication Error (Y_Device Error (No ID chip))

SC681-14

D

Toner Supply: ID Chip Communication Error (K_Communication aborted (error during communication))

SC681-16

D

Toner Supply: ID Chip Communication Error (M_Communication aborted (error during communication))

SC681-17

D

Toner Supply: ID Chip Communication Error (C_Communication aborted (error during communication))

SC681-18

D

Toner Supply: ID Chip Communication Error (Y_Communication aborted (error during communication))

SC681-19

D

Toner Supply: ID Chip Communication Error (K_Communication timeout)

SC681-21

D

Toner Supply: ID Chip Communication Error (M_Communication timeout)

SC681-22

D

Toner Supply: ID Chip Communication Error (C_Communication timeout)

SC681-23

D

Toner Supply: ID Chip Communication Error (Y_Communication timeout)

SC681-24

D

Toner Supply: ID Chip Communication Error (K_Device stopped (logically stopped))

SC681-26

D

Toner Supply: ID Chip Communication Error (M_Device stopped (logically stopped))

SC681-27

D

Toner Supply: ID Chip Communication Error (C_Device stopped (logically stopped))

SC681-28

D

Toner Supply: ID Chip Communication Error (Y_Device stopped (logically stopped))

SC681-29

D

Toner Supply: ID Chip Communication Error (K_Requested buffer full)

SC681-31

D

Toner Supply: ID Chip Communication Error (M_Requested buffer full)

SC681-32

D

Toner Supply: ID Chip Communication Error (C_Requested buffer full)

SC681-33

D

Toner Supply: ID Chip Communication Error (Y_Requested buffer full)

SC681-34

D

Toner Supply: ID Chip Communication Error (K_Verify error)

SC681-35

D

Toner Supply: ID Chip Communication Error (M_Verify error)

SC681-36

D

Toner Supply: ID Chip Communication Error (C_Verify error)

SC681-37

D

Toner Supply: ID Chip Communication Error (Y_Verify error)

SC681-38

D

Toner Supply: ID Chip Communication Error (K_Invalid Device ID)

SC681-39

D

Toner Supply: ID Chip Communication Error (M_Invalid Device ID)

  

Errors defined in I2C communication

  • When abnormality occurs at cable connection

  • When error notification was received during communication with the tag and operation is not resumed after 3 retries.

There was an error during (wired) communication with the ID chip on the toner bottle.

SC681-01 to 04: Device ID data corrupted.

SC681-06 to 09: Contact fault (e.g. Bus disconnection)

SC681-11 to 14: No ID chip

SC681-16 to 19/21 to 24/26 to 39: Noise

SC681-31 to 34/36 to 39: Software problem

  • Toner supply unit set error

  • ID chip defective

  • Harness broken

  • BICU damaged

  • IOB damaged

  • TSB damaged

  • TCB damaged

  • Unintended noise

  • Cycle the machine off/on.

  • Set the toner supply unit again.

  • Replace the ID chip.

  • Fix the harness.

  • Replace the BICU.

  • Replace the IOB.

  • Replace the TSB.

  • Replace the TCB.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC682

 

PCU: ID Chip Communication Error

SC682-01

D

PCU: ID Chip Communication Error(K_Invalid Device ID)

SC682-02

D

PCU: ID Chip Communication Error(M_Invalid Device ID)

SC682-03

D

PCU: ID Chip Communication Error(C_Invalid Device ID)

SC682-04

D

PCU: ID Chip Communication Error(Y_Invalid Device ID)

SC682-05

D

PCU: ID Chip Communication Error(K_Channel error (e.g. bus disconnection))

SC682-06

D

PCU: ID Chip Communication Error(M_Channel error (e.g. bus disconnection))

SC682-07

D

PCU: ID Chip Communication Error(C_Channel error (e.g. bus disconnection))

SC682-08

D

PCU: ID Chip Communication Error(Y_Channel error (e.g. bus disconnection))

SC682-09

D

PCU: ID Chip Communication Error(K_Device Error (No ID chip))

SC682-11

D

PCU: ID Chip Communication Error(M_Device Error (No ID chip))

SC682-12

D

PCU: ID Chip Communication Error(C_Device Error (No ID chip))

SC682-13

D

PCU: ID Chip Communication Error(Y_Device Error (No ID chip))

SC682-14

D

PCU: ID Chip Communication Error(K_Communication aborted (error during communication))

SC682-16

D

PCU: ID Chip Communication Error(M_Communication aborted (error during communication))

SC682-17

D

PCU: ID Chip Communication Error(C_Communication aborted (error during communication))

SC682-18

D

PCU: ID Chip Communication Error(Y_Communication aborted (error during communication))

SC682-19

D

PCU: ID Chip Communication Error(K_Communication timeout)

SC682-21

D

PCU: ID Chip Communication Error(M_Communication timeout)

SC682-22

D

PCU: ID Chip Communication Error(C_Communication timeout)

SC682-23

D

PCU: ID Chip Communication Error(Y_Communication timeout)

SC682-24

D

PCU: ID Chip Communication Error(K_Device stopped (logically stopped))

SC682-26

D

PCU: ID Chip Communication Error(M_Device stopped (logically stopped))

SC682-27

D

PCU: ID Chip Communication Error(C_Device stopped (logically stopped))

SC682-28

D

PCU: ID Chip Communication Error(Y_Device stopped (logically stopped))

SC682-29

D

PCU: ID Chip Communication Error(K_Requested buffer full)

SC682-31

D

PCU: ID Chip Communication Error(M_Requested buffer full)

SC682-32

D

PCU: ID Chip Communication Error(C_Requested buffer full)

SC682-33

D

PCU: ID Chip Communication Error(Y_Requested buffer full)

SC682-34

D

PCU: ID Chip Communication Error(K_No error code)

SC682-35

D

PCU: ID Chip Communication Error(M_No error code)

SC682-36

D

PCU: ID Chip Communication Error(C_No error code)

SC682-37

D

PCU: ID Chip Communication Error(Y_No error code)

SC682-38

D

PCU: ID Chip Communication Error(K_Invalid Device ID)

SC682-39

D

PCU: ID Chip Communication Error(M_Invalid Device ID)

  

Errors defined in I2C communication

  • When abnormality occurs at cable connection

  • When error notification was received during communication with the tag and operation is not resumed after 3 retries.

There was an error during (wired) communication with the ID chip on the toner bottle.

  • PCU set error

  • TD sensor defective

  • Harness broken

  • BICU damaged

  • IOB damaged

  • Unintended noise

  • Set the PCU again.

  • Replace the TD sensor.

  • Fix the harness.

  • Replace the BICU.

  • Replace the IOB.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC687-00

D

PER Not Received Error

  • Unable to receive the PER command of the I/F commands from the controller.
  • Unable to prepare the image data with the controller.

  • Communication error

  • Inside of the controller defective

  • Cycle the machine off/on.

SC No.

Level

Error Name/Error Condition/Major Cause/Solution

SC689-00

D

IH Inverter Communication Error

IH inverter not responding to request

IH inverter communication error (ASAP IV compliant)

IH inverter response information unavailable

  • Harness broken

  • IH inverter defective

  • IOB defective

  • Remove the cause of the SC and then turn off/on the power or main power.

  • Replace the harness/IH inverter/IOB as required.