Eeprom data error

Содержание

1. Проблема с техникой. EEPROM ERROR-вот что написано на экране телевизора при включении. Что это? Как с этим бороться?
2. Код ошибки P062F – ошибка электронной стираемой постоянной памяти запоминающего устройства (EEPROM) внутреннего модуля управления
3. Техническое описание и расшифровка ошибки P062F
4. Симптомы неисправности
5. Причины возникновения ошибки
6. Как устранить или сбросить код неисправности P062F
7. Диагностика и решение проблем
8. Проверка контроллера и электрической части
9. На каких автомобилях чаще встречается данная проблема
10. eeprom
11. Тематики
12. Тематики
13. Синонимы
14. Тематики
15. Синонимы
16. Тематики
17. Тематики
18. См. также в других словарях:

Code: Select all

// ArduinoISP version 04m3
// Copyright (c) 2008-2011 Randall Bohn
// If you require a license, see 
//     http://www.opensource.org/licenses/bsd-license.php
//
// This sketch turns the Arduino into a AVRISP
// using the following arduino pins:
//
// pin name:    not-mega:         mega(1280 and 2560)
// slave reset: 10:               53 
// MOSI:        11:               51 
// MISO:        12:               50 
// SCK:         13:               52 
//
// Put an LED (with resistor) on the following pins:
// 9: Heartbeat   - shows the programmer is running
// 8: Error       - Lights up if something goes wrong (use red if that makes sense)
// 7: Programming - In communication with the slave
//
// 23 July 2011 Randall Bohn
// -Address Arduino issue 509 :: Portability of ArduinoISP
// http://code.google.com/p/arduino/issues/detail?id=509
//
// October 2010 by Randall Bohn
// - Write to EEPROM > 256 bytes
// - Better use of LEDs:
// -- Flash LED_PMODE on each flash commit
// -- Flash LED_PMODE while writing EEPROM (both give visual feedback of writing progress)
// - Light LED_ERR whenever we hit a STK_NOSYNC. Turn it off when back in sync.
// - Use pins_arduino.h (should also work on Arduino Mega)
//
// October 2009 by David A. Mellis
// - Added support for the read signature command
// 
// February 2009 by Randall Bohn
// - Added support for writing to EEPROM (what took so long?)
// Windows users should consider WinAVR's avrdude instead of the
// avrdude included with Arduino software.
//
// January 2008 by Randall Bohn
// - Thanks to Amplificar for helping me with the STK500 protocol
// - The AVRISP/STK500 (mk I) protocol is used in the arduino bootloader
// - The SPI functions herein were developed for the AVR910_ARD programmer 
// - More information at http://code.google.com/p/mega-isp

#include "pins_arduino.h"
#define RESET     SS

#define LED_HB    9
#define LED_ERR   8
#define LED_PMODE 7
#define PROG_FLICKER true

#define HWVER 2
#define SWMAJ 1
#define SWMIN 18

// STK Definitions
#define STK_OK      0x10
#define STK_FAILED  0x11
#define STK_UNKNOWN 0x12
#define STK_INSYNC  0x14
#define STK_NOSYNC  0x15
#define CRC_EOP     0x20 //ok it is a space...

void pulse(int pin, int times);

void setup() {
  Serial.begin(19200);
  pinMode(LED_PMODE, OUTPUT);
  pulse(LED_PMODE, 2);
  pinMode(LED_ERR, OUTPUT);
  pulse(LED_ERR, 2);
  pinMode(LED_HB, OUTPUT);
  pulse(LED_HB, 2);
}

int error=0;
int pmode=0;
// address for reading and writing, set by 'U' command
int here;
uint8_t buff[256]; // global block storage

#define beget16(addr) (*addr * 256 + *(addr+1) )
typedef struct param {
  uint8_t devicecode;
  uint8_t revision;
  uint8_t progtype;
  uint8_t parmode;
  uint8_t polling;
  uint8_t selftimed;
  uint8_t lockbytes;
  uint8_t fusebytes;
  int flashpoll;
  int eeprompoll;
  int pagesize;
  int eepromsize;
  int flashsize;
} 
parameter;

parameter param;

// this provides a heartbeat on pin 9, so you can tell the software is running.
uint8_t hbval=128;
int8_t hbdelta=8;
void heartbeat() {
  if (hbval > 192) hbdelta = -hbdelta;
  if (hbval < 32) hbdelta = -hbdelta;
  hbval += hbdelta;
  analogWrite(LED_HB, hbval);
  delay(20);
}


void loop(void) {
  // is pmode active?
  if (pmode) digitalWrite(LED_PMODE, HIGH); 
  else digitalWrite(LED_PMODE, LOW);
  // is there an error?
  if (error) digitalWrite(LED_ERR, HIGH); 
  else digitalWrite(LED_ERR, LOW);

  // light the heartbeat LED
  heartbeat();
  if (Serial.available()) {
    avrisp();
  }
}

uint8_t getch() {
  while(!Serial.available());
  return Serial.read();
}
void fill(int n) {
  for (int x = 0; x < n; x++) {
    buff[x] = getch();
  }
}

#define PTIME 30
void pulse(int pin, int times) {
  do {
    digitalWrite(pin, HIGH);
    delay(PTIME);
    digitalWrite(pin, LOW);
    delay(PTIME);
  } 
  while (times--);
}

void prog_lamp(int state) {
  if (PROG_FLICKER)
    digitalWrite(LED_PMODE, state);
}

void spi_init() {
  uint8_t x;
  SPCR = 0x53;
  x=SPSR;
  x=SPDR;
}

void spi_wait() {
  do {
  } 
  while (!(SPSR & (1 << SPIF)));
}

uint8_t spi_send(uint8_t b) {
  uint8_t reply;
  SPDR=b;
  spi_wait();
  reply = SPDR;
  return reply;
}

uint8_t spi_transaction(uint8_t a, uint8_t b, uint8_t c, uint8_t d) {
  uint8_t n;
  spi_send(a); 
  n=spi_send(b);
  //if (n != a) error = -1;
  n=spi_send(c);
  return spi_send(d);
}

void empty_reply() {
  if (CRC_EOP == getch()) {
    Serial.print((char)STK_INSYNC);
    Serial.print((char)STK_OK);
  } 
  else {
    error++;
    Serial.print((char)STK_NOSYNC);
  }
}

void breply(uint8_t b) {
  if (CRC_EOP == getch()) {
    Serial.print((char)STK_INSYNC);
    Serial.print((char)b);
    Serial.print((char)STK_OK);
  } 
  else {
    error++;
    Serial.print((char)STK_NOSYNC);
  }
}

void get_version(uint8_t c) {
  switch(c) {
  case 0x80:
    breply(HWVER);
    break;
  case 0x81:
    breply(SWMAJ);
    break;
  case 0x82:
    breply(SWMIN);
    break;
  case 0x93:
    breply('S'); // serial programmer
    break;
  default:
    breply(0);
  }
}

void set_parameters() {
  // call this after reading paramter packet into buff[]
  param.devicecode = buff[0];
  param.revision   = buff[1];
  param.progtype   = buff[2];
  param.parmode    = buff[3];
  param.polling    = buff[4];
  param.selftimed  = buff[5];
  param.lockbytes  = buff[6];
  param.fusebytes  = buff[7];
  param.flashpoll  = buff[8]; 
  // ignore buff[9] (= buff[8])
  // following are 16 bits (big endian)
  param.eeprompoll = beget16(&buff[10]);
  param.pagesize   = beget16(&buff[12]);
  param.eepromsize = beget16(&buff[14]);

  // 32 bits flashsize (big endian)
  param.flashsize = buff[16] * 0x01000000
    + buff[17] * 0x00010000
    + buff[18] * 0x00000100
    + buff[19];

}

void start_pmode() {
  spi_init();
  // following delays may not work on all targets...
  pinMode(RESET, OUTPUT);
  digitalWrite(RESET, HIGH);
  pinMode(SCK, OUTPUT);
  digitalWrite(SCK, LOW);
  delay(50);
  digitalWrite(RESET, LOW);
  delay(50);
  pinMode(MISO, INPUT);
  pinMode(MOSI, OUTPUT);
  spi_transaction(0xAC, 0x53, 0x00, 0x00);
  pmode = 1;
}

void end_pmode() {
  pinMode(MISO, INPUT);
  pinMode(MOSI, INPUT);
  pinMode(SCK, INPUT);
  pinMode(RESET, INPUT);
  pmode = 0;
}

void universal() {
  int w;
  uint8_t ch;

  fill(4);
  ch = spi_transaction(buff[0], buff[1], buff[2], buff[3]);
  breply(ch);
}

void flash(uint8_t hilo, int addr, uint8_t data) {
  spi_transaction(0x40+8*hilo, 
  addr>>8 & 0xFF, 
  addr & 0xFF,
  data);
}
void commit(int addr) {
  if (PROG_FLICKER) prog_lamp(LOW);
  spi_transaction(0x4C, (addr >> 8) & 0xFF, addr & 0xFF, 0);
  if (PROG_FLICKER) {
    delay(PTIME);
    prog_lamp(HIGH);
  }
}

//#define _current_page(x) (here & 0xFFFFE0)
int current_page(int addr) {
  if (param.pagesize == 32)  return here & 0xFFFFFFF0;
  if (param.pagesize == 64)  return here & 0xFFFFFFE0;
  if (param.pagesize == 128) return here & 0xFFFFFFC0;
  if (param.pagesize == 256) return here & 0xFFFFFF80;
  return here;
}


void write_flash(int length) {
  fill(length);
  if (CRC_EOP == getch()) {
    Serial.print((char) STK_INSYNC);
    Serial.print((char) write_flash_pages(length));
  } 
  else {
    error++;
    Serial.print((char) STK_NOSYNC);
  }
}

uint8_t write_flash_pages(int length) {
  int x = 0;
  int page = current_page(here);
  while (x < length) {
    if (page != current_page(here)) {
      commit(page);
      page = current_page(here);
    }
    flash(LOW, here, buff[x++]);
    flash(HIGH, here, buff[x++]);
    here++;
  }

  commit(page);

  return STK_OK;
}

#define EECHUNK (32)
uint8_t write_eeprom(int length) {
  // here is a word address, get the byte address
   int start = here; // * 2; - NA for m64
  int remaining = length;
  if (length > param.eepromsize) {
    error++;
    return STK_FAILED;
  }
  while (remaining > EECHUNK) {
    write_eeprom_chunk(start, EECHUNK);
    start += EECHUNK;
    remaining -= EECHUNK;
  }
  write_eeprom_chunk(start, remaining);
  return STK_OK;
}
// write (length) bytes, (start) is a byte address
uint8_t write_eeprom_chunk(int start, int length) {
  // this writes byte-by-byte,
  // page writing may be faster (4 bytes at a time)
  fill(length);
  prog_lamp(LOW);
  for (int x = 0; x < length; x++) {
    int addr = start+x;
    spi_transaction(0xC0, (addr>>8) & 0xFF, addr & 0xFF, buff[x]);
    delay(45);
  }
  prog_lamp(HIGH); 
  return STK_OK;
}

