Table of Contents
Advertisement
Communications Troubleshooting
A new radio or modem system that doesn't communicate is difficult to
troubleshoot because proper operation has never been proven, and all
the initial hardware and software settings are suspect. More than one
problem can be present, causing component replacement to be an
inadequate trouble shooting technique. Use the following checklist as an
aid.
•
Does the " " flash (Totalflow Remote Protocol only) with the Listen
Cycle time in the A8 display (default position)? If no,
1) The Protocol needs to be selected in the Entry Mode using
PCCU32.
2) The communication's module in Comm 1 or Comm 2 is missing
or bad or the module is the wrong type (RS232 or RS485).
Note: Comm 1 and Comm 2 are in opposite locations when
compared to the previous electronics board (2015333).
3) Inadequate 12 VDC battery voltage.
•
Insure base radio is working for other locations.
•
Verify Station ID and Device ID matches with WinCCU and is the
only Totalflow device with that ID.
•
Verify Baud rate, Stop Bits, Security Code, and Link Establishment
time are same as CCU.
•
Verify WinCCU is using Packet Protocol. X Series devices support
only DB2 Packet Protocol.
•
Verify wiring to antenna, to UCI, UCI to Radio for RS485 installation
or to Radio/Modem for RS232 installation.
TIP: To check for wiring shorts or opens with two or more wire
connections, use a multimeter set on continuity (resistance).
Check two wires at a time from one unit to another. If black and
white wires are to be tested, disconnect both wires at both ends,
set one probe on black, the other on white. The meter should read
OL or OFL (over range) if no shorts. Jumper the two wires at the
other end. The meter should read a low resistance if no opens.
This method requires only one end of wiring to be tested, no matter
how far the units are apart.
13
Advertisement
Table of Contents
