Frequently Asked Questions

 

What is the minimum iNetGrow system I can construct?

You need at least one controller and one I/O module.  For example, with a controller and a TRHIO module, you can monitor temperature and relative humidity at two different spots, read two digital inputs and activate two digital outputs.  A typical application is where the outputs are connected to fans and where a simple thermostat-type control scheme is programmed into the controller to keep the greenhouse at the desired temperature.

 

Do I need a PC?

A PC is needed to initialize the controllers and the I/O modules.  This includes programming the modules for automated control tasks and for data logging.  Once programmed, the controllers can be run without a PC.  However, a PC is highly useful to monitor and override the control of the system, and to observe the logged data.

 

Can I use a wireless network?

The iNetGrow controllers work over an Ethernet LAN.  You may use wireless access points and wireless bridges to connect the controllers to your network, using the same hardware readily available for home and office networking.  In fact, this approach is recommended in cases where wiring is difficult, or where the danger of lightning is relatively high.  The I/O modules are connected to the controllers by wire.

 

How many I/O modules can I connect to a single controller?

Each controller has four (4) sockets.  Up to four (4) I/O modules may be daisy-chained and connected to a controller socket.  This allows up to 16 I/O modules to be connected to a single controller.  A controller can typically supply power to four to six I/O modules.  You may need to use additional power supplies for systems where a large number of I/O modules are connected to a single controller.  A power supply connected to an I/O module supplies power to that module and all downstream modules in that chain.

 

How often does the controller program update its outputs?

When programmed to do so, a controller polls its inputs, then computes and updates its outputs about once every five (5) to ten (10) seconds.  The exact time depends on its workload, that is, other tasks currently being conducted.  These include data logging activities or supplying data to remote PCs.

 

 

 


© Rigel Corporation iNetGrow 2003-2006.  All rights reserved.