• Code: 681
• Description: Toner bottle: IDChip Communication error • 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
• Causes: • Corrupted ID data • Disconnected ID chip • No ID chip • Noise
• Remedy: • Clean the ID chip. • Replace the communication board on the toner bottle. • Replace the toner bottle. • Cycle the power off/on. • Replace the BiCU.

• Code: 682
• Description: TD sensor communication error TD sensor cannot be recovered after retrying three times for an ID chip communication error. • 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
• Causes: • Corrupted ID data • Disconnected ID chip • No ID chip • Noise
• Remedy: Turn the main power off, and then do the following. 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

• Code: 687-00
• Description: Memory address (PER) command error The BiCU does not receive a memory address command from the controller 120 seconds after paper is in the position for registration.
• Causes: • Loose connection • Defective controller • Defective BiCU
• Remedy: 1. Check if the controller is firmly connected to the BiCU. 2. Replace the controller 3. Replace the BiCU

• Code: 790-00
• Description: Too many paper tray units An attachment identification code is other than “01H” or ”02H”.
• Causes: • Number of paper tray units is more than the machine specification.
• Remedy: 1. Reduce the number of paper tray units within the machine specification.

• Code: 816
• Description: Energy save I/O subsystem error. Energy save I/O subsystem detected some abnormality.
• Causes: • Energy save I/O subsystem defective • Energy save I/O subsystem detected a controller board error (nonresponse). • Error was detected during preparation for transition to STR.
• Remedy: • Cycle the main power off and on. • Replace the controller board.

• Code: 817-00
• Description: Monitor error: File detection / Digital signature error • Bootloader cannot read any of diagnostic module, kernel, or root filesystem. • In a bootloader SD card, the digital signature checking for any of diagnostic module, kernel, or root filesystem is failed.
• Causes: • Any of the following items does not exist or is broken OS Flash ROM, Diagnostic module in SD card, Kernel, Root filesystem • Any of the following items is revised fraudulently: Diagnostic module in SD card, Kernel, Root filesystem
• Remedy: • ROM update for controller system • Use another booting SD card having a valid digital signature

• Code: 818-00
• Description: Watchdog timer error The system program fell into a bus-hold state or an endless loop of the program interruption occurred, causing other process to stop.
• Causes: • System program defective • Controller board defective • Optional board defective
• Remedy: • Cycle the main power off and on. • Replace the controller board.

• Code: 819-00
• Description: Kernel halt error [xxxx]: Detailed error code Due to a control error, a RAM overflow occurred during system processing. One of the following messages was displayed on the operation panel.
• Causes: [0x5032] HAIC-P2 error HAIC-P2 decompression error (An error occurred in the ASIC compression/ decompression module.) • The code data saved in the HDD was broken for an unexpected reason. (HDD device defective) • The code data saved to memory was broken for an unexpected reason. (Memory device defective) • ASIC defective • Data other than code data was unzipped due to a software malfunction. • Cycle the main power off and on. • Replace the HDD. • Replace the memory • Replace the controller board. • Fix the software [0x6261] HDD defective Received file system data was broken even if the initialization succeeds and there was no error reply from the HDD. Power supply disconnection during data writing to the HDD. Replace the HDD. This SC may occur when turning on the machine for the first time with a new HDD. In this case, turn the main power off/on. [0x696e] gwinit processing end If the SCS process is ended for some reason If an unexpected error occurs at SCS processing end, gwint processing also halts (this result is judged a kernel stop error, by gwinit specification) “0x69742064” -> “init died” Cycle the main power off and on. [0x766d] VM full error Occurs when too much RAM is used during system processing "vm_pageout: VM is full" Cycle the main power off and on. Console string Other error (characters on operation panel) System detected internal mismatch error • Software defective • Insufficient memory • Hardware driver defective (RAM, flash memory) • Replace with a larger capacity RAM, or flash memory. • Replace the controller board.
• Remedy: