Phaser 7700 Unlisted Error Codes

Phaser 770 Unlisted Error Codes
01-300 L/H COVER INTERLOCK OPEN

EXPLANATION: When the L/H Cover is open.
Refer to BSD: CH 1.6 Ch 1.8
Procedure
Release the L/H Cover lock and cheat the Interlock Switch with a
screwdriver.
Did the 01-300 display disappear?
Yes No
Return the L/H Cover
Between I/F PWB J536-4 (+) GND (-)
Is the voltage +5VDC?
Yes No
Is the voltage between L/H Cover Interlock Switch J127-A2 (+) GND (-)
+5VDC?
Yes No
Between L/H Cover Interlock Switch J127-B2 (+)GND(-)
Yes No
Use the wire network in Chapter 7, and check the +5VDC circuit up to the
L/H Cover Interlock
Switch J127-B2. (WN 7.3.5 +5VDC-1)
Change the L/H Cover Interlock Switch. (PL2.10)
Check for broken wires or insufficient contact from the L/H Cover
Interlock Switch J127-A2 to I/F PWB J536-4.
Check the contact between I/F PWB and MCU PW; if there is no problem,
change the MCU PWB (PL13.1)
If that doesn’t work, change the I/F PWB. (PL9.1)
Check to confirm that there is no problem with the actuator or the
installation of the switch. Redwood xlate
01-301 L/H Lower Cover Interlock Open

Explanation
The L/H Lower Cover is open.
Refer to BSD: CH 8.2 CH 8.9
Procedure
Execute DC330 [001-302]
Open L/H Low Cover, turn L/H Lower Cover Interlock Sensor on or off with
paper.
Did the display change to H/L?
Yes No
Use an all-purpose permeable sensor FIP and fix the L/H Lower Cover
Interlock Sensor (PL2.3)
Check the installation of the actuator and the cover; if there is no
problem, change the MCU PWB. (PL13.1).
01-302 Front Cover Interlock Open

EXPLANATION
The front cover is open.
Refer to BSD: CH1.6 CH 1.8
Procedure
Remove the front cover, and with a the front cover interlock switch.
Did the 01-302 display disappear?
Yes No
I/F PWB between J536-2(+)GND(-)
Yes No
Front Cover Interlock Switch between J126-B1(+)GND(-)
Yes No
Front Cover Interlock Switch between J126-A1(+)GND(-)
Yes No
L/H Cover Interlock Switch between J127-B1(+)GND(-)
Yes No
L/H Cover Interlock Switch between J127-A1(+)GND(-)
Yes No
Use the wire network in Chapter 7 and check the L/H Cover Interlock
Switch
J127-A1 up to the +24VDC circuit (WN 7.3.11 + 24VDC-1)
Change L/H Cover Interlock Switch (PL2.10)
Check for broken wires or poor contact from L/H Cover Interlock Switch
J127-B1 to Front Cover
Interlock Switch J126-A1.
Change Front Cover Interlock Switch (PL10.1)
Check for broken wires or poor contact from Front Cover Interlock Switch
J126-B1 to I/F PWB J536-2.
Check the connection between I/F PWB and MCU PWB. If there is no
problem, change the MCU PWB (PL13.1)
If that doesn’t work, change the I/F PWB. (PL9.1)
Check to see whether there is a problem with the installation of the
actuator and switch..
01-306 Duplex Cover Interlock Open

EXPLANATION
The duplex cover is open
Refer to BSD: CH10.6 CH10.8
Procedure
Execute DC330 [008-300].
Open the duplex cover, and turn the Duplex Cover Interlock Switch on and
off with a screwdriver.
Does the H/L Display change?
Yes No
Actuate the Duplex Cover Interlock Switch.
Between I/F PWB J533-A9 (+)GND(-)
Is the voltage 0VDC?
Yes No
Between Duplex PWB J540-2 (+)GND(-)
Yes No
Between Duplex Cover Interlock Switch J136-2 (+)GND(-)
Yes No
Using the wire network in Chapter 7, check the DC COM circuits up to the
Duplex Cover
Interlock Switch J136-2. (WN 7.3.10 5VRTN-3)
Between Duplex Cover Interlock Switch J136-1 (+)GND(-)
Yes No
Change the Duplex Cover Interlock Switch ( PL12.2 )
Check for broken wires and poor connections from Duplex PWB J540-2 thru
Duplex Cover Interlock
Switch J136-1
Check for broken wires and poor connections from I/F PWB J533-A9 thru
Duplex PWB J540-2
Check the connection between the I/F PWB and the MCU PWB, and if there
is no problem, change the MCU PWB. (PL13.1)
Check the installation of the cover and the cover actuator, and if there
are no problems, change the MCU PWB. (PL13.1).
03-920 Tray 1 Not in Position

EXPLANATION
Tray 1 is not set
Refer to BSD: CH7.1 CH7.13A
Procedure
Push Tray 1 into the machine.
Between I/F PWB J534-B14 (+) GND (-)
Is the voltage +3.38VDC or above?
Yes No
Check for poor connections between I/F PWB and MCU PWB, and if there are
no problems, change the MCU PWB
(PL13.1)
Pull out Tray 1 and confirm paper size setting.
Is the setting correct?
Yes No
Reset it.
Between Tray 1 Size Sensor J115-2 (+) GND (-)
Yes No
Check for broken wires or poor connections between Tray 1 Size Sensor
J115-1 and I/F PWB J534-B14.
Between Tray 1 Size Sensor J115-1 (+) GND (-)
Is the voltage +3.3VDC?
Yes No
Using the wire network in Chapter 7, check the +3.3VDC circuits up to
Tray 1 Size Sensor J115-1. (WN 7.3.3 + 3.3VDC)
Between Tray 1 Size Sensor J115-1 (+) J115-3 (-)
Yes No
Using the wire network from Chapter 7, check the DC COM circuits up to the Tray 1 Size Sensor J115-3
(WN 7.3.3
+ 3.3VDC)
Check the installation of the sensor, and if there is no problem, change the Tray Size Sensor (PL2.1).

EXPLANATION
Tray 2 is not set
Procedure
Between Tray Module PWB J546-8 (IT: J546-8 , 3T: J546-8 , TT: J546-8 )
(+) GND (-)
Yes No
Change the Tray Module PWB (PL14.5 / PL15.5 / PL16.13 )
Yes No
Reset it.
Between Tray 2 Size Sensor J816-2 (3T: J816-2 ,TT: J816-2 ) (+) GND (-)
Yes No
J816-2 (3T: J816-2, TT: J816-2 ) and Tray Module
PWB J546-8 (IT: J546-8, 3T: J546-8, TT: J546-8 ).
Between Tray 2 Size Sensor (3T: J816-1 , TT: J816-1) (+) GND (-)
Yes No
Using the wire network from Chapter 7, check the +5VDC circuits up to
the Tray 2 Size Sensor J816-1 (3T: J816-1, TT:
J816-1 ). (WN 7.3.6 + 5VDC-2)
Between Tray 2 Size Sensor J816-1 (3T: J816-1 , TT: J816-1 ) (+) J816-3 (3T: J816-3, TT: J816-3) (-)
Yes No
(3T: J816-
3, TT: J816-3 ) (WN 7.3.8 + 5DC)
Check the installation of the sensor, and if there is no problem, change the Tray Size Sensor (PL14.1 /
PL15.1 / PL16.1)

EXPLANATION
Tray 3 is not set.
Procedure
Between Tray Module PWB J548-11 (IT: J548-11 , 3T: J548-11 , TT: J548-11
) (+) GND (-)
Yes No
Change the Tray Module PWB (PL15.5 / PL16.13 )
Pull outTray 3 and confirm paper size setting.
Yes No
Reset it.
Between Tray 3 Size Sensor J820-2 (3T: J820-2 ,TT: J820-2 ) (+) GND (-)
Yes No
J820-2 (3T: J820-2, TT: J820-2 ) and Tray Module
PWB J548-11 (IT: J548-11, 3T: J548-11, TT: J548-11 ).
Between Tray 3 Size Sensor J820-1 (3T: J816-1 , TT: J816-1) (+) GND (-)
Yes No
J820-1 ). (WN 7.3.6 + 5VDC-2)
Yes No
(3T: J820-
3, TT: J820-3 ) (WN 7.3.8 + 5V$TN-1)
PL16.1).

EXPLANATION
Tray 4 is not set
Refer to BSD: CH7.5 CH7.6 CH7.13A
Procedure
Between Tray Module PWB J548-5 (IT: J548-5 , 3T: J548-5 , TT: J548-5 )
(+) GND (-)
Yes No
Change the Tray Module PWB (PL15.5 / PL16.13 )
Yes No
Reset it.
Between Tray 4 Size Sensor J824-2 (IT: J548-2 ,3T: J548-2 ,TT: J548-2 )
(+) GND (-)
Yes No
J824-2 (IT: J548-2 ,3T: J548-2, TT: J548-2 ) and
Tray PWB J548-5 (IT: J548-2, 3T: J548-2, TT: J548-2 ).
Between Tray 4 Size Sensor J824-1 (3T: J824-1 , TT: J824-1) (+) GND (-)
Yes No
J824-1 ). (WN 7.3.6 + 5VDC-2)
Yes No
(3T: J824-
3, TT: J824-3 ) (WN 7.3.8 + 5VRTN-1)
PL16.1).
03-950 Tray 1 No Paper

EXPLANATION
Tray 1 is out of paper.
Refer to BSD: CH7.7 CH7.13B
Procedure
Execute DC330 [007-120] .
Turn the No-Paper Sensor Actuator on/off.
Does the display change?
Yes No
Using the all-purpose permeable defective-sensor FIP, fix the Tray 1 No-
Paper Sensor. (PL2.4)
Change the MCU PWB (PL13.1).

EXPLANATION
Procedure
Execute DC330 [007-121] .
Yes No
Paper Sensor. (PL14.3 / PL15.3 / PL16.7)

EXPLANATION
Procedure
Execute DC330 [007-122] .
Yes No
Paper Sensor. (PL15.5 / PL16.9 )
EXPLANATION
Procedure
Execute DC330 [007-122] .
Yes No
Paper Sensor. (PL15.5 / PL16.9 )
04-340 IOT RAM FAIL

EXPLANATION
The MCU PWB RAM Test was no good.
Refer to BSD: CH3.1A CH3.4
Procedure
If turning the power switch off/on does not fix the problem, change the
MCU PWB. ( PL13.1).
04-341 IOT RAM FAIL

EXPLANATION
MCU PWB malfunction.
Procedure
MCU PWB. ( PL13.1).
04-342 IOT FLASH ROM LIMIT FAIL

EXPLANATION
FLASH ROM malfunction.
Procedure
MCU PWB. ( PL13.1).
04-343 IOT FLASH ROM R/W FAIL

EXPLANATION
FLASH ROM malfunction.
Procedure
MCU PWB. ( PL13.1).
04-344 IOT MICRO PITCH FAIL

EXPLANATION
Micro Pit is not generated within the prescribed time.
Procedure
MCU PWB. ( PL13.1).
04-345 IOT HVPS COMMUNICATION FAIL

EXPLANATION
Communication error between MCU PWB and HVPS Control.
Refer to BSD: CH3.1B CH3.4
Procedure
Between MCU PWB J406-A4 (+) GND (-)
Yes No
Yes No
Check the frame short between MCU PWB J406-A4 and HVPS Control PWB J574-
7, and if there is no problem,
change the MCU PWB. (PL13.1)
Check for broken wires or bad connections between MCU PWB J406-A4 and
HVPS Control PWB J574-7
Cut off the power and check the following.
From HVPS Control PWB J574-5 to MCU PWB J406-A6
From HVPS Control PWB J574-4 to MCU PWB J406-A7
Is any of the resistance values 1 omega or less?
Yes No
Fix broken wires and bad connections.
Is the resistance value between HVPS Control PWB J574-6 and MCU PWB
J406-A5 1 omega or less?
Yes No
Fix broken wires and bad connections.
Change Mcu PWB (PL13.1), and if that doesn’t work, change HVPS Control
PWB. (PL9.1).
04-346 IOT BELT HOME FAIL TOO LONG

EXPLANATION
The IBT Home Sensor does not detect the Home Belt.
Refer to BSD: CH9.15 CH9.16 CH9.27
Procedure
Is there a label indicating Belt Home?
Yes No
Change the IBT Belt (PL5.3 )
Make sure that the Belt Home Label is in the home-sensor-detection
position. (Put paper in the detection position)
Execute DC330 [004-100] .
Does the display read “H”?
Yes No
Yes No
Between I/F PWB J533-87 (+) J533-85 (-)
Yes No
Close the front door, and if the voltage between J533-B7(+) J533-B5 (-)
is not +5VDC, change the MCU
PWB. (PL13.1)
Check for broken wires or bad connections from IBT Home Sensor J121 to
I/F PWB J533, and if there are no
problems, change the IBT Home Sensor. (PL5.4)
Change MCU PWB (PL13.1)
If that doesn’t solve the problem, change I/F PWB. (PL9.1)
Take off the IBT ASSY and execute DC330 [004-002].
Is the IBT Motor rotating?
Yes No
Is the voltage +24 VDC?
Yes No
Using the wire network from Chapter 7, check the +24FDC circuits up to
I/F PWB J530-B11. (WN 7.3.11 +24VDC-1)
Between IBT Motor J208-3 (+) GND (-).
Yes No
Check for broken wires or bad connections between IBT Motor J208-3 and
I/F PWB J530-B11.
Check for broken wires or bad connections between IBT Motor J208 and I/F
PWB J530.
Are there any broken wires or bad connections?
Yes No
Change IBT Motor (PL1.1)
Fix the broken wires or bad connections
Change Mcu PWB (PL13.1), and if that doesn’t work, change I/F PWB.
(PL9.1).
04-347 IOT BELT POSITION FAIL

EXPLANATION
Poorly adjusted IBT Belt Edge.
Procedure
Is the Edge Sensor actuator touching the Belt?
Yes No
Check the installation of the actuator.
Switch the machine on, and between I/F PWB J533-B2 (+) GND (-)
Is the voltage between +3VDC and +1VDC?
Yes No
Between I/F PWB J533-B1 (+) J533-B3 GND (-)
Yes No
is not +5VDC, change the MCU PWB. (PL13.1) Between I/F PWB J533-B2 (+)
GND (-)
Yes No
Is the voltage 0 VDC?
Yes No
Check for broken wires or bad connections from I/F PWB J533 to IBT Edge
Sensor J119, and if there are
no problems, change the IBT Edge Sensor. (PL5.4); if that doesn’t work,
change the Mcu PWB. (PL13.1)
Check for broken wires or bad connections from I/F PWB J533-B2 to IBT
Edge Sensor J119-2
Change the IBT Edge Sensor (PL5.4)
Between I/F PWB J530-B7 (+) GND (-).
04-347 IOT BELT POSITION FAIL (cont)

