• Code: 672
• Description: Controller-tooperation panel communication error at startup
• Causes: • Controller stalled • Controller board installed incorrectly • Controller board defective • Operation panel connector loose or defective • The controller is not completely shutdown when you turn the main switch off.

• Code: 680
• Description: BCU/ MUSIC communication error
  After the engine CPU sends a message, the Music CPU does not respond within five seconds three consecutive times.
• Causes: • Toner cartridge memory chip loose connection • Memory chip problem • Memory chip cable wiring problem

• Code: 685
• Description: SBU-IPU communication error
  • During data transfer, a checksum error occurs. • During any operation except initialization, the SBU sends a hardware-reset acknowledgement to the IPU.
• Causes: • Loose connection between SBU and IPU • SBU board defective • IPU board defective • External noise

• Code: 686
• Description: BCU-IPU communication error
  • After the machine is powered on or recovering from the power save mode, timeout occurs during BCU communication. • The break signal is received after the communication is normally established with the BCU. • Timeout occurs while the communication with the BCU is retried after a communication error.
• Causes: • Board connector between BCU and controller loose • Board connector between controller and motherboard loose • Board connector between motherboard and IPU loose • BCU board defective • IPU board defective • Controller board defective • Motherboard defective

• Code: 687
• Description: Memory address command error
  The BCU does not receive a memory address command from the controller 120 seconds after paper is in the position for registration.
• Causes: • Loose connection • Defective controller • Defective BCU

• Code: 690-001
• Description: GAVD communication error
  690-001: Y 690-002: M 690-003: C 690-004: K • The I2C bus device ID is not identified during initialization. • A device-status error occurs during I2C bus communication. • The I2C bus communication is not established due to an error other than a buffer shortage.
• Causes: • Loose connection • Defective BCU • Defective LD controller board

• Code: 692
• Description: GAPCI2C communication error
  • The I2C bus device ID is not identified during initialization. • A device-status error occurs during I2C bus communication. • The I2C bus communication is not established due to an error other than a buffer shortage.
• Causes: • Loose connection • Defective BCU • Defective LD controller board

• Code: 700
• Description: ARDF original pick-up malfunction
  • After the pick-up motor is turned on, the original stopper HP sensor is not activated.
• Causes: • Original stopper HP sensor defective • Pick-up motor defective (not rotating) • Timing belt out of position • ARDF main board defective