Ricoh D3D9 Field Service Manual page 48

3.Troubleshooting
Code
0-84 The line was disconnected due to
abnormal signaling in V.34 phase 4 –
control channel start-up.
0-85 The line was disconnected due to
abnormal signaling in V.34 control
channel restart.
0-86 The line was disconnected because the
other terminal 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.
0-88 The line was disconnected because PPR
was transmitted/received 9 (default)
times within the same ECM frame.
2-11 Only one V.21 connection flag was
received
2-12 Modem clock irregularity
2-13 Modem initialization error
2-22 Counter overflow error of JBIG chip
2-23 JBIG compression or reconstruction
error
2-24 JBIG ASIC error
2-25 JBIG data reconstruction error (BIH
error)
2-26 JBIG data reconstruction error (Float
marker error)
2-27 JBIG data reconstruction error (End
marker error)
2-28 JBIG data reconstruction error
(Timeout)
2-29 JBIG trailing edge maker error
44
Meaning Suggested Cause/Action
•
The signal did not stop within 10 s.
•
Turn OFF the main power, and 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 main power, and 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.
•
The receiving terminal restarted the control channel
because data reception in the primary channel was not
successful.
•
This does not result in an error communication.
•
Try using a lower data rate at the start.
•
Try adjusting the cable equalizer setting.
•
Replace the FCU.
•
Replace the FCU.
•
Turn OFF the main power, and then turn it back ON.
•
Update the modem ROM.
•
Replace the FCU.
If error occurs frequently, change the settings for resolution,
paper size, and compression type.
Turn OFF the main power, and then turn it back ON.
•
Turn OFF the main power, and then turn it back ON.
•
JBIG data error
•
Check the sender's JBIG function.
•
Update the FCU ROM.
•
FCU defective