Did the IBT Steering Motor rotate?
Yes No
Check for broken wires or bad connections from I/F PWB J530 and IBT
Steering Motor J207 .
Yes No
Change the MCU PWB (PL13.1), and if that doesn’t work, change I/F PWB
(PL9.1) and the IBT Steering Motor
(PL13.1).
Fix the broken wires and bad connections
Check the installation of the IBT Belt, and if there is no problem,
change the MCU PWB (PL13.1).
04-348 IOT BELT EDGE SENSOR FAIL

EXPLANATION
Defective IBT Belt Edge Sensor.
Procedure
Yes No
Switch the machine on, and between I/F PWB J533-B2 (+) GND (-)
Yes No
Between I/F PWB J533-B1 (+) J533-B3 GND (-)
Yes No
is not +5VDC, change the MCU PWB. (PL13.1) Between I/F PWB J533-B2 (+)
GND (-)
Yes No
Yes No
change the Mcu PWB. (PL13.1)
Check for broken wires or bad connections from I/F PWB J533-B2 to IBT
Edge Sensor J119-2
Change the IBT Edge Sensor (PL5.4) Between I/F PWB J530-B7 (+) GND (-)
Is thevoltage +24VDC?
Yes No
Using the wire network from Chapter 7, check the +24VDC circuits up to I/F PWB J530-B7. (WN7.3.11
+24VDC-1) Remove the IBT Assy, and execute DC330 [004-001].
Yes No
Check for broken wires or bad connections from I/F PWB J530 and IBT
Steering Motor J207
Yes No
Change the MCU PWB (PL13.1), and if that doesn’t work, change I/F PWB
(PL9.1) and the IBT Steering Motor
(PL13.1).
Fix the broken wires and bad connections
change the MCU PWB (PL13.1
04-358 IOT COMMUNICATION FAIL

EXPLANATION
Bad transmission between ESS – IOT
Procedure
Check the connector of the MCU PWB and ESS PWB, and if there is no
problem, change the MCU PWB (PL13.1); if that doesn’t work, change ESS
PWB. (PL13.1).
04-361 DRUM MOTOR DRIVE FAIL

EXPLANATION
Poor Drum Motor rotation.
Procedure
Remove the Drum ASSY (Y/M/C/K), execute DC330 [004-003].
Does the Drum Motor rotate?
Yes No
Between Drum Motor J210-4 (+) GND (-)
Yes No
Using the wire network from Chapter 7, check the +5VDC circuits up to Drum Motor J210-4. (WN7.3.6
+5VDC-2)
Between Drum Motor J210-6 (+)GND (-)
Yes No
Drum Motor J210-6. (WN7.3.13
+24VDC-3)
Execute DC330 [004-003].
Between Drum Motor J210-1 (+)GND (-)
Yes No
Execute DC330 [004-003].
Between MCU PWB J407-B1 (+) GND (-)
Yes No
Check for broken wires or bad connections from Drum Motor J210-1 to MCU
PWB J407-B1, and if there
are no problems, change the MCU PWB. (PL5.4).
Check for broken wires or bad connections from Drum Motor J210-1 to MCU
PWB J407-Bq
Execute DC330 [004-003].
Between Drum Motor J210-2 (+) GND (-)
Is the frequency between 1KHz and 1.3KHz?
Yes No
Execute DC330 [004-003].
MCU PWB J407-B3 (+) GND (-)
Yes No
Check for frame shorts between Drum Motor J210-3. And MCU PWB J407-B3 ,
and if there are no
problems, change MCU PWB. (PL13.1)
Check for cut wires and bad connections between Drum Motor J210-3. and
MCU PWB J407-B3 .
Change Drum Motor. (PL1.1)
Execute DC330 [004-003].
Yes No
Execute DC330 [004-003].
Drum Motor J210-8 (+) GND (-)
Yes No
Check for cut wires and bad connections between MCU PWB J407-B3 and Drum
Motor J210-3
Change Drum Motor. (PL1.1).
04-362 IOT NVM R/W FAIL

EXPLANATION
MCU PWB NVM R/W is no good.
Procedure
Turn the power switch off/on, and if that doesn’t work, change MCU PWB.
(PL13.1).
04-371 CONTROLLER IOT SYSTEM TIMING FAIL

EXPLANATION
Poor transmission between ESS – IOT.
Procedure
Check the connection of the MCU PWB and ESS PWB connectors, and if there
is no problem, change MCU PWB (PL13.1);
if that doesn’t work, change ESS PWB (PL13.1)
04-414 IBT BELT CLEANER ASSY CHANGE SOON
EXPLANATION
When to change IBT Belt Cleaner.
Refer to BSD: CH9.27A
Procedure
Change the Cleaner ASSY, and if that doesn’t work, change the MCU PWB.
(PL13.1).
04-415 BTR UNIT CHANGE SOON

EXPLANATION
When to change the 2 nd BTR Unit.
Procedure
Change the 2 nd BTR Unit, and if that doesn’t work, change the MCU PWB.
(PL13.1).
04-417 IBT BELT UNIT (1 st BTR) CHANGE SOON

EXPLANATION
When to change the IBT Belt Unit.
Procedure
Change the IBT Belt Unit, and if that doesn’t work, change the MCU PWB.
(PL13.1).
04-420 IBT BELT UNIT (1 st BTR) LIFE END

EXPLANATION
Lifecycle of the IBT Belt Unit.
Procedure
Change the IBT Belt Unit, and if that doesn’t work, change the MCU PWB.
(PL13.1
04-421 IBT BELT CLEANER ASSY LIFE END

EXPLANATION
Lifecycle of the IBT Belt Cleaner ASSY.
Procedure
Change the IBT Belt Cleaner ASSY, and if that doesn’t work, change the
MCU PWB. (PL13.1).
04-605 IOT NVM EMPTY

EXPLANATION
Detects that the NVM of the IOT is empty.
Procedure
Switch the power off/on and if that doesn’t work, change MCU PWB.
(PL13.1).
04-640 BELT WALK FAIL

EXPLANATION
Bad IBT Belt Edge adjustment.
Procedure
Yes No
Turn the power on; between I/F PWB J533-B2 (+)GND (-)
Yes No
Between I/F PWB J533-B1 (+) J533-B3 (-)
Yes No
Check the +5VDC circuits up to I/F PWB J533-B1.
Yes No
Yes No
Check for broken wires or bad connections from I/F PWB J533-B2 to Edge
Sensor J119-2
Change IBT Edge Sensor (PL5.4)
Yes No
I/F PWB J530-B7. (WN7.3.11 24 VDC-1)
Remove IBT ASSY, execute DC330 [004-003]
Yes No.
Check for broken wires or bad connections from I/F PWB J530 to IBT
Steering Motor J207.
Were there any broken wires or bad connections?
Yes No
Change MCU PWB (PL13.1), and if that doesn’t work, change I/F PWB
(PL9.1), and IBT Steering Motor. (PL1.1)
Fix any broken wires or poor connections.
change MCU PWB (PL13.1).
04-641 BELT EDGE LEARN FAIL

EXPLANATION
Procedure
Yes No
Yes No
Yes No
Close the front door; if the voltage between I/F PWB J533-B1 and J533-B3
is not +5VDC, change the MCU PWB.
(PL13.1)
Yes No
Yes No
Sensor J119-2
Yes No
I/F PWB J530-B7. (WN7.3.11 24 VDC-1)
Remove IBT ASSY, execute DC330 [004-003]
Yes No
Yes No
04-642 BELT EDGE CHECK FAIL

EXPLANATION
Procedure
Yes No
Yes No
Yes No
Close the front door; if the voltage between I/F PWB J533-B1 and J533-B3
is not +5VDC, change the MCU PWB.
(PL13.1)
Yes No
Yes No
Sensor J119-2
Yes No
I/F PWB J530-B7. (WN7.3.11 24 VDC-1)
Remove IBT ASSY, execute DC330 [004-003].
Yes No
Yes No
04-650 IOT TIME OUT CYCLE DOWN FAIL

EXPLANATION
Bad PRINT processing continued for over 2 minutes.
Procedure
Check for poor contact between ESS PWB and MCU PWB, and if there are no
problems, change ESS PWB. (PL13.1).
04-908 2 nd BTR UNIT LIFE END

EXPLANATION
Life cycle of the 2 nd BTR Unit.
Procedure
Change the 2 nd BTR Unit, and if that doesn’t work, change MCU PWB.
(PL13.1).
06-372 ROS POLYGON MOTOR FAIL

EXPLANATION
Poor ROS Motor rotation.
Procedure
Execute DC330 [006-031]
Between MCU PWB J400-3 (+) GND (-)
Yes No
Change the MCU PWB. (PL13.1)
Execute DC330 [006-031].
Between ROS ASSY Relay Connector J518-4 (+) GND (-)
Yes No
Check for broken wires or bad connections from ROS ASSY relay connector
J518-4 to MCU PWB J400.
Between ROS ASSY relay connector J518-1 (+) GND (-)
Yes No
Yes No
MCU PWB J400-6. (WN7.3.13 +24
VDC-3)
Check for broken wires or bad connections from MCU PWB J400-6 to ROS
Relay Connector J518-1.
Execute DC330 [006-031].
Between ROS ASSY Relay Connector J518-3 (+) GND (-)
Yes No
Execute DC330 [006-031].
Yes No.
ASSY Relay Connector J518-3, and if there are no problems, change the
MCU PWB. (PL13.1).
ASSY Relay Connector J518-3
Execute DC330 [006-031].
Between ROS Relay Connector J518-5 (+) GND (-)
Yes No
Execute DC330 [006-031].
Yes No
ASSY Relay Connector J518-5,
and if there are no problems, change the MCU PWB. (PL13.1).
ASSY Relay Connector J518-5
Check the harness wiring inside the ROS ASSY and if there is no problem
change the ROS ASSY (PL3.1).
06-380 ROS SOS LENGTH FAIL Y

EXPLANATION
The interval [Translator’s Note: “ spacing” ?] of the ROS SOS (Y) signal
exceeds the specified value.
Procedure
Execute DC330 [006-031].
Does the ROS Motor make a rotating sound?
Yes No
Proceed to 06-372 FIP
Check for severed lines, poor contact between SOS PWB (Y) J516 and MCU
PWB J401, and if there is no problem, change ROS
ASSY. (PL3.1).
06-381 ROS SOS LENGTH FAIL Y

EXPLANATION
The interval [Translator’s Note: “ spacing” ?] of the ROS SOS (Y) signal
Procedure
Execute DC330 [006-031].
Yes No
Check for severed lines, poor contact between SOS PWB (M) J517 and MCU
PWB J401, and if there is no problem, change ROS ASSY. (PL3.1).
06-382 ROS SOS LENGTH FAIL C

EXPLANATION
The interval [Translator’s Note: “ spacing” ?] of the ROS SOS (C) signal
Procedure
Execute DC330 [006-031].
Yes No
Check for severed lines, poor contact between SOS PWB (C) J514 and MCU
06-383 ROS SOS LENGTH FAIL K

EXPLANATION
The interval [Translator’s Note: “ spacing” ?] of the ROS SOS (K) signal
Procedure
Execute DC330 [006-031].
Yes No
Check for severed lines, poor contact between SOS PWB (K) J515 and MCU
06-385 ROS ASIC FAIL

EXPLANATION
The MCU PWB’s ROS ASIC movement is bad.
Procedure
Turn the power off/on, and if that doesn’t fix the problem, change MCU
PWB. (PL3.1).
07-104 TRAY 1 FEED OUT SENSOR ON JAM (FROM TAKE AWAY SENSOR)
EXPLANATION
The Tray 1 Feed Out Sensor does not detect the presence of paper even
after the specified amount of time has passed since
The Take Away Sensor On.
DC330 code to check.
[08-100] Tray 1 Feed Out Sensor
[08-106] Take Away Sensor
[08-013 to 08-020] Take Away Motor 1 (1TM)
[08-029 to 08-036] Take Away Motor 1 (TTM)
Items to check:
Malfunction of Take Away Motor 1
Malfunction of Tray 1 Feed Out Sensor
Wear, poor rotation of Take Away Roll 2
Poor advancementt of paper due to foreign objects in the paper path,
or the presence of “ flash,” etc.
Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )
Defective I/F PWB, MCU PWB, ESS PWB.
07-105 TRAY 1 MISFEED

EXPLANATION
Tray 1 Feed Out Sensor does not detect the presence of paper even after
the specified amount of time has passed since
feeding began from Tray 1.
[08-001] Tray 1 Feed/Liftup Motor (Feed)
Items to check:
Malfunction of Tray 1 Feed/Liftup Motor
Wear, poor rotation of Tray 1 Feed Roll and Tray 1 Nudger Roll
Poor advancement of paper due to foreign objects in the paper path, or
the presence of “ flash,” etc.
Defective I/F PWB, MCU PWB, ESS PWB.

EXPLANATION
The Take Away Sensor does not detect the presence of paper even after
the specified amount of time has passed since feeding
began from Tray 2.
[08-106] Take Away Sensor
[08-029 to 08-036] Take Away Motor 1 (TTM)
Items to check:
Malfunction of Take Away Sensor
Wear, poor rotation of Tray 2 feed Roll, Tray 2 Nudger Roll.
Defective Tray Module PWB, MCU PWB, ESS PWB

EXPLANATION
Items to check:
Wear, poor rotation of Tray 3 Feed Roll, Tray 3 Nudger Roll.
Defective Tray Module PWB, MCU PWB, ESS PWB.
07-117 TRAY 3 MISFEED (3TM)

EXPLANATION
Items to check:
07-119 TRAY 4 MISFEED (TTM)
EXPLANATION
Items to check:
07-120 TRAY 4 MISFEED (3TM)

EXPLANATION
Items to check:
07-122 TRAY 4 FEED JAM (TTM)

EXPLANATION
The Tray 4 Feed Out Sensor does not detect the presence of paper when
Tray 4 is pulled out in the middle of a job.
Items to check:
07-250 TRAY COMMUNICATION FAIL

EXPLANATION
Poor transmission [communication?] between the Tray Module PWB and MCU
PWB.
Refer to BSD: CH1.4 CH1.5 CH3.1B CH3.4
Procedure
Between Tray Module PWB J555-1 (IT: J555-1, 3T: J555-1, TT: J555-1) (+)
GND (-)
Yes No
Using the wire network from Chapter 7, check the +5VDC circuits to Tray
Module PWB J555-1 (IT: J555-1, 3T: J555-1, TT:
J555-1 ). (WN 7.3.6 +5VDC-2)
Between Tray Module PWB J555-3 (IT: J555-3, 3T: J555-3, TT: J555-3) (+)
GND (-)
Yes No
Module PWB J555-3 (IT: J555-3, 3T: J555-3,
TT: J555-3 ). (WN 7.3.13 +24VDC-3)
Turn off the power. Check the following:
From MCU PWB J407-B10 to Tray Module PWB J541-7 (IT: J541-7, 3T: J541-7,
TT: J541-7)
TT: J541-9)
TT: J541-5)
TT: J541-4)
Are all of the resistances 1 omega or less?
Yes No
Check for broken wires or bad contacts on wires that are not 1 omega or
less.
Change the following parts in order:
Tray Module PWB (PL14.5 / PL15.9 / PL16.15 )
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-270 TRAY 1 PAPER SIZE SENSOR BROKEN

