跳转至主要内容
跳转至主要内容
LoRaWAN SCADA

LoRaWAN SCADA: wireless sensors in your SCADA, from the field to the dashboard

LoRaWAN sensors
Gateways
Network server
Cloud Studio platform logoSCADA / IoT platform
Dashboards and alarms

How to bring battery-powered LoRaWAN sensors into a SCADA: the architecture, what LoRaWAN is good at, where wired SCADA still wins, and how to connect network servers such as TTN, ChirpStack, Actility or LORIOT.

What is LoRaWAN SCADA?

A LoRaWAN SCADA is a supervisory system whose field data comes from LoRaWAN sensors instead of, or alongside, wired PLCs and RTUs. Battery-powered sensors report every few minutes over kilometres of radio to a gateway; a network server decodes the data and hands it to the SCADA, which draws the dashboards, raises alarms and keeps the history. It is built for monitoring many spread-out points cheaply, not for fast closed-loop control.

Long range, years on batteries

LoRa radio reaches several kilometres in cities and more in open terrain, and sensors that report every few minutes run for years on batteries. That removes trenches and cabling for points that are far apart.

Small payloads, minutes not milliseconds

Each uplink carries a few dozen bytes, and radio duty-cycle rules (1% in most EU868 sub-bands) limit how often a device can talk. Readings every 5 to 15 minutes are typical; alarms can be sent at once when a threshold is crossed.

The network server decodes

Gateways only relay radio packets. The network server (TTN, ChirpStack, Actility ThingPark, LORIOT) authenticates devices, removes duplicates and runs the payload decoder that turns bytes into values such as temperature or level.

The SCADA supervises

The SCADA or IoT platform receives decoded values over MQTT or HTTP, shows them on synoptics and maps, raises and escalates alarms, stores history and reports, and can mix them with Modbus and OPC UA data from the plant.

Wired SCADA vs LoRaWAN SCADA

They solve different problems, and most projects end up using both.

Attribute
Wired SCADA (PLC, RTU)
LoRaWAN SCADA
Update rate
Sub-second polling
Every few minutes, alarms on change
Control
Closed-loop control and interlocks
Monitoring; occasional commands with seconds of latency
Installation
Cabling, cabinets, power at each point
Battery sensors, no cabling to each point
Distance
Limited by the cable or the fieldbus
Kilometres to the nearest gateway
Cost per point
High for remote or scattered points
Low: sensor plus a share of a gateway
Best for
Process control inside a plant
Tanks, meters, pumps and assets spread over a territory
The key difference

Keep control loops on wired PLCs and use LoRaWAN to see everything the cables never reached.

The LoRaWAN SCADA architecture

Five layers, each with a clear job. Choosing well at each one avoids most surprises in the field.

01

Sensors and converters

Measure in the field

Level, pressure, temperature, flow and energy sensors report on their own. Existing equipment joins through converters: a 4-20 mA or Modbus RS485 to LoRaWAN node reads the instrument and sends its values over radio.

Supported protocols
LoRaWAN Class AClass C4-20 mAModbus RS485

LoRaWAN SCADA with Cloud Studio IoT

A web SCADA built for LoRaWAN from the start, with the plant protocols on the same screens.

Decoders and custom drivers

A library of device codecs, and engineers who write the driver or dashboard you are missing.

Many sites, many clients

Organized by sites and client portals, with white label for integrators who resell the platform.

Network servers and plant protocols

Ready-made integrations with Actility, ChirpStack, TTN, LORIOT and Helium, direct MQTT, and Modbus TCP/RTU or OPC UA through a software gateway installed at the edge.

Monthly, from €100

From €100 a month for 50 devices, or €550 a month on a dedicated server; on-premise when data must stay in-house.

LoRaWAN SCADA: frequently asked questions

Short answers to the questions integrators and operators ask most.

LoRaWAN SCADA

Bring your remote sites into one SCADA

Start with a pilot of up to 50 devices and grow site by site.

Talk to an engineer