Status Codes Table 1 Status Code List

Status
Table 1 Status Code List Code Fault Description RAP BSD
Status 010-310 There is a Heat Roll Thermistor 1 over temperature condition. Y 10.5
Code Fault Description RAP BSD 010-311 There is a Heat Roll Thermistor 2 over temperature condition. Y 10.5
005-100 The Feed Stop Sensor detected that a document was inserted N 6.2 010-312 There is a Heat Roll Thermistor 3 over temperature condition. Y 10.5
and then pulled out. Check the following: damaged original, dam- 010-313 An overheat condition caused the Overheat Thermostat to open. Y 10.3
aged or contaminated document transport rolls. 10.4
005-101 The Feed Stop Sensor detected another document when the N 6.2 010-314 There is a Heat Roll Thermistor 2 overheat condition. Y 10.5
original feed stopped.
010-315 There is a Heat Roll Thermistor 4 overheat condition. Y 10.5
The Registration Sensor detected another document when the
010-316 The Thermistor 1 detected a low fuser temperature. The Heat Y 10.5
pre-feed stopped after completion.
Check the following: damaged original, damaged or contami- Roll temperature was 90°C or lower.
nated transport document rolls. 010-317 The Thermistor 3 detected a low fuser temperature. The Heat Y 10.5
005-102 The Right Skew Sensor detected a document during original N 6.2 Roll temperature was 90°C or lower.
feed. 1.10 010-318 There is an open circuit in the Heat Roll Thermistor 1 or in its wir- N 10.5
The IIT Cover Sensors were not actuated. Ensure that the Docu- ing
ment Handler is seated correctly. 010-319 There is an open circuit in the Heat Roll Thermistor 2 or in its wir- N 10.5
Check the following: obstruction in document transport, damaged ing
original, damaged or contaminated document transport rolls. 010-320 There is an open circuit in the Heat Roll Thermistor 3 or in its wir- N 10.5
005-103 The Left Skew Sensor detected a document during original feed. N 6.2 ing
The IIT Cover Sensors were not actuated. Ensure that the Docu- 1.10 010-321 There is an open circuit in the Heat Roll Thermistor 4 or in its wir- N 10.5
ment Handler is seated correctly. ing
Check the following: obstruction in document transport, damaged
010-322 The temperature at Thermistor 1 did not reach the ready temper- Y 10.5
original, damaged or contaminated document transport rolls.
ature in a specified amount of time.
005-104 The Registration Sensor detected that the document being fed is N 6.2
010-323 The temperature at Thermistor 3 did not reach the ready temper- Y 10.5
over the maximum length during original feed.
ature in a specified amount of time.
Check the following: document drives binding, damaged original,
damaged or contaminated document transport rolls. 010-324 Fuser Drive Motor Error Y 10.2

005-110 The Feed Stop Sensor did not detect the document lead edge at Y 6.2 010-325 RH Exhaust Fan Error N 10.7
the scheduled timing during original feed. 010-326 LH Exhaust Fan Error N 10.7
005-111 The Feed Stop Sensor did not detect the document trail edge at N 6.2 010-970 The fusing temperature dropped below a point where the toner N 10.5
the scheduled timing during original feed. does not fuse correctly. The printing stops and the paper is
005-112 The Registration Sensor did not detect the document lead edge N 6.2 ejected. The machine goes to the print ready state when the tem-
at the scheduled timing during original feed. perature reaches the specified value.

005-113 The Registration Sensor did not detect the document trail edge at
the scheduled timing during original feed.
005-300 One of the IIT Cover Open Sensors was detected to be open
while the machine was in operation.
The IIT Cover Sensors were not actuated. Ensure that the Docu-
ment Handler is seated correctly.
005-301 One of the IIT Cover Open Sensors was detected to be open
while the machine was in standby.
The IIT Cover Sensors were not actuated. Ensure that the Docu-
ment Handler is seated correctly.
005-900 Paper was detected on any IIT sensor when power was switched
on or when original feed is stopped while the machine was not in
operation.
N 6.2 041-310 There is a communication error between the CP-Cont PWB and N 3.1
the IOT PWB during the normal mode of operation. Replace the
IOT PWB (PL 8.1).
N 1.10
041-311 There is a communication error between the CP-Cont PWB and N 3.1
the IOT PWB during the boot sequence. Ensure that the USB
cable is seated correctly at the CP control PWB and the IOT
PWB. If the problem continues, replace the IOT PWB (PL 8.1).
N 1.10
041-312 There is an IOT PWB communication command length error. N 3.7
Ensure that the USB cable is seated correctly at the CP control
PWB and the IOT PWB. If the problem continues, replace the IOT
PWB (PL 8.1). If the problem continues, replace the CP Control
Y 6.1, 6.2
PWB (PL 8.6).

10/31/05
1
 Table 1 Status Code List Table 1 Status Code List
