SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC621-01

D

Finisher communication error

SC621-02DMailbox communication error
  
  • When the communication line has opened and the machine is in a normal communication state, it has received a break signal from a connected device.

  • There is not any response within 100 ms after the data frame transmission, and retries have failed with timeout error for 3 times in a row.

  • When changing the baud rate after program downloading starts, the machine has failed to detect the break signal of the finisher or has failed to detect that the break has been cleared.

  
  • Connection error between finisher and main machine.

  • The finisher-related firmware is not installed properly.

  • The engine firmware is not installed properly.

  • Finisher control board defective.

  • BCU, or IOB defective

  • Communication error caused by electrostatic noise

  

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.

  1. Check if all connectors in the finisher/mailbox are connected securely. Reconnect the connectors if they are disconnected, or loose.
  2. Update the firmware to the latest version.
  3. Check all harnesses in the mailbox or finisher. Replace any harness that is damaged.
  4. Replace the BCU, or IOB.
  5. Replace the controller board of the finisher or the mailbox.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC622

D

Paper Bank Communication Error

SC622-11

D

Paper Bank 1 Communication Error (M494)

SC622-12

D

Paper Bank 1 Communication Error (M494)

SC622-31

D

Paper Bank 1 Communication Error (M496)

  

Detected an error when connecting the communication line.

  • Paper bank control board defective
  • BCU defective
  • Paper bank-main machine connection fault

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.

  1. Check if all connectors in tray 1, 2, and optional paper tray are connected securely. Reconnect the connectors if they are disconnected, or loose.
  2. Check the harness in tray 1, 2, and optional paper tray. Replace the harness if it is disconnected, or damaged.
  3. Check if there are any signs of a short circuit on the Bank Main Board. If there are any defects, replace the board.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC623-00

D

Paper Bank Communication Error (D696)

When two trays PFU (M494) and side LICT (D696) or LCIT (M496) and side LCIT (D696) are installed,

  1. When the upper stream unit (M494 or M496) recognizes the lower stream unit (D696), the break of the lower stream unit is not canceled within predetermined milliseconds.
  2. After the upper stream unit (M494 or M496) recognizes the lower stream unit (D696), there is no ACK within predetermined milliseconds after transmission of a data frame to the lower stream unit, and a timeout error occurs for 3 times consecutively even if retransmission is performed.
  • Bank control board fault
  • Connector disconnected
  • Turn the power off/on.
  • Reset the optional paper tray connecting cable.
  • Replace the BCU.
  • Replace the optional paper tray.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC641-00

D

Communication error between BCU and Controller board.

Controller board does not respond after BCU tries to communicate three times.

  • Controller board software error

  • Connection error between BCU and Controller board

  • Engine board software error

  • Check connections between Controller board and BCU.

  • Turn the main switch off and on.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC664-01

D

Access Permission Error to VODKA SRAM

SC664-02

D

Write Error to VODKA SRAM

SC664-03

D

VODKA Program Startup Error

  The machine detects the communication error between VODKA and SRAM when starting up, or recovery from energy saver mode.
  • BCU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Replace the BCU.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC665-01

D

BCU-IPU Connection Error

The machine detects the communication error between BCU and IPU (No FFC connection) when starting up, or recovery from energy saver mode.
  • BCU defective, IPU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Reconnect the FFC.
  • Replace the FFC.
  • Replace the BCU.
  • Replace the IPU.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC665-04

D

BCU (IOB Module) Does Not Start

The IOB does not start up when starting up, or recovery from energy saver mode.

  • No power supply to the BCU (IOB module) (power supply connector installed incorrectly, harness broken)
  • Board defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Reconnect the BCU power supply harness.
  • Replace the BCU power supply harness.
  • Replace the BCU.

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.

  • BCU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Replace the BCU.

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 Slave1 when starting up, or recovery from energy saver mode.

  • BCU defective, IPU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Reconnect the FCC.
  • Replace the FCC.
  • Replace the BCU.
  • Replace the IPU.

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.

  • BCU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Replace the BCU.

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.

  • BCU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Replace the BCU.

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.

  • BCU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Replace the BCU.

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.

  • BCU defective (Parts implementation defect, solder scrap, implemented parts defect, etc.)
  • Turn the power off/on.
  • Replace the BCU.
  • Replace the IPU.

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

  

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

  • Electrical noise
  • EEPROM not connected fully
  • EEPROM damaged
  • BCU damaged
  • Turn the power off/on.
  • Check the EEPROM.
  • Replace the EEPROM.
  • Replace the BCU.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC669-36

