Phaser 770 Unlisted Error Codes

01-300 L/H COVER INTERLOCK OPENEXPLANATION: When the L/H Cover is open.Refer to BSD: CH 1.6 Ch 1.8ProcedureRelease the L/H Cover lock and cheat the Interlock Switch with ascrewdriver.Did the 01-300 display disappear?Yes NoReturn the L/H CoverBetween I/F PWB J536-4 (+) GND (-)Is the voltage +5VDC?Yes NoIs the voltage between L/H Cover Interlock Switch J127-A2 (+) GND (-)+5VDC?Yes NoBetween L/H Cover Interlock Switch J127-B2 (+)GND(-)Is the voltage +5VDC?Yes NoUse the wire network in Chapter 7, and check the +5VDC circuit up to theL/H Cover InterlockSwitch 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 CoverInterlock 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 theinstallation of the switch. Redwood xlate

01-301 L/H Lower Cover Interlock OpenExplanationThe L/H Lower Cover is open.Refer to BSD: CH 8.2 CH 8.9ProcedureExecute DC330 [001-302]Open L/H Low Cover, turn L/H Lower Cover Interlock Sensor on or off withpaper.Did the display change to H/L?Yes NoUse an all-purpose permeable sensor FIP and fix the L/H Lower CoverInterlock Sensor (PL2.3)Check the installation of the actuator and the cover; if there is noproblem, change the MCU PWB. (PL13.1).

01-302 Front Cover Interlock OpenEXPLANATIONThe front cover is open.Refer to BSD: CH1.6 CH 1.8ProcedureRemove the front cover, and with a the front cover interlock switch.Did the 01-302 display disappear?Yes NoI/F PWB between J536-2(+)GND(-)Is the voltage +24VDC?Yes NoFront Cover Interlock Switch between J126-B1(+)GND(-)Is the voltage +24VDC?Yes No

Front Cover Interlock Switch between J126-A1(+)GND(-)Is the voltage +24VDC?Yes NoL/H Cover Interlock Switch between J127-B1(+)GND(-)Is the voltage +24VDC?Yes NoL/H Cover Interlock Switch between J127-A1(+)GND(-)Is the voltage +24VDC?Yes NoUse the wire network in Chapter 7 and check the L/H Cover InterlockSwitchJ127-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 SwitchJ127-B1 to Front CoverInterlock Switch J126-A1.Change Front Cover Interlock Switch (PL10.1)Check for broken wires or poor contact from Front Cover Interlock SwitchJ126-B1 to I/F PWB J536-2.Check the connection between I/F PWB and MCU PWB. If there is noproblem, 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 theactuator and switch..

01-306 Duplex Cover Interlock OpenEXPLANATIONThe duplex cover is openRefer to BSD: CH10.6 CH10.8ProcedureExecute DC330 [008-300].Open the duplex cover, and turn the Duplex Cover Interlock Switch on andoff with a screwdriver.Does the H/L Display change?Yes NoActuate the Duplex Cover Interlock Switch.Between I/F PWB J533-A9 (+)GND(-)Is the voltage 0VDC?Yes NoBetween Duplex PWB J540-2 (+)GND(-)Is the voltage 0VDC?Yes NoBetween Duplex Cover Interlock Switch J136-2 (+)GND(-)Is the voltage 0VDC?Yes NoUsing the wire network in Chapter 7, check the DC COM circuits up to theDuplex CoverInterlock Switch J136-2. (WN 7.3.10 5VRTN-3)Between Duplex Cover Interlock Switch J136-1 (+)GND(-)Is the voltage 0VDC?Yes NoChange the Duplex Cover Interlock Switch ( PL12.2 )Check for broken wires and poor connections from Duplex PWB J540-2 thruDuplex Cover InterlockSwitch J136-1Check for broken wires and poor connections from I/F PWB J533-A9 thruDuplex PWB J540-2Check the connection between the I/F PWB and the MCU PWB, and if thereis no problem, change the MCU PWB. (PL13.1)Check the installation of the cover and the cover actuator, and if thereare no problems, change the MCU PWB. (PL13.1).

03-920 Tray 1 Not in Position

EXPLANATIONTray 1 is not setRefer to BSD: CH7.1 CH7.13AProcedurePush Tray 1 into the machine.Between I/F PWB J534-B14 (+) GND (-)Is the voltage +3.38VDC or above?Yes NoCheck for poor connections between I/F PWB and MCU PWB, and if there areno problems, change the MCU PWB(PL13.1)Pull out Tray 1 and confirm paper size setting.Is the setting correct?Yes NoReset it.Between Tray 1 Size Sensor J115-2 (+) GND (-)Is the voltage +3.38VDC or above?Yes NoCheck for broken wires or poor connections between Tray 1 Size SensorJ115-1 and I/F PWB J534-B14.Between Tray 1 Size Sensor J115-1 (+) GND (-)Is the voltage +3.3VDC?Yes NoUsing the wire network in Chapter 7, check the +3.3VDC circuits up toTray 1 Size Sensor J115-1. (WN 7.3.3 + 3.3VDC)Between Tray 1 Size Sensor J115-1 (+) J115-3 (-)Is the voltage +3.3VDC?Yes NoUsing 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).

03-921 Tray 2 Not in PositionEXPLANATIONTray 2 is not setRefer to BSD: CH7.2 CH7.13AProcedurePush Tray 2 into the machine.Between Tray Module PWB J546-8 (IT: J546-8 , 3T: J546-8 , TT: J546-8 )(+) GND (-)Is the voltage +4.6VDC or above?Yes NoChange the Tray Module PWB (PL14.5 / PL15.5 / PL16.13 )Pull out Tray 2 and confirm paper size setting.Is the setting correct?Yes NoReset it.Between Tray 2 Size Sensor J816-2 (3T: J816-2 ,TT: J816-2 ) (+) GND (-)Is the voltage +4.6VDC or above?Yes NoCheck for broken wires or poor connections between Tray 2 Size SensorJ816-2 (3T: J816-2, TT: J816-2 ) and Tray ModulePWB J546-8 (IT: J546-8, 3T: J546-8, TT: J546-8 ).Between Tray 2 Size Sensor (3T: J816-1 , TT: J816-1) (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up tothe 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) (-)

Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the DC COM circuits up to the Tray 2 Size Sensor J816-3(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)