Status Status
Code Fault Description RAP BSD Code Fault Description RAP BSD
041-313 A cut length error causes the machine to cut and eject the paper. N 3.1 061-311 A ROS on interruption occurred during the exposure preparation N 6.7
Re-install CP Control PWB firmware. operation for Roll 1. The IOT waits for a print recovery state from
041-314 No Report on Image Length Error. Replace the IOT PWB (PL N 3.1 the CP-Cont PWB. Re-install the IOT PWB firmware.
8.1). 061-312 A ROS on interruption occurred during the exposure preparation N 6.7
042-310 The hardware reset did not cause the IOT PWB Watch Dog N 3.1 operation for Roll 2. The IOT waits for a print recovery state from
Timer to reset. Re-install IOT PWB firmware the CP-Cont PWB. Re-install the IOT PWB firmware.
042-311 There was an IOT PWB Flash ROM Error. Switch the power off N 3.1 061-314 A ROS on interruption occurred during the exposure preparation N 6.7
then on. Replace the IOT PWB (PL 8.1). operation for Manual feed. The IOT waits for a print recovery
042-312 The USB cable is disconnected between the CP-Cont PWB and N 3.1 state from the CP-Cont PWB. Re-install the IOT PWB firmware.
the IOT PWB. Ensure that the cable is seated correctly and is not 061-315 A ROS on interruption occurred before receiving a Clear Feature N 6.7
damaged. signal. Re-install the CP Control PWB firmware.
042-313 USB Video Control: Interrupt Status Underrun Error. Replace the N 3.7 061-316 An error in the LPH Controller on the IOT Control PWB was N 6.4, 6.5,
IOT PWB (PL 8.1). If the problem still exists, replace the CP Con- detected. (FPGA Initializing). 6.6
trol PWB (PL 8.6). Check for +5 VDC at J440-2 at the IOT PWB.
042-314 There was checksum error that caused the IOT PWB NVRAM N 3.1 061-317 An error in the LPH Controller on the IOT Control PWB was N 6.4, 6.5,
Error (both Flash & EEPROM). Replace the IOT PWB and the detected. (Data Acquisition) 6.6
EEPROM (PL 8.1). Replace the IOT PWB (PL 8.1). 1.5
042-600 There was checksum error that caused the IOT PWB EEPROM N 3.1 061-318 An error in the LPH Controller on the IOT Control PWB was N 6.4, 6.5,
Out Of Range error. Replace the IOT PWB and the EEPROM (PL detected. (Data Transmission) 6.6
8.1). Replace the IOT PWB (PL 8.1). 1.5
042-601 There was no acknowledgement from the EEPROM on the IOT N 3.1 061-319 An error in the LPH Controller on the IOT Control PWB was N 6.4, 6.5,
PWB. Replace the IOT PWB. If the fault recurs, re-install the orig- detected. (Data Reading) 6.6
inal IOT PWB and replace the EEPROM. Ensure that the ribbon cable is seated correctly between the LPH 1.5
Interface PWB and the LPH and is not damaged.
042-602 There was checksum error that caused the IOT PWB NVRAM N 3.1
Error (Sum Mismatch). Enter IOT DC131 and save the NVM val- An LVPS 5C fault. Check for AC power to LVPS 5C.
ues. If the fault still exists, replace the IOT PWB or the EEPROM 061-320 An error in the LPH Controller on the IOT Control PWB was N 6.4, 6.5,
(PL 8.1). detected. (Data Comparison) 6.6
Ensure that the ribbon cable is seated correctly between the LPH 1.5
042-603 There was checksum error that caused the IOT PWB VRAM N 3.1
Error (Flash ROM). Enter IOT DC131 and save the NVM values. Interface PWB and the LPH and is not damaged.
If the fault still exists, replace the IOT PWB (PL 8.1). An LVPS 5C fault. Check for AC power to LVPS 5C.

042-604 There was checksum error that caused the IOT PWB NVRAM N 3.1 061-321 Abnormally high temperature was detected for the LPH. Ther- Y 6.4
mistor Error (LPH Overheat). DC330 061-250 indicated 150 or
Error (EEPROM). Enter IOT DC131 and save the NVM values. If
the fault still exists, replace the EEPROM (PL 8.1). less.

042-605 There was checksum error that caused the IOT PWB EEPROM N 3.1 061-322 There is an open circuit to the LPH Thermistor Error. DC330 061- N 6.4
Verify Error (Recycling Label). Replace the EEPROM (PL 8.1). 250 indicated 1000 or higher.

042-606 There was checksum error that caused the IOT PWB EEPROM N 3.1 062-310 An abnormal SUM value was detected in the user part program N 3.6
on the IIT PWB. Reinstall IIT firmware. If the fault still exists,
Verify Error (Recycling Data). Replace the EEPROM (PL 8.1).
replace the IIT PWB (PL 8.3).
042-607 There was checksum error that caused the IOT PWB EEPROM N 3.1
Verify Error (NVRAM). Replace the EEPROM (PL 8.1). 062-311 An abnormal SUM value was detected in the boot part program N 3.6
on the IIT PWB. Replace the IIT PWB (PL 8.3).
046-310 LVPS 24B Monitor Error Y 1.7
062-312 An abnormal SUM value was detected in IPS data on the IIT N 3.6
046-311 LVPS 24C Monitor Error Y 1.10
PWB. Reinstall IIT firmware. If the fault still exists, replace the IIT
046-312 LVPS 5B Monitor Error Y 1.4 PWB (PL 8.3).
061-310 LVPS 5C Monitor Error Y 1.5 062-313 An error was detected during the CPU built-in RAM Read/Write N 3.1
check on the IIT PWB. Replace the IIT PWB (PL 8.3).

10/31/05
2
 Table 1 Status Code List Table 1 Status Code List