EXPLANATION
An abnormal AD value was detected from the Tray 1 Paper Size Sensor.
Procedure
Set Tray 1 in the machine.
Is the I/F PWB J534-B14 (+) GND (-) voltage the same as that in the Tray 1 Paper Size Sensor
Output Table inscribed in BSD:
CH7.1?
Yes No
Between Tray 1 Paper Size Sensor J115-2 (+) GND (-)
Is the voltage the same as that in the Tray 1 Size Sensor Output Table inscribed in BSD: CH7.1?
Yes No
Between Tray 1 Size Sensor J115-2 (+) J115-3 (-)
Yes No
Using the wire network from Chapter 7, check the 3.3VDC circuits to Tray
1 Paper Size Sensor. (WN 7.3.3
+3.3VDC)
Check for malfunctioning paper guide, poor contact caused by bending in
the projection that pushes the switch, and
if there is no problem, change the Tray 1 Paper Size Sensor.
Check for cut wires, poor connections from Tray 1 Paper Size Sensor
J115-2 to I/F PWB J534-B14 .
I/F PWB (PL9.1)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-271 TRAY 2 PAPER SIZE SENSOR BROKEN

EXPLANATION
Procedure
Between Tray Module PWB J546-8 (IT: J546-8 , 3T: J546-8 , TT: J546-8)
Is the voltage the same as that in the Tray 2 Paper Size Sensor Output Table inscribed in BSD:
CH7.2?
Yes No
Between Tray 2 Paper Size Sensor J816-2 (3T: J816-2 TT: J816-2 ) (+) GND
(-)
Yes No
Between Tray 2 Paper Size Sensor J816-1 (3T: J816-1 TT: J816-1 ) (+)
J816-3 (3T: J816-3 TT: J816-3)
Yes No
Using the wire network from Chapter 7, check the 5VDC circuits to Tray 2
Paper Size Sensor J816-1 (3T:
J816-1 TT: J816-1 ).
(WN 7.3.3 +5VDC-2)
if there is no problem, change the Tray 2 Paper Size Sensor. (PL14.5 /
PL15.9 / PL16.15 )
Check for cut wires, poor connections between Tray 2 Paper Size Sensor
J816-2 (3T: J816-2 TT: J816-2 ) and Tray Module
PWB J546-8 (1T: J546-8 3T: J546-8, TT: J546-8 )
TRAY MODULE PWB (PL14.5 / PL15.9 / PL16.15 )
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-272 TRAY 3 PAPER SIZE SENSOR BROKEN (3TM)

EXPLANATION
Procedure
Between Tray Module PWB J548-11 (3T: J548-11 , TT: J548-11)
Is the voltage the same as that in the Tray3 Paper Size Sensor Output Table inscribed in BSD:
CH7.3?
Yes No
(-)
Yes No
J820-3 (3T: J820-3 TT: J820-3)
Yes No
3 Paper Size Sensor J820-1
(3T: J820-1 TT: J820-1 ).
(WN 7.3.6 +5VDC-2)
if there is no problem, change the Tray 3 Paper Size Sensor. (PL15.1)
PWB J548-11 (3T: J548-11, TT: J548-11)
TRAY MODULE PWB (PL15.9)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-273 TRAY 4 PAPER SIZE SENSOR BROKEN (3TM)
EXPLANATION
Procedure
Between Tray Module PWB J548-5 (3T: J548-5 , TT: J548-5 ) (+) GND (-)
CH7.5?
Yes No
(-)
Yes No
J824-3 (3T: J824-3 TT: J824-3)
Yes No
(3T: J824-1 TT: J824-1 ).
(WN 7.3.6 +5VDC-2)
PWB J548-5 (3T: J548-5 TT: J548-5)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-274 MSI PAPER SIZE SENSOR BROKEN

EXPLANATION
The Connector for MSI Paper Size Sensor is off.
Procedure
Check for poor contact, cut wires, and displacement of the connector
from the MSI Paper Size Sensor to the base, and if there
are no problems, succesively change I/F PWB (PL9.1), MCU PWB (PL13.1),
ESS PWB (PL13.1)..
07-276 TRAY 3 PAPER SIZE SENSOR BROKEN (TTM)

EXPLANATION
Procedure
Between Tray Module PWB J548-11 (3T: J548-11 , TT: J548-11) (+) GND (-)
CH7.4?
Yes No
(-)
Yes No
Between Tray 3 Paper Size Sensor J820-1 (3T: J820-1 TT: J820-1 )
(+)J820-3 (3T: J820-3 TT: J820-3) (-)
Yes No
(3T: J820-1 TT: J820-1 ).
(WN 7.3.6 +5VDC-2)
PWB J548-11 (3T: J548-11, TT: J548-11)
Change the following parts successively:
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-277 TRAY 4 PAPER SIZE SENSOR BROKEN (TTM)

EXPLANATION
Procedure
Between Tray Module PWB J548-5 (3T: J548-5 , TT: J548-5) (+) GND (-)
CH7.6?
Yes No
GND (-)
Yes No
Between Tray 4 Paper Size Sensor J824-1 (3T: J824-1 TT: J824-1 )
(+)J824-3 (3T: J824-3 TT: J824-3) (-)
Yes No
(3T: J824-1 TT: J824-1 ).
(WN 7.3.6 +5VDC-2)
PWB J548-5 (3T: J548-5, TT: J548-5)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-281 TRAY 1 LIFT UP FAIL

EXPLANATION
The Tray 1 Level Sensor does not come on (shade) with in the prescribed
time from lift up.
Procedure
Set Tray 1. Execute DC330 [08-002].
Does Tray 1’s Bottom Plate lift up?
Yes No
When executing DC330 [08-002], does the Tray 1 Feed/Liftup Motor attempt to rotate?
Yes No
Between Tray 1 Feed/Lift Up Motor J205-3 , 4 (+) GND (-)
Yes No
Using the wire network from Chapter 7, check the +24VDC circuits to the
Tray 1 Feed/LiftUp Motor J205-3,
4. (WN 7.3.11 +24VDC-1)
Turn off the power.
Check the following:
From Tray 1 Feed/Liftup Motor J205-1 to I/F PWB J535-B6.
From Tray 1 Feed/Liftup Motor J205-6 to I/F PWB J535-B1
Are all of the resistances 1 or below?
Yes No
Check for severed lines or poor contact in wires not 1 or below.
Change Tray 1 Feed/Liftup Motor (PL2.4), I/F PWB (PL9.1), and MCU PWB
(PL13.1) successively.
Check the following moving parts:
Turn the gear to the rear of Tray 1 with your hand. Does the bottom
plate rise and fall smoothly?
Push Tray 1 carefully. Does the moving-transmission part [Translator’s
Note: unclear] fit smoothly?
Execute DC330 [07-116]. Pull out Tray 1, turn Tray 1 Level Sensor
on/off..
Does the display change to H/L?
Yes No
Using a Poor-Permeability-Sensing FIP, fix the Tray 1 Level Sensor.
(PL2.4)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-282 TRAY 2 LIFT UP FAIL

EXPLANATION
time from lift up.
Procedure
Yes No
Yes No
Between Tray 2 Feed/Lift Up Motor J205-3 , 4 (3T: J827-3, 4, TT: J827-3,
4) (+) GND (-)
Yes No
Tray 2 Feed/LiftUp Motor J827-3,4
(3T: J827-3, 4, TT: J827-3, 4) . (WN 7.3.13 +24VDC-3)
Turn off the power.
From Tray 2 Feed/Liftup Motor J827-1 (3T: J827-1, TT: J827-1) to Tray
Module PWB J547-6 (1T:
J547-6,3T: J547-6, TT: J547-6).
J547-5,3T: J547-5, TT: J547-5).
J547-2,3T: J547-2, TT: J547-2).
J547-1,3T: J547-1, TT: J547-1).
Yes No
Change Tray 2 Feed/Liftup Motor (PL14.3 / PL15.3 / PL16.7), and Tray
Module PWB (PL14.5 / PL15.9 / PL16.15)
successively.
plate rise and fall smoothly?.
Note: unclear] fit smoothly?
Execute DC330 [07-117]. Pull out Tray 2, turn Tray 2 Level Sensor
on/off.
Yes No
(PL14.3 / PL15.3 / PL16.7)
TRAY MODULE PWB (PL14.5 / PL15.9 / PL16.15)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-283 TRAY 3 LIFT UP FAIL (3TM)

EXPLANATION
time from lift up.
Procedure
Yes No
Yes No
Between Tray 3 Feed/Lift Up Motor J828-3 ,4 (3T: J828-3, 4, TT: J828-3,
4) (+) GND (-)
Yes No
(3T: J828-3, 4, TT: J828-3, 4) . (WN 7.3.13 +24VDC-3)
Turn off the power.
Module PWB J549-B6 (3T:
J549-B6, TT: J547-6).
J549-B5, TT: J549-B5).
J549-B2, TT: J549-B2).
J549-B1, TT: J549-B1).
Yes No
Change Tray 3 Feed/Liftup Motor (PL15.5), and Tray Module PWB (PL15.9)
successively.
Push Tray 3 carefully. Does the moving-transmission part fit smoothly?.
Execute DC330 [07-118].
Pull out Tray 3, turn Tray 3 Level Sensor on/off.
Yes No
(PL15.5)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-284 TRAY 4 LIFT UP FAIL (3TM)

EXPLANATION
time from lift up.
Procedure
Yes No
Yes No
4) (+) GND (-)
Yes No
(3T: J829-3, 4, TT: J829-3, 4) . (WN 7.3.13 +24VDC-3)
Turn off the power.
Module PWB J549-A6 (3T:
J549-A6, TT: J549-A6).
J549-A5, TT: J549-A5).
J549-A2, TT: J549-A2).
J549-A1, TT: J549-A1).
Yes No
successively.
Note: unclear] fit smoothly?.
Execute DC330 [07-119].
Yes No
(PL15.5)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-291 TRAY 3 LIFT UP FAIL (TTM)
EXPLANATION
time from lift up.
Procedure
Yes No
Yes No
4) (+) GND (-)
Yes No
(3T: J828-3, 4, TT: J828-3, 4) . (WN 7.3.13 +24VDC-3)
Turn off the power.
J549-B6, TT: J549-B6).
From Tray 3 Feed/Liftup Motor J828-2 (3T: J8282, TT: J828-2) to Tray
J549-B5, TT: J549-B5).
J549-B2, TT: J549-B2).
J549-B1, TT: J549-B1).
Yes No
successively.
Execute DC330 [07-118].
Yes No
(PL16.9)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-293 TRAY 4 LIFT UP FAIL (TTM)

EXPLANATION
time from lift up.
Procedure
Yes No
Yes No
4) (+) GND (-)
Yes No
(3T: J829-3, 4, TT: J829-3, 4) . (WN 7.3.13 +24VDC-3)
Turn off the power.
J549-A6, TT: J549-A6).
From Tray 4 Feed/Liftup Motor J829-2 (3T: J8289, TT: J829-2) to Tray
J549-A5, TT: J549-A5).
J549-A2, TT: J549-A2).
J549-A1, TT: J549-A1).
Yes No
successively.
Execute DC330 [07-119].
Yes No
(PL16.11)
MCU PWB (PL13.1)
ESS PWB (PL13.1 ).
07-297 ALL TRAY LIFT UP FAIL

EXPLANATION
None of the Tray Level Sensors comes on within the prescribed time.
Refer to BSD: CH7.7 CH7.8 CH7.9 CH7.10 CH7.13
Procedure
Check the DC122 Shutdown History
Is any of the following generated? : 07-282, 07-283, 07-284, 07-291, 17-293
Yes No
Successively change the following parts:
Tray Module PWB (PL14.5 / PL15.9 / PL16.15 )
MCU PWB (PL13.1)
ESS PWB (PL13.1)
Proceed to the FIP indicated..
07-930 TRAY 1 PAPER SIZE MISMATCH

EXPLANATION
The On/Off button for the Tray 1 Paper Size Sensor is outside of the
size that can be detected.
Procedure
If it is not fixed by changing the size of the paper, execute Procedure
for FIP 07-271..

EXPLANATION
Procedure
If it is not fixed by changing the size of the paper, execute Procedure
for FIP 07-271..

EXPLANATION
Procedure
If it is not fixed by changing the size of the paper, execute the
Procedure for either FIP 07-272. (3TM), or
07-276 (TTM).

EXPLANATION
Procedure
If it is not fixed by changing the size of the paper, execute the
Procedure for either FIP 07-273. (3TM), or
07-277 (TTM).
07-935 JOB CANNOT BE CONTINUED FAIL

EXPLANATION
During automatic tray-change processing time, there is no tray to that
can be changed to, and the job cannot continue.
Procedure
Refer to the Instruction Manual..
07-959 MSI PAPER MISMATCH 1 (WHEN SOMETHING OTHER THAN AN IMARI-

EXCLUSIVE-USE SHEET IS
DETECTED)
EXPLANATION
An Imari-exclusive sheet is not being used.
Are Imari-specific sheets being used?
Is the overhead-projector sheet facing the right way?
Are as-yet-unused overhead-projector sheets set?
Are there any foreign substances by the Sensor Detector position?
Procedure
Block the Paper-Detecting Partfor Overhead Projector Sensor “ R” with
normal paper.
Between I/F PWB J534-A4 (+) GND (-)
Yes No
Using a Reflecting Defective-Sensor FIP, fix Overhead Projector Sensor
“ R.” (PL2.6)
Change the following parts in succession:
I/F PWB (PL9.1)
MCU PWB(PL13.1)
ESS PWB(PL13.1).
07-960 MSI PAPER MISMATCH 2 (WHEN OVERHEAD-PROJECTOR SHEET IS DETECTED

WITH NORMAL OR
THICK PAPER)
EXPLANATION
The UI is set for normal or thick paper, but a sheet made of something
other than paper is detected.
Is the sheet set the same as that selected on the UI?
Are there any foreign substances by the Sensor Detector position?
Procedure
Block the Paper-Detecting Partfor Overhead Projector Sensor “ R” with
normal paper.
Yes No
Using a Reflecting Defective-Sensor FIP, fix Overhead Projector Sensor
“ R.” (PL2.6)
I/F PWB (PL9.1)
MCU PWB(PL13.1)
ESS PWB(PL13.1).
07-969 FULL PAPER STACK FAILT

EXPLANATION
The Full-Paper-Stack Sensor detects a full Face-Down Tray continuously
for10 seconds.
Refer to BSD: CH10.3 CH10.4B CH10.8
Has the paper on top of the Face-Down Tray been eliminated?
Is the Full-Paper-Sack-Sensor Actuator malfunctioning, or are there
any foreign substances within it?
Procedure
Execute DC330 [10-102]. Move the Full-Paper-Stack-Sensor Actuator up and
down.
Yes No
Using a Malfunctioning Permeable Sensor FIP, fix the Full-Paper-Stack
Sensor. (PL2.10 / PL2.11)
I/F PWB (PL9.1)
MCU PWB(PL13.1)
ESS PWB(PL13.1).
08-149 TAKE-AWAY SENSOR ON JAM (FROM 3TM TRAY 3 FEED)

