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. A checklist follows 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. 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 flow computer with that ID.
•
Verify Baud rate, Stop Bits, Security Code, and Listen Cycle time are
the same as WinCCU.
•
Verify WinCCU is using Packet Protocol.
support DB2 Packet Protocol.
•
Verify a cable is in place from J3 on the
the radio and a cable from the radio to the antenna.
•
When using communications termination board, verify wiring to radio
or other communication's device. Also verify setting for J2 on the
termination board. For RS232 set to DCD for Alarm Cryout feature.
(See page 11)
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 device to another. If black
and white wires are to be tested, disconnect both wires at both
ends, put 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 devices are apart.
µ
FLO Series devices only
µ
FLO electronics board to
13
Advertisement
Table of Contents