03-922 Tray 3 Not in PositionEXPLANATIONTray 3 is not set.Refer to BSD: CH7.3 CH7.4ProcedurePush Tray 3 into the machine.Between Tray Module PWB J548-11 (IT: J548-11 , 3T: J548-11 , TT: J548-11) (+) GND (-)Is the voltage +4.6VDC or above?Yes NoChange the Tray Module PWB (PL15.5 / PL16.13 )Pull outTray 3 and confirm paper size setting.Is the setting correct?Yes NoReset it.Between Tray 3 Size Sensor J820-2 (3T: J820-2 ,TT: J820-2 ) (+) GND (-)Is the voltage +4.6VDC or above?Yes NoCheck for broken wires or poor connections between Tray 3 Size SensorJ820-2 (3T: J820-2, TT: J820-2 ) and Tray ModulePWB 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 (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up tothe Tray 3 Size Sensor J820-1 (3T: J820-1, TT:J820-1 ). (WN 7.3.6 + 5VDC-2)Between Tray 3 Size Sensor J820-1 (3T: J820-1 , TT: J820-1 ) (+) J820-3 (3T: J820-3, TT: J820-3) (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the DC COM circuits up to the Tray 3 Size Sensor J820-3(3T: J820-3, TT: J820-3 ) (WN 7.3.8 + 5V$TN-1)Check the installation of the sensor, and if there is no problem, change the Tray Size Sensor (PL15.1 /PL16.1).

03-923 Tray 4 Not in PositionEXPLANATIONTray 4 is not setRefer to BSD: CH7.5 CH7.6 CH7.13AProcedurePush Tray 4 into the machine.Between Tray Module PWB J548-5 (IT: J548-5 , 3T: J548-5 , TT: J548-5 )(+) GND (-)Is the voltage +4.6VDC or above?Yes NoChange the Tray Module PWB (PL15.5 / PL16.13 )Pull out Tray 4 and confirm paper size setting.Is the setting correct?Yes NoReset it.

Between Tray 4 Size Sensor J824-2 (IT: J548-2 ,3T: J548-2 ,TT: J548-2 )(+) GND (-)Is the voltage +4.6VDC or above?Yes NoCheck for broken wires or poor connections between Tray 4 Size SensorJ824-2 (IT: J548-2 ,3T: J548-2, TT: J548-2 ) andTray 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 (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up tothe Tray 4 Size Sensor J824-1 (3T: J824-1, TT:J824-1 ). (WN 7.3.6 + 5VDC-2)Between Tray 4 Size Sensor J824-1 (3T: J824-1 , TT: J824-1 ) (+) J824-3 (3T: J824-3, TT: J824-3) (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the DC COM circuits up to the Tray 4 Size Sensor J824-3(3T: J824-3, TT: J824-3 ) (WN 7.3.8 + 5VRTN-1)Check the installation of the sensor, and if there is no problem, change the Tray Size Sensor (PL15.1 /PL16.1).

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

03-951 Tray 2 No PaperEXPLANATIONTray 2 is out of paper.Refer to BSD: CH7.8 CH7.13BProcedureExecute DC330 [007-121] .Turn the No-Paper Sensor Actuator on/off.Does the display change?Yes NoUsing the all-purpose permeable defective-sensor FIP, fix the Tray 2 No-Paper Sensor. (PL14.3 / PL15.3 / PL16.7)Change the MCU PWB (PL13.1).

03-952 Tray 3 No PaperEXPLANATIONTray 3 is out of paper.Refer to BSD: CH7.9 CH7.13BProcedureExecute DC330 [007-122] .Turn the No-Paper Sensor Actuator on/off.Does the display change?Yes NoUsing the all-purpose permeable defective-sensor FIP, fix the Tray 3 No-Paper Sensor. (PL15.5 / PL16.9 )Change the MCU PWB (PL13.1).

03-953 Tray 3 No PaperEXPLANATIONTray 3 is out of paper.Refer to BSD: CH7.9 CH7.13BProcedureExecute DC330 [007-122] .Turn the No-Paper Sensor Actuator on/off.Does the display change?Yes NoUsing the all-purpose permeable defective-sensor FIP, fix the Tray 3 No-Paper Sensor. (PL15.5 / PL16.9 )Change the MCU PWB (PL13.1).

04-340 IOT RAM FAILEXPLANATIONThe MCU PWB RAM Test was no good.Refer to BSD: CH3.1A CH3.4ProcedureIf turning the power switch off/on does not fix the problem, change theMCU PWB. ( PL13.1).

04-341 IOT RAM FAILEXPLANATIONMCU PWB malfunction.Refer to BSD: CH3.1A CH3.4ProcedureIf turning the power switch off/on does not fix the problem, change theMCU PWB. ( PL13.1).

04-342 IOT FLASH ROM LIMIT FAILEXPLANATIONFLASH ROM malfunction.Refer to BSD: CH3.1A CH3.4ProcedureIf turning the power switch off/on does not fix the problem, change theMCU PWB. ( PL13.1).

04-343 IOT FLASH ROM R/W FAILEXPLANATIONFLASH ROM malfunction.Refer to BSD: CH3.1A CH3.4ProcedureIf turning the power switch off/on does not fix the problem, change theMCU PWB. ( PL13.1).

04-344 IOT MICRO PITCH FAILEXPLANATIONMicro Pit is not generated within the prescribed time.Refer to BSD: CH3.1A CH3.4ProcedureIf turning the power switch off/on does not fix the problem, change theMCU PWB. ( PL13.1).

04-345 IOT HVPS COMMUNICATION FAILEXPLANATIONCommunication error between MCU PWB and HVPS Control.Refer to BSD: CH3.1B CH3.4ProcedureBetween MCU PWB J406-A4 (+) GND (-)Is the voltage +5VDC?

Yes NoBetween MCU PWB J406-A4 (+) GND (-)Is the voltage +3.3VDC?Yes NoCheck 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 andHVPS Control PWB J574-7Cut off the power and check the following.From HVPS Control PWB J574-5 to MCU PWB J406-A6From HVPS Control PWB J574-4 to MCU PWB J406-A7Is any of the resistance values 1 omega or less?Yes NoFix broken wires and bad connections.Is the resistance value between HVPS Control PWB J574-6 and MCU PWBJ406-A5 1 omega or less?Yes NoFix broken wires and bad connections.Change Mcu PWB (PL13.1), and if that doesn’t work, change HVPS ControlPWB. (PL9.1).

04-346 IOT BELT HOME FAIL TOO LONGEXPLANATIONThe IBT Home Sensor does not detect the Home Belt.Refer to BSD: CH9.15 CH9.16 CH9.27ProcedureIs there a label indicating Belt Home?Yes NoChange the IBT Belt (PL5.3 )Make sure that the Belt Home Label is in the home-sensor-detectionposition. (Put paper in the detection position)Execute DC330 [004-100] .Does the display read “H”?Yes NoBetween I/F PWB J533-86 (+) GND (-)Is the voltage +5VDC?Yes NoBetween I/F PWB J533-87 (+) J533-85 (-)Is the voltage +5VDC?Yes NoClose the front door, and if the voltage between J533-B7(+) J533-B5 (-)is not +5VDC, change the MCUPWB. (PL13.1)Check for broken wires or bad connections from IBT Home Sensor J121 toI/F PWB J533, and if there are noproblems, 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 NoBetween I/F PWB J530-B11 (+) GND (-)Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check the +24FDC circuits up toI/F PWB J530-B11. (WN 7.3.11 +24VDC-1)Between IBT Motor J208-3 (+) GND (-). Is the voltage +24 VDC?Yes NoCheck for broken wires or bad connections between IBT Motor J208-3 andI/F PWB J530-B11.

Check for broken wires or bad connections between IBT Motor J208 and I/FPWB J530.Are there any broken wires or bad connections?Yes NoChange IBT Motor (PL1.1)Fix the broken wires or bad connectionsChange Mcu PWB (PL13.1), and if that doesn’t work, change I/F PWB.(PL9.1).

04-347 IOT BELT POSITION FAILEXPLANATIONPoorly adjusted IBT Belt Edge.Refer to BSD: CH9.16 CH9.27AProcedureIs the Edge Sensor actuator touching the Belt?Yes NoCheck 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 NoBetween I/F PWB J533-B1 (+) J533-B3 GND (-)Is the voltage +5VDC?Yes NoClose the front door, and if the voltage between J533-B1(+) J533-B3 (-)is not +5VDC, change the MCU PWB. (PL13.1) Between I/F PWB J533-B2 (+)GND (-)Is the voltage +5VDC?Yes NoBetween I/F PWB J533-B2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or bad connections from I/F PWB J533 to IBT EdgeSensor J119, and if there areno 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 IBTEdge Sensor J119-2Change 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 NoCheck for broken wires or bad connections from I/F PWB J530 and IBTSteering Motor J207 .Are there any broken wires or bad connections?Yes NoChange 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 connectionsCheck the installation of the IBT Belt, and if there is no problem,change the MCU PWB (PL13.1).

04-348 IOT BELT EDGE SENSOR FAILEXPLANATIONDefective IBT Belt Edge Sensor.Refer to BSD: CH9.16 CH9.27AProcedureIs 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 NoBetween I/F PWB J533-B1 (+) J533-B3 GND (-)Is the voltage +5VDC?Yes NoClose the front door, and if the voltage between J533-B1(+) J533-B3 (-)is not +5VDC, change the MCU PWB. (PL13.1) Between I/F PWB J533-B2 (+)GND (-)Is the voltage +5VDC?Yes NoBetween I/F PWB J533-B2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or bad connections from I/F PWB J533 to IBT EdgeSensor J119, and if there areno 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 IBTEdge Sensor J119-2Change the IBT Edge Sensor (PL5.4) Between I/F PWB J530-B7 (+) GND (-)Is thevoltage +24VDC?Yes NoUsing 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].Did the IBT Steering Motor rotate?Yes NoCheck for broken wires or bad connections from I/F PWB J530 and IBTSteering Motor J207 Are there any broken wires or bad connections?Yes NoChange 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 connectionsCheck the installation of the IBT Belt, and if there is no problem,change the MCU PWB (PL13.1

04-358 IOT COMMUNICATION FAILEXPLANATIONBad transmission between ESS – IOTRefer to BSD: CH3.1A CH3.4ProcedureCheck the connector of the MCU PWB and ESS PWB, and if there is noproblem, change the MCU PWB (PL13.1); if that doesn’t work, change ESSPWB. (PL13.1).

04-361 DRUM MOTOR DRIVE FAILEXPLANATIONPoor Drum Motor rotation.Refer to BSD: CH9.1 CH9.1ProcedureRemove the Drum ASSY (Y/M/C/K), execute DC330 [004-003].Does the Drum Motor rotate?Yes NoBetween Drum Motor J210-4 (+) GND (-)Is the voltage +5VDC?Yes NoUsing 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 (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toDrum Motor J210-6. (WN7.3.13+24VDC-3)Execute DC330 [004-003].Between Drum Motor J210-1 (+)GND (-)Is the voltage 0 VDC?Yes NoExecute DC330 [004-003].Between MCU PWB J407-B1 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or bad connections from Drum Motor J210-1 to MCUPWB J407-B1, and if thereare no problems, change the MCU PWB. (PL5.4).Check for broken wires or bad connections from Drum Motor J210-1 to MCUPWB J407-BqExecute DC330 [004-003].Between Drum Motor J210-2 (+) GND (-)Is the frequency between 1KHz and 1.3KHz?Yes NoExecute DC330 [004-003].MCU PWB J407-B3 (+) GND (-)Is the frequency between 1KHz and 1.3KHz?Yes NoCheck for frame shorts between Drum Motor J210-3. And MCU PWB J407-B3 ,and if there are noproblems, change MCU PWB. (PL13.1)Check for cut wires and bad connections between Drum Motor J210-3. andMCU PWB J407-B3 .Change Drum Motor. (PL1.1)Execute DC330 [004-003].Between MCU PWB J407-B8 (+) GND (-)Is the voltage +5VDC?Yes NoChange MCU PWB (PL13.1)Execute DC330 [004-003].Drum Motor J210-8 (+) GND (-)Is the voltage +5VDC?Yes NoCheck for cut wires and bad connections between MCU PWB J407-B3 and DrumMotor J210-3Change Drum Motor. (PL1.1).

04-362 IOT NVM R/W FAILEXPLANATIONMCU PWB NVM R/W is no good.Refer to BSD: CH3.3 CH3.4ProcedureTurn the power switch off/on, and if that doesn’t work, change MCU PWB.(PL13.1).

04-371 CONTROLLER IOT SYSTEM TIMING FAILEXPLANATIONPoor transmission between ESS – IOT.Refer to BSD: CH3.1A CH3.4ProcedureCheck the connection of the MCU PWB and ESS PWB connectors, and if thereis no problem, change MCU PWB (PL13.1);if that doesn’t work, change ESS PWB (PL13.1)

04-414 IBT BELT CLEANER ASSY CHANGE SOONEXPLANATIONWhen to change IBT Belt Cleaner.Refer to BSD: CH9.27AProcedureChange the Cleaner ASSY, and if that doesn’t work, change the MCU PWB.(PL13.1).

04-415 BTR UNIT CHANGE SOONEXPLANATIONWhen to change the 2 nd BTR Unit.Refer to BSD: CH9.27AProcedureChange 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 SOONEXPLANATIONWhen to change the IBT Belt Unit.Refer to BSD: CH9.27AProcedureChange 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 ENDEXPLANATIONLifecycle of the IBT Belt Unit.Refer to BSD: CH9.27AProcedureChange the IBT Belt Unit, and if that doesn’t work, change the MCU PWB.(PL13.1

04-421 IBT BELT CLEANER ASSY LIFE ENDEXPLANATIONLifecycle of the IBT Belt Cleaner ASSY.Refer to BSD: CH9.27AProcedureChange the IBT Belt Cleaner ASSY, and if that doesn’t work, change theMCU PWB. (PL13.1).

04-605 IOT NVM EMPTYEXPLANATIONDetects that the NVM of the IOT is empty.Refer to BSD: CH3.3 CH3.4ProcedureSwitch the power off/on and if that doesn’t work, change MCU PWB.(PL13.1).

04-640 BELT WALK FAILEXPLANATIONBad IBT Belt Edge adjustment.Refer to BSD: CH9.16 CH9.27AProcedureIs the Edge Sensor actuator touching the Belt?Yes NoCheck the installation of the actuator.Turn the power on; between I/F PWB J533-B2 (+)GND (-)Is the voltage between +3VDC and +1VDC?Yes No

Between I/F PWB J533-B1 (+) J533-B3 (-)Is the voltage +5VDC?Yes NoCheck the +5VDC circuits up to I/F PWB J533-B1.Between I/F PWB J533-B2 (+) GND (-)Is the voltage +5 VDC?Yes NoBetween I/F PWB J533-B2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or bad connections from I/F PWB J533 to IBT EdgeSensor J119, and if there areno 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 EdgeSensor J119-2Change IBT Edge Sensor (PL5.4)Between I/F PWB J530-B7 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toI/F PWB J530-B7. (WN7.3.11 24 VDC-1)Remove IBT ASSY, execute DC330 [004-003]Did the IBT Steering Motor rotate?Yes No.Check for broken wires or bad connections from I/F PWB J530 to IBTSteering Motor J207.Were there any broken wires or bad connections?Yes NoChange 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.Check the installation of the IBT Belt, and if there is no problem,change MCU PWB (PL13.1).

04-641 BELT EDGE LEARN FAILEXPLANATIONBad IBT Belt Edge adjustment.Refer to BSD: CH9.16 CH9.27AProcedureIs the Edge Sensor actuator touching the Belt?Yes NoCheck the installation of the actuator.Turn the power on; between I/F PWB J533-B2 (+)GND (-)Is the voltage between +3VDC and +1VDC?Yes NoBetween I/F PWB J533-B1 (+) J533-B3 (-)Is the voltage +5VDC?Yes NoClose the front door; if the voltage between I/F PWB J533-B1 and J533-B3is not +5VDC, change the MCU PWB.(PL13.1)Between I/F PWB J533-B2 (+) GND (-)Is the voltage +5 VDC?Yes NoBetween I/F PWB J533-B2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or bad connections from I/F PWB J533 to IBT EdgeSensor J119, and if there areno 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 EdgeSensor J119-2Change IBT Edge Sensor (PL5.4)Between I/F PWB J530-B7 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toI/F PWB J530-B7. (WN7.3.11 24 VDC-1)Remove IBT ASSY, execute DC330 [004-003]Did the IBT Steering Motor rotate?Yes NoCheck for broken wires or bad connections from I/F PWB J530 to IBTSteering Motor J207.Were there any broken wires or bad connections?Yes NoChange 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.Check the installation of the IBT Belt, and if there is no problem,change MCU PWB (PL13.1).

04-642 BELT EDGE CHECK FAILEXPLANATIONBad IBT Belt Edge adjustment.Refer to BSD: CH9.16 CH9.27AProcedureIs the Edge Sensor actuator touching the Belt?Yes NoCheck the installation of the actuator.Turn the power on; between I/F PWB J533-B2 (+)GND (-)Is the voltage between +3VDC and +1VDC?Yes NoBetween I/F PWB J533-B1 (+) J533-B3 (-)Is the voltage +5VDC?Yes NoClose the front door; if the voltage between I/F PWB J533-B1 and J533-B3is not +5VDC, change the MCU PWB.(PL13.1)Between I/F PWB J533-B2 (+) GND (-)Is the voltage +5 VDC?Yes NoBetween I/F PWB J533-B2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or bad connections from I/F PWB J533 to IBT EdgeSensor J119, and if there areno 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 EdgeSensor J119-2Change IBT Edge Sensor (PL5.4)Between I/F PWB J530-B7 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toI/F PWB J530-B7. (WN7.3.11 24 VDC-1)Remove IBT ASSY, execute DC330 [004-003].Did the IBT Steering Motor rotate?Yes NoCheck for broken wires or bad connections from I/F PWB J530 to IBTSteering Motor J207.Were there any broken wires or bad connections?

Yes NoChange MCU PWB (PL13.1), and if that doesn’t work, change I/F PWB(PL9.1), and IBT Steering Motor. (PL1.3)Fix any broken wires or poor connections.Check the installation of the IBT Belt, and if there is no problem,change MCU PWB (PL13.1).

04-650 IOT TIME OUT CYCLE DOWN FAILEXPLANATIONBad PRINT processing continued for over 2 minutes.Refer to BSD: CH3.1AProcedureCheck for poor contact between ESS PWB and MCU PWB, and if there are noproblems, change ESS PWB. (PL13.1).

04-908 2 nd BTR UNIT LIFE ENDEXPLANATIONLife cycle of the 2 nd BTR Unit.Refer to BSD: CH9.27AProcedureChange the 2 nd BTR Unit, and if that doesn’t work, change MCU PWB.(PL13.1).

06-372 ROS POLYGON MOTOR FAILEXPLANATIONPoor ROS Motor rotation.Refer to BSD: CH6.5 CH6.8ProcedureExecute DC330 [006-031]Between MCU PWB J400-3 (+) GND (-)Is the voltage +5VDC?Yes NoChange the MCU PWB. (PL13.1)Execute DC330 [006-031].Between ROS ASSY Relay Connector J518-4 (+) GND (-)Is the voltage +5VDC?Yes NoCheck for broken wires or bad connections from ROS ASSY relay connectorJ518-4 to MCU PWB J400.Between ROS ASSY relay connector J518-1 (+) GND (-)Is the voltage +24VDC?Yes NoBetween MCU PWB J400-6 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J400-6. (WN7.3.13 +24VDC-3)Check for broken wires or bad connections from MCU PWB J400-6 to ROSRelay Connector J518-1.Execute DC330 [006-031].Between ROS ASSY Relay Connector J518-3 (+) GND (-)Is the voltage 0 VDC?Yes NoExecute DC330 [006-031].Between MCU PWB J400-4 (+) GND (-)Is the voltage 0 VDC?Yes No.Check for broken wires or bad connections from MCU PWB J400-4 to ROSASSY Relay Connector J518-3, and if there are no problems, change theMCU PWB. (PL13.1).

Check for broken wires or bad connections from MCU PWB J400-4 to ROSASSY Relay Connector J518-3Execute DC330 [006-031].Between ROS Relay Connector J518-5 (+) GND (-)Is the frequency between 2KHz and 2.5KHz?Yes NoExecute DC330 [006-031].Between MCU PWB J400-2 (+) GND (-)Is the frequency between 2KHz and 2.5KHz?Yes NoCheck for broken wires or bad connections from MCU PWB J400-2 to ROSASSY Relay Connector J518-5,and if there are no problems, change the MCU PWB. (PL13.1).Check for broken wires or bad connections from MCU PWB J400-2 to ROSASSY Relay Connector J518-5Check the harness wiring inside the ROS ASSY and if there is no problemchange the ROS ASSY (PL3.1).

06-380 ROS SOS LENGTH FAIL YEXPLANATIONThe interval [Translator’s Note: “ spacing” ?] of the ROS SOS (Y) signalexceeds the specified value.Refer to BSD: CH6.1 CH6.8ProcedureExecute DC330 [006-031].Does the ROS Motor make a rotating sound?Yes NoProceed to 06-372 FIPCheck for severed lines, poor contact between SOS PWB (Y) J516 and MCUPWB J401, and if there is no problem, change ROSASSY. (PL3.1).

06-381 ROS SOS LENGTH FAIL YEXPLANATIONThe interval [Translator’s Note: “ spacing” ?] of the ROS SOS (Y) signalexceeds the specified value.Refer to BSD: CH6.1 CH6.8ProcedureExecute DC330 [006-031].Does the ROS Motor make a rotating sound?Yes NoProceed to 06-372 FIPCheck for severed lines, poor contact between SOS PWB (M) J517 and MCUPWB J401, and if there is no problem, change ROS ASSY. (PL3.1).

06-382 ROS SOS LENGTH FAIL CEXPLANATIONThe interval [Translator’s Note: “ spacing” ?] of the ROS SOS (C) signalexceeds the specified value.Refer to BSD: CH6.3 CH6.8ProcedureExecute DC330 [006-031].Does the ROS Motor make a rotating sound?Yes NoProceed to 06-372 FIPCheck for severed lines, poor contact between SOS PWB (C) J514 and MCUPWB J401, and if there is no problem, change ROS ASSY. (PL3.1).

06-383 ROS SOS LENGTH FAIL KEXPLANATION

The interval [Translator’s Note: “ spacing” ?] of the ROS SOS (K) signalexceeds the specified value.Refer to BSD: CH6.4 CH6.8ProcedureExecute DC330 [006-031].Does the ROS Motor make a rotating sound?Yes NoProceed to 06-372 FIPCheck for severed lines, poor contact between SOS PWB (K) J515 and MCUPWB J401, and if there is no problem, change ROS ASSY. (PL3.1).

06-385 ROS ASIC FAILEXPLANATIONThe MCU PWB’s ROS ASIC movement is bad.Refer to BSD: CH6.1 CH6.8ProcedureTurn the power off/on, and if that doesn’t fix the problem, change MCUPWB. (PL3.1).

07-104 TRAY 1 FEED OUT SENSOR ON JAM (FROM TAKE AWAY SENSOR)EXPLANATIONThe Tray 1 Feed Out Sensor does not detect the presence of paper evenafter the specified amount of time has passed sinceThe 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-021 to 08-028] Take Away Motor 1 (3TM)[08-029 to 08-036] Take Away Motor 1 (TTM)Items to check:Malfunction of Take Away Motor 1Malfunction of Tray 1 Feed Out SensorWear, poor rotation of Take Away Roll 2Poor 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 MISFEEDEXPLANATIONTray 1 Feed Out Sensor does not detect the presence of paper even afterthe specified amount of time has passed sincefeeding began from Tray 1.DC330 code to check.[08-100] Tray 1 Feed Out Sensor[08-001] Tray 1 Feed/Liftup Motor (Feed)Items to check:Malfunction of Tray 1 Feed/Liftup MotorMalfunction of Tray 1 Feed Out SensorWear, poor rotation of Tray 1 Feed Roll and Tray 1 Nudger RollPoor advancement of paper due to foreign objects in the paper path, orthe 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-110 TRAY 2 MISFEEDEXPLANATIONThe Take Away Sensor does not detect the presence of paper even afterthe specified amount of time has passed since feeding

began from Tray 2.DC330 code to check.[08-106] Take Away Sensor[08-003] Tray 2 Feed/Liftup Motor (Feed)[08-013 to 08-020] Take Away Motor 1 (1TM)[08-021 to 08-028] Take Away Motor 1 (3TM)[08-029 to 08-036] Take Away Motor 1 (TTM)Items to check:Malfunction of Take Away Motor 1Malfunction of Tray 2 Feed/Liftup MotorMalfunction of Take Away SensorWear, poor rotation of Take Away Roll 2Wear, poor rotation of Tray 2 feed Roll, Tray 2 Nudger Roll.Poor advancement of paper due to foreign objects in the paper path, orthe presence of “ flash,” etc.Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )Defective Tray Module PWB, MCU PWB, ESS PWB

07-115 TRAY 3 MISFEEDEXPLANATIONTray 3 Feed Out Sensor does not detect the presence of paper even afterthe specified amount of time has passed sincefeeding began from Tray 3.DC330 code to check.[08-102] Tray 3 Feed Out Sensor[08-005] Tray 3 Feed/Liftup Motor (Feed)[08-029 to 08-036] Take Away Motor 1 (1TM)Items to check:Malfunction of Take Away Motor 1Malfunction of Tray 3 Feed/Liftup MotorMalfunction of Tray 3 Feed Out SensorWear, poor rotation of Take Away Roll 3Wear, poor rotation of Tray 3 Feed Roll, Tray 3 Nudger Roll.Poor advancement of paper due to foreign objects in the paper path, orthe presence of “ flash,” etc.Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )Defective Tray Module PWB, MCU PWB, ESS PWB.

07-117 TRAY 3 MISFEED (3TM)EXPLANATIONTray 3 Feed Out Sensor does not detect the presence of paper even afterthe specified amount of time has passed sincefeeding began from Tray 3.DC330 code to check.[08-102] Tray 3 Feed Out Sensor[08-005] Tray 3 Feed/Liftup Motor (Feed)[08-021 to 08-028] Take Away Motor 1 (3TM)Items to check:Malfunction of Take Away Motor 1Malfunction of Tray 3 Feed/Liftup MotorMalfunction of Tray 3 Feed Out SensorWear, poor rotation of Take Away Roll 3Wear, poor rotation of Tray 3 Feed Roll, Tray 3 Nudger Roll.Poor advancement of paper due to foreign objects in the paper path, orthe presence of “ flash,” etc.Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )Defective Tray Module PWB, MCU PWB, ESS PWB.

07-119 TRAY 4 MISFEED (TTM)EXPLANATIONTray 4 Feed Out Sensor does not detect the presence of paper even afterthe specified amount of time has passed sincefeeding began from Tray 4.DC330 code to check.[08-103] Tray 4 Feed Out Sensor[08-005] Tray 4 Feed/Liftup Motor (Feed)Items to check:Malfunction of Tray 4 Feed/Liftup MotorMalfunction of Tray 4 Feed Out SensorWear, poor rotation of Tray 4 Feed Roll, Tray 4 Nudger Roll.Poor advancement of paper due to foreign objects in the paper path, orthe presence of “ flash,” etc.Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )Defective Tray Module PWB, MCU PWB, ESS PWB.

07-120 TRAY 4 MISFEED (3TM)EXPLANATIONTray 4 Feed Out Sensor does not detect the presence of paper even afterthe specified amount of time has passed sincefeeding began from Tray 4.DC330 code to check.[08-103] Tray 4 Feed Out Sensor[08-007] Tray 4 Feed/Liftup Motor (Feed)[08-021 to 08-028] Take Away Motor 1 (3TM)Items to check:Malfunction of Tray 4 Feed/Liftup MotorMalfunction of Take Away Motor 1Malfunction of Tray 4 Feed Out SensorWear, poor rotation of Tray 4 Feed Roll, Tray 4 Nudger Roll.Wear, poor rotation of Take Away Roll 4Poor advancement of paper due to foreign objects in the paper path, orthe presence of “ flash,” etc.Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )Defective Tray Module PWB, MCU PWB, ESS PWB.

07-122 TRAY 4 FEED JAM (TTM)EXPLANATIONThe Tray 4 Feed Out Sensor does not detect the presence of paper whenTray 4 is pulled out in the middle of a job.DC330 code to check.[08-103] Tray 4 Feed Out SensorItems to check:Malfunction of Tray 4 Feed Out SensorPoor advancement of paper due to foreign objects in the paper path, orthe presence of “ flash,” etc.Use of paper outside spec. (for specs., refer to Chapter 6 “ Specs” )Defective Tray Module PWB, MCU PWB, ESS PWB.

07-250 TRAY COMMUNICATION FAILEXPLANATIONPoor transmission [communication?] between the Tray Module PWB and MCUPWB.Refer to BSD: CH1.4 CH1.5 CH3.1B CH3.4ProcedureBetween Tray Module PWB J555-1 (IT: J555-1, 3T: J555-1, TT: J555-1) (+)GND (-)Is the voltage +5VDC?

Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits to TrayModule 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 (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to TrayModule 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)From MCU PWB J407-B9 to Tray Module PWB J541-9 (IT: J541-9, 3T: J541-9,TT: J541-9)From MCU PWB J407-B11 to Tray Module PWB J541-5 (IT: J541-5, 3T: J541-5,TT: J541-5)From MCU PWB J407-B12 to Tray Module PWB J541-4 (IT: J541-4, 3T: J541-4,TT: J541-4)Are all of the resistances 1 omega or less?Yes NoCheck for broken wires or bad contacts on wires that are not 1 omega orless.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 BROKENEXPLANATIONAn abnormal AD value was detected from the Tray 1 Paper Size Sensor.Refer to BSD: CH7.1 CH7.13AProcedureSet Tray 1 in the machine.Is the I/F PWB J534-B14 (+) GND (-) voltage the same as that in the Tray 1 Paper Size SensorOutput Table inscribed in BSD:CH7.1?Yes NoBetween 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 NoBetween Tray 1 Size Sensor J115-2 (+) J115-3 (-)Is the voltage +3.3VDC?Yes NoUsing the wire network from Chapter 7, check the 3.3VDC circuits to Tray1 Paper Size Sensor. (WN 7.3.3+3.3VDC)Check for malfunctioning paper guide, poor contact caused by bending inthe projection that pushes the switch, andif there is no problem, change the Tray 1 Paper Size Sensor.Check for cut wires, poor connections from Tray 1 Paper Size SensorJ115-2 to I/F PWB J534-B14 .Change the following parts in order:I/F PWB (PL9.1)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-271 TRAY 2 PAPER SIZE SENSOR BROKENEXPLANATIONAn abnormal AD value was detected from the Tray 2 Paper Size Sensor.Refer to BSD: CH7.2 CH7.13A

