Skip to content

See every Modbus device.
On one dashboard.

A gateway on your network reads your flow meters, drives and sensors, whether they speak Modbus RTU or Modbus TCP. You see every reading on one dashboard and get the alert on your phone when one drifts.

Nothing opened up
one encrypted connection out
RTU and TCP
one gateway reads both
Alerts included
the right person is told first
Silosweight
Conveyorsspeed · rate · totaliser
Motorsrpm · power · temperature
Water pumpsflowRate · pressure · power
Scalesweight · stability
Flow metersinstantFlow · totalFlow
Weigh binsweight · isOpen
Check weighersweight · count
A pressure gauge and pipe fittings on a pump skid inside a plant
4.2 barPump 2 discharge
A gateway reads the pressure transmitter over Modbus and sends each reading out over one encrypted connection. Nothing is written back, and nothing on the skid opens a port.

Every Modbus device on one list.

Flow Meter 12 reports 41.2 m³/h. The gateway reads it the same way it reads a drive, a scale or a sensor, whether the device speaks Modbus RTU or Modbus TCP.

  • One dashboard for every deviceFlow meters, drives, scales and sensors, all on the same screen.
  • Know when one driftsSet a limit on any value. The right person gets the reading before the line stops.
  • Nothing on the internetThe gateway sends readings out over one encrypted connection. Nothing comes in.
LogableJD
Dashboards /Modbus DevicesLiveSave
Flow Meter 12
TimeinstantFlowtotalFlow
09:4141.21 284.1
09:4041.01 283.4
09:3941.31 282.7
Transfer Pump 3
180L/min

Devices that already speak Modbus

Each type comes with the metrics and dashboard widgets already set up. Add a device and it just works.

A silo running low books its own delivery.

Fill level and weight, on the same dashboard as everything else.

A stopped belt does not wait to be found.

Belt scale throughput, belt speed and a running total.

A drive tells you before it trips.

RPM, power draw, temperature and run status.

A pump running against a closed valve says so.

Flow rate, pressure, power and efficiency.

Every load is weighed on the way out.

Weight, with stability and calibration state.

A line losing flow is caught before the tank runs dry.

Instantaneous and total flow, with direction.

A batch that misses its target is caught on the shift.

Batch weighing, with the open and close state.

An underweight pack is caught at the line, not at the depot.

In-motion weighing and count verification.

What comes back from a register

The gateway maps registers to named values with units, so a dashboard shows flow rate and temperature rather than register 40001.

ReadingUnitWhat it tells youWhere it comes from
Instantaneous flowL/minwhether the line is moving what it shouldthe meter's holding register
Total flowLwhat actually moved this shiftthe meter's own totaliser
Discharge pressurebara blockage or a closed valvethe pressure transmitter on the skid
Drive speedrpma drive slowed or stoppedthe VFD's Modbus register
Weightkgthe load on the platformthe indicator's serial output

From the meter to the phone

A gateway on your own network reads every Modbus device, serial or Ethernet, and sends each reading to Logable over one encrypted connection. The device never touches the internet.

  1. Flow meterRS-485 · Unit 12
    Pump driveEthernet · Unit 1
  2. Modbus RTU
    Modbus TCP
  3. GatewayPolls · Publishes
  4. MQTT, encrypted
  5. Logable CloudOne dashboard

One gateway handles both wiring types, so a new flow meter or drive is wired to the gateway, not connected to Logable a second way.

One gateway, both protocols

ProtocolHow it reaches LogableNotes
MQTTDirect to LogableThe gateway publishes every reading to Logable over MQTT with TLS.
HTTPSDirect to LogableA gateway can post the same readings to the Logable API instead.
Modbus RTUThrough a gatewaySerial devices on RS-485 are polled by the gateway on your own network.
Modbus TCPThrough a gatewayEthernet devices are polled by the same gateway. Logable never speaks Modbus itself.

A gateway on your own network polls RS-485 and Ethernet devices at the interval you set and publishes upward over one encrypted connection. See how to connect a PLC or a Modbus device via a gateway.

Every Modbus device on one screen

Flow meters, drives, scales and sensors on the same dashboard, updating as each poll lands.

LogableJD
A Logable dashboard showing two silo levels and a weigh bin's fill percentage

RTU or TCP, the gateway reads it. You never touch the wiring.

Add a flow meter, a drive or a sensor and the same gateway picks it up. Nothing changes on your network.

A limit on any register

Four rules cover what a Modbus fleet reports going wrong.

  • Low flow

    Tells you when flow drops to the low threshold you set on this meter.

  • Over pressure

    Tells you when discharge pressure reaches 90 % of the pump’s rated maximum.

  • Belt stopped

    Tells you when the belt stops moving. Only add this to a belt that is meant to run continuously. It will also fire on planned stops.

  • Not reporting

    Tells you when this device stops sending data, and again when it comes back.

The reading, wherever you are.

Flow Meter 12 falls to 8.4 L/min at 03:40. The push carries the device and the value, so the decision is made before anyone drives out.

  • One dashboard for every deviceFlow meters, drives, scales and sensors, all on the same screen.
  • Know when one driftsSet a limit on any value. The right person gets the reading before the line stops.
  • Nothing on the internetThe gateway sends readings out over one encrypted connection. Nothing comes in.
The Logable app's active alerts, with Acknowledge and Resolve buttons
LogablenowFlow Meter 12 flowing below its low limitFlow Meter 12 · 8.4 L/min, below the 20 L/min limit

What goes wrong on a Modbus fleet

Three failures a serial loop cannot tell anyone about on its own.

What happensWhat you see todayWhat Logable does
A line loses flow overnight.The tank is found empty in the morning.The low-flow alert fires when the meter drops under its limit.Low flow
A pump runs against a closed valve.The seal fails before anyone reads the gauge.A phone alert carries the over-pressure reading.Over pressure
A gateway loses power.Every dashboard on that loop quietly stops moving.The not-reporting alert names each device that went silent.Not reporting

Modbus RTU vs Modbus TCP

Both protocols are fully supported through IoT gateways. Here is how they compare.

Modbus RTUModbus TCP
Physical LayerRS-485 serial (wired)Ethernet / Wi-Fi
SpeedUp to 115.2 kbps10/100/1000 Mbps
DistanceUp to 1,200m (RS-485)Standard network reach
AddressingEach device has its own addressIP address, plus each device's own address
Common UseLegacy devices, field instrumentsModern PLCs, VFDs, meters

What you get with Modbus monitoring

The dashboard, the alerts and the phone, on top of the devices you already have.

Charts and gauges update the moment a new value arrives from the gateway. Build the layout you need with the dashboard builder.
Set a limit on any reading. The right person gets it by push, email or the inbox before the line stops.
The gateway sends readings out over one encrypted connection. No inbound firewall ports, on any device.
Flow rate, weight, RPM and temperature, not raw register numbers. Each device type comes mapped already.

What it costs

One gateway can serve a whole RS-485 loop. You pay for the devices you watch.

The trial runs 14 days with 5 devices and Growth features, and asks for no card. Industry plans are quoted per site.

The gateway is bought once from your supplier and is not a Logable cost.

See pricing in your currency

Frequently asked questions

What teams ask before they connect the first device.

Modbus connectivity is handled through IoT gateways, not built directly into the Logable platform. The gateway reads values from your Modbus devices and sends the data to Logable over MQTT. For other data, Logable also accepts a simple web request.

Start with one gateway and one meter

Connect the first Modbus device today. The dashboard and the alerts are ready when it reports.