610

D

Mechanical counter error: BK

This SC is only for NA models.

The machine detects the mechanical counter error when SP5987-001 is set to "1".

 Disconnected mechanical counter

 Defective mechanical counter

620

D

ADF communication error

-01

-

Communication error between machine and ADF

Communication error between machine and ADF with ASAP is detected.

 Disconnected cable

 ARDF defective

 IPU board defective External noise

-02

-

Communication error between IPU and ADF

After the ARDF is detected, the break signal occurs or communication timeout occurs.

 Incorrect installation of ARDF

 ARDF defective

 IPU board defective

 External noise

621

D

Communication timeout error between IOB and finisher or mailbox

A break (low) signal is received from the finisher or the mailbox.

 Disconnected cable

 Defective IOB

 Defective main board in the peripherals

622

D

Paper feed unit communication error

While the IOB communicates with a peripheral, an SC code is displayed if one of following conditions occurs.

 The IOB receives the break signal which is generated by the peripheral only just after the main switch is turned on.

 The IOB receives the break signal which is generated by URAT.

 Defective main control board of the peripheral

 Defective BCU or IOB

 Disconnected peripheral

623

D

2nd Paper Bank communication error

This SC is not issued for this machine when a communication error signal between the 1st paper bank and 2nd paper bank is received.

 Loose connector

630

C

CSS communication error

A communication error occurred during communication with the CSS.

 Communication line error

632

B

MF accounting device error 1

The controller sends data to the accounting device, but the device does not respond. This occurs three times.

 Loose connection between the controller and the accounting device

633

B

MF accounting device error 2

After communication is established, the controller receives the brake signal from the accounting device.

 Loose connection between the controller and the accounting device

634

B

MF accounting device error 3

The accounting device sends the controller the report that indicates a backup RAM error has occurred.

 Defective controller of the MF accounting device

 Battery error

635

B

MF accounting device error 4

The accounting device sends the controller the report that indicates the battery voltage error has occurred.

 Defective controller of the MF accounting device

 Battery error

636

D

IC Card Error

-01

D

External authentication module error

This SC is generated if the external authentication is enabled and following condition occurs:

 No external authentication module

 SD card error or external authentication module broken

 No DESS module

-02

D

Version error

The version of the external authentication module is not correct.

 Incorrect module version

-11

D

OSM User Code File Error

The correct "usercode" file could not be found in the root folder of the SD card because the file is not present, or the existing file is corrupted or the wrong type file.

Make sure the eccm.mod file is in the root folder of the SD card.

Note: Check the eccm.mod file is in the root folder of the SD card.

-99

D

Management area error

The management number of the external authentication module exceeds the maximum limit.

 Software error

637

D

Tracking Information Notice Error

-01

D

Tracking Application Error

When the tracking information is lost, this SC is issued.

 The machine failed to give notice the tracking information to the tracking SDK application.

 Tracking information is lost, and the machine cannot count correctly.

-02

D

Tracking Information Notice Error

When the tracking information is lost, this SC is issued.

 The machine failed to give notice the tracking information to the management server.

 Tracking information is lost, and the machine cannot count correctly.

641

D

BCU communication error

The BCU does not respond to the frame transmitted from the controller.

 Defective controller

 Detective BCU

650

-

Communication error of the remote service modem (Embedded RCG-M)

-001

-

Authentication error

The authentication for the Embedded RCG-M fails at a dial up connection.

 Incorrect SP settings

 Disconnected telephone line

 Disconnected modem board

Check and set the correct user name (SP5816-156) and password (SP5816-157).

-004

-

Incorrect modem setting

Dial up fails due to the incorrect modem setting.

 Same as -001

Check and set the correct AT command (SP5816-160).

-005

-

Communication line error

The supplied voltage is not sufficient due to a defective communication line or defective connection.

 Same as -001

Consult with the user's local telephone company.

-013

-

Modem board error 1