ProcedureSet Tray 2 in the machine.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 NoBetween Tray 2 Paper Size Sensor J816-2 (3T: J816-2 TT: J816-2 ) (+) GND(-)Is the voltage the same as that in the Tray 2 Size Sensor Output Table inscribed in BSD: CH7.2?Yes NoBetween Tray 2 Paper Size Sensor J816-1 (3T: J816-1 TT: J816-1 ) (+)J816-3 (3T: J816-3 TT: J816-3)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the 5VDC circuits to Tray 2Paper Size Sensor J816-1 (3T:J816-1 TT: J816-1 ).(WN 7.3.3 +5VDC-2)Check for malfunctioning paper guide, poor contact caused by bending inthe projection that pushes the switch, andif 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 SensorJ816-2 (3T: J816-2 TT: J816-2 ) and Tray ModulePWB J546-8 (1T: J546-8 3T: J546-8, TT: J546-8 )Change the following parts in order: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)EXPLANATIONAn abnormal AD value was detected from the Tray 3 Paper Size Sensor.Refer to BSD: CH7.3 CH7.13AProcedureSet Tray 3 in the machine.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 NoBetween Tray 3 Paper Size Sensor J820-2 (3T: J820-1 TT: J820-1 ) (+) GND(-)Is the voltage the same as that in the Tray 3 Size Sensor Output Table inscribed in BSD: CH7.3?Yes NoBetween Tray 3 Paper Size Sensor J820-1 (3T: J820-1 TT: J820-1 ) (+)J820-3 (3T: J820-3 TT: J820-3)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits to Tray3 Paper Size Sensor J820-1(3T: J820-1 TT: J820-1 ).(WN 7.3.6 +5VDC-2)Check for malfunctioning paper guide, poor contact caused by bending inthe projection that pushes the switch, andif there is no problem, change the Tray 3 Paper Size Sensor. (PL15.1)Check for cut wires, poor connections between Tray 3 Paper Size SensorJ820-2 (3T: J820-2 TT: J820-2 ) and Tray ModulePWB J548-11 (3T: J548-11, TT: J548-11)Change the following parts in order:TRAY MODULE PWB (PL15.9)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-273 TRAY 4 PAPER SIZE SENSOR BROKEN (3TM)EXPLANATIONAn abnormal AD value was detected from the Tray 4 Paper Size Sensor.Refer to BSD: CH7.5 CH7.13AProcedureSet Tray 4 in the machine.Between Tray Module PWB J548-5 (3T: J548-5 , TT: J548-5 ) (+) GND (-)Is the voltage the same as that in the Tray 4 Paper Size Sensor Output Table inscribed in BSD:CH7.5?Yes NoBetween Tray 4 Paper Size Sensor J824-2 (3T: J824-2 TT: J824-2 ) (+) GND(-)Is the voltage the same as that in the Tray 4 Size Sensor Output Table inscribed in BSD: CH7.5?Yes NoBetween Tray 4 Paper Size Sensor J824-1 (3T: J824-1 TT: J824-1 ) (+)J824-3 (3T: J824-3 TT: J824-3)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits to Tray4 Paper Size Sensor J824-1(3T: J824-1 TT: J824-1 ).(WN 7.3.6 +5VDC-2)Check for malfunctioning paper guide, poor contact caused by bending inthe projection that pushes the switch, andif there is no problem, change the Tray 4 Paper Size Sensor. (PL15.1)Check for cut wires, poor connections between Tray 4 Paper Size SensorJ824-2 (3T: J824-2 TT: J824-2 ) and Tray ModulePWB J548-5 (3T: J548-5 TT: J548-5)Change the following parts in order:TRAY MODULE PWB (PL15.9)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-274 MSI PAPER SIZE SENSOR BROKENEXPLANATIONThe Connector for MSI Paper Size Sensor is off.Refer to BSD: CH7.11 CH7.11ProcedureCheck for poor contact, cut wires, and displacement of the connectorfrom the MSI Paper Size Sensor to the base, and if thereare 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)EXPLANATIONAn abnormal AD value was detected from the Tray 3 Paper Size Sensor.Refer to BSD: CH7.4 CH7.13AProcedureSet Tray 3 in the machine.Between Tray Module PWB J548-11 (3T: J548-11 , TT: J548-11) (+) GND (-)Is the voltage the same as that in the Tray 3 Paper Size Sensor Output Table inscribed in BSD:CH7.4?Yes NoBetween Tray 3 Paper Size Sensor J820-2 (3T: J820-2 TT: J820-2 ) (+) GND(-)Is the voltage the same as that in the Tray 3 Size Sensor Output Table inscribed in BSD: CH7.4?Yes NoBetween Tray 3 Paper Size Sensor J820-1 (3T: J820-1 TT: J820-1 )(+)J820-3 (3T: J820-3 TT: J820-3) (-)Is the voltage +5VDC?

Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits to Tray3 Paper Size Sensor J820-1(3T: J820-1 TT: J820-1 ).(WN 7.3.6 +5VDC-2)Check for malfunctioning paper guide, poor contact caused by bending inthe projection that pushes the switch, andif there is no problem, change the Tray 3 Paper Size Sensor. (PL16.1)Check for cut wires, poor connections between Tray 3 Paper Size SensorJ820-2 (3T: J820-2 TT: J820-2 ) and Tray ModulePWB J548-11 (3T: J548-11, TT: J548-11)Change the following parts successively:TRAY MODULE PWB (PL16.9)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-277 TRAY 4 PAPER SIZE SENSOR BROKEN (TTM)EXPLANATIONAn abnormal AD value was detected from the Tray 4 Paper Size Sensor.Refer to BSD: CH7.6 CH7.13AProcedureSet Tray 4 in the machine.Between Tray Module PWB J548-5 (3T: J548-5 , TT: J548-5) (+) GND (-)Is the voltage the same as that in the Tray 4 Paper Size Sensor Output Table inscribed in BSD:CH7.6?Yes NoBetween Tray 4 Paper Size Sensor J8240-2 (3T: J824-2 TT: J824-2 ) (+)GND (-)Is the voltage the same as that in the Tray 4 Size Sensor Output Table inscribed in BSD: CH7.6?Yes NoBetween Tray 4 Paper Size Sensor J824-1 (3T: J824-1 TT: J824-1 )(+)J824-3 (3T: J824-3 TT: J824-3) (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits to Tray4 Paper Size Sensor J824-1(3T: J824-1 TT: J824-1 ).(WN 7.3.6 +5VDC-2)Check for malfunctioning paper guide, poor contact caused by bending inthe projection that pushes the switch, andif there is no problem, change the Tray 4 Paper Size Sensor. (PL16.1)Check for cut wires, poor connections between Tray 4 Paper Size SensorJ824-2 (3T: J824-2 TT: J824-2 ) and Tray ModulePWB J548-5 (3T: J548-5, TT: J548-5)Change the following parts successively:TRAY MODULE PWB (PL16.15)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-281 TRAY 1 LIFT UP FAILEXPLANATIONThe Tray 1 Level Sensor does not come on (shade) with in the prescribedtime from lift up.Refer to BSD: CH7.7 CH7.13BProcedureSet Tray 1. Execute DC330 [08-002].Does Tray 1’s Bottom Plate lift up?Yes NoWhen executing DC330 [08-002], does the Tray 1 Feed/Liftup Motor attempt to rotate?Yes NoBetween Tray 1 Feed/Lift Up Motor J205-3 , 4 (+) GND (-)Is the voltage +24VDC?

Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theTray 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-2 to I/F PWB J535-B5.From Tray 1 Feed/Liftup Motor J205-5 to I/F PWB J535-B2.From Tray 1 Feed/Liftup Motor J205-6 to I/F PWB J535-B1Are all of the resistances 1 or below?Yes NoCheck 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 bottomplate rise and fall smoothly?Push Tray 1 carefully. Does the moving-transmission part [Translator’sNote: unclear] fit smoothly?Execute DC330 [07-116]. Pull out Tray 1, turn Tray 1 Level Sensoron/off..Does the display change to H/L?Yes NoUsing a Poor-Permeability-Sensing FIP, fix the Tray 1 Level Sensor.(PL2.4)Change the following parts successively:TRAY MODULE PWB (PL9.1)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-282 TRAY 2 LIFT UP FAILEXPLANATIONThe Tray 2 Level Sensor does not come on (shade) with in the prescribedtime from lift up.Refer to BSD: CH7.8 CH7.13BProcedureSet Tray 2. Execute DC330 [08-004].Does Tray 2’s Bottom Plate lift up?Yes NoWhen executing DC330 [08-004], does the Tray 2 Feed/Liftup Motor attempt to rotate?Yes NoBetween Tray 2 Feed/Lift Up Motor J205-3 , 4 (3T: J827-3, 4, TT: J827-3,4) (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theTray 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.Check the following:From Tray 2 Feed/Liftup Motor J827-1 (3T: J827-1, TT: J827-1) to TrayModule PWB J547-6 (1T:J547-6,3T: J547-6, TT: J547-6).From Tray 2 Feed/Liftup Motor J827-2 (3T: J827-2, TT: J827-2) to TrayModule PWB J547-5 (1T:J547-5,3T: J547-5, TT: J547-5).From Tray 2 Feed/Liftup Motor J827-5 (3T: J827-5, TT: J827-5) to TrayModule PWB J547-2 (1T:J547-2,3T: J547-2, TT: J547-2).From Tray 2 Feed/Liftup Motor J827-6 (3T: J827-6, TT: J827-6) to TrayModule PWB J547-1 (1T:J547-1,3T: J547-1, TT: J547-1).

Are all of the resistances 1 or below?Yes NoCheck for severed lines or poor contact in wires not 1 or below.Change Tray 2 Feed/Liftup Motor (PL14.3 / PL15.3 / PL16.7), and TrayModule PWB (PL14.5 / PL15.9 / PL16.15)successively.Check the following moving parts:Turn the gear to the rear of Tray 2 with your hand. Does the bottomplate rise and fall smoothly?.Push Tray 1 carefully. Does the moving-transmission part [Translator’sNote: unclear] fit smoothly?Execute DC330 [07-117]. Pull out Tray 2, turn Tray 2 Level Sensoron/off.Does the display change to H/L?Yes NoUsing a Poor-Permeability-Sensing FIP, fix the Tray 2 Level Sensor.(PL14.3 / PL15.3 / PL16.7)Change the following parts successively: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)EXPLANATIONThe Tray 3 Level Sensor does not come on (shade) with in the prescribedtime from lift up.Refer to BSD: CH7.9 CH7.13BProcedureSet Tray 3. Execute DC330 [08-006].Does Tray 3’s Bottom Plate lift up?Yes NoWhen executing DC330 [08-006], does the Tray 3 Feed/Liftup Motor attempt to rotate?Yes NoBetween Tray 3 Feed/Lift Up Motor J828-3 ,4 (3T: J828-3, 4, TT: J828-3,4) (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theTray 3 Feed/LiftUp Motor J828-3,4(3T: J828-3, 4, TT: J828-3, 4) . (WN 7.3.13 +24VDC-3)Turn off the power.Check the following:From Tray 3 Feed/Liftup Motor J828-1 (3T: J828-1, TT: J828-1) to TrayModule PWB J549-B6 (3T:J549-B6, TT: J547-6).From Tray 3 Feed/Liftup Motor J828-2 (3T: J828-2, TT: J828-2) to TrayModule PWB J549-B5 (3T:J549-B5, TT: J549-B5).From Tray 3 Feed/Liftup Motor J828-5 (3T: J828-5, TT: J828-5) to TrayModule PWB J549-B2 (3T:J549-B2, TT: J549-B2).From Tray 3 Feed/Liftup Motor J828-6 (3T: J828-6, TT: J828-6) to TrayModule PWB J549-B1 (3T:J549-B1, TT: J549-B1).Are all of the resistances 1 or below?Yes NoCheck for severed lines or poor contact in wires not 1 or below.Change Tray 3 Feed/Liftup Motor (PL15.5), and Tray Module PWB (PL15.9)successively.Check the following moving parts:Turn the gear to the rear of Tray 3 with your hand. Does the bottomplate rise and fall smoothly?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.Does the display change to H/L?Yes NoUsing a Poor-Permeability-Sensing FIP, fix the Tray 3 Level Sensor.(PL15.5)Change the following parts successively:TRAY MODULE PWB (PL15.9)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-284 TRAY 4 LIFT UP FAIL (3TM)EXPLANATIONThe Tray 4 Level Sensor does not come on (shade) with in the prescribedtime from lift up.Refer to BSD: CH7.10 CH7.13BProcedureSet Tray 4. Execute DC330 [08-008].Does Tray 3’s Bottom Plate lift up?Yes NoWhen executing DC330 [08-008], does the Tray 4 Feed/Liftup Motor attempt to rotate?Yes NoBetween Tray 4 Feed/Lift Up Motor J829-3 ,4 (3T: J829-3, 4, TT: J829-3,4) (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theTray 4 Feed/LiftUp Motor J829-3,4(3T: J829-3, 4, TT: J829-3, 4) . (WN 7.3.13 +24VDC-3)Turn off the power.Check the following:From Tray 4 Feed/Liftup Motor J829-1 (3T: J829-1, TT: J829-1) to TrayModule PWB J549-A6 (3T:J549-A6, TT: J549-A6).From Tray 4 Feed/Liftup Motor J829-2 (3T: J829-2, TT: J829-2) to TrayModule PWB J549-A5 (3T:J549-A5, TT: J549-A5).From Tray 4 Feed/Liftup Motor J829-5 (3T: J829-5, TT: J829-5) to TrayModule PWB J549-A2 (3T:J549-A2, TT: J549-A2).From Tray 4 Feed/Liftup Motor J829-6 (3T: J829-6, TT: J829-6) to TrayModule PWB J549-A1 (3T:J549-A1, TT: J549-A1).Are all of the resistances 1 or below?Yes NoCheck for severed lines or poor contact in wires not 1 or below.Change Tray 3 Feed/Liftup Motor (PL15.7), and Tray Module PWB (PL15.9)successively.Check the following moving parts:Turn the gear to the rear of Tray 4 with your hand. Does the bottomplate rise and fall smoothly?Push Tray 4 carefully. Does the moving-transmission part [Translator’sNote: unclear] fit smoothly?.Execute DC330 [07-119].Pull out Tray 4, turn Tray 4 Level Sensor on/off.Does the display change to H/L?Yes NoUsing a Poor-Permeability-Sensing FIP, fix the Tray 3 Level Sensor.(PL15.5)Change the following parts successively:TRAY MODULE PWB (PL15.9)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-291 TRAY 3 LIFT UP FAIL (TTM)EXPLANATIONThe Tray 3 Level Sensor does not come on (shade) with in the prescribedtime from lift up.Refer to BSD: CH7.9 CH7.13BProcedureSet Tray 3. Execute DC330 [08-006].Does Tray 3’s Bottom Plate lift up?Yes NoWhen executing DC330 [08-006], does the Tray 3 Feed/Liftup Motor attempt to rotate?Yes NoBetween Tray 3 Feed/Lift Up Motor J828-3 ,4 (3T: J828-3, 4, TT: J828-3,4) (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theTray 3 Feed/LiftUp Motor J828-3,4(3T: J828-3, 4, TT: J828-3, 4) . (WN 7.3.13 +24VDC-3)Turn off the power.Check the following:From Tray 3 Feed/Liftup Motor J828-1 (3T: J828-1, TT: J828-1) to TrayModule PWB J549-B6 (3T:J549-B6, TT: J549-B6).From Tray 3 Feed/Liftup Motor J828-2 (3T: J8282, TT: J828-2) to TrayModule PWB J549-B5 (3T:J549-B5, TT: J549-B5).From Tray 3 Feed/Liftup Motor J828-5 (3T: J828-5, TT: J828-5) to TrayModule PWB J549-B2 (3T:J549-B2, TT: J549-B2).From Tray 3 Feed/Liftup Motor J828-6 (3T: J828-6, TT: J828-6) to TrayModule PWB J549-B1 (3T:J549-B1, TT: J549-B1).Are all of the resistances 1 or below?Yes NoCheck for severed lines or poor contact in wires not 1 or below.Change Tray 3 Feed/Liftup Motor (PL16.9), and Tray Module PWB (PL16.15)successively.Check the following moving parts:Turn the gear to the rear of Tray 3 with your hand. Does the bottomplate rise and fall smoothly?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.Does the display change to H/L?Yes NoUsing a Poor-Permeability-Sensing FIP, fix the Tray 3 Level Sensor.(PL16.9)Change the following parts successively:TRAY MODULE PWB (PL16.15)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-293 TRAY 4 LIFT UP FAIL (TTM)EXPLANATIONThe Tray 4 Level Sensor does not come on (shade) with in the prescribedtime from lift up.Refer to BSD: CH7.10 CH7.13BProcedureSet Tray 4. Execute DC330 [08-008].Does Tray 4’s Bottom Plate lift up?Yes No

When executing DC330 [08-008], does the Tray 4 Feed/Liftup Motor attempt to rotate?Yes NoBetween Tray 4 Feed/Lift Up Motor J829-3 ,4 (3T: J829-3, 4, TT: J829-3,4) (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theTray 4 Feed/LiftUp Motor J829-3,4(3T: J829-3, 4, TT: J829-3, 4) . (WN 7.3.13 +24VDC-3)Turn off the power.Check the following:From Tray 4 Feed/Liftup Motor J829-1 (3T: J829-1, TT: J829-1) to TrayModule PWB J549-A6 (3T:J549-A6, TT: J549-A6).From Tray 4 Feed/Liftup Motor J829-2 (3T: J8289, TT: J829-2) to TrayModule PWB J549-A5 (3T:J549-A5, TT: J549-A5).From Tray 4 Feed/Liftup Motor J829-5 (3T: J829-5, TT: J829-5) to TrayModule PWB J549-A2 (3T:J549-A2, TT: J549-A2).From Tray 4 Feed/Liftup Motor J829-6 (3T: J829-6, TT: J829-6) to TrayModule PWB J549-A1 (3T:J549-A1, TT: J549-A1).Are all of the resistances 1 or below?Yes NoCheck for severed lines or poor contact in wires not 1 or below.Change Tray 4 Feed/Liftup Motor (PL16.11), and Tray Module PWB (PL16.15)successively.Check the following moving parts:Turn the gear to the rear of Tray 4 with your hand. Does the bottomplate rise and fall smoothly?Push Tray 4 carefully. Does the moving-transmission part fit smoothly?.Execute DC330 [07-119].Pull out Tray 4, turn Tray 4 Level Sensor on/off.Does the display change to H/L?Yes NoUsing a Poor-Permeability-Sensing FIP, fix the Tray 4 Level Sensor.(PL16.11)Change the following parts successively:TRAY MODULE PWB (PL16.15)MCU PWB (PL13.1)ESS PWB (PL13.1 ).

07-297 ALL TRAY LIFT UP FAILEXPLANATIONNone of the Tray Level Sensors comes on within the prescribed time.Refer to BSD: CH7.7 CH7.8 CH7.9 CH7.10 CH7.13ProcedureCheck the DC122 Shutdown HistoryIs any of the following generated? : 07-282, 07-283, 07-284, 07-291, 17-293Yes NoSuccessively 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 MISMATCHEXPLANATIONThe On/Off button for the Tray 1 Paper Size Sensor is outside of thesize that can be detected.Refer to BSD: CH7.1 CH7.13Procedure

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

07-931 TRAY 2 PAPER SIZE MISMATCHEXPLANATIONThe On/Off button for the Tray 2 Paper Size Sensor is outside of thesize that can be detected.Refer to BSD: CH7.2 CH7.13AProcedureIf it is not fixed by changing the size of the paper, execute Procedurefor FIP 07-271..

07-932 TRAY 3 PAPER SIZE MISMATCHEXPLANATIONThe On/Off button for the Tray 3 Paper Size Sensor is outside of thesize that can be detected.Refer to BSD: CH7.3 CH7.4 CH7.13AProcedureIf it is not fixed by changing the size of the paper, execute theProcedure for either FIP 07-272. (3TM), or07-276 (TTM).

07-933 TRAY 4 PAPER SIZE MISMATCHEXPLANATIONThe On/Off button for the Tray 4 Paper Size Sensor is outside of thesize that can be detected.Refer to BSD: CH7.5 CH7.6 CH7.13AProcedureIf it is not fixed by changing the size of the paper, execute theProcedure for either FIP 07-273. (3TM), or07-277 (TTM).

07-935 JOB CANNOT BE CONTINUED FAILEXPLANATIONDuring automatic tray-change processing time, there is no tray to thatcan be changed to, and the job cannot continue.ProcedureRefer to the Instruction Manual..

07-959 MSI PAPER MISMATCH 1 (WHEN SOMETHING OTHER THAN AN IMARI-EXCLUSIVE-USE SHEET ISDETECTED)EXPLANATIONAn Imari-exclusive sheet is not being used.Refer to BSD: CH8.8 CH8.9Check the following: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?

ProcedureBlock the Paper-Detecting Partfor Overhead Projector Sensor “ R” withnormal paper.Between I/F PWB J534-A4 (+) GND (-)Is the voltage +5VDC?Yes NoUsing 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 DETECTEDWITH NORMAL ORTHICK PAPER)EXPLANATIONThe UI is set for normal or thick paper, but a sheet made of somethingother than paper is detected.Refer to BSD: CH8.8 CH8.9Check the following:Is the sheet set the same as that selected on the UI?Are there any foreign substances by the Sensor Detector position?

ProcedureBlock the Paper-Detecting Partfor Overhead Projector Sensor “ R” withnormal paper.Between I/F PWB J534-A4 (+) GND (-)Is the voltage +5VDC?Yes NoUsing 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-969 FULL PAPER STACK FAILTEXPLANATIONThe Full-Paper-Stack Sensor detects a full Face-Down Tray continuouslyfor10 seconds.Refer to BSD: CH10.3 CH10.4B CH10.8Check the following:Has the paper on top of the Face-Down Tray been eliminated?Is the Full-Paper-Sack-Sensor Actuator malfunctioning, or are thereany foreign substances within it?ProcedureExecute DC330 [10-102]. Move the Full-Paper-Stack-Sensor Actuator up anddown.Did the display change to H/L?Yes NoUsing a Malfunctioning Permeable Sensor FIP, fix the Full-Paper-StackSensor. (PL2.10 / PL2.11)Change the following parts in succession: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)EXPLANATIONThe Take-Away Sensor fails to detect paper fed from Tray 3 within theprescribed 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 SensorMalfunctioning Take-Away Motor 1Wear, failure to rotate of Take-Away Roll 2Wear, failure to rotate of take-Away Roll 3

Poor paper advancement due to presence of foreign objects within thepaper 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)EXPLANATIONThe Take-Away Sensor fails to detect paper fed from Tray 4 within theprescribed 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 SensorMalfunctioning Take-Away Motor 1Wear, failure to rotate of Take-Away Roll 2Wear, failure to rotate of take-Away Roll 3Wear, failure to rotate of take-Away Roll 4Poor paper advancement due to presence of foreign objects within thepaper 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-151 TAKE-AWAY SENSOR ON JAM (FROM TTM TRAY 3 FEED)EXPLANATIONThe Take-Away Sensor fails to detect paper fed from Tray 3 within theprescribed period of time.DC330 Code to check:[08-106] Take-Away Sensor[08-029 to 08-036] Take-Away Motor 1 (TTM)Items to check:Malfunctioning Take-Away SensorMalfunctioning Take-Away Motor 1Wear, failure to rotate of Take-Away Roll 2Wear, failure to rotate of take-Away Roll 3Poor paper advancement due to presence of foreign objects within thepaper 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-152 TAKE-AWAY SENSOR ON JAM (FROM TTM TRAY 4 FEED)EXPLANATIONThe Take-Away Sensor fails to detect paper fed from Tray 4 within theprescribed period of time.DC330 Code to check:[08-106] Take-Away Sensor[08-029 to 08-036] Take-Away Motor 1 (TTM)[08-047 to 08-048] Take-Away Motor 2 (TTM)Items to check:Malfunctioning Take-Away SensorMalfunctioning Take-Away Motor 1Malfunctioning Take-Away Motor 2Wear, failure to rotate of Take-Away Roll 2Wear, failure to rotate of take-Away Roll 3Wear, failure to rotate of take-Away Roll 3Poor paper advancement due to presence of foreign objects within thepaper 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-164 POB SENSOR ON JAMEXPLANATIONThe POB Sensor fails to detect paper from the REGI Clutch within theprescribed period of time.DC330 Code to check:[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 BTRMalfunctioning POB SensorWear, failure to rotate of REGI RollMalfunctioning REGI ClutchPoor paper advancement due to presence of foreign objects within thepaper path, or the presence of “ flash,” etc.Use of non-spec. paper (refer to Chapter 6 “ Specs” )Malfunctioning I/F PWB, MCU PWB, ESS PWB.

08-175 POB SENSOR ON JAM (FROM MSI FEED)EXPLANATIONThe REGI Sensor fails to detect paper fed from the MSI within theprescribed period of time.DC330 Code to check:[08-104] REGI Sensor[04-004] Main Motor[07-003] MSI Misfeed SolenoidItems to check:Main Motor malfunctionREGI Sensor malfunctionMSI Feed Solenoid malfunctionWear, failure to rotate of MSI Feed RollWear, failure to rotate of MSI Take-Away RollPoor paper advancement due to presence of foreign objects within thepaper path, or the presence of “ flash,” etc.Use of non-spec. paper (refer to Chapter 6 “ Specs” )Malfunctioning I/F PWB, MCU PWB, ESS PWB.

08-176 REGI SENSOR ON JAM (FROM TRAY FEED)EXPLANATIONThe REGI Sensor fails to detect paper fed from each Tray within theprescribed period of time.DC330 Code to check:[08-104] REGI Sensor[08-038] Take-Away Clutch[04-004] Main MotorItems to check:Main Motor malfunctionREGI Sensor malfunctionTake-Away Clutch malfunction

Wear, failure to rotate of Take-Away Roll 1Poor paper advancement due to presence of foreign objects within thepaper path, or the presence of “ flash,” etc.Use of non-spec. paper (refer to Chapter 6 “ Specs” )Malfunctioning I/F PWB, MCU PWB, ESS PWB

08-180 REGI SENSOR ON JAM (FROM DUPLEX FEED)EXPLANATIONThe REGI Sensor fails to detect paper fed from the Duplex Feed withinthe prescribed period of time.DC330 Code to check:[08-104] REGI Sensor[08-009 to 08-012] Duplex Motor[08-046] Duplex Gate Solenoid[08-043] Inverter Reverse Clutch[08-046] Main MotorItems to check:Duplex Motor malfunctionMain Motor malfunctionInverter Reverse Clutch malfunctionDuplex Gate Solenoid malfunctionREGI Sensor malfunctionWear, failure to rotate of Exit Roll, Transport Roll, Wait Roll.Poor paper advancement due to presence of foreign objects within thepaper path, or the presence of “ flash,” etc.Use of non-spec. paper (refer to Chapter 6 “ Specs” )Malfunctioning Duplex PWB, I/F PWB, MCU PWB, ESS PWB.

08-181 REGI SENSOR ON JAM (FROM WAIT SENSOR)EXPLANATIONThe REGI Sensor fails to detect paper fed from the Duplex Wait Sensorwithin the prescribed period of time.DC330 Code to check:[08-104] REGI Sensor[08-105] Duplex Wait Sensor[08-009 to 08-012] Duplex MotorItems to check:Duplex Motor malfunctionRegi Sensor malfunctionDuplex Wait Sensor malfunctionDuplex Gate Solenoid malfunctionWear, failure to rotate of Transport Roll, Wait Roll.Poor paper advancement due to presence of foreign objects within thepaper path, or the presence of “ flash,” etc.Use of non-spec. paper (refer to Chapter 6 “ Specs” )Malfunctioning Duplex PWB, I/F PWB, MCU PWB, ESS PWB.

08-184 REGI SENSOR OFF JAMEXPLANATIONThe Fuser Exit Switch fails to detect paper fed from the from the RegiClutch ON within the prescribed period of time.DC330 Code to check:[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 malfunctionWear, 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 ClutchPoor paper advancement due to presence of foreign objects within thepaper path, or the presence of “ flash,” etc.Use of non-spec. paper (refer to Chapter 6 “ Specs” )Malfunctioning I/F PWB, MCU PWB, ESS PWB.

08-620 REGICON TEMP SENSOR FAILEXPLANATIONOutput of the Enviornment Sensor “ A” exceeds the range of 20-60degrees.WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Refer to BSD: Ch9.14 CH9.27EProcedureTurn off the power. Check the following wires and look for poor contact.1. Environment Sensor J255-1 from MCU PWB J404-A132. Environment Sensor J255-3 from MCU PWB J404-A113. Environment Sensor J255-4 from MCU PWB J404-A10Is any of the resistance values 1 • or less?Yes NoCheck for severed lines and poor connections in wires of 1 or less.Remove Environment Sensor J255Is the resistance betweeen Environment Sensor J255-3 and J255-4 6K to20K ?Yes NoChange 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)EXPLANATIONWhen the A-1 Patch is detected, the XSO revised set value for the resultof the calculation (either Y, M or C) exceeds the setrange (0 to 472 on the NVM Value).WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-623 REGICON DATA OVERFLOW FAIL (A 2 PATCH-Y)

EXPLANATIONWhen the A-2 Patch is detected, the YSO revised set value for the resultof the calculation (either Y, M or C) exceeds the setrange (0 to 474 on the NVM Value).WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-624 REGICON SAMPLE BLOCK FAIL (A1 PATCH-REAR)EXPLANATIONWhen the A-2 Patch is detected, the MAG revised set value for the resultof the calculation (either Y, M or C) exceeds theset range (0 to 1432 on the NVM Value).WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-625 REGICON SAMPLE BLOCK FAIL (A1 PATCH-REAR)EXPLANATIONWhen the A-1 (IN) Patch is detected, the prescribed sample block numberwas not obtained.WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-626 REGICON SAMPLE BLOCK FAIL (A1 PATCH-FRONT)EXPLANATIONWhen the A-1 (OUT) Patch is detected, the prescribed sample block numberwas not obtained.WARNING

This failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-627 REGICON SAMPLE LATERAL FAIL (A1 PATCH-REAR)EXPLANATIONWhen the A-1 (IN) Patch is detected, the principal scanning position ofthe CYAN color, which serves as the standard, isabnormal. (The position of the CYAN pattern’s central point is skewedmore than plus/minus 500 u m.)WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-628 REGICON SAMPLE LATERAL FAIL (A1 PATCH-FRONT)EXPLANATIONWhen the A-1 (OUT) Patch is detected, the principal scanning position ofthe CYAN color, which serves as the standard, isabnormal. (The position of the CYAN pattern’s central point is skewedmore than plus/minus 500 u m.)WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, was the same FAILgenerated?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 contactbetween the connectors.4. Dirty or damaged IBT Belt, Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-629 REGICON SKEW FAIL (A1 PATCH-Y)EXPLANATIONWhen the A-1 Patch is detected, the relative skew vis-à-vis the CYANcolor exceeds the prescribed limit.WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop the

machine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, output the 4C gridchart from the DC612; is the skew of the colorage withinthe prescribed limits?2. Dirty detectors in MOB Sensor 1 and 2; severed wires, poor contactbetween the connectors.3. Dirty or damaged IBT Belt4. Dirty or damaged Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-630 REGICON SKEW FAIL (A1 PATCH-M)EXPLANATIONWhen the A-1 Patch is detected, the relative skew vis-à-vis the CYANcolor exceeds the prescribed limit.WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, output the 4C gridchart from the DC612; is the skew of the colorage withinthe prescribed limits?2. Dirty detectors in MOB Sensor 1 and 2; severed wires, poor contactbetween the connectors.3. Dirty or damaged IBT Belt4. Dirty or damaged Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-631 REGICON SKEW FAIL (A1 PATCH-K)EXPLANATIONWhen the A-1 Patch is detected, the relative skew vis-à-vis the CYANcolor exceeds the prescribed limit.WARNINGThis failure is a hidden failure. Thus, in the custom mode used by thecustomer, the generation of a “ FAIL” does not stop themachine, and the FAIL code is not displayed on the UI, so copy dischargeis possible.Items to check:1. After executing the DC685 REGICON Set-up Cycle, output the 4C gridchart from the DC612; is the skew of the colorage withinthe prescribed limits?2. Dirty detectors in MOB Sensor 1 and 2; severed wires, poor contactbetween the connectors.3. Dirty or damaged IBT Belt4. Dirty or damaged Drum5. Warped frame6. Bad MCU PWB, ESS PWB, ROS ASSY.

08-900 STATIC JAMEXPLANATIONWhen the power is turned on and all of the interlocks are closed, theSensor detects paper on the paper conveyance path.Items to check:1. Check to see whether the voltage for the power switch has decreased2. Check for any severed circuit lines or poor contact between sensorsalong the paper-conveyance path and each base.3. Check for any foreign matter on the paper-conveyance path, and checkfor any jammed paper that might have been forgotten

4. Dirty detectors on the Reflexive Sensor, snagged actuators on thepermeable Sensors5. Defective Tray Module PWB, I/F PWB, MCU PWB, ESS PWB.

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

BTR Retract Motor?Yes NoBetween I/F PWB J532-A3 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theI/F PWB J532-A3. (WN 7.3.13 +24VDC-1)Check for broken wires, poor contact from I/F PWB J532 thru 2 nd RetractMotor J216.Are there any broken wires or poor contacts?Yes NoChange 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 wellas the Sensor actuator; if there are no problems, change theMCU PWB. (PL13.1 ).

009-343 2 ND BTR RETRACT FAILEXPLANATIONRetract not completed within prescribed time limit from 2 nd BTR MotorON.Refer to BSD: CH9.21A. CH9.27AProcedureExecute DC330 [009-200].Open the Left Cover, turn the 2 nd BTR Retract Sensor on/off with paper.Does the display change to H/LYes NoUsing an all-purpose Permeable Sensor FIP, fix the 2 ND BTR RetractSensor. (PL2.9)Close the Left Cover, execute DC330 [009-051] and [009-052].Is there a rotating noise from the 2nd

BTR Retract Motor?Yes NoBetween I/F PWB J532-A3 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits to theI/F PWB J532-A3. (WN 7.3.11 +24VDC-1)Check for broken wires, poor contact from I/F PWB J532 thru 2 nd RetractMotor 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 wellas the Sensor actuator; if there are no problems, change theMCU PWB. (PL13.1 ).

009-350 IBT HOME SENSOR FAILEXPLANATIONA Home detection signal was generated by the IBT Home Sensor before theIBT made one rotation.Refer to BSD: CH9.16. CH9.27AProcedureCheck the following items:Pieces of paper or metal in the detection positionSevered wires or poor contact from IBT Home Sensor to I/F PWBLeak in the HVPSIf there is no problem, change the IBT Home SensorIf that doesn’t work, change the MCU PWB. (PL13.1 ).

009-351 DRIVE LOGIC FAILEXPLANATIONMalfunctioning IBT Belt.Refer to BSD: CH9.16 CH9.27AProcedureIs the Edge Sensor actuator touching the Belt?Yes NoCheck the installation of the actuator.Turn on the power. Between I/F PWB J533-B2 (+) GND (-)Is the voltage between +3VDC and +1VDC?Yes NoBetween I/F PWB J532-B1 (+) J533-B3 (-)Is the voltage +5VDC?Yes NoBetween J533-B2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken lines, poor contact from I/F PWB J533 to IBT EdgeSensor J119, and if there are noproblems, 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 EdgeSensor J119-2Change the IBT Edge Sensor (PL5.4)Between I/F PWB J530-B7 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up tothe 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 NoCheck for broken lines, poor contact from I/F PWB J530 to IBT SteeringMotor J207.Are there any broken lines or poor contacts?Yes NoChange the MCU PWB. (PL13.1) and if that doesn’t work, change the I/FPWB (PL9.1) and change the IBTSteering 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 FAILEXPLANATIONBreakdown of the Full Toner SensorRefer to BSD: CH9.26 CH9.27EProcedureRemove the Full Toner Sensor from the bottle, and execute DC330 [009-150]Turn the Full Toner Sensor on/off with paper.Did the display change to H/L?Yes NoUsing all-purpose Permeable Sensor FIP, fix the Full Toner Sensor.(PL4.1)Check for the presence of toner-stain paper and foreign objects; ifthere is no problem, change the MCU PWB. (PL13.1).

009-360 DRUM COMMUNICATION FAIL (Y)EXPLANATIONCommunication with the drum fails.Refer to BSD: CH9.2 CH9.27BProcedureExecute DC330 [009-150]Did the display change to H/L?Yes NoCheck the position of the Drum, and check to see whether there are anybroken wires or poor contact between Drum (Y) J151and 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)EXPLANATIONCommunication with the Drum fails.Refer to BSD: CH9.2 CH9.27BProcedureExecute DC330 [009-152]Did the display change to H/L?Yes NoCheck the position of the Drum, and check to see whether there are anybroken wires or poor contact between Drum (M)J152 and MCU PWB J405, and if there are no problems, change Drum (M).(PL4.1)Change the MCU PWB. (PL13.1).

009-362 DRUM COMMUNICATION FAIL (C)EXPLANATIONCommunication with the Drum fails.Refer to BSD: CH9.3 CH9.27BProcedureExecute DC330 [009-153]Did the display change to H/L?Yes NoCheck the position of the Drum, and check to see whether there are anybroken wires or poor contact between Drum (C) J154and MCU PWB J405, and if there are no problems, change Drum (C). (PL4.1)Change the MCU PWB. (PL13.1).

009-363 DRUM COMMUNICATION FAIL (K)EXPLANATIONCommunication with the Drum fails.

Refer to BSD: CH9.3 CH9.27BProcedureExecute DC330 [009-154]Did the display change to H/L?Yes NoCheck the position of the Drum, and check to see whether there are anybroken wires or poor contact between Drum (K) J153and MCU PWB J405, and if there are no problems, change Drum (K). (PL4.1)Change the MCU PWB. (PL13.1).

009-380 ATC SENSOR FAIL (Y)EXPLANATIONATC Sensor (Y) failure.NOTEIn order to resolve this fault, the value for DC131 [752-162] must clear“ 0” .Refer to BSD: CH9.3 CH9.27CProcedureExecute DC922 Tone Up/Down. (If this cannot be executed, changeDC131[752-123] to 4, then return to the original state aftertermination.)Is the ATC Sensor (Y) Fail judgment OK?Yes NoCheck the position of the ATC Sensor, and check to see whether there areany broken wires or poor contact between ATCSensor P129 and I/F PWB J534, and if there are no problems, change theATC Sensor. (PL6.2)Change the MCU PWB. (PL13.1).

009-381 ATC SENSOR FAIL (M)EXPLANATIONATC Sensor (M) failure.NOTEIn order to resolve this fault, the value for DC131 [752-163] must clear“ 0” .Refer to BSD: CH9.10 CH9.27CProcedureExecute DC922 Tone Up/Down. (If this cannot be executed, changeDC131[752-123] to 4, then return to the original state aftertermination.)Is the ATC Sensor (M) Fail judgment OK?Yes NoCheck the position of the ATC Sensor, and check to see whether there areany broken wires or poor contact between ATCSensor P130 and I/F PWB J534, and if there are no problems, change theATC Sensor. (PL6.2)Change the MCU PWB. (PL13.1).

009-382 ATC SENSOR FAIL (C)EXPLANATIONATC Sensor (C) failure.NOTEIn order to resolve this fault, the value for DC131 [752-164] must clear“ 0” .Refer to BSD: CH9.11 CH9.27CProcedureExecute DC922 Tone Up/Down. (If this cannot be executed, changeDC131[752-123] to 4, then return to the original state aftertermination.)Is the ATC Sensor (M) Fail judgment OK?Yes No

Check the position of the ATC Sensor, and check to see whether there areany broken wires or poor contact between ATCSensor P131 and I/F PWB J534, and if there are no problems, change theATC Sensor. (PL6.2)Change the MCU PWB. (PL13.1).

009-383 ATC SENSOR FAIL (K)EXPLANATIONATC Sensor (K) failure.NOTEIn order to resolve this fault, the value for DC131 [752-165] must clear“ 0” .Refer to BSD: CH9.12 CH9.27CProcedureExecute DC922 Tone Up/Down. (If this cannot be executed, changeDC131[752-123] to 4, then return to the original state aftertermination.)Is the ATC Sensor (K) Fail judgment OK?Yes NoCheck the position of the ATC Sensor, and check to see whether there areany broken wires or poor contact between ATCSensor P132 and I/F PWB J534, and if there are no problems, change theATC Sensor. (PL6.2)Change the MCU PWB. (PL13.1).

009-408 WASTE BOTTLE NEAR FULLEXPLANATIONThe Toner Collection Bottle is close to full.Refer to BSD: CH9.26 CH9.27EProcedureIs there any dirt from the toner or are there any foreign objects near the Full Toner SensorActuator?Yes NoClean it.Execute DC330[009-150].Is H displayed?Yes NoChange the MCU PWB. (PL13.1)Using an all-purpose Permeable Sensor FIP, fix the Full-Toner Sensor.(PL4.1).

009-410 WASTE BOTTLE NEAR FULLEXPLANATIONTiming for replenishment of yellow toner.Refer to BSD: CH9.8 CH9.9 CH9.13 CH9.14 CH9.27CProcedureIs there toner within the DEVE Unit, evenly distributed?Yes NoExecute DC330 [009-001].Does the Dispense Motor (Y) revolve?Yes NoUsing the all-purpose Motor-Doesn’t-Turn FIP, fix the Dispense Motor.(PL6.1)Check the toner-supply auger mechanismExecute DC922 Tone Up/Down.Is the ATC Sensor (Y) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P129 and I/FPWB 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 NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-)..Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079].MCU PWB J406-B1 (+) GND (-)Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ATCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ATCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Between DEVE Motor J232-7 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up tothe DEVE Motor J232-4. (WN 7.3.13 +24VDC-3)Between DEVE Motor J232-7 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up tothe DEVE Motor J232-7. (WN 7.3.13 +24VDC-3)Check for broken wires or poor contact between the DEVE Motor J232 andMCU PWB J407 and if there are no problems, change theDEVE Motor (PL1.1)Change the MCU PWB. (PL13.1).

