A cabinet leaves your factory and you hear from it again when it fails under warranty. A controller fitted on the line reports its temperature, door, power and compressor load from wherever it ends up, to you, your dealer and the operator, each seeing only their own units.
The operator wants to know before the stock is lost, not after. A probe placed with the load, and not in the return air, is what makes the answer honest.
A warm cabinet with the door open or the power off is not a warranty claim. Door and power state turn an unexplained warm period into an explained one.
A compressor that runs longer each week to hold the same setpoint is saying something. Run current over time shows it before the unit stops.
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 |
|---|---|---|
| Product temperature | 1-Wire or PT1000 probe placed with the load | How long the product actually spent warm |
| Air temperature | A second probe in the return air | How hard the unit is working to hold setpoint |
| Door state | Dry contact on a digital input | Whether an excursion was a fault or an open door |
| Power state | Supply sense on a digital input | Outages, and units unplugged at the outlet |
| Compressor current | Clamp-on current sensor over RS485 | Run time, cycling and rising load |
| Refrigeration controller | RS485 Modbus RTU, from your register map | Setpoint, defrost state and its own alarms |
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 refrigeration controller runs the machine. This controller observes it and reports, and the two sit side by side. Where your controller has a Modbus port, its setpoint, defrost state and alarms are read as well.
With the product, or as close to it as the cabinet allows. Return air warms first and recovers first, so it under-reports how long the load was warm. A second probe in the air stream is still useful, for seeing how hard the unit is working.
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 →