The modem board does not work properly even though the setting of the modem board is installed with a dial up connection.

 Same as -001

1. Install the modem board.

2. Check and reset the modem board setting with SP5816.

3. Replace the modem board.

-014

-

Modem board error 2

The modem board is installed even though the RCG-N is installed.

1. Uninstall the modem board, if it is installed.

2. Check that the Wireless LAN or Ethernet LAN is working properly.

651

C

Incorrect dial up connection

-001: Program parameter error

-002: Program execution error

An unexpected error occurs when the modem (Embedded RCG-M) tries to call the center with a dial up connection.

 Caused by a software bug

652

D

ID2 mismatching

ID2 for @Remote certification is mismatching between the controller board and NVRAM.

 Used controller board installed

 Used NVRAM installed

An unexpected error occurs when the modem (Embedded RCG-M) tries to call the center with a dial up connection.

1. Install the correct controller board or new controller board.

2. Install the correct NVRAM or new NVRAM.

653

D

ID2 error

ID2 stored in the NVRAM is incorrect.

 Used NVRAM installed

An unexpected error occurs when the modem (Embedded RCG-M) tries to call the center with a dial up connection.

Clear the ID2 in the NVRAM, and then input a correct ID2.

669

D

EEPROM error

-

-

[1]

Open communication error: ID error

[2]

Open communication error: Channel error

[3]

Open communication error: Device error

[4]

Open communication error: Communication failed error

[5]

Open communication error: Communication time error

[6]

Open communication error: Communication suspended error

[7]

Open communication error: Buffer full error

[8]

Close communication error: No error code

[9]

Close communication error: ID error

[10]

Close communication error: No error code

[11]

Data write error: ID error

[12]

Data write error: Channel error

[13]

Data write error: Device error

[14]

Data write error: Communication suspended error

[15]

Data write error: Communication time over error

[16]

Data write error: Communication suspended error

[17]

Data write error: Buffer full error

[18]

Data write error: No error code

[19]

Data read error: ID error

[20]

Data read error: Channel error

[21]

Data read error: Device error

[22]

Data read error: Communication failed error

[23]

Data read error: Communication time over error

-

-

[24]

Data read error: Communication suspended error

[25]

Data read error: Buffer full error

[26]

Data read error: No error code

[27]

Device detection error: ID error

[28]

Device detection error: Channel error

[29]

Device detection error: Device error

[30]

Device detection error: Communication failed error

[31]

Device detection error: Communication time over error

[32]

Device detection error: Communication suspended error

[33]

Device detection error: Buffer full error

[34]

Device detection error: No error code

Retry of EEPROM communication fails three times after the machine has detected the EEPROM error.

 Caused by noise

670

D

Engine startup error

The BCU fails to respond with the prescribed time when the machine is turned on.

 Connections between BCU and controller board are loose, disconnected, or damaged

1. Replace the BCU

2. Replace the controller board

672

D

Controller-to-operation panel communication error at startup

 After the machine is powered on, the communication between the controller and the operation panel is not established, or communication with controller is interrupted after a normal startup.

 After startup reset of the operation panel, the attention code or the attention acknowledge code is not sent from the controller within 30 seconds.

 After the controller issues a command to check the communication line with the controller at 30-second intervals, the controller fails to respond twice.

 Controller stalled

 Controller board installed incorrectly

 Controller board defective

 Operation panel connector loose or defective

 The controller is not completely shutdown when you turn the main switch off.

Check the setting of SP5875-001. If the setting is set to "1 (OFF)", change it to "0 (ON)".

674

D

Transmission error in controller board

Video transmission error is detected in the controller board.

 Defective Controller Board

687

D

Memory address (PER) command error

The BCU does not receive a memory address command from the controller for the prescribed time after the paper has reached the registration sensor.

 Harness Disconnection at BCU

 Controller board loose or broken

 Defective BCU

 Defective Controller Board