World of Fax & Copiers
Fax, Copier & Printer
Parts/Supplies Specialist
Outside or within the
U.S. (845) 624-2332
FAX ORDERS TO 845-624-2299
We Stock full line of parts for Sharp, Xerox, Canon, Brother, Hp, Toshiba, Panasonic, Ricoh
Return to main menu Canon G3 Error Codes
Canon
G3 error Codes
G3 Error Codes
##001 [ TX ]
Fail to receive phase OK signal in FAX/TEL mode.
A.
Cause: Other party cannot properly receive phase signal due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive the
phase signal properly.
Solution: Adjust the NL equalizer so the other party can receive the
phase signal properly.
##002 [ RX ]
Picture memory full upon G2 reception.
A.
Cause: Defective buffer memory.
Solution: Replace the SCNT PWB.
##003 [ TX ]
Failed MCF2/ PIS reception during G2 transmission.
A.
Cause: Other party cannot properly receive signals due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive
MCF2 or PIS.
Solution: Adjust the NL equalizer so the other party can receive MCF2 or
PIS signals properly.
##004 [ RX ]
Fail EOM/ PIS reception during G2 reception.
A.
Cause: Picture signal cannot be received over 1 second due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive EOM
or PIS signal properly.
Solution: Adjust the NL equalizer so the other party can receive EOM or
PIS signal properly.
##005 [ TX ]
Failed G12 reception during G2 transmission.
A.
Cause: Other party cannot properly receive the G12 signals due to poor
line conditions.
Solution: Have the other party boost their transmission level so they can
properly receive G12 signal.
B.
Cause: Other party confused by echo and does not send G12.
Solution: Have the other party lower their transmission level so they
will not receive echo signals.
##006 [ RX ]
Failed phase synchronization from second sheet during G2 reception.
A.
Cause: Other party cannot properly receive phase signal due to poor line
conditions.
Solution: Have the other party boost their transmission level to allow
for proper phase signal reception.
Solution: Adjust the NL equalizer so the other party can receive the
phase signal properly.
##007 [ TX ]
Failed CFR2 reception during G2 transmission.
A.
Cause: The other party cannot receive CFR2 due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
CFR2 properly.
Solution: Adjust the NL equalizer so the other party can receive CFR2
signal properly.
B.
Cause: The other machine is out of paper.
Solution: Have the other party refill their machine with recording paper.
##008 [ RX ]
Fail to receive GC2, PIS and Phase signals for 35 seconds and receive
other signals during G2 reception.
A.
Cause: The other party cannot receive the signals immediately before GC2,
PIS or the Phase signals properly due to poor line conditions.
Solution: Boost the transmission level so that the other party can
receive the signals immediately before GC2, PIS or the Phase signals.
Solution: Adjust the NL equalizer so the other party can receive the
signals immediately before GC2, PIS or the Phase signals.
B.
Cause: Cannot receive GC2, PIS or Phase signals from the other party
properly due to poor line conditions.
Solution: Have the other party boost the transmission level so they can
receive the signals immediately before GC2, PIS or the Phase signals.
##009 [ TX / RX ]
Failed to detect last tonal signal from the other party.
A.
Cause: Line noise.
Solution: Contact the telephone company and request line maintenance.
##010 [ RX ]
Failed Phase synchronization on first sheet during reception in G2 or
MF1.
A.
Cause: Cannot receive the Phase signal from the other party properly due
to poor line conditions.
Solution: Have the other party boost the transmission level so they can
receive the Phase signals properly.
Solution: Adjust NL equalizer so the other party can receive the Phase
signals properly.
##011 [ RX ]
Fail to receive picture signals for 5 seconds after CFR2 transmission
upon G2 reception.
A.
Cause: Cannot receive the picture signals from the other party properly
due to poor line conditions.
Solution: Have the other
party boost the transmission level for proper reception of the picture signals.
Solution: Adjust the NL equalizer to receive the picture signals
properly.
##012 [ RX ]
Receive signals other than PIS and GC2 after detecting MCF2 or GI2 when
EOM is received during G2 reception.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tapes and then request the Local
Canon office and/or Technical
Center to analyze the information.
##013 [ TX ]
Receive PIS during picture signal transmission in G2 mode.
A.
Cause: The other machine is out of paper.
Solution: Contact the other party and have them resupply recording paper.
##050 [ RX ]
Thermal Head Thermistor detects abnormality.
A.
Cause: Thermal head trouble.
Solution: Replace the Thermal head.
B.
Cause: SCNT PWB trouble.
Solution: Refer to specific
trouble shooting procedures in Service Manual.
##051 [TX / RX]
Stepping Motor trouble.
A.
Cause: Gear unit trouble.
Solution: Replace gear unit.
B.
Cause: Cutter trouble.
Solution: Replace cutter.
C.
Cause: SCNT PWB trouble.
Solution: Refer to specific
trouble shooting procedures in Service Manual.
##052 [TX / RX)
Backup Memory damaged.
A.
Cause: Affected by noise.
Solution: Print out all the data, clear the memory and then re-register
data.
B.
Cause: Backup battery trouble.
Solution: Replace the backup battery.
C.
Cause: SCNT PWB trouble.
Solution: Refer to specific
trouble shooting procedures in Service Manual.
##053 [ TX/RX ]
Thermal Head or Thermistor of the motor detects abnormality.
A.
Cause: Performed continuous copy, transmission for a prolonged period of
time.
Solution: Turn OFF the power and let machine cool for a while.
B.
Cause: Thermal head trouble.
Solution: Replace the thermal head.
C.
Cause: Motor trouble.
Solution: Replace the motor.
D.
Cause: Thermistor trouble.
Solution: Replace the Thermistor Assy.
##054 [ TX / RX ]
Image Memory backup error.
A.
Cause: Image memory backup secondary battery is dead.
Solution: Leave powered ON
for 5 days, battery will recharge, but data has been cleared.
Solution: Replace the backup secondary battery.
B.
Cause: DRAM failure.
Solution: Replace the SCNT PWB.
##100 [ TX ]
Excessive repeat protocol during transmission.
A.
Cause: (Q signal transmission after picture signals); The other party
cannot receive picture or Q signals properly due to poor line conditions.
Solution: Boost the transmission level so that the other party can
receive picture or Q signals properly.
Solution: Lower the
transmission start speed to 4800 bps.
Solution: Adjust the NL equalizer so the other party can receive picture
or Q signals properly.
Solution: Add an EPT on the V29 modem signals.
Solution: Adjust the continuous transmission time of 1 before
transmitting the picture signal so the other party can receive picture signals
properly.
Solution: Lengthen the no-sound time after receiving CFR so the other
party can receive picture signals properly.
B.
Cause: (After TCF transmission before picture signals); The other party
cannot properly receive due to low transmission level.
Solution: Boost the transmission level so the other party can properly
receive the signals
C.
Cause: (After TCF
transmission before picture signals); The other party experience echo
malfunction.
Solution: Take echo counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
##101 [ TX / RX ]
Modem speed different from other party.
A.
Cause: (TX / RX) The modem transmission speed is different from other
machine.
Solution: No solution as modem speed is dependant on each machines
specifications.
B.
Cause: (TX) The fall back speed is not the same as in the other machine.
Solution: Boost the transmission level so the other party can receive TCF
properly.
Solution: Adjust the NL equalizer so the other party can receive TCF
properly
Solution: Take echo
counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the reception level to prevent the
other party from receiving echo signals.
##102 [ TX ]
Fall back failure during transmission.
A.
Cause: TCF is not transmitted properly due to poor line conditions.
Solution: Boost the transmission level so the other party can properly
receive TCF.
Solution: Adjust the NL equalizer so that the other party can properly
receive TCF.
B.
Cause: Other party experienced echo malfunction.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the reception level to prevent the
other party from receiving echo signals.
##103 [ RX ]
Fail to detect EOL for 5 seconds (15 seconds for CBT) during reception.
A.
Cause: Cannot receive picture signals properly due to poor connection.
Solution: Boost the transmission level so the other party can receive the
picture signals properly.
Solution: Have the other party lower their transmission speed to 4800
bps.
Solution: Adjust the NL equalizer so the picture signals can be received
properly.
Solution: Adjust the echo monitor time after CFR transmission so picture
signals can be received properly.
B.
Cause: Malfunction due to CFR echo.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Lower the
transmission level so the echo of the CFR transmission is not received.
##104 [ TX ]
RTN or PIN received during transmission.
A.
Cause: The other party cannot
receive picture signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
picture signals properly.
Solution: Lower the transmission start speed to 4800 bps.
Solution: Adjust the NL equalizer so the other party can receive picture
signals properly.
Solution: Add an EPT on the V29 modem signals.
Solution: Have the other party relax their RTN transmission conditions so
they will not transmit RTN.
B.
Cause: The other party
experienced echo malfunction.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the reception level to prevent the
other party from receiving echo signals.
##105 [ RX ]
Over 40 continuous lines of data error during reception.
A.
Cause: Cannot receive picture signal properly due to poor line
conditions.
Solution: Have the other party boost the transmission level for proper
reception of the picture signal.
Solution: Have the other party lower their transmission start speed to
4800 bps
Solution: Adjust the NL equalizer so that the picture signal can properly
be received.
##106 [ RX ]
Fail to receive protocol for 6 seconds when waiting for protocol during
reception.
A.
Cause: Cannot receive protocol properly from the other party due to poor
line conditions.
Solution: Have the other party boost the transmission level so this
machine can receive the protocol signals properly.
B.
Cause: The other party cannot receive the signals properly due to poor
line conditions.
Solution: Boost the transmission level so that the other party can
receive the signals.
C.
Cause: Malfunction due to echo.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Lower the transmission level to prevent the reception of echo
signals.
##107 [ RX ]
Fall back failure on TX side during reception.
A.
Cause: Cannot receive the other party's signal properly after receiving
at 2400 bps due to poor line conditions.
Solution: Have the other party boost the transmission level so this
machine can receive the signals properly.
Solution: Adjust the NL equalizer so signals from
the other party can be received properly.
Solution: Relax the TCF assessment standards to prevent FTT transmission.
Solution: Relax the RTN transmission conditions to prevent RTN
transmission.
B.
Cause: Malfunction due to echo.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Lower the transmission level to prevent the reception of echo
signals.
##108 [ TX ]
Detect polarity inversion during TX in f-networks 2.
A.
Cause: Attempted to send more than 32 documents at one time.
Solution: Divide the job so that less than 31 document are sent at one
time.
B.
Cause: The length of 1 document is longer than 2 A4 size sheets.
Solution: Divide the document so that it is smaller than 2 A4 size
sheets.
C.
Cause: The other party released the line during transmission.
Solution: Retransmit.
D.
Cause: STOC detected an abnormality
Solution: Call NTT notifying them of the trouble
E.
Cause: Presence of tariff pulse.
##109 [ TX ]
Receive signals other than DIS, DTC, FTT, CFR or CRP after DCS
transmission and exceeded the number of protocol retransmission during
transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##110 [ TX ]
Detect PIS during picture transmission.
A.
Cause: The other party's line was released.
Solution: Retransmit.
##111 [ TX / RX ]
Memory error.
A.
Cause: Noise causes data
error when printing the data in the image memory.
Solution: Print the entire data, clear the memory and then re-register
the data.
B.
Cause: Noise causes erroneous dialing (the print/ display pointer of the
telephone number and the pointer of the calling side does not match).
Solution: Replace SCNT.
##112 [ TX ]
Receive DIS three times during transmission.
A.
Cause: The other party cannot receive the signals properly due to low
transmission level.
Solution: Boost the transmission level so the other party can receive the
signals properly.
B.
Cause: Malfunction caused by echo
Solution: Take echo
counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the reception level to prevent the
other party from receiving echo signals.
##113 [ TX ]
Receive signals other than MFC, RTP, RTN, PIP or PIN after q or PRI-q in
TX.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##114 [ RX ]
RTN was transmitted during reception.
A.
Cause: Cannot receive picture signals properly from the other party due
to poor line conditions.
Solution: Have the other party boost the transmission level to receive
the picture signals properly.
Solution: Have the other party lower the transmission start speed to 4800
bps.
Solution: Adjust the NL equalizer so picture signals can properly be
received.
Solution: Relax the RTN transmission conditions to prevent RTN
transmission.
B.
Cause: Malfunction due to CFR echo.
Solution: Perform echo counter-measures as listed in Service manual.
Solution: Lower the transmission level to prevent echo reception of
transmitted CFR.
##115 [ TX ]
Exceeded the one-line maximum transmission time (5 seconds) during
picture transmission.
A.
Cause: Volume of encoded data very large, due to too many fine lines in
document.
Solution: Make a copy of the document with a copier and then retransmit.
Solution: Transmit without setting the halftone or AA mode.
##116 [TX / RX]
Detect loop current disconnection during communication [Swiss
specifications].
A.
Cause: The other party released the line
Solution: Retransmit
B.
Cause: Exchanger
malfunction.
Cause: Insufficient loop current.
Solution: Contact the telephone company.
##117 [ RX ]
Receive DCN after DIS transmission from the second sheet.
A.
Cause: Other party cannot receive DIS signal properly due to poor line
conditions.
Solution: Boost the transmission level so that the other party can
receive DIS properly.
B.
Cause: Other party pressed the Stop key.
Solution: Have the other party retransmit
##118 [ RX ]
T1 timer over after reception of second sheet.
A.
Cause: The other party cannot receive signals properly due to poor line
conditions.
Solution: Boost the transmission level so that the other party can
receive the signals properly.
B.
Cause: Cannot receive signals from the other party properly due to poor
line conditions.
Solution: Have the other party boost their transmission level.
##120 [ TX ]
Mechanical abnormality in the document transport unit.
A.
Communication was interrupted as a preventative measure since there was a
mechanical abnormality in the document transport unit.
Solution: Check each part of the document transport unit for any
abnormalities using the Service manual.
##121 [ RX ]
Ink sheet and Recording paper cling together.
A.
Cause: Too much power applied to the Thermal head.
Solution: Lower the resistance rank of the Thermal head (printing will be
lighter).
##122 [ TX ]
Other party does not have ITU-T recommended TX function.
A.
Cause: The other party's DIS
bit 33 is ON and there is no transmission function displayed in bits 34 thru 37.
Solution: Transmit to a FAX whose bits 33 and over are not covered by
recommendations.
Solution: Transmit to a FAX whose bits 33 and over are not defined.
##200 [ RX ]
Fail to detect picture reception carrier for 5 seconds during reception.
A.
Cause: Cannot receive picture signals properly due to poor line
conditions.
Solution: Have the other party boost the transmission level so picture
signals can be received properly.
Solution: Have the other party lower the transmission start speed to 4800
bps.
B.
CFR echo inhibits training signal reception, resulting in time over.
Solution: Perform echo counter-measures in accordance with the Service
Manual.
Solution: Lower the transmission level so the echo of the CFR is not
received.
##201 [TX / RX]
DCN reception other than normal binary protocol.
A.
Cause: Other party's machine is out of paper.
Solution: Have other party replenish recording paper supply.
B.
Cause: The user telephone number is not registered (if the receiver is a
Ricoh 3000L)
Solution: Register
user telephone number.
C.
Cause: No response to bell tone after talk reservation.
Solution: Contact by phone.
D.
Cause: Wrong password during polling reception.
Solution: If the other party is using a Canon model then contact them and
have them match the passwords.
Solution: If the other party is not a Canon model then contact them and
have them set all passwords to [1].
E.
Cause: Document is not set
upon polling transmission.
Solution: Set the document and have the other party call again
F.
Cause: Transmission was reserved from the other party, however, your
machine was out of paper.
Solution: Replenish recording paper.
G.
Cause: The other party cannot receive protocol properly due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive the
protocol properly.
H.
Cause: Malfunction caused by echo.
Solution: Perform echo counter-measures in accordance with the Service
manual.
Solution: Lower the transmission level to prevent echo reception.
##202 [TX / RX]
Fail to detect the last binary signal from the other party.
A.
Cause: Line noise.
Solution: Contact the telephone company and request maintenance.
##203 [TX / RX]
Operational error due to causes other than codes #003 thru #008
A.
Cause: The machine was switching between transmission and reception.
Cause: The machine was out of recording paper.
Cause: The document was not set during polling.
Solution: Set the document or replenish recording
paper.
##204 [ TX ]
Receive DTC without transmission data in direct TX, CEP 2; receive DIS
after image transmission without transmission data
A.
Cause: (DTC received) abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
B.
Cause: (DIS received) in CEP 2 transmission, the actual condition of the
other party is different from that registered with the sending FAX.
Solution: Resend
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##205 [ TX ] Data error during image memory
storage.
A.
Cause: Trouble with image storage memory
Solution: Replace the circuit PWB (SCNT, etc.) Mounted for
transmission memory
##220 [ TX / RX ]
System error (main program runaway).
A.
Cause: CPU malfunctioned due to noise.
Solution: Turn the power OFF and then back ON.
##221 [ TX ]
Actual-size recording crystal breakdown.
A.
Cause: Trouble with crystal for actual-size recording.
Solution: Replace the crystal attached unit for actual-size recording.
Solution: Replace SCNT.
##222 [ RX ]
90% compression recording crystal breakdown.
A.
Cause: Trouble with crystal for 90% compression recording.
Solution: Replace the crystal attached unit for 90% compression
recording.
Solution: Replace the SCNT PWB.
##223 [ TX ]
Line disconnected during communication.
A.
Cause: Stop key was pressed during picture signal transmission.
Solution: Retransmit.
##224 [ TX / RX ]
Abnormal protocol during G3 communication
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##226 [ TX / RX ]
Stack pointer not within RAM range.
A.
Cause: CPU malfunctioning due to noise.
Solution: Turn the power OFF and then back ON
##227 [ RX ]
Attempt to record file without picture data.
A.
Cause: Unknown
Solution: This is an error code to test for memory trouble for the L770
series. There are no measures
possible since there are no results concerning this trouble.
##228 [ RX ]
Abnormal picture control information.
A.
Cause: Unknown
Solution: This is an error code to test for memory trouble for the L770
series. There are no measures
possible since there are no results concerning this trouble.
##229 [ RX ]
Recording unit locked for 1 minute.
A.
Cause: Unknown
Solution: Cancel the lock, press the Start button and print the picture
data.
Solution: Replace the ROM (U.K. only).
##230 [ TX / RX ]
Display control unit malfunction.
A.
Cause: The UPI to control the display did not function properly
Solution: Replace the display control unit (display unit, etc.).
##231 [ TX / RX ]
Button control unit malfunction.
A.
Cause: The UPI to control
the button did not function properly.
Solution: Replace the button control unit (operation unit, etc.).
##232 [ TX ]
ENCODE control unit malfunction.
A.
Cause: The UPI to control the ENCODE did not function properly.
Solution: Replace the ENCODE control unit (SCNT PWB, etc.).
##233 [ TX ]
CCD control unit malfunction.
A.
Cause: The operation of the UPI to control CCD did not finish properly.
Solution: Replace the CCD control unit (Video 2 unit, etc.).
##234 [ TX ]
READ control unit malfunction.
A.
Cause: The operation of the UPI to control READ operations did not finish
properly.
Solution: Replace the READ
control unit (Video 2 unit, etc.).
##235 [ TX / RX ]
G2 modem control unit malfunction.
A.
Cause: The operation of the UPI to control the G2 modem did not finish
properly.
Solution: Replace the G2 modem control unit
(MOD2 unit, etc.).
##236 [ TX / RX ]
G3 modem control unit malfunction.
A.
Cause: The operation of the UPI to control the G3 modem did not finish
properly.
Solution: Replace the G3 modem control unit (MOD2 unit, etc.).
##237 [ RX ]
DECODE control UPI malfunction.
A.
Cause: The operation of the UPI to control the DECODE operations did not
finish properly.
Solution: Replace the DECODE control unit (PRINT, etc.).
##238 [ RX ]
PRINT control unit malfunction.
A.
Cause: The operation of the UPI to control the PRINT operations did not
finish properly.
Solution: Replace the PRINT control unit (SCNT PWB, etc.).
##239 [ TX / RX ]
TONAL control unit malfunction.
A.
Cause: The operation of the UPI to control the TONAL operations did not
finish properly.
Solution: Replace the TONAL control unit (MOD2 unit, etc.).
##244 [ TX / RX ]
OPT2 control unit malfunction.
A.
Cause: The operation of the UPI to control the OPT2 did not finish
properly.
Solution: Replace the OPT2 control unit (OPT2 unit, etc.).
##260 [ TX / RX ]
System error between modem and SCNT.
A.
Cause: Defective internal unit; (CS will not set 0 when RS is set to 0).
Solution: Replace the modem or modem attached circuit board.
Solution: Replace the SCNT PWB
##261 [ TX / RX ]
System error between modem and SCNT.
A.
Cause: Defective internal unit; (CS will not set to 1 when RS is set to
0).
Solution: Replace the modem or modem attached circuit board.
Solution: Replace the SCNT PWB
##262 [ TX ]
CFR detection filter output cannot be turned off during MF1 transmission.
A.
Cause: Defective internal unit.
Solution: Replace NCU PWB
##263 [ TX / RX ]
Fail to respond for 20 seconds after detecting preamble.
A.
Cause: Continuous line noise
Solution: Have the other party boost their transmission level so signals
can be received
B.
Cause: The other party's preamble is too long
Solution: Have the other party set their preamble length to 1 second.
C.
Cause: Defective internal unit.
Solution: Replace SCNT PWB
Solution: Replace the modem or modem attached circuit board.
Solution: Replace NCU board.
##264 [ RX ]
Fail to receive picture signals within 10 seconds after entering picture
reception status.
A.
Cause: Cannot receive picture signals properly due to poor line
conditions.
Solution: Have the other party lower their transmission start speed to
4800 bps.
Solution: Adjust the NL equalizer to properly receive the signals.
Solution: Have the other party boost the transmission level to receive
picture signals properly.
B.
Cause: Malfunction due to CRF echo.
Solution: Perform echo counter-measures listed in Service manual.
Solution: Lower the
transmission level to prevent reception of the transmitted CRF echo.
##265 [ TX / RX ]
SCNT hardware signal error.
A.
Cause: Defective internal unit; (the correct modem speed is not
selected).
Solution: Replace the modem or modem attached circuit board.
Solution: Replace the SCNT PWB.
##266 [ TX / RX ]
Internal signal error.
A.
Cause: Defective internal unit; (byte pack interrupt was not generated).
Solution: Replace the modem or modem attached circuit board.
Solution: Replace the SCNT PWB.
##267 [ TX / RX ]
Internal memory error.
A.
Cause: Defective internal unit; (EEPROM write error).
Solution: Replace SCNT PWB
Solution: Replace the modem or modem attached circuit board.
##271 [ RX ]
Detected 1650 Hz binary signal after CFR transmission however, failed to
receive binary signal within 10 seconds.
A.
Cause: Defective internal unit; (byte pack interrupt was not generated).
Solution: Replace SCNT PWB
Solution: Replace the modem or modem attached circuit board.
##280 [ TX ]
Excessive repeat protocol command during transmission.
A.
Cause: The other party cannot receive properly after TCF due to low
transmission level.
Solution: Boost the transmission level so signals can be properly
received by the other party.
B.
Cause: The other party experienced echo malfunction.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Press Start button after confirming the first
DIS from the other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower its transmission level to prevent
the other party from receiving echo signals.
##281 [ TX ]
Excessive repeat protocol command during transmission.
A.
Cause: Proper signal was not received after EOP transmission since the
picture signal or EOP was not transmitted properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
picture or EOP signals properly.
Solution: Lower the transmission start speed to 4800 bps.
Solution: Adjust the NL equalizer so the other party can receive picture
or EOP signals properly.
Solution: Add an EPT to the V29 modem signals
Solution: Adjust the continuous transmission time of 1 before
transmitting the picture signal so the other party can receive picture signals
properly.
Solution: Lengthen the no-sound time after receiving CFR so the other
party can receive picture signals properly.
##282 [ TX ]
Excessive repeat protocol during transmission.
A.
Cause: Proper signal was not received after EOM transmission since the
picture signal or EOM was not transmitted properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
picture or EOM signals properly.
Solution: Lower the transmission start speed to 4800 bps.
Solution: Adjust the NL equalizer so the other party can receive picture
or EOM signals properly.
Solution: Add an EPT to the V29 modem signals
Solution: Adjust the continuous transmission time of 1 before
transmitting the picture signal so the other party can receive picture signals
properly.
Solution: Lengthen the no-sound time after receiving CFR so the other
party can receive picture signals properly.
##283 [ TX ]
Excessive repeat protocol during transmission.
A.
Cause: Proper signal was not received after MPS transmission since the
picture signal or MPS was not transmitted properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
picture or MPS signals properly.
Solution: Lower the transmission start speed to 4800 bps.
Solution: Adjust the NL equalizer so the other party can receive picture
or MPS signals properly.
Solution: Add an EPT to the V29 modem signals
Solution: Adjust the continuous transmission time of 1 before
transmitting the picture signal so the other party can receive picture signals
properly.
Solution: Lengthen the no-sound time after receiving CFR so the other
party can receive picture signals properly.
##284 [ TX ]
DCN reception after TCF transmission.
A.
Cause: The other party cannot receive; (out of paper or the document is
not set).
Solution: Have the other party set their machine to allow for reception;
(replenish paper, set document).
B.
Cause: The user telephone number is not registered; (if receiver is Ricoh
3000L).
Solution: Register the telephone number.
C.
Cause: The other party cannot receive.
Solution: Boost the transmission level so that the other party can
receive the signals properly.
D.
Cause: The other party experienced an echo malfunction.
Solution: Take echo
counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower its transmission
level to prevent the other party from receiving echo signals.
E.
Cause: Indicated relay command to other party, but the other party was in
the middle of relay broadcasting.
Solution: Retransmit at a later time.
##285 [ TX ]
DCN reception after EOP transmission.
A.
Cause: Stop button was pressed during communication
Solution: Retransmit
##286 [ TX ]
DCN reception after EOM transmission.
A.
Cause: Stop button was pressed during communication
Solution: Retransmit
##287 [ TX ]
DCN reception after MPS transmission.
A.
Cause: Stop button was pressed during communication
Solution: Retransmit
##288 [ TX ]
Receive signals other than PIN, PIP, MCF, RTP or RTH after EOP
transmission
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##289 [ TX ]
Receive signals other than PIN, PIP, MCF, RTP or RTH after EOM
transmission
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##290 [ TX ]
Receive signals other than PIN, PIP, MCF, RTP or RTH after MPS
transmission
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##291 [ TX ]
Receive non-DTC signal in DTC stand-by after the second DTC
reception
during polling transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##292 [ RX ]
Fail to detect EOL at the start of the picture signal for 5 seconds after
CFR transmission during RX.
A.
Cause: Proper EOL signal at the start of the picture signal was not
received due to poor line conditions.
Solution: Have the other party lower the transmission start speed to 4800
bps.
Solution: Boost the transmission level so that the other party can
receive picture or EOL signals properly.
Solution: Adjust the NL equalizer so that the other party can receive the
picture or EOL signals properly.
B.
Cause: CFR echo malfunction.
Solution: Perform echo counter-measures listed in service manual
Solution: Lower the transmission level to prevent echo reception of the
transmitted CFR signal.
##293 [ RX ]
Fail to detect carrier at the start of the picture signal for 6 seconds
after CFR transmission during RX.
A.
Cause: Proper carrier signal at the start of the picture signal was not
received due to poor line conditions.
Solution: Have the other party lower the transmission start speed to 4800
bps.
Solution: Boost the transmission level so that the other party can
receive carrier signals properly.
Solution: Adjust the NL equalizer so that the other party can receive the
picture or EOL signals properly.
B.
Cause: CFR echo malfunction.
Solution: Perform echo counter-measures listed in service manual
Solution: Lower the transmission level to prevent echo reception of the
transmitted CFR signal.
##294 [ RX ]
Fail to receive protocol for 6 seconds after RTN or PIN transmission
during reception.
A.
Cause: The other party cannot receive RTN or PIN due to poor line
conditions
Solution: Boost transmission level so other party can receive RTN or PIN
properly.
B.
Cause: Cannot receive protocols from the other party due to poor line
conditions.
Solution: Have the other party boost the transmission level to receive
protocol properly.
##300 [ TX ]
Interface error between reader and controller.
A.
Cause: Defective internal unit; (the wait signal will not go off for 8
seconds when waiting to respond to the reader after the fluorescent light goes
on).
Solution: Refer to Service Manual.
##301 [ TX ]
Interface error between reader and controller.
A.
Cause: Defective internal unit; (the wait signal will not go off for 3
seconds when waiting to respond to the reader after pre-scanning the document
length).
Solution: Refer to Service Manual.
##302 [ TX ]
Interface error between reader and controller.
A.
Cause: Defective internal unit; (+24 volts down).
Solution: Refer to Service Manual.
##303 [ TX / RX ]
Page memory error.
A.
Cause: Defective internal unit; (fail to detect RP END signal).
Solution: Refer to Service Manual.
##304 [ RX ]
Fail memory copy failure.
A.
Cause: Defective internal unit; (RECORD will not go on during memory
copy).
Solution: Refer to Service Manual.
##305 [ TX ]
System error between modem and MCPU.
A.
Cause: Defective internal unit; (CS of high speed modem will not go on).
Solution: Refer to Service Manual.
##306 [ TX ]
System error between modem and MCPU.
A.
Cause: Defective internal unit; (CS of high speed modem will not turn
off).
Solution: Refer to Service Manual.
##307 [ TX / RX ]
Bad communication mode.
A.
Cause: CPU malfunction due to noise.
Solution: Power cycle the machine.
##308 [ TX / RX ]
1 frame time over during HDLC transmission.
A.
Cause: CPU malfunction due to noise.
Solution: Power cycle the machine.
##309 [ TX / RX ]
Command error between SCPU and MCPU.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##310 [ RX ]
CD (carrier detect) fails to go on during training check.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##311 [ RX ]
Control error.
A.
Cause: Defective internal unit; (RTC does not go on after RCVEND
reception during T$ decoder).
Solution: Refer to Service manual
##312 [ RX ]
Control error.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##320 [ RX ]
Printer (LBP) ready error.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##321 [ RX ]
Printer (LBP) status error.
A.
Cause: Defective internal unit; (returning status signal is abnormal).
Solution: Refer to Service manual
##322 [ RX ]
Printer (LBP) Fixing unit trouble.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##323 [ RX I
Printer (LBP) BD (beam detect) trouble.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##324 [ RX ]
Printer (LBP) Scanner trouble.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##325 [ RX ]
Printer (LBP) Main motor trouble.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##326 [ RX ]
Printer (LBP) Trouble.
A.
Cause: Defective internal unit; (LBP VSREQ does not go on).
Solution: Refer to Service manual
##327 [ RX ]
Printer (LBP) Trouble.
A.
Cause: Defective internal unit; (LBP VSREQ does not go off).
Solution: Refer to Service manual
##328 [ RX ]
Printer (LBP) Trouble.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##329 [ RX ]
Abnormal detection by Thermistor of
Thermal head.
A.
Cause: Thermal head trouble
Solution: Replace the Thermal head
B.
Cause: SCNT PWB
Solution: Trouble-shoot according to Service manual.
C.
Cause: Power unit trouble
Solution: Replace power unit
##330 [ TX / RX ]
Power supply unit ACVIN signal abnormality.
A.
Cause: Defective internal unit.
Solution: Refer to Service manual
##331 [ TX / RX ]
The remaining amount of Ink in the BJ cartridge cannot be detected.
A.
Cause: The ink sensor is defective.
Solution: Replace the ink sensor and re-register the ink level
##332 [ TX / RX ]
Printer control DRAM check error.
A.
Cause: Printer control DRAM malfunction
Solution: Power cycle the machine.
Solution: Replace the board containing a printer control DRAM
B.
Cause: SCNT PWB malfunction.
Solution: Power cycle the machine.
Solution: Replace the SCNT PWB.
##333 [ TX / RX ]
Printer control ROM check error.
A.
Cause: Printer control ROM malfunction
Solution: Power cycle the machine.
Solution: Replace the board containing a printer control ROM
B.
Cause: SCNT PWB malfunction.
Solution: Power cycle the machine.
Solution: Replace the SCNT PWB.
##334 [ TX / RX ]
Printer control EEPROM check error.
A.
Cause: Printer control EEPROM is damaged.
Solution: Power cycle the machine.
Solution: EEPROM data are automatically initialized when this error
occurs. Check the ink capacity of
the ink suction unit waste ink tank, and input the waste ink capacity value
corresponding to the amount of absorbed ink.
B.
Cause: Printer control EEPROM malfunction
Cause: SCNT PWB malfunction
Solution: Power cycle the machine
Solution: Replace the SCNT PWB
##335 [ TX / RX ]
Data communication error between system Control section and Printer
control section.
A.
Cause: Defective internal unit
Solution: Refer to Service manual
##336 [ TX / RX ]
BJ head temperature malfunction.
A.
Cause: BJ Cartridge (BJ head) malfunction.
Solution: Turn off the power and unplug the unit.
Let the machine sit for awhile so BJ head can cool down and retry.
Solution: Replace the BJ cartridge.
##337 [ RX ]
BJ head temperature sensor error.
A.
Cause: BJ cartridge (BJ head) malfunction.
Solution: Replace the BJ cartridge
B.
Cause: The BJ controller in the BJ printer control unit is defective
Solution: Turn off the power and unplug the unit.
Let the machine sit for awhile so BJ head can cool down and retry.
Solution: Replace the PC board containing the BJ controller.
C.
Cause: SCNT PWB malfunction.
Solution: Turn off the power and unplug the unit.
Let the machine sit for awhile so BJ head can cool down and retry.
Solution: Replace the SCNT PWB.
##338 [ RX ]
Printing position correction failed.
A.
Cause: Carriage movement prevented by one of the following: damaged
shaft, deformed parts, insufficient grease, dirty sliding part of the pressure
plate, or foreign material in the carriage.
Solution: Replace shaft, replace deformed parts, apply more grease, clean
sliding part of the pressure plate or remove the foreign material in the
carriage.
B.
Cause: Bi-directional print displacement correction failed because the
carriage motor is out of step, or some similar reason
Solution: Replace the trailer unit and carriage unit.
##339 [ RX ]
BJ head voltage malfunction error.
A.
Cause: BJ Cartridge (BJ
head) malfunction
Solution: Power cycle the machine (unplug unit).
Solution: Replace BJ cartridge
B.
Cause: The BJ controller in the BJ printer control unit is faulty.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the board containing the BJ controller
C.
Cause: SCNT PWB malfunction.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the SCNT PWB
##340 [ TX / RX ]
Home position error.
A.
Cause: Foreign body in carriage section.
Solution: Open printer body and remove foreign body.
B.
Cause: Loose carriage belt
Solution: Replace carriage belt.
C.
Cause: Carriage motor does not work.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the carriage motor
Solution: Replace the board containing the motor driver IC.
D.
Cause: Carriage position cannot be detected (Home Position sensor
breakdown or BJ).
Solution: Power cycle the machine (unplug unit).
Solution: Replace carriage cable with one that has a home position sensor
attached.
E.
Cause: Carriage position cannot be detected due to a defective gate array
for the BJ controller.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the board containing the BJ controller.
F.
Cause: SCNT PWB malfunction.
Solution: Replace the SCNT PWB
##341 [ TX / RX ]
Maintenance jet waste ink tank full.
A.
Cause: The absorption pad for the maintenance jet is full of waste ink.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the maintenance jet absorption pad.
Reset the maintenance jet absorption pad capacity to 0, in the service
mode. Note: if the capacity of the
absorption pad is unclear, register a value corresponding to the quantity of
absorbed ink in pad
Solution: Replace the PCNT PWB, and
register a value for the absorption capacity, according to the quantity
of absorbed ink in pad.
Solution: Replace the SCNT PWB, and register a value for the absorption
capacity, according to the quantity of absorbed ink in pad.
##342 [ TX / RX ]
Cleaning absorption waste ink pad full.
A.
Cause: The waste ink pad of the cleaning absorption is full.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the cleaning absorption waste ink pad.
Reset the Cleaning absorption pad capacity to 0, in the service mode.
Note: if the capacity of the absorption pad is unclear, register a value
corresponding to the quantity of absorbed ink in pad
Solution: Replace the PCNT PWB, and
register a value for the absorption capacity, according to the quantity
of absorbed ink in pad.
Solution: Replace the SCNT PWB, and register a value for the absorption
capacity, according to the quantity of absorbed ink in pad.
##343 [ TX / RX ]
Ink detection waste ink tank full.
A.
Cause: The ink detection waste ink tank is full.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the ink detection waste ink pad.
Reset the ink detection waste ink pad capacity to 0, in the service mode.
Note: if the capacity of the absorption pad is unclear, register a value
corresponding to the quantity of absorbed ink in pad
Solution: Replace the PCNT PWB, and
register a value for the absorption capacity, according to the quantity
of absorbed ink in pad.
Solution: Replace the SCNT PWB, and register a value for the absorption
capacity, according to the quantity of absorbed ink in pad.
##344 [ TX / RX ]
BJ cartridge disconnection error.
A.
Cause: BJ cartridge installed incorrectly
Solution: Reinstall the BJ cartridge.
Solution: Install another BJ cartridge.
B.
Cause: BJ cartridge installation surface is defective.
Cause: Carriage installation surface is defective.
Solution: Clean the contact surface between the BJ cartridge and carriage
with a soft clean cloth.
Solution: Replace the carriage cable.
Solution: Replace the unit including the carriage cable.
Solution: Replace the board containing the BJ controller.
##345 [ TX / RX ]
BJ cartridge head cleaning error.
A.
Cause: When the power is turned on after or when the BJ cartridge is
installed, there is a foreign material in the carriage unit.
Solution: Remove the foreign material in the carriage unit.
B.
Cause: The actuator malfunctions during cleaning.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the purge unit.
##346 [ TX / RX ]
Inside temperature error.
A.
Cause: Abnormal inside temperature rise.
Solution: Power off and unplug the unit and wait awhile for machine to
cool down.
Solution: Replace the SCNT PWB
B.
Cause: The Thermistor is defective.
Solution: Replace the Thermistor.
Solution: Replace the board containing the Thermistor
##347 [ TX / RX ]
BJ printer control ROM/ RAM check error.
A.
Cause: BJ printer control
ROM error
Solution: Power cycle the machine (unplug unit).
Solution: Replace the BJ printer control ROM.
B.
Cause: BJ printer control DRAM error.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the board containing the BJ printer DRAM.
C.
Cause: SCNT PWB malfunction.
Solution: Power cycle the machine (unplug unit).
Solution: Replace the SCNT PWB.
##348 [ TX / RX ]
Ink detection sensor error.
A.
Cause: Ink has adhered to
the ink detection sensor
Solution: Remove the ink, etc., from the sensor's slit.
B.
Cause: The ink detection sensor is faulty
Solution: Replace the ink detection sensor
Solution: Replace the unit containing the ink detection sensor.
##349 [ TX ]
Home position sensor does not detect the home position.
A.
(If the CS does not move from the CS reference position):
1. Cause: The home position
sensor stays ON or OFF.
Cause: The home position sensor is defective.
Solution: Replace the home position sensor.
2. Cause: The CS motor does
not run.
Cause: The CS motor malfunctions.
Solution: Replace the CS motor.
B.
(If the CS does not stop at the CS reference position):
1. Cause: The home position
sensor stays ON or OFF.
Cause: The home position sensor is defective.
Solution: Replace the home position sensor.
##350 [ TX ]
Lead end sensor does not detect the leading end.
A.
(If the CS does not move from the stop position at the right edge of the
document):
1. Cause: The read end
sensor stays ON or OFF.
Cause: The read end sensor is defective.
Solution: Replace the read end sensor.
2. Cause: The CS motor does
not run.
Cause: The CS motor malfunctions.
Solution: Replace the CS motor.
B.
(If the CS does not stop at the right edge of the document):
1. Cause:
The read end sensor stays ON or OFF.
Cause: The read end sensor is defective.
Solution: Replace the read end sensor.
##503 [ TX ]
Fail MCF1 or PIS reception during G1 transmission.
A.
Cause: The other party cannot receive picture signals or EOM properly due
to poor line conditions.
Solution: Have the other party boost their transmission level so they can
receive picture signals or EOM properly.
Solution: Adjust the NL equalizer so the other party can receive picture
signals or EOM properly.
##504 [ RX ]
CD (carrier detect) was interrupted over 1 second and failed EOM or PIS
reception during G1 transmission.
A.
Cause: EOM or PIS from the other party was not received properly due to
poor line conditions.
Solution: Have the other party boost the transmission level to receive
EOM or PIS properly.
##506 [ RX ]
Fail phase synchronization during G1 reception.
A.
Cause: Other party cannot receive signal properly due to poor line
conditions.
Solution: Boost the transmission level so that the other party can
receive the phase signal properly.
Solution: Adjust the NL equalizer so the other party can receive the
phase signal properly.
##507 [ TX ] Fail
CFR1 reception during G1 transmission.
A.
Cause: Other party cannot receive signal properly due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive
properly.
B.
Cause: Other party experienced echo malfunction.
Solution: Perform echo measures as outlined in Service Manual.
Solution: Press the START button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the reception level to prevent the
other party from receiving echo signals.
##509 [ TX / RX ]
Failed to detect end of Tonal signal from other party.
A.
Cause: Line noise
Solution: Contact the telephone company and request line maintenance.
##511 [ TX / RX ]
OPCNT and SCNT do not match.
A.
Cause: Different OPCNT and SCNT models were mounted in the same machine.
Solution: Confirm the PWB's part numbers and use the proper combination.
##526 [ RX ]
Fail phase synchronization in OLD-FM mode.
A.
Cause: Cannot receive phase signal properly due to poor line conditions.
Solution: Have the other party boost the transmission level so they can
receive the phase signal properly.
Solution: Adjust the NL equalizer so the other party can receive the
phase signal properly.
##551 [ TX / RX ]
Voice IC malfunction.
A.
Cause: Defective voice IC; (does not go into ready mode).
Solution: Replace voice IC attached unit.
##552 [ TX ]
DTMF IC malfunction.
A.
Cause: Defective DTMF IC; (does not go into ready mode).
Solution: Replace DTMF IC attached unit.
##553 [ TX / RX ]
Abnormal password memory.
A.
Cause: Defective memory.
Solution: Replace the password memory attached unit.
##554 [ TX / RX ]
Abnormal password input via other party's line.
A.
Cause: Mis-operation by other party; (including time over).
Solution: Have the other party re-input the proper password.
##555 [TX / RX]
Voice memory erased.
A.
Cause: Defective DRAM memory.
Solution: Replace voice memory attached unit.
##603 [ TX ]
Fail MCF reception during MF1 transmission.
A.
Cause: Cannot receive MCF signal from the other party due to poor line
conditions.
Solution: Have the other party boost the transmission level so they can
receive the signal properly.
Solution: Adjust the NL equalizer to properly receive MCF from the other
party properly.
##604 [ RX ]
Fail EOM reception during MF1 transmission.
A.
Cause: Cannot receive the picture or EOM from the other party properly
due to poor line conditions.
Solution: Have the other party boost the transmission level so they can
receive the picture signal or EOM properly.
Solution: Adjust the NL equalizer to receive EOM from the other party
properly.
##606 [ RX I
Fail phase synchronization during MF1 reception.
A.
Cause: Cannot receive phase signal properly due to poor line conditions.
Solution: Have the other party boost their transmission level so they can
receive the phase signal properly.
Solution: Adjust the NL equalizer to receive the phase signal properly.
##607 [ TX ]
Fail CFR reception during MF1 transmission.
A.
Cause: The other party cannot receive properly due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive
properly.
B.
Cause: The other party is out of recording paper.
##609 [ TX / RX ]
Fail to detect end of other party's MF1 signal.
A.
Cause: Line noise.
Solution: Contact the telephone company and request line maintenance.
##610 [ TX ]
Receive PIS during MF1 transmission.
A.
Cause: STOC (F-network side) detected abnormality.
Solution: Check to see if the length of the document transmitted in fine
and standard mode exceeds 630 mm and 420 mm respectively.
B.
Cause: Defective DES sensor.
Solution: Replace sensor.
##611 [ TX ]
Detect CD (carrier detect) interruption for over 1 second during picture
reception upon MF1 reception.
A.
Cause: Picture signal was not received properly due to poor line
conditions.
Solution: Have the other party boost the transmission level to receive
picture signals properly.
##612 [ RX ]
Fail to detect picture signals for 5 seconds after CFR transmission
during MF1 reception.
A.
Cause: Picture signal was not received properly due to poor line
conditions.
Solution: Have the other party boost the transmission level to receive
picture signals properly.
Solution: Adjust the NL equalizer to receive picture signals properly.
**************
##670
[TX] At V.8 late
start, the called party declares the V.8 protocol in DIS signal and this unit
transmits a CI signal, but the protocol does not progress and a T1 time-out
occurs.
A.
Cause: The other party disconnected the line while the CI signal was
being transmitted, or unable to detect ANSam/ DIS from the called party..
Solution: Increase #2 MENU
No. 07 transmission level within a range of -8 to -15 dBm, or set #1 SSSW SW28
bit 0 to 1 to inhibit the V.8/ V.34 protocol on calling.
NOTE:
This code is not in the G3 book even though several manuals indicates it
is.
##671
[RX] At V.8
termination, the protocol did not advance to phase 2 and a T1 time-out occurs
after the caller CM signal was detected.
A.
Cause: The caller disconnected the line or unable to detect the
signal from the caller.
Solution: Increase #2 MENU
No. 07 transmission level within a range of -8 to -15 dBm, or set #1 SSSW SW28
bit 0 to 1 to inhibit the V.8/ V.34 protocol for the called party.
NOTE:
This code is not in the G3 book even though several manuals indicates it
is.
##672
[TX] The protocol did
not move from phase 2 to phase 3 and a T1 time-out error occurred during V.34
transmission.
A.
Cause: Increase #2 MENU No. 07 transmission level within a range of
-8 to -15 dBm, or set #1 SSSW SW28 bit 0 to 1 to inhibit the V.8/ V.34 protocol
on calling.
NOTE:
This code is not in the G3 book even though several manuals indicates it
is.
##673
[RX] The protocol did
not move from phase2 to phase 3 and a T1 time-out error occurred during V.34
reception.
A.
Cause: The transmitter disconnected the line during phase 2 or the
signal from the transmitter was not able to be detected.
Solution: Increase #2 MENU
No. 07 transmission level within a range of -8 to -15 dBm, or set #1 SSSW SW28
bit 0 to 1 to inhibit the V.8/ V.34 protocol on termination.
NOTE:
This code is not in the G3 book even though several manuals indicates it
is.
##674
[TX] The protocol did
not move from phase 3 to phase 4 and a T1 time-out error occurred during V.34
transmission.
A.
Cause: The called party
disconnected the line during phase 3 or unable to detect the signal from the
called party.
Solution: Increase #2 MENU
No. 07 transmission level within a range of -8 to -15 dBm, or set #1 SSSW SW28
bit 0 to 1 to inhibit the V.8/ V.34 protocol on calling.
NOTE:
This code is not in the G3 book even though several manuals indicates it
is.
##675
[RX] ]
The protocol did not move from phase 3 to phase 4 and a T1 time-out error
occurred during V.34 reception.
A.
Cause: The transmitter disconnected the line during phase 3 or
unable to detect the signal from the transmitter.
Solution: Increase #2 MENU
No. 07 transmission level within a range of -8 to -15 dBm, or set #1 SSSW SW28
bit 0 to 1 to inhibit the V.8/ V.34 protocol on termination.
NOTE:
This code is not in the G3 book even though several manuals indicates it
is.
**************
##701 [ RX ]
Other party fails to detect NACK signals during ARQ reception.
A.
Cause: The other party cannot receive NACK signals properly due to poor
line conditions.
Solution: Have the other party boost the transmission level to receive
NACK signals properly.
##702 [ RX ]
Exceed continuous repeat number (9 times) of NACK signals during ARQ
reception.
A.
Cause: Cannot receive picture signals from the other party properly due
to poor line conditions.
Solution: Have the other party boost the transmission level to receive
picture signals properly.
Solution: Adjust the NL equalizer to receive picture signals properly.
##703 [ RX ]
Exceeded total repeat number (20 times) of NACK signals during ARQ
reception.
A.
Cause: Usually--cannot receive picture signals properly due to poor line
conditions.
Solution: Have the other party boost the transmission level to receive
picture signals properly.
Solution: Adjust the NL equalizer to receive picture signals properly.
##704 [ RX ]
Exceeded NSC repeat number (3 times) during ARQ reception.
A.
Cause: The other party cannot receive NSC signals properly due to poor
line conditions.
Solution: Boost the transmission level so that the other party can
receive NSC properly.
B.
Cause: Cannot receive signals properly due to poor line conditions.
Solution: Have the other party boost the transmission level to receive
signals properly.
##705 [ TX ]
Receive DCN after NACK signal detection during ARQ reception.
A.
Cause: Other party cannot receive; (out of recording paper or not set).
Solution: Contact other party and have them reset their machine.
##706 [ TX ]
Exceed memory during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##707 [ TX ]
NSC transmission speed command error during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##710 [ TX ]
Exceed RR transmission number after no response to picture transmission
during ARQ transmission.
A.
Cause: Picture signal or RR was not properly transmitted due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive
picture signals or RR properly.
Solution: Lower the transmission start speed to 4800 bps.
Solution: Adjust the NL equalizer so the other party can receive picture
signals or RR properly.
##711 [ TX ]
REJ reception after picture transmission during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##712 [ TX ]
RNR reception after picture transmission during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##713 [ TX ]
Receive signals other than RR, RNR or REJ after picture transmission
during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##714 [ TX ]
Time over due to failure to receive REJ during retransmission procedures
upon ARQ transmission.
A.
Cause: The other party cannot receive ACK properly due to poor line
conditions.
Solution: Boost the transmission level so that the other party can
receive ACK properly.
B.
Cause: Cannot receive REJ due to poor line conditions.
Solution: Have the other party boost their transmission level to receive
REJ properly.
##715 [ TX ]
Receive signals other than RR, RNR or REJ after retransmission procedures
during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##716 [ TX ]
Fail to fall back during ARQ transmission.
A.
Cause: Cannot transmit
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
Solution: Adjust the NL equalizer so the other party can receive signals
properly.
##717 [ TX ]
Other party's buffer memory over during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##718 [ TX ]
Decode error by other party during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##719 [ TX ]
Wrong block number by other party during ARQ transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##730 [ RX ]
Time over due to failure to receive signals corresponding to RR for 6
seconds after picture reception during ARQ reception.
A.
Cause: The other party cannot receive RR properly due to poor line
conditions.
Solution: Boost the transmission level so that the other party can
receive signals properly.
B.
Cause: Cannot receive signals properly due to poor line conditions.
Solution: Have the other party boost the transmission level to receive
the signals properly.
##731 [ RX ]
REJ reception after picture reception during ARQ.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##732 [ RX ]
Receive RNR after picture reception.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##734 [ RX ]
Excessive NACK transmission (3 times) due to failure to receive ACK
during retransmission procedure upon ARQ reception.
A.
Cause: The other party
cannot receive NACK properly due to poor line conditions.
Solution: Boost the transmission level so that the other party can
receive NACK properly.
B.
Cause: Cannot receive ACK properly due to poor line conditions.
Solution: Have the other party boost the transmission level to receive
ACK properly.
##735 [ RX ]
Excessive REJ transmission (3 times) during retransmission procedures
upon ARQ reception.
A.
Cause: The other party cannot receive REJ properly due to poor line
conditions.
Solution: Boost the transmission level so the other party can receive REJ
properly.
B.
Cause: Cannot receive signals properly due to poor line conditions.
Solution: Have the other party boost the transmission level to receive
signals properly.
##736 [ RX ]
Time over due to failure to receive valid data after ESD reception upon
ARQ reception.
A.
Cause: The other party cannot receive data properly due to poor line
conditions.
Solution: Have the other party lower the transmission start speed to 4800
bps.
Solution: Adjust the NL equalizer to receive the data properly.
Solution: Have the other party boost the transmission level to receive
data properly.
Solution: Have the other party add an EPT to the V29 modem signal.
##737 [ RX ]
Picture decode error during ARQ reception.
A.
Cause: Abnormal protocol; (fill or EOL present in picture data).
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##738 [ RX ]
Wrong block number during ARQ reception.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##739 [ RX ]
Exceed buffer memory during ARQ reception.
A.
Cause: Abnormal protocol; (your busy signal is not canceled within 30
seconds after receiving RNR
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##740 [ RX ]
Other party fails to fall back during ARQ reception.
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Adjust the NL
equalizer to receive signals properly.
Solution: Have the other party boost the transmission level to receive
signals properly.
##750 [ TX ]
Exceed repeat protocol due to failure to receive significant signals
after transmitting PPS-NULL during ECM transmission.
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
Solution: Adjust the NL equalizer so the other party can receive signals
properly.
Solution: Add EPT (echo
protect tones) to V29 modem signal.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##751 [ TX ]
Receive signals other than MCF, PPR or RNR after transmitting PPS-NULL
during ECM transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##752 [ TX ]
Receive DCN after PPS-NULL transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
B.
Cause: The STOP button was
pressed during communication.
Solution: Retransmit.
##753 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after
PPS-NULL transmission during ECM transmission.
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##754 [ TX ]
Exceed retransmit protocol after PPS-null transmission during ECM
transmission.
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##755 [ TX ]
Exceed protocol retransmission limit due to failure to receive
significant signals after PPS-MPS transmission during ECM transmission
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
Solution: Adjust the NL equalizer so the other party can receive signals
properly.
Solution: Add EPT (echo protect tones) to V29 modem signal.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##756 [ TX ]
Receive signals other than MCF, PPR or RNR after PPS-MPS transmission
upon ECM transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##757 [ TX ]
Receive DCN after PPS-MPS transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
B.
Cause: The STOP button was
pressed during communication.
Solution: Retransmit.
##758 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after
PPS-MPS transmission during ECM transmission.
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##759 [ TX ]
Exceed retransmit protocol after PPS-MPS transmission during ECM
transmission.
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can
receive signals properly.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##760 [ TX ]
Exceed protocol retransmission limit due to failure to receive
significant signals after PPS-EOM transmission during ECM transmission.
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other party boost their transmission level so signals
can be received properly.
Solution: Adjust the NL equalizer so the other party can receive signals
properly.
Solution: Add EPT (echo protect tones) to V29 modem signal.
##761 [ TX ]
Received signals other than MCF, PPR or RNR after PPS-EOM transmission
during ECM transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##762 [ TX ]
Receive DCN after PPS-EOM transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
B.
Cause: The STOP button was
pressed during communication.
Solution: Retransmit.
##763 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after
PPS-MPS transmission during ECM transmission
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##764 [ TX ]
Exceed retransmit protocol after PPS-EOM transmission during ECM
transmission.
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##765 [ TX ]
Exceed protocol retransmission limit due to failure to receive
significant signals after PPS-EOP transmission during ECM transmission
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other party boost their transmission level so signals
can be received properly.
Solution: Adjust the NL equalizer so the other party can receive signals
properly.
Solution: Add EPT (echo protect tones) to V29 modem signal.
##766 [ TX ]
Receive signals other than MCF, PPR or RNR after PPS-EOP transmission
upon ECM transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##767 [ TX ]
Receive DCN after PPS-EOP transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
B.
Cause: The STOP button was
pressed during communication.
Solution: Retransmit.
##768 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after PPS-EOP
transmission during ECM transmission
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##769 [ TX ]
Exceed retransmit protocol after PPS-EOP transmission during ECM
transmission.
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##770 [ TX ]
Exceed repeat protocol limit due to failure to receive significant
signals after transmitting EOR-NULL during ECM transmission.
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other party boost their transmission level so signals
can be received properly.
##771 [ TX ]
Receive signals other than ERA after transmitting EOR-null during ECM
transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##772 [ TX ]
Receive DCN after EOR-NULL transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Boost the transmission level so the other party can receive
signals properly.
B.
Cause: The STOP button was
pressed during communication.
Solution: Retransmit.
##773 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after EOR-NULL
transmission during ECM transmission.
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##774 [ TX ]
Receive ERR after EOR-NULL transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
Solution: Adjust the NL
equalizer so that the other fax can correctly receive signals.
B.
Cause: The other party
experienced an echo malfunction.
Solution: Take echo counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the transmission level to prevent
the other party from receiving echo signals.
##775 [ TX ]
Exceed protocol retransmission limit due to failure to receive
significant signals after EOR-MPS transmission during ECM transmission.
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other fax
raise their transmission level so signals can be received correctly.
##776 [ TX ]
Receive signals other than ERR after EOP-MPS transmission during ECM
transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##777 [ TX ]
Receive DCN after EOR-MPS transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
B.
Cause: The STOP key was
pressed during communication.
Solution: Transmit again.
##778 [ TX ]
Exceed protocol retransmission limit or T5 time (60.seconds) after EOR-MPS
transmission during ECM transmission.
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##779 [ TX ]
Receive ERR after EOR-MPS transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
Solution: Adjust the NL
equalizer so that the other fax can correctly receive signals.
B.
Cause: The other party
experienced an echo malfunction.
Solution: Take echo counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the transmission level to prevent
the other party from receiving echo signals.
##780 [ TX ]
Exceed protocol retransmission limit due to failure to receive
significant signals after EOR-EOM transmission during ECM transmission.
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other fax
raise their transmission level so signals can be received correctly.
##781 [ TX ]
Receive signals other than ERR after EOR-EOM transmission during ECM
transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##782 [ TX ]
Receive DCN after EOR-EOM transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
B.
Cause: The STOP key was
pressed during communication.
Solution: Transmit again.
##783 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after EOR-EOM
transmission during ECM transmission
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##784 [ TX ]
Receive ERR after EOR-EOM transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
Solution: Adjust the NL
equalizer so that the other fax can correctly receive signals.
B.
Cause: The other party
experienced an echo malfunction.
Solution: Take echo counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the transmission level to prevent
the other party from receiving echo signals.
##785 [ TX ]
Exceed protocol retransmission limit due to failure to receive
significant signals after EOR-EOP transmission during ECM transmission.
A.
Cause: Cannot send/ receive
signals properly due to poor line conditions.
Solution: Raise the modem
transmission level, so that the other fax can receive signals correctly.
Solution: Have the other fax
raise their transmission level so signals can be received correctly.
##786 [ TX ]
Receive signals other than ERR after EOR-EOP transmission during ECM
transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##787 [ TX ]
Receive DCN after EOR-EOP transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
B.
Cause: The STOP key was
pressed during communication.
Solution: Transmit again.
##788 [ TX ]
Exceed protocol retransmission limit or T5 time (60 seconds) after
EOR-EOP transmission during ECM transmission.
A.
Cause: The other party's
page buffer file was full or being used.
Solution: Lengthen the T5
timer; reset ECM frame size at 256 bytes to 64 Kbytes.
##789 [ TX ]
Receive ERR after EOR-EOP transmission during ECM transmission.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
Solution: Adjust the NL
equalizer so that the other fax can correctly receive signals.
B.
Cause: The other party
experienced an echo malfunction.
Solution: Take echo counter-measures as described in Service manual.
Solution: Press Start button after confirming the first DIS from the
other party during a manual call.
Solution: Add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: Have the other party lower the transmission level so it does
not receive echoes.
##790 [ RX ]
Transmit ERR after EOR-Q reception during ECM reception.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
Solution: Adjust the NL
equalizer so that the other fax can correctly receive signals.
B.
Cause: The other party
experienced an echo malfunction.
Solution: Take echo counter-measures as described
in Service manual.
##791 [ TX / RX ]
Receive non-significant signals during ECM mode procedures.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##792 [ RX ]
Fail to detect PPS-NULL between partial pages during ECM reception.
A.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other fax
raise their transmission level so signals can be received correctly.
##793 [ RX ]
Time over due to failure to receive valid frame during high speed signal
reception upon ECM reception.
A.
Cause: Cannot send signals
properly due to poor line conditions.
Solution: Raise the modem
transmission level so that the other fax can correctly receive signals.
Solution: Adjust the NL
equalizer so that the other fax can correctly receive signals.
B.
Cause: Cannot receive
signals properly due to poor line conditions.
Solution: Have the other fax
change their transmit speed to 4800bps.
Solution: Have the other fax
raise their transmission level so signals can be received correctly.
C.
Cause: The other party
experienced an echo malfunction.
Solution: Take echo counter-measures as described in Service manual.
##794 [ TX ]
Receive all 0 PPR during ECM transmission.
A.
Cause: Abnormal protocol.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##795 [ TX / RX ]
Trouble in the decoding processing during communication.
A.
Cause: The communications
coding was busy.
Solution:
1. Power cycle the machine.
2. Replace SCNT PWB.
##799 [ TX ]
System error.
A.
Cause: An attempt was made
to transmit EOR during the Canon express protocol
Solution:
1. Power cycle the machine.
2. Replace SCNT PWB.
##800 [ TX ]
Multi-file transmission error.
A.
Cause: Multi-file
transmission error took place when the relay command was being relayed
Solution: Perform normal
transmission to the other party and confirm the cause.
Solution: Record the protocol on DAT tape and then request the Canon
Technical center to analyze the information.
##801 [ TX / RX ]
Exceed signal repeat limit to hard disk.
A.
Cause: No response to
signals to hard disk.
Solution: Check the
connections around the hard disk.
##802 [TX / RX ]
Hard disk message reception error.
A.
Cause: The message from the
hard disk cannot be received properly.
Solution: Replace the hard
disk.
##803 [ TX / RX ]
Phase error when receiving status from hard disk.
A.
Cause: Received signals
other than expected when receiving status signals from the hard disk.
Solution: Replace the hard
disk.
##804 [ TX / RX ]
Hard disk specified 0 for transfer data Length.
A.
Cause: Data length 0 was
specified when receiving data from the hard disk.
Solution: Replace the hard
disk.
##805 [ TX / RX ]
Exceed data retransmission limit to hard disk.
A.
Cause: No response
regardless of data transmission after transmitting protocol to the hard disk.
Solution: Replace the hard
disk.
##806 [ TX / RX ]
Hard disk error.
A.
Cause: Disk trouble (signal
transfer error, data transfer error).
Solution: Replace the hard
disk.
##807 [ TX / RX ]
Hard disk error.
A.
Cause: Disk trouble (signal
transfer error, data transfer error).
Solution: Replace the hard
disk.
##808 [ TX / RX ]
Hard disk error.
A.
Cause: Disk trouble (signal
transfer error, data transfer error).
Solution: Replace the hard
disk.
##809 [ TX / RX ]
Hard disk error.
A.
Cause: Disk trouble (signal
transfer error, data transfer error).
Solution: Replace the hard
disk.
##811 [ TX / RX ]
Hard disk error.
A.
Cause: Disk trouble (signal
transfer error, data transfer error).
Solution: Replace the hard
disk.
##812 [ TX / RX ]
Hard disk error.
A.
Cause: Disk trouble (signal
transfer error, data transfer error).
Solution: Replace the hard
disk.
##813 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn the power OFF
then turn it back ON.
##814 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn the power OFF
then turn it back ON.
##815 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn the power OFF
then turn it back ON.
##816 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn the power OFF
then turn it back ON.
##817 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn
the power OFF then turn it back ON.
##818 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn the power OFF
then turn it back ON.
##819 [ TX / RX ]
Hard disk out of control (System error).
A.
Cause: Abnormal signal
processing (timing, etc.) by hard disk.
Solution: Turn the power OFF
then turn it back ON.
G3 Error Service Codes:
#001 [ TX ]
Paper Jam
A.
Cause: document caught in feeder.
Solution: remove document and retry.
B.
Cause: document is not of standard size and thickness.
Solution: make a copy onto standard paper or use a carrier sheet.
C.
Cause: machine failure.
Solution: perform procedures indicated in the trouble shooting section of
the service manual.
#002 [ TX ]
Short Document
A.
Cause: document is not of standard length.
Solution: make a copy onto standard paper or use a carrier sheet.
#003 [ TX / RX ]
Copy page, Transmission time over.
A.
Cause: the document is too long, requiring longer than the standard time
to transmit or copy
Solution: Divide to document into smaller sections and retransmit, or
reset the page timer to a greater number.
B.
Cause: It takes longer than the standard time to receive the document.
Solution: ask TX side to divide the document into smaller sections and
retransmit, reset the page timer to a greater number or contact the TX side to
confirm problem.
C.
Cause: machine failure.
Solution: perform procedures indicated in the trouble shooting section of
the service
#004 [ TX ]
(Talk Notice) Call failure.
A.
Cause: other machine is not a Canon machine and/ or does not support this
Canon Fax exclusive feature.
#005 [ TX / RX ]
Initial ID (T1) time over.
A.
Cause: erroneous tone/ pulse setting.
Solution: correct tone/ pulse setting.
B.
Cause: takes too long to connect with the other party.
Solution: add a long pause to delay the timer start time when making an
auto-dialing registration; or, set a longer value for the T1 timer setting so
that the operations will not exceed the time limit.
C.
Cause: other party does not respond.
Solution: contact other party and have them check their machine.
D.
Cause: other party's communication mode is not compatible (G2, G3, etc.)
Solution: no remedy for the communication mode since it is dependant on
the specifications of the machine.
E.
Cause: transmission made to MF1 without MF1 mode being set.
Solution: switch to MF1 mode and retry.
F.
Cause: second dial tone is not received in transmission to F-network.
Solution: check to confirm membership in the F-network then call
telephone company to report a "troubled connection".
G.
Cause: in TX, echo causes other machine to malfunction.
Solution: use echo countermeasures in service manual.
Solution: wait to press START key unit the first DIS signal from the
other party is heard (manual call).
Solution: add a long pause after the telephone number when registering
the user in the auto- dialing directory so that the system will not respond to
the first DIS from the other party.
Solution: have the other party lower their
reception level to prevent them from receiving the echo signals.
H.
Cause: in RX, echo causes this machine to malfunction.
Solution: use echo countermeasures in service manual.
#006 [ TX ]
Transmission Failure.
#006 [ RX ]
Phase synchronization not possible with OLD-FM.
A.
Cause: transmission button was pressed without setting document.
Solution: set document and retry.
B.
Cause: bad connection inhibited reception of proper phase signals.
Solution: have other party increase their transmission level; or, adjust
the NL equalizer.
#007 [ TX / RX ]
Talk reservation failure (other operator does not pickup).
#007 [ RX ]
Phase synchronization not possible.
A.
Cause: Other party made talk reservation however the operator does not
answer the other party's call.
Solution: Contact the other party and have them answer the phone after
transmission.
B.
Cause: Bad connection inhibited reception of proper phase signals.
Solution: Have other party raise their transmission level for
proper reception of the phase signals.
Solution: Adjust the NL equalizer for proper reception of the phase
signals.
#008 [ TX ]
Polling Password error.
A.
Cause: Polling error generated due
to different ID password in the other machine.
Solution: If the other party uses a Canon machine, contact them and have
them set the same password.
Solution: Set all the passwords to [ 1 ] if the other party does not use
a Canon machine.
Solution: Record the TX protocol in DAT format and then request the local
Canon office or technical center to analyze the information.
#009 [ RX ]
Recording paper jam or Out of paper.
A.
Cause: Facsimile paper jam.
Solution: Fix the paper jam.
B.
Cause: Out of Facsimile paper.
Solution: Refill machine with paper.
C.
Cause: Machine failure.
Solution: Perform trouble shooting procedures outlined in the service
manual.
#010 [ TX / RX ]
Communication control memory full.
A.
Cause: Documents in memory cannot be printed because the machine is out
of paper, and as a result there is not enough memory.
Solution: Refill machine with paper.
#011 [ RX ]
Polling error.
A.
Cause: Document is not set in the other party's machine.
Solution: Have the other party set the document in their machine.
B.
Cause: Polling reception was not activated since the document was not
properly set for transmission.
Solution: Properly set the document and transmit.
#012 [ TX ]
Other party Out of paper.
A.
Cause: There is not recording paper in the other party's machine.
Solution: Have the other party refilled their machine with paper.
#013 [ TX ]
Document size error in MF1 mode.
A.
Cause: B4 width document was sent in MF1 mode.
Solution: Make an A4 or smaller copy of the document with a copier and
them transmit.
#014 [ TX ]
Paper size error.
A.
Cause: A non-A4 size document was sent without making proper settings.
Solution: Set the document size and then transmit.
#015 [ TX ]
Fine mode error during G2 transmission.
A.
Cause: G2 transmission was attempted in fine mode.
Solution: Transmit documents in standard mode during G2 transmissions.
#018 [ TX ]
Automatic dialing error.
A.
Cause: Erroneous tone/ pulse setting.
Solution: properly set the tone/ pulse mode.
B.
Cause: Connection time is too long.
Solution: Add a longer pause to delay the timer start time when
registering the automatic dialing feature.
Solution: Reset the T1 timer with a longer value to prevent time over.
C.
Cause: Time over due to busy signal.
Solution: Redial.
D.
Cause: Time over because of a busy line or because the other party's
machine was not on.
Solution: Contact the other party to check the cause of the trouble.
E.
Cause: Time over since the party's machine was out of recording paper.
Solution: Have the other party refill their machine with recording paper.
F.
Cause: Second dial tone did not arrive from the F-network transmission.
Solution: Check whether they are a member of the F-network and contact
the telephone company and notify them of connecting trouble.
#019 [ TX ]
Memory transmission failure.
A.
Cause: Image data are not stored in memory during memory transmission.
(Delayed/ redial transmission).
Solution: Perform memory transmission operations after storing the data
in the memory or transmit the data direct.
#020 [ TX ]
Different recording paper size.
A.
Cause: The image size is B4 when the recording paper is A4 during memory
transmit or memory copy operations.
Solution: Set B4 size recording paper.
#021 [ RX ]
DCN during polling reception.
A.
Cause: Wrong password
Solution: Contact the other party to use the same
password.
#022 [ TX ]
Call failure.
A.
Cause: Broadcasting or multi-polling telephone number is not registered
for auto dialing.
Solution: Register the other party's number in auto-dialing.
#023 [ TX ]
Memory transmission error.
A.
Cause: MF1 memory
transmission attempted
Solution: Memory transmission is not possible to MF1. Transmit the
document direct.
#024 [ TX ]
Delayed transmission failure.
A.
Cause: The document is not set at the time set for delayed transmission
(direct).
Solution: None since it is passed the specified time.
#025 [ TX / RX ]
Automatic dialing setting error.
A.
Cause: MF mode was set for auto-dialing to receive polling message.
Cause: MF mode and confidential or relay were set and auto-dialing was
attempted.
Cause: Confidential and relay were set, and was auto-dialing attempted.
Solution: Set auto-dialing in accordance with the procedures indicated in
the service Manual.
#027 [ RX ]
LBP power off
A.
Cause: LBP power is turned off.
Solution: Turn LBP on.
#028 [ RX ]
LBP cartridge missing.
A.
Cause: LBP cartridge
is not set
Solution: Set LBP cartridge
#029 [ RX ]
LBP recording paper jam.
A.
Cause: Recording paper is jammed
Solution: Clear the paper jam
#030 [ RX ]
No LBP Toner.
A.
Cause: LBP toner cartridge is empty.
Solution: Replace LBP toner cartridge.
#031 [ RX ]
No LBP paper warning.
A.
Cause: No LBP recording paper.
Solution: Replenish LBP recording paper.
#032 [ TX ]
Power failure.
A.
Cause: Power failure in delayed transmission standby mode.
Solution: Set delayed transmission.
B.
Cause: Power was turned off.
Solution: Turn on power and set delayed transmission.
C.
Cause: Power trouble.
Solution: Replace the PSU.
#033 [ TX ]
Confidential transmission failure.
A.
Cause: The other party's machine does not have a confidential mailbox
feature
Solution: Perform regular transmission since confidential transmission is
not possible.
#034 [ TX ]
Failure to transmit to other party's confidential mailbox.
A.
Cause: Designated mailbox does not exist in the other party's machine.
Solution: Check the number of the mailbox, then resend to correct
mailbox.
B.
Cause: Other party's memory is full.
Solution: Have the other party clear some memory.
#035 [ TX ]
No original relay transmission.
A.
Cause: No relay function in the other party's machine.
Solution: Transmit direct by sequential broadcast transmission since
relay transmission is not possible.
#036 [ TX ]
No original relay transmission.
A.
Cause: User telephone number is not registered in the auto-dialing relay
directory of the relay station.
Solution: Register the number into the auto-dialing relay directory of
the relay station.
B.
Cause: User telephone number is erroneously registered in the
auto-dialing relay directory of the relay station.
Solution: Register the correct number into the auto-dialing relay
directory of the relay station.
C.
Cause: The relay feature of the relay station is turned OFF.
Solution: Turn on the relay feature.
D.
Cause: The relay station's memory is full.
Solution: Have the relay station clear some memory.
#037 [ RX ]
Image memory full.
A.
Cause: Excessive data reception.
Solution: Request clearance of any unnecessary image data and then
retransmit data.
#038 [ TX / RX
] Hard disk error.
A.
Cause: Hard disk file access malfunction
Solution: Follow procedure listed in Service manual.
#039 [ TX ]
Closed network transmission failure.
A.
Cause: The closed network switch is turned OFF.
Solution: Turn ON the closed network switch.
B.
Cause: The other party's closed network switch is turned OFF.
Solution: Request the other party turn ON closed network switch.
C.
Cause: Closed network ID does not match that of the other party.
Solution: Match the closed network ID of your machine with that of the
other party.
D.
Cause: G2 or MF1 transmission was forced during transmission in a closed
network.
Solution: Transmit in G3.
E.
Cause: The other party's machine was a G2 or MF1 within a closed network
Solution: Turn OFF the TX closed network switch.
#040 [ TX ]
Image memory full during sequential broadcast failure.
A.
Cause: Excessive transmission data during broadcasting.
Solution: Clear all unnecessary image data.
Solution: Divide the documents upon broadcasting
Solution: Lower the resolution.
#041 [ TX ]
Broadcasting failure.
A.
Cause: Sequential broadcast transmission was attempted to MF1 or G2
machine.
Solution: Sequential broadcast transmission is not possible to MF1 or G2
machines; send by normal transmission.
#042 [ RX ]
Cutter failure.
A.
Cause: Defective cutter.
Solution: Correct the problem according to the trouble-shooting
procedures in Service manual.
#043 [ RX ]
No Toner Cartridge.
A.
Cause: Toner cartridge is not properly set.
Solution: Properly set the Toner cartridge as indicated in Service
manual.
Solution: Correct the problem according to trouble-shooting section of
Service manual.
B.
Cause: Toner Cartridge is empty.
Solution: Replace the Toner cartridge.
C.
Cause: Sensor malfunction
Solution: Correct the problem according to trouble-shooting section of
Service manual.
#044 [ RX ]
Recording paper and Ink sheet cartridge size incompatible.
A.
Cause: The size of the recording paper and ink sheet cartridge differ.
Solution: Replace either the recording paper or the ink sheet cartridge
so that they will be the same size.
B.
Cause: Sensor malfunction.
Solution: Correct the problem according to trouble-shooting section of
Service manual.
#045 [ TX ]
Incomplete transmission warning
A.
Cause: Mistaken input of number of documents to transmit.
Solution: Nothing possible since all documents were sent.
B.
Cause: Set a number less than the number of documents to transmit
Solution: Transmit the remaining documents.
C.
Cause: Double feed
Solution: Repeat transmission.
#046 [ RX ]
Receiving restriction.
A.
Cause: The other party's telephone number is not registered in the
auto-dialing directory.
Solution: Set receiving restrictions to NO and then have other party
retransmit the document.
Solution: Register the other party's telephone number in the auto-dialing
directory.
#047 [ RX ]
Reception failure.
A.
Cause: Recording paper cover is open.
Solution: Close the recording paper cover.
B.
Cause: Sensor malfunction.
Solution: Correct the problem according to trouble-shooting section of
Service manual.
#048 [ TX ]
Multi-file transmission error.
A.
Cause: Multi-file transmission error takes place during batch
transmission.
Solution: Transmit to the other party by regular transmission, and then
look for cause of failure.
#049 [ TX ]
Multi-file transmission error.
A. Cause: The cipher key
does not match that of the other machine.
Solution: Match the cipher keys of the local and the remote FAX machine.
#050 [ TX ]
Cipher transmission failed.
A.
Cause: The other FAX machine does not have cipher transmission function.
Solution: Perform normal transmission, instead of cipher transmission.
Solution: Select the normal fallback function.
Solution: Transmit to a FAX machine that has the cipher transmission
function.
#051 [ TX ]
Decode error during cipher reception.
A.
Cause: The cipher keys do not match.
Solution: Contact the other party and match the cipher keys.
#052 [ RX ]
Image memory full by no ink error.
A.
Cause: Image memory full due to printer error caused by no ink in BJ.
Solution: Replace the BJ cartridge and have the other party retransmit
the data if necessary.
#054 [ TX / RX ]
Call failure.
A.
Cause: User ID not registered.
Solution: Register ID.
B.
Cause: User telephone number not registered
Solution: Register user telephone number.
#055 [ TX ]
Other party does not have MDC capability. (GP55 only)
A.
Cause: When attempting to send image signals from the computer, GP does
not have MDC capability.
Solution: Output document to
printer and fax page instead of Faxing from computer.
Solution: Transmit to a machine that is MDC compatible.
#080 [ TX ]
Other party does not have ITU-T recommended Sub-address reception
function.
A.
Cause: The other party's DIS bit 40 is 0.
Solution: Transmit to another machine which has the function.
Solution: If the other party is a Canon machine, set to confidential
transmission, or other available mode, and transmit.
Solution: If the other party is not a Canon machine, transmit in normal
G3 mode.
#081 [ TX ]
Other party does not have ITU-T recommended password reception function.
A.
Cause: The other party's DIS bit 50 is 0.
Solution: Transmit to another machine which has the function.
Solution: If the other party is a Canon machine, set to confidential
transmission, or other available mode, and transmit.
Solution: If the other party is not a Canon machine, transmit in normal
G3 mode.
#082 [ TX ]
Other party does not have ITU-T recommended selective polling
transmission function.
A.
Cause: The other party's DIS bit 47 is set to 47.
Solution: If the other party is not a Canon machine, have the other party
enabled for polling transmission and do polling reception.
Solution: If the other party is a Canon machine, use the Canon original
polling ID and do polling reception.
#102 [ TX / RX ]
Different password during password transmission.
A.
Cause: Password of both machines do not match.
Solution: Match the passwords.
#103 [ RX ]
Wrong user telephone number during ID transmission.
A.
Cause: The other party's user telephone number is not registered in your
auto-dialing directory.
Solution: Register the other party's telephone number.
B.
Cause: The other party's user telephone number is wrongly registered in
your auto-dialing directory.
Solution: Re-register the number correctly.
#104 [ TX / RX ]
Password transmission failure
A.
Cause: The other party's machine does not have a password transmission
feature.
Solution: Turn on the ID transmission mode and repeat the transmission.
#105 [ TX / RX ]
Wrong user telephone number during ID transmission.
A.
Cause: The other party's user telephone number was not registered.
Solution: Contact the other party to have the user telephone number
registered.
#106 [ TX / RX ]
Low backup battery.
A.
Cause: The backup battery for the IC to record messages when power is OFF
was disconnected.
Cause: The voltage dropped when the power was turned OFF.
Solution: Replace the battery after the power is turned OFF, and then
rerecord the message after the power is turned back ON.
#995 [ TX / RX ]
Memory transmission reservation cancellation.
A. Cause: (TX) The user
cleared the memory transmission reservation.
Solution: Transmit again.
B.
Cause: (RX) The user cleared the memory reception image data.
Solution: Contact the other party and have them retransmit.
#996 [ TX / RX ]
Hard disk error.
A.
Cause: Hard disk trouble.
Solution: Correct the problem by following instructions under
trouble-shooting in Service manual.
#997 [ TX / RX ]
Power failure during transmission.
A.
Cause: There was a power failure or the power was turned OFF during
transmission.
Solution: Correct the problem by following instructions under
trouble-shooting in Service manual.
B.
Cause: Malfunctioning power unit.
Solution: Replace the power unit.
#998 [ RX ]
Memory RX completed.
A.
Cause: Code indicates on the activity report that memory reception took
place.
Solution: No measures possible since the transmission result was OK.
#999 [ RX ]
Image memory full during memory reception.
A.
Cause: Excessive data transmitted during memory reception.
Solution: Set the recording paper and ask the other party to retransmit
the data.
MAIN PAGE