Status Status
Code Fault Description RAP BSD Code Fault Description RAP BSD
062-314 Error was detected during Read/Write check for the areas except N 3.1 062-352 There was an operation error caused by the ASIC SDC6W TRC N 3.1
the data backup area of the External RAM. (IIT PWB). Replace module. Reinstall IIT firmware. If the fault still exists, replace the
the IIT PWB (PL 8.3). IIT PWB (PL 8.3).
062-315 An abnormal SUM value was detected in the system data stored N 3.1 062-353 There was an operation error caused by the ASIC SDC6W DF N 3.1
in the EEPROM on the IIT PWB. Initialize IIT NVM (DC131). If the module.Reinstall IIT firmware. If the fault still exists, replace the
fault still exists, replace the IIT PWB (PL 8.3). IIT PWB (PL 8.3).
062-317 Abnormal data was detected in the error history/error log stored N 3.1 062-354 There was an operation error caused by the ASIC IPS6W BKG N 3.1
in the EEPROM on the IIT PWB. Initialize IIT NVM (DC131). If the module.Reinstall IIT firmware. If the fault still exists, replace the
fault still exists, replace the IIT PWB (PL 8.3). IIT PWB (PL 8.3).
062-318 Error was detected in the feed count/recycle data stored in the N 3.1 062-355 There was an operation error caused by the ASIC IPS6W RE N 3.1
EEPROM on the IIT PWB. Replace the IIT PWB (PL 8.3). module.Reinstall IIT firmware. If the fault still exists, replace the
062-320 An error was detected while erasing the Flash ROM on the IIT N 3.1 IIT PWB (PL 8.3).
PWB. Reinstall IIT firmware. If the fault still exists, replace the IIT 062-356 There was an operation error caused by the ASIC IPS6W TRC N 3.1
PWB (PL 8.3). module.Reinstall IIT firmware. If the fault still exists, replace the
062-321 An error was detected while writing data into the Flash ROM on N 3.1 IIT PWB (PL 8.3).
the IIT PWB. Reinstall IIT firmware. If the fault still exists, replace 062-357 There was an operation error caused by the ASIC IPS6W DF N 3.1
the IIT PWB (PL 8.3). module.Reinstall IIT firmware. If the fault still exists, replace the
062-322 The value written in the Flash ROM on the IIT PWB is different N 3.1 IIT PWB (PL 8.3).
from the one written by user. Reinstall IIT firmware. If the fault still 062-358 There was an operation error caused by the ASIC IPS6W SG N 3.1
exists, replace the IIT PWB (PL 8.3). module.Reinstall IIT firmware. If the fault still exists, replace the
062-324 Error was detected while writing data into the EEPROM on the IIT N 3.1 IIT PWB (PL 8.3).
PWB. Replace the IIT PWB (PL 8.3). 062-359 There was an operation error caused by the FPGA USBC. N 3.1
062-325 The value written in the EEPROM on the IIT PWB is different N 3.1 Replace the IIT PWB (PL 8.3).
from the one written by user. Replace the IIT PWB (PL 8.3). 062-360 There was an operation error caused by the USB IC. Replace the N 3.1
062-340 There was a read/write check error for the ASIC SDC6W register/ N 3.1 IIT PWB (PL 8.3).
built-in memory on the IIT PWB. Replace the IIT PWB (PL 8.3). 062-370 The average output value for IC units in the CIS was lower than N 6.3
062-341 There was a read/write check error for the ASIC IPS6W register/ N 3.1 or equal to the limit value in every IC. Use component control to
built-in memory on the IIT PWB. Replace the IIT PWB (PL 8.3). try to switch on the lamps. Also check for +5 VDC at the CIS
PWB.
062-342 There was a read/write check error for the SDRAM used in the N 3.1
ASIC IPS6W BKG module. Replace the IIT PWB (PL 8.3). 062-371 The average output value for IC units in the CIS was lower than N 6.3
or equal to the limit value in a least on IC. Use component control
062-343 There was a bus check error between the ASIC SDC6W and the N 3.1
to try to switch on the lamps. Also check for +5 VDC at the CIS
ASIC IPS6W. Replace the IIT PWB (PL 8.3).
PWB.
062-344 There was a bus check error between ASIC IPS6W and the N 3.1
062-372 No sensor connections were detected (initialization of input FIFO N 6.3
FPGA USBC. Replace the IIT PWB (PL 8.3).
from the sensor was not completed). Ensure that the cable is
062-345 There was a bus check error between the FPGA USBC and the N 3.1 seated correctly between the CIS PWB and IIT PWB and that it is
USB IC. Replace the IIT PWB (PL 8.3). not damaged. If the wiring is OK, replace the CIS PWB (PL 3.2).
062-350 There was an operation error caused by the ASIC SDC6W SHDC N 3.1 If the problem still exists, replace the IIT PWB (PL 8.3).
module. Reinstall IIT firmware. If the fault still exists, replace the
062-390 The CPU Watch Dog timer activated software reset. (IIT PWB). N 3.1
IIT PWB (PL 8.3).
Reinstall IIT firmware.
062-351 There was an operation error caused by the ASIC SDC6W VDAC N 3.1 062-940 A sequence error occurred while receiving diagnostic parame- N 3.1
module. Reinstall IIT firmware. If the fault still exists, replace the ters. (IIT PWB). Reinstall IIT firmware. If the problem still exists,
IIT PWB (PL 8.3).
reinstall the CP Control firmware.

10/31/05
3
 Table 1 Status Code List Table 1 Status Code List
