AvL Technologies Appendix D, Interface And Reference Manual

Page: 16 / 16

iDirect Modem
AvL Technologies | Proprietary – Content is Subject to Change without Notice
15
Issues and Troubleshooting 5.
Issue Description Corrective Action
AAQ will not communicate to
Modem Device Window does not say
“iDirect” at the top
Check that the module has been
installed. This can be done through
the AAQRemote GUI’s
Help→Version
Info .
Check that the iDirect is configured as
the Scan, Coarse, and Fine Source for
the selected Target
AAQ will not communicate to
Modem
System in an alarm state
“iDirect- Not Ready”
Device Window shows “Not
Connected” or “Establishing
Comms”
Check the configuration items and
make sure the iDirect modem module
is configured to communicate through
Serial or Ethernet.
Check Serial or Ethernet cables and
connections.
AAQ will not log into the
Modem The Device Window item
“Console Logged in” is false.
Check that the Console username and
password in the Core Configuration
are correct for the modem.
AAQ will not log into the
Modem The Device Window item
“Telnet Logged in” is false.
Check that the Telnet username
and/or password in the Core
Configuration are correct.
The appropriate Telnet command
should also be identified. The default
value “telnet 0” could be modified by
the iDirect options file. In some cases
this changes the location of the telnet
to a specific IP address (ex. “telnet
10.1.1.1”).
AAQ will not acquire or loses
Signal Lock during Peaking
“All signal sources tried with no
valid signal detected” or “Invalid
Signal For Peaking” error
message reached after an
attempted acquire.
Check that the AAQ is communicating
with the modem.
Check that the correct target profile is
selected and that it is configured
properly.
Check that the Scan and Peaking
parameters are configured correctly
in the Signal tab of the Configuration
Window
Check all RF cables and connections.