Ricoh B022, Руководство по обслуживанию, Страница: 608 / 878

ERROR CODES
B418 2-4 SM
Code Meaning Suggested Cause/Action
0-23 Too many errors during
reception
•
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 their tx level.
•
Try adjusting the rx cable equalizer setting and/or
rx error criteria.
Cross reference
•
Rx cable equalizer - G3 Switch 07 (PSTN)
•
Rx error criteria - Communication Switch 02, bits
0 and 1
0-30 The other terminal did not
reply to NSS(A) in AI short
protocol mode
•
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 compatible.
Cross reference
•
Dedicated tx parameters - Section 4
0-32 The other terminal sent a
DCS, which contained
functions that the receiving
machine cannot handle.
•
Check the protocol dump list.
•
Ask the other party to contact the manufacturer.
0-52 Polarity changed during
communication
•
Check the line connection.
Retry communication.
0-70 The communication mode
specified in CM/JM was not
available
(V.8 calling and called
terminal)
•
The other terminal did not have a compatible
communication mode (e.g., the other terminal
was a V.34 data modem and not a fax modem.)
•
A polling tx file was not ready at the other
terminal when polling rx was initiated from the
calling terminal.
0-74 The calling terminal fell back
to T.30 mode, because it
could not detect ANSam
after sending CI.
•
The calling terminal could not detect ANSam due
to noise, etc.
•
ANSam was too short to detect.
•
Check the line connection and condition.
•
Try making a call to another V.8/V.34 fax.
0-75 The called terminal fell back
to T.30 mode, because it
could not detect a CM in
response to ANSam
(ANSam timeout).
•
The terminal could not detect ANSam.
•
Check the line connection and condition.
•
Try receiving a call from another V.8/V.34 fax.
0-76 The calling terminal fell back
to T.30 mode, because it
could not detect a JM in
response to a CM
(CM timeout).
•
The called terminal could not detect a CM due to
noise, etc.
•
Check the line connection and condition.
•
Try making a call to another V.8/V.34 fax.