EXPLANATION
The Take-Away Sensor fails to detect paper fed from Tray 3 within the
prescribed period of time.
DC330 Code to check:
[08-106] Take-Away Sensor
[08-021 to 08-028] Take-Away Motor 1 (3TM)
Items to check:
Malfunctioning Take-Away Sensor
Malfunctioning Take-Away Motor 1
Wear, failure to rotate of Take-Away Roll 2
Wear, failure to rotate of take-Away Roll 3
Poor paper advancement due to presence of foreign objects within the
paper path, or the presence of “ flash,” etc.
Use of non-spec. paper (refer to Chapter 6 “ Specs” )
Malfunctioning Tray Module PWB, MCU PWB, ESS PWB.
08-150 TAKE-AWAY SENSOR ON JAM (FROM 3TM TRAY 4 FEED)

EXPLANATION
[08-021 to 08-028] Take-Away Motor 1 (3TM)
Items to check:
08-151 TAKE-AWAY SENSOR ON JAM (FROM TTM TRAY 3 FEED)

EXPLANATION
[08-029 to 08-036] Take-Away Motor 1 (TTM)
Items to check:
08-152 TAKE-AWAY SENSOR ON JAM (FROM TTM TRAY 4 FEED)

EXPLANATION
Items to check:
08-164 POB SENSOR ON JAM

EXPLANATION
The POB Sensor fails to detect paper from the REGI Clutch within the
[09-201] POB Sensor
[04-004] Main Motor
[08-037] REGI Clutch
[09-051] 2 nd BTR Retract Motor (contact)
[09-052] 2 nd BTR Retract Motor (retract)
Items to check:
Is paper wrapped around the IBT?
Poor rotation of 2 nd BTR, damage to the moving-transmission gear
[Translator’s Note: meaning unclear]
Poor contact on 2 nd BTR
Malfunctioning POB Sensor
Wear, failure to rotate of REGI Roll
Malfunctioning REGI Clutch
Malfunctioning I/F PWB, MCU PWB, ESS PWB.
08-175 POB SENSOR ON JAM (FROM MSI FEED)

EXPLANATION
The REGI Sensor fails to detect paper fed from the MSI within the
[08-104] REGI Sensor
[04-004] Main Motor
[07-003] MSI Misfeed Solenoid
Items to check:
Main Motor malfunction
REGI Sensor malfunction
MSI Feed Solenoid malfunction
Wear, failure to rotate of MSI Feed Roll
Wear, failure to rotate of MSI Take-Away Roll
08-176 REGI SENSOR ON JAM (FROM TRAY FEED)

EXPLANATION
The REGI Sensor fails to detect paper fed from each Tray within the
[08-038] Take-Away Clutch
[04-004] Main Motor
Items to check:
Take-Away Clutch malfunction
Malfunctioning I/F PWB, MCU PWB, ESS PWB
08-180 REGI SENSOR ON JAM (FROM DUPLEX FEED)

EXPLANATION
The REGI Sensor fails to detect paper fed from the Duplex Feed within
the prescribed period of time.
[08-009 to 08-012] Duplex Motor
[08-046] Duplex Gate Solenoid
[08-043] Inverter Reverse Clutch
[08-046] Main Motor
Items to check:
Duplex Motor malfunction
Inverter Reverse Clutch malfunction
Duplex Gate Solenoid malfunction
Wear, failure to rotate of Exit Roll, Transport Roll, Wait Roll.
Malfunctioning Duplex PWB, I/F PWB, MCU PWB, ESS PWB.
08-181 REGI SENSOR ON JAM (FROM WAIT SENSOR)

EXPLANATION
The REGI Sensor fails to detect paper fed from the Duplex Wait Sensor
within the prescribed period of time.
[08-105] Duplex Wait Sensor
[08-009 to 08-012] Duplex Motor
Items to check:
Duplex Motor malfunction
Regi Sensor malfunction
Duplex Wait Sensor malfunction
Duplex Gate Solenoid malfunction
Wear, failure to rotate of Transport Roll, Wait Roll.
Malfunctioning Duplex PWB, I/F PWB, MCU PWB, ESS PWB.
08-184 REGI SENSOR OFF JAM

EXPLANATION
The Fuser Exit Switch fails to detect paper fed from the from the Regi
Clutch ON within the prescribed period of time.
[10-101] Fuser Exit Switch
[04-004] Main Motor
[08-037] REGI Clutch
[09-051] 2 nd BTR Retract Motor (contact)
[09-052] 2 nd BTR Retract Motor (retract)
Items to check:
Fuser Exit Switch malfunction
Wear, failure to rotate of Fuser Belt, Heat Roll; damage to Moving-
Parts-Transmission Gear [Translator’s Note: ? ]
2 nd BTR failure to rotate; damage to Moving-Parts-Transmission Gear
[Translator’s Note: ? ]
Insufficient 2 nd BTR contact.
Wear, failure to rotate of REGI Roll.
Malfunction of REGI Clutch
08-620 REGICON TEMP SENSOR FAIL

EXPLANATION
Output of the Enviornment Sensor “ A” exceeds the range of 20-60
degrees.
WARNING
This failure is a hidden failure. Thus, in the custom mode used by the
customer, the generation of a “ FAIL” does not stop the
machine, and the FAIL code is not displayed on the UI, so copy discharge
is possible.
Refer to BSD: Ch9.14 CH9.27E
Procedure
Turn off the power. Check the following wires and look for poor contact.
1. Environment Sensor J255-1 from MCU PWB J404-A13
Is any of the resistance values 1 • or less?
Yes No
Check for severed lines and poor connections in wires of 1 or less.
Remove Environment Sensor J255
Is the resistance betweeen Environment Sensor J255-3 and J255-4 6K to
20K ?
Yes No
Change the Environment Sensor (PL1.3)
Successively change the following parts:
MCU PWB (PL13.1)
ESS PWB (PL13.1).
08-622 REGICON DATA OVERFLOW FAIL (A 1 PATCH-X)

EXPLANATION
When the A-1 Patch is detected, the XSO revised set value for the result
of the calculation (either Y, M or C) exceeds the set
range (0 to 472 on the NVM Value).
WARNING
is possible.
Items to check:
1. After executing the DC685 REGICON Set-up Cycle, was the same FAIL
generated?
2. Is the colorage-related NVM 760-7 to 14, 19 to 26 at a default value?
3. Dirty detectors in MOB Sensor 1 and 2; severed wires, poor contact
between the connectors.
4. Dirty or damaged IBT Belt, Drum
5. Warped frame
6. Bad MCU PWB, ESS PWB, ROS ASSY.
08-623 REGICON DATA OVERFLOW FAIL (A 2 PATCH-Y)

EXPLANATION
When the A-2 Patch is detected, the YSO revised set value for the result
of the calculation (either Y, M or C) exceeds the set
range (0 to 474 on the NVM Value).
WARNING
is possible.
Items to check:
generated?
5. Warped frame
08-624 REGICON SAMPLE BLOCK FAIL (A1 PATCH-REAR)

EXPLANATION
When the A-2 Patch is detected, the MAG revised set value for the result
of the calculation (either Y, M or C) exceeds the
set range (0 to 1432 on the NVM Value).
WARNING
is possible.
Items to check:
generated?
5. Warped frame
08-625 REGICON SAMPLE BLOCK FAIL (A1 PATCH-REAR)

EXPLANATION
When the A-1 (IN) Patch is detected, the prescribed sample block number
was not obtained.
WARNING
is possible.
Items to check:
generated?
5. Warped frame
08-626 REGICON SAMPLE BLOCK FAIL (A1 PATCH-FRONT)

EXPLANATION
When the A-1 (OUT) Patch is detected, the prescribed sample block number
was not obtained.
WARNING
is possible.
Items to check:
generated?
5. Warped frame
08-627 REGICON SAMPLE LATERAL FAIL (A1 PATCH-REAR)

EXPLANATION
When the A-1 (IN) Patch is detected, the principal scanning position of
the CYAN color, which serves as the standard, is
abnormal. (The position of the CYAN pattern’s central point is skewed
more than plus/minus 500 u m.)
WARNING
is possible.
Items to check:
generated?
5. Warped frame
08-628 REGICON SAMPLE LATERAL FAIL (A1 PATCH-FRONT)

EXPLANATION
When the A-1 (OUT) Patch is detected, the principal scanning position of
the CYAN color, which serves as the standard, is
abnormal. (The position of the CYAN pattern’s central point is skewed
more than plus/minus 500 u m.)
WARNING
is possible.
Items to check:
generated?
5. Warped frame
08-629 REGICON SKEW FAIL (A1 PATCH-Y)

EXPLANATION
When the A-1 Patch is detected, the relative skew vis-à-vis the CYAN
color exceeds the prescribed limit.
WARNING
is possible.
Items to check:
1. After executing the DC685 REGICON Set-up Cycle, output the 4C grid
chart from the DC612; is the skew of the colorage within
the prescribed limits?
3. Dirty or damaged IBT Belt
4. Dirty or damaged Drum
5. Warped frame
08-630 REGICON SKEW FAIL (A1 PATCH-M)

EXPLANATION
WARNING
is possible.
Items to check:
5. Warped frame
08-631 REGICON SKEW FAIL (A1 PATCH-K)

EXPLANATION
WARNING
is possible.
Items to check:
5. Warped frame
08-900 STATIC JAM

EXPLANATION
When the power is turned on and all of the interlocks are closed, the
Sensor detects paper on the paper conveyance path.
Items to check:
1. Check to see whether the voltage for the power switch has decreased
2. Check for any severed circuit lines or poor contact between sensors
along the paper-conveyance path and each base.
3. Check for any foreign matter on the paper-conveyance path, and check
for any jammed paper that might have been forgotten
4. Dirty detectors on the Reflexive Sensor, snagged actuators on the
permeable Sensors
5. Defective Tray Module PWB, I/F PWB, MCU PWB, ESS PWB.
009-342 2 nd BTR CONTACT FAIL

EXPLANATION
Contact not completed within prescribed time limit by 2 nd BTR Motor ON.
Refer to BSD: CH9.21A. CH9.27A
Procedure
Execute DC330 [009-200].
Open the Left Cover, turn the 2 nd BTR Retract Sensor on/off with paper.
Does the display change to H/L
Yes No
Using an all-purpose Permeable Sensor FIP, fix the 2 ND BTR Retract
Sensor. (PL2.9)
Close the Left Cover, execute DC330 [009-051] and [009-052].
Is there a rotating noise from the 2
nd
BTR Retract Motor?

Yes No
Yes No
I/F PWB J532-A3. (WN 7.3.13 +24VDC-1)
Check for broken wires, poor contact from I/F PWB J532 thru 2 nd Retract
Motor J216.
Are there any broken wires or poor contacts?
Yes No
Change the 2 nd BTR Retract Motor (PL2.9)
Change the MCU PWB (PL13.1)
If that doesn’t work, change the I/F PWB (PL9.1)
Fix broken wires or poor contacts.
Check the mechanical [?] connection between the motor and shaft as well
as the Sensor actuator; if there are no problems, change the
MCU PWB. (PL13.1 ).
009-343 2 ND BTR RETRACT FAIL

EXPLANATION
Retract not completed within prescribed time limit from 2 nd BTR Motor
ON.
Refer to BSD: CH9.21A. CH9.27A
Procedure
Execute DC330 [009-200].
Open the Left Cover, turn the 2 nd BTR Retract Sensor on/off with paper.
Does the display change to H/L
Yes No
Using an all-purpose Permeable Sensor FIP, fix the 2 ND BTR Retract
Sensor. (PL2.9)
Close the Left Cover, execute DC330 [009-051] and [009-052].
Is there a rotating noise from the 2
nd
BTR Retract Motor?

Yes No
Yes No
I/F PWB J532-A3. (WN 7.3.11 +24VDC-1)
Check for broken wires, poor contact from I/F PWB J532 thru 2 nd Retract
Motor J216.
Are there any broken wires or poor contacts?
Yes No
Change the 2 nd BTR Retract Motor (PL2.9)
Change the MCU PWB (PL13.1)
If that doesn’t work, change the I/F PWB (PL9.1)
Fix broken wires or poor contacts.
Check the mechanical [?] connection between the motor and shaft as well
as the Sensor actuator; if there are no problems, change the
MCU PWB. (PL13.1 ).
009-350 IBT HOME SENSOR FAIL

EXPLANATION
A Home detection signal was generated by the IBT Home Sensor before the
IBT made one rotation.
Refer to BSD: CH9.16. CH9.27A
Procedure
Check the following items:
Pieces of paper or metal in the detection position
Severed wires or poor contact from IBT Home Sensor to I/F PWB
Leak in the HVPS
If there is no problem, change the IBT Home Sensor
If that doesn’t work, change the MCU PWB. (PL13.1 ).
009-351 DRIVE LOGIC FAIL

EXPLANATION
Malfunctioning IBT Belt.
Procedure
Yes No
Turn on the power. Between I/F PWB J533-B2 (+) GND (-)
Yes No
Yes No
Between J533-B2 (+) GND (-)
Yes No
Check for broken lines, poor contact from I/F PWB J533 to IBT Edge
Sensor J119, and if there are no
problems, change the IBT Edge Sensor (PL5.4). If that doesn’t work,
change the MCU PWB. (PL13.1)
Check for broken lines, poor contact from I/F PWB J533-B2 to IBT Edge
Sensor J119-2
Change the IBT Edge Sensor (PL5.4)
Yes No
the I/F PWB J530-B7. (WN 7.3.11 +24VDC-1)
Remove the IBT ASSY and execute DC330 [004-001].
Does the IBT Steering Motor make a revolving sound?
Yes No
Check for broken lines, poor contact from I/F PWB J530 to IBT Steering
Motor J207.
Are there any broken lines or poor contacts?
Yes No
Change the MCU PWB. (PL13.1) and if that doesn’t work, change the I/F
PWB (PL9.1) and change the IBT
Steering Motor. (PL13.1)
Fix any broken lines or poor contacts..
Check the installation of the IBT Belt, and if there are no problems,
change the MCU PWB. (PL13.1).
009-358 FULL TONER SENSOR FAIL

EXPLANATION
Breakdown of the Full Toner Sensor
Refer to BSD: CH9.26 CH9.27E
Procedure
Remove the Full Toner Sensor from the bottle, and execute DC330 [009-
150]
Turn the Full Toner Sensor on/off with paper.
Yes No
Using all-purpose Permeable Sensor FIP, fix the Full Toner Sensor.
(PL4.1)
Check for the presence of toner-stain paper and foreign objects; if
there is no problem, change the MCU PWB. (PL13.1).
009-360 DRUM COMMUNICATION FAIL (Y)

EXPLANATION
Communication with the drum fails.
Procedure
Execute DC330 [009-150]
Yes No
Check the position of the Drum, and check to see whether there are any
broken wires or poor contact between Drum (Y) J151
and MCU PWB J405, and if there are no problems, change Drum (Y). (PL4.1)
Change the MCU PWB. (PL13.1).
009-361 DRUM COMMUNICATION FAIL (M)