Status Status
Code Fault Description RAP BSD Code Fault Description RAP BSD
062-941 A parameter error occurred while receiving diagnostic parame- N 3.1 071-102 Peeled-off core was detected during Roll 1 feed. (Roll 1 A3 Sen- N 7.1
ters. (IIT PWB). If the problem still exists, reinstall the CP Control sor was off)
firmware.
NOTE: The trail edge of the roll is glued to the core. When the roll
062-942 The diagnosis was aborted by the abort diagnostic request. The N 3.1
runs out of paper, the roll paper tube is pulled out of the holder.
error occurred during self diagnosis. No action required.
062-943 An original was jammed during the diagnosis that requires feed- N 6.2 Ensure that the Roll Paper Tube (PL10.1/PL10.2) is attached and
ing an original. The error occurred during self diagnosis. No rotates normally.
action required. Ensure that the paper conforms to the specifications.
062-944 A cover was opened during the diagnosis that requires feeding N 1.10 071-103 The Roll 1 Cut Trigger Sensor was not actuated within a specified Y 8.2
an original. The error occurred during self diagnosis. No action time.
required. 071-104 The Roll 1 Cut Trigger Sensor was not de-actuated within a spec- Y 8.2
062-945 An error occurred during diagnosis. The error occurred during N 3.1 ified time.
self diagnosis. No action required. 071-105 A Roll 1 Cutter error was detected during printing. (Jam when N 8.2
062-946 Diagnosis is not available because the item targeted for diagno- 3.1 071-311 occurred)
sis is missing. The error occurred during self diagnosis. No action 071-300 Roll 1 Cutter Cover was detected to be open during printing. N 1.9
required. 071-301 RFC 1 Drawer was detected to be open during printing. N 1.9
062-950 C/P-Cont communication has not been established since power N 3.1 071-310 The Roll 1 Feeder Motor Clock signal cannot be detected. N 8.1
was switched on. No action required.
071-311 Cutter was moved but its completion was not detected. (The R/H Y 8.2
062-951 Communication still failed after three retries when transferring N 3.1 Roll 1 Cutter Switch or L/H Roll 1 Cutter Switch was not actu-
data (Text, ACK, NAK) to the CP-Cont PWB. No action required. ated.)
062-952 The notification that operation is unavailable was received from N 3.1 071-312 Bounce was detected after the cutter motion had completed (It N 8.2
the CP-Cont. No action required. was detected that the R/H Roll 1 Cutter Switch or L/H Roll 1 Cut-
062-960 Overflow occurred during image transfer via the USB. (Data read N 3.1 ter Switch was actuated then deactuated). Refer to the 071-311
delay occurred at CP-Cont) No action required. RAP.
062-961 The IPS parameter resetting process did not complete within a N 3.1 071-313 There is a cutter position fault. Both the Roll 1 R/H Cutter Switch N 8.2
specified time. No action required. and the Roll 1 L/H Cutter Switch were actuated or deactuated at
071-100 The Roll 1 A3 Sensor did not detect paper within a specified time N 7.1 the same time. Refer to the 071-311 RAP.
during Roll 1 auto loading (forward rotation after backward rota- 071-900 The Roll 1 Cut Trigger Sensor or RFC Page Sync Sensor was N 8.2, 8.7
tion). blocked when the Front Door was closed.
Check the Roll 1 A3 Sensor for contamination or damage. 071-940 There were no pulses from the Roll 1 No Paper Sensor. Ensure N 7.1
Ensure that there is no obstruction in the paper path. that the wheel that blocks the Roll 1 No Paper Sensor moves
RFC 1 Motor fault. IOT DC 071-001 and 071-003 switch the RFC freely and is not damaged. Check the Roll 1 No Paper Sensor
1 Motor on. and the Roll 1 Set Sensor.
071-101 The Roll 1 A3 Sensor was not blocked within a specified time dur- N 7.1 The Roll 1 Set Sensor did not detect paper.
ing Roll 1 auto loading. No paper was sensed during auto load. 1.7, 8.1 071-941 The Roll 1 Cutter Cover was detected to be open when the lead N 1.9
Ensure that the roll is loaded correctly. edge was cut as the Roll was removed or when paper was
Check the Roll 1 A3 Sensor for contamination or damage. loaded. Ensure that the cover is closed.
Ensure that there is no obstruction in the paper path.
072-100 The Roll 2 A3 Sensor did not detect paper within a specified time N 7.2
Check for an RFC 1 Motor fault. IOT DC 071-001 and 071-003
during Roll 2 auto loading (forward rotation after backward rota-
switch the RFC 1 Motor on.
tion).
Check the Roll 2 A3 Sensor for contamination or damage.
Ensure that there is no obstruction in the paper path.
RFC 2 Motor fault. IOT DC 072-001 and 072-003 switch the RFC
2 Motor on.

10/31/05
4
 Table 1 Status Code List Table 1 Status Code List
