No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC622-00

D

1st paper tray communication error

While the BiCU communicates with an optional unit, an SC code is displayed if one of following conditions occurs.

  • The BiCU receives the break signal which is generated by the peripherals only just after the main power is turned on.
  • When the BiCU does not receive an OK signal from a PFU 100ms after sending a command to it.
  • Defective the PFU controller board
  • Defective the BiCU
  • Loose or disconnected connector
  • Replace the PFU controller board (1st paper tray).
  • Replace the BiCU. 
  • Set the 1st paper tray again.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

 

SC623-00

D

2nd paper tray communication error

This SC is not issued for this machine.

When a communication error signal between the 1st paper tray and 2nd paper tray is received.

  • Loose or disconnected connector
  • Defective PFU controller board
  • Replace the PFU controller board (2nd paper tray).
  • Replace the PFU controller board (1st paper tray).
  • Set the 1st and 2nd paper tray again.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC636-02

D

IC card error (Version error)

The version of the expanded authentication module is not correct.

Incorrect module version

Install the correct file of the expanded authentication module.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC637-01

D

Tracking Information notification error (Tracking application error)

Tracking information was lost.

  • Tracking SDK application error
  • Internal notification error

Cycle the main power off and on.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC637-02

D

Tracking Information notification error (Management server error)

Tracking information was lost.

Communication with tracking management server failed.

  • Network error
  • tracking management server error
  • Tracking SDK application error

Cycle the main power off and on.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC641-00

D

Communication error between engine and controller

Although frame is sent from controller, engine does not reply to it.

  • Controller Board soft error
  • BiCU soft error
  • BiCU and controller board connection error
  • Cycle the main power off and on.
  • Check the connection between the BiCU and the controller board.

SC645-01-04

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC650-01

C

Remote service modem communication error (Dialup authentication failure)

  • An error related to communication (dialup connection, modem board etc.) using the RC Gate Type M was detected or an error that prevents RC Gate operation was detected at power on.
  • Displayed only when an error is detected while RC Gate is operating.
  • SC is not issued if an error occurs during RC Gate installation (because it can be referenced using SP).
  • SP settings invalid
  • Modem connector disconnected
  • Modem board disconnected
  • Wireless LAN card disconnected

Check the following SPs.

  • SP5-816-156 (Remote Service: Dial Up User Name)
  • SP5-816-157 (Remote Service: Dial Up Password)

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC650-04

C

Remote Service Modem Communication Error (dialup failing because of incorrect modem configuration)

  • An error related to communication (dialup connection, modem board etc.) using the RC Gate Type M was detected or an error that prevents RC Gate operation was detected at power on.
  • Displayed only when an error is detected while RC Gate is operating.
  • SC is not issued if an error occurs during RC Gate installation (because it can be referenced using SP).
  • SP settings invalid
  • Modem connector disconnected
  • Modem board disconnected
  • Wireless LAN card disconnected

Software bug.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC650-05

C

Remote Service Modem Communication Error (insufficient current or connection fault)

  • An error related to communication (dialup connection, modem board etc.) using the RC Gate Type M was detected or an error that prevents RC Gate operation was detected at power on.
  • Displayed only when an error is detected while RC Gate is operating.
  • SC is not issued if an error occurs during RC Gate installation (because it can be referenced using SP).
  • SP settings invalid
  • Modem connector disconnected
  • Modem board disconnected
  • Wireless LAN card disconnected

The line is not supported and nothing can be done.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC650-13

C

Remote Service Modem Communication Error (RC Gate Type M was installed but modem is not present (detected during operation))

  • An error related to communication (dialup connection, modem board etc.) using the RC Gate Type M was detected or an error that prevents RC Gate operation was detected at power on.
  • Displayed only when an error is detected while RC Gate is operating.
  • SC is not issued if an error occurs during RC Gate installation (because this error can be referred by using SP).
  • SP settings invalid
  • Modem connector disconnected
  • Modem board disconnected
  • Wireless LAN card disconnected
  • If a modem board is not installed, install it.
  • Check again if the modem driver configurations (SP5-816-160, SP5-816-165 to 171, and SP5-816-165 to 171) are correct.
  • If the problem is not solved, replace the modem.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC650-14

C

