SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC641-01 (CTL SC) | D | Engine serial communication error (Time-out) |
No response over the specified time. | ||
| ||
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC641-02 (CTL SC) | D | Engine serial communication error (Retry-Over) |
When commands are sent in the normal mode (ESIF_LECI_NORMAL), communication fails over the upper limit numbers (3 times) of command byte retry. | ||
| ||
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC641-03 (CTL SC) | D | Engine serial communication error (Download Error) |
In the download command mode (ESIF_LECI_DLCOM) or download data mode (ESIF_LECI_DLDAT), a communication error is returned from engine. | ||
| ||
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC641-04 (CTL SC) | D | Engine serial communication error (UART Error) |
UART receive errors (Break condition, Framing, Parity or Overrun error) are detected. | ||
| ||
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC667-01 | D | Master device operation mode setting error |
When the machine starts or returns from the energy saver mode, a CPU mode setting error is detected. | ||
Engine board is defective. | ||
Check if the SC occurs by turning the 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.
|
SC NO. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC669-** | D | EEPROM communication error |
An error is notified during EEPOM communication and the printer does not recover after three retries. | ||
669 - 1 ID error during EEPROM OPEN 669 - 2 Channel error during EEPROM OPEN 669 - 3 Device error during EEPROM OPEN 669 - 4 Communication interrupted error during EEPROM OPEN 669 - 5 Communication timeout error during EEPROM OPEN 669 - 6 Not operating error during EEPROM OPEN 669 - 7 Buffer full during EEPROM OPEN 669 - 11 ID error during EEPROM data write 669 - 12 Channel error during EEPROM data write 669 - 13 Device error during EEPROM data write 669 - 14 Communication interrupted error during EEPROM data write 669 - 15 Communication timeout error during EEPROM data write | ||
669 - 16 Not operating error during EEPROM data write 669 - 17 Buffer full during EEPROM data write 669 - 18 No error code during EEPROM data write 669 - 19 ID error during EEPROM data read 669 - 20 Channel error EEPROM data read 669 - 21 Device error during EEPROM data read 669 - 22 Communication interrupted error during EEPROM data read 669 – 23 EEPROM Data read: Communication timeout error 669 - 24 Not operating error during EEPROM data read 669 - 25 Buffer full during EEPROM data read 669 - 26 No error code during EEPROM data read 669 - 36 Verify error | ||
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC670-01 (CTL SC) | D | Engine start up error when the machine boots up |
| ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC670-02 (CTL SC) | D | Engine start up error when the machine is in operation |
| ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | 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. | ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | 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. | ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-12 | D | Controller start up error |
Communication with controller was interrupted after a normal startup. | ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-13 | D | Controller start up error |
The operation panel detected that the controller is down. | ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-20 | D | Controller start up error |
The operation panel detected that the controller is down. | ||
Operation panel connector is loose, broken or defective. | ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-21 | D | Controller start up error |
The operation panel detected that the controller is down. | ||
| ||
Check if the SC occurs by turning the 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.
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC672-99 | D | Controller start up error |
The operation panel software ended abnormally. | ||
| ||
Turn the main power OFF and then ON. |
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC673-01 | D | Flair connection error of Smart Operation Panel |
The SC is issued only when the Smart Operation Panel is installed. Abnormal end (ABEND) of Smart Operation Panel system is detected. | ||
- | ||
|
SC No. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
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. | ||
Note for the phone number: Other Information: When the automatic reboot cannot be performed due to a hardware failure, SC672 or SC673 is displayed. The SC call is not issued. You cannot reboot the machine manually, regardless of the SP5-875-002 setting. |
SC NO. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC687-00 | D | RAPI-PER receipt failure |
Even though 120 seconds have elapsed after RAPI -PES (request for image transfer) is issued, a RAPI-PER receipt is not received from the controller board. | ||
Defective controller board/software | ||
|
SC NO. | Pattern | Details (Symptom, Possible Cause, Troubleshooting Procedures) |
---|---|---|
SC688-00 | D | PRREQ signal not asserted |
The print request signal (PRREQ) signal is not asserted within the prescribed time after paper reaches the registration stand-by position, | ||
| ||
|