Description: DFGATE negate error
The DFGATE signal does not negate within 1 minute after the DFGATE has been asserted.
Causes: • ADF interface cable defective • SBCU defective • Mismatched firmware between the SBCU board and ADF
Code: 197
Description: DFGATE error
The DFGEATE signal has already been asserted at the original scan.
Causes: • ADF interface cable defective • SBCU board defective • Mismatched firmware between the SBCU board and ADF
Code: 198
Description: Memory address error
The IPU board does not receive the memory address from the controller board.
Causes: • Mismatched firmware between the SBCU board and controller board • Controller defective • SBCU defective • IPU board defective
Code: 199
Description: DF scanning finish error
The original does not finish scanning with in 1 minute
Causes: • ADF interface cable defective • SBCU board defective • Mismatched firmware between the SBCU board and ADF
Code: 302
Description: Charge roller error
A charge roller current leak signal is detected.
Causes: • Charge high voltage supply board defective • Connection at PCU loose, disconnected, or damaged
Code: 320
Description: Polygon motor error
• The XSCRDY signal did not activate (go LOW) within 10 sec. after the polygon motor turned on. • The XSCRDY signal did not deactivate (go HIGH) within 3 sec. after the polygon motor turned off. • The polygon motor continued to rotate for the prescribed number of rotations for 200 ms after the XSCRDY signal went HIGH (deactivated). • After the polygon motor turned on, or after the machine detected that the prescribed number of rotations had changed, the XSCRDY signal did not go LOW (active).
Causes: • Polygon motor I/F harness loose, disconnected, or defective • Polygon motor defective • Polygon motor driver defective • SBCU board defective