Agrowtek GCX Controller
Cultivation controller that shares the values of each connected sensor, relay and pump over Modbus TCP.
The Agrowtek GCX is a cultivation controller for greenhouses and indoor farms that runs climate, lighting, irrigation and dosing with GrowNET sensors, relays and pumps. This Modbus TCP template reads the values, output states and inputs of one connected device per unit ID, and lets you set output throttles, force outputs on or off and calibrate sensors from ModbusCloud.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 64, read and write
- Brand
- Agrowtek
- Key readings
- Sensor values per device · Output states · Digital inputs · Device name
- Available commands
- Output throttle · Force output on or off · Sensor calibration
- Compatible models
- GCX · GCX+ · GrowNET devices on a GCX: SXC, SXE, SXW, SXH, PHX, RD8i, VXi, ADi, DXI8 and others
- Last updated
Registers (64)
57 read, 31 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| Integer Value 1 | Read | ||||
| Integer Value 2 | Read | ||||
| Integer Value 3 | Read | ||||
| Integer Value 4 | Read | ||||
| Integer Value 5 | Read | ||||
| Integer Value 6 | Read | ||||
| Integer Value 7 | Read | ||||
| Integer Value 8 | Read | ||||
| Float Value 1 | Read | ||||
| Float Value 2 | Read | ||||
| Float Value 3 | Read | ||||
| Float Value 4 | Read | ||||
| Float Value 5 | Read | ||||
| Float Value 6 | Read | ||||
| Float Value 7 | Read | ||||
| Float Value 8 | Read | ||||
| Output 1 Status | Read | ||||
| Output 2 Status | Read | ||||
| Output 3 Status | Read | ||||
| Output 4 Status | Read | ||||
| Output 5 Status | Read | ||||
| Output 6 Status | Read | ||||
| Output 7 Status | Read | ||||
| Output 8 Status | Read | ||||
| Input 1 | Read | ||||
| Input 2 | Read | ||||
| Input 3 | Read | ||||
| Input 4 | Read | ||||
| Input 5 | Read | ||||
| Input 6 | Read | ||||
| Input 7 | Read | ||||
| Input 8 | Read | ||||
| Throttle Channel 1 | Read and write | ||||
| Throttle Channel 2 | Read and write | ||||
| Throttle Channel 3 | Read and write | ||||
| Throttle Channel 4 | Read and write | ||||
| Throttle Channel 5 | Read and write | ||||
| Throttle Channel 6 | Read and write | ||||
| Throttle Channel 7 | Read and write | ||||
| Throttle Channel 8 | Read and write | ||||
| Output 1 Force Off | Read and write | ||||
| Output 2 Force Off | Read and write | ||||
| Output 3 Force Off | Read and write | ||||
| Output 4 Force Off | Read and write | ||||
| Output 5 Force Off | Read and write | ||||
| Output 6 Force Off | Read and write | ||||
| Output 7 Force Off | Read and write | ||||
| Output 8 Force Off | Read and write | ||||
| Output 1 Force On | Read and write | ||||
| Output 2 Force On | Read and write | ||||
| Output 3 Force On | Read and write | ||||
| Output 4 Force On | Read and write | ||||
| Output 5 Force On | Read and write | ||||
| Output 6 Force On | Read and write | ||||
| Output 7 Force On | Read and write | ||||
| Output 8 Force On | Read and write | ||||
| Offset Calibration 1 | Write | ||||
| Offset Calibration 2 | Write | ||||
| Offset Calibration 3 | Write | ||||
| Offset Calibration 4 | Write | ||||
| Span Calibration 2 | Write | ||||
| Span Calibration 3 | Write | ||||
| Span Calibration 4 | Write | ||||
| Device Name | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Bring the climate, water and output values of a GCX into one ModbusCloud dashboard with your other sites.
- Get an email or webhook when a sensor value on the GCX leaves your band, with one rule for each limit.
- Keep 365 days of history for every GrowNET device on the GCX.
- Force an output on or off from the portal during maintenance and hand it back to automatic afterwards.
- Watch the digital inputs of GCX input modules with a rule on the change condition.
Installation
On the GCX, open the network settings, enable the TCP/IP server and note the IP address. Use port 502 or 4040.
Connect the GCX by Ethernet to the same network as the ModbusCloud Gateway.
Look up the device address of each GrowNET device on the GCX. On a GCX+, add 100 for devices on bus 1.
In ModbusCloud, add one Modbus device per GrowNET device with protocol TCP, the GCX IP address, the port and the device address as unit ID, and import this template.
Rename the values after what they measure on that device and remove the registers it does not have.
Things to watch for
The GCX does not answer on Modbus TCP. What should I check?
Check that the TCP/IP command server is enabled in the GCX network settings and that you use port 502 or 4040 as set there. The GCX must be reachable from the network of the ModbusCloud Gateway; a fixed IP address reserved in the router keeps it at the same address.
Some values give an illegal data address error.
Each device only has the values, outputs and inputs it really has; asking for more returns an illegal data address error. Remove the registers that the device does not use from its Modbus device in ModbusCloud.
Which unit ID belongs to which device?
The unit ID is the device address on the GCX, 1 to 100 on bus 0. On a GCX+ devices on bus 1 use the address plus 100, so address 20 on bus 1 is unit ID 120. Unit IDs from 201 hold control functions and recipes, which this template does not cover.
How do I switch an output from ModbusCloud?
Write 1 to the Force On or Force Off coil of that output; setting one clears the other. Write 0 to both to return the output to automatic. A throttle above 0 also puts the channel in manual on, and 0 is not accepted there. Writing is off per gateway by default; request it for the gateway in the portal.
Why are some values much too large?
The whole-number values are scaled per device type: temperature and pH by 100, humidity by 10. The floating-point values carry the real reading, so use those on your dashboards.
Want to see how it works?