009-411 TONER MAGENTA NEAR EMPTYEXPLANATIONTiming for replenishment of magenta toner.Refer to BSD: CH9.8 CH9.10 CH9. 13 CH9.14 CH9.27CProcedureIs there toner within the DEVE Unit, evenly distributed?Yes NoExecute DC330 [009-002].Does the Dispense Motor (M) revolve?Yes No

Using the all-purpose Motor-Doesn’t-Turn FIP, fix the Dispense Motor.(PL6.1)Check the toner-supply auger mechanismExecute DC922 Tone Up/Down.Is the ATC Sensor (M) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P130 and I/FPWB J534, and if there are no problems, change the ATC Sensor (PL6.2)Execute the DC934 ATC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Between DEVE Motor J232-4 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up tothe DEVE Motor J232-4. (WN 7.3.13 +24VDC-3)Between DEVE Motor J232-7 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up tothe DEVE Motor J232-7. (WN 7.3.6 +5VDC-2)Check for broken wires or poor contact between the DEVE Motor J232 andMCU PWB J407 and if there are no problems, change theDEVE Motor (PL1.1)Change the MCU PWB. (PL13.1).

009-412 TONER CYAN NEAR EMPTY

EXPLANATIONTiming for replenishment of cyan toner.Refer to BSD: CH9.8 CH9.11 CH9. 13 CH9.14 CH9.27CProcedureIs there toner within the DEVE Unit, evenly distributed?Yes NoExecute DC330 [009-003].Does the Dispense Motor (C) revolve?Yes NoUsing the all-purpose Motor-Doesn’t-Turn FIP, fix the Dispense Motor.(PL6.1)Check the toner-supply auger mechanismExecute DC922 Tone Up/Down.Is the ATC Sensor (C) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P131 and I/FPWB J534, and if there are no problems, change the ATC Sensor (PL6.2)Execute the DC934 ATC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Between DEVE Motor J232-4 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up tothe DEVE Motor J232-4. (WN 7.3.13 +24VDC-3)Between DEVE Motor J232-7 (+) GND (-).

Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up tothe DEVE Motor J232-7. (WN 7.3.6 +5VDC-2)Check for broken wires or poor contact between the DEVE Motor J232 andMCU PWB J407 and if there are no problems, change theDEVE Motor (PL1.1)Change the MCU PWB. (PL13.1).