D

EEPROM: Verify Error

The machine receives an error notification during EEPROM (BCU) communication and does not resume after 2 retries.

The machine detects an abnormal value in the EEPROM data when starting up, or recovery from energy saver mode.

  • Electrical noise
  • EEPROM not connected fully
  • EEPROM damaged
  • BCU damaged
  • Turn the power off/on.
  • Check the EEPROM.
  • Replace the EEPROM.
  • Replace the BCU.

SC669-37

D

EEPROM: Failure Detection Error

The machine receives an error notification during EEPROM (BCU) communication and does not resume after 1 retries.

The machine determined EEPROM failure in the EEPROM detection operation when starting up, or recovery from energy saver mode.

  • Electrical noise
  • EEPROM not connected fully
  • EEPROM damaged
  • BCU damaged
  • Turn the power off/on.
  • Check the EEPROM.
  • Replace the EEPROM.
  • Replace the BCU.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC670-01

D

Engine start up error when the machine boots up

  • /ENGRDY signal was not asserted when the machine was turned on.

  • PCI I/F is not linked up when the machine returns from energy saver mode.

  • /IPURDY signal was not asserted when the machine was turned on or returned from energy saver mode.

  • EC/PC/SC response was not received within specified time from power on.

  • Writing to Rapi driver failed (the other party not found through PCI).

  • Connection defect between controller board and BCU.

  • BCU is down / unstable
  • BCU defective

  • PSU defective
  • Controller board defective
Refer to When SC670 Is Displayed.
SC No.TypeError Name/Error Condition/Major Cause/Solution
SC670-02DEngine start up error when the machine is in operation
  
  • CPU reset by software
  • CPU reset by anomaly CPU
  • CPU reset by hardware defect / noise
  • Hardware defect
Engine board reset unexpectedly.
Refer to When SC670 Is Displayed.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC672-00

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

Refer to When SC672 (Controller start up error) is displayed.
SC No.TypeError Name/Error Condition/Major Cause/Solution
SC672-10DController 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
Refer to When SC672 (Controller start up error) is displayed.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

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

Refer to When SC672 (Controller start up error) is displayed.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

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

Refer to When SC672 (Controller start up error) is displayed.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC672-13

D

Controller start up error

The operation panel detected that the controller is down.

  • Controller stalled

  • Board installed incorrectly

  • Controller board defective

  • Operation panel connector loose, broken, or defective

  • Controller late

Refer to When SC672 (Controller start up error) is displayed.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

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

Refer to When SC672 (Controller start up error) is displayed.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC673-10

D

Flair connection error of Smart Operation Panel

The SC is issued only when the Smart Operation Panel is installed.

The main machine does not respond to the smart operation panel with the Flair communication.

The SP setting for the smart operation panel is mismatched.

  • Turn the main power off/on.
  • Set the SP5748-201 (OpePanel Setting) to [1: ON].

Note for the phone number:
There is a phone number column on the SC673-10 display, but the phone number is not displayed because of this SC feature.

Other Information:

When the automatic reboot cannot be performed due to the hardware failure, SC672 or SC673 is displayed.

The SC call is not issued.

You cannot reboot the machine manually regardless of SP5-875-002 setting.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC682

 

PCU: ID Chip Communication Error

SC682-01

D

Invalid Device ID

SC682-06

D

Channel Error

SC682-11

D

Device Error

SC682-16

D

Communication Aborted (error during communication)

SC682-21

D

Communication Timeout

SC682-26

D

Device Stopped (logically stopped)

SC682-31

D

Requested Buffer Full

  

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

  • Device ID date error
  • Mu sensor / EEPROM defective
  • Electrical noise
  • PCU is not set properly.
  • Turn the power off/on.
  • Replace the PCU.

SC No.

Type

Error Name/Error Condition/Major Cause/Solution

SC682-36

D

PCU: Verify Error

Received a error notification during EEPROM communication and does not resume after 2 retries.

  • Device ID date error
  • Mu sensor / EEPROM defective
  • Electrical noise
  • PCU is not set properly.
  • Turn the power off/on.
  • Replace the PCU.

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.