Status Status
Code Fault Description RAP BSD Code Fault Description RAP BSD
072-101 The Roll 2 A3 Sensor was not blocked within a specified time dur- N 7.2 075-100 The Manual Feed Stop Sensor was not blocked within a specified N 8.6
ing Roll 2 auto loading. No paper was sensed during auto load. 1.7, 8.3 time after Pre-feed had started.
Ensure that the roll is loaded correctly. Check the Manual Feed Clutch and the Manual Feed Stop Sen-
Check the Roll 2 A3 Sensor for contamination or damage. sor.
Ensure that there is no obstruction in the paper path. Check for damage to the drive to the Manual Feed assembly.
Check for an RFC 2 Motor fault. IOT DC 072-001 and 072-003 075-101 The Manual Page Sync Sensor was not blocked within a speci- N 8.7
switch the RFC 2 Motor on. fied time.
072-102 Peeled-off core was detected during Roll 2 feed. (Roll 2 A3 Sen- 7.2 075-102 The Manual Page Sync Sensor was not unblocked within a spec- N 8.7
sor was off) ified time.
NOTE: The trail edge of the roll is glued to the core. When the roll 075-900 The Manual Feed Stop Sensor or Manual Page Sync Sensor was N 8.6, 8.7
runs out of paper, the roll paper tube is pulled out of the holder. detected to be blocked when paper was loaded.
075-940 Paper was not loaded within a specified time after missing paper N 7.3
Ensure that the Roll Paper Tube (PL10.1/PL10.2) is attached and
had been detected (during printing).
rotates normally.
075-941 The width of loaded paper was narrower than the image width N 7.3
Ensure that the paper conforms to the specifications.
during manual printing. check the Manual width sensors.
072-103 The Roll 2 Cut Trigger Sensor was not actuated within a specified N 8.4
077-100 The RFC Vertical Jam Sensor was not blocked within a specified N 8.5
time.
time.
072-104 The Roll 2 Cut Trigger Sensor was not de-actuated within a spec- N 8.4
Check the Vertical Jam Sensor and the RFC Takeaway Clutch.
ified time. Check for an obstruction in the paper path.
072-105 A Roll 2 Cutter error was detected during printing. (Jam when Check the RFC Takeaway Roll drives for damage.
072-311 occurred) 077-101 The RFC Page Sync Sensor was not blocked within a specified N 8.7, 8.5
072-300 Roll 2 Cutter Cover was detected to be open during printing. N 1.9 time.
072-301 RFC 2 Drawer was detected to be open during printing. N 1.9 Check the RFC Page Sync Sensor and the RFC Takeaway
072-310 The Roll 2 Feeder Motor Clock signal cannot be detected. N 8.3 Clutch.
072-311 Cutter was moved but its completion was not detected. (The R/H Y 8.4 Check for an obstruction in the paper path.
Roll 2 Cutter Switch or L/H Roll 2 Cutter Switch was not actu- Check the RFC Takeaway Roll drives for damage.
ated.) 077-103 The Exit Jam Sensor was not blocked within a specified time. N 10.6,
Check the Fuser Drive Control circuit. 10.2
072-312 Bounce was detected after the cutter motion had completed (It N 8.4
was detected that the R/H Roll 2 Cutter Switch or L/H Roll 2 Cut- 077-104 The RFC Vertical Jam Sensor was not unblocked within a speci- N 8.5
ter Switch was actuated then deactuated). Refer to the 072-311 fied time.
RAP. Check the Vertical Jam Sensor and the RFC Takeaway Clutch.
Check for an obstruction in the paper path.
072-313 There is a cutter position fault. Both the Roll 2 R/H Cutter Switch N 8.4
and the Roll 2 L/H Cutter Switch were actuated or deactuated at Check the RFC Takeaway Roll drives for damage.
the same time. Refer to the 072-311 RAP. 077-105 The RFC Page Sync Sensor was not unblocked within a speci- N 8.7
072-900 The Roll 2 Cut Trigger Sensor or RFC Page Sync Sensor was N 8.4, 8.7 fied time.
Check the RFC Page Sync Sensor and the RFC Takeaway
blocked when the Front Door was closed.
Clutch.
072-940 There were no pulses from the Roll 2 No Paper Sensor. Ensure N 7.2
Check for an obstruction in the paper path.
that the wheel that blocks the Roll 2 No Paper Sensor moves
Check the Registration Roll drives for damage.
freely and is not damaged. Check the Roll 2 No Paper Sensor
077-106 The Exit Jam Sensor was not unblocked within a specified time. N 10.6
and the Roll 2 Set Sensor.
The Roll 2 Set Sensor did not detect paper. Check the Exit Jam Sensor and the Fuser Drive Control circuit.

072-941 The Roll 2 Cutter Cover was detected to be open when the lead N 1.9 077-107 The pulse detection time in the Exit Motion Sensor was below the N 10.6
specified time range.
edge was cut as the Roll was removed or when paper was
loaded. Ensure that the cover is closed.

10/31/05
5
 Table 1 Status Code List Table 1 Status Code List
