Networking your garden

This week, a summer distraction and complete geek-out as we network our garden irrigation system.

The problem is that standard irrigation timers just do not cut it when you have a large garden. We have such a garden with 29 separate watering zones, and we wound up with two clusters of timers in two buildings separated by some 200 feet, one cluster in a barn and the other in a basement.

This might not sound too problematic until you notice in passing that this flower bed needs more water or that shrub looks a little dry, or rain makes it necessary to skip all watering for 24 hours, or a high wind makes it pointless to have sprinklers on at all.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

This week, a summer distraction and complete geek-out as we network our garden irrigation system.

The problem is that standard irrigation timers just do not cut it when you have a large garden. We have such a garden with 29 separate watering zones, and we wound up with two clusters of timers in two buildings separated by some 200 feet, one cluster in a barn and the other in a basement.

This might not sound too problematic until you notice in passing that this flower bed needs more water or that shrub looks a little dry, or rain makes it necessary to skip all watering for 24 hours, or a high wind makes it pointless to have sprinklers on at all.

Any of these critical horticultural situations can turn into an inconvenient trek to the barn or basement only to find that the timer you want is in the other location. Then when you do find the right one you have to fool with a horrible user interface. The obvious solution is networking.

We looked around for remote controllable irrigation systems, and not wanting to spend thousands of dollars on commercial products designed for watering hundreds of acres we concluded that an X-10 product might help.

X-10 is a simple, low-speed, power-line network technology that Gearhead covered a few years ago (here and here). While it is not the most robust or high-performance network offering it is cost-effective (cheap) and adequate for this kind of application.

After much research, we also settled on a neat device called the Rain8 from WGL & Associates. This is a tiny box with three connectors: one for programming; one for connecting to a separate power-line interface module that converts the X-10 signals into a custom serial interface for the Rain8; and a terminal block with eight connections (one for valves or "zone," one common for all valves and two for the 12-volt power supply).

WGL provides a utility for programming the Rain8 that lets you set the X-10 codes and maximum run time for each zone and two optional codes that trigger running the zones in sequence with a separate list of zone run times. There are two further optional codes: one that disables the unit and another that skips the next sequenced run (in effect, a 24-hour delay function).

We found a box to house the equipment (three Rain8s, power supply and power-line interface), wired it all up (click here for some pictures and links to all of the components), and tested it by replacing the timers in the barn.

With a stand-alone X-10 controller plugged in next to the unit, there were no problems. But from the computer room being controlled by a computer through a power-line interface, nothing worked.

We assumed the problem was signal degradation because of the power circuit being about 200 feet long. But after buying a new power-line interface for the Rain8 setup and trying the same on the computer, installing an X-10 signal booster and an X-10 phase coupler, and after much fooling around, we still couldn't get it to work.

It turned out that simply moving the computer's power-line interface from a socket powering several computers to another a dozen feet away with nothing plugged into it fixed the problem. Such are the curiosities of the X-10.