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.
| ||
| ||
|
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. | |||
| |||
|
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. | ||
| ||
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.
| ||
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. | ||
| ||
|
SC645-01-04
No. | Type | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC650-01 | C | Remote service modem communication error (Dialup authentication failure) |
| ||
| ||
Check the following SPs.
|
No. | Type | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC650-04 | C | Remote Service Modem Communication Error (dialup failing because of incorrect modem configuration) |
| ||
| ||
Software bug. |
No. | Type | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC650-05 | C | Remote Service Modem Communication Error (insufficient current or connection fault) |
| ||
| ||
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)) |
| ||
| ||
|
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) |
| ||
| ||
|
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. | ||
| ||
|
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.
| ||
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 |
| ||
| ||
|
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-08 | D | BiCU 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. | ||
| ||
|
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. | ||
| ||
| ||
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. | ||
| ||
| ||
SC667-40 | D | ASIC operation mode setting error |
- | ||
| ||
|
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. | ||
| ||
|
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) |
| ||
| ||
Check the connection between the engine board and the controller board.
|
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.
|
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. | ||
| ||
|
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. | ||
| ||
|
No. | Type | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-12 | D | Controller start up error |
Communication with controller was interrupted after a normal startup. | ||
| ||
|
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. | ||
| ||
|
No. | Type | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-99 | D | Controller start up error |
The operation panel software ended abnormally. | ||
| ||
|
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.
| ||
The CATS module (controller) did not see the response to notification of monitoring service module (operation panel) | ||
|
No. | Type | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC681-** | D | Toner bottle: ID chip communication error |
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: | ||
|
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. | ||
| ||
Check the SC’s branch number (-** part) and do the above steps for the corresponding color.
|
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 |
| ||
| ||
Cycle the main power off/on. |