void program_page() {
  char result = (char) STK_FAILED;
  int length = 256 * getch();
  length += getch();
  char memtype = getch();
  // flash memory @here, (length) bytes
  if (memtype == 'F') {
    write_flash(length);
    return;
  }
  if (memtype == 'E') {
    result = (char)write_eeprom(length);
    if (CRC_EOP == getch()) {
      Serial.print((char) STK_INSYNC);
      Serial.print(result);
    } 
    else {
      error++;
      Serial.print((char) STK_NOSYNC);
    }
    return;
  }
  Serial.print((char)STK_FAILED);
  return;
}

uint8_t flash_read(uint8_t hilo, int addr) {
  return spi_transaction(0x20 + hilo * 8,
  (addr >> 8) & 0xFF,
  addr & 0xFF,
  0);
}

char flash_read_page(int length) {
  for (int x = 0; x < length; x+=2) {
    uint8_t low = flash_read(LOW, here);
    Serial.print((char) low);
    uint8_t high = flash_read(HIGH, here);
    Serial.print((char) high);
    here++;
  }
  return STK_OK;
}

char eeprom_read_page(int length) {
  // here again we have a word address
   int start = here; // * 2; - NA for m64
  for (int x = 0; x < length; x++) {
    int addr = start + x;
    uint8_t ee = spi_transaction(0xA0, (addr >> 8) & 0xFF, addr & 0xFF, 0xFF);
    Serial.print((char) ee);
  }
  return STK_OK;
}

void read_page() {
  char result = (char)STK_FAILED;
  int length = 256 * getch();
  length += getch();
  char memtype = getch();
  if (CRC_EOP != getch()) {
    error++;
    Serial.print((char) STK_NOSYNC);
    return;
  }
  Serial.print((char) STK_INSYNC);
  if (memtype == 'F') result = flash_read_page(length);
  if (memtype == 'E') result = eeprom_read_page(length);
  Serial.print(result);
  return;
}

void read_signature() {
  if (CRC_EOP != getch()) {
    error++;
    Serial.print((char) STK_NOSYNC);
    return;
  }
  Serial.print((char) STK_INSYNC);
  uint8_t high = spi_transaction(0x30, 0x00, 0x00, 0x00);
  Serial.print((char) high);
  uint8_t middle = spi_transaction(0x30, 0x00, 0x01, 0x00);
  Serial.print((char) middle);
  uint8_t low = spi_transaction(0x30, 0x00, 0x02, 0x00);
  Serial.print((char) low);
  Serial.print((char) STK_OK);
}
//////////////////////////////////////////
//////////////////////////////////////////


////////////////////////////////////
////////////////////////////////////
int avrisp() { 
  uint8_t data, low, high;
  uint8_t ch = getch();
  switch (ch) {
  case '0': // signon
    error = 0;
    empty_reply();
    break;
  case '1':
    if (getch() == CRC_EOP) {
      Serial.print((char) STK_INSYNC);
      Serial.print("AVR ISP");
      Serial.print((char) STK_OK);
    }
    break;
  case 'A':
    get_version(getch());
    break;
  case 'B':
    fill(20);
    set_parameters();
    empty_reply();
    break;
  case 'E': // extended parameters - ignore for now
    fill(5);
    empty_reply();
    break;

  case 'P':
    start_pmode();
    empty_reply();
    break;
  case 'U': // set address (word)
    here = getch();
    here += 256 * getch();
    empty_reply();
    break;

  case 0x60: //STK_PROG_FLASH
    low = getch();
    high = getch();
    empty_reply();
    break;
  case 0x61: //STK_PROG_DATA
    data = getch();
    empty_reply();
    break;

  case 0x64: //STK_PROG_PAGE
    program_page();
    break;

  case 0x74: //STK_READ_PAGE 't'
    read_page();    
    break;

  case 'V': //0x56
    universal();
    break;
  case 'Q': //0x51
    error=0;
    end_pmode();
    empty_reply();
    break;

  case 0x75: //STK_READ_SIGN 'u'
    read_signature();
    break;

    // expecting a command, not CRC_EOP
    // this is how we can get back in sync
  case CRC_EOP:
    error++;
    Serial.print((char) STK_NOSYNC);
    break;

    // anything else we will return STK_UNKNOWN
  default:
    error++;
    if (CRC_EOP == getch()) 
      Serial.print((char)STK_UNKNOWN);
    else
      Serial.print((char)STK_NOSYNC);
  }
}

Guest

Link

Guest

maxwell

• Code: C0070
• Description: FAX PWB incompatible detection error
• Causes: Abnormal detection of FAX control PWB incompatibility in the initial communication with the FAX control PWB, any normal communication command is not transmitted.
• Remedy: 1 Checking the FAX PWB The incompatible FAX PWB is installed. Install the FAX PWB for the applicable model. 2 Firmware upgrade The FAX firmware is faulty. Reinstall the FAX firmware. 3 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C0100
• Description: Backup memory device error
• Causes: An abnormal status is output from the flash memory.
• Remedy: 1 Resetting the main power The flash memory does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Checking the main PWB The connector or the FFC is not connected properly. Or, the wire, FFC, the PWB is faulty. Clean the terminal of the connectors on the main PWB, reconnect the connector of the wire, and reconnect the FFC terminal. If the wire or the FFC is faulty, repair or replace them. If not resolved, replace the main PWB.

• Code: C0120
• Description: MAC address data error
• Causes: The MAC address data is incorrect.
• Remedy: 1 Resetting the main power The flash memory does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Checking the MAC address The MAC address is incorrect. Replace the main PWB when the MAC address is not indicated on the network status page.

• Code: C0130
• Description: Backup memory reading/writing error
• Causes: The reading or writing into the flash memory is unavailable.
• Remedy: 1 Resetting the main power The flash memory does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Checking the main PWB The connector or the FFC is not connected properly. Or, the wire, FFC, the PWB is faulty. Clean the terminal of the connectors on the main PWB, reconnect the connector of the wire, and reconnect the FFC terminal. If the wire or the FFC is faulty, repair or replace them. If not resolved, replace the main PWB.

• Code: C0140
• Description: Backup memory data error
• Causes: The flash memory data read at the initial start-up is faulty
• Remedy: 1 Resetting the main power The flash memory does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Checking the main PWB The connector or the FFC is not connected properly. Or, the wire, FFC, the PWB is faulty. Clean the terminal of the connectors on the main PWB, reconnect the connector of the wire, and reconnect the FFC terminal. If the wire or the FFC is faulty, repair or replace them. If not resolved, replace the main PWB.

• Code: C0150
• Description: Engine EEPROM reading / writing error
• Causes: 1. Continuous five times detection of no response from the device for 5ms or more on reading / writing. 2. Data read twice do not match continuous 8 times. 3. Writing data and reading data do not match continuous 8 times.
• Remedy: 1 Resetting the main power The EEPROM on the engine PWB does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Checking the EEPROM on the engine PWB The EEPROM is not properly attached. Reattach the EEPROM on the engine PWB. 3 Replacing the EEPROM The EEPROM is faulty. 1. Print Maintenance Report at U000 beforehand. 2. Replace the EEPROM on the engine PWB. C6990 appears when turning the power on. Execute U169 at that state. 3. Then, print Maintenance Report at U000. Compare the setting values with Maintenance Report printed before and change the different values. (Target maintenance mode: U063, U100, U127, U140, U161, U465, U468 and U901, etc.) 4. Check the output image and adjust the image at U410, U411, etc. if necessary. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0160
• Description: EEPROM data error
• Causes: The data read from the EEPROM is judged as abnormal.
• Remedy: 1 Resetting the main power The EEPROM on the engine PWB does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Executing U021 The storage data in the EEPROM on the engine PWB is faulty. Execute U021. 3 Replacing the EEPROM The EEPROM is faulty. 1. Print Maintenance Report at U000 beforehand. 2. Replace the EEPROM on the engine PWB. C6990 appears when turning the power on. Execute U169 at that state. 3. Then, print Maintenance Report at U000. Compare the setting values with Maintenance Report printed before and change the different values. (Target maintenance mode: U063, U100, U127, U140, U161, U465, U468 and U901, etc.) 4. Check the output image and adjust the image at U410, U411, etc. if necessary. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0170
• Description: Charger count error
• Causes: 1. Errors are detected in both backup memory of the engine PWB charge counter and main PWB charge counter. 2. Main PWB counter data and engine PWB counter date are faulty
• Remedy: 1 Replacing the main PWB The main PWB is faulty. Replace the main PWB and execute U004 2 Replacing the EEPROM on the engine PWB The EEPROM is faulty. 1. Print Maintenance Report at U000 beforehand. 2. Replace the EEPROM on the engine PWB. C6990 appears when turning the power on. Execute U169 at that state. 3. Then, print Maintenance Report at U000. Compare the setting values with Maintenance Report printed before and change the different values. (Target maintenance mode: U063, U100, U127, U140, U161, U465, U468 and U901, etc.) 4. Check the output image and adjust the image at U410, U411, etc. if necessary. 3 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0180
• Description: Machine serial number mismatch
• Causes: The machine serial Nos. in the main PWB and the EEPROM on the engine PWB mismatch when turning the power on.
• Remedy: 1 Checking the machine serial No. of the main PWB The main PWB for the different main unit is installed. Check the machine serial Nos of MAIN and ENGINE at U004, and install the correct main PWB if the MAIN No. differs. 2 Checking the machine serial No. in the EEPROM on the engine PWB The EEPROM for the different main unit is installed. Check the machine serial Nos of MAIN and ENGINE at U004, and install the correct EEPROM on the engine PWB if the ENGINE machine serial No. differs. 3 Replacing the main PWB The main PWB is faulty. When the MAIN machine serial No. differs at U004, replace the main PWB and execute U004. 4 Checking the EEPROM on the engine PWB The EEPROM is faulty. If the machine serial number on the engine PWB is different at U004, reattach the EEPROM. If not repaired, replace the EEPROM on the engine PWB by referring to the following procedures. 1. Print Maintenance Report at U000 beforehand. 2. Replace the EEPROM on the engine PWB. C6990 appears when turning the power on. Execute U169 at that state. 3. Then, print Maintenance Report at U000. Compare the setting values with Maintenance Report printed before and change the different values. (Target maintenance mode: U063, U100, U127, U140, U161, U465, U468 and U901, etc.) 4. Check the output image and adjust the image at U410, U411, etc. if necessary. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0190
• Description: Backup memory device error (Engine)
• Causes: Data from the main unit IC cannot be read out at power-up
• Remedy: 1 Resetting the main power The IC in the engine PWB does not operate normally Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0500
• Description: Drive lock detected by the engine firmware
• Causes: During the engine steady state control, the main motor drive continued 60 minutes or more (except during the maintenance mode)
• Remedy: 1 Resetting the main power The firmware in the engine PWB does not operate normally Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0510
• Description: Main charger control error
• Causes: The main charger bias turns on while the drum stops.
• Remedy: 1 Resetting the main power The firmware in the engine PWB does not operate normally Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0520
• Description: Developer control error
• Causes: The developer bias off is detected during the main charge bias off
• Remedy: 1 Resetting the main power The firmware in the engine PWB does not operate normally Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0530
• Description: Backup task error
• Causes: No operation 30s or more when monitoring the backup task operation
• Remedy: 1 Resetting the main power The firmware in the engine PWB does not operate normally Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C0800
• Description: Image processing error
• Causes: The print sequence jam (J010x) is detected 2 times continuously.
• Remedy: 1 Checking the image data The image data is faulty. When this issue occurs only when handling the certain image data, check if the image data is faulty. 2 Checking the situation The printing operation of the certain file is faulty. Acquire the job’s log if the phenomenon can be reproduced by specifying the job when the error was detected. 3 Checking the main PWB The connector or the FFC is not connected properly. Or, the wire, FFC, the PWB is faulty. Clean the terminal of the connectors on the main PWB, reconnect the connector of the wire, and reconnect the FFC terminal. If the wire or the FFC is faulty, repair or replace them. If not resolved, replace the main PWB.

