• Code: 630
• Description: CSS communication error
  The machine tries to communicate with one of the terminals of a relevant service center. → An error signal returns.
• Causes: • Communication error on the public telephone network (logged only; the machine can still operate)

• Code: 632
• Description: MF accounting device error 1
  The machine sends a data frame. → No normal end signal returns. → This symptom happens three times.
• Causes: • Defective or broken line between machine and device

• Code: 633
• Description: MF accounting device error 2
  The machine is communicating with the accounting device. → The break signal returns.
• Causes: • Defective or broken line between machine and device

• Code: 634
• Description: MF accounting device error 3
  A backup RAM error is reported from the accounting device.
• Causes: • Defective accounting device controller • Defective battery in the accounting device

• Code: 635
• Description: MF accounting device error 4
  A battery voltage error is reported from the accounting device.
• Causes: • Defective accounting device controller • Defective battery in the accounting device

• Code: 640
• Description: Engine-to-controller communication checksum error
  While the BICU and controller are communicating, a checksum error has occurred.
• Causes: • Logged only; the machine can still operate

• Code: 641
• Description: Engine-to-controller response error
  The controller has sent a frame with the RAPI protocol, but the engine does not respond.
• Causes: • Defective controller board • External noise

• Code: 670
• Description: Engine startup error
  Just after the main power is turned on or the machine is recovering from auto off mode, the engine ready signal assertion fails. Just after the main power is turned on, the engine does not respond.
• Causes: • Defective controller board