009-413 TONER BLACK NEAR EMPTYEXPLANATIONTiming for replenishment of black toner.Refer to BSD: CH4.1 CH9.12 CH9. 13 CH9.14 CH9.27CProcedureIs there toner within the DEVE Unit, evenly distributed?Yes NoExecute DC330 [009-004].Does the Dispense Motor (B) revolve?Yes NoUsing the all-purpose Motor-Doesn’t-Turn FIP, fix the Dispense Motor.(PL6.1)Check the toner-supply auger mechanismExecute DC922 Tone Up/Down.Is the ATC Sensor (K) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P131 and I/FPWB J534, and if there are no problems, change the ATC Sensor (PL6.2)Execute the DC934 ATC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)

Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Execute DC330 [004-004].Did the main motor rotate?Yes NoBetween Main Motor J203-4 (+) GND (-)Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up tothe DEVE Motor J232-4. (WN 7.3.13+24VDC-3)Execute DC330 [004-004]Between DEVE Motor J203-1 (+) GND (-).Is the voltage 0 VDC?Yes NoExecute DC330 [004-004]Between MCU PWB J407-A1 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J407-A1 to MainMotor J203-1 and if thereare no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J407-A1 to MainMotor J203-1.Execute DC330 [004-004].Between Main Motor J203-2 (+) GND (-)Is the voltage 0 VDC?Yes NoExecute DC330 [004=004]Between Main Motor J203-2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J407-A2 to MainMotor J203-2 and if thereare no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J407-A2 to MainMotor J203-2.Change the Main Motor (PL1.1)Execute DC330 [009-013]Did the DEVE Clutch (K) function?Yes NoUsing an all-purpose Clutch-Doesn’t-Run FIP, fix the DEVE Clutch.(PL1.2)Change the MCU PWB. (PL13.1).

009-428 DRUM CARTRIDGE CHANGE SOON (K)EXPLANATION:It is almost time to change the DrumRefer to BSD: CH9.3 CH9.27BProcedureChange 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 DrumRefer to BSD: CH9.2 CH9.27BProcedureChange Drum (Y) (PL4.1), and if that doesn’t work, change MCU PWB(PL13.1)..

009-655 ADC PATCH FAIL (Y)EXPLANATIONWrong concentration on ADC Patch (Y)Refer to BSD: CH9.13 CH9.14 CH9.27DProcedureExecute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3).Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Is there toner in the DEVE Unit, distributed evenly?Yes NoExecute DC330 [009-001]Did the Dispense Motor (Y) turn?Yes NoUsing an all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor(PL6.1)Check the auger mechanism for toner supply.Check the following:Check the IBT Belt for damage, dirtiness, or poor cleaning.Poor installation of ADC Sensor UnitROS Shutter malfunction.If there is no problem, change the MCU PWB. (PL13.1).

009-657 ADC PATCH FAIL (C)EXPLANATIONWrong concentration on ADC Patch (C)

Refer to BSD: CH9.13 CH9.14 CH9.27DProcedureExecute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3).Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Is there toner in the DEVE Unit, distributed evenly?Yes NoExecute DC330 [009-003]Did the Dispense Motor (C) turn?Yes NoUsing an all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor(PL6.1)Check the auger mechanism for toner supply.Check the following:Check the IBT Belt for damage, dirtiness, or poor cleaning.Poor installation of ADC Sensor UnitROS Shutter malfunction.If there is no problem, change the MCU PWB. (PL13.1).

009-660 ENVIRONMENT SENSOR TEMP. FAILEXPLANATIONAbnormality detected on Environment Sensor (temperature).Refer to BSD: CH9.14 CH9.27EProcedureCheck the following:From MCU PWB J404-A11 to Environment Sensor J255-3.

From MCU PWB J404-A10 to Environment Sensor J255-4.Is the resistance value for all of them 1 • or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between P255-3 and P255-4.Is the resistance value between 6K • and 20K •?Yes NoChange the Environment Sensor (PL1.3)Change the MCU PWB. (PL13.1).

009-661 ENVIRONMENT SENSOR HUMIDITY FAILEXPLANATIONAbnormality detected on Environment Sensor (humidity).Refer to BSD: CH9.14 CH9.27EProcedureBetween MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and +1.7VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Turn off the power and check the following:From MCU PWB J404-A11 to Environment Sensor J255-3.From MCU PWB J404-A12 to Environment Sensor J255-2.From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all the resistance values 1 • or less?Yes NoCheck for severed lines, poor contact.Change the Environment Sensor (PL1.3)Change the MCU PWB. (PL13.1).

009-662 LD POWER CONTROL FAIL (Y)EXPLANATIONThe Amount-of-Light Value from the ADC Patch exceeds the stipulatedamount.Refer to BSD: CH9.13 CH9.14 CH9.27DProcedureExecute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?

Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3).Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADC Sensor Unit J602 and if thereare no problems, change the MOB Sensor ASSY (PL1.3)Is the toner in the DEVE Unit distributed evenly?Yes NoExecute DC330 [009-001]Did the Dispense Motor (Y) turn?Yes NoUsing the all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor(PL6.1)Check the auger mechanism for toner supply.Check the following:Check the IBT Belt for damage, dirtiness, or poor cleaning.Poor installation of ADC Sensor UnitROS Shutter malfunction.If there is no problem, change the MCU PWB. (PL13.1).

009-663 LD POWER CONTROL FAIL (M)EXPLANATIONThe Amount-of-Light Value from the ADC Patch exceeds the stipulatedamount.Refer to BSD: CH9.13 CH9.14 CH9.27DProcedureExecute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]

Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3).Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Is the toner in the DEVE Unit distributed evenly?Yes NoExecute DC330 [009-002]Did the Dispense Motor (M) turn?Yes NoUsing the all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor(PL6.1)Check the auger mechanism for toner supply.Check the following:Check the IBT Belt for damage, dirtiness, or poor cleaning.Poor installation of ADC Sensor UnitROS Shutter malfunction.If there is no problem, change the MCU PWB. (PL13.1).

009-664 LD POWER CONTROL FAIL (C)EXPLANATIONThe Amount-of-Light Value from the ADC Patch exceeds the stipulatedamount.Refer to BSD: CH9.13 CH9.14 CH9.27DProcedureExecute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes No

Check for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3).Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADC Sensor Unit J602 and if thereare no problems, change the MOB Sensor ASSY (PL1.3)Is the toner in the DEVE Unit distributed evenly?Yes NoExecute DC330 [009-003]Did the Dispense Motor (C) turn?Yes NoUsing the all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor(PL6.1)Check the auger mechanism for toner supply.Check the following:Check the IBT Belt for damage, dirtiness, or poor cleaning.Poor installation of ADC Sensor UnitROS Shutter malfunction.If there is no problem, change the MCU PWB. (PL13.1).

009-665 LD POWER CONTROL FAIL (K)EXPLANATIONThe Amount-of-Light Value from the ADC Patch exceeds the stipulatedamount.Refer to BSD: CH9.13 CH9.14 CH9.27DProcedureExecute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078]Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ATCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)

Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3).Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADC Sensor Unit J602 and if thereare no problems, change the MOB Sensor ASSY (PL1.3)Is the toner in the DEVE Unit distributed evenly?Yes NoExecute DC330 [009-004]Did the Dispense Motor (K) turn?Yes NoUsing the all-purpose Motor-Doesn’t-Run FIP, fix the Dispense Motor(PL6.1)Check the auger mechanism for toner supply.Check the following:Check the IBT Belt for damage, dirtiness, or poor cleaning.Poor installation of ADC Sensor UnitROS Shutter malfunction.If there is no problem, change the MCU PWB. (PL13.1)..

009-666 DEVE BIAS CONTROL FAIL (Y)EXPLANATIONThe DEVE BIAS Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor P255-3 and P255-4.Is the Resistance value between 6K • and 20K •?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact..Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-667 DEVE BIAS CONTROL FAIL (M)EXPLANATIONThe DEVE BIAS Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27E

ProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-668 DEVE BIAS CONTROL FAIL (C)EXPLANATIONThe DEVE BIAS Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)

Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-669 DEVE BIAS CONTROL FAIL (K)EXPLANATIONThe DEVE BIAS Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-670 BCR CONTROL FAIL (Y)EXPLANATIONThe BCR Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.

Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-671 BCR CONTROL FAIL (M)EXPLANATIONThe BCR Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-672 BCR CONTROL FAIL (C)

EXPLANATIONThe BCR Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact..Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-673 BCR CONTROL FAIL (K)EXPLANATIONThe BCR Voltage Adjustment Value exceeds the standard value.Refer to BSD: CH9.14 CH9.27EProcedureIs there a “Drum Change” message showing?Yes NoChange Drum (PL4.1)Shut off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A10 to Environment Sensor J255-4

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Remove Environment Sensor J255.Between Environment Sensor J255-3 and P255-4.Is the Resistance Value between 6K . and 20K .?Yes NoChange the Environment Sensor (PL 1.3)Turn on the power.Between MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4VDC and 1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?

Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch the power off, and check the following:From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1.

Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-684 ADC SHUTTER FAILEXPLANATIONADC Shutter Malfunction.Refer to BSD: CH9.14 CH9.27DProcedureExecute DC330 [009-078]Did the ADC Shutter Solenoid operate?Yes NoIs the voltage between MCU PWB J406-B2 (+) GND (-) +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24 VDC circuits up toMUC PWB J406-B2.(WN 7.3.13 +24VDC-3)Execute 330 [009-078]Between MCU PWB J406-B3 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for severed lines, poor contact from MCU PWB J406-B3 to ADC SensorUnit J602-3, and if there is noproblem, change MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J404-A12 (+) GND (-)Did the voltage change to 0 VDC momentarily?Yes NoCheck for severed lines, poor contact from MCU PWB J406-B1 to ADC SensorUnit J602-1, and if there is noproblem, change MCU PWB (PL13.1)Check for severed lines, poor contact from MCU PWB J406 to ADC SensorUnit J602, and if there is no problem, changeMOB Sensor ASSY (PL1.3)Change MCU PWB (PL13.1).Are all of the Resistance Values 1• or less?Yes NoCheck for severed wires, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-685 ENVIRONMENT SENSOR TEMP. CONTROL LIMIT FAILEXPLANATIONThe value from the Environment Sensor (Temp.) exceeeds the control limitvalue.Refer to BSD: CH9.14 CH9.27EProcedureCheck the following:From MCU PWB J404-A11 to Environment Sensor J255-3.From MCU PWB J404-A10 to Environment Sensor J255-4.

Are all of the Resistance Values 1 • or less?Yes NoCheck for severed lines, poor contact.

Remove Environment Sensor J255.Between Environment Sensor J255-3 and J255-4Is the Resistance Values between 6K • and 20K •?Yes NoChange Environment Sensor. (PL1.3)Change MCU PWB. (PL13.1).

009-686 ENVIRONMENT SENSOR HUMIDITY CONTROL LIMIT FAILTTEXPLANATIONThe Environment Sensor (Humidity) value exceeds the control limit value.Refer to BSD: CH9.14 CH9.27EProcedureBetween MCU PWB J404-A12 (+) GND (-)Is the voltage between +0.4 VDC and +1.7 VDC?Yes NoBetween MCU PWB J404-A13 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J404-A13. (WN 7.3.6 +5VDC-2)Switch off the power, check the following:From MCU PWB J404-A11 to Environment Sensor J255-3From MCU PWB J404-A12 to Environment Sensor J255-2From MCU PWB J404-A13 to Environment Sensor J255-1

Are all of the Resistance Values 1• or less?Yes NoCheck for severed lines, poor contact.Change Environment Sensor (PL1.3)Change MCU PWB (PL13.1).

009-910 DRUM TYPE MISMATCH (Y)EXPLANATIONThe type of drum is not suitable.Refer to BSD: CH9.2ProcedureExecute DC330 [009-151].Is the display “H”?Yes NoCheck the installation of the drum.Check for severed lines, poor contact from Drum (Y) J151 to MCU PWBJ405., and if there are no problems, change Drum (Y).(PL4.1)Change MCU PWB (PL13.1).

009-911 DRUM TYPE MISMATCH (M)EXPLANATIONThe type of drum is not suitable.Refer to BSD: CH9.2ProcedureExecute DC330 [009-152].Is the display “H”?Yes NoCheck the installation of the drum.Check for severed lines, poor contact from Drum (M) J152 to MCU PWBJ405., and if there are no problems, change Drum (Y).(PL4.1)Change MCU PWB (PL13.1).

009-912 DRUM TYPE MISMATCH (C)EXPLANATIONThe type of drum is not suitable.

Refer to BSD: CH9.3ProcedureExecute DC330 [009-153].Is the display “H”?Yes NoCheck the installation of the drum.Check for severed lines, poor contact from Drum (C) J153 to MCU PWBJ405., and if there are no problems, change Drum (C).(PL4.1)Change MCU PWB (PL13.1).

009-913 DRUM TYPE MISMATCH (K)EXPLANATIONThe type of drum is not suitable.Refer to BSD: CH9.3ProcedureExecute DC330 [009-154].Is the display “H”?Yes NoCheck the installation of the drum.Check for severed lines, poor contact from Drum (C) J154 to MCU PWBJ405., and if there are no problems, change Drum (C).(PL4.1)Change MCU PWB (PL13.1).

009-920 TONER YELLOW EMPTYEXPLANATIONThe yellow toner is empty.Refer to BSD: CH9.8 CH9.9 CH9.13 CH9.14 CH9.27CProcedureIs the toner in the DEVE Unit spread evenly?Yes NoExecute 330 [009-001].Is the Dispense Motor (Y) turning?Yes NoUsing the all-purpose Motor-Doesn’t-Turn FIP, fix the Dispense Motor.(PL6.1)Check the tonor-supply auger mechanism.Execute DC922 Tone Up/Down.Is the ATC Sensor (Y) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P129 to I/F PWBJ534 and if there are no problems, change the ATC Sensor (PL6.2)Execute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078].

Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ADCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)After switching the power off/on, did the DEVE Motor rotate?Yes NoBetween DEVE Motor J232-4 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toDEVE Motor J232-4. (WN 7.3.13+24VDC-3)Is the voltage between DEVE Motor J232-7 (+) GND (-) +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toDEVE Motor J232-7. (WN 7.3.6 +5VDC-2)Check for broken wires or poor contact between DEVE Motor J232 to MCUPWB J407 and if there are no problems, changethe DEVE Motor (PL1.1)Change the MCU PWB. (PL13.1).

009-921 TONER MAGENTA EMPTYEXPLANATIONThe magenta toner is empty.Refer to BSD: CH9.8 CH9.10 CH9.13 CH9.14 CH9.27CProcedureIs the toner in the DEVE Unit spread evenly?Yes NoExecute 330 [009-002].Is the Dispense Motor (M) turning?Yes NoUsing 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.Is the ATC Sensor (M) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P130 to I/F PWBJ534 and if there are no problems, change the ATC Sensor (PL6.2)Execute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes No

Using the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078].Between MCU PWB J406-B3 (+) GND (-).Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ADCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]Between MCU PWB J406-B1 (+) GND (-).Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)After switching the power off/on, did the DEVE Motor rotate?Yes NoBetween DEVE Motor J232-4 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toDEVE Motor J232-4. (WN 7.3.13+24VDC-3)Between DEVE Motor J232-7 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toDEVE Motor J232-7. (WN 7.3.6 +5VDC-2)Check for broken wires or poor contact between DEVE Motor J232 to MCUPWB J407 and if there are no problems, changethe DEVE Motor (PL1.1)Change the MCU PWB. (PL13.1).

009-922 TONER CYAN EMPTYEXPLANATIONThe magenta toner is empty.Refer to BSD: CH9.8 CH9.11 CH9.13 CH9.14 CH9.27CProcedureIs the toner in the DEVE Unit spread evenly?Yes NoExecute 330 [009-003].Is the Dispense Motor (C) turning?Yes NoUsing 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.Is the ATC Sensor (C) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P131 to I/F PWBJ534 and if there are no problems, change the ATC Sensor (PL6.2)Execute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078].Is the voltage between MCU PWB J406-B3 (+) GND (-). 0VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ADCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]MCU PWB J406-B1 (+) GND (-)Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)After switching the power off/on, did the DEVE Motor rotate?Yes NoBetween DEVE Motor J232-4 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toDEVE Motor J232-4. (WN 7.3.13+24VDC-3)Between DEVE Motor J232-7 (+) GND (-)Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toDEVE Motor J232-7. (WN 7.3.6 +5VDC-2)Check for broken wires or poor contact between DEVE Motor J232 to MCUPWB J407 and if there are no problems, changethe DEVE Motor (PL1.1)Change the MCU PWB. (PL13.1).

