RLE SeaHawk Sensing Cable - Manual (Page 2)

Question Response
My water leak detection
cable touches metal. Is
this a problem or potential
problem?
In general, no. The two water sensing wires are covered by a nonconductive polymer weave. This
weave isolates the cable from metal surfaces. However, as with all electrical wires and cable, avoid
sharp objects that can slice or pierce through the insulation and nonconductive polymer weave.
The sensing cable is routed
so that it has to cross over
itself. Can this cause false
alarms?
Crossing sensing cables will not cause false alarms, but it can cause a false distance reading if a
leak occurs at the crossover point. If the cables must cross, use a 10 foot section of non-sensing
cable to jump over the section of sensing cable.
If I suspect a bad section
of sensing cable, how can
I verify that it is ok without
sending it back to RLE for
warranty evaluation?
It can be very difficult to remove sensing cable, so verify the cable is working before you attempt
to remove it and return it to the manufacturer. Use either a cable tester (RLE part # LDCE) or
request a Cable Break Alarm assessment document from RLE to determine which section of cable
may be faulty.
My system shows an alarm
condition, but a leak is not
found at location shown
on display. The system will
not clear. It is in alarm all
the time!
The most common causes for this condition includes:
1. Water is touching the cable in two places at the same time. The distance reading is an
average of the two values. For example, if leaks are detected at 200 feet and at 100 feet, the
system would register a leak at 150 feet ( (200 + 100)/2 = 150 ). This is a common problem
when, after an alarm sounds, the operator resets the system without recording the first value
displayed. It is very rare that water will touch two places on the same cable at the exact same
time. This situation is true for all systems which measure distance. Check the Alarm History
log for the first incidence of the leak.
2. The cable has been exposed to high humidity, or the dew point has been reached. This is
especially common when two or more air conditioners share the same under-floor space.
Problems of this nature can be resolved as follows:
a. Fix the air conditioners. This is sometimes easier said than done as most people believe if
the unit is on and cooling, it is working properly. Extensive investigation may have to be
done just to prove the air conditioner is faulty.
b. Turn the sensitivity adjustment on the controller to its least sensitive setting - refer to
Chapter 3, “Leak Settings” on page 36. This should keep the system from alarming, but
will not resolve the air conditioner problem.
c. Move the cable at least 10’ away from the front of the air conditioner.
d. Cover the sensing cable in front of the air conditioner with spiral wrap (plastic covering
which allows water in but keeps dew point from condensing water on the cable).
3. A cable has been contaminated either chemically (floor sealing chemicals dissolve and damage
cable), or physically (small metallic chips from filings or solder around pipes or wires from
electrical installation). This requires replacement of the cable.
4. The cable has become damaged - most often from a floor tile being dropped on it. Damaged
cable must be repaired or replaced.
Test a SeaHawk Leak Detection System
RLE Technologies recommends testing a leak detection system at least once a year, although some applications may require more
frequent testing. System testing should include the following points:
• With the system powered up, ensure no alarms are present on the system.
• If you are using a distance-read controller, look at the local display or web interface and find the cable current reading.
This value should be 15mA or lower. 0mA is ideal. If the value is 15mA or higher, clean the sensing cable.
• If sensing cable is installed on the floor, test the response time. Place a small puddle of water on the cable, covering a
two inch area along the length of the cable. The controller should alarm within a reasonable time. This time may vary
depending on controller type and the alarm time frame set within the controller. If the controller fails to alarm properly,
contact RLE.
• If sensing cable is mounted to piping, test the response time in a different manner. Place a rag soaked with water
on the cable, covering a two to four inch area along the length of the cable. The controller should alarm within a
reasonable time. This time may vary depending on controller type. If the controller fails to alarm properly, contact RLE.
• Verify all alarms are received by the controller. You can verify this by a change of visual status, through the audible
alarm, a relay closure to another device, email notification, and/or protocol updating to a master device.