EXPLANATION
Communication with the Drum fails.
Procedure
Execute DC330 [009-152]
Yes No
broken wires or poor contact between Drum (M)
J152 and MCU PWB J405, and if there are no problems, change Drum (M).
(PL4.1)
009-362 DRUM COMMUNICATION FAIL (C)

EXPLANATION
Procedure
Execute DC330 [009-153]
Yes No
broken wires or poor contact between Drum (C) J154
and MCU PWB J405, and if there are no problems, change Drum (C). (PL4.1)
009-363 DRUM COMMUNICATION FAIL (K)

EXPLANATION
Procedure
Execute DC330 [009-154]
Yes No
broken wires or poor contact between Drum (K) J153
and MCU PWB J405, and if there are no problems, change Drum (K). (PL4.1)
009-380 ATC SENSOR FAIL (Y)

EXPLANATION
ATC Sensor (Y) failure.
NOTE
In order to resolve this fault, the value for DC131 [752-162] must clear
“ 0” .
Refer to BSD: CH9.3 CH9.27C
Procedure
Execute DC922 Tone Up/Down. (If this cannot be executed, change
DC131[752-123] to 4, then return to the original state after
termination.)
Is the ATC Sensor (Y) Fail judgment OK?
Yes No
Check the position of the ATC Sensor, and check to see whether there are
any broken wires or poor contact between ATC
Sensor P129 and I/F PWB J534, and if there are no problems, change the
ATC Sensor. (PL6.2)
009-381 ATC SENSOR FAIL (M)

EXPLANATION
ATC Sensor (M) failure.
NOTE
“ 0” .
Procedure
termination.)
Is the ATC Sensor (M) Fail judgment OK?
Yes No
ATC Sensor. (PL6.2)
009-382 ATC SENSOR FAIL (C)

EXPLANATION
ATC Sensor (C) failure.
NOTE
“ 0” .
Procedure
termination.)
Yes No
ATC Sensor. (PL6.2)
009-383 ATC SENSOR FAIL (K)

EXPLANATION
ATC Sensor (K) failure.
NOTE
“ 0” .
Procedure
termination.)
Is the ATC Sensor (K) Fail judgment OK?
Yes No
ATC Sensor. (PL6.2)
009-408 WASTE BOTTLE NEAR FULL

EXPLANATION
The Toner Collection Bottle is close to full.
Procedure
Is there any dirt from the toner or are there any foreign objects near the Full Toner Sensor
Actuator?
Yes No
Clean it.
Execute DC330[009-150].
Is H displayed?
Yes No
Using an all-purpose Permeable Sensor FIP, fix the Full-Toner Sensor.
(PL4.1).
009-410 WASTE BOTTLE NEAR FULL

EXPLANATION
Timing for replenishment of yellow toner.
Refer to BSD: CH9.8 CH9.9 CH9.13 CH9.14 CH9.27C
Procedure
Is there toner within the DEVE Unit, evenly distributed?
Yes No
Execute DC330 [009-001].
Does the Dispense Motor (Y) revolve?
Yes No
Using the all-purpose Motor-Doesn’t-Turn FIP, fix the Dispense Motor.
(PL6.1)
Check the toner-supply auger mechanism
Execute DC922 Tone Up/Down.
Yes No
Check the installation of the ATC Sensor and check for broken wires or
poor contact between ATC Sensor P129 and I/F
PWB J534, and if there are no problems, change the ATC Sensor (PL6.2)
Execute the DC934 ADC Output Check.
Is the ADC Sensor Fail judgment OK?
Yes No
Between MCU PWB J406-B8 (+) GND (-).
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Did the ADC Shutter Solenoid function?
Yes No
Yes No
MCU PWB J406-B2. (WN
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Between MCU PWB J406-B3 (+) GND (-)..
Yes No
Check for broken wires or poor contact between MCU PWB J406-B3 to ATC
Sensor Unit J602-3 and if
there are no problems, change the MCU PWB (PL13.1)
Execute DC330 [009-079].
Did the voltage change to 0 momentarily?
Yes No
Check for broken wires or poor contact between MCU PWB J406 to ATC
Sensor Unit J602 and if there are no
problems, change the MOB Sensor ASSY (PL1.3)
Check the installation of the ADC Sensor and check for broken wires or
poor contact between MCU PWB J406 and ADC
Sensor Unit J602 and if there are no problems, change the MOB Sensor
ASSY (PL1.3)
Between DEVE Motor J232-7 (+) GND (-).
Yes No
the DEVE Motor J232-4. (WN 7.3.13 +24VDC-3)
Yes No
Check for broken wires or poor contact between the DEVE Motor J232 and
MCU PWB J407 and if there are no problems, change the
DEVE Motor (PL1.1)
009-411 TONER MAGENTA NEAR EMPTY

EXPLANATION
Timing for replenishment of magenta toner.
Refer to BSD: CH9.8 CH9.10 CH9. 13 CH9.14 CH9.27C
Procedure
Yes No
Execute DC330 [009-002].
Does the Dispense Motor (M) revolve?
Yes No
(PL6.1)
Yes No
Execute the DC934 ATC Output Check.
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
Check for broken wires or poor contact between MCU PWB J406-B1 to ADC
Check for broken wires or poor contact between MCU PWB J406 to ADC
ASSY (PL1.3)
Yes No
Yes No
DEVE Motor (PL1.1)
009-412 TONER CYAN NEAR EMPTY

EXPLANATION
Timing for replenishment of cyan toner.
Procedure
Yes No
Execute DC330 [009-003].
Does the Dispense Motor (C) revolve?
Yes No
(PL6.1)
Is the ATC Sensor (C) Fail judgment OK?
Yes No
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Yes No
Yes No
DEVE Motor (PL1.1)
009-413 TONER BLACK NEAR EMPTY

EXPLANATION
Timing for replenishment of black toner.
Procedure
Yes No
Execute DC330 [009-004].
Does the Dispense Motor (B) revolve?
Yes No
(PL6.1)
Yes No
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Execute DC330 [004-004].
Did the main motor rotate?
Yes No
Between Main Motor J203-4 (+) GND (-)
Yes No
the DEVE Motor J232-4. (WN 7.3.13
+24VDC-3)
Execute DC330 [004-004]
Yes No
Execute DC330 [004-004]
Yes No
Check for broken wires or poor contact between MCU PWB J407-A1 to Main
Motor J203-1 and if there
are no problems, change the MCU PWB (PL13.1)
Motor J203-1.
Execute DC330 [004-004].
Yes No
Execute DC330 [004=004]
Yes No
are no problems, change the MCU PWB (PL13.1)
Motor J203-2.
Change the Main Motor (PL1.1)
Execute DC330 [009-013]
Did the DEVE Clutch (K) function?
Yes No
Using an all-purpose Clutch-Doesn’t-Run FIP, fix the DEVE Clutch.
(PL1.2)
009-428 DRUM CARTRIDGE CHANGE SOON (K)

EXPLANATION:
It is almost time to change the Drum
Procedure
Change Drum (K) (PL4.1), and if that doesn’t work, change MCU PWB
(PL13.1)..
009-429 DRUM CARTRIDGE CHANGE SOON (Y)

EXPLANATION:
It is almost time to change the Drum
Procedure
Change Drum (Y) (PL4.1), and if that doesn’t work, change MCU PWB
(PL13.1)..
009-655 ADC PATCH FAIL (Y)
EXPLANATION
Wrong concentration on ADC Patch (Y)
Refer to BSD: CH9.13 CH9.14 CH9.27D
Procedure
Execute DC934 ADC Output Check.
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
problems, change the MOB Sensor ASSY (PL1.3).
ASSY (PL1.3)
Is there toner in the DEVE Unit, distributed evenly?
Yes No
Execute DC330 [009-001]
Did the Dispense Motor (Y) turn?
Yes No
Using an all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor
(PL6.1)
Check the auger mechanism for toner supply.
Check the IBT Belt for damage, dirtiness, or poor cleaning.
Poor installation of ADC Sensor Unit
ROS Shutter malfunction.
If there is no problem, change the MCU PWB. (PL13.1).
009-657 ADC PATCH FAIL (C)

EXPLANATION
Wrong concentration on ADC Patch (C)
Procedure
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Is there toner in the DEVE Unit, distributed evenly?
Yes No
Execute DC330 [009-003]
Did the Dispense Motor (C) turn?
Yes No
Using an all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor
(PL6.1)
009-660 ENVIRONMENT SENSOR TEMP. FAIL

EXPLANATION
Abnormality detected on Environment Sensor (temperature).
Procedure
From MCU PWB J404-A11 to Environment Sensor J255-3.
Is the resistance value for all of them 1 • or less?
Yes No
Check for severed lines, poor contact.
Remove Environment Sensor J255.
Between P255-3 and P255-4.
Is the resistance value between 6K • and 20K •?
Yes No
009-661 ENVIRONMENT SENSOR HUMIDITY FAIL

EXPLANATION
Abnormality detected on Environment Sensor (humidity).
Procedure
Is the voltage between +0.4VDC and +1.7VDC?
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Turn off the power and check the following:
Are all the resistance values 1 • or less?
Yes No
009-662 LD POWER CONTROL FAIL (Y)

EXPLANATION
The Amount-of-Light Value from the ADC Patch exceeds the stipulated
amount.
Procedure
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3).
poor contact between MCU PWB J406 and ADC Sensor Unit J602 and if there
are no problems, change the MOB Sensor ASSY (PL1.3)
Is the toner in the DEVE Unit distributed evenly?
Yes No
Execute DC330 [009-001]
Did the Dispense Motor (Y) turn?
Yes No
Using the all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor
(PL6.1)
009-663 LD POWER CONTROL FAIL (M)

EXPLANATION
amount.
Procedure
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Yes No
Execute DC330 [009-002]
Did the Dispense Motor (M) turn?
Yes No
(PL6.1)
009-664 LD POWER CONTROL FAIL (C)

EXPLANATION
amount.
Procedure
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3).
Yes No
Execute DC330 [009-003]
Did the Dispense Motor (C) turn?
Yes No
(PL6.1)
009-665 LD POWER CONTROL FAIL (K)

EXPLANATION
amount.
Procedure
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078]
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3).
Yes No
Execute DC330 [009-004]
Did the Dispense Motor (K) turn?
Yes No
(PL6.1)
If there is no problem, change the MCU PWB. (PL13.1)..
009-666 DEVE BIAS CONTROL FAIL (Y)

EXPLANATION
The DEVE BIAS Voltage Adjustment Value exceeds the standard value.
Procedure
Is there a “Drum Change” message showing?
Yes No
Change Drum (PL4.1)
Shut off the power, check the following:
From MCU PWB J404-A11 to Environment Sensor J255-3
Are all of the Resistance Values 1• or less?
Yes No
Between Environment Sensor P255-3 and P255-4.
Is the Resistance value between 6K • and 20K •?
Yes No
Change the Environment Sensor (PL 1.3)
Turn on the power.
Is the voltage between +0.4VDC and 1.7 VDC?
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Switch the power off, and check the following:
Yes No
Check for severed wires, poor contact..
Change Environment Sensor (PL1.3)
Change MCU PWB (PL13.1).
009-667 DEVE BIAS CONTROL FAIL (M)

EXPLANATION
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Between Environment Sensor J255-3 and P255-4.
Is the Resistance Value between 6K . and 20K .?
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
Check for severed wires, poor contact.
009-668 DEVE BIAS CONTROL FAIL (C)

EXPLANATION
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
009-669 DEVE BIAS CONTROL FAIL (K)

EXPLANATION
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
009-670 BCR CONTROL FAIL (Y)

EXPLANATION
The BCR Voltage Adjustment Value exceeds the standard value.
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
009-671 BCR CONTROL FAIL (M)

EXPLANATION
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
009-672 BCR CONTROL FAIL (C)

EXPLANATION
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
Check for severed wires, poor contact..
009-673 BCR CONTROL FAIL (K)

EXPLANATION
Procedure
Yes No
Change Drum (PL4.1)
Yes No
Yes No
Turn on the power.
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Yes No
009-684 ADC SHUTTER FAIL

EXPLANATION
ADC Shutter Malfunction.
Refer to BSD: CH9.14 CH9.27D
Procedure
Execute DC330 [009-078]
Did the ADC Shutter Solenoid operate?
Yes No
Is the voltage between MCU PWB J406-B2 (+) GND (-) +24VDC?
Yes No
Using the wire network from Chapter 7, check the +24 VDC circuits up to
MUC PWB J406-B2.
(WN 7.3.13 +24VDC-3)
Execute 330 [009-078]
Yes No
Check for severed lines, poor contact from MCU PWB J406-B3 to ADC Sensor
Unit J602-3, and if there is no
problem, change MCU PWB (PL13.1)
Execute DC330 [009-079]
Did the voltage change to 0 VDC momentarily?
Yes No
Check for severed lines, poor contact from MCU PWB J406-B1 to ADC Sensor
Unit J602-1, and if there is no
problem, change MCU PWB (PL13.1)
Check for severed lines, poor contact from MCU PWB J406 to ADC Sensor
Unit J602, and if there is no problem, change
MOB Sensor ASSY (PL1.3)
Yes No
009-685 ENVIRONMENT SENSOR TEMP. CONTROL LIMIT FAIL

EXPLANATION
The value from the Environment Sensor (Temp.) exceeeds the control limit
value.
Procedure
Are all of the Resistance Values 1 • or less?
Yes No
Between Environment Sensor J255-3 and J255-4
Is the Resistance Values between 6K • and 20K •?
Yes No
Change Environment Sensor. (PL1.3)
Change MCU PWB. (PL13.1).
009-686 ENVIRONMENT SENSOR HUMIDITY CONTROL LIMIT FAILTT

EXPLANATION
The Environment Sensor (Humidity) value exceeds the control limit value.
Procedure
Is the voltage between +0.4 VDC and +1.7 VDC?
Yes No
Yes No
MCU PWB J404-A13. (WN 7.3.6 +5VDC-2)
Switch off the power, check the following:
Yes No
009-910 DRUM TYPE MISMATCH (Y)

EXPLANATION
The type of drum is not suitable.
Refer to BSD: CH9.2
Procedure
Execute DC330 [009-151].
Is the display “H”?
Yes No
Check the installation of the drum.
Check for severed lines, poor contact from Drum (Y) J151 to MCU PWB
J405., and if there are no problems, change Drum (Y).
(PL4.1)
009-911 DRUM TYPE MISMATCH (M)

EXPLANATION
Refer to BSD: CH9.2
Procedure
Execute DC330 [009-152].
Yes No
Check for severed lines, poor contact from Drum (M) J152 to MCU PWB
J405., and if there are no problems, change Drum (Y).
(PL4.1)
009-912 DRUM TYPE MISMATCH (C)

EXPLANATION
Refer to BSD: CH9.3
Procedure
Execute DC330 [009-153].
Yes No
Check for severed lines, poor contact from Drum (C) J153 to MCU PWB
J405., and if there are no problems, change Drum (C).
(PL4.1)
009-913 DRUM TYPE MISMATCH (K)

EXPLANATION
Refer to BSD: CH9.3
Procedure
Execute DC330 [009-154].
Yes No
Check for severed lines, poor contact from Drum (C) J154 to MCU PWB
J405., and if there are no problems, change Drum (C).
(PL4.1)
009-920 TONER YELLOW EMPTY