• Code: C0830
• Description: FAX PWB flash program area checksum error
• Causes: The program stored in the flash memory on the FAX PWB is broken so it cannot perform.
• Remedy: 1 Resetting the main power The FAX PWB is not connected properly. Turn off the power switch and pull out the power plug. After passing 5s, reattach the FAX PWB and reinsert the power plug. Then, turn on the power switch. 2 Firmware upgrade The firmware is faulty. Reinstall the FAX firmware. 3 Initializing the fax The data in the FAX PWB is faulty. Execute U600 to initialize the FAX. 4 Replacing the FAX PWB The FAX PWB is faulty. Replace the FAX PWB. Step

• Code: C0840
• Description: RTC error
• Causes: • Not communicated with RTC correctly. • RTC data is inconsistent with empty battery.
• Remedy: 1 Setting time and date (RTC) Time and date (RTC) are erased Set Date and Time (RTC) from System Menu 2 Replacing the main PWB The main PWB is faulty, or the backup battery runs out. Replacing the main PWB

• Code: C0870
• Description: PC FAX Image data transmission error
• Causes: Data was not properly transmitted even if the specified times of retry were made when the large volume data is transmitted between the FAX PWB and the main PWB.
• Remedy: 1 Resetting the main power The FAX PWB does not operate properly. Turn off the power switch and pull out the power plug. After passing 5s, reattach the FAX PWB and reinsert the power plug. Then, turn on the power switch. 2 Initializing the fax The data in the FAX PWB is faulty. Execute U600 to initialize the FAX. 3 Firmware upgrade The FAX firmware is faulty. Upgrade the fax firmware to the latest version. 4 Replacing the FAX PWB The FAX PWB is faulty. Replace the FAX PWB. 5 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C0920
• Description: FAX file system error
• Causes: The backup data could not be stored since the file system of the flash memory is faulty.
• Remedy: 1 Resetting the main power The FAX PWB does not operate properly. Turn off the power switch and pull out the power plug. After passing 5s, reattach the FAX PWB and reinsert the power plug. Then, turn on the power switch. 2 Initializing the fax FAX control values are incorrect Execute U600 to initialize the FAX. 3 Reconnecting the FAX PWB The FAX PWB is not connected properly. Reinstall FAX PWB to Main PWB. 4 Firmware upgrade The firmware is faulty. Reinstall the FAX firmware. 5 Replacing the FAX PWB The FAX PWB is faulty. Replace the FAX PWB.

• Code: C0980
• Description: 24V power interruption detection
• Causes: • 24V power shutoff signal is detected 1s continuously. • Other service call error occurs after 24V power shutoff signal is lowered, and then 24V power is recovered.
• Remedy: 1 Resetting the main power The firmware in the engine PWB does not operate normally Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Low-voltage PWB — Engine PWB 3 Replacing the low voltage PWB The low voltage PWB is faulty. When the +24V generation from the low voltage PWB is not stable, and it lowers, replace the low voltage PWB. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C1010
• Description: Lift motor 1 error
• Causes: • Cassette 1 lift motor over-current is detected 5 times continuously. • Lift sensor on is not detected 5 times continuously when passing 15s after cassette 1 is loaded.
• Remedy: 1 Checking the lift plate The lift plate does not operate properly. Repair or replace the lift plate when it does not move vertically. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Lift motor — Engine PWB(YC15) • Lift sensor — Engine PWB(YC15) 3 Checking the lift motor The lift motor is faulty. Check the lift motor operation, and replace it if necessary. 4 Checking the lift sensor The lift sensor is not properly attached, or it is faulty. Reattach PF lift upper limit sensor. If not repaired, replace it. 5 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C1020
• Description: PF lift motor 1 error Object: 500-sheet paper feeder, 500-sheetx2 paper feeder
• Causes: The PF lift sensor 1 on is not detected 5 times continuously when passing 15s after loading cassette 2.
• Remedy: 1 Checking the lift plate The lift plate does not operate properly. Repair or replace the lift plate when it does not move vertically. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • PF lift moor 1 — PF PWB (YC4) • PF upper limit sensor 1 — PF PWB (YC3) 3 Checking PF lift motor 1 PF lift motor 1 is faulty. Check the operation of lift motor 1, and replace it if necessary. 4 Checking PF lift sensor 1 PF lift sensor 1 is not properly attached, or it is faulty. Reattach PF lift sensor 1. If not repaired, replace it. 5 PF firmware upgrade The PF firmware is not the latest version. Upgrade the PF firmware to the latest version. 6 Replacing the PF PWB The PF PWB is faulty. Replace the PF PWB.

• Code: C1030
• Description: PF lift motor 2 error Object: 500-sheetx2 paper feeder
• Causes: The PF lift sensor 2 on is not detected 5 times continuously when passing 15s after loading cassette 3.
• Remedy: 1 Checking the lift plate The lift plate does not operate properly. Repair or replace the lift plate when it does not move vertically. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • PF lift moor 2 — PF PWB (YC6) • PF upper limit sensor 2 — PF PWB (YC5) 3 Checking PF lift motor 2 PF lift motor 2 is faulty. Check the operation of lift motor 2, and replace it if necessary. 4 Checking PF lift sensor 2 PF lift sensor 2 is not properly attached, or it is faulty. Reattach PF lift sensor 2. If not repaired, replace it. 5 PF firmware upgrade The PF firmware is not the latest version. Upgrade the PF firmware to the latest version. 6 Replacing the PF PWB The PF PWB is faulty. Replace the PF PWB.

• Code: C1800
• Description: Paper Feeder communication error Object: 500-sheet paper feeder, 500-sheetx2 paper feeder
• Causes: The communication error was detected 10 times continuously.
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Engine PWB (YC25) — PF PWB(YC1) 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware and PF firmware to the latest version 3 Replacing the PF PWB The PF PWB is faulty. Replace the PF PWB. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C1900
• Description: Paper Feeder EEPROM error Object: 500-sheet paper feeder, 500-sheetx2 paper feeder For internal count
• Causes: The writing data and the reading data mismatch 4 times continuously when writing.
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Engine PWB (YC25) — PF PWB(YC1) 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware and PF firmware to the latest version 3 Replacing the PF PWB The PF PWB is faulty. Replace the PF PWB. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2101
• Description: Developer motor K steady-state error
• Causes: Developer motor K steady state off is detected for 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer motor K — Engine PWB (YC18) 3 Checking the drive unit The drive unit is faulty. Execute U030 [Dlp(K)/Drum] and check the developer motor K operation. If there are any load for the gear rotation inside the drive unit replace drive unit B. 4 Replacing the developer motor The developer motor is faulty. Replace developer motor K. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2102
• Description: Developer motor CMY steady-state error
• Causes: Developer motor CMY steady state off is detected 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer motor CMY — Engine PWB (YC19) 3 Checking the drive unit The drive unit is faulty. Execute U030 [Dlp(Col)] and check the drum motor CMY operation. If there are any load for the gear rotation inside the drive unit replace drive unit A. 4 Replacing the developer motor The developer motor is faulty. Replace developer motor CMY. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2201
• Description: Drum motor K steady-state error
• Causes: Drum motor K steady state off is detected for 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drum motor K — Engine PWB (YC19) 3 Checking the drive unit The drive unit is faulty. Execute U030 [Dlp(K)/Drum] and check the drum motor K operation. If there are any load for the gear rotation inside the drive unit replace drive unit A. 4 Replacing drum motor K Drum motor K is faulty. Replace drum motor K. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2202
• Description: Drum motor CMY steady-state error
• Causes: Drum motor CMY steady state off is detected 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drum motor CMY — Engine PWB (YC19) 3 Checking the drive unit The drive unit is faulty. Execute U030 [Dlp(K)/Drum] and check the drum motor CMY operation. If there are any load for the gear rotation inside the drive unit replace drive unit A. 4 Replacing drum motor CMY Drum motor CMY are faulty. Replace drum motor CMY. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2300
• Description: Fuser motor steady state error
• Causes: The fuser motor steady state off is detected 1s continuously after becoming steady state
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Fuser motor — Engine PWB (YC18) 3 Checking the drive unit The drive unit is faulty. Check the fuser motor operation. If there are any load for the gear rotation inside the drive unit replace drive unit B. 4 Replacing the fuser motor The fuser motor is faulty. Replace the fuser motor. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2310
• Description: Fuser motor start-up error
• Causes: The fuser motor is not in the steady state within 1.5s after start-up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Fuser motor — Engine PWB (YC18) 3 Checking the drive unit The drive unit is faulty. Check the fuser motor operation. If there are any load for the gear rotation inside the drive unit replace drive unit B. 4 Replacing the fuser motor The fuser motor is faulty. Replace the fuser motor. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2550
• Description: Conveying motor steady-state error
• Causes: The conveying motor steady state off is detected 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Conveying motor — Engine PWB (YC14) 3 Checking the drive unit The drive unit is faulty. Execute U030 [Feed] and check the feed motor operation. If there are any load for the gear rotation inside the drive unit replace drive unit C. 4 Replacing the conveying motor The conveying motor is faulty. Replace the conveying motor. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2550
• Description: Conveying motor startup error
• Causes: The conveying motor is not in the steady state within 2s after start-up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Conveying motor — Engine PWB (YC14) 3 Checking the drive unit The drive unit is faulty. Execute U030 [Feed] and check the feed motor operation. If there are any load for the gear rotation inside the drive unit replace drive unit C. 4 Replacing the conveying motor The conveying motor is faulty. Replace the conveying motor. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C2600
• Description: PF motor error Object: 500-sheet paper feeder, 500-sheetx2 paper feeder
• Causes: An error signal was detected 2s continuously during the PF motor drive
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • PF motor — PF PWB(YC25) 2 Firmware upgrade The firmware is not the latest version. Upgrade the PF firmware to the latest version. 3 Checking the PF motor The PF motor is faulty Replace the PF motor 4 Replacing the PF PWB The PF PWB is faulty. Replace the PF PWB.

