iNetGrow Architecture
The iNetGrow architecture is designed to allow a network of Apopka Controllers to communicate over the LAN with a PC and with each other. In addition Each controller has one or more smart modules. Each module has several inputs and outputs. A controller and its smart I/O modules collectively are referred to as a control unit (see diagram).

Each control unit has the capability to automate its control tasks and log local data. Moreover, any control unit is accessible through the LAN using a PC. 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 control unit, provided that the security criteria (e.g. passwords) are met. PC access is provided through the iNetGrow Software.

The iNetGrow architecture is built using two levels of networking.
The Apopka Controllers are connected through a standard Ethernet LAN. Under each controller, there is a local network, referred to as the mNet, which carries the communications between the controller and the smart I/O modules. The mNet has a multi-drop protocol, which allows smart I/O modules to be daisy-chained. This lower level of networking introduces a tremendous level of flexibility and extensibility. The modules provide a level of generalization that isolates the specific hardware aspects of a module from the controller. The communications over the mNet are in logical messages, not hardware-specific signals. This allows new types of modules to be implemented without having to modify the existing mNet architecture. Similarly, the controllers encapsulate all tasks of a control unit in a manner, which is accessible over the LAN. Once again, control units may freely be added to the LAN without having to consider any hardware-specific aspects. Moreover, LAN messaging is conducted using standard Internet protocols, further simplifying PC access to the control units.