EXPLANATION
The yellow toner is empty.
Procedure
Is the toner in the DEVE Unit spread evenly?
Yes No
Execute 330 [009-001].
Is the Dispense Motor (Y) turning?
Yes No
(PL6.1)
Check the tonor-supply auger mechanism.
Yes No
poor contact between ATC Sensor P129 to I/F PWB
J534 and if there are no problems, change the ATC Sensor (PL6.2)
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078].
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
After switching the power off/on, did the DEVE Motor rotate?
Yes No
Yes No
DEVE Motor J232-4. (WN 7.3.13
+24VDC-3)
Is the voltage between DEVE Motor J232-7 (+) GND (-) +5VDC?
Yes No
DEVE Motor J232-7. (WN 7.3.6 +5VDC-2)
Check for broken wires or poor contact between DEVE Motor J232 to MCU
PWB J407 and if there are no problems, change
the DEVE Motor (PL1.1)
009-921 TONER MAGENTA EMPTY

EXPLANATION
The magenta toner is empty.
Procedure
Yes No
Execute 330 [009-002].
Is the Dispense Motor (M) turning?
Yes No
(PL6.1)
Check the toner-supply auger mechanism.
Yes No
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078].
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Yes No
Yes No
+24VDC-3)
Between DEVE Motor J232-7 (+) GND (-)
Yes No
009-922 TONER CYAN EMPTY

EXPLANATION
The magenta toner is empty.
Procedure
Yes No
Execute 330 [009-003].
Is the Dispense Motor (C) turning?
Yes No
(PL6.1)
Is the ATC Sensor (C) Fail judgment OK?
Yes No
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078].
Is the voltage between MCU PWB J406-B3 (+) GND (-). 0VDC?
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Yes No
Yes No
+24VDC-3)
Between DEVE Motor J232-7 (+) GND (-)
Yes No
009-923 TONER BLACK EMPTY
EXPLANATION
The black toner is empty.
Procedure
Yes No
Execute 330 [009-004].
Is the Dispense Motor (B) turning?
Yes No
(PL6.1)
Yes No
Yes No
Yes No
MCU PWB J406-B8. (WN 7.3.6 +5VDC-2)
Execute DC330 [009-078].
Yes No
Yes No
7.3.13 +24VDC-3)
Execute DC330 [009-078].
Is the voltage between MCU PWB J406-B3 (+) GND (-). 0VDC?
Yes No
Execute DC330 [009-079]
Yes No
ASSY (PL1.3)
Execute DC330 [004-004]
Did the Main Motor rotate?
Yes No
Between Main Motor J203-4 (+) GND (-).
Yes No
+24VDC-3)
Execute DC330 [004-004]
Yes No
Execute DC330 [004-004]
Yes No
are no problems, change the MCU PWB(PL13.1)
Motor J203-1
Execute DC330 [004-004]
Between Main Motor J203-2 (+) GND (-).
Yes No
Execute DC330 [004-004]
Yes No
are no problems, change the MCU PWB(PL13.1)
Motor J203-2
Change the Main Motor. (PL1.1)
Execute DC330 [009-013]
Did the DEVE Clutch (K) move?
Yes No
Using the all-purpose Clutch-Doesn’t-Work FIP, fix the DEVE Clutch.
(PL1.2)
009-924 WASTE BOTTLE FULL

EXPLANATION
The toner-collection bottle is full
Procedure
Is there residue from the toner and are there foreign objects near the Full Toner Sensor Actuator?
Yes No
Clean it.
Execute DC330 [009-150].
Does the display read “H”?
Yes No
Using the all-purpose Permeable Sensor FIP, fix the Full-Toner Sensor.
(PL4.1).
009-925 WASTE TONER BOTTLE NOT SET

EXPLANATION
Mis-installation of the Toner-Collection Bottle
Pre-Operation Confirmation
This problem can occur even if the Drum (Y/M/C/K) is improperly
installed, so make sure to confirm the installation of the Drum.
Procedure
Between I/F PWB J536-1 (+) GND (-).
Yes No
Open the front door, cheat the Front-Door I/L Switch
Between Waste-Toner Bottle Interlock SW FS-135 (+) GND (-).
Yes No
Yes No
Yes No
I/F PWB J536-4. (WN
7.3.5 +5VDC-1)
Change I/F PWB. (PL9.1)
Check for broken wires or poor contact between I/F PWB J536-3 to Waste
Toner Bottle Interlock SW FS-135
Between Waste-Toner Bottle Interlock SW FS-134 (+) GND (-).
Yes No
Change Waste-Toner Bottle Interlock SW (PL4.1)
Check for broken wires or poor contact between I/F PWB J536-3 to Waste
Toner Bottle Interlock SW FS-135
Check the connection of the Connector P/J410 (P410 / J410) between I/F
PWB and MCU PWB, and if there are no problems, change
MCU PWB. (PL13.1)
If that doesn’t work, change I/F PWB (PL9.1).
009-926 DRUM CARTRIDGE END OF LIFE (K)

EXPLANATION
Timing for Drum replacement.
Procedure
Replace Drum (K) (PL4.1), and if that doesn’t work, change MCU PWB.
(PL13.1).
009-927 DRUM CARTRIDGE END OF LIFE (C)

EXPLANATION
Procedure
Replace Drum (C) (PL4.1), and if that doesn’t work, change MCU PWB.
(PL13.1).
009-928 DRUM CARTRIDGE END OF LIFE (M)

EXPLANATION
Procedure
Replace Drum (M) (PL4.1), and if that doesn’t work, change MCU PWB.
(PL13.1).
009-929 DRUM CARTRIDGE END OF LIFE (Y)

EXPLANATION
Procedure
Replace Drum (Y) (PL4.1), and if that doesn’t work, change MCU PWB.
(PL13.1).
009-931 DRUM NOT DETECT (M)
EXPLANATION
Drum Detect Data is unsuitable.
Procedure
Switch the power off/on, and if that doesn’t work, change the MCU PWB
(PL13.1), and change the Drum (M). (PL4.1).
009-932 DRUM NOT DETECT (C)

EXPLANATION
Drum Detect Data is unsuitable.
Procedure
Switch the power off/on, and if that doesn’t work, change the MCU PWB
(PL13.1), and change the Drum (C). (PL4.1).
10-125 DUPLEX WAIT SENSOR ON JAM

EXPLANATION
The Wait Sensor does not come on within the prescribed time.
DC330 Code to Check:
[008-105] Duplex Wait Sensor
[008-009] Duplex Motor
[008-046] Duplex Gate Solenoid
Check Items
Malfunctioning Wait Sensor
Wear, poor rotation of Duplex Trance Roll
Wear, poor rotation of Duplex Wait Roll
Malfunctioning Duplex Gate
Poor rotation of Duplex Motor
Malfunctioning Duplex Gate Solenoid
Damage to and wear of Gears
Poor conveyance of paper due to foreign objects in the paper path
Use of non-spec. paper. (Refer to “ Specs” in Chapter 6).
10-348 MAIN HEATER OVERHEAT FAIL

EXPLANATION
The Front Thermistor detects an abnormally high temperature
NOTE
In order to undo this fault, the value for DC131 [744-010] must “ 0”
clear.
Procedure
Turn off the power, remove the Fuser ASSY and allow it to cool
sufficiently.
Between Fuser ASSY Connector P600-4 (+) P600-6 (-)
Measure the Resistance Value.
Is the Resistance Value between 30K• and 190K • ?
Yes No
Check for broken wires or poor contact in the Front Thermistor within
the Fuser ASSY, and if there are no problems, change
the Fuser ASSY. (PL7.1)
Return the Fuser ASSY to its position, turn on the power, and execute
DC140 [010-100].
Is the Monitor Value between 900 and 1000?
Yes No
Turn off the power, check for broken wires or poor contact between MCU
PWB J404-A2 and Front Thermistor J211-1
Are there any broken wires or poor contact?
Yes No
Check for broken wires or poor contact between MCU PWB J404-A1 and Front
Thermistor J211-2
Yes No
Fix broken lines, poor contact.
Measure the voltage.
Is it +5VDC until the occurrence of Fail?
Yes No
Between AC Drive PWB J590-5 (+) GND (-).
Yes No
Change AC Drive PWB (PL9.2)
Check for broken lines, poor contact.
10-349 FRONT THERMISTOR DISCONNECTION

EXPLANATION
Front Thermistor disconnection detected.
Procedure
sufficiently.
Yes No
Check for broken wires or poor contact in the Front Thermistor within
DC140 [010-100].
Yes No
Yes No
Thermistor J211-2
Yes No
10-350 SUB HEATER OVERHEAT FAIL

EXPLANATION
The Rear Thermistor detects an abnormally high temperature
NOTE
In order to undo this fault, the value for DC131 [744-010] must “ 0”
clear.
Procedure
sufficiently.
Yes No
Check for broken wires or poor contact in the Rear Thermistor within the
Fuser ASSY, and if there are no problems, change
DC140 [010-101].
Yes No
Yes No
Thermistor J212-2
Yes No
Yes No
Yes No
Change AC Drive PWB (PL9.2)
Check for broken lines, poor contact.
10-351 REAR THERMISTOR DISCONNECTION

EXPLANATION
sufficiently.
Yes No
Check for disconnection or poor contact in the Front Thermistor within
DC140 [010-101].
Rear Thermistor disconnection detected.
Procedure
Yes No
Turn off the power, check for disconnection or poor contact between MCU
Is there any disconnection or poor contact?
Yes No
Check for disconnection or poor contact between MCU PWB J404-A3 and
Front Thermistor J212-2
Yes No
Fix disconnection, poor contact.
10-352 MAIN HEATER WARMUP FAIL
EXPLANATION
[Main Heater] fails to reach Ready Temperature within the prescribed
time.
Procedure
sufficiently.
Yes No
DC140 [010-100].
Is the Resistance Value 20• or less?
Yes No
Check for disconnection or poor contact in the Wire within the Fuser
ASSY, and check for disconnection of the Thermostat,
and if there are no problems, change the Fuser ASSY. (PL7.1)
Yes No
Yes No
Yes No
Is it 0VDC until the occurrence of Fail?
Yes No
Is it 0 VDC until the occurrence of Fail?
Yes No
Yes No
Using the wire network from Chapter 7, check the DC-COM circuits in the
AC Drive PWB J590-4. (WN
5VRTN-2 5VRTN-2)
Between AC Drive PWB FS48 (+)FS41 (-).
Is the voltage 100VAC?
Yes No
Yes No
Using the wire network from Chapter 7, check the AC circuits up to the
AC Drive PWB FS39,
FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)
Between AC Drive PWB J590-1 (+) GND(-).
Yes No
Using the wire network from Chapter 7, check the +24 circuits up to the
AC Drive PWB J590-1
(WN 7.3.1 +24VDC-3)
Yes No
Between MCU PWB J406-B14 (+) GND(-).
Yes No
Check for disconnection or poor contact between AC Drive PWB J590-2 and
MCU PWB
J406-B14 , and if there are no problems, change MCU PWB (PL13.1)
MCU PWB J406-B14
Change AC Drive PWB. (PL9.2)
Check for disconnection or poor contact between AC Drive PWB FS41 and
FUSER ASSY J600-1 , and between
AC Drive PWB FS48 and FUSER ASSY J600-12
MCU PWB J406-B11
Check for frame short in wire, and if there are no problems, change MCU
PWB. (PL13.1).
10-353 MAIN HEATER ON TIME FAIL

EXPLANATION
The Main Heater [light?] is on for a continuous period that exceeds the
prescribed time
Procedure
sufficiently.
Yes No
Measure the Resistance Value
Yes No
Yes No
Yes No
Yes No
Measure the voltage between MCU PWB J406-B11 (+) GND (-).
Yes No
Yes No
Yes No
7.3.9 5VRTN-2)
Yes No
Yes No
AC Drive PWB FS39,
FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)
Yes No
AC Drive PWB J590-1
(WN 7.3.1 +24VDC-3)
Yes No
Yes No
MCU PWB
MCU PWB J406-B14
MCU PWB J406-B11
PWB. (PL13.1).
10-354 SUB HEATER WARM UP

EXPLANATION
Failed to reach Ready Temperature within the prescribed time.
Procedure
sufficiently.
Yes No
Check for disconnection or poor contact in the Rear Thermistor within
Between Fuser ASSY P600-3 (+) P600-12 (-)
Yes No
Yes No
PWB J404-A4 and Rear Thermistor J212-1
Yes No
Check for disconnection or poor contact between MCU PWB J404-A3 and Rear
Thermistor J211-2
Yes No
Yes No
Yes No
Yes No
7.3.9 5VRTN-2)
Yes No
Yes No
AC Drive PWB FS39,
FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)
Yes No
AC Drive PWB J590-1
(WN 7.3.13 +24VDC-3)
Yes No
Yes No
MCU PWB
MCU PWB J406-B14
MCU PWB J406-B13
PWB. (PL13.1).
10-356 SUB HEATER ON TIME FAIL
EXPLANATION
The Sub Heater [light] is continuously illuminated for more than the
prescribed time.
Procedure
sufficiently.
Yes No
Check for disconnection or poor contact in the Rear Thermistor within
Between Fuser ASSY P600-3 (+) P600-12 (-)
Yes No
Yes No
PWB J404-A4 and Rear Thermistor J212-1
Yes No
Check for disconnection or poor contact between MCU PWB J404-A3 and Rear
Thermistor J211-2
Yes No
Yes No
Yes No
Yes No
7.3.9 5VRTN-2)
Yes No
Yes No
AC Drive PWB FS39,
FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)
Yes No
Using the wire network from Chapter 7, check the +24 VDC circuits up to
the AC Drive PWB
J590-1 (WN 7.3.13 +24VDC-3)
Yes No
Yes No
MCU PWB
MCU PWB J406-B14
MCU PWB J406-B13
Check for frame short in Wire, and if there are no problems, change MCU
PWB. (PL13.1).
10-398 FAN LOCK FAIL