• Code: C2700
• Description: Belt release motor error
• Causes: The error signal is detected for 3s continuously after the belt release motor starts up.
• Remedy: 1 Firmware upgrade The engine firmware is faulty. Upgrade the engine firmware to the latest version 2 Checking the drive parts The drive transmission of the belt release motor is faulty. Repair the drive transmission parts if the drive from the belt release motor is not transmitted. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Belt release motor — Transfer PWB (YC2) • Belt rotation sensor — Transfer PWB (YC2) • Transfer PWB (YC2) — Transfer relay PWB (YC1) • Transfer relay PWB (YC2) — Engine PWB (YC11) 4 Checking the belt rotation sensor The belt rotation sensor comes off. Reattach or replace the belt rotation sensor. 5 Checking the belt release motor The belt release motor is not operated correctly. Reattach or replace the belt release motor. 6 Primary transfer unit replacement The primary transfer roller liftup drive section is faulty. Replace the primary transfer unit. 7 Replacing the transfer relay PWB The transfer relay PWB is faulty. Replace the transfer relay PWB. 8 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3100
• Description: Carriage error Object: CIS model
• Causes: The home position sensor is off and does not turn on when passing the specified time at initialization and it does not turn on at retry once.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the scanner and ISU shaft A load is applied to the scanner movement. Move the mirror unit manually. If there is heavy load in excess, check the drive belt and clean the ISU shaft. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Scanner motor — Engine PWB (YC12) 4 Checking the scanner motor The scanner motor is faulty. Reattach the scanner motor. If not repaired, replace it. 5 Checking the home position sensor The home position sensor is faulty. Reattach the home position sensor. If not repaired, replace it. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3100
• Description: Carriage error Object: LED model
• Causes: The home position sensor is off and does not turn on when passing the specified time at initialization and it does not turn on at retry once.
• Remedy: 1 Unlocking the primary mirror unit The primary mirror unit is not unlocked. Unlock the primary mirror unit. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version. 3 Checking the scanner and scanner wire A load is applied to the scanner movement. Move the mirror unit manually. If there is heavy load in excess, clean the scanner wire, wire drum, scanner rail, etc. 4 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Scanner motor — Engine PWB (YC12) 5 Checking the scanner motor and the belt tension. The scanner motor or belt tension is faulty Reattach the scanner motor and adjust the belt tension. If not repaired, replace the scanner motor. 6 Checking the home position sensor The home position sensor is faulty. Reattach the home position sensor. If not repaired, replace it. 7 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3200
• Description: LED error Object: LED model
• Causes: The white reference data retrieved by lighting the lamp at the initial operation is at the specified value or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the LED lamp The LED lamp does not light. Check if the LED lamp lights. If it does not light, replace the lamp unit and execute U411 [Table]. 3 Checking the connection The FFC is not correctly connected. Clean the FFC terminals of the following FFC and reconnect them. If the FFC terminal is deformed or broken, replace the FFC. • LED drive PWB — Main PWB (YC3003) 4 Checking the lens unit The CCD PWB is faulty. Clean the FFC terminal and reconnect it. If deformed or broken, replace the FFC. • CCD PWB — Main PWB (YC3002) If not repaired, replace the lens unit and execute U411. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3200
• Description: CIS error Object: CIS model
• Causes: • The white reference data retrieved by lighting the lamp at the initial operation is lower than the specified value. • The white reference data retrieved by lighting the lamp at the auto table adjustment is lower than the specified value.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the CIS lamp The CIS lamp does not light Check if the CIS lamp turns on. If not, replace the lamp unit and execute U411 [Table] 3 Checking the connection The FFC is not correctly connected. Clean the FFC terminals of the following FFC and reconnect them. If the FFC terminal is deformed or broken, replace the FFC. • CIS PWB — Main PWB (YC3001) 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3300
• Description: CCD AGC error Object: LED model For internal count
• Causes: The white reference data after adjustment is not within the target range
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Cleaning the backside of the contact glass The white reference sheet is dirty. Clean the white reference sheet at the backside of the contact glass. 3 Checking the LED lamp The LED lamp is broken. Check if the LED lamp lights. If it does not light, replace the lamp unit and execute U411 [Table]. 4 Checking the connection The FFC is not correctly connected. Clean the FFC terminals of the following FFC and reconnect them. If the FFC terminal is deformed or broken, replace the FFC. • LED drive PWB — Main PWB (YC3003) 5 Checking the lens unit The CCD PWB is faulty. Clean the FFC terminal and reconnect it. If deformed or broken, replace the FFC. • CCD PWB — Main PWB (YC3002) If not repaired, replace the lens unit and execute U411. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3300
• Description: CIS AGC error Object: CIS model For internal count
• Causes: The white reference data after adjustment is not within the target range
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Cleaning the backside of the contact glass The white reference sheet is dirty. Clean the white reference sheet at the backside of the contact glass. 3 Checking the CIS lamp The CIS lamp does not light Check if the CIS lamp turns on. If not, replace the lamp unit and execute U411 [Table] 4 Checking the connection The FFC is not correctly connected. Clean the FFC terminals of the following FFC and reconnect them. If the FFC terminal is deformed or broken, replace the FFC. • CIS PWB — Main PWB (YC3001) 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C3500
• Description: Scanner AISC communication error
• Causes: Readback values are different 4 times continuously during communication between the scanner and ASIC
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware and the engine firmware to the latest version. 2 Checking the connection FFC is not connected properly. Or it is faulty. Clean the FFC terminals of the following FFC and reconnect them. If the FFC terminal is deformed or broken, replace the FFC. • Main PWB (YC26) — Engine PWB (YC3) 3 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 4 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C3600
• Description: Scanner sequence error
• Causes: • Mail box buffer overflow is detected. • Software sequence error is detected.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware and the engine firmware to the latest version. 2 Executing U021 The memory operation is faulty. Execute U021 and initialize the backup data 3 Checking the connection FFC is not connected properly. Or it is faulty. Clean the FFC terminals of the following FFC and reconnect them. If the FFC terminal is deformed or broken, replace the FFC. • Main PWB (YC26) — Engine PWB (YC3) 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 5 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C4001
• Description: Polygon motor K startup error
• Causes: Polygon motor K is not in the steady state within 10s after becoming steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor K — LSU relay PWB (YC5) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU K if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4002
• Description: Polygon motor C startup error
• Causes: Polygon motor C is not in the steady state within 10s after becoming steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor C — LSU relay PWB (YC7) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU C if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4003
• Description: Polygon motor M startup error
• Causes: Polygon motor M is not in the steady state within 10s after becoming steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor M — LSU relay PWB (YC6) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU M if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4004
• Description: Polygon motor Y startup error
• Causes: Polygon motor Y is not in the steady state within 10s after becoming steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor Y — LSU relay PWB (YC8) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU Y if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4011
• Description: Polygon motor K steady-state error
• Causes: Polygon motor K is off from the steady state for 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor K — LSU relay PWB (YC5) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU K if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4012
• Description: Polygon motor C steady-state error
• Causes: Polygon motor C is off from the steady state for 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor C — LSU relay PWB (YC7) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU C if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4013
• Description: Polygon motor M steady-state error
• Causes: Polygon motor M is off from the steady state for 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor M — LSU relay PWB (YC6) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU M if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4014
• Description: Polygon motor Y steady-state error
• Causes: Polygon motor Y is off from the steady state for 1s continuously after becoming the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Polygon motor Y — LSU relay PWB (YC8) • LSU relay PWB (YC9) — Engine PWB (YC6) 3 Checking the polygon motor The polygon motor does not rotate properly. Check the rotation sound of the polygon motor, and reattach or replace LSU Y if it does not rotate properly. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4101
• Description: BD initialization error (Black)
• Causes: BD is not detected within 1s after polygon motor K is in the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware to the latest version. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • APC PWB K — LSU relay PWB (YC1) • LSU relay PWB (YC10) — Main PWB (YC23) 3 Checking the LSU The APC PWB does not operate normally Reinstall or replace LSU K. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C4102
• Description: BD initialization error (Cyan)
• Causes: BD is not detected within 1s after polygon motor C is in the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware to the latest version. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • APC PWB C — LSU relay PWB (YC3) • LSU relay PWB (YC10) — Main PWB (YC23) 3 Checking the LSU The APC PWB does not operate normally Reinstall or replace LSU C. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C4103
• Description: BD initialization error (Magenta)
• Causes: BD is not detected within 1s after polygon motor M is in the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware to the latest version. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • APC PWB M — LSU relay PWB (YC2) • LSU relay PWB (YC10) — Main PWB (YC23) 3 Checking the LSU The APC PWB does not operate normally Reinstall or replace LSU M. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C4104
• Description: BD initialization error (Yellow)
• Causes: BD is not detected within 1s after polygon motor Y is in the steady state.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware to the latest version. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • APC PWB Y — LSU relay PWB (YC4) • LSU relay PWB (YC10) — Main PWB (YC23) 3 Checking the LSU The APC PWB does not operate normally Reinstall or replace LSU Y. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C4600
• Description: LSU cleaning motor error
• Causes: The error signal is detected for 2s continuously after the motor starts up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the drive parts The drive transmission from the LSU cleaning motor is faulty. Repair the drive transmission parts if the drive from the LSU cleaning motor is not transmitted. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • LSU cleaning motor — LSU relay PWB (YC11) • LSU relay PWB (YC9) — Engine PWB (YC6) 4 Replacing the LSU cleaning motor The LSU cleaning motor is faulty. Replace the LSU cleaning motor. 5 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C4700
• Description: Video ASIC device error
• Causes: Writing data and reading data does not match 8 consecutive times.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware and engine firmware to the latest version. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Main PWB (YC26) — Engine PWB (YC3) 3 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 4 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: C6000
• Description: IH heating error
• Causes: 1. The fuser center thermistor does not detect 100°C / 212°F or more within 25s after warm-up is started. 2. During the warm-up, the fuser center thermistor does not detect the ready temperature within 20s after it detects 100°C / 212°F.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Executing U169 The IH setting mismatches the power supply specification. Set the destination same as the voltage of the IH PWB at U169. 3 Removing foreign material There are foreign objects between the fuser unit and the IH unit. Or, the foreign objects are adhered on the fuser heat belt. Remove foreign material if it is on between the fuser unit and the IH unit, or on the fuser unit. Then, reinstall the fuser unit. 4 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 5 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 6 Replacing the fuser unit The parts such as the thermistor or thermal cutout are faulty. Replace the fuser unit. 7 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 8 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 9 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6020
• Description: Fuser center thermistor high temperature error
• Causes: The fuser center thermistor detected 230°C / 446°F or more for 1s.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 4 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 6 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 7 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6030
• Description: Broken fuser center thermistor
• Causes: 1. During warm-up, the fuser center thermistor detects 41°C / 105°F for 1s continuously while the fuser edge thermistor detects 100°C / 212°F or more. 2. The fuser center thermistor does not detect 25°C / 77°F within 12s after start-up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Removing foreign material There are foreign objects between the fuser unit and the IH unit. Or, the foreign objects are adhered on the fuser heat belt. Remove foreign material if it is on between the fuser unit and the IH unit, or on the fuser unit. Then, reinstall the fuser unit. 3 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 4 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 5 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 7 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 8 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6050
• Description: Fuser center thermistor low temperature error
• Causes: The fuser center thermistor detects less than 80°C / 176°F for 1s during printing.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Removing foreign material There are foreign objects between the fuser unit and the IH unit. Or, the foreign objects are adhered on the fuser heat belt. Remove foreign material if it is on between the fuser unit and the IH unit, or on the fuser unit. Then, reinstall the fuser unit. 3 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 4 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 5 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 7 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 8 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6120
• Description: Fuser press roller thermistor high temperature error
• Causes: The fuser press roller thermistor detected 210°C / 410°F or more for 1s.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6130
• Description: Broken fuser press roller thermistor
• Causes: 1. During warm-up, the fuser press roller thermistor detects less than 35°C / 95°F for 60s continuously. 2. After finishing warm-up, the fuser press roller thermistor detects less than 35°C / 95°F for 30s continuously.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Removing foreign material There are foreign objects between the fuser unit and the IH unit. Or, the foreign objects are adhered on the fuser heat belt. Remove foreign material if it is on between the fuser unit and the IH unit, or on the fuser unit. Then, reinstall the fuser unit. 3 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 4 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 5 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 7 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 8 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6200
• Description: IH heating error 2
• Causes: 1. After warm-up is started, the fuser edge thermistor does not detect 80°C / 176°F within 25s. Or, during the warm-up, specified temperature (Ready display temperature) is not detected even 420s passed after center thermistor reached 100°C / 212°F.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Removing foreign material There are foreign objects between the fuser unit and the IH unit. Or, the foreign objects are adhered on the fuser heat belt. Remove foreign material if it is on between the fuser unit and the IH unit, or on the fuser unit. Then, reinstall the fuser unit. 3 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 4 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 5 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 7 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 8 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6220
• Description: Fuser edge thermistor high temperature error
• Causes: The fuser edge thermistor detects 245°C / 473°F or more for 1s.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 6 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6230
• Description: Broken fuser edge thermistor
• Causes: 1. During warm-up, the fuser edge thermistor detects less than 41°C / 105°F for 1s continuously while the fuser center thermistor detects 100°C / 212°F or more. 2. The fuser edge thermistor does not detect 25°C / 77°F within 12s after start-up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6250
• Description: Fuser edge thermistor low temperature error
• Causes: The fuser edge thermistor detected less than 80°C / 176°F for 1s during printing.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Removing foreign material There are foreign objects between the fuser unit and the IH unit. Or, the foreign objects are adhered on the fuser heat belt. Remove foreign material if it is on between the fuser unit and the IH unit, or on the fuser unit. Then, reinstall the fuser unit. 3 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 4 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 5 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 7 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 8 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6320
• Description: Fuser middle thermistor high temperature error
• Causes: The fuser middle thermistor detected 245°C / 473°F or more for 1s.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 6 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6330
• Description: Broken fuser middle thermistor
• Causes: The fuser middle thermistor detects less than 41 °C / 105°F for 1s continuously while the fuser center thermistor or the fuser edge thermistor detects 100°C / 212°F or more during warm-up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The parts such as the thermistor are faulty. Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 6 Replacing the IH unit The IH unit is faulty. Replace the IH unit.

