Recipes, dosing logs, alarms and remote access are part of the controller. Buy a unit and you can run it for its service life without paying for a licence.
Per crop, per block, per stage. Change the recipe and the loop re-settles in about half a minute — that is a hardware property, but the software is what makes it repeatable.
Every dosing event and every EC/pH reading is stored. When a block underperforms, the log is what separates a dosing fault from a root-zone problem.
Sensor drift, motor overload, closed limit switch, communications loss. One list for the head, the valves and the vents, instead of four panels with four buzzers.
Android, iOS, WeChat and a browser, over 4G or the site LAN. Enough for commissioning by video and for a weekly check from another country.
The cabinet controller holds the recipes and the rules. A 7-inch touchscreen on site, 4G and Ethernet to the outside.
A site computer running Android or Ubuntu when the project needs local logic, a local database, or a protocol bridge to equipment we did not supply.
Multi-site dashboards and notifications are optional. The rules that protect the crop do not depend on the connection being up.
Everything the software talks to is documented: Modbus RTU on RS485, MQTT for telemetry, LoRa for battery nodes, 4G or Ethernet for the uplink. A distributor who wants to integrate with an existing SCADA system does not need our permission.
Records are stored on the gateway on site. Cloud synchronisation is an option, not a condition of use.
A 20-minute screen share covers recipes, the dosing log and the alarm list — in your language, on a unit we already shipped.