EXPLANATION
Broken Fuser Fan/LVPS Fan
NOTE
Before undertaking the operation, confirm the source of the fail---
either the Fuser Fan or the LVPS Fan.
Refer to BSD: CH1.2 CH10.2 CH10.8
Procedure
Execute DC330 [004-050]
Is the Fuser Fan rotating at a high speed?
Yes No
Between Fuser Fan J222-4 (+) GND (-)
Yes No
Using the wire network from Chapter 7, check the+24VDC circuits up to
the Fuser Fan J222-4. (WN 7.3.12 +24
VDC-2)
Between Fuser Fan P222-4 (+) P222-1 (-)
Yes No
Using the wire network from Chapter 7, check theDC-COM circuits up to
Fuser Fan J222-1. (WN 7.3.14 24
VRTN-1)
Execute DC330 [004-050]
Between Fuser Fan P222-3 (+) GND (-)
Yes No
Execute DC330 [004-050]
Between I/F PWB J530-A2 (+) GND(-).
Yes No
Check for disconnection or poor contact between Fuser Fan J222-3 and I/F
PWB J530-A2 , and check the
connection between MCU PWB and I/F PWB; if there are no problems, change
MCU PWB (PL13.1)
If that doesn’t work, change I/F PWB. (PL9.1)
PWB J530-A2
Change AC Drive PWB. (PL9.2).
Execute DC330 [004-050].
Between Fuser Fan J222-2 (+) GND(-).
Is the voltage +3.3 VDC?
Yes No
Execute DC330 [004-050]
Yes No
Check the connection between MCU PWB and I/F PWB, and if there are no
problems, MCU PWB (PL13.1)
PWB J530-A3.
Change Fuser Fan. (PL8.1)
Execute DC330 [004-050]
Is the LVPS Fan rotating at high speed?
Yes No
Between LVPS Fan J214-4 (+) GND (-)
Yes No
LVPS Fan J214-4. (WN 7.3.12 +24
VDC-2)
Between LVPS Fan J214-4 (+) J214-1.
Yes No
Using the wire network from Chapter 7, check the DC COM circuits up to
LVPS Fan J214-1. (WN 7.3.14
24VRTNC-1)
Execute DC330 [004-050]
Yes No
Execute DC330 [004-050]
Yes No
Check the for disconnection, poor contact between LVPS Fan J214-3 and
I/F PWB J530-A6 and check the
connection between MCU PWB and I/F PWB; if there are no problems, change
MCU PWB (PL13.1).
Check for disconnection or poor contact between LVPS Fan J214-3 and I/F
PWB J530-A6.
Change LVPS Fan (PL9.1)
Execute DC330 [040-050]
Between LVPS Fan J214-2 (+) GND (-)
Yes No
Execute DC330 [040-050]
Yes No
Check connection between MCU PWB and I/F PWB, and if there are no
problems, change MCU PWB (PL13.1)
Check for disconnection or poor contact betweenI/F PWB J530-A7 and LVPS
Fan J214-2.
Change LVPS Fan (PL9.1).
10-420 FUSER ASSY CHANGE SOON

EXPLANATION
The time to change the Fuser ASSY is drawing near.
Refer to BSD: CH10.8
Procedure
Has the Change Button been pushed down?
Yes No
Push the Change Button down.
Execute DC135 [954-804]
Is the initial value 0?
Yes No
After confirming that the LIFE Set Value is 10000, turn the power off/on
If that doesn’t work, change MCU PWB (PL13.1).
10-421 FUSER ASSY END OF LIFE

EXPLANATION
Timing of Fuser ASSY change.
Procedure
Has the Change Button been pushed down?
Yes No
Push the Change Button down.
Execute DC135 [954-804]
Is the initial value 0?
Yes No
After confirming that the LIFE Set Value is 10000, turn the power off/on
If that doesn’t work, change MCU PWB (PL13.1).
03-205 BILLING FAIL 1

[Detection Conditions]
All 3 Billing Counters maintained in 3 different places are different.
[Rectification Method]
Turn power off/on, and if the trouble continues, execute the following:
Execute Measure Diag (DC132), and reconcile the Billing Values. If the
problem continues after executing the measure,
replace ESS PWB (PL13.1).
03-206 BILLING FAIL 2

1 inconsistent Billing Counter cannot be repaired.
Abnormality in ESS PWB SLEEPROM or NVM. Or abnormality in EEPROM MCU
PWB. If it’s not a problem with the
NVM Battery, change ESS PWB (PL13.1) or change MCU PWB. (PL13.1).
03-340 IOT-ESS COMMUNICATION FAIL 1

Error message due to abnormal paramaters set for Transmission Function
Factor.
4. Check the MCU PWB Connection Harness.
5. Software problem. Reinstall software.
6. If the above steps do not rectify the situation, change the MCU PWB
(PL13.1).

Communication Fail occurs because ACK was not received even after 2
attempts to re-transmit. (The “ SequenceNo” value
for the Message Packet of the transmission is not correct.)
(PL13.1).

attempts to re-transmit. (The PacketNo value for the
Message Packet of the transmission is not correct.)
(PL13.1).

attempts to re-transmit. (The value for the message
length of the transmission’s Message Packet is not correct.)
(PL13.1).

attempts to re-transmit. (The Check Code for the
Message Packet of the transmission is not correct.)
(PL13.1).

attempts to re-transmit. (Parity Error was detected on
IOT-side hardware.)
(PL13.1).
attempts to re-transmit. (Framing Error was detected
in IOT-side hardware.)
(PL13.1).

attempts to re-transmit. (Overrun Error was detected
in IOT-side hardware.)
(PL13.1).

attempts to re-transmit. (After Header Recognition
on IOT Side, “ Transmission-Interrupted” was detected.)
(PL13.1).

Occurs when NAK, which notifies of the occurrence of a communication
fail, is received. (The SequenceNo of the Message
Packet received is not a correct value.)
(PL13.1).