• Code: C6600
• Description: Fuser heat belt rotation error
• Causes: The belt rotation pulse is not input for 1.8s continuously.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The fuser unit parts such as the fuser heat belt, the belt rotation detecting system, or the belt rotation sensor are faulty Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB. 6 Replacing the fuser drive unit The fuser drive unit is faulty. Replace the fuser drive unit. Step

• Code: C6610
• Description: Fuser pressure release sensor error
• Causes: 1. The fuser pressure release sensor does not turn off even after 10s passed from instructing to reduce the fuser pressure. 2. The fuser pressure release sensor does not turn on even after 10s passed from instructing to increase the fuser pressure. 3. The lock signal of the fuser pressure release motor became error for 300ms.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Drawer connector of the fuser unit — Engine PWB (YC9) 4 Replacing the fuser unit The fuser unit is faulty at the fuser pressure release mechanism or the fuser pressure release sensor . Replace the fuser unit. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6740
• Description: IH PWB high temperature error (IGBT2)
• Causes: The IGBT temperature acquired from the power microprocessor detects 115°C / 239°F or more for 1s continuously.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • IH fan motor — Engine PWB (YC20) • IH PWB (YC4) — Engine PWB (YC10) 3 Replacing the IH PWB fan motor The IH PWB fan motor is faulty. Replace the IH PWB fan motor. 4 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6760
• Description: Fuser IH input excessive electric current error
• Causes: The input current obtained from the power microcomputer was 20A (100/120V) or 10A (200V) or more continued for 200ms.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the fuser unit The fuser heat belt is faulty. Detach the fuser unit and check if the fuser heat belt is not faulty. If there is any damage, replace the fuser unit. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • IH PWB (YC4) — Engine PWB (YC10) 4 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6770
• Description: IH low power error
• Causes: After fuser heating starts,the electric power detection on the IH PWB detected a set electric power value of 30% or less for a predetermined time.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the fuser unit There are foreign objects in the drawer contact terminal of the fuser unit Clean the drawer connector terminal of the fuser unit. Check if the pin of the drawer connector is not bent, and replace the fuser unit if it is bent. If it is normal, reinstall the fuser unit so that the drawer connector is securely connected. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • IH unit — IH PWB (YC2, YC3) • IH PWB (YC4) — Engine PWB (YC10) 4 Replacing the IH unit The IH unit is faulty. (The coil is broken.) Replace the IH unit. 5 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6940
• Description: IH fan motor error
• Causes: Lock-up is detected for 20s continuously when the fan motor drives.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • IH fan motor — Engine PWB (YC20) 3 Checking the IH fan motor The IH fan motors do not properly operate. Clean the IH fan motor and remove foreign objects. If not resolved after that, replace the IH fan motor. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6950
• Description: IH-CPU communication error
• Causes: 1. Communication between the IH PWB and the engine PWB is not established in the initial communication. (150ms interval x 10 times retries and then 3 times retries of the relay remote) 2. After the initial communication is established, communication between the IH PWB and the engine PWB is not established at the operation except for printing. (If communication fails for 500ms, 3 times retries or the relay remote are performed.) 3. After the initial communication is established, communication between the IH PWB and the engine PWB is not established durint printing. (If communication fails for 500ms, 150ms interval x 10 times retries are performed.)
• Remedy: 1 Resetting the main power The power startup delays. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • IH PWB (YC4) — Engine PWB (YC10) 4 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C6990
• Description: Fuser power source destination error
• Causes: The engine backup data does not match the IH PWB power supply destination. (0, 5 or more)
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Executing U169 The voltage setting at U169 mismatches the voltage of the IH PWB. Set the destination same as the voltage of the IH PWB at U169. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • IH PWB (YC4) — Engine PWB (YC10) 4 Replacing the IH PWB The IH PWB is faulty. Replace the IH PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7101
• Description: T/C sensor K error
• Causes: The sensor input voltage is less than 0.3V, or 3.2V or more. Also, that state continues for 5s or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the developer unit The developer unit is not properly installed. Reinstall developer unit K so that the connector firmly connects. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer PWB K — Drum/Developer relay PWB (YC9) • Drum/Developer relay PWB (YC1) — Engine PWB (YC17) 4 Developer unit replacement Developer unit K (T/C sensor K) is faulty. Replace developer unit K. 5 Replacing the drum/developer relay PWB The drum/developer relay PWB is faulty. Replace the drum/developer relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7102
• Description: T/C sensor C error
• Causes: The sensor input voltage is less than 0.3V, or 3.2V or more. Also, that state continues for 5s or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the developer unit The developer unit is not properly installed. Reinstall developer unit C so that the connector firmly connects. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer PWB C — Drum/Developer relay PWB (YC7) • Drum/Developer relay PWB (YC1) — Engine PWB (YC17) 4 Developer unit replacement Developer unit C (T/C sensor C) is faulty. Replace the developer unit C. 5 Replacing the drum/developer relay PWB The drum/developer relay PWB is faulty. Replace the drum/developer relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7103
• Description: T/C sensor M error
• Causes: The sensor input voltage is less than 0.3V, or 3.2V or more. Also, that state continues for 5s or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the developer unit The developer unit is not properly installed. Reinstall developer unit M so that the connector firmly connects. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer PWB M — Drum/Developer relay PWB (YC8) • Drum/Developer relay PWB (YC1) — Engine PWB (YC17) 4 Developer unit replacement Developer unit M (T/C sensor M) is faulty. Replace the developer unit M. 5 Replacing the drum/developer relay PWB The drum/developer relay PWB is faulty. Replace the drum/developer relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7104
• Description: T/C sensor Y error
• Causes: The sensor input voltage is less than 0.3V, or 3.2V or more. Also, that state continues for 5s or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the developer unit The developer unit is not properly installed. Reinstall developer unit Y so that the connector firmly connects. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer PWB Y — Drum/Developer relay PWB (YC6) • Drum/Developer relay PWB (YC1) — Engine PWB (YC17) 4 Developer unit replacement Developer unit Y (T/C sensor Y) is faulty. Replace the developer unit Y. 5 Replacing the drum/developer relay PWB The drum/developer relay PWB is faulty. Replace the drum/developer relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7200
• Description: Inner thermistor broken (developer)
• Causes: The sensor input data is 0.3V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the developer unit The developer unit is not properly installed. Reinstall developer unit K so that the connector firmly connects. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer PWB K — Drum/Developer relay PWB (YC9) • Drum/Developer relay PWB (YC1) — Engine PWB (YC17) 4 Developer unit replacement The sensor on the developer PWB is faulty Replace developer unit K. 5 Replacing the drum/developer relay PWB The drum/developer relay PWB is faulty. Replace the drum/developer relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7210
• Description: Inner thermistor short-circuited (developer)
• Causes: The sensor input data is 3.0V or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Reinstalling the developer unit The developer unit is not properly installed. Reinstall developer unit K so that the connector firmly connects. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Developer PWB K — Drum/Developer relay PWB (YC9) • Drum/Developer relay PWB (YC1) — Engine PWB (YC17) 4 Developer unit replacement The sensor on the developer PWB is faulty Replace developer unit K. 5 Replacing the drum/developer relay PWB The drum/developer relay PWB is faulty. Replace the drum/developer relay PWB. 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7221
• Description: Broken LSU thermistor K
• Causes: The sensor input data is 0.3V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector or FFC is not properly connected, or the wire or FFC is faulty. Clean the terminal of the following wire connectors and the FFC, then reinsert them. If there is no continuity, replace the wire or FFC. • APC PWB K — LSU relay PWB (YC1) • LSU relay PWB (YC9) — Engine PWB(YC6) 3 Replacing the LSU LSU thermistor K is faulty. Replace LSU K. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7224
• Description: Broken LSU thermistor Y
• Causes: The sensor input data is 0.3V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector or FFC is not properly connected, or the wire or FFC is faulty. Clean the terminal of the following wire connectors and the FFC, then reinsert them. If there is no continuity, replace the wire or FFC. • APC PWB Y — LSU relay PWB (YC4) • LSU relay PWB (YC9) — Engine PWB(YC6) 3 Replacing the LSU LSU thermistor Y is faulty. Replace LSU Y. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7231
• Description: LSU thermistor K short-circuited
• Causes: The sensor input data is 3.0V or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector or FFC is not properly connected, or the wire or FFC is faulty. Clean the terminal of the following wire connectors and the FFC, then reinsert them. If there is no continuity, replace the wire or FFC. • APC PWB K — LSU relay PWB (YC1) • LSU relay PWB (YC9) — Engine PWB(YC6) 3 Replacing the LSU LSU thermistor K is faulty. Replace LSU K. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7234
• Description: LSU thermistor Y short-circuited
• Causes: The sensor input data is 3.0V or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector or FFC is not properly connected, or the wire or FFC is faulty. Clean the terminal of the following wire connectors and the FFC, then reinsert them. If there is no continuity, replace the wire or FFC. • APC PWB Y — LSU relay PWB (YC4) • LSU relay PWB (YC9) — Engine PWB(YC6) 3 Replacing the LSU LSU thermistor Y is faulty. Replace LSU Y. 4 Replacing the LSU relay PWB The LSU relay PWB is faulty. Replace the LSU relay PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7240
• Description: Broken container thermistor
• Causes: The sensor input data is 0.3V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Container relay PWB (YC1) — Engine PWB (YC22) 3 Replacing the container relay PWB The container relay PWB is faulty. Replace the container relay PWB. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7250
• Description: Container thermistor short-circuited
• Causes: The sensor input data is 3.0V or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Container relay PWB (YC1) — Engine PWB (YC22) 3 Replacing the container relay PWB The container relay PWB is faulty. Replace the container relay PWB.

