30
VTM6801
+
Installation and Operation Manual
Appendix A: Communication and Control Troubleshooting Tips
Software Communication and Control Issues
•
“+ Pilot Lite Fails to Communicate with Installed Modules” on
page 30
•
“+ Pilot Lite Does Not Find All Modules in Frame” on page 31
•
“+ Pilot Lite or CCS Software Application Not Responding” on
page 32
•
“+ Pilot Lite Cannot Control a Module Showing
in the Control Window” on page 32
•
“+ Pilot Lite Status Bar Reports “Not Ready”” on page 32
•
“CCS Software Application or Remote Control Panel Does Not
Communicate with Module” on page 33
•
“Alarm Query Fails When a Device Reboots” on page 33
+
Pilot Lite Fails to Communicate with Installed Modules
Confirm that the following items are not the reason for the
communication failure:
•
The proper module slot has not been specified (
+
Pilot Lite is not
communicating with the appropriate slot). See your
Frame Installation and Operation Manual
for more information on
slot identification.
•
The COM port is used elsewhere (Check that the correct COM port
is configured in
+
Pilot Lite and that another application is not
using that COM port).
•
The actual frame ID does not match with the two DIP switch
settings in the back of the frame (
+
Pilot Lite is not communicating
with the proper frame). See your
Frame Installation and
Operation Manual
for more information on frame ID switch
settings.
•
A null modem cable is not being used. Between the PC running
+
Pilot Lite and the FR6802
+
frame, there should be a null RS-232
modem cable. At minimum, this requires that pins 2 and 3 are
crossed and 5 to 5 for ground.
•
An ICE6800
+
or 6800
+
ETH module is installed in the frame
(
+
Pilot Lite control is disabled if an ICE6800
+
or 6800
+
ETH
control module is installed in the frame; ICE6800
+
and 6800
+
ETH
modules are used for CCS control).
