A boiler house is visited when it has already locked out. A controller reports temperatures, pressure, burner state and the gas detectors in the room, so the lockout arrives as a message with its history attached.
The lockout contact gives the moment. Temperatures and pressure from the minutes before give the reason, or at least rule several out.
Burner starts per hour, over weeks, show a boiler that is oversized for its load or badly set up. Nobody standing in the room for ten minutes can see that.
Carbon monoxide and fuel gas detectors in the boiler room report on the same record, while their own relays act locally.
A starting list, not a fixed kit. The ports are set from the dashboard, so the same controller takes a different mix of sensors on a different model.
| Signal | How it is read | What it tells you |
|---|---|---|
| Flow and return temperature | 1-Wire or PT1000 probes | Output, and how the load changes through the day |
| System pressure | Analogue pressure transducer | Loss of pressure before the low pressure cut-out |
| Burner run | Dry contact on a digital input | Run hours and starts per hour |
| Lockout | Dry contact on a digital input | A lockout, the moment it happens |
| Carbon monoxide and fuel gas | Fixed gas detectors over RS485 | The state of the room, on the same record |
| Boiler controller | RS485 Modbus RTU, from your register map | Setpoints, states and fault codes |
Four ports on one controller, and RS485 devices share a bus, so most of this list fits on a single unit.
One machine reporting is a gadget. Every machine you have shipped reporting to the same place is a service business.
Each machine reports to the same cloud. Your service desk sees which units are running, which are in alarm and which have gone quiet, before the customer calls.
Accounts nest: you sit above your dealers, and each dealer above its customers. A parent account cannot grant more than it holds, and a unit can be shared with a service company without handing over a login.
Readings and events are stored with their time and export to Excel, for a warranty claim, a service report or a disagreement about what happened and when.
A REST API with scoped tokens covers what the dashboard covers, so fleet data can feed your service system, your ERP or your customer portal directly.
The controller takes 6 to 32 V DC, so it runs from a 12 or 24 V supply already on the machine. Its internal rechargeable battery keeps it reporting after the machine loses power, which is when the reading matters most.
It connects over 4G-LTE from wherever the machine is installed. There are no Wi-Fi credentials to collect and no IT department to convince at each customer.
If the machine already has a controller with an RS485 Modbus RTU port, give us its register map and we add it as a supported device. Its values and alarms then arrive alongside the sensor readings.
The web dashboard is served on your domain with your name, logo and colours, and the iOS and Android apps are published under your own developer accounts. Your customers log in to your product.
Readings are held on the device while the network is down and sent in order when it returns, so the record has no gap where the incident was.
No. The detector's own relays trip the fan, the valve or the siren locally. The controller adds the record and the remote alert on top.
Yes, from the burner run contact. Starts per hour over time is the figure that shows short cycling.
Either. Every controller comes with OmniCloud included, and the REST API does what the dashboard does if you would rather build your own front end on top of it.
The supply voltage available on the machine, the signals you want reported, the register map if the machine has a Modbus controller, and how your dealers and customers should be separated. A first batch on machines already in the field is the usual way to begin.
Over the air, by cellular. Where there is no network at all, the unit raises its own Wi-Fi access point and takes the update from a phone or laptop beside it.
What it is, what you want it to report, and who needs to see which units. We come back with how the controller wires in and how the accounts would be laid out.
Talk to us →