• Code: C7601
• Description: Front ID sensor error
• Causes: • The sensor output value of the dark potential is 0.15V or less, or 0.80V or more. • Bright potential is lower than the dark potential, or the gap is 0.5V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Cleaning the front ID sensor The front ID sensor is dirty. Clean the front ID sensor surface. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Front ID sensor — Engine PWB (YC7) 3 Replacing the front D sensor The front ID sensor is faulty. Replace the front ID sensor. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7602
• Description: Rear ID sensor error
• Causes: • The sensor output value of the dark potential is 0.15V or less, or 0.80V or more. • Bright potential is lower than the dark potential, or the gap is 0.5V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Cleaning the rear ID sensor The rear ID sensor is dirty. Clean the rear ID sensor surface. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Rear ID sensor — Engine PWB (YC7) 3 Replacing the rear ID sensor The rear ID sensor is faulty. Replace the rear ID sensor. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7611
• Description: ID sensor density error K
• Causes: The density of the BK-patch on the primary transfer belt is faulty at the Calibration or Color Adjustment.
• Remedy: 1 Resetting the main power The ID sensor does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 3 Cleaning the ID sensor The ID sensor is dirty. Clean the surface of the front and rear ID sensors. 4 Checking the developer unit and drum unit The developer unit or the drum unit is not properly installed. Reinstall developer unit K and drum unit K. 5 Checking the primary transfer unit The primary transfer belt is dirty. Clean the surface of the primary transfer belt, or replace the primary transfer unit. 6 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Front ID sensor and Rear ID sensor — Engine PWB (YC7) 7 Replacing the ID sensor The ID sensor is faulty. Replace the front ID sensor or the rear ID sensor. 8 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7612
• Description: ID sensor density error C
• Causes: The density of the C-patch on the primary transfer belt is faulty at the Calibration or Color Adjustment.
• Remedy: 1 Resetting the main power The ID sensor does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 3 Cleaning the ID sensor The ID sensor is dirty. Clean the surface of the front and rear ID sensors. 4 Checking the developer unit and drum unit The developer unit or the drum unit is not properly installed. Reinstall developer unit C and drum unit C. 5 Checking the primary transfer unit The primary transfer belt is dirty. Clean the surface of the primary transfer belt, or replace the primary transfer unit. 6 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Front ID sensor and Rear ID sensor — Engine PWB (YC7) 7 Replacing the ID sensor The ID sensor is faulty. Replace the front ID sensor or the rear ID sensor. 8 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7613
• Description: ID sensor density error M
• Causes: The density of the M-patch on the primary transfer belt is faulty at the Calibration or Color Adjustment.
• Remedy: 1 Resetting the main power The ID sensor does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 3 Cleaning the ID sensor The ID sensor is dirty. Clean the surface of the front and rear ID sensors. 4 Checking the developer unit and drum unit The developer unit or the drum unit is not properly installed. Reinstall developer unit M and drum unit M. 5 Checking the primary transfer unit The primary transfer belt is dirty. Clean the surface of the primary transfer belt, or replace the primary transfer unit. 6 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Front ID sensor and Rear ID sensor — Engine PWB (YC7) 7 Replacing the ID sensor The ID sensor is faulty. Replace the front ID sensor or the rear ID sensor. 8 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7614
• Description: ID sensor density error Y
• Causes: The density of the Y-patch on the primary transfer belt is faulty at the Calibration or Color Adjustment.
• Remedy: 1 Resetting the main power The ID sensor does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 3 Cleaning the ID sensor The ID sensor is dirty. Clean the surface of the front and rear ID sensors. 4 Checking the developer unit and drum unit The developer unit or the drum unit is not properly installed. Reinstall developer unit Y and drum unit Y. 5 Checking the primary transfer unit The primary transfer belt is dirty. Clean the surface of the primary transfer belt, or replace the primary transfer unit. 6 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Front ID sensor and Rear ID sensor — Engine PWB (YC7) 7 Replacing the ID sensor The ID sensor is faulty. Replace the front ID sensor or the rear ID sensor. 8 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7620
• Description: ID sensor timing error
• Causes: The color registration fails.
• Remedy: 1 Resetting the main power The ID sensor does not operate properly. Turn off the power switch and unplug the power plug. After 5s passes, reconnect the power plug and turn on the power switch. 2 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 3 Cleaning the ID sensor The ID sensor is dirty. Clean the surface of the front and rear ID sensors. 4 Checking the developer unit and drum unit The developer unit or the drum unit is not properly installed. Reinstall the developer unit and drum unit. 5 Checking the primary transfer unit The primary transfer belt is dirty. Clean the surface of the primary transfer belt, or replace the primary transfer unit. 6 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Front ID sensor and Rear ID sensor — Engine PWB (YC7) 7 Replacing the ID sensor The ID sensor is faulty. Replace the front ID sensor or the rear ID sensor. 8 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7800
• Description: Outer thermistor broken
• Causes: The sensor input data is 0.3V or less.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Temperature/humidity sensor — Engine PWB (YC11) 3 Replacing the temperature/ humidity sensor The temperature/humidity sensor is faulty. Replace the temperature/humidity sensor. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C7810
• Description: Outer thermistor short-circuited
• Causes: The sensor input data is 3.0V or more.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Temperature/humidity sensor — Engine PWB (YC11) 3 Replacing the temperature/ humidity sensor The temperature/humidity sensor is faulty. Replace the temperature/humidity sensor. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C8030
• Description: DF tray upper limit detection error Object: 500-sheet document finisher
• Causes: The DF tray upper limit sensor on is detected when the DF tray motor is in ascending operation
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DF tray upper limit sensor — DFPWB (CN5) • Paper level sensor 1, 2 — DFPWB (CN6) 2 Replacing the sensor The Dr tray upper limit sensor, paper level sensor 1 or 2 is faulty Replace the DF tray upper limit sensor or paper level sensor. 3 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 4 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8040
• Description: DF belt error Object: 500-sheet document finisher
• Causes: The DF belt sensor on or off cannot be detected when passing the specified time after the DF belt solenoid turns on
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the wire connector terminal and reconnect it. If there is no continuity, replace the wire. • DF belt sensor — DF PWB (CN10) • DF belt solenoid — DF PWB (CN21) 2 Replacing the DF belt sensor DF belt sensor is faulty Replace DF belt sensor 3 Replacing the DF belt solenoid DF belt solenoid is faulty Replace DF belt solenoid 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8140
• Description: Dr tray motor error Object: 500-sheet document finisher
• Causes: During the DF tray motor drive, the DF tray lower limit sensor, paper level sensor 1 and 2 on is not detected within 10s.
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DF tray motor — DF PWB (CN15) • DF tray lower limit sensor — DF PWB (CN5) • Paper level sensor1, 2 — DF PWB (CN6) 2 Replacing the DF tray motor The DF tray motor is faulty. Replace the DF tray motor. 3 Replacing the sensor The DF tray lower limit sensor, paper level sensor 1 or 2 is faulty Replace the DF tray lower limit sensor or paper level sensor. 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8210
• Description: DF staple error Object: 500-sheet document finisher
• Causes: JAM7013 and 7023 was detected twice
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DF staple unit — DF PWB 2 Checking the staple Check if the upper BF registration guide shifts manually, and reattach it if it does not smoothly shift. Check if the lower BF registration guide shifts manually, and reattach it if it does not smoothly shift. 3 Replacing the DF staple unit The DF staple unit is faulty. Replace the DF staple unit. 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8320
• Description: DF adjuster motor 2 error Object: 500-sheet document finisher
• Causes: The DF adjustor sensor 2 on or off cannot be detected when passing the specified time after the DF adjustor motor 2 turns on
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DF adjustor motor 2 — DFPWB (CN18) • DF adjustor sensor 2 — DFPWB (CN7) 2 Replacing DF adjustor motor 2 DF adjustor motor 2 is faulty Replace DF adjustor motor 2 3 Replacing the DF adjustor sensor 2 DF adjustor sensor 2 is faulty Replace DF adjustor sensor 2 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8330
• Description: DF adjuster motor 1error Object: 500-sheet document finisher
• Causes: The DF adjustor sensor 1 on or off cannot be detected when passing the specified time after the DF adjustor motor 1 turns on
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire.• DF adjustor motor 1 — DFPWB(CN18) • DF adjustor sensor 1 — DFPWB(CN7) 2 Replacing DF adjustor motor 1 DF adjustor motor 1 is faulty Replace DF adjustor motor 1 3 Replacing the DF adjustor sensor 1 DF adjustor sensor 1 is faulty Replace DF adjustor sensor 1 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8350
• Description: DF roller motor error Object: 500-sheet document finisher
• Causes: The DF roller sensor on or off cannot be detected when passing the specified time after the DF roller motor turns on
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DF roller motor — DF PWB (CN20) • DF roller sensor — DF PWB (CN11) 2 Replacing the DF roller sensor DF roller sensor is faulty Replace DF roller sensor 3 Replacing the DF roller motor The DF roller motor is faulty Replace DF roller motor 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8360
• Description: DF slide motor error Object: 500-sheet document finisher
• Causes: The DF slide sensor on or off cannot be detected when passing the specified time after the DF slide motor turns on
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DF slide motor — DF PWB(CN14) • DF slide sensor — DF PWB(CN22) 2 Replacing the DF slide sensor The DF slide sensor is faulty. Replace the DF slide sensor 3 Replacing the DF slide motor The DF slide motor is faulty. Replace the DF slide motor 4 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 5 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8460
• Description: EEPROM error Object: 500-sheet document finisher
• Causes: EEPROM read/write is not available
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 2 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB.

