Service manual

Operating the System Remotely C-19
C.1.6 Troubleshooting Guide
Table C-3 lists a number of possible causes and suggested solutions for
symptoms you might see.
Table C-3 RCM Troubleshooting
Symptom Possible Cause Suggested Solution
The local terminal
will not communi-
cate with the system
or the RCM.
System and terminal baud rate
set incorrectly.
Cables not correctly installed.
Set the system and
terminal baud rates to
9600 baud.
Review external cable
installation.
RCM will not
answer when the
modem is called.
Modem cables may be
incorrectly installed.
RCM remote access is disabled.
RCM does not have a valid
password set.
The local terminal is currently
in the RCM console firmware.
On power-up, the RCM defers
initializing the modem for 30
seconds to allow the modem to
complete its internal
diagnostics and initialization.
Modem may have had power
cycled since last being
initialized or modem is not set
up correctly.
Check modem phone
lines and connections.
Enable remote access.
Set password and enable
remote access.
Issue a quit command
on the local terminal.
Wait 30 seconds after
powering up the system
and RCM before
attempting to dial in.
Enter enable command
from RCM console.