009-923 TONER BLACK EMPTYEXPLANATIONThe black toner is empty.Refer to BSD: CH4.1 CH9.12 CH9.13 CH9.14 CH9.27CProcedureIs the toner in the DEVE Unit spread evenly?Yes NoExecute 330 [009-004].Is the Dispense Motor (B) turning?Yes NoUsing 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.Is the ATC Sensor (K) Fail judgment OK?Yes NoCheck the installation of the ATC Sensor and check for broken wires orpoor contact between ATC Sensor P131 to I/F PWBJ534 and if there are no problems, change the ATC Sensor (PL6.2)Execute DC934 ADC Output Check.Is the ADC Sensor Fail judgment OK?Yes NoBetween MCU PWB J406-B8 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toMCU PWB J406-B8. (WN 7.3.6 +5VDC-2)Execute DC330 [009-078].Did the ADC Shutter Solenoid function?Yes NoBetween MCU PWB J406-B2 (+) GND (-).Is the voltage +24VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toMCU PWB J406-B2. (WN7.3.13 +24VDC-3)Execute DC330 [009-078].Is the voltage between MCU PWB J406-B3 (+) GND (-). 0VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B3 to ADCSensor Unit J602-3 and ifthere are no problems, change the MCU PWB (PL13.1)Execute DC330 [009-079]MCU PWB J406-B1 (+) GND (-)Did the voltage change to 0 momentarily?Yes NoCheck for broken wires or poor contact between MCU PWB J406-B1 to ADCSensor Unit J602-1 and ifthere are no problems, change the MCU PWB (PL13.1)Check for broken wires or poor contact between MCU PWB J406 to ADCSensor Unit J602 and if there are noproblems, change the MOB Sensor ASSY (PL1.3)Check the installation of the ADC Sensor and check for broken wires orpoor contact between MCU PWB J406 and ADCSensor Unit J602 and if there are no problems, change the MOB SensorASSY (PL1.3)Execute DC330 [004-004]Did the Main Motor rotate?Yes NoBetween Main Motor J203-4 (+) GND (-).Is the voltage +24VDC?Yes No

Using the wire network from Chapter 7, check the +24VDC circuits up toDEVE Motor J232-4. (WN 7.3.13+24VDC-3)Execute DC330 [004-004]Between Main Motor J203-1 (+) GND (-)Is the voltage 0 VDC?Yes NoExecute DC330 [004-004]Between MCU PWB J407-A1 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J407-A1 to MainMotor J203-1 and if thereare no problems, change the MCU PWB(PL13.1)Check for broken wires or poor contact between MCU PWB J407-A1 to MainMotor J203-1Execute DC330 [004-004]Between Main Motor J203-2 (+) GND (-).Is the voltage 0 VDC?Yes NoExecute DC330 [004-004]Between MCU PWB J407-A2 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck for broken wires or poor contact between MCU PWB J407-A2 to MainMotor J203-2 and if thereare no problems, change the MCU PWB(PL13.1)Check for broken wires or poor contact between MCU PWB J407-A2 to MainMotor J203-2Change the Main Motor. (PL1.1)Execute DC330 [009-013]Did the DEVE Clutch (K) move?Yes NoUsing the all-purpose Clutch-Doesn’t-Work FIP, fix the DEVE Clutch.(PL1.2)Change the MCU PWB. (PL13.1).

009-924 WASTE BOTTLE FULLEXPLANATIONThe toner-collection bottle is fullRefer to BSD: CH9.26 CH9.27EProcedureIs there residue from the toner and are there foreign objects near the Full Toner Sensor Actuator?Yes NoClean it.Execute DC330 [009-150].Does the display read “H”?Yes NoChange the MCU PWB. (PL13.1)Using the all-purpose Permeable Sensor FIP, fix the Full-Toner Sensor.(PL4.1).

009-925 WASTE TONER BOTTLE NOT SETEXPLANATIONMis-installation of the Toner-Collection BottleRefer to BSD: CH1.6 CH9.27EPre-Operation ConfirmationThis problem can occur even if the Drum (Y/M/C/K) is improperlyinstalled, so make sure to confirm the installation of the Drum.ProcedureBetween I/F PWB J536-1 (+) GND (-).

Is the voltage +5VDC?Yes NoOpen the front door, cheat the Front-Door I/L SwitchBetween Waste-Toner Bottle Interlock SW FS-135 (+) GND (-).Is the voltage +5VDC?Yes NoBetween I/F PWB J536-3 (+) GND (-).Is the voltage +5VDC?Yes NoBetween I/F PWB J536-4 (+) GND (-).Is the voltage +5VDC?Yes NoUsing the wire network from Chapter 7, check the +5VDC circuits up toI/F PWB J536-4. (WN7.3.5 +5VDC-1)Change I/F PWB. (PL9.1)Check for broken wires or poor contact between I/F PWB J536-3 to WasteToner Bottle Interlock SW FS-135Between Waste-Toner Bottle Interlock SW FS-134 (+) GND (-).Is the voltage +5VDC?Yes NoChange Waste-Toner Bottle Interlock SW (PL4.1)Check for broken wires or poor contact between I/F PWB J536-3 to WasteToner Bottle Interlock SW FS-135Check the connection of the Connector P/J410 (P410 / J410) between I/FPWB and MCU PWB, and if there are no problems, changeMCU PWB. (PL13.1)If that doesn’t work, change I/F PWB (PL9.1).

009-926 DRUM CARTRIDGE END OF LIFE (K)EXPLANATIONTiming for Drum replacement.Refer to BSD: CH9.3 CH9.27BProcedureReplace Drum (K) (PL4.1), and if that doesn’t work, change MCU PWB.(PL13.1).

009-927 DRUM CARTRIDGE END OF LIFE (C)EXPLANATIONTiming for Drum replacement.Refer to BSD: CH9.3 CH9.27BProcedureReplace Drum (C) (PL4.1), and if that doesn’t work, change MCU PWB.(PL13.1).

009-928 DRUM CARTRIDGE END OF LIFE (M)EXPLANATIONTiming for Drum replacement.Refer to BSD: CH9.2 CH9.27BProcedureReplace Drum (M) (PL4.1), and if that doesn’t work, change MCU PWB.(PL13.1).

009-929 DRUM CARTRIDGE END OF LIFE (Y)EXPLANATIONTiming for Drum replacement.Refer to BSD: CH9.2 CH9.27BProcedureReplace Drum (Y) (PL4.1), and if that doesn’t work, change MCU PWB.(PL13.1).

009-931 DRUM NOT DETECT (M)EXPLANATIONDrum Detect Data is unsuitable.Refer to BSD: CH9.2 CH9.27BProcedureSwitch 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)EXPLANATIONDrum Detect Data is unsuitable.Refer to BSD: CH9.3 CH9.27BProcedureSwitch 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 JAMEXPLANATIONThe 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 SolenoidCheck ItemsMalfunctioning Wait SensorWear, poor rotation of Duplex Trance RollWear, poor rotation of Duplex Wait RollMalfunctioning Duplex GatePoor rotation of Duplex MotorMalfunctioning Duplex Gate SolenoidDamage to and wear of GearsPoor conveyance of paper due to foreign objects in the paper pathUse of non-spec. paper. (Refer to “ Specs” in Chapter 6).

10-348 MAIN HEATER OVERHEAT FAILEXPLANATIONThe Front Thermistor detects an abnormally high temperatureNOTEIn order to undo this fault, the value for DC131 [744-010] must “ 0”clear.Refer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-4 (+) P600-6 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for broken wires or poor contact in the Front Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Return the Fuser ASSY to its position, turn on the power, and executeDC140 [010-100].Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for broken wires or poor contact between MCUPWB J404-A2 and Front Thermistor J211-1Are there any broken wires or poor contact?Yes No

Check for broken wires or poor contact between MCU PWB J404-A1 and FrontThermistor J211-2Are there any broken wires or poor contact?Yes NoChange MCU PWB (PL13.1)Fix broken lines, poor contact.Fix broken lines, poor contact.Between MCU PWB J406-B11 (+) GND (-).Measure the voltage.Is it +5VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-5 (+) GND (-).Measure the voltage.Is it +5VDC until the occurrence of Fail?Yes NoChange AC Drive PWB (PL9.2)Check for broken lines, poor contact.Change MCU PWB (PL13.1).

10-349 FRONT THERMISTOR DISCONNECTIONEXPLANATIONFront Thermistor disconnection detected.Refer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-4 (+) P600-6 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for broken wires or poor contact in the Front Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Return the Fuser ASSY to its position, turn on the power, and executeDC140 [010-100].Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for broken wires or poor contact between MCUPWB J404-A2 and Front Thermistor J211-1Are there any broken wires or poor contact?Yes NoCheck for broken wires or poor contact between MCU PWB J404-A1 and FrontThermistor J211-2Are there any broken wires or poor contact?Yes NoChange MCU PWB (PL13.1)Fix broken lines, poor contact.Fix broken lines, poor contact.Change MCU PWB (PL13.1).

10-350 SUB HEATER OVERHEAT FAILEXPLANATIONThe Rear Thermistor detects an abnormally high temperatureNOTEIn order to undo this fault, the value for DC131 [744-010] must “ 0”clear.Refer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-7 (+) P600-9 (-)Measure the Resistance Value.

Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for broken wires or poor contact in the Rear Thermistor within theFuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Return the Fuser ASSY to its position, turn on the power, and executeDC140 [010-101].Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for broken wires or poor contact between MCUPWB J404-A4 and Front Thermistor J212-1Are there any broken wires or poor contact?Yes NoCheck for broken wires or poor contact between MCU PWB J404-A3 and FrontThermistor J212-2Are there any broken wires or poor contact?Yes NoChange MCU PWB (PL13.1)Fix broken lines, poor contact.Fix broken lines, poor contact.Between MCU PWB J406-B13 (+) GND (-).Measure the voltage.Is it +5VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-3 (+) GND (-).Measure the voltage.Is it +5VDC until the occurrence of Fail?Yes NoChange AC Drive PWB (PL9.2)Check for broken lines, poor contact.Change MCU PWB (PL13.1).

10-351 REAR THERMISTOR DISCONNECTIONEXPLANATIONTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-7 (+) P600-9 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for disconnection or poor contact in the Front Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Return the Fuser ASSY to its position, turn on the power, and executeDC140 [010-101].Rear Thermistor disconnection detected.Refer to BSD: CH10.1 CH10.8ProcedureIs the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for disconnection or poor contact between MCUPWB J404-A4 and Front Thermistor J212-1Is there any disconnection or poor contact?Yes NoCheck for disconnection or poor contact between MCU PWB J404-A3 andFront Thermistor J212-2Is there any disconnection or poor contact?Yes NoChange MCU PWB (PL13.1)Fix disconnection, poor contact.Fix disconnection, poor contact.Change MCU PWB (PL13.1).

10-352 MAIN HEATER WARMUP FAILEXPLANATION[Main Heater] fails to reach Ready Temperature within the prescribedtime.Refer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-4 (+) P600-5 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for disconnection or poor contact in the Front Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Return the Fuser ASSY to its position, turn on the power, and executeDC140 [010-100].Is the Resistance Value 20• or less?Yes NoCheck for disconnection or poor contact in the Wire within the FuserASSY, and check for disconnection of the Thermostat,and if there are no problems, change the Fuser ASSY. (PL7.1)Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for disconnection or poor contact between MCUPWB J404-A2 and Front Thermistor J211-1Is there any disconnection or poor contact?Yes NoCheck for disconnection or poor contact between MCU PWB J404-A1 andFront Thermistor J211-2Is there any disconnection or poor contact?Yes NoChange MCU PWB (PL13.1)Fix disconnection, poor contact.Fix disconnection, poor contact.Between MCU PWB J406-B11 (+) GND (-).Measure the voltage.Is it 0VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-5 (+) GND (-).Measure the voltage.Is it 0 VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-4 (+) GND (-).Is it 0 VDC until the occurrence of Fail?Yes NoUsing the wire network from Chapter 7, check the DC-COM circuits in theAC Drive PWB J590-4. (WN5VRTN-2 5VRTN-2)Between AC Drive PWB FS48 (+)FS41 (-).Is the voltage 100VAC?Yes NoBetween AC Drive PWB FS39 (+)FS40 (-).Is the voltage 100VAC?Yes NoUsing the wire network from Chapter 7, check the AC circuits up to theAC Drive PWB FS39,FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)Between AC Drive PWB J590-1 (+) GND(-).Is the voltage +24 VDC?Yes No

Using the wire network from Chapter 7, check the +24 circuits up to theAC Drive PWB J590-1(WN 7.3.1 +24VDC-3)Between AC Drive PWB J590-2 (+) GND(-).Is the voltage 0 VDC?Yes NoBetween MCU PWB J406-B14 (+) GND(-).Is the voltage 0 VDC?Yes NoCheck for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWBJ406-B14 , and if there are no problems, change MCU PWB (PL13.1)Check for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWB J406-B14Change AC Drive PWB. (PL9.2)Check for disconnection or poor contact between AC Drive PWB FS41 andFUSER ASSY J600-1 , and betweenAC Drive PWB FS48 and FUSER ASSY J600-12Check for disconnection or poor contact between AC Drive PWB J590-5 andMCU PWB J406-B11Check for frame short in wire, and if there are no problems, change MCUPWB. (PL13.1).

10-353 MAIN HEATER ON TIME FAILEXPLANATIONThe Main Heater [light?] is on for a continuous period that exceeds theprescribed timeRefer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-4 (+) P600-5 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for disconnection or poor contact in the Front Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Between Fuser ASSY Connector P600-1 (+) P600-12 (-)Measure the Resistance ValueIs the Resistance Value 20• or less?Yes NoCheck for disconnection or poor contact in the Wire within the FuserASSY, and check for disconnection of the Thermostat,and if there are no problems, change the Fuser ASSY. (PL7.1)Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for disconnection or poor contact between MCUPWB J404-A2 and Front Thermistor J211-1Is there any disconnection or poor contact?Yes NoCheck for disconnection or poor contact between MCU PWB J404-A1 andFront Thermistor J211-2Is there any disconnection or poor contact?Yes NoChange MCU PWB (PL13.1)Fix disconnection, poor contact.Fix disconnection, poor contact.Measure the voltage between MCU PWB J406-B11 (+) GND (-).Is it 0VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-5 (+) GND (-).Measure the voltage.

Is it 0 VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-4 (+) GND (-).Is it 0 VDC until the occurrence of Fail?Yes NoUsing the wire network from Chapter 7, check the DC-COM circuits in theAC Drive PWB J590-4. (WN7.3.9 5VRTN-2)Between AC Drive PWB FS48 (+)FS41 (-).Is the voltage 100VAC?Yes NoBetween AC Drive PWB FS39 (+)FS40 (-).Is the voltage 100VAC?Yes NoUsing the wire network from Chapter 7, check the AC circuits up to theAC Drive PWB FS39,FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)Between AC Drive PWB J590-1 (+) GND(-).Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check the +24 circuits up to theAC Drive PWB J590-1(WN 7.3.1 +24VDC-3)Between AC Drive PWB J590-2 (+) GND(-).Is the voltage 0 VDC?Yes NoBetween MCU PWB J406-B14 (+) GND(-).Is the voltage 0 VDC?Yes NoCheck for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWBJ406-B14 , and if there are no problems, change MCU PWB (PL13.1)Check for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWB J406-B14Change AC Drive PWB. (PL9.2)Check for disconnection or poor contact between AC Drive PWB FS41 andFUSER ASSY J600-1 , and betweenAC Drive PWB FS48 and FUSER ASSY J600-12Check for disconnection or poor contact between AC Drive PWB J590-5 andMCU PWB J406-B11Check for frame short in wire, and if there are no problems, change MCUPWB. (PL13.1).

10-354 SUB HEATER WARM UPEXPLANATIONFailed to reach Ready Temperature within the prescribed time.Refer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-7 (+) P600-9 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for disconnection or poor contact in the Rear Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Between Fuser ASSY P600-3 (+) P600-12 (-)Measure the Resistance ValueIs the Resistance Value 20• or less?Yes No

Check for disconnection or poor contact in the Wire within the FuserASSY, and check for disconnection of the Thermostat,and if there are no problems, change the Fuser ASSY. (PL7.1)Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for disconnection or poor contact between MCUPWB J404-A4 and Rear Thermistor J212-1Is there any disconnection or poor contact?Yes NoCheck for disconnection or poor contact between MCU PWB J404-A3 and RearThermistor J211-2Is there any disconnection or poor contact?Yes NoChange MCU PWB (PL13.1)Fix disconnection, poor contact.Fix disconnection, poor contact.Measure the voltage between MCU PWB J406-B13 (+) GND (-).Is it 0VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-4 (+) GND (-).Measure the voltage.Is it 0 VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-4 (+) GND (-).Is it 0 VDC until the occurrence of Fail?Yes NoUsing the wire network from Chapter 7, check the DC-COM circuits in theAC Drive PWB J590-4. (WN7.3.9 5VRTN-2)Between AC Drive PWB FS48 (+)FS47 (-).Is the voltage 100VAC?Yes NoBetween AC Drive PWB FS39 (+)FS40 (-).Is the voltage 100VAC?Yes NoUsing the wire network from Chapter 7, check the AC circuits up to theAC Drive PWB FS39,FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)Between AC Drive PWB J590-1 (+) GND(-).Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check the +24 circuits up to theAC Drive PWB J590-1(WN 7.3.13 +24VDC-3)Between AC Drive PWB J590-2 (+) GND(-).Is the voltage 0 VDC?Yes NoBetween MCU PWB J406-B14 (+) GND(-).Is the voltage 0 VDC?Yes NoCheck for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWBJ406-B14 , and if there are no problems, change MCU PWB (PL13.1)Check for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWB J406-B14Change AC Drive PWB. (PL9.2)Check for disconnection or poor contact between AC Drive PWB FS47 andFUSER ASSY J600-3 , and betweenAC Drive PWB FS48 and FUSER ASSY J600-12Check for disconnection or poor contact between AC Drive PWB J590-3 andMCU PWB J406-B13Check for frame short in wire, and if there are no problems, change MCUPWB. (PL13.1).

10-356 SUB HEATER ON TIME FAILEXPLANATIONThe Sub Heater [light] is continuously illuminated for more than theprescribed time.Refer to BSD: CH10.1 CH10.8ProcedureTurn off the power, remove the Fuser ASSY and allow it to coolsufficiently.Between Fuser ASSY Connector P600-7 (+) P600-9 (-)Measure the Resistance Value.Is the Resistance Value between 30K• and 190K • ?Yes NoCheck for disconnection or poor contact in the Rear Thermistor withinthe Fuser ASSY, and if there are no problems, changethe Fuser ASSY. (PL7.1)Between Fuser ASSY P600-3 (+) P600-12 (-)Measure the Resistance ValueIs the Resistance Value 20• or less?Yes NoCheck for disconnection or poor contact in the Wire within the FuserASSY, and check for disconnection of the Thermostat,and if there are no problems, change the Fuser ASSY. (PL7.1)Is the Monitor Value between 900 and 1000?Yes NoTurn off the power, check for disconnection or poor contact between MCUPWB J404-A4 and Rear Thermistor J212-1Is there any disconnection or poor contact?Yes NoCheck for disconnection or poor contact between MCU PWB J404-A3 and RearThermistor J211-2Is there any disconnection or poor contact?Yes NoChange MCU PWB (PL13.1)Fix disconnection, poor contact.Fix disconnection, poor contact.Measure the voltage between MCU PWB J406-B13 (+) GND (-).Is it 0VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-3 (+) GND (-).Measure the voltage.Is it 0 VDC until the occurrence of Fail?Yes NoBetween AC Drive PWB J590-4 (+) GND (-).Is it 0 VDC until the occurrence of Fail?Yes NoUsing the wire network from Chapter 7, check the DC-COM circuits in theAC Drive PWB J590-4. (WN7.3.9 5VRTN-2)Between AC Drive PWB FS48 (+)FS47 (-).Is the voltage 100VAC?Yes NoBetween AC Drive PWB FS39 (+)FS40 (-).Is the voltage 100VAC?Yes NoUsing the wire network from Chapter 7, check the AC circuits up to theAC Drive PWB FS39,FS40 (WN 7.3.1 ACH/ WN 7.3.1 ACN)Between AC Drive PWB J590-1 (+) GND(-).Is the voltage +24 VDC?Yes No

Using the wire network from Chapter 7, check the +24 VDC circuits up tothe AC Drive PWBJ590-1 (WN 7.3.13 +24VDC-3)Between AC Drive PWB J590-2 (+) GND(-).Is the voltage 0 VDC?Yes NoBetween MCU PWB J406-B14 (+) GND(-).Is the voltage 0 VDC?Yes NoCheck for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWBJ406-B14 , and if there are no problems, change MCU PWB (PL13.1)Check for disconnection or poor contact between AC Drive PWB J590-2 andMCU PWB J406-B14Change AC Drive PWB. (PL9.2)Check for disconnection or poor contact between AC Drive PWB FS47 andFUSER ASSY J600-3 , and betweenAC Drive PWB FS48 and FUSER ASSY J600-12Check for disconnection or poor contact between AC Drive PWB J590-3 andMCU PWB J406-B13Check for frame short in Wire, and if there are no problems, change MCUPWB. (PL13.1).

