EasyManua.ls Logo

Ricoh M0A0

Ricoh M0A0
776 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
3.Troubleshooting
16
Code
Meaning
Suggested Cause/Action
Replace the 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-29
Data block format failure in ECM reception
Check for line noise or other line problems.
Check the FCU - NCU connectors.
Replace the NCU or FCU.
0-30
The other terminal did not reply to NSS(A)
in AI short protocol mode.
Check the line connection.
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-33
The data reception (not ECM) is not
completed within 10 minutes.
Check the line connection.
The other terminal may have a defective modem/FCU.
0-52
Polarity changed during communication
Check the line connection.
Retry communication.
0-55
FCU does not detect the SG3.
FCU firmware or board defective.
SG3 firmware or board defective.
0-56
The stored message data exceeds the
capacity of the mailbox in the SG3.
SG3 firmware or board defective.
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
The calling terminal could not detect ANSam due to
noise, etc.

Table of Contents

Related product manuals