Status Status
Code Fault Description RAP BSD Code Fault Description RAP BSD
077-300 Swing Frame was detected to be open. Ensure that the Swing N 1.8 091-312 An Open Air Sensor Air error was detected (IOT DC330 091-251 N 9.4
Frame is closed. was 1000 or higher).
Check the Swing Frame Interlock circuit. Ensure that the sensor is mounted correctly and is not damaged.
077-301 Fuser Cover was detected to be open. Ensure that the Fuser N 1.8 Refer to BSD 9.4 and check the wiring to the Open Air Sensor.
Cover is closed. If the wiring is OK, replace the Open Air Sensor (PL 8.5).
Check the Fuser Cover Interlock circuit. 091-313 An Open Air Sensor Air error was detected (IOT DC330 091-251 N 9.4
077-302 Front Door was detected to be open. Ensure that the Front Doors N 1.8 100 or lower).
are closed. Ensure that the sensor is mounted correctly and is not damaged.
Check the Front Door Interlock circuit. Refer to BSD 9.4 and check the wiring to the Open Air Sensor.
If the wiring is OK, replace the Open Air Sensor (PL 8.5).
077-303 Horizontal Transport was detected to be open. N 10.1
091-940 Printed paper was longer than the IOT DC131 910-364 specified N 9.4
077-304 Swing Frame was detected to be open during printing. Ensure N 1.8
length was output after the Toner Bottle Full had been detected.
that the Swing Frame is closed.
If the Toner Bottle is full, ask the customer to replace it.
Check the Swing Frame Interlock circuit.
Ensure that the value in IOT DC131 910-364 has not changed.
077-305 Fuser Cover was detected to be open during printing. Ensure that N 1.8 Ensure that the Toner Bottle Full Sensor is not contaminated by
the Fuser Cover is closed. toner.
Check the Fuser Cover Interlock circuit.
Refer to BSD 9.4 and check the Toner Bottle Full Sensor.
077-306 Front Door was detected to be open during printing. Ensure that N 1.8 If the problem still exists, replace the Toner Bottle Full Sensor (PL
the Front Doors are closed. 6.1).
Check the Front Door Interlock circuit.
091-941 Printed paper longer than the IOT DC131 910-363 specified N 9.2
077-307 Horizontal Transport was detected to be open. Ensure that the N 10.1 length was output after Low Toner had been detected.
Horizontal Transport is closed. Ensure that the value in IOT DC131 910-363 has not changed.
077-310 The Main Drive Motor was detected to be out of sync (Lock). Y 4.1 Check the wiring to the Toner Empty Sensor.
077-900 A paper path sensor detected paper when the machine was Y If the problem still exists, replace the Toner Empty Sensor (PL
stopped. 5.2).
077-901 A paper path sensor detected paper when the machine was in N 102-390 Control Panel firmware download has failed (Parameter Error) N 2.1
the Low Power Mode. Refer to the 077-900 RAP. Check the connection between the CP Control PWB and the
Console.
077-902 A paper path sensor detected paper after a print was delivered. N
Switch the power off then on and then re-install it.
Refer to the 077-900 RAP.
If the problem still exists, replace the Console (PL 8.4).
091-300 Rear Top Cover was detected to be open. N 1.10
102-391 Control Panel firmware download has failed (Sequence Error) N 2.1
Ensure that the Rear Top Cover Sensor is mounted correctly and
Check the connection between the CP Control PWB and the
is not damaged (PL 9.3).
Console.
091-301 Rear Top Cover was detected to be open during printing. N 1.10 Switch the power off then on and then re-install it.
Ensure that the Rear Top Cover Sensor is mounted correctly and
If the problem still exists, replace the Console (PL 8.4).
is not damaged (PL 9.3).
102-392 Control Panel firmware download has failed (Flash ROM Error) N 2.1
091-310 An Open Air Sensor Humidity error was detected (IOT DC330 N 9.4 Check the connection between the CP Control PWB and the
091-250 was 700 or higher). Console.
Ensure that the sensor is mounted correctly and is not damaged.
Switch the power off then on and then re-install it.
Refer to BSD 9.4 and check the wiring to the Open Air Sensor. If the problem still exists, replace the Console (PL 8.4).
If the wiring is OK, replace the Open Air Sensor (PL 8.5).
102-395 Control Panel firmware download has failed in the diagnostic N 2.1
091-311 An Open Air Sensor Humidity error was detected (IOT DC330 N 9.4 mode (Parameter Error)
091-250 was 10 or lower).
Reinstall the firmware by USB installation.
Ensure that the sensor is mounted correctly and is not damaged. If the problem still exists, replace the Control Panel (PL 8.4)
Refer to BSD 9.4 and check the wiring to the Open Air Sensor.
If the wiring is OK, replace the Open Air Sensor (PL 8.5).

10/31/05
6
 Table 1 Status Code List
