The question usually arrives as "can this replace a PLC", and the honest answer is no. A PLC runs a machine on a deterministic cycle with a safety rating behind it. A cellular IoT controller covers the points a PLC is uneconomic for: distributed, unpowered, outside any panel.
| PLC | Cellular IoT controller | |
|---|---|---|
| Built to | Run a machine or a process cell | Measure, report and switch at distributed points |
| Timing | Deterministic scan cycle | Readings on intervals set from the cloud |
| Logic | IEC 61131-3 programs | Thresholds and simple rules held on the device |
| Safety | Safety-rated variants exist | No safety rating |
| Installation | A panel, mains power and a network | Battery or solar, cellular, no cabinet |
| Where data goes | To a SCADA or HMI on the site network | To a cloud with alerts, export and a REST API |
Interlocks, sequences, motion and anything that protects people or plant belong on a PLC or a safety controller.
A tank at the end of the yard, a pump in an outbuilding, a cold room on another site: points where a panel build costs more than the measurement is worth.
The PLC runs the line. The IoT controller watches the utilities around it and reports to people who are not on the site network.
Genesis reads RS485 Modbus, analogue, I2C and 1-Wire sensors on four ports set from the dashboard, runs on battery and solar, and reports over 4G-LTE. It switches relays and solenoids on rules held on the device.
It is sold for the points between machines. It is not sold as a PLC, and it should not be specified as one.
Where the PLC exposes values on RS485 Modbus RTU, a register map is enough to add it as a supported device.
Simple ones, such as starting a transfer pump on a level, with the rule held on the device. Anything time-critical or safety-related stays on the PLC.
Tell us what has to be measured or switched, where, and what it has to report into. We say which approach fits, including when it is not ours.
Talk to us →