Overview

iNetGrow is a comprehensive Internet-connected, distributed, monitoring, control, automation, and data logging system especially designed for greenhouse use. Its de-centralized architecture with Ethernet LAN support and smart input/output modules provide the greatest level of flexibility and extensibility while achieving an unprecedented level of cost-effectiveness.

The iNetGrow system consists of a collection of controllers on the same local area network (LAN), and a collection of input/output (I/O) modules connected to each controller. There are several types of I/O modules (see Components). The distributed and networked architecture makes iNetGrow highly flexible and extensible.

Flexibility

An iNetGrow system is set up using only the I/O modules needed, and only as many modules needed. By selecting different combinations of I/O modules, a vast number of different implementations are possible. Controllers and I/O modules may be freely interchanged as your system requirements change. Moreover, the iNetGrow controllers are networked through the local area network (LAN) over ethernet. Ethernet LAN equipment, such as switches and cabling, are among the most readily available and cost-effective in the history of networking. Since the LAN technology used by iNetGrow is the same used for home and small office networking, many components, such as wireless bridges and access points work with iNetGrow. The latter allow you to network the iNetGrow controllers through wireless devices, reducing wiring costs and susceptibility to lightning, while increasing flexibility.

Extensibility

As your system grows, you simply add more controllers or I/O modules. For example, if you need another input at a certain point, you may choose to simply add another module to the existing controller. If you construct a new wing, you may choose to put another controller with its set of I/O modules dedicated to serve the new wing.

Cost-Effectiveness

The high degree of flexibility and extensibility of the iNetGrow architecture translates into cost-effectiveness. You buy only the type of components you need, only as many as you need, and reuse them as your system demands change.

Architecture

The iNetGrow architecture (see diagram) treats each controller as a peer device with its own IP address on the LAN. Each controller has one or more modules. Each module has several inputs and outputs. A controller and its I/O modules collectively are referred to as a unit. Each unit has the capability to automate its control tasks and log local data. Moreover, any unit is accessible through the LAN using one or more PCs. Each PC may monitor and control the units, log their data, update web pages with information collected from the units, or generate e-mail messages containing data collected from the units. Being on the LAN, any PC may access any unit, provided that the security criteria (e.g. passwords) are met.

Also see the sections Concepts, Architecture and Network Topology, Components, and Frequently Asked Questions.