Status
Code Fault Description RAP BSD
102-396 Control Panel firmware download has failed in the diagnostic N 2.1
mode (Sequence Error)
Reinstall the firmware by USB installation.
If the problem still exists, replace the Control Panel (PL 8.4)
102-397 Control Panel firmware download has failed in the diagnostic N 2.1
mode (Flash ROM Error)
Reinstall the firmware by USB installation.
If the problem still exists, replace the Control Panel (PL 8.4)
102-610 The UI parameter was corrected to be within the range because it N 2.1
was set to an out of range value.
103-310 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued.
Reload the software.
If the fault still exists, escalate the call.
103-311 Error was detected during communication between the CP-Cont N 3.1
PWB and the IIT.
Ensure that the USB Cable is seated correctly between the IIT
PWB and the CP Control PWB and that it is not damaged.
If the cable is OK, reinstall the firmware.
If the problem still exists, replace the following in order:
• IIT PWB (PL 8.3)
• CP Control PWB (PL 8.6)
103-390 IIT firmware download failed (Boot Type Unknown) N 3.1
Ensure that the IIT is using firmware later than V0.03.02.
Ensure that he USB cable is seated correctly between the IIT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IIT PWB (PL 8.3).
103-391 IIT firmware download failed (DL Mode Reset NG) N 3.1
Ensure that he USB cable is seated correctly between the IIT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IIT PWB (PL 8.3).
103-392 IIT firmware download failed (DL Ready NG) N 3.1
Ensure that he USB cable is seated correctly between the IIT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IIT PWB (PL 8.3).
103-393 IIT firmware download failed (DL Proc NG) N 3.1
Ensure that he USB cable is seated correctly between the IIT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IIT PWB (PL 8.3).
103-394 IIT firmware download failed (Normal Mode Reset NG) N 3.1
Switch the power off then on in order to update the data success-
fully.
10/31/05
7
Table 1 Status Code List
Status
Code Fault Description RAP BSD
103-395 IIT firmware download failed (DL Proc Time Out) N 3.1
Ensure that he USB cable is seated correctly between the IIT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IIT PWB (PL 8.3).
103-710 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued.
Reload the software.
If the fault still exists, escalate the call.
116-310 A CMOS Checksum error occurred during Power On Self Test. N 3.1
NOTE: CMOS default value is loaded when CMOS checksum
error has occurred.
Switch the power off then on. check the date and time.
If the problem still exists after the above procedures, replace the
CP Control PWB. (PL8.6).
116-311 A Memory Check error occurred during Power On Self Test. N 3.1
Switch the power off. Ensure that the memory modules are
seated correctly.
NOTE: When multiple memory modules are installed, replace
them one at a time.
If the error occurs again, replace the memory. (PL 8.6)
116-312 A hard disk drive error occurred during Power On Self Test. N 16.1
Refer to BSD 16.1 and ensure that the hard drive is receiving
power.
Ensure that the IDE cable is seated correctly between the hard
drive and the CP Control PWB and that it is not damaged.
If the wiring is OK, replace the hard drive (PL 8.6).
116-313 Power On Self Test error due to BIOS (Battery Error) N 3.1
Switch the power off and remove the battery from the CP Control
PWB and check its voltage.
• If the voltage is measured to be +2.4VDC or lower, replace
the CP Control PWB. (PL8.6)
• If the voltage is measured to be higher than +2.4VDC, use a
clean cloth to wipe any contaminations from the battery
electrodes. Re-install the battery and switch the power on.
Check the date and time.
116-314 Power On Self Test error due to BIOS (CPU Fan Error) N 3.1
If the CPU fan on the CP Control PWB is dirty then clean it.
If the CPU Fan is not rotating or is rotating slowly, ensure that the
CPU fan connector is seated correctly and is not damaged.
If the problem still exists after the above procedures, replace the
CP Control PWB. (PL8.6)
 Table 1 Status Code List
Status
Code Fault Description RAP
116-315 Power On Self Test error due to BIOS (CPU Temperature Error) N 3.1
If the CPU fan on the CP Control PWB is dirty then clean it.
Check the CPU heat sink on the CP Control PWB for dirt and
abnormalities and clean it.
If the problem still exists after the above procedures, replace the
CP Control PWB. (PL8.6)
116-316 Power On Self Test error due to BIOS (System Fan Error) N 3.1
Ensure that the CP Control Exhaust Fan is rotating.
If the CP Control Exhaust Fan is dirty then clean it.
If the CP Control Exhaust Fan is not rotating or is rotating slowly,
ensure that the CP Control Exhaust Fan connector is seated cor-
rectly and is not damaged.
If no failures can be found in the connection, replace the CP Con-
trol Exhaust Fan. (PL8.6)
If the problem still exists after the above procedures, replace the
CP Control PWB. (PL8.6)
116-317 Power On Self Test error due to BIOS (PCI Resource Conflict) N 3.1
Switch the power off then on to clear the fault.
If the error occurs again, switch the power off and remove the
battery from the CP Control PWB in order to clear CMOS data.
Re-install the battery and switch the power on. Check the date
and time.
If the problem still exists after the above procedures, replace the
CP Control PWB. (PL8.6)
116-318 Power On Self Test error due to BIOS (OS not found) N 3.1
Switch the power off. Set the CP-Cont DIP switch Bit 2 (upper) for
booting from the Flash ROM to the off position. Switch the power
on.
• If the system starts up correctly, there must be an HDD data
error or failure. Perform re-installation of firmware.
• If the system does not start up correctly, replace the CP
Control PWB. (PL8.6)
Switch the power off. Set the CP-Cont DIP switch Bit 2 (upper) for
booting from the HDD to the on position. Switch the power on.
If the system does not start up correctly, replace the HDD.
(PL8.6)
116-329 Undefined Error (Boot ROM) N 3.1
Switch the power off then on.
If the problem still exists, replace the CP Control PWB (PL 8.6).
116-330 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Copy Manager)
Reload the software.
If the fault still exists, escalate the call.
Table 1 Status Code List
Status
BSD Code Fault Description RAP BSD
116-335 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (HD Long RW)
Reload the software.
If the fault still exists, escalate the call.
116-340 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Image Library)
Reload the software.
If the fault still exists, escalate the call.
116-350 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Job Manager/ Job)
Reload the software.
If the fault still exists, escalate the call.
116-351 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Job Manager/ Input)
Reload the software.
If the fault still exists, escalate the call.
116-352 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Job Manager/ Output)
Reload the software.
If the fault still exists, escalate the call.
116-353 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Job Manager/ Sort)
Reload the software.
If the fault still exists, escalate the call.
116-354 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Job Manager/ Interrupt)
Reload the software.
If the fault still exists, escalate the call.
116-355 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Job Manager/ Image)
Reload the software.
If the fault still exists, escalate the call.
116-360 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Net Scan Manager)
Reload the software.
If the fault still exists, escalate the call.
116-365 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Print Control)
Reload the software.
If the fault still exists, escalate the call.
116-370 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (Scan Control)
Reload the software.
If the fault still exists, escalate the call.
10/31/05
8
 Table 1 Status Code List Table 1 Status Code List