10-398 FAN LOCK FAILEXPLANATIONBroken Fuser Fan/LVPS FanNOTEBefore 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.8ProcedureExecute DC330 [004-050]Is the Fuser Fan rotating at a high speed?Yes NoBetween Fuser Fan J222-4 (+) GND (-)Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check the+24VDC circuits up tothe Fuser Fan J222-4. (WN 7.3.12 +24VDC-2)Between Fuser Fan P222-4 (+) P222-1 (-)Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check theDC-COM circuits up toFuser Fan J222-1. (WN 7.3.14 24VRTN-1)Execute DC330 [004-050]Between Fuser Fan P222-3 (+) GND (-)Is the voltage 0 VDC?Yes NoExecute DC330 [004-050]Between I/F PWB J530-A2 (+) GND(-).Is the voltage 0 VDC?Yes NoCheck for disconnection or poor contact between Fuser Fan J222-3 and I/FPWB J530-A2 , and check theconnection between MCU PWB and I/F PWB; if there are no problems, changeMCU PWB (PL13.1)If that doesn’t work, change I/F PWB. (PL9.1)Check for disconnection or poor contact between Fuser Fan J222-3 and I/FPWB J530-A2Change AC Drive PWB. (PL9.2).Execute DC330 [004-050].

Between Fuser Fan J222-2 (+) GND(-).Is the voltage +3.3 VDC?Yes NoExecute DC330 [004-050]Between I/F PWB J530-A3 (+) GND (-)Is the voltage +3.3 VDC?Yes NoCheck the connection between MCU PWB and I/F PWB, and if there are noproblems, MCU PWB (PL13.1)If that doesn’t work, change I/F PWB. (PL9.1)Check for disconnection or poor contact between Fuser Fan J222-2 and I/FPWB J530-A3.Change Fuser Fan. (PL8.1)Execute DC330 [004-050]Is the LVPS Fan rotating at high speed?Yes NoBetween LVPS Fan J214-4 (+) GND (-)Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check the +24VDC circuits up toLVPS Fan J214-4. (WN 7.3.12 +24VDC-2)Between LVPS Fan J214-4 (+) J214-1.Is the voltage +24 VDC?Yes NoUsing the wire network from Chapter 7, check the DC COM circuits up toLVPS Fan J214-1. (WN 7.3.1424VRTNC-1)Execute DC330 [004-050]Between I/F PWB J214-3 (+) GND (-)Is the voltage 0 VDC?Yes NoExecute DC330 [004-050]Between I/F PWB J530-A6 (+) GND (-)Is the voltage 0 VDC?Yes NoCheck the for disconnection, poor contact between LVPS Fan J214-3 andI/F PWB J530-A6 and check theconnection between MCU PWB and I/F PWB; if there are no problems, changeMCU PWB (PL13.1).If that doesn’t work, change I/F PWB. (PL9.1)Check for disconnection or poor contact between LVPS Fan J214-3 and I/FPWB J530-A6.Change LVPS Fan (PL9.1)Execute DC330 [040-050]Between LVPS Fan J214-2 (+) GND (-)Is the voltage +3.3 VDC?Yes NoExecute DC330 [040-050]Between I/F PWB J530-A7 (+) GND (-)Is the voltage +3.3 VDC?Yes NoCheck connection between MCU PWB and I/F PWB, and if there are noproblems, change MCU PWB (PL13.1)If that doesn’t work, change I/F PWB. (PL9.1)Check for disconnection or poor contact betweenI/F PWB J530-A7 and LVPSFan J214-2.Change LVPS Fan (PL9.1).

10-420 FUSER ASSY CHANGE SOONEXPLANATION

The time to change the Fuser ASSY is drawing near.Refer to BSD: CH10.8ProcedureHas the Change Button been pushed down?Yes NoPush the Change Button down.Execute DC135 [954-804]Is the initial value 0?Yes NoChange MCU PWB (PL13.1)After confirming that the LIFE Set Value is 10000, turn the power off/onIf that doesn’t work, change MCU PWB (PL13.1).

10-421 FUSER ASSY END OF LIFEEXPLANATIONTiming of Fuser ASSY change.Refer to BSD: CH10.8ProcedureHas the Change Button been pushed down?Yes NoPush the Change Button down.Execute DC135 [954-804]Is the initial value 0?Yes NoChange MCU PWB (PL13.1)After confirming that the LIFE Set Value is 10000, turn the power off/onIf that doesn’t work, change MCU PWB (PL13.1).

03-205 BILLING FAIL 1Refer to BSD: CH16.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 theproblem continues after executing the measure,replace ESS PWB (PL13.1).

03-206 BILLING FAIL 2Refer to BSD: CH16.1[Detection Conditions]1 inconsistent Billing Counter cannot be repaired.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:Abnormality in ESS PWB SLEEPROM or NVM. Or abnormality in EEPROM MCUPWB. If it’s not a problem with theNVM Battery, change ESS PWB (PL13.1) or change MCU PWB. (PL13.1).

03-340 IOT-ESS COMMUNICATION FAIL 1Refer to BSD: CH16.1[Detection Conditions]Error message due to abnormal paramaters set for Transmission FunctionFactor.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following: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).

