NOTE: 1) Never install telephone wiring during a lightning storm.
2) Never install telephone jacks in wet locations unless the jack is
specifically designed for wet locations.
3) Never touch uninsulated telephone wires or terminals unless the
telephone line has been disconnected at the network interface.
4) Use caution when installing or modifying telephone lines.
5) Avoid using a telephone (other than a cordless type) during an electrical
storm. There may be a remote risk of electric shock from lightning.
6) If there is a gas leak, do not use the telephone in the vicinity of the leak
to report it.
!
CAUTION
1. Before installing the fax unit, switch off the main power and operation
switches, and disconnect the power cord.
2. The fax unit contains a lithium battery. The danger of explosion exists if
a battery of this type is incorrectly replaced. Replace only with the same
or an equivalent type recommended by the manufacturer. Discard used
batteries in accordance with the manufacturer’s instructions.
Installation
1-1
FAX UNIT10 August, 2001
1.1.2 FLOW CHART
Before installing the fax unit and/or fax options, refer to the following flow chart.
START
Will you be installing the
Fax Function Upgrade Unit and/or
Expansion Memory?
No
Will you be installing the G3
Interface Unit?
Yes
Remove the NCU board from the
standard NCU unit.
Attach the bracket and NCU board
to the G3 unit.
Will you be installing the ISDN
Remove the G4 board from the G4
unit.
Attach the G4 board to the G3 unit.
Option?
Yes
Install the Fax Function Upgrade
Unit and/or Expansion Memory to
Yes
the FCU board.
No
Will you be installing the ISDN
Option?
Yes
Remove the NCU board from the
standard NCU unit.
Attach the bracket and NCU board
to the G4 unit.
No
No
Install the FCU baord and the NCU unit in the machine.
Reaasemble the operation panel and affix the decals.
Will you be installing the handset?
* USA model only
Yes
Install the handset.
END
1-2
No
B418I501.WMF
10 August, 2001FAX UNIT
1.1.3 FAX OPTION TYPE 1027 INSTALLATION
Installation
[A]
[B]
B418I101.WMF
[C]
[D]
[E]
B418I503.WMF
!
CAUTION
Before installing this option, do the following:
B418I502.WMF
B418I504.WMF
1. If there is a printer option in the machine, print out all data in the printer
buffer.
2. Turn off the main switch and disconnect the power cord and the
network cable.
1. Remove the small cover [A] (1 rivet) and the rear cover [B] (4 screws).
2. Attach the NCU unit [C] (4 screws) to the machine.
3. Remove the shield cover [D] (8 screws).
4. Attach the DIMM board (4 MB) [E] to slot 1 (CN7) on the controller board.
1-3
FAX UNIT10 August, 2001
[D]
[A]
[C]
[B]
B418I505.WMF
[L]
[E]
[F]
[G]
[H]
[I]
[J]
B418I106.WMF
[M
[K]
B418I607.WMF
[N]
B418I108.WMF
5. Turn on the battery switch (SW1) [A] on the MBU board, then attach the FCU
unit [B] (6 screws). Connect the cables [C], then clamp the cable at [D] as
shown. Replace the rear cover and the small cover.
6. Remove parts [E], [G] and [J], then install parts [F], [H] and [I].
7. Attach the FCC decal [K] and the serial number decal [L] to the rear cover as
shown. Then install the small cover [M] on the rear cover.
8. Attach the super G3 decal [N] as shown.
1-4
10 August, 2001FAX UNIT
[A]
B418I552.WMF
9. If the ADF has been installed, insert the stamp cartridge [A] into the ADF as
shown.
Installation
10. Connect the telephone line to the “LINE” jack at the rear of the machine.
11. Plug in the machine and turn on the main power switch.
NOTE: The copier must be connected to a properly-grounded socket outlet.
12. Be sure to set the clock (date and time).
13. Enter service mode and program the serial number into the fax unit (SP 3-102-
000). The serial number can be found on the serial number label (attached to
the machine in step 7).
1-5
FAX UNIT OPTIONS10 August, 2001
1.2 FAX UNIT OPTIONS
1.2.1 G3 INTERFACE UNIT TYPE 1027 INSTALLATION
[D]
[C]
[A]
[B]
B448I101.WMF
B448I502.WMF
[F]
[E]
B448I503.WMF
!
CAUTION
Before installing this option, do the following:
1. If there is a printer option in the machine, print out all data in the printer
buffer.
2. Turn off the main switch and disconnect the power cord and the network
cable.
1. Remove the small cover [A] (1 rivet) and the rear cover [B] (4 screws). Then cut
away the jack window [C].
2. Remove the NCU unit [D] (4 screws, 2 connectors)
3. Remove the NCU [E] from the NCU unit (4 screws). Connect cable [F] to the
FCU.
If the G4 unit is not being installed at the same time, go to step 6.
1-6
10 August, 2001FAX UNIT OPTIONS
[B]
[E]
[C]
[A]
B448I104.WMF
[D]
[C]
Installation
[D]
[A]
B448I105.WMF
Do steps 4 and 5 only when installing the G4 unit at the same time.
4. Remove the G4 board [A] (2 screws), the bracket [C] (2 screws) and the ISDN
connector [D] from the G4 unit [B].
5. Attach the G4 board [A] (2 screws), the bracket [C] (2 screws) and the ISDN
connector [D] to the G3 unit [E] as shown.
1-7
FAX UNIT OPTIONS10 August, 2001
[A]
[D]
B448I506.WMF
[E]
[C]
[B]
B448I507.WMF
6. Attach the G3 unit [A] to the machine (6 screws, 1 connector).
7. Connect cable [B] to the interface board and attach bracket [C] (1 screw). Then
attach the NCU [D] (removed from the NCU unit in step 3) to the G3 unit (4
screws). After that, connect cable [E] to the NCU [D], then clamp cable [E] as
shown.
8. Replace the rear cover and the small cover.
9. Connect the cable to the LINE2 jack, then plug in the machine and turn the
main switch on.
10. Enter service mode and set bit 1 of communication switch 16 to “1”. After that
turn the main switch off and on.
11. Print the system parameter list and ensure that “SG3-V34” is listed as an
option.
12. Set up and program the items required for PSTN-2 communications.
1-8
10 August, 2001FAX UNIT OPTIONS
1.2.2 ISDN OPTION TYPE 1027 INSTALLATION
[B]
[C]
Installation
[A]
B449I101.WMF
[D]
B449I502.WMF
!
CAUTION
Before installing this option, do the following:
1. If there is a printer option in the machine, print out all data in the printer
buffer.
2. Turn off the main switch and disconnect the power cord and the network
cable.
1. Remove the small cover [A] (1 rivet) and the rear cover [B] (4 screws). Then cut
away the jack window [C].
2. Remove the NCU unit [D] (4 screws, 2 connectors)
1-9
FAX UNIT OPTIONS10 August, 2001
[B]
[A]
B449I503.WMF
[A]
[E]
[C]
B449I104.WMF
[D]
[B]
B449I505.WMF
3. Remove the NCU [A] from the NCU unit (4 screws). Connect the cable [B] to
the FCU.
4. Attach the G4 unit [C] to the machine (6 screws, 1 connector).
5. Connect the cable [B] to the interface board and attach bracket [D] (1 screw).
Then attach the NCU [A] (removed from the NCU unit in step 3) to the G4 unit
(4 screws). After that, connect the cable [E] to the NCU [A], then clamp cable
[E] as shown.
1-10
10 August, 2001FAX UNIT OPTIONS
6. Replace the rear cover and the small cover.
[B]
[A]
Installation
B360I102.WMF
B366I108.WMF
[D]
[C]
B366I101.WMF
7. Connect the cable to the ISDN jack, then plug in the machine and turn the main
switch on.
8. Attach the FCC/IC approval label to the machine near the ISDN jack. (This step
is only for US/Canada.)
9. Enter service mode and set bit 2 of communication switch 16 to "1". After that
turn the main switch off and on.
10. Print the system parameter list and ensure that "G4" is listed as an option.
11. Set up and program the items required for ISDN communications. After setting
up the ISDN parameters, be sure to turn the main switch off and on.
1-11
10 August, 2001ERROR CODES
2. TROUBLESHOOTING
2.1 ERROR CODES
If an error code occurs, retry the communication. If the same problem occurs, try to
fix the problem as suggested below. Note that some error codes appear only in the
error code display and on the service report.
CodeMeaningSuggested Cause/Action
0-00DIS/NSF not detecte d within
40 s of Start being pressed
0-01DCN received unexpectedly
0-03Incompatible modem at the
other end
0-04CFR or FTT not received
after modem training
0-05Unsuccessful after modem
training at 2400 bps
• Check the line connection.
• Check the NCU - FCU connectors.
• The machine at the other end may be
incompatible.
• Replace the NCU or FCU.
• Check for DIS/NSF wit h an oscilloscope.
• If the rx signal is weak, there may be a bad line.
• The other party is out of paper or has a jammed
printer.
• The other party pressed Stop during
communication.
• The other terminal is incompatible.
• Check the line connection.
• Check the NCU - FCU connectors.
• Try changing the tx level and/or cable equalizer
settings.
• Replace the FCU or NCU.
• The other terminal may be faulty; try sending to
another machine.
• If the rx signal is weak or defectiv e, there may be
a bad line.
Cross reference
• Tx level - NCU Pa r ameter 01 (PSTN)
• Cable equalizer - G3 Switch 07 (PSTN)
• Dedicated Tx parameters - Section 4
• Check the line connection.
• Check the NCU - FCU connectors.
• Try adjusting the tx level and/ or cable equalizer.
• Replace the FCU or NCU.
• Check for line problems.
Cross reference
• See error code 0-04.
Trouble-
shooting
2-1
ERROR CODES10 August, 2001
CodeMeaningSuggested Cause/Action
0-06The other terminal did not
reply to DCS
0-07No post-message response
from the other end after a
page was sent
0-08The other end sent RTN or
PIN after receiving a page,
because there were too
many errors
0-14
Non-standard post messag e
response code received
• Check the line connection.
• Check the FCU - NCU connectors.
• Try adjusting the tx level and/ or cable equalizer
settings.
• Replace the NCU or FCU.
• The other end may be defective or incompatible;
try sending to another machine.
• Check for line problems.
Cross reference
• See error code 0-04.
• Check the line connection.
• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• The other end may have jammed or run out o f
paper.
• The other end user may have disconne ct ed t he
call.
• Check for a bad line.
• The other end may be defectiv e; t ry sending to
another machine.
• Check the line connection.
• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• The other end may have jammed, or run out of
paper or memory space.
• Try adjusting the tx level and/ or cable equalizer
settings.
• The other end may have a defectiv e
modem/NCU/FC U; try sending to another
machine.
• Check for line problems and noise.
Cross reference
• Tx level - NCU Pa r ameter 01 (PSTN)
• Cable equalizer - G3 Switch 07 (PSTN)
• Dedicated Tx parameters - Section 4
• Check the FCU - NCU connectors.
• Incompatible or defective remote terminal; try
sending to another machin e.
• Noisy line: resend.
• Try adjusting the tx level and/ or cable equalizer
settings.
• Replace the NCU or FCU.
Cross reference
• See error code 0-08.
2-2
10 August, 2001ERROR CODES
CodeMeaningSuggested Cause/Action
0-15The other terminal is not
capable of specific
functions.
The other terminal is not capa bl e of a ccepting the
following functions, or the other terminal’s memory
is full.
• Confidential rx
• Transfer function
• SEP/SUB/PWD/SID
0-16CFR or FTT not detected
after modem training in
confidential or transfer mod e
• Check the line connection.
• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• Try adjusting the tx level and/ or cable equalizer
settings.
• The other end may have discon nect ed, or it may
be defective; try calli ng another machine.
• If the rx signal level is too low , there may be a
line problem.
Cross reference
• See error code 0-08.
0-17Communication was
interrupted by pressing the
If the Stop key was not pressed and this error keeps
occurring, replace the operation p anel.
Stop key.
0-20Facsimile data not received
within 6 s of retraining
• Check the line connection.
• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• Check for line problems.
• Try calling another fax machine.
• Try adjusting the reconstruction ti me for the first
line and/or rx cable equaliz er setting.
Cross reference
• Reconstruction time - G3 Switch 0A, bit 6
• Rx cable equalizer - G3 Swit ch 07 (PSTN)
0-21EOL signal (end-of-line)
from the other end not
received within 5 s of the
previous EOL signal
• Check the connection s bet ween the FCU, NCU,
& line.
• Check for line noise or other line problems.
• Replace the NCU or FCU.
• The remote machine may be defective or may
have disconnected.
Cross reference
• Maximum interval between EOLs and between
ECM frames - G3 Bit Switch 0A, bit 4
0-22The signal from the other
end was interrupted for
more than the acceptable
modem carrier drop time
(default: 200 ms)
• Check the line connection.
• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• Defective remote terminal.
• Check for line noise or other line problems.
• Try adjusting the acceptable mode m c arrier drop
time.
Cross reference
• Acceptable modem carrier drop time - G3 Sw itch
0A, bits 0 and 1
Trouble-
shooting
2-3
ERROR CODES10 August, 2001
CodeMeaningSuggested Cause/Action
0-23Too many errors during
reception
0-30The other terminal did not
reply to NSS(A) in AI shor t
protocol mode
0-32The other terminal sent a
DCS, which contained
functions that the receiv ing
machine cannot handle.
0-52Polarity changed during
communication
0-70The communication mode
specified in CM/J M was not
available
(V.8 calling and called
terminal)
• Check the line connection.
• Check the FCU - NCU connectors.
• Replace the NCU or FCU.
• Defective remote terminal.
• Check for line noise or other line problems.
• Try asking the other end to adjust t heir tx level.
• Try adjusting the rx cable equaliz er set t ing an d/ or
rx error criteria.
Cross reference
• Rx cable equalizer - G3 Swit ch 07 (PSTN)
• Rx error criteria - Communication Switch 02, bits
0 and 1
• Check the line connection.
• Check the FCU - NCU connectors.
• Try adjusting the tx level and/ or cable equalizer
settings.
• The other terminal may not be co mp at ible.
Cross reference
• Dedicated tx parameters - Section 4
• Check the protocol dump list .
• Ask the other party to contact the manufacturer.
• Check the line connection.
Retry communication.
• The other terminal did not have a co mpatible
communication mode (e.g., t he ot her t erminal
was a V.34 data modem and not a fax modem.)
• A polling tx file was not ready at t he ot her
terminal when polling rx was initiated from the
calling terminal.
0-74
0-75
0-76The calling terminal fell back
The calling term inal fell back
to T.30 mode, because it
could not detect ANSam
after sending CI.
The called terminal fell bac k
to T.30 mode, because it
could not detect a CM in
response to ANSam
(ANSam timeout).
to T.30 mode, because it
could not detect a JM in
response to a CM
(CM timeout).
• The calling terminal coul d not detect ANSam due
to noise, etc.
• ANSam was too short to detect.
• Check the line connection an d condition.
• Try making a call to another V.8/ V. 34 fax.
• The terminal could not detect ANSam.
• Check the line connection an d condition.
• Try receiving a call from another V.8/V.34 fax.
• The called terminal could not det ect a CM due to
noise, etc.
• Check the line connection an d condition.
• Try making a call to another V.8/ V. 34 fax.
2-4
10 August, 2001ERROR CODES
CodeMeaningSuggested Cause/Action
0-77The called terminal fell back
to T.30 mode, because it
could not detect a CJ in
response to JM
(JM timeout).
• The calling terminal coul d not det ect a JM due to
noise, etc.
• A network that has narrow bandwidt h cannot
pass JM to the other end.
• Check the line connection an d condition.
• Try receiving a call from another V.8/V.34 fax.
0-79The called terminal detected
CI while waiting for a V. 21
signal.
0-80
The line was disconnected
due to a timeout in V.34
phase 2 – line probing.
0-81The line was disconnected
due to a timeout in V.34
phase 3 – equalizer trainin g .
0-82The line was disconnected
due to a timeout in the V.34
phase 4 – control channel
start-up.
0-83The line was disconnected
due to a timeout in the V.34
control channel restart
sequence.
Check for line noise or other line problems.
If this error occurs, the called terminal falls back to
T.30 mode.
• The guard timer expired while starting t hese
phases. Serious noise, narrow bandwidth, or low
signal level can cause t hese errors.
If these errors happen at the transmitti ng t erminal:
• Try making a call at a later time.
• Try using V.17 or a slower modem using
dedicated tx parameters.
• Try increasing the tx level.
• Try adjusting the tx cable equa lizer setting.
If these errors happen at the receiving t erminal:
• Try adjusting the rx cable equaliz er set t ing.
• Try increasing the tx level.
• Try using V.17 or a slower modem if the s ame
error is frequent when receiving from multiple
senders.
0-84
0-85
0-86The line was disconnected
The line was disconnected
due to abnormal signaling in
V.34 phase 4 – control
channel start-up.
The line was disconnected
due to abnormal signaling in
V.34 control channel restart.
because the other terminal
• The signal did not stop within 10 s.
• Turn off the machine, then turn it back on.
• If the same error is frequent, replace the FCU.
• The signal did not stop within 10 s.
• Turn off the machine, then turn it back on.
• If the same error is frequent, replace the FCU.
• The other terminal was incompatible.
• Ask the other party to contact the manufacturer.
requested a data rate using
MPh that was not available
in the currently selected
symbol rate.
0-87
The control channel started
after an unsuccessful
primary channel.
• The receiving terminal restarted the control
channel because data recept ion in the primary
channel was not successfu l.
• This does not result in an error communicat ion.
0-88
The line was disconnected
because PPR was
• Try using a lower data rate at the start.
• Try adjusting the cable equalizer setting.
transmitted/received 9
(default) times within the
same ECM frame.
2-25JBIG data reconstruction
2-26
2-27
2-28JBIG data reconstruction
2-50The machine resets itself for
2-51The machine resets itself
3-00G4 interface board reset
3-10Disconnection during I S DN
3-11Disconnection during I S DN
3-20
3-21A CSA signal was sent
3-30Mismatched specifications
4-01Line current was cut
4-10
JBIG compression or
reconstruction error
error (BIH error)
JBIG data reconstruction
error (Float marker error)
JBIG data reconstruction
error (End marker error)
error (Timeout)
a fatal FCU syst em error
because of a fatal
communication error
G3 communication
G4 communication
A CSA signal was received
during ISDN G4
communication
during ISDN G4
communication, becau se t he
Stop key was pressed
(rx capability)
Communication failed
because of an ID Code
mismatch (Closed Network)
or Tel. No./CSI mismatch
(Protection against Wrong
Connections)
• Replace the FCU.
• Turn off the machine, then turn it back on.
• Update the modem ROM.
• Replace the FCU.
• Replace the FCU.
• Turn off the machine, then turn it back on.
• Replace the EXFUNC board i f the error is
frequent.
• Turn off the machine, then turn it back on.
• Replace the EXFUNC board i f the error is
frequent.
• JBIG data error
• Check the sender’s JBIG function.
• Update the MBU RO M .
• If this is frequent, update the ROM, or replace the
FCU.
• If this is frequent, update the ROM, or replace the
FCU.
• Replace the G4 interface board or FCU.
• Check the other terminal and the IS DN line.
• The other terminal may have dialed a wrong
number.
• Check the other terminal and the IS DN line.
• The operator at the other terminal may have
interrupted the communication.
• The local operator has interrupte d t he
communication.
• Check the receive capabilities requested from the
other terminal.
• Check the line connector.
• Check the connection bet w een FCU and NCU.
• Check for line problems.
• Replace the FCU or the NCU .
• Get the ID Codes the same and/or the CSI s
programmed correctly, then resend.
• The machine at the other end may be defective.
2-6
10 August, 2001ERROR CODES
CodeMeaningSuggested Cause/Action
5-00Data construction not
• Replace the FCU.
possible
5-01Data reconstruction not
possible
5-10DCR timer expired
5-20Storage impossible because
of a lack of memory
• Temporary memory shortage.
• Test the SAF memory.
• Replace the FCU or optiona l EXMEM board
5-21Memory overflow
5-22Mode table overflow after
the second page of a
scanned document
5-23Print data error when
printing a substitute rx or
confidential rx message
5-24Memory overflow after the
second page of a scanned
document
• Wait for the messages which are currently in the
memory to be sent or delete some files from
memory.
• Test the SAF memory.
• Ask the other end to resend the messag e.
• Replace the FCU or optiona l EXMEM board.
• Try using a lower resolution setting.
• Wait for the messages which are currently in the
memory to be sent or delete some files from
memory.
5-25SAF file access error
6-00G3 ECM - T1 time out
during reception of facsi m ile
• Replace the FCU or EXMEM board.
• Try adjusting the rx cable equaliz er.
• Replace the FCU or NCU.
data
6-01
G3 ECM - no V.21 signal
was received
6-02
G3 ECM - EOR was
received
6-04G3 ECM - RTC not detected
• Check the line connection.
• Check connections from t he NCU to the FCU.
• Check for a bad line or defective remote ter minal.
• Replace the FCU or NCU.
6-05G3 ECM - facsimile data
frame not received within 18
s of CFR, but there was no
line fail
• Check the line connection.
• Check connections from t he NCU to the FCU.
• Check for a bad line or defective remote ter minal.
• Replace the FCU or NCU.
• Try adjusting the rx cable equaliz er
Cross reference
• Rx cable equalizer - G3 Swit ch 07 (PSTN)
6-06G3 ECM - coding/decoding
error
6-08G3 ECM - PIP/PIN received
in reply to PPS.NULL
• Defective FCU.
• The other terminal may be defective.
• The other end pressed Stop during
communication.
• The other terminal may be defective.
6-09G3 ECM - ERR received
• Check for a noisy line.
• Adjust the tx levels of the communicating
machines.
• See code 6-05.
Trouble-
shooting
2-7
ERROR CODES10 August, 2001
CodeMeaningSuggested Cause/Action
6-10G3 ECM - error frames still
received at the other end
after all communication
attempts at 2400 bps
6-21V.21 flag detected during
high speed modem
communication
6-22
6-99V.21 signal not stopped
22-00Original length exceeded the
22-01Memory overflow while
22-02Tx or rx job stalled due to
22-04The machine cannot store
23-00Data read timeout during
25-00The machine software
F0-xxV.34 modem error
F6-8xSG3-V34 modem error
The machine resets the
sequence because of an
abnormal handshake in the
V.34 control channel
within 6 s
maximum scan length
receiving
line disconnection at the
other end
received data in the SAF
construction
resets itself after a fatal
transmission error occurred
• Check for line noise.
• Adjust the tx level (use NCU parameter 01 or the
dedicated tx parameter for that address).
• Check the line connection.
• Defective remote terminal.
• The other terminal may be defective or
incompatible.
• Check for line noise.
• If the same error occurs frequently, replac e t he
FCU.
• Defective remote terminal.
• Replace the FCU.
• Divide the original into more than one page.
• Check the resolution used for sca nning. Lower
the scan resolution if possible.
• Add optional page memory.
• Wait for the files in the queue t o be sent .
• Delete unnecessary files from memory.
• Transfer the substitute reception files t o an
another fax machine, if the machine’s printer is
busy or out of order.
• Add an optional SAF memory card or hard di sk.
• The job started normally but did not finish
normally; data may or may not have been
received fully .
• Restart the machine.
• Update the ROM
• Replace the FCU.
• Restart the machine.
• Replace the FCU
• Update the ROM
• Replace the FCU.
• Replace the FCU.
• Update the SG3-V34 mode m RO M.
• Replace the SG3-V34 boar d.
• Check for line noise or other line problems.
• Try communicating another V.8/V.34 fax.
2-8
10 August, 2001ERROR CODES FOR THE ISDN OPTION
2.2 ERROR CODES FOR THE ISDN OPTION
The tables on the following pages show the error codes for the ISDN option.
The meaning of the numbers in the Action column is as follows.
1. Check Layer 1 signaling with a protocol analyzer to determine the cause of the
problem. This may require assistance from a G4 specialist.
2. Repeat the communication. If the problem does not repeat itself, the problem
was a temporary one caused by the user connecting the machine to another
interface. However, if the problem remains, there is a network problem.
3. There is a network problem.
4. There is a network problem. Do the following:
• Check the error bit rate of the network. If it is high, contact the network and
ask them to improve the line.
• Check the network speed (is it 56 or 64 kbps), and make sure that the bit
switch setting is correct. You may also use the dedicated transmission
parameters if this problem only occurs when dialing certain numbers.
• Check that the user dialed the correct number.
Trouble-
shooting
5. There is a network problem, or a problem in the machine at the other end.
6. There is a problem in the machine at the other end; ask a technician to check it.
7. The machine at the other end is not a Group 4 fax terminal.
8. The machine is not compatible with the machine at the other end. A
compatibility test is needed.
Error codes related to the errors detected by the FCU are listed in the service
manual of the main body.
2-9
ERROR CODES FOR THE ISDN OPTION10 August, 2001
2.2.1 D-CHANNEL LAYER MANAGEMENT
CodeProbable CauseAction
7-00Link reset2
7-01Link set-up failed because of ti me-out .2
7-02Link release failed because of ti me-out .2
7-03Link set-up parameter error2
2.2.2 D-CHANNEL, L AYER 1
CodeProbable CauseAction
7-10T3 timeout (layer 1 activation error)1
7-11No connection on the S0 int erface1
7-12Deactivated1
2.2.3 D-CHANNEL LINK L AYER
CodeProbable CauseAction
7-20At the start of link set-up, the ma chine received an unsolicited S (F=1).2
7-21At the start of link set-up, the ma chi ne received an unsolicited DM
(F=1).
7-22At TEI release, the machine received an unsolicited UA (F=1).2
7-23At the start of link set-up, the ma chi ne received an unsolicited DM
(F=0).
7-24At TEI release, the machine received an unsolicited UA (F=0).2
7-25SABME received at the st art of network link set-upNo error
7-26N200 retransmission error for SABME2
7-27N200 retransmission error for DISC2
7-28N200 retransmission error for situat ion enquiry (RR)2
7-29N(R) sequence number error3
7-30N(S) sequence number error3
7-31FRMR received3
7-32Non-standard frame received3
7-33Abnormal frame length3
7-34N201 error; information field N in the I frame exceeded N2013
7-35T201 timeout; timeout whi le w aiting for checking3
7-36T202 timeout; timeout while waiting for ID assignment3
2
2
2-10
10 August, 2001ERROR CODES FOR THE ISDN OPTION
2.2.4 D-CHANNEL NETWORK L AYER
CodeProbable CauseAction
7-40Insufficient mandatory information elements3
7-41Abnormal LI for a mandatory information element3
7-42T301 timeout; time out while waiting for R:CONN3
7-43T303 timeout; timeout w h i le w aiting for R: CALL-PROC etc.3
7-44T304 timeout; timeout w h i le w aiting for R: CALL-PROC etc.3
7-45T305 timeout; timeout while waiting for R:REL3
7-46T308 timeout; timeout while waiting for R:REL-COMP3
7-47T310 timeout; timeout w h i le w aiting for R: ALERT etc.3
7-48T313 timeout; timeout while waiting for R:CONN-ACK3
7-49Internal error3
7-51Release call reference during communication3
2.2.5 B-CHANNEL LINK L AYER
CodeProbable CauseAction
7-60T3 timeout; timeout while wa it ing for flag4
7-61T3 timeout; timeout while wa it ing for SABM during an incoming call4
7-62T1 timeout x N2; timeout w hi le w aiting for UA after sending SABM5
7-63
7-64T1 timeout x N2; timeout whi le waiting for SABM or DISC after sending
7-65T1 timeout x N2; timeout while waiting for a response to DISC5
7-66RNR x N2 (other end busy, RCB counter error)5
7-67Invalid (Ad) frame received5
7-68Invalid short frame receiv ed5
7-69Link reset error5
7-70FRMR received5
7-71Non-standard (Cn) frame received5
7-72An S or U frame having an in formation field was received5
7-73A frame longer than the maximum N1 length was received5
7-74An S or I frame having an N(R) error w as received5
7-75CRC error3
T1 timeout x N2; timeout whi le w aiting for a response to a transmitted
S frame (P=1)
FRMR
5
5
Trouble-
shooting
2-11
ERROR CODES FOR THE ISDN OPTION10 August, 2001
2.2.6 B-CHANNEL NETWORK L AYER
CodeProbable CauseAction
7-80A packet having an abnorma l G FI w as received6
7-81A packet was received that had a l ogical channel number different
from the logical channel be ing used for the communication
7-82A packet containing a format error was received6
7-83A packet containing an LI error was received7
7-84A CN packet was received t hat had a PID different from 027
7-85Unsupported packet ty pe received7
7-86Abnormal or unsupporte d fac ility received7
7-87P(s) sequence number error6
7-88P(r) sequence number error6
7-89A reset using S:RQ or R:RI occurred6
7-90A restart using S:RQ or R:SI occurred6
7-91Call set-up error; in reply to S:CR, R:CI wa s received to indicate
rejection of the call
7-92T20 timeout; timeout whil e w ait ing for an SF packet6
7-93T21 timeout; timeout whil e w ait ing for a CC packet6
7-94T22 timeout; timeout whil e w ait ing for an RF packet6
7-95T23 timeout; timeout whil e w ait ing for a CF packet6
7-96T10 timeout; timeout whil e w ait ing for the first frame6
6
7
2.2.7 TRANSPORT LAYER
CodeProbable CauseAction
8-00Invalid block received8
8-01TCC block received8
8-02TBR block received8
8-05TCR block; block format error8
8-06TCR block; block size param et er LI error8
8-07TCR block; extended addressing LI error8
8-08TCR block; block size length error8
8-10TCA block; block format error8
8-11TCA block; Tx origin reference data in TCR disagreed with the address
reference data in TCA
8-12TCA block; octet 7 did not eq ual 08
8-13TCA block; extended addressing LI error8
8-14TCA block; block size exce eded that set by TCR8
8-15TCA block; block size paramet er LI error8
8-20TDT block; block format error8
8-21TDT block; octet 3 did not equal either 00 or 80(H)8
8-22TDT block; the end indicator was “Continue” even though there was no
field data
8-23TDT block; an end block with no f ie ld dat a w as received after an end
indicator of “End”
8-26Timeout during state 0.28
8-27Timeout during state 1.18
8-28Timeout during state 0.38
8
8
8
2-12
10 August, 2001ERROR CODES FOR THE ISDN OPTION
2.2.8 SESSION LAYER
CodeProbable CauseAction
8-30Invalid frame receiv ed8
8-31RSSN received8
8-32CSA received8
8-34Calling terminal identification error in CSS8
8-35Date and time error in CSS8
8-36Window size error in CSS8
8-37Service identification error in CSS8
8-38Session user data error in CSS8
8-39CSS rejected (new session re ject ed)8
8-40Called terminal identification error in RSSP8
8-41Date and time error in RSSP8
8-42Date and time in RSSP was n ot the same as that in CSS8
8-43Window size error in RSSP8
8-44Service identificat ion error in RSSP8
8-45Session user data error in RSSP8
8-47Message synchronization error inside the CCU8
8-48Document task busy8
8-50Ti timeout; non-communicat ion surveillance timer (T.62)8
8-51T2 timeout; timeout while waiting for a response (T.62)8
8-52T3 timeout; CSA timer timeout (T.62)8
8-53G4 board load timer timeout; call ing side waited too long for a new
session
8-54G4 board load timer timeout; calling side waited too long for transport
probability
8-55G4 board load timer timeout; call ed side waited too long for S:RSSP8
8-56G4 board load timer timeout; docume nt t ransmission surveillance t imer
timeout
8-57G4 board load timer timeout; timeout w hi le waiting for a user abort
request after a provider fail
8
8
8
8
Trouble-
shooting
2-13
ERROR CODES FOR THE ISDN OPTION10 August, 2001
2.2.9 DOCUMENT LAYER
CodeProbable CauseAction
8-60T.62 coding format error (LI error)8
8-61A mandatory PI was absent, or the LI for a man dat ory PI was 08
8-62
8-63The LI for session user data exceeded t he maximum value (512)8
8-64The LI for CDUI was not 08
8-65Checkpoint and document reference numbers LI error, or they were
8-66The checkpoint reference nu mb er di ffered from the expected value8
8-70RDGR received8
8-71A non-standard PDU was received while in calling mode8
8-72A non-standard PDU was received while in called mode8
8-73Abnormal PDU received while in calling state ds18
8-7415 consecutive CDCL signals received8
8-75Session window size cont rol error (size not equal to 0)8
8-76Internal error8
Calling/called t erminal identification LI was different from that specified
by F.184 (LI = 24)
not in T.61 (ASCII) coding
8
8
2.2.10 PRESENTATION LAYER
CodeProbable CauseAction
8-80X.209 coding error in session user data (LI error)8
8-81PV error in session user data8
8-82PI error in session user data8
8-83The capabilities in t he session user data of CDS/CDC were not the
same as those in RDCLP
8-84X.209 coding error in the DP (LI error)8
8-85X.209 coding error in the SLD (docu ment descriptor/page descriptor)
(LI error)
8-86SLD object type absen t8
8-87PI error in the SLD (document descript or/ page descriptor)8
8-88
8-89No document descriptor at the st art of the document8
8-90No page descriptor at the start of the page8
8-91Page descriptor PV error8
8-92X.209 coding error in the TU (LI error)8
8-93The TU was absent8
8-94PV error in the TU8
8-95TI error8
8-96X.209 coding nest level >> 8, or an LI form error8
8-97CDPB/CDE received while T U/TI not yet completed, or an unexpected
The capabilities in the SLD (document descriptor/page descriptor) are
duplicated or are not the same as those in RDCLP
PDU was received wh ile analyzing an SLD
8
8
8
8
2-14
10 August, 2001FAX SC CODES
2.3 FAX SC CODES
2.3.1 OVERVIEW
When the FCU detects a Fax SC Code condition other than SC1201 and SC1207,
it resets itself automatically (default setting). This initializes the FCU without
erasing files in the SA F memory or resetting the switches.
NOTE: For details on Fax SC Codes 1201 and 1207, refer to the following
sections.
If bit 7 of System Switch 1F is changed to “1”, when the FCU detects a Fax SC
Code condition, it displays the code on the display and stops working until the fax
unit is initialized using one of the following me thods:
• Hold down the “7” and “9” keys for more than 10 s.
• Turn off the main power switch and turn it back on.
2.3.2 SC1201
When the FCU detects an unrecoverable error in the SRAM, which requires a
complete SRAM initialization, the fax unit displays this SC Code and stops.
There is no way to recover from this error condition without a complete SRAM
initialization (all the user and service programmed data will be erased).
Trouble-
shooting
The possible causes are:
• SRAM backup battery defect, or SW1 on the MBU is at the “OFF” position
• SRAM on the MBU has a physical defect
• Flash memory card connection was loose
2.3.3 SC1207
This is the same as SC1201 except the error location is the SRAM on the Fax
Function Upgrade board.
The possible causes are:
• SRAM backup battery defect, or SW1 on the Fax Function Upgrade board is at
the “OFF” position.
• SRAM on the Fax Function Upgrade board has a physical defect.
• The Fax Function Upgrade board connection was loose.
2-15
Loading...
+ 112 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.