• Code: C8800
• Description: Document finisher communication error Object: 500-sheet document finisher
• Causes: The communication error was detected 10 times continuously.
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the wire connector terminal and reconnect it. If there is no continuity, replace the wire. • Engine PWB (YC5) — DF relay PWB (YC2) • DF relay PWB (YC3) — DF PWB (CN1) 2 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 3 Replacing the DF relay PWB The DF relay PWB is faulty Replace the DF relay PWB. 4 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB. 5 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C8830
• Description: Relay conveying unit communication error Object: 500-sheet document finisher + relay conveying unit
• Causes: The communication error was detected 10 times continuously.
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Engine PWB (YC5) — DF relay PWB (YC2) • DF relay PWB (YC4) — BR PWB (YC5) 2 Firmware upgrade The firmware is not the latest version. Upgrade the BR firmware to the latest version. 3 Replacing the BR PWB The BR PWB is faulty. Replace the BR PWB. 4 Replacing the DF relay PWB The DF relay PWB is faulty Replace the DF relay PWB. 5 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 6 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C8990
• Description: Finisher setup error Object: 500-sheet document finisher + relay conveying unit
• Causes: 1. Communication error occurs with either the finisher or relay conveying unit. 2. Communication error occurs while installation of the relay conveying unit is detected
• Remedy: 1 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the wire connector terminal and reconnect it. If there is no continuity, replace the wire. • DF PWB (CN1) — DF relay PWB (YC3) • DF relay PWB (YC4) — BR PWB (YC5) 2 Firmware upgrade The firmware is not the latest version. Upgrade the DP firmware to the latest version. 3 Replacing the DF PWB The DF PWB is faulty. Replace the DF PWB. 4 Replacing the BR PWB The BR PWB is faulty. Replace the BR PWB.

• Code: C9000
• Description: DP communication error Object: Document processor
• Causes: The communication error was detected 10 times continuously.
• Remedy: 1 Firmware upgrade The main unit firmware and the document processor firmware mismatch Upgrade the main unit firmware and the document processor firmware to the latest version. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • DP PWB (YC2) — Engine PWB (YC4) 3 Replacing the DP PWB The DP PWB is faulty. Replace the DP PWB. 4 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: C9060
• Description: DP EEPROM error Object: Document processor
• Causes: The writing data and the reading data into the EEPROM mismatch.
• Remedy: 1 Checking the EEPROM The EEPROM is not properly installed. Reattach the EEPROM on the DP PWB. 2 Replacing the DP PWB The DP PWB is faulty. Replace the DP PWB. 3 Replacing the EEPROM The EEPROM is faulty. Replace the EEPROM on the DP PWB, then execute U411.

• Code: C9180
• Description: DP feed-shift motor error Object: Document processor
• Causes: 1. The DP feed-shift motor home position cannot be detected even driving it for one round. 2. The DP feed-shift motor home position cannot be detected even after retrying the detection for 3 times.
• Remedy: 1 Checking the connection The EEPROM is not properly installed. Reattach the EEPROM on the DP PWB. 2 Replacing the DP feed-shift sensor Replace the DP feed-shift sensor 3 Replacing the DP feed-shift motor Replace the DP feed-shift motor 4 Replacing the DP PWB The DP PWB is faulty. Replace the DP PWB 5 Replacing the engine PWB The EEPROM is faulty. Replace the engine PWB

• Code: F000
• Description: Main unit CPU communication error (Controller — Panel)
• Causes: The panel cannot be detected since the CPU communication between the main PWB and the operation panel main PWB is unavailable.
• Remedy: 1 Resetting the main power The communication between the main PWB and the operation panel main PWB is faulty. Turn off the power switch and pull out the power plug. After passing 5s, reinsert the power plug and turn on the power switch. 2 Checking the connection The connector is not connected properly. Or, the wire or the SATA cable is faulty. Clean the wire, the terminal of SATA cable connector and reconnect them. If there is no continuity, replace the wire. • Main PWB — Operation panel PWB 3 Executing U021 The backup RAM data is faulty. Execute U021 to initialize the backup RAM data. 4 Replacing the main PWB The main PWB is faulty. Replace the main PWB. 5 Replacing the operation panel main PWB The operation panel main PWB is faulty. Replace the panel main PWB.

• Code: F000
• Description: CF000 will be displayed if * notes progress is carried out for a definite period of time with a Welcome screen.The communication fault between Panel-Main boards.Communication fault between Panel Core- Main Core Notes 2
• Causes:
• Remedy: 1) Check the harness of * (between Main board <=>SSD), and the connection state of a connector between Panel<=>Main boards, and perform an operation check. (2) Check contact of a DDR memory (extracting) and perform an operation check. If exchangeable, it will exchange and will perform an operation check. (3) Initialize SSD and perform an operation check. * (4) U021 Controller backup initialization is carried out and an operation check is performed. (5) Exchange a Main board and perform an operation check. (6) Exchange a PanelMain board and perform an operation check. (7) It will get, if USBLOG is obtainable, and contact service headquarters. * : only SSD standard model * Note 2 : Only Dual Core CPU model

• Code: F010
• Description: Program read error
• Causes: Data corruption is detected at the program read
• Remedy: 1 Resetting the main power The communication between the main PWB and the operation panel main PWB is faulty. Turn off the power switch and pull out the power plug. After passing 5s, reinsert the power plug and turn on the power switch. 2 Executing U021 The backup RAM data is faulty. Execute U021 to initialize the backup RAM data. 3 Replacing the main PWB The main PWB is faulty. Replace the main PWB.

• Code: F020
• Description: System memory error (RAM reading/writing error or CPU memory error)
• Causes: The error appears during the reading/writing check of the RAM for the CPU when the main unit starts up.
• Remedy: 1 Resetting the main power The communication between the main PWB and the operation panel main PWB is faulty. Turn off the power switch and pull out the power plug. After passing 5s, reinsert the power plug and turn on the power switch. 2 Executing U021 The backup RAM data is faulty. Execute U021 to initialize the backup RAM data. 3 Checking the main PWB The connector or the FFC is not connected properly. Or, the wire, FFC, the PWB is faulty. Clean the terminal of the connectors on the main PWB, reconnect the connector of the wire, and reconnect the FFC terminal. If the wire or the FFC is faulty, repair or replace them. If not resolved, replace the main PWB.

• Code: F040
• Description: Communication error between the main unit CPU (Communication error between the controller and engine)
• Causes: There is an error in the communication between the main PWB and the engine PWB.
• Remedy: 1 Resetting the main power There is an error in the communication between the main PWB and the engine PWB. Turn off the power switch and pull out the power plug. After passing 5s, reinsert the power plug and turn on the power switch. 2 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the following wire connectors and reconnect the connectors. If there is no continuity, replace the wire. • Engine PWB (YC3) — Main PWB (YC26) 3 Firmware upgrade The firmware is not the latest version. Upgrade the main firmware and the engine firmware to the latest version. 4 Replacing the main PWB The main PWB is faulty. Replace the main PWB. 5 Replacing the engine PWB The engine PWB is faulty. Replace the engine PWB.

• Code: F050
• Description: Engine program error
• Causes: The engine program cannot start up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the engine firmware to the latest version 2 Resetting the main power The engine firmware checksum is faulty. Turn off the power switch and pull out the power plug. After passing 5s, reinsert the power plug and turn on the power switch. 3 Checking the EEPROM The EEPROM is not properly attached. Reattach the EEPROM. 4 Checking the engine PWB The connector or the FFC is not connected properly. Or, the wire, FFC, the PWB is faulty. Clean the terminal of the connectors on the engine PWB, reconnect the connector of the wire, and reconnect the FFC terminal. If the wire or the FFC is faulty, repair or replace it. If not resolved, replace the engine PWB.

• Code: F052
• Description: Panel engine program error
• Causes: The panel program cannot start up.
• Remedy: 1 Firmware upgrade The firmware is not the latest version. Upgrade the panel firmware to the latest version. 2 Resetting the main power The panel RAM checksum is faulty. Turn off the power switch and pull out the power plug. After passing 5s, reinsert the power plug and turn on the power switch. 3 Checking the connection The connector is not connected properly, or the wire is faulty. Clean the terminal of the connectors on the operation panel PWB, reconnect the connector of the wire. If there is no continuity, replace the wire. 4 Replacing the operation panel main PWB The operation panel main PWB is faulty. Replace the panel main PWB.

• Code: F12X
• Description: Abnormality detecting in a Scan control section
• Causes:
• Remedy: (1) Check the harness between Scan/DP<=>Main boards, and the connection state of a connector, and perform an operation check. (2) Initialize HDD and perform an operation check. * (3) U021 Controller backup initialization is carried out and an operation check is performed. (4) Exchange a Scan/DP board and perform an operation check. (5) Exchange a Main board and perform an operation check. (6) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F14X
• Description: Abnormality detecting in a FAX control part
• Causes:
• Remedy: (1) Check the harness between FAX<=>Main boards, and the connection state of a connector, and perform an operation check. (2) Initialize SSD and perform an operation check. * (3) U021 Controller backup initialization is carried out and an operation check is performed. (4) Perform a deed operation check for DIMM Clear by U671. * Notes(Since it disappears when received data remain, cautions are required.) (5) Exchange FAX_DIMM and perform an operation check. * Notes (6) Exchange a FAX board and perform an operation check. (7) Exchange a Main board and perform an operation check. (8) Get USBLOG and contact service headquarters. * Only SSD standard model * Note Only model which has Flash for FAX data in a Main board