03-341 IOT-ESS COMMUNICATION FAIL 2

Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (The “ SequenceNo” valuefor the Message Packet of the transmission is not correct.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:7. Check the MCU PWB Connection Harness.8. Software problem. Reinstall software.9. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-342 IOT-ESS COMMUNICATION FAIL 3Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (The PacketNo value for theMessage Packet of the transmission is not correct.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:10. Check the MCU PWB Connection Harness.11. Software problem. Reinstall software.12. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-343 IOT-ESS COMMUNICATION FAIL 4Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (The value for the messagelength of the transmission’s Message Packet is not correct.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:13. Check the MCU PWB Connection Harness.14. Software problem. Reinstall software.15. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-345 IOT-ESS COMMUNICATION FAIL 5Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (The Check Code for theMessage Packet of the transmission is not correct.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:16. Check the MCU PWB Connection Harness.17. Software problem. Reinstall software.18. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-346 IOT-ESS COMMUNICATION FAIL 6Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (Parity Error was detected onIOT-side hardware.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:19. Check the MCU PWB Connection Harness.20. Software problem. Reinstall software.21. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-347 IOT-ESS COMMUNICATION FAIL 7Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (Framing Error was detectedin IOT-side hardware.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:22. Check the MCU PWB Connection Harness.23. Software problem. Reinstall software.24. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-348 IOT-ESS COMMUNICATION FAIL 8Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (Overrun Error was detectedin IOT-side hardware.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:25. Check the MCU PWB Connection Harness.26. Software problem. Reinstall software.27. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-349 IOT-ESS COMMUNICATION FAIL 9Refer to BSD: CH16.1[Detection Conditions]Communication Fail occurs because ACK was not received even after 2attempts to re-transmit. (After Header Recognitionon IOT Side, “ Transmission-Interrupted” was detected.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:28. Check the MCU PWB Connection Harness.29. Software problem. Reinstall software.30. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-350 IOT-ESS COMMUNICATION FAIL 10Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (The SequenceNo of the MessagePacket received is not a correct value.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:31. Check the MCU PWB Connection Harness.32. Software problem. Reinstall software.33. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-351 IOT-ESS COMMUNICATION FAIL 11Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (The PacketNo of the MessagePacket received is not a correct value.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:34. Check the MCU PWB Connection Harness.

35. Software problem. Reinstall software.36. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-352 IOT-ESS COMMUNICATION FAIL 12Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (The Message Length of theMessage Packet received is not a correct value.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:37. Check the MCU PWB Connection Harness.38. Software problem. Reinstall software.39. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-353 IOT-ESS COMMUNICATION FAIL 13Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (The Check Code of the MessagePacket received is not a correct value.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:40. Check the MCU PWB Connection Harness.41. Software problem. Reinstall software.42. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-354 IOT-ESS COMMUNICATION FAIL 14Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (A Parity Error was detected in thehardware that UART itself holds.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:43. Check the MCU PWB Connection Harness.44. Software problem. Reinstall software.45. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-355 IOT-ESS COMMUNICATION FAIL 15Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (A Framing Error was detected inthe hardware that UART itself holds.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:46. Check the MCU PWB Connection Harness.47. Software problem. Reinstall software.48. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-356 IOT-ESS COMMUNICATION FAIL 16Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (An Over-run Error was detectedin the hardware that UART itself holds.)

[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:49. Check the MCU PWB Connection Harness.50. Software problem. Reinstall software.51. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-357 IOT-ESS COMMUNICATION FAIL 17Refer to BSD: CH16.1[Detection Conditions]Occurs when NAK, which notifies of the occurrence of a communicationfail, is received. (After recognition of Header, a“ Receive-Interrupted” was detected.)[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:52. Check the MCU PWB Connection Harness.53. Software problem. Reinstall software.54. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-358 IOT-ESS COMMUNICATION FAIL 18Refer to BSD: CH16.1[Detection Conditions]Detection of Paper Feed and Paper Discharge that aren’t NBR-compatible.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:55. Check the MCU PWB Connection Harness.56. Software problem. Reinstall software.57. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-359 IOT-ESS COMMUNICATION FAIL 19Refer to BSD: CH16.1[Detection Conditions]Error occurring when the Receiving-Function Factor has abnormalparameters.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:58. Check the MCU PWB Connection Harness.59. Software problem. Reinstall software.60. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-360 IOT-ESS INITIALIZATION FAILRefer to BSD: CH16.1[Detection Conditions] IOT Driver Initialization Fail.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:61. Check the MCU PWB Connection Harness.62. Software problem. Reinstall software.63. If the above steps do not rectify the situation, change the MCU PWB(PL13.1).

03-362 PAGE SYNC ILLEGAL STARTRefer to BSD: CH16.1[Detection Conditions]Page Sync is activated before FIFO is written full with Output Dataduring IOT Output.[Rectification Method] At present, this fail is not displayed..

03-363 PAGE SYNC ILLEGAL STOPRefer to BSD: CH16.1

[Detection Conditions]Page Sync is negated before IOT Output reaches the designated size.[Rectification Method] At present, this fail is not displayed..

03-364 DMA TRANSFER FAILRefer to BSD: CH16.1[Detection Conditions]Occurs when, during compression/decompression of the designated data wasentered, but the compression/expansion doesnot terminate.[Rectification Method]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, changeHDD (PL13.1)9. ESS PWB (PL13.1).

03-365 OVERFLOW ON LOOP BACK WRITERefer to BSD: CH16.1[Detection Conditions]Decompressed data exceeds the buffer size that was reserved.[Rectification Method] At present, this fail is not displayed..

03-366 JBIG Library Other FailRefer to BSD: CH16.1[Detection Conditions] Not used at present.[Rectification Method]Turn power off/on; if the trouble continues, execute the following:1. ESS PWB (PL13.1).

03-370 Marker Code Defect FailRefer to BSD: CH16.1[Detection Conditions]Amount decompressed was equal to the designated size, but theCompression Data Termination Code (FF02) was not found.[Rectification Method]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 FIXRefer to BSD: CH16.1[Detection Conditions] The Billing Master Counter was fixedautomatically.[Rectification Method] Only Registration at History.

03-601 IMARI: BILLING MASTER COUNTER 1 FIXRefer to BSD: CH16.1[Detection Conditions] The Billing Master Counter 1 was fixedautomatically.[Rectification Method] Only Registration at History.

03-602 IMARI: BILLING MASTER COUNTER 2 FIXRefer to BSD: CH16.1[Detection Conditions] The Billing Master Counter 2 was fixedautomatically.[Rectification Method] Only Registration at History.

03-747 PRINT INSTRUCTION FAILRefer to BSD: CH16.1[Detection Conditions] The designated print parameters are abnormal.[Rectification Method] Change print parameters and reprint..

03-954 TRAY SMH EMPTYRefer to BSD: CH16.1[Detection Conditions] No paper detected in paper-feed tray.[Rectification Method]Replenish paper. If the trouble continues, refer to All-Purpose SensorFIP and check the Sensor..

03-958 SIZE MISMATCH 1 SMH SIZE UNSUITABLERefer to BSD: CH16.1[Detection Conditions]The paper designated with the print command and the paper in the paper-feed tray are different.[Rectification Method]Set the proper kind of paper..

03-959 SIZE MISMATCH TRAY 1 SIZE UNSUITABLERefer to BSD: CH16.1[Detection Conditions]The paper designated with the print command and the paper in Tray 1 aredifferent.[Rectification Method]Set the proper kind of paper. If the trouble continues, refer to All-Purpose Sensor FIP and check the Sensor..

03-960 SIZE MISMATCH TRAY 2 SIZE UNSUITABLERefer to BSD: CH16.1[Detection Conditions]The paper designated with the print command and the paper in Tray 2 aredifferent.[Rectification Method]Set the proper kind of paper. If the trouble continues, refer to All-Purpose Sensor FIP and check the Sensor..

03-961 SIZE MISMATCH TRAY 3 SIZE UNSUITABLERefer to BSD: CH16.1[Detection Conditions]The paper designated with the print command and the paper in Tray 3 aredifferent.[Rectification Method]Set the proper kind of paper. If the trouble continues, refer to All-Purpose Sensor FIP and check the Sensor..

03-962 SIZE MISMATCH TRAY 4 SIZE UNSUITABLERefer to BSD: CH16.1[Detection Conditions]The paper designated with the print command and the paper in Tray 4 aredifferent.[Rectification Method]Set the proper kind of paper. If the trouble continues, refer to All-Purpose Sensor FIP and check the Sensor..

03-965 ATS/APS NO PAPER, APS/ATS NG (NO PAPER)Refer to BSD: CH16.1[Detection Conditions] There is no paper of the type designated with theprint command[Rectification Method]

Set the proper kind of paper. If the trouble continues, refer to All-Purpose Sensor FIP and check the Sensor..

03-966 ATS/APS NO DESTINATION ERROR, ATS/APS NG ( EXCLUDING NO PAPER)Refer to BSD: CH16.1[Detection Conditions] No paper of the type designated with the printcommand is detected.[Rectification Method]Change the setting. If the trouble continues, refer to All-PurposeSensor FIP and check the Sensor..

03-985 SMH TEMPORARY STOP CONFIRMATIONRefer to BSD: CH16.1[Detection Conditions] Movement of paper from the Paper-Feed Tray stopsdue to some problem.[Rectification Method]Check the paper size, paper direction and paper type, then push theDischarge Key..

16-450 DUPLICATE SMB HOST NAMERefer to BSD: CH16.1[Detection Conditions]A PC on the network has a host name has a host name that is alreadybeing used.[Rectification Method]Change the host name..

16-452 DUPLICATE IP ADDRESSRefer to BSD: CH16.1[Detection Conditions]A PC on the network has a host namehas an IP address that is alreadybeing used.[Rectification Method]Change the IP address..

16-453 OBTAINING IP ADDRESS FROM DHCP SERVER FAILSRefer to BSD: CH16.1[Detection Conditions]Failure to obtain IP address from DHCP server.[Rectification Method]Set IP address. (Do not obtain from DHCP server).

16-701 SHORT OF PLW MEMORYRefer to BSD: CH16.1[Detection Conditions]Insufficient memory detected during ART EX usage.[Rectification Method]Imari: PLW memroy is fixed; if possible, lower the picture resolution..

16-702 SHORT OF PLW MEMORYRefer to BSD: CH16.1[Detection Conditions]Insufficient memory detected on print-page buffer that couldn’t compresseven one page.[Rectification Method]Imari: PLW memroy is fixed; if possible, lower the picture resolution..

16-705 SECURITY STORAGE WITHOUT HDRefer to BSD: CH16.1[Detection Conditions]

With no HDD, security storage impossible, causing a failure to registersecurity print.[Rectification Method]Check to see whether HDD is set. If there is trouble in setting HDD,check to see whether the security print operation ismistaken..

16-709 PLW COMMAND ERRORRefer to BSD: CH16.1[Detection Conditions]During PLW processing, ART EX command error occurs.[Rectification Method]Cancel the job and re-execute..

16-713 DETECT ERROR IN IMAGERRefer to BSD: CH16.1[Detection Conditions]During image processing, an image error occurs.[Rectification Method]Data that will cause the error is being used within the print data;alter or remove this data..

16-721 OTHER ERRORSRefer to BSD: CH16.1[Detection Conditions]During printing, an unanticipated error occurs.[Rectification Method]Re-execute the same job, and after confirming the type of error, requesthelp from Support G

16-726 CANNOT SWITCH DECOMPOSER <AUTOMATIC JUDGMENT ERROR>Refer to BSD: CH16.1[Detection Conditions]Print language automatic judgment error.[Rectification Method]Do Fix-Choose on the Decomposer either thru the operating panel or thrua command..

16-730 ART COMMAND INVALID <ART COMMAND ERROR>Refer to BSD: CH16.1[Detection Conditions]ART IV command error.[Rectification Method]Delete non-support command(s) from data, re-print..

16-748 HDD FULLRefer to BSD: CH16.1[Detection Conditions]HD is detected as full when attempting to acces it; job is terminated.[Rectification Method]Empty the HDD capacity, execute re-print..

16-749 XJCL SYNTAX ERROR <JCL STRUCTURE ERROR>Refer to BSD: CH16.1[Detection Conditions]Error detected in JCL command structure [architecture?][Rectification Method]Revise the command..

16-760 DECOMPOSE ERROR <PS DECOMPOSE ERROR?>Refer to BSD: CH16.1

[Detection Conditions]Error occurs during decompose processing.[Rectification Method]Re-transmit the job. (If it re-occurs the execution environment/datamust be checked).

16-761 FIFO EMPTY <IMAGE OUTPUT>Refer to BSD: CH16.1[Detection Conditions]Image Expansion error. (FIFO Empty Error)[Rectification Method]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>Refer to BSD: CH16.1[Detection Conditions]Non-loaded print language, not-included function (print language, printutility, etc.) requested. (The decomposer specified byPJL or Auto SW is not included.)[Rectification Method]Do fix-choose for Decomposer thru Operating Panel or thru a command..

103-203 MACHINE CODE FAILRefer to BSD: CH16.1[Detection Conditions] ProductNo Fail (no initialization)[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing:If the trouble persists, successively change the ESS PWB (PL13.1) or MCUPWB (PL13.1). (The 2 PWBs cannot be changedat the same time.) If the trouble still persists, ask for help from TSPor Support G..

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

103-207 ALL MACHINE CODES MISMATCHRefer to BSD: CH16.1[Detection Conditions]Even 1 of the ProductNos held in 3 places is different.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing:If the trouble persists, successively change the ESS PWB (PL13.1) or MCU PWB (PL13.1). (The 2 PWBscannot be changed at the same time.) If the trouble still persists, ask for help from TSP or Support G..

103-208 ALL MACHINE CODES MISMATCHRefer to BSD: CH16.1[Detection Conditions]Even 1 of the Serial Numbers held in 3 places is different.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing:

If the trouble persists, successively change the ESS PWB (PL13.1) or MCUPWB (PL13.1). (The 2 PWBs cannot be changed at the same time.) If thetrouble still persists, ask for help from TSP or Support G

103-320 EEPROM FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality occurs on writing in ESS Board SEEPROM[Rectification Method] Change ESS PWB (PL13.1).

103-321 BACKUP SRAM FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality occurs on writing in ESS Board NVM[Rectification Method] Change ESS PWB (PL13.1).

103-330 ESS ROM DIMM #3 CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Fail detected during check of ESS ROM DIMM #3.[Rectification Method] Pull out ESS ROM DIMM #3. If the troublepersists, change ESS ROM DIMM #3.

103-331 ESS ROM DIMM #1 NOT FOUNDRefer to BSD: CH16.1[Detection Conditions]Detects that ESS ROM DIMM #1 is not set in place.[Rectification Method] Set ESS ROM DIMM #1 in place.. If the troublepersists after setting it in place, change ESS PWB.(PL13.1)

103-332 ESS STANDARD ROM ERRORRefer to BSD: CH16.1[Detection Conditions] Error detected in the standard ROM loaded intothe ESS.[Rectification Method] Take out the standard ROM loaded into the ESS. Ifthe trouble persists, change the standard ROMloaded into the ESS..

103-333 ASIC FAIL (PANTHER-T)Refer to BSD: CH16.1[Detection Conditions] Panther error detected.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing: Change ESS PWB (PL13.1)

103-334 STANDARD FONT ROM ERRORRefer to BSD: CH16.1[Detection Conditions] Abnormality detected in Standard Loaded Font ROM.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing: Change Font ROM.

103-335 FONT ROM NOT FOUNDRefer to BSD: CH16.1[Detection Conditions] Font ROM not detected as being in place.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing: Set Font ROM. in place.

103-336 ESS RAM DIMM #3 W/R CHECK FAILRefer to BSD: CH16.1

[Detection Conditions]Error detected in ESS RAM DIMM #3 during Read/Write Check.[Rectification Method]Take out ESS RAM DIMM #3. If the trouble continues, change the ESS ROMDIMM #3.103-337 ESS STANDARD RAM ERRORRefer to BSD: CH16.1[Detection Conditions]Error detected in ESS Standard-Loaded RAM[Rectification Method]Take out ESS RAM DIMM #3. If the trouble continues, execute thefollowing: Change the ESS ROM PWB (PL13.1).

103-338 SAME FONT ROMs FOUNDRefer to BSD: CH16.1[Detection Conditions]Detects that the same Font ROM is in place.[Rectification Method]Check the Font ROM. If the trouble continues, execute the following:Change the ESS PWB (PL13.1)

103-339 ROM DIMM OF ANOTHER PRODUCT FOUNDRefer to BSD: CH16.1[Detection Conditions]Detects that the ROM DIMM for a different type of machine is in place.[Rectification Method]Check the ROM DIMM, and put in the proper ROM DIMM. If the troublecontinues, execute the following: Change the ESSPWB (PL13.1)

103-372 IOT sc SOFT FAILRefer to BSD: CH16.1[Detection Conditions]IOT Controller Soft problem. A problem occurred during softwareprocessing [running?], and further processing [running?]cannot occur.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing:1. Re-install ESS software.2. Change the ESS PWB (PL13.1).

116-200 MAIN PWBA IC FAILRefer to BSD: CH16.1[Detection Conditions] Abnormality on IC within the ESS PWB detected.[Rectification Method] Change the ESS PWB (PL13.1)

116-201 HDD FAILRefer to BSD: CH16.1[Detection Conditions]HDD could not be booted up due to HDD abnormality detected during boot-up.[Rectification Method]Turn the power off/on, and if the trouble persists, execute thefollowing:1. Execute HDD Diagnosis (DC355)2. Change HDD (PL13.1)3. Change ESS PWB (PL13.1)

116-206 TIMER FAILRefer to BSD: CH16.1[Detection Conditions] Timer abnormality detected.[Rectification Method] Change ESS PWB (PL13.1)

116-207 ETHERNET BOARD FAILRefer to BSD: CH16.1[Detection Conditions] Ethernet Board Fail detected.[Rectification Method] Does not occur with DPC 2220 Code.

116-209 FONT ROM DIMM #1 CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected when ESS Font ROM Dimm #1 is checked.[Rectification Method]Take out ESS Font ROM DIMM #1. If the trouble persists, change ESS FontROM DIMM #1..

116-310 FONT ROM DIMM #2 CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected when ESS Font ROM Dimm #2 is checked.[Rectification Method]Take out ESS Font ROM DIMM #2. If the trouble persists, change ESS FontROM DIMM #2.

116-311 FONT ROM DIMM #3 CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected when ESS Font ROM Dimm #3 is checked.[Rectification Method]Take out ESS Font ROM DIMM #3. If the trouble persists, change ESS FontROM DIMM #3.

116-314 FONT ROM DIMM #3 CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Ethernet abnormality detected.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:Change ESS PWB (PL13.1)

116-315 ESS RAM DIMM #1 W/R CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected at ESS RAM DIMM #1 W/R.[Rectification Method]Take out ESS RAM DIMM #1. If the trouble continues, change ESS RAM DIMM#1..

116-316 ESS RAM DIMM #2 W/R CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected at ESS RAM DIMM #2 W/R.[Rectification Method]Take out ESS RAM DIMM #2. If the trouble continues, change ESS RAM DIMM#2.

116-317 ESS RAM DIMM #2 W/R CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected during check of standard ROM DIMM.[Rectification Method]Take out standard ROM DIMM. If the trouble continues, change standardROM DIMM.

116-318 OPTION ROM DIMM CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected during check of Option ROM DIMM.[Rectification Method]Take out Option ROM DIMM. If the trouble continues, change Option ROMDIMM.

116-319 SERIAL FAILRefer to BSD: CH16.1[Detection Conditions]During Serial port Initialization Fail, there is no Serial Board.[Rectification Method]Does not occur with DPC 2220 Code..

116-320 STREAMZ SOFT FAILRefer to BSD: CH16.1[Detection Conditions]A problem occurs during Streamz Fatal Error software processing, andfurther processing cannot be done.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:1. Reinstall ESS Software.2. Change ESS PWB (PL13.1)

116-321 SYSTEM SOFT FAILRefer to BSD: CH16.1[Detection Conditions]A problem occurs during software processing, and further processingcannot be done.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:3. Reinstall ESS Software.4. Change ESS PWB (PL13.1)

116-322 TRAP FAILRefer to BSD: CH16.1[Detection Conditions] Unusual CPU processing occurs.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:Change ESS PWB (PL13.1).

116-323 ESS NVRAM W/R CHECK FAILRefer to BSD: CH16.1[Detection Conditions]Abnormality detected during ESS PWB NVM Read/Write Check.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:Change ESS PWB (PL13.1)

116-324 EXCEPTION FAILRefer to BSD: CH16.1[Detection Conditions] Unusual CPU processing detected.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:Change ESS PWB (PL13.1)

116-325 ESS FAN FAILRefer to BSD: CH16.1[Detection Conditions] Abnormality occurs in ESS Fan rotation.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:

1. Change ESS Fan (PL13.1)2. Change ESS PWB (PL13.1)

116-326 ESS ROM DIMM #1 FLASH FAILRefer to BSD: CH16.1[Detection Conditions]ESS ROM DIMM #1 Flash Fail detected.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:3. Take out ESS ROM DIMM #14. Change ESS ROM DIMM #1.

116-327 ESS ROM DIMM #2 FLASH FAILRefer to BSD: CH16.1[Detection Conditions]ESS ROM DIMM #2 Flash Fail detected.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:5. Take out ESS ROM DIMM #26. Change ESS ROM DIMM #2

116-328 L2 CACHE FAILRefer to BSD: CH16.1[Detection Conditions] L2 Cache Fail detected.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:7. Change ESS PWB (PL13.1)

116-329 SERIAL I/F SOFT FAILRefer to BSD: CH16.1[Detection Conditions]Serial I/F-related system call error detected.[Rectification Method] Does not occur with DPC 2220.

116-330 HDD FILE SYSTEM FAILRefer to BSD: CH16.1[Detection Conditions]Error or HDD not formatted in check on HDD when power is switched on.[Rectification Method]Switch power off/on, and if the trouble continues, execute thefollowing:1. Execute HDD Diagnosis (DC355)2. Change HDD (PL13.1)3. Change ESS PWB(PL13.1).

116-332 INVALID LOG INFORefer to BSD: CH16.1[Detection Conditions] Log-related abnormality detected.[Rectification Method]Switch power off/on, and if the trouble continues, execute thefollowing:4. Remove HDD once and turn the power off/on, then put HDD back on andturn the power on.5. Execute HDD Diagnosis (DC355).6. Change ESS PWB (PL13.1)

116-340 SHORT OF MEMORYRefer to BSD: CH16.1[Detection Conditions] Shortage of memory detected.[Rectification Method]Switch power off/on, and if the trouble continues, execute thefollowing:

7. Add memory8. Take out PostScript option.

116-341 ROM DIMMs MISMATCHRefer to BSD: CH16.1[Detection Conditions]Improper version of several installed ROM DIMMs. An unusable combinationof ROM DIMMs is installed. When more thanone ROM DIMM is installed, it is necessary to match major versions andminor versions.[Rectification Method]Does not occur with DPC 2220, since it only takes 1 ROM.

116-345 TOKEN RING BOARD FAILRefer to BSD: CH16.1[Detection Conditions] Token Ring Control IC Acesseror [?][Rectification Method]Does not occur with DPC 220, since PWB in question does not exist..

116-347 LOCALTALK BOARD FAILRefer to BSD: CH16.1[Detection Conditions] LocalTalk Board does not boot up properly.[Rectification Method]Does not occur with DPC 2220, since PWB in question does not exist.

116-349 SIF FAIL ON CALLING PFLITE FUNCTIONRefer to BSD: CH16.1[Detection Conditions] SIF error on calling Pflite Function.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:Change ESS PWB (PL13.1)

116-350 APPLETALK SOFT FAILRefer to BSD: CH16.1[Detection Conditions]Overall fatal error on AppleTalk. A problem occurs during softwareprocessing, and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:1. Re-install ESS software.2. Change ESS PWB (PL13.1)

116-351 ETHERTALK SOFT FAILRefer to BSD: CH16.1[Detection Conditions]EtherTalk-related fatal error. A problem occurs during softwareprocessing, and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:3. Re-install ESS software.4. Change ESS PWB (PL13.1).

116-352 NETWARE SOFT FAILRefer to BSD: CH16.1[Detection Conditions]NetWare-related fatal error. A problem occurs during softwareprocessing, and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:5. Re-install ESS software.6. Change ESS PWB (PL13.1)

116-353 IPD SOFT FAILRefer to BSD: CH16.1[Detection Conditions]Ipd-related fatal error. A problem occurs during software processing,and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:7. Re-install ESS software.8. Change ESS PWB (PL13.1)

116-355 SNMP AGENT SOFT FAILRefer to BSD: CH16.1[Detection Conditions]SNMP Agent-related fatal error. A problem occurs during softwareprocessing, and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:9. Re-install ESS software.10. Change ESS PWB (PL13.1).

116-356 EWS SOFT FAILRefer to BSD: CH16.1[Detection Conditions]EWS-related fatal error. A problem occurs during software processing,and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:11. Re-install ESS software.12. Change ESS PWB (PL13.1)

116-357 PS SOFT FAILRefer to BSD: CH16.1[Detection Conditions]PS Fatal System error. A problem occurs during software processing, andfurther processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:Change ESS PWB (PL13.1)

116-358 SALUTATION SOFT FAILRefer to BSD: CH16.1[Detection Conditions]Salutation-related fatal error. A problem occurs during softwareprocessing, and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:1. Re-install ESS software.2. Change ESS PWB (PL13.1).

116-359 PLW SOFT FAILRefer to BSD: CH16.1[Detection Conditions]Fatal error on PLW. A problem occurs during software processing, andfurther processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:3. Re-install ESS software.4. Change ESS PWB (PL13.1)

116-360 SMB SOFT FAILRefer to BSD: CH16.1[Detection Conditions]

SMB-related fatal error. A problem occurs during software processing,and further processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:5. Re-install ESS software.6. Change ESS PWB (PL13.1)

116-361 SPOOL FATAL HDDRefer to BSD: CH16.1[Detection Conditions]SPL HDD fatal error.SpoolCont detects an error during HDD access.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:7. Execute HDD Diagnosis (DC355)8. Change HDD (PL13.1)9. Change ESS PWB (PL13.1).

116-365 SPOOL FATALRefer to BSD: CH16.1[Detection Conditions]SPL fatal error. Problem occurs during software processing, and nofurther processing can occur.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:10. Re-install ESS software.11. Change ESS PWB (PL13.1)

116-366 SPOOL FATALRefer to BSD: CH16.1[Detection Conditions]Report Generator malfunction. Problem occurs during software processing,and no further processing can occur.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:Change ESS PWB (PL13.1)

116-367 PARALLEL I/F SOFT FAILRefer to BSD: CH16.1[Detection Conditions]Overall Parallel fatal error. Problem occurs during software processing,and no further processing can occur.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:1. Re-install ESS software.2. Change ESS PWB (PL13.1).

116-368 DUMP PRINT FAILRefer to BSD: CH16.1[Detection Conditions]DumpPrint fatal error. Problem occurs during software processing, and nofurther processing can occur.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:3. Re-install ESS software.4. Change ESS PWB (PL13.1)

116-370 XJCL FAILRefer to BSD: CH16.1[Detection Conditions]XJCL fatal error. Problem occurs during software processing, and nofurther processing can occur.[Rectification Method]

Turn power off/on, and if the trouble continues, execute the following:5. Re-install ESS software.6. Change ESS PWB (PL13.1)

116-372 P-FORMATTER FAILRefer to BSD: CH16.1[Detection Conditions]P-Formatter fatal error. Problem occurs during software processing, andno further processing can occur.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:Change ESS PWB (PL13.1).

116-374 AUTO SWITCH FAILRefer to BSD: CH16.1[Detection Conditions]AutoSW fatal error. Problem occurs during software processing, and nofurther processing can occur.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:1. Re-install ESS software2. Change ESS PWB (PL13.1)

116-377 VIDEO DMA FAILRefer to BSD: CH16.1[Detection Conditions] Video DMA Fail detected.[Rectification Method]Turn power off/on, and if the trouble continues, execute the following:Change ESS PWB (PL13.1)

116-390 STANDARD ROM AND NVM VERSION MISMATCHRefer to BSD: CH16.1[Detection Conditions]Standard ROM and NVM version mismatch detected.[Rectification Method]Following the LCD display, initialize the NVM. (If not initializing NVM,use version compatible with Standard ROM.).

116-398 IPP SOFT FAILRefer to BSD: CH16.1[Detection Conditions]IPP-related fatal error. Problem occurs during software processing, andfurther processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:1. Re-install ESS software2. Change ESS PWB (PL13.1)

116-399 JME SOFT FAILRefer to BSD: CH16.1[Detection Conditions]JME-related fatal error. Problem occurs during software processing, andfurther processing cannot take place.[Rectification Method]Turn power off/on, and if the trouble persists, execute the following:3. Re-install ESS software4. Change ESS PWB (PL13.1).

116-701 DOUBLE-SIDED COPY STOP (ryomen-nakiwakare) EXECUTEDRefer to BSD: CH16.1[Detection Conditions] Double-sided copies cannot be printed due to lackof memory.

[Rectification Method]Imari: Either increase memory, or if no HD, add HDD.

116-702 PRINTING WITH ALTERNATIVE FONTRefer to BSD: CH16.1[Detection Conditions] Printing done with alternative font.[Rectification Method]Unnecessary.

116-703 PS INTERPRET ERRORRefer to BSD: CH16.1[Detection Conditions] Error occurs during Language-InterpretationProcessing[Rectification Method] Correct the job data.

116-710 HP-GL SPOOL FILE OVERFLOWRefer to BSD: CH16.1[Detection Conditions] HP-GL/2 memory overflow[Rectification Method] Increase HP-GL spool size. Or add HDD.

116-711 PLW FORM COMPOSITION [synthesis?] ERRORRefer to BSD: CH16.1[Detection Conditions]PL Form image size/direction is different from paper size/direction, sothat composition [synthesis?] is impossible.[Rectification Method]Imari: Choose paper that is consistent with the size and direction ofthe form that is registered..

116-712 PLW FORM LACKS CAPACITYRefer to BSD: CH16.1[Detection Conditions]Insufficient capacity in RAM Disk or Hard Disk, so that PLW Form/LogoData cannotbe registered.[Rectification Method]After confirming registered Form/Logo on the utility on the OperatingPanel, delete unnecessary items. If it is a RAM Disk,increase the capacity allotment.

116-714 HP-GL COMMAND ERROR DETECTEDRefer to BSD: CH16.1[Detection Conditions] HP-GL/2 Command Error[Rectification Method]Data that will cause an error within the print data is being used;revise or delete such data.

116-715 PLW FORM REGISTRATION ERRORRefer to BSD: CH16.1[Detection Conditions]During PLW Form Data registration, the number of units exceeds thelimit, so registration cannot proceed.[Rectification Method]After confirming registered Form on the utility on the Operating Panel,delete unnecessary items. Or delete unnecessaryForm with the print command.

116-718 PLW FORM COMPOSITION [synthesis?] ERRORRefer to BSD: CH16.1[Detection Conditions] The designated Form is not registered.[Rectification Method]Imari: Use the registered Form or register the necessary Form..

116-737 INSUFFICIENT ART USER DEFINITION AREARefer to BSD: CH16.1[Detection Conditions]During registration of data on user definition (non-standard characters,patterns, etc.) in Art, insufficient RAM capacitymakes registration impossible.[Rectification Method]Delete User Definition Data that has been registered. Or else increasecapacity allotment.

116-738 PLW FORM COMPOSITION [synthesis?] ERRORRefer to BSD: CH16.1[Detection Conditions]Form image size/direction is different from paper size/direction, sothat composition [synthesis?] is impossible.[Rectification Method]Choose paper that is consistent with the size and direction of the formthat is registered.

116-739 INSUFFICIENT FORM / LOGO CAPACITYRefer to BSD: CH16.1[Detection Conditions]Lack of RAM Disk or Hard Disk capacity makes Form/Logo registrationimpossible.[Rectification Method]After confirming registered Form/Logo on the utility on the OperatingPanel, delete unnecessary items. If it is a RAM Disk,increase the capacity allotment.

116-740 VALUE OPERATION [calculating?] ERRORRefer to BSD: CH16.1[Detection Conditions]The value operation [calculation?] executed within the interpreterexceeds the limit.[Rectification Method]Within the print data, there is/are value(s) used that exceed theprinter’s value limit; remove such data..

116-741 FORM REGISTRATION ERRORRefer to BSD: CH16.1[Detection Conditions]Registration cannot be completed because the Form Data exceeds the unitlimit.[Rectification Method]After confirming registered Form on the utility on the Operating Panel,delete unnecessary items. Or delete unnecessaryForms with the print command.

116-742 LOGO REGISTRATION ERRORRefer to BSD: CH16.1[Detection Conditions]Registration cannot be completed because the Logo Data exceeds the unitlimit.[Rectification Method]After confirming registered Logo(s) on the utility on the OperatingPanel, delete unnecessary items. Or delete unnecessaryLogo(s) with the print command.

116-743 FORM/LOGO SIZE OVERFLOWRefer to BSD: CH16.1[Detection Conditions]The Form/Logo Registration Impossible (insufficient space) Received Data(Form/Logo) exceeds the registered buffer size.

[Rectification Method]Increase the size of the Form Registration Area on the operating panel.Or add HD.

116-745 ART COMMAND ERRORRefer to BSD: CH16.1[Detection Conditions]During decomposition, there is a grammatical error; Decompose checks alltypes of value limits for excesses.[Rectification Method]Command Revision, etc Imari: Change Art command that showed the error..

116-746 FORM COMPOUND [synthesis?] ERRORRefer to BSD: CH16.1[Detection Conditions] The designated Form is not registered.[Rectification Method]Use registered Form or register the necessary Form.

116-747 BLANK PAPER PAGE DETECTEDRefer to BSD: CH16.1[Detection Conditions]Subtracting paper margin from valid coordinates gives a negative value.[Rectification Method]Unnecessary.

116-748 BLANK PAPER PAGE DETECTEDRefer to BSD: CH16.1[Detection Conditions]Image data does not exist within page data.[Rectification Method]Unnecessary..