fail, is received. (The PacketNo of the Message
(PL13.1).

fail, is received. (The Message Length of the
Message Packet received is not a correct value.)
(PL13.1).

fail, is received. (The Check Code of the Message
(PL13.1).

fail, is received. (A Parity Error was detected in the
hardware that UART itself holds.)
(PL13.1).

fail, is received. (A Framing Error was detected in
the hardware that UART itself holds.)
(PL13.1).

fail, is received. (An Over-run Error was detected
in the hardware that UART itself holds.)
(PL13.1).

fail, is received. (After recognition of Header, a
“ Receive-Interrupted” was detected.)
(PL13.1).

Detection of Paper Feed and Paper Discharge that aren’t NBR-compatible.
(PL13.1).

Error occurring when the Receiving-Function Factor has abnormal
parameters.
(PL13.1).
03-360 IOT-ESS INITIALIZATION FAIL

[Detection Conditions] IOT Driver Initialization Fail.
(PL13.1).
03-362 PAGE SYNC ILLEGAL START

Page Sync is activated before FIFO is written full with Output Data
during IOT Output.
[Rectification Method] At present, this fail is not displayed..
03-363 PAGE SYNC ILLEGAL STOP

Page Sync is negated before IOT Output reaches the designated size.
03-364 DMA TRANSFER FAIL

Occurs when, during compression/decompression of the designated data was
entered, but the compression/expansion does
not terminate.
Turn power off/on, and if the trouble persists, execute the following:
7. Change RAM (PL13.1)
8. Execute DC355 Diag. Diagnosis, and if the trouble persists, change
HDD (PL13.1)
9. ESS PWB (PL13.1).
03-365 OVERFLOW ON LOOP BACK WRITE

Decompressed data exceeds the buffer size that was reserved.
03-366 JBIG Library Other Fail

[Detection Conditions] Not used at present.
Turn power off/on; if the trouble continues, execute the following:
1. ESS PWB (PL13.1).
03-370 Marker Code Defect Fail

Amount decompressed was equal to the designated size, but the
Compression Data Termination Code (FF02) was not found.
Turn power off/on; if the trouble continues, execute the following:
Change RAM (PL13.1)
Execute DC355 Diag Diagnosis, and if the trouble persists, change HDD
(PL13.1)
ESS PWB (PL13.1).
03-600 IMARI: BILLING MASTER COUNTER FIX

[Detection Conditions] The Billing Master Counter was fixed
automatically.
[Rectification Method] Only Registration at History.
03-601 IMARI: BILLING MASTER COUNTER 1 FIX

[Detection Conditions] The Billing Master Counter 1 was fixed
automatically.
03-602 IMARI: BILLING MASTER COUNTER 2 FIX

[Detection Conditions] The Billing Master Counter 2 was fixed
automatically.
03-747 PRINT INSTRUCTION FAIL
[Detection Conditions] The designated print parameters are abnormal.
[Rectification Method] Change print parameters and reprint..
03-954 TRAY SMH EMPTY

[Detection Conditions] No paper detected in paper-feed tray.
Replenish paper. If the trouble continues, refer to All-Purpose Sensor
FIP and check the Sensor..
03-958 SIZE MISMATCH 1 SMH SIZE UNSUITABLE

The paper designated with the print command and the paper in the paper-
feed tray are different.
Set the proper kind of paper..
03-959 SIZE MISMATCH TRAY 1 SIZE UNSUITABLE

The paper designated with the print command and the paper in Tray 1 are
different.
Set the proper kind of paper. If the trouble continues, refer to All-
Purpose Sensor FIP and check the Sensor..

different.

different.

different.
03-965 ATS/APS NO PAPER, APS/ATS NG (NO PAPER)

[Detection Conditions] There is no paper of the type designated with the
print command
03-966 ATS/APS NO DESTINATION ERROR, ATS/APS NG ( EXCLUDING NO PAPER)

[Detection Conditions] No paper of the type designated with the print
command is detected.
Change the setting. If the trouble continues, refer to All-Purpose
Sensor FIP and check the Sensor..
03-985 SMH TEMPORARY STOP CONFIRMATION

[Detection Conditions] Movement of paper from the Paper-Feed Tray stops
due to some problem.
Check the paper size, paper direction and paper type, then push the
Discharge Key..
16-450 DUPLICATE SMB HOST NAME

A PC on the network has a host name has a host name that is already
being used.
Change the host name..
16-452 DUPLICATE IP ADDRESS

A PC on the network has a host namehas an IP address that is already
being used.
Change the IP address..
16-453 OBTAINING IP ADDRESS FROM DHCP SERVER FAILS

Failure to obtain IP address from DHCP server.
Set IP address. (Do not obtain from DHCP server).
16-701 SHORT OF PLW MEMORY

Insufficient memory detected during ART EX usage.
Imari: PLW memroy is fixed; if possible, lower the picture resolution..
16-702 SHORT OF PLW MEMORY

Insufficient memory detected on print-page buffer that couldn’t compress
even one page.
Imari: PLW memroy is fixed; if possible, lower the picture resolution..
16-705 SECURITY STORAGE WITHOUT HD

With no HDD, security storage impossible, causing a failure to register
security print.
Check to see whether HDD is set. If there is trouble in setting HDD,
check to see whether the security print operation is
mistaken..
16-709 PLW COMMAND ERROR

During PLW processing, ART EX command error occurs.
Cancel the job and re-execute..
16-713 DETECT ERROR IN IMAGER

During image processing, an image error occurs.
Data that will cause the error is being used within the print data;
alter or remove this data..
16-721 OTHER ERRORS

During printing, an unanticipated error occurs.
Re-execute the same job, and after confirming the type of error, request
help from Support G
16-726 CANNOT SWITCH DECOMPOSER <AUTOMATIC JUDGMENT ERROR>

Print language automatic judgment error.
Do Fix-Choose on the Decomposer either thru the operating panel or thru
a command..
16-730 ART COMMAND INVALID <ART COMMAND ERROR>

ART IV command error.
Delete non-support command(s) from data, re-print..
16-748 HDD FULL

HD is detected as full when attempting to acces it; job is terminated.
Empty the HDD capacity, execute re-print..
16-749 XJCL SYNTAX ERROR <JCL STRUCTURE ERROR>

Error detected in JCL command structure [architecture?]
Revise the command..
16-760 DECOMPOSE ERROR <PS DECOMPOSE ERROR?>

Error occurs during decompose processing.
Re-transmit the job. (If it re-occurs the execution environment/data
must be checked).
16-761 FIFO EMPTY <IMAGE OUTPUT>

Image Expansion error. (FIFO Empty Error)
Print in speed mode. If it still does not work, print in high-print-
quality mode..
16-762 ECIFIED DECOMPOSER NOT EXIST <DECOMPOSER DOESN’T EXIST>

Non-loaded print language, not-included function (print language, print
utility, etc.) requested. (The decomposer specified by
PJL or Auto SW is not included.)
Do fix-choose for Decomposer thru Operating Panel or thru a command..
103-203 MACHINE CODE FAIL

[Detection Conditions] ProductNo Fail (no initialization)
Turn the power off/on, and if the trouble persists, execute the
following:
If the trouble persists, successively change the ESS PWB (PL13.1) or MCU
PWB (PL13.1). (The 2 PWBs cannot be changed
at the same time.) If the trouble still persists, ask for help from TSP
or Support G..
103-204 SerialNo Fail

[Detection Conditions] SerialNo Fail (no initialization)
following:
PWB (PL13.1). (The 2 PWBs cannot be changed at the same time.) If the
trouble still persists, ask for help from TSP or Support G..
103-207 ALL MACHINE CODES MISMATCH

Even 1 of the ProductNos held in 3 places is different.
following:
If the trouble persists, successively change the ESS PWB (PL13.1) or MCU PWB (PL13.1). (The 2 PWBs
cannot be changed at the same time.) If the trouble still persists, ask for help from TSP or Support G..
103-208 ALL MACHINE CODES MISMATCH

Even 1 of the Serial Numbers held in 3 places is different.
following:
PWB (PL13.1). (The 2 PWBs cannot be changed at the same time.) If the
trouble still persists, ask for help from TSP or Support G
103-320 EEPROM FAIL

Abnormality occurs on writing in ESS Board SEEPROM
[Rectification Method] Change ESS PWB (PL13.1).
103-321 BACKUP SRAM FAIL

Abnormality occurs on writing in ESS Board NVM
[Rectification Method] Change ESS PWB (PL13.1).
103-330 ESS ROM DIMM #3 CHECK FAIL

Fail detected during check of ESS ROM DIMM #3.
[Rectification Method] Pull out ESS ROM DIMM #3. If the trouble
persists, change ESS ROM DIMM #3.
103-331 ESS ROM DIMM #1 NOT FOUND

Detects that ESS ROM DIMM #1 is not set in place.
[Rectification Method] Set ESS ROM DIMM #1 in place.. If the trouble
persists after setting it in place, change ESS PWB.
(PL13.1)
103-332 ESS STANDARD ROM ERROR

[Detection Conditions] Error detected in the standard ROM loaded into
the ESS.
[Rectification Method] Take out the standard ROM loaded into the ESS. If
the trouble persists, change the standard ROM
loaded into the ESS..
103-333 ASIC FAIL (PANTHER-T)

[Detection Conditions] Panther error detected.
following: Change ESS PWB (PL13.1)
103-334 STANDARD FONT ROM ERROR

[Detection Conditions] Abnormality detected in Standard Loaded Font ROM.
following: Change Font ROM.
103-335 FONT ROM NOT FOUND

[Detection Conditions] Font ROM not detected as being in place.
following: Set Font ROM. in place.
103-336 ESS RAM DIMM #3 W/R CHECK FAIL

Error detected in ESS RAM DIMM #3 during Read/Write Check.
Take out ESS RAM DIMM #3. If the trouble continues, change the ESS ROM
DIMM #3.
103-337 ESS STANDARD RAM ERROR
Error detected in ESS Standard-Loaded RAM
Take out ESS RAM DIMM #3. If the trouble continues, execute the
following: Change the ESS ROM PWB (PL13.1).
103-338 SAME FONT ROMs FOUND

Detects that the same Font ROM is in place.
Check the Font ROM. If the trouble continues, execute the following:
Change the ESS PWB (PL13.1)
103-339 ROM DIMM OF ANOTHER PRODUCT FOUND

Detects that the ROM DIMM for a different type of machine is in place.
Check the ROM DIMM, and put in the proper ROM DIMM. If the trouble
continues, execute the following: Change the ESS
PWB (PL13.1)
103-372 IOT sc SOFT FAIL

IOT Controller Soft problem. A problem occurred during software
processing [running?], and further processing [running?]
cannot occur.
following:
1. Re-install ESS software.
2. Change the ESS PWB (PL13.1).
116-200 MAIN PWBA IC FAIL

[Detection Conditions] Abnormality on IC within the ESS PWB detected.
[Rectification Method] Change the ESS PWB (PL13.1)
116-201 HDD FAIL

HDD could not be booted up due to HDD abnormality detected during boot-
up.
following:
1. Execute HDD Diagnosis (DC355)
2. Change HDD (PL13.1)
3. Change ESS PWB (PL13.1)
116-206 TIMER FAIL

[Detection Conditions] Timer abnormality detected.
[Rectification Method] Change ESS PWB (PL13.1)
116-207 ETHERNET BOARD FAIL
[Detection Conditions] Ethernet Board Fail detected.
[Rectification Method] Does not occur with DPC 2220 Code.
116-209 FONT ROM DIMM #1 CHECK FAIL

Abnormality detected when ESS Font ROM Dimm #1 is checked.
Take out ESS Font ROM DIMM #1. If the trouble persists, change ESS Font
ROM DIMM #1..

ROM DIMM #2.

ROM DIMM #3.

Ethernet abnormality detected.
Change ESS PWB (PL13.1)

Abnormality detected at ESS RAM DIMM #1 W/R.
Take out ESS RAM DIMM #1. If the trouble continues, change ESS RAM DIMM
#1..

Abnormality detected at ESS RAM DIMM #2 W/R.
Take out ESS RAM DIMM #2. If the trouble continues, change ESS RAM DIMM
#2.

Abnormality detected during check of standard ROM DIMM.
Take out standard ROM DIMM. If the trouble continues, change standard
ROM DIMM.
116-318 OPTION ROM DIMM CHECK FAIL
Abnormality detected during check of Option ROM DIMM.
Take out Option ROM DIMM. If the trouble continues, change Option ROM
DIMM.
116-319 SERIAL FAIL

During Serial port Initialization Fail, there is no Serial Board.
Does not occur with DPC 2220 Code..
116-320 STREAMZ SOFT FAIL

A problem occurs during Streamz Fatal Error software processing, and
further processing cannot be done.
1. Reinstall ESS Software.
116-321 SYSTEM SOFT FAIL

A problem occurs during software processing, and further processing
cannot be done.
3. Reinstall ESS Software.
116-322 TRAP FAIL

[Detection Conditions] Unusual CPU processing occurs.
Change ESS PWB (PL13.1).
116-323 ESS NVRAM W/R CHECK FAIL

Abnormality detected during ESS PWB NVM Read/Write Check.
116-324 EXCEPTION FAIL

[Detection Conditions] Unusual CPU processing detected.
116-325 ESS FAN FAIL

[Detection Conditions] Abnormality occurs in ESS Fan rotation.
1. Change ESS Fan (PL13.1)
116-326 ESS ROM DIMM #1 FLASH FAIL

ESS ROM DIMM #1 Flash Fail detected.
3. Take out ESS ROM DIMM #1
4. Change ESS ROM DIMM #1.
116-327 ESS ROM DIMM #2 FLASH FAIL

ESS ROM DIMM #2 Flash Fail detected.
5. Take out ESS ROM DIMM #2
6. Change ESS ROM DIMM #2
116-328 L2 CACHE FAIL

[Detection Conditions] L2 Cache Fail detected.
116-329 SERIAL I/F SOFT FAIL

Serial I/F-related system call error detected.
[Rectification Method] Does not occur with DPC 2220.
116-330 HDD FILE SYSTEM FAIL

Error or HDD not formatted in check on HDD when power is switched on.
Switch power off/on, and if the trouble continues, execute the
following:
3. Change ESS PWB(PL13.1).
116-332 INVALID LOG INFO

[Detection Conditions] Log-related abnormality detected.
following:
4. Remove HDD once and turn the power off/on, then put HDD back on and
turn the power on.
5. Execute HDD Diagnosis (DC355).
116-340 SHORT OF MEMORY

[Detection Conditions] Shortage of memory detected.
following:
7. Add memory
8. Take out PostScript option.
116-341 ROM DIMMs MISMATCH

Improper version of several installed ROM DIMMs. An unusable combination
of ROM DIMMs is installed. When more than
one ROM DIMM is installed, it is necessary to match major versions and
minor versions.
Does not occur with DPC 2220, since it only takes 1 ROM.
116-345 TOKEN RING BOARD FAIL

[Detection Conditions] Token Ring Control IC Acesseror [?]
Does not occur with DPC 220, since PWB in question does not exist..
116-347 LOCALTALK BOARD FAIL

[Detection Conditions] LocalTalk Board does not boot up properly.
Does not occur with DPC 2220, since PWB in question does not exist.
116-349 SIF FAIL ON CALLING PFLITE FUNCTION

[Detection Conditions] SIF error on calling Pflite Function.
116-350 APPLETALK SOFT FAIL

Overall fatal error on AppleTalk. A problem occurs during software
processing, and further processing cannot take place.
116-351 ETHERTALK SOFT FAIL

EtherTalk-related fatal error. A problem occurs during software
4. Change ESS PWB (PL13.1).
116-352 NETWARE SOFT FAIL

NetWare-related fatal error. A problem occurs during software
116-353 IPD SOFT FAIL
Ipd-related fatal error. A problem occurs during software processing,
and further processing cannot take place.
116-355 SNMP AGENT SOFT FAIL

SNMP Agent-related fatal error. A problem occurs during software
116-356 EWS SOFT FAIL

EWS-related fatal error. A problem occurs during software processing,
116-357 PS SOFT FAIL

PS Fatal System error. A problem occurs during software processing, and
further processing cannot take place.
116-358 SALUTATION SOFT FAIL

Salutation-related fatal error. A problem occurs during software
116-359 PLW SOFT FAIL

Fatal error on PLW. A problem occurs during software processing, and
116-360 SMB SOFT FAIL

SMB-related fatal error. A problem occurs during software processing,
116-361 SPOOL FATAL HDD

SPL HDD fatal error.
SpoolCont detects an error during HDD access.
116-365 SPOOL FATAL

SPL fatal error. Problem occurs during software processing, and no
further processing can occur.
116-366 SPOOL FATAL

Report Generator malfunction. Problem occurs during software processing,
and no further processing can occur.
116-367 PARALLEL I/F SOFT FAIL

Overall Parallel fatal error. Problem occurs during software processing,
and no further processing can occur.
116-368 DUMP PRINT FAIL

DumpPrint fatal error. Problem occurs during software processing, and no
116-370 XJCL FAIL

XJCL fatal error. Problem occurs during software processing, and no
116-372 P-FORMATTER FAIL

P-Formatter fatal error. Problem occurs during software processing, and
no further processing can occur.
Change ESS PWB (PL13.1).
116-374 AUTO SWITCH FAIL

AutoSW fatal error. Problem occurs during software processing, and no
1. Re-install ESS software
116-377 VIDEO DMA FAIL

[Detection Conditions] Video DMA Fail detected.
116-390 STANDARD ROM AND NVM VERSION MISMATCH

Standard ROM and NVM version mismatch detected.
Following the LCD display, initialize the NVM. (If not initializing NVM,
use version compatible with Standard ROM.).
116-398 IPP SOFT FAIL

IPP-related fatal error. Problem occurs during software processing, and
116-399 JME SOFT FAIL

JME-related fatal error. Problem occurs during software processing, and
116-701 DOUBLE-SIDED COPY STOP (ryomen-nakiwakare) EXECUTED

[Detection Conditions] Double-sided copies cannot be printed due to lack
of memory.
Imari: Either increase memory, or if no HD, add HDD.
116-702 PRINTING WITH ALTERNATIVE FONT

[Detection Conditions] Printing done with alternative font.
Unnecessary.
116-703 PS INTERPRET ERROR

[Detection Conditions] Error occurs during Language-Interpretation
Processing
[Rectification Method] Correct the job data.
116-710 HP-GL SPOOL FILE OVERFLOW

[Detection Conditions] HP-GL/2 memory overflow
[Rectification Method] Increase HP-GL spool size. Or add HDD.
116-711 PLW FORM COMPOSITION [synthesis?] ERROR

PL Form image size/direction is different from paper size/direction, so
that composition [synthesis?] is impossible.
Imari: Choose paper that is consistent with the size and direction of
the form that is registered..
116-712 PLW FORM LACKS CAPACITY

Insufficient capacity in RAM Disk or Hard Disk, so that PLW Form/Logo
Data cannotbe registered.
After confirming registered Form/Logo on the utility on the Operating
Panel, delete unnecessary items. If it is a RAM Disk,
increase the capacity allotment.
116-714 HP-GL COMMAND ERROR DETECTED

[Detection Conditions] HP-GL/2 Command Error
Data that will cause an error within the print data is being used;
revise or delete such data.
116-715 PLW FORM REGISTRATION ERROR

During PLW Form Data registration, the number of units exceeds the
limit, so registration cannot proceed.
After confirming registered Form on the utility on the Operating Panel,
delete unnecessary items. Or delete unnecessary
Form with the print command.

[Detection Conditions] The designated Form is not registered.
Imari: Use the registered Form or register the necessary Form..
116-737 INSUFFICIENT ART USER DEFINITION AREA
During registration of data on user definition (non-standard characters,
patterns, etc.) in Art, insufficient RAM capacity
makes registration impossible.
Delete User Definition Data that has been registered. Or else increase
capacity allotment.

Form image size/direction is different from paper size/direction, so
that composition [synthesis?] is impossible.
Choose paper that is consistent with the size and direction of the form
that is registered.
116-739 INSUFFICIENT FORM / LOGO CAPACITY

Lack of RAM Disk or Hard Disk capacity makes Form/Logo registration
impossible.
After confirming registered Form/Logo on the utility on the Operating
Panel, delete unnecessary items. If it is a RAM Disk,
increase the capacity allotment.
116-740 VALUE OPERATION [calculating?] ERROR

The value operation [calculation?] executed within the interpreter
exceeds the limit.
Within the print data, there is/are value(s) used that exceed the
printer’s value limit; remove such data..
116-741 FORM REGISTRATION ERROR

Registration cannot be completed because the Form Data exceeds the unit
limit.
After confirming registered Form on the utility on the Operating Panel,
delete unnecessary items. Or delete unnecessary
Forms with the print command.
116-742 LOGO REGISTRATION ERROR

Registration cannot be completed because the Logo Data exceeds the unit
limit.
After confirming registered Logo(s) on the utility on the Operating
Panel, delete unnecessary items. Or delete unnecessary
Logo(s) with the print command.
116-743 FORM/LOGO SIZE OVERFLOW

The Form/Logo Registration Impossible (insufficient space) Received Data
(Form/Logo) exceeds the registered buffer size.
Increase the size of the Form Registration Area on the operating panel.
Or add HD.
116-745 ART COMMAND ERROR

During decomposition, there is a grammatical error; Decompose checks all
types of value limits for excesses.
Command Revision, etc Imari: Change Art command that showed the error..
116-746 FORM COMPOUND [synthesis?] ERROR

[Detection Conditions] The designated Form is not registered.
Use registered Form or register the necessary Form.
116-747 BLANK PAPER PAGE DETECTED

Subtracting paper margin from valid coordinates gives a negative value.
Unnecessary.
116-748 BLANK PAPER PAGE DETECTED

Image data does not exist within page data.
Unnecessary..

Phaser 7700 Unlisted Error Codes

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Phaser 7700 Unlisted Error Codes

Caricato da

Copyright:

Formati disponibili

Phaser 770 Unlisted Error Codes

01-300 L/H COVER INTERLOCK OPEN

01-301 L/H Lower Cover Interlock Open

01-302 Front Cover Interlock Open

01-306 Duplex Cover Interlock Open

03-920 Tray 1 Not in Position

03-921 Tray 2 Not in Position

03-922 Tray 3 Not in Position

03-923 Tray 4 Not in Position

03-950 Tray 1 No Paper

03-951 Tray 2 No Paper

03-952 Tray 3 No Paper

04-340 IOT RAM FAIL

04-341 IOT RAM FAIL

04-342 IOT FLASH ROM LIMIT FAIL

04-343 IOT FLASH ROM R/W FAIL

04-344 IOT MICRO PITCH FAIL

04-345 IOT HVPS COMMUNICATION FAIL

04-346 IOT BELT HOME FAIL TOO LONG

04-347 IOT BELT POSITION FAIL

04-347 IOT BELT POSITION FAIL (cont)

04-348 IOT BELT EDGE SENSOR FAIL

04-358 IOT COMMUNICATION FAIL

04-361 DRUM MOTOR DRIVE FAIL

04-362 IOT NVM R/W FAIL

04-371 CONTROLLER IOT SYSTEM TIMING FAIL

04-415 BTR UNIT CHANGE SOON

04-417 IBT BELT UNIT (1 st BTR) CHANGE SOON

04-420 IBT BELT UNIT (1 st BTR) LIFE END

04-421 IBT BELT CLEANER ASSY LIFE END

04-605 IOT NVM EMPTY

04-640 BELT WALK FAIL

04-641 BELT EDGE LEARN FAIL

04-642 BELT EDGE CHECK FAIL

04-650 IOT TIME OUT CYCLE DOWN FAIL

04-908 2 nd BTR UNIT LIFE END

06-372 ROS POLYGON MOTOR FAIL

06-380 ROS SOS LENGTH FAIL Y

06-381 ROS SOS LENGTH FAIL Y

06-382 ROS SOS LENGTH FAIL C

06-383 ROS SOS LENGTH FAIL K

06-385 ROS ASIC FAIL

07-105 TRAY 1 MISFEED

07-110 TRAY 2 MISFEED

07-115 TRAY 3 MISFEED

07-117 TRAY 3 MISFEED (3TM)

07-120 TRAY 4 MISFEED (3TM)

07-122 TRAY 4 FEED JAM (TTM)

07-250 TRAY COMMUNICATION FAIL

07-270 TRAY 1 PAPER SIZE SENSOR BROKEN

07-271 TRAY 2 PAPER SIZE SENSOR BROKEN

07-272 TRAY 3 PAPER SIZE SENSOR BROKEN (3TM)

07-274 MSI PAPER SIZE SENSOR BROKEN

07-276 TRAY 3 PAPER SIZE SENSOR BROKEN (TTM)

07-277 TRAY 4 PAPER SIZE SENSOR BROKEN (TTM)

07-281 TRAY 1 LIFT UP FAIL

07-282 TRAY 2 LIFT UP FAIL

07-283 TRAY 3 LIFT UP FAIL (3TM)

07-284 TRAY 4 LIFT UP FAIL (3TM)

07-293 TRAY 4 LIFT UP FAIL (TTM)

07-297 ALL TRAY LIFT UP FAIL

07-930 TRAY 1 PAPER SIZE MISMATCH

07-931 TRAY 2 PAPER SIZE MISMATCH

07-932 TRAY 3 PAPER SIZE MISMATCH