Remote Service Modem Communication Error (RC Gate Type N was installed but modem is present or wired/wireless LAN is not working correctly)

  • An error related to communication (dialup connection, modem board etc.) using the RC Gate was detected or an error that prevents RC Gate operation was detected at power on.
  • Displayed only when an error is detected while RC Gate is operating.
  • SC is not issued if an error occurs during RC Gate installation (because this error can be referred by using SP).
  • SP settings invalid
  • Modem connector disconnected
  • Modem board disconnected
  • Wireless LAN card disconnected
  • If a modem board is attached, remove it.
  • Check if wired/wireless LAN works.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

Sc651-01

C

Illegal Remote Service Dial-up (Chat program parameter error)

An unexpected error occurred when RC Gate Type M dialed up the NRS Center.

Software bug

Logging only.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC651-02

C

Illegal Remote Service Dial-up (Chat program execution error)

An unexpected error occurred when RC Gate dialed up the NRS Center.

Software bug

Logging only.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC652-00

A

Remote service ID2 mismatching

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.)
  • 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.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC653-00

A

Incorrect remote service ID2

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

Replace the NVRAM.

Clear the RC Gate install status, write the common certificate, and then begin installation again.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC664-01

D

ASIC – SRAM Communication error

  • When the machine starts or returns from the energy saver mode, a connection error signal between ASIC and SRAM device is detected.
  • Defective BiCU
  • Cycle the main power off/on.
  • Replace the BiCU.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC665-05

D

BiCU control signal connection error

SC665-07

D

BiCU control signal connection error

SC665-08DBiCU control signal connection error
  

When the machine starts or returns from the energy saver mode, a connection error signal between CPU and slave device is detected, or the machine cannot access all I/O IPU-ASICs correctly.

SC665-11 through -031: When the machine starts or returns from the energy saver mode, a connection error between CPU and ASIC is detected.

  1. Incorrect FFC connection
  2. Damaged FFC (disconnection or dust)
  3. BiCU failure (Deteriorated board, sticking dust, or damaged parts)
  • Cycle the main power off/on.
  • Replace the BiCU.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

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.

  • BiCU failure
  • Cycle the power off/on.
  • Replace the BiCU.

SC667-10

D

Srave device 1 mode setting error

When the machine starts or returns from the energy saver mode, an error in the slave device 1 is detected.

  • BiCU failure
  • Cycle the power off/on.
  • Replace the BiCU.

SC667-40

D

ASIC operation mode setting error

-

  • BiCU failure
  • Cycle the power off/on.
  • Replace the BiCU.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC669-00

D

EEPROM error

The TD sensor cannot be recovered after retrying three times for EEPROM communication error.

  • Corrupted data due to noise
  • Incorrect EEPROM installation
  • Defective EEPROM
  • Defective BiCU
  1. Cycle the main power off/on.
  2. Turn the main power off and re-insert the EEPROM, then turn the main power on.
  3. Turn the main power off and replace the EEPROM, then turn the main power on.
  4. Turn the main power off and replace the BiCU, then turn the main power on.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC670-01

D

Engine start up error when main power switch on (* Refer to “When SC670 Is Displayed” below)

  • /ENGRDY 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).
  • Engine board does not start up.

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.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC670-02

D

Engine is down when machine starts up (SC reboot can not be performed) (* See “When SC670 Is Displayed” below)

Machine-down was detected after the /ENGRDY signal was not asserted.

The engine board was reset at an unexpected time

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.
When SC670 is Displayed

 

 

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC672-10

D

Controller start up error

After the machine was powered on, communication between the controller and the operation panel was not established.

  • Controller stalled
  • Board installed incorrectly
  • Controller board defective
  • Operation panel connector loose, broken or defective
  • Controller late
  • Cycle the main power off and on.
  • Check the connection of the controller board.
  • Replace the controller board.
  • Check the control panel harness.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC672-11

D

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.

  • Controller stalled
  • Board installed incorrectly
  • Controller board defective
  • Operation panel connector loose, broken or defective
  • Controller late
  • Incorrect Dip Switch Setting on Smart Operation Panel
  • Cycle the main power off and on.
  • Check the connection of the controller board.
  • Replace the controller board.
  • Check the control panel harness.
  • Make sure that the DIP switch numbers 3 and 7 are ON.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC672-12

