Cellular Modbus data logger

Several RS485 Modbus sensors, a site with no network, and a need for the readings somewhere other than the sensor display. Genesis polls the sensors on the bus, stores each reading with its time, and sends them over 4G-LTE to a cloud with alerts, Excel export and a REST API.

What it does with a Modbus bus

Polls every sensor on the bus

RS485 sensors share one twisted pair, each on its own address. The controller reads each one in turn at the interval you set, with the sensor rail switched on only while it reads.

Keeps the record whole

Each reading is stored with the time from the on-board clock and sent in order on the next successful transmission, so a coverage gap delays the data rather than losing it.

Reports a dead sensor as dead

A sensor that stops answering its address is reported as a fault, not as a frozen last value or a zero that looks like a measurement.

What matters for this job

BusRS485 Modbus RTU, multi-drop by address, on any of the four ports
Default serial setting9600 bps, 8N1
Sensor powerSwitched 5 V or 12 V, applied per reading cycle
Link4G-LTE by default, Wi-Fi 2.4 GHz where a site network exists
PowerDual 18650 Li-ion, rechargeable, with a 6 to 32 V DC input for solar or a fixed supply
Offline bufferingReadings held locally and backfilled in order

Setting it up

Give each sensor its own address

Before the sensors go on one bus, set a unique Modbus address on each, from its own menu or by a write to its address register. Two sensors on the same address corrupt each other.

Wire A to A and B to B

Use shielded twisted pair. On long runs or busy buses, fit a 120 Ω termination at the far end and power the sensors locally.

Assign the port and the intervals

In the dashboard, set the port to RS485, add the sensors, and set how often to read and how often to transmit. Both can be changed later without a site visit.

Set the alerts

Minimum and maximum per sensor, with notifications to the people who act on them.

What to check before you order

The sensor has to be supported

Over fifty sensor types are supported today. A Modbus instrument that is not on the list yet is added on request from its register map.

It is a logger, not a transparent gateway

It reads defined values from defined sensors. If you need raw Modbus frames tunnelled to your own master over the network, that is a different product.

Related

Frequently asked questions

How many Modbus sensors can one unit read?

They share the bus by address, so several sensors sit on one cable. The practical limit is the number of addresses, the cable length and the time each read takes within your reading interval. Tell us the sensors and the interval and we confirm it.

Can it read my existing energy meter or flow meter?

If it speaks RS485 Modbus RTU, yes. If its model is not supported yet, send the register map and we add it.

Where does the data go?

To OmniCloud, where it is charted, alerted on and exported to Excel, and from where a REST API with scoped tokens serves it to your own systems.

Does it need a gateway?

No. The cellular modem is built in, so the unit connects on its own wherever there is coverage.

Tell us what needs reading

The sensors, how many points, where they sit, and whether there is power and coverage. We come back with whether the ports cover it and what the installation looks like.

Talk to us →