Contact us

How it works

From the reading to the confirmed command.

What one Ilonnati controller does, step by step: how often it reports, how it moves a valve, what happens when the power or the link fails, and the alerts and reports that reach the control room.

Reports
Every 10 seconds by default
Valves
0 to 100% open
Each command
Confirmed and recorded
Illustration of a town water system: treatment works, an elevated reservoir, a pump house, the main with motorised valves, homes with meters, and an Ilonnati controller beside each valve and pump.

In the field

  1. Actuator on an existing valve
  2. Ilonnati controller

The chain

Readings go up from the equipment to IoTyX; commands come down, and the controller confirms each one.

How the system connects, from the field to the screenA schematic in five steps, left to right. Equipment in the field, a sensor, a valve, a pump and a meter, is wired to an Ilonnati controller. The controller has a radio link to IoTyX, the platform, which serves a browser, a phone and a control room. Between each step, readings travel toward the screens and commands travel back toward the machine. From the controller onward, a dashed line carries the controller's confirmation back to the screens.Equipment in the fieldIlonnati controllerRadio linkPlatformScreensSensorValvePumpMeterIoTyXOne beside each machineLinks the controllerto the platformRuns the hardware froma browser or a phoneBrowserPhoneControl roomHow the system connects, from the field to the screenEquipment in the fieldSensorValvePumpMeterIlonnati controllerOne beside each machineRadio linkLinks the controllerto the platformIoTyXPlatformRuns the hardware froma browser or a phoneBrowserPhoneControl room
  • Readings travel from the equipment to the screens: levels, flow, pressure and consumption.
  • Commands travel from a screen to the machine: open a valve, start a pump.
  • Confirmation comes back from the controller once a command has happened, and every command is logged.
TitleFrom the field to the screen
ViewSchematic

Step by step

One cycle of a controller beside a valve, as its firmware runs today.

  1. 01

    Readings are taken

    The controller reads every instrument wired to it: flow totals, pressure, quality, levels and the valve’s position, with its own battery voltage, load current and charge.

  2. 02

    A report goes to IoTyX

    One time-stamped report carries all of them. By default it goes every ten seconds; the interval is set per site, and a change takes effect without a restart.

  3. 03

    Anything that moves reports at once

    Beyond the regular interval, the controller reports at start-up, after every command, and whenever a valve moves by more than 1%.

  4. 04

    An operator sends a command

    From IoTyX on the web or a phone, an authorised operator sets a valve anywhere from 0 to 100% open, or starts or stops a pump, and confirms it before it is sent.

  5. 05

    The valve moves, within limits

    The valve is given 60 seconds to reach its position and its motor is stopped at 90, so a valve that sticks is not driven on. Position is measured against the valve’s own learned closed and open points.

  6. 06

    Confirmed, with fresh readings

    The controller reports when the valve arrives, and a fresh set of readings follows, so the screen shows the result. The command is recorded with who sent it and when.

When the power or the link fails

Field sites lose power and signal. This is what the controller does when they do.

  • Power failure

    A backup battery on the board keeps the controller running long enough to report the power failure and send the last data it took.

  • Link lost

    If the mobile link drops, the controller reconnects by itself and reports again. IoTyX raises an alert for any device that goes offline.

Automation

Timed supply, held at the controller

A line is given supply slots, each with a time, a quantity and the days of the week it runs. At the slot’s time the valve opens; when the meter has counted the quantity, it closes. The slots are set from a phone and held at the controller, and the phone shows the flow as it rises and falls.

Example: supply slots on one line

  1. 07:008,000 LSMTWTFS
  2. 16:002,000 LSMTWTFS
  3. 21:306,500 LSMTWTFS

The valve opens at the time and closes when the meter has counted the quantity.

Alerts

Raised in IoTyX and sent by push notification, email and in the app, with thresholds set per sensor.

  • Leak or abnormal flow

    Flow where there should be none, or more than a zone should draw.

  • Tank overflow

    A tank or reservoir passing its high mark.

  • Low chlorine in distribution

    Residual chlorine below its limit at a reservoir or in the network.

  • Filling started late

    A tank whose scheduled filling began later than planned.

  • Device offline

    A controller that has stopped reporting.

  • Dry running

    A pump about to run with too little water to draw.

Control room

Reports

What a water control room on IoTyX cycles through on its screens.

  1. Online reports
  2. Schedule deviation
  3. Monthly reservoir reports
  4. Online faults
  5. Status of each hydraulic zone
  6. Overflow reports
  7. Leakage reports

Tell us what you need to connect, monitor or control

An engineer will reply.