• Code: F15X
• Description: Abnormality detecting in an authentication device control section
• Causes: Authentication device: Card reader etc.
• Remedy: (1) Check the harness between authentication device <=>Main boards, and the connection situation of a connector, and perform an operation check. (2) Initialize SSD and perform an operation check. * (3) Carry out U021 Main backup initialization and perform an operation check. (4) Exchange a Main board and perform an operation check. (5) Exchange SSD and perform an operation check. * (6) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F17X
• Description: Abnormality detecting in a printer data control part
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F18X
• Description: Abnormality detecting in a Video control section
• Causes:
• Remedy: (1) Check the harness between Engine<=>Main boards, and the connection state of a connector, and perform an operation check. (2) Initialize SSD and perform an operation check. * (3) U021 Controller backup initialization is carried out and an operation check is performed. (4) Exchange an Engine board and perform an operation check. (5) Exchange a Main board and perform an operation check. (6) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F1DX
• Description: Abnormality detecting of the image memory Management Department
• Causes: Poor arrangement of F1D4:Random Access Memory(1) Confirmation of U340(2) Initialization of a set point (U021)
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F21X, F22X, F23X
• Description: Abnormality detecting in an image-processing part
• Causes: F248 is the abnormalities of a printer process.In recurring by specific printer data, please give me cooperation at acquisition of capture data and USBLOG.
• Remedy: (1) Check contact of a DDR memory and perform an operation check. (2) Initialize SSD and perform an operation check. * (3) Carry out U021 Main backup initialization and perform an operation check. (4) Exchange a Main board and perform an operation check. (5) Exchange SSD and perform an operation check. * (6) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F24X
• Description: Abnormality detecting in the system Management Department
• Causes: F248 is the abnormalities of a printer process.In recurring by specific printer data, please give me cooperation at acquisition of capture data and USBLOG.
• Remedy: (1) Check contact of a DDR memory and perform an operation check. (2) Initialize SSD and perform an operation check. * (3) Carry out U021 Main backup initialization and perform an operation check. (4) Exchange a Main board and perform an operation check. (5) Exchange SSD and perform an operation check.* (6) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F25X
• Description: Abnormality detecting in a network management department
• Causes: It may occur according to a visitor’s network environment.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Get USBLOG and packet capture and contact service headquarters. * Only SSD standard model

• Code: F26X … F2AX
• Description: Abnormality detecting in the system Management Department
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard mode

• Code: F2BX … F32X
• Description: Abnormality detecting in a network control part
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. 4) Get USBLOG and contact service headquarters. (Depending on an analysis result, it is packet capture acquisition) * Only SSD standard model

• Code: F33X
• Description: Abnormality detecting in the Scan Management Department
• Causes:
• Remedy: (1) Check the harness between Scan/DP<=>Main boards, and the connection state of a connector, and perform an operation check. (2) Initialize SSD and perform an operation check. * (3) U021 Controller backup initialization is carried out and an operation check is performed. (4) Exchange a Scan/DP board and perform an operation check. (5) Exchange a Main board and perform an operation check. (6) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F34X
• Description: Abnormality detecting in the Panel Management Department
• Causes:
• Remedy: (1) Check the harness between Panel<=>Main boards, and the connection state of a connector, and perform an operation check. * Notes (2) Initialize SSD and perform an operation check. * (3) U021 Controller backup initialization is carried out and an operation check is performed. (4) Exchange a Panel board and perform an operation check. * Notes (5) Exchange a Main board and perform an operation check. (6) Get USBLOG and contact service headquarters. * Only SSD standard model * Note : A Dual Core CPU model and HyPAS model

• Code: F35X
• Description: Abnormality detecting in the printing controlling Management Department
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F37X
• Description: Abnormality detecting in the FAX Management Department
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Perform a deed operation check for DIMM Clear by U671.(Since it disappears when received data remain, cautions are required.) * notes (4) Exchange FAX_DIMM and perform an operation check. * Notes (5) Exchange a Main board and perform an operation check. (6) Exchange SSD and perform an operation check. * (7) Get USBLOG and contact service headquarters. * Only SSD standard model * Note Only model which has Flash for FAX data in a Main board

• Code: F38X
• Description: Abnormality detecting in the authentication authorized Management Department
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F3AX … F45X
• Description: Abnormality detecting in the Entity Management Department
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F46X
• Description: Abnormality detecting of a printer rendering part
• Causes: F46F is the abnormalities of a printer process.In recurring by specific printer data, please give me cooperation at acquisition of capture data and USBLOG.
• Remedy: (1) Exchange boards and perform an operation check. (2) the acquisition wish of USBLOG — carry out(Depending on the (2) case, it is print capture data acquisition) * Only SSD standard model

• Code: F47X
• Description: Abnormality detecting of an image editing processing part
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F4DX
• Description: Abnormality detecting in the Entity Management Department
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F50X
• Description: Abnormality detecting in the FAX Management Department
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F52X … F57X
• Description: Abnormality detecting in a JOB execution part
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F63X
• Description: Abnormality detecting in a device control section
• Causes:
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F68X
• Description: Abnormality detecting in a storage device control section
• Causes: F684 is the overwrite error at the time of an SSD security kit.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F80X
• Description: Abnormality detecting in the Data Access Platform Service
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F90X
• Description: Abnormality detecting in the extension application service part
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F93X
• Description: Abnormality detecting in the extension application management part
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: F9FX
• Description: Abnormality detecting in the extension application various service part
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FC0X
• Description: Abnormality detecting in system application
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FC5X
• Description: Abnormality detecting in Copy application
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FCAX
• Description: Abnormality detecting in Print application
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FCFX
• Description: Abnormality detecting in Send application
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FD4X
• Description: Abnormality detecting in Box application
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FD9X
• Description: Abnormality detecting in FAX application
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FE3X
• Description: Abnormality detecting in a authentication/ authorization part
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FF5X
• Description: Abnormality detecting in the Application Entity Management Department
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard model

• Code: FF7X
• Description: Abnormality detecting in a report creation part
• Causes: Since the USB log immediately after occurrence is needed for analysis, please give me cooperation of acquisition.
• Remedy: (1) Initialize SSD and perform an operation check. * (2) Carry out U021 Main backup initialization and perform an operation check. (3) Exchange a Main board and perform an operation check. (4) Exchange SSD and perform an operation check. * (5) Get USBLOG and contact service headquarters. * Only SSD standard mode

— Если напряжение питания ниже определенной величины, запись в EEPROM будет выполняться некорректно.
— При пониженном напряжении питания микроконтроллер сам может выполнять команды некорректно.

   Этих повреждений EEPROM данных можно избежать, соблюдая следующие рекомендации:

— Нужно удерживать микроконтроллер AVR в состоянии сброса, если напряжение питания находится ниже нормы. Для этого можно использовать внешние супервизоры питания или встроенный детектор пониженного питания — Brown-out Detector (BOD). Встроенный детектор управляется с помощью fuse битов микроконтроллера — BODEN и BODLEVEL. BODEN — разрешает/запрещает работу детектора, а BODLEVEL — определяет его уровень срабатывания.
   Если сброс микроконтроллера происходит во время процесса записи в EEPROM, то операция записи будет завершена только при достаточном уровне напряжения.

— Также в многие разработчике рекомендуют не использовать 0-ую ячейку EEPROM`a, поскольку именно ее содержимое чаще всего повреждается при снижении питания микроконтроллера.

1. Ожидаем готовности EEPROM, опрашивая бит EEWE регистра EECR.
2. Устанавливаем адрес в регистре EEAR.
3. Записываем байт данных в регистр EEDR.
4. Устанавливаем основной флаг разрешения записи EEMWE регистра EECE
5. Устанавливаем флаг разрешения записи EEWE регистра EECE

   Бит EEWE должен быть установлен в течении 4-ех тактов после установки бита EEMWE. Если этого не произойдет по причине прерываний, то запись в EEPROM не будет произведена. Этого легко избежать, если запретить прерывания перед 4-м шагом, а после 5-го снова разрешить их.

   Однако есть еще один подводный камень. Если прерывание возникло после 1-го, 2-го или 3-го шага, и в прерывании тоже используются операции с EEPROM (чтение или запись), то запись может не состояться, или запишутся не те данные и не туда, потому что содержимое регистров EEAR (адрес) и EEDR (данные) будет изменено.

   Описанное выше касается и процедуры чтения EEPROM.

   Лечить это можно следующими способами:

   — Не использовать операции чтения и записи EEPROM в прерываниях.
   Это особенно касается операции записи, потому что она медленная и выполняется с использованием внутреннего RC генератора. Например, для mega16 в даташите указано, что при записи в EEPROM используется внутренний RC генератор с частотой 1 МГц (независимо от установок fuse битов CKSEL) и время записи составляет 8.5 мс. Для прерывания это очень долго.

   — Запрещать прерывания на время всей процедуры записи (чтения) EEPROM, то есть в самом начале.

   — Сохранять в начале обработчика прерывания содержимое регистров EEAR (адрес) и EEDR (данные), а перед выходом восстанавливать их.

   — Использовать флаги (семафоры) для сигнализации о выполнении работы с EEPROM.
   Перед выполнением записи в основном цикле программы (или задаче, если используется ос) устанавливать программный флаг, а в прерывании (или другой задаче) проверять его.

   EEPROM имеет ограниченный ресурс. Atmel гарантирует, что количество циклов перезаписи EEPROM составляет не меньше 100000. Цифра довольно большая, однако и она может быть достигнута, если записывать в EEPROM часто и на протяжении долгого времени.
   Есть два приема по «увеличению» ресурса EEPROM.
   Первый — простой и состоит в том, чтобы записывать в EEPROM данные, только если они изменили свое значение.

   Переменные, которые объявлены, но не используются, часто удаляются компилятором в процессе оптимизации. Если такие переменные нужны, перед ними следует добавлять ключевое слово volatile.

Один из простых способов повышения надежности хранения данных в EEPROM — это метод мажоритарного резервирования. Суть метода заключается в том, что для хранения данных выделяется нечетное количество ячеек памяти — N. При сохранении данных — запись производится во все выделенные ячейки. При чтении — читаются тоже все, но решение относительно содержимого принимается на основе равенства (N+1)/2 ячеек.

   Рассмотрим пример тройного мажоритарного резервирования байта данных. Для сохранения байта используются три байта EEPROM, а решение о содержимом принимается на основании равенства 2 байтов. Код приведен для компилятора IAR AVR.