D

Controller start up error

Communication with controller was interrupted after a normal startup.

  • Controller stalled
  • Board installed incorrectly
  • Controller board defective
  • Operation panel connector loose, broken or defective
  • Controller late
  • Cycle the main power off and on.
  • Check the connection of the controller board.
  • Replace the controller board.
  • Check the control panel harness.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC672-13

D

Controller start up error

The operation panel detects that the controller is down due to other reason shown in SC672-10, SC672-11, and SC672-12.

  • Controller stalled
  • Board installed incorrectly
  • Controller board defective
  • Operation panel connector loose, broken or defective
  • Controller late
  • Cycle the main power off and on.
  • Check the connection of the controller board.
  • Replace the controller board.
  • Check the control panel harness.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC672-99

D

Controller start up error

The operation panel software ended abnormally.

  • Controller stalled
  • Board installed incorrectly
  • Controller board defective
  • Operation panel connector loose, broken or defective
  • Controller late
  • Cycle the main power off and on.

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC673-10

D

Operation panel Flair communication error (Smart Operation Panel)

This SC is issued only for the machine that has the Smart Operation Panel installed.

  • Communication between Smart Operation Panel and main machine (this is called “Flair communication”) is not sent to Smart Operation Panel.
  • SP setting (SP5-748-201) for Smart Operation Panel is not activated.

The CATS module (controller) did not see the response to notification of monitoring service module (operation panel)

  • Cycle the main power off and on.
  • Set SP5-748-201 to “1: Connect” if the value is “0: Not connect”

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC681-**

D

Toner bottle: ID chip communication error

  • Corrupted ID data
  • Disconnected ID chip
  • No ID chip
  • Noise

Check the SC’s branch number (-** part) and do the above steps for the corresponding color.

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

  • Clean the ID chip.
  • Check the toner bottle detection board, and replace if damaged.
  • Reconnect the connectors between the BiCU and toner bottle detection board.
  • Set the toner bottle again.
  • Replace the harness between the BiCU and toner bottle detection board.
  • Replace the BiCU.
SC681 Details

No.

Detail

Causes

681

01 - 04

Invalid device ID

Noise, Incorrect connection, Malfunction

06 - 09

Channel error

Noise, Incorrect connection, Malfunction

11 - 14

Device Error

Noise, Incorrect connection

16 - 19

Communication error (interrupted)

Noise, Incorrect connection

21 - 24

Communication timeout

Noise, Incorrect connection, Malfunction

26 - 29

Device stops (logically)

Noise, Incorrect connection, Malfunction

31 - 34

Full of buffer (request)

Noise, Incorrect connection, Malfunction

36 - 39

Verification error

Noise, Incorrect connection

 

 

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

SC682-**

D

TD sensor communication error

TD sensor cannot be recovered after retrying three times for an ID chip communication error.

  • Corrupted ID data
  • Disconnected ID chip
  • No ID chip
  • Noise
  1. Remove the PCU and check the connector condition.
  2. Re-insert the harness (BiCU side) between the BiCU and the TD sensor.
  3. Replace the PCDU (if the TD sensor works incorrectly)
  4. Replace the harness between the BiCU and the TD sensor.
  5. Replace the BiCU.

Check the SC’s branch number (-** part) and do the above steps for the corresponding color.

  • 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

SC682 Details

No.

Description

Cause

682

01 - 04

Invalid device ID

Noise, Incorrect connection, Malfunction

06 - 09

Channel error

Noise, Incorrect connection, Malfunction

11 - 14

Device Error

Noise, Incorrect connection

16 - 19

Communication error (interrupted)

Noise, Incorrect connection

21 - 24

Communication timeout

Noise, Incorrect connection, Malfunction

26 - 29

Device stops (logically)

Noise, Incorrect connection, Malfunction

31 - 34

Full of buffer (request)

Noise, Incorrect connection, Malfunction

36 - 39

Verification error

Noise, Incorrect connection

51

Verification error (during storing to EEPROM)

Noise

52

Verification error (SRAM)

Noise

No.

Type

Details (Symptom, Possible Cause, Troubleshooting Procedures)

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 main power off/on.