Status Status
Code Fault Description RAP BSD Code Fault Description RAP BSD
116-380 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 123-310 UI Panel ROM Program Area Fault N 2.2
cessing cannot be continued. (Utility Library) Reinstall the firmware by USB installation.
Reload the software. If the fault still exists, replace the Console. (PL8.4)
If the fault still exists, escalate the call. 123-311 UI Panel ROM Data Area Fault N 2.2
116-390 Failure to write to the Flash ROM on the CP Control PWB. N 3.1 Reinstall the firmware by USB installation.
Check the setting of FROM Write Dip switch (Bit 1) setting on the If the fault still exists, replace the Console. (PL8.4)
CP Control PWB. 123-314 UI Panel Communication Fault N 2.2
Switch the power off then on and then re-install. Switch the power off. Set the DIP Switch of Bit 2 (upper) on the
116-740 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 CP Control PWB (PL8.6) to off. switch the power on to boo the
cessing cannot be continued. (Image Library) Flash ROM.
Reload the software. • If the system boots correctly, reinstall the firmware. If the
If the fault still exists, escalate the call. problem still exists, replace the hard drive (PL 8.6)
116-741 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 • If the system does not boot correctly, replace the CP Control
cessing cannot be continued. (Image Library/ Font) PWB (PL8.6).
Reload the software. 123-315 UI Panel Communication Error N 2.2
If the fault still exists, escalate the call. Reload the software.
116-750 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 If the fault still exists, escalate the call.
cessing cannot be continued. (Job Manager/ Job) 123-316 UI Panel Communication Fault N 2.2
Reload the software. Reload the software.
If the fault still exists, escalate the call. If the fault still exists, escalate the call.
116-751 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 123-317 UI Panel Communication Error N 2.2
cessing cannot be continued. (Job Manager/ Input) Reload the software.
Reload the software. If the fault still exists, escalate the call.
If the fault still exists, escalate the call.
124-310 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
116-752 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 cessing cannot be continued. (IOT Interface)
cessing cannot be continued. (Job Manager/ Output) Reload the software.
Reload the software. If the fault still exists, escalate the call.
If the fault still exists, escalate the call.
124-311 Error was detected during communication between the CP-Cont N 3.1
116-765 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 PWB and the IOT PWB
cessing cannot be continued. (Print Control) Ensure that the USB Cable is seated correctly between the IOT
Reload the software. PWB and the CP Control PWB and that it is not damaged.
If the fault still exists, escalate the call. If the cable is seated correctly, reinstall firmware.
116-770 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 If the problem still exists, replace the IOT PWB (PL8.1).
cessing cannot be continued. (Scan Control) 124-320 It was detected that the three billing values are mismatched. N 3.5
Reload the software.
124-390 IOT firmware download failed (Boot Type Unknown) N 3.1
If the fault still exists, escalate the call.
Ensure that the IOT Main firmware is later than V0.05.01 and the
116-780 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1 IOT Boot firmware is later than V1.00.00.
cessing cannot be continued. (Utility Library) Ensure that he USB cable is seated correctly between the IOT
Reload the software. PWB and the CP Control PWB and that it is not damaged.
If the fault still exists, escalate the call. Switch the power off then on and then re-install it.
121-311 EP-SV Communication Fault N 3.3, 3.4 If the problem still exists, replace the IOT PWB (PL 8.1).
Ensure that the connected EPSV or DocuLyzer conforms to the
specifications.
Refer to BSD 3.3 and 3.4 and check the power to the EPSV or
DocuLyzer.
Check the EPSV or DocuLyzer control circuit.

10/31/05
9
 Table 1 Status Code List
Status
Code Fault Description RAP BSD
124-391 IOT firmware download failed (DL Mode Reset NG) N 3.1
Ensure that he USB cable is seated correctly between the IOT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IOT PWB (PL 8.1).
124-392 IOT firmware download failed (DL Ready NG) N 3.1
Ensure that he USB cable is seated correctly between the IOT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IOT PWB (PL 8.1).
124-393 IOT firmware download failed (DL Proc NG) N 3.1
Ensure that he USB cable is seated correctly between the IOT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IOT PWB (PL 8.1).
124-394 IOT firmware download failed (Normal Mode Reset NG) N 3.1
Ensure that he USB cable is seated correctly between the IOT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IOT PWB (PL 8.1).
124-395 IOT firmware download failed (DL Proc Time Out) N 3.1
Ensure that he USB cable is seated correctly between the IOT
PWB and the CP Control PWB and that it is not damaged.
Switch the power off then on and then re-install it.
If the problem still exists, replace the IOT PWB (PL 8.1).
124-610 It was detected that NVM2 billing value mismatched. (Socket N 3.5
NVM of CP Control PWB)
124-611 It was detected that NVM1 billing value mismatched. (Onboard N 3.5
NVM of CP Control PWB)
124-612 It was detected that IOT billing value mismatched. N 3.5
124-710 Conflict had occurred in SW operation of the CP-Cont and pro- N 3.1
cessing cannot be continued. (IOT Interface)
Reload the software.
If the fault still exists, escalate the call.
199-999 The machine configuration is not set. N
Enter CP-Cont diagnostic DC131. Enter the appropriate code for
the machine configuration [700-000]:
• 1 - EP (Engineering Printer)
• 2 - EC (Engineering Copier)
• 5 - MF (Multifunction)
Enter CP-Cont diagnostic DC361 to initialize the machine.

10/31/05
10