.png)
Wireless Pump Station Monitoring with Dragino and Industrial Sensors
A remote pump station can fail quietly for hours before anyone sees water on the ground, a dry tank, or a fault light. By then, the real cost is not only the repair. It is the travel, lost production, water loss, environmental risk, and the time spent finding out what happened.
Wireless monitoring changes that. A pump station fitted with industrial sensors and Dragino wireless devices can report pressure, flow, tank level, pump run status, power use, and fault alarms from almost anywhere with suitable radio or internet backhaul. Instead of sending staff to check gauges and panels, the site sends data back to operators.
That makes Wireless Pump Station Monitoring with Dragino and Industrial Sensors useful for councils, irrigation schemes, water treatment systems, mine sites, and industrial facilities where assets are spread across large areas.
What a remote pump station should monitor
A useful monitoring system starts with the right measurements. The goal is not to collect every possible signal. The goal is to collect the signals that explain whether the station is running safely, efficiently, and as expected.
Most pump station monitoring projects include these points.
Measurement | What it tells you | Common sensor or signal |
Pressure | Pump discharge pressure, suction pressure, blocked lines, burst mains, low head | 4–20 mA pressure transmitter |
Flow | Pump output, water transfer volume, leakage, no-flow conditions | Pulse output flow meter or Modbus flow meter |
Tank level | Available storage, overflow risk, dry-run protection | 4–20 mA level sensor, ultrasonic sensor, hydrostatic probe |
Pump status | Whether the pump is running, stopped, tripped, or in manual mode | Digital input from contactor, relay, or PLC |
Energy use | kWh, current, voltage, power factor, abnormal load | Modbus energy meter or CT-based meter |
Faults | Motor overload, VSD fault, high level, low level, door open, mains failure | Digital input or Modbus register |
For many sites, these signals already exist in the switchboard or local PLC. The monitoring device does not need to replace the control system. It can sit beside it and read selected signals.
That matters because many pump stations were built years before remote telemetry became affordable. A wireless node can often be added without rebuilding the whole panel.
How Dragino fits into the system
Dragino makes LoRaWAN sensors, I/O controllers, RS485 nodes, and gateways used in long-range, low-power monitoring. In a pump station, a Dragino field device connects to sensors or panel signals. It then sends data wirelessly to a Dragino gateway or an existing LoRaWAN network.
From there, the gateway forwards the data to a server, cloud platform, SCADA system, or dashboard over Ethernet, 4G, Wi-Fi, or another available backhaul.
A simple architecture looks like this:
Industrial sensors measure the process
Pressure transmitters, flow meters, tank level sensors, energy meters, and fault relays provide electrical signals.
A Dragino wireless controller reads the signals
The controller accepts analogue, pulse, digital, or RS485 inputs, depending on the model and wiring.
Data travels by LoRaWAN
LoRaWAN suits low data rates over long distances, especially where buried cables or fixed internet are not practical.
A gateway forwards the data
The gateway receives radio packets and sends them to the chosen application or network server.
Operators view alarms and trends
The data becomes live values, trend charts, fault messages, and reports.
This setup works well when the system needs periodic readings, event alarms, and status updates. It is not intended for high-speed closed-loop control. The pump control should still remain local, using the PLC, VSD, pressure switch, float switch, or dedicated controls designed for safe operation.
Connecting 4–20 mA sensors
The 4–20 mA current loop is one of the most common industrial signal types. It is widely used because it tolerates electrical noise and voltage drop better than many voltage signals.
In pump stations, 4–20 mA is commonly used for:
Discharge pressure
Suction pressure
Tank level
Bore level
Chemical tank level
Differential pressure
Analogue flow output
A typical pressure sensor might output 4 mA at 0 kPa and 20 mA at the top of its range. A tank level sensor might output 4 mA when empty and 20 mA when full.
When connecting a 4–20 mA transmitter to a Dragino analogue input device, check three things before wiring.
Power supply
Many industrial transmitters need 12 to 24 V DC loop power. Some wireless sensor nodes can power a sensor for short sampling periods, while others may need an external DC supply. For a pump station with mains power, the panel supply is often available. For a solar site, sensor power budget matters.
Input type
Confirm whether the Dragino input accepts current directly or needs a shunt resistor to convert current to voltage. This affects accuracy and wiring.
Scaling
The raw signal must be scaled into engineering units. For example, 4–20 mA may become 0 to 1,000 kPa, or 0 to 5 m tank level. Good scaling makes dashboards readable and alarms meaningful.
It is also wise to set fault limits. A reading below 4 mA may indicate a broken wire or failed sensor. A reading above 20 mA may indicate over-range or wiring trouble.
Connecting pulse signals from flow meters
Pulse outputs are common on mechanical, magnetic, and ultrasonic flow meters. Each pulse represents a fixed volume, such as one litre, ten litres, or one kilolitre, depending on the meter configuration.
A Dragino pulse input or digital counter can record these pulses and send totals or flow rates at set intervals.
Pulse monitoring is useful when the key question is:
How much water has been pumped today?
Is flow present when the pump is running?
Has a transfer target been met?
Is there unexpected flow when the pump should be off?
Are two pumps producing different volumes?
There are two common ways to use pulse data.
Totalised volume
The controller counts pulses over time. If one pulse equals 10 litres, then 1,000 pulses equals 10,000 litres. This is useful for daily transfer totals, bore extraction reporting, irrigation allocation, or chemical dosing checks.
Calculated flow rate
The system calculates flow by counting pulses within a time window. This can show approximate L/s or m³/h. The result is useful for trends and alarms, but accuracy depends on pulse frequency and reporting interval.
Low-flow systems may produce pulses slowly, so short intervals can look uneven. High-flow systems need inputs that can handle the pulse rate. The flow meter data sheet should be checked before selecting the wireless input device.
Pulse wiring also needs care. Flow meters may provide dry contact, reed switch, open collector, NPN, PNP, or powered pulse outputs. The input must match the pulse type, or use an interface relay or signal conditioner.
Connecting Modbus devices over RS485
Many modern pump stations already have smart meters and drives that speak Modbus RTU over RS485. This is often the best way to collect detailed data without adding more sensors.
Common Modbus devices include:
VSDs
Energy meters
Magnetic flow meters
Smart pressure transmitters
Pump protection relays
PLCs
Water quality analysers
A Dragino RS485 or Modbus wireless node can poll selected registers and send the values over LoRaWAN. This can reduce wiring because several values come from one cable.
For example, one energy meter may provide:
Voltage per phase
Current per phase
kW
kWh
Power factor
Frequency
Demand
A VSD may provide:
Run status
Speed
Output current
Fault code
Motor load
Drive temperature
Start and stop history, depending on the model
Modbus is powerful, but it needs clear setup. The key settings must match across all devices on the bus.
Setting | What to confirm |
Slave address | Each Modbus device needs a unique address |
Baud rate | Common values include 9,600 or 19,200 bps, but the site must match |
Parity and stop bits | These must be the same across the network |
Register map | The correct register numbers and data formats are needed |
Polling interval | Longer intervals reduce radio traffic and power use |
Cable and termination | RS485 needs suitable twisted pair cabling and correct termination on longer runs |
Register mapping is where many jobs slow down. The device manual may list registers using different numbering styles. Data may be signed, unsigned, 16-bit, 32-bit, integer, or floating point. A short bench test before site work saves time.
Connecting digital status and fault signals
Digital inputs are the simplest and often the most valuable part of a pump monitoring system. A digital input reports an on or off state. It can come from a relay, auxiliary contact, float switch, pressure switch, door switch, or PLC output.
Typical digital inputs include:
Pump running
Pump failed
Auto or manual mode
High tank level
Low tank level
Low suction pressure
Motor overload
VSD fault
Mains power fail
Generator running
Cabinet door open
Emergency stop active
These signals are easy to understand and make good alarms. If a pump trips at 2 am, operators do not need to wait for a routine inspection. They can receive an alert and decide whether the issue needs an immediate callout.
Dry contacts are often preferred because they provide electrical separation between the pump control circuit and the monitoring device. If the signal is powered, confirm the voltage and whether the Dragino input expects wet contact, dry contact, sinking, or sourcing input.
Digital outputs can also be useful, but they should be treated carefully. A wireless output might reset an alarm, turn on a beacon, or enable a non-critical function. It should not become the only safety control for a pump or tank. Critical interlocks belong in local hardwired controls.
Turning readings into alarms that help
Collecting data is only half the job. The system also needs sensible alarm rules. Too many alarms cause people to ignore them. Too few alarms leave faults hidden.
Good alarm design starts with clear conditions.
For pressure:
Low discharge pressure while the pump is running may indicate no water, failed impeller, valve issue, or burst pipe.
High discharge pressure may indicate a closed valve, blockage, or downstream restriction.
Low suction pressure may indicate a dry bore, blocked strainer, or empty supply tank.
For flow:
Pump running with no flow can suggest dry running, air lock, closed valve, or failed pump.
Flow while the pump is off can suggest leakage, siphoning, or a valve passing.
Flow below expected range can show wear, blockage, or low suction level.
For tank level:
High level can warn of overflow risk.
Low level can protect downstream supply or stop dry running.
Rate of change can show whether inflow or outflow is abnormal.
For energy:
Rising current at the same flow may suggest a mechanical problem.
Low current while running may suggest loss of prime or no load.
High kWh per kilolitre can point to poor pump efficiency, blocked filters, or incorrect operating pressure.
The best systems combine signals. A single low-pressure alarm is useful. A low-pressure alarm with pump running, low current, and no flow gives a clearer fault picture.
Power and communications at remote sites
Remote pump stations often have limited services. Some have mains power and mobile coverage. Others run from solar and sit outside reliable mobile range.
LoRaWAN suits many remote monitoring jobs because field devices can send small packets over long distances using low power. The actual range depends on terrain, antenna height, vegetation, buildings, and radio noise. A clear line of sight and a well-mounted antenna can make a major difference.
A Dragino gateway can be installed where it has both radio coverage to the pump stations and backhaul to the internet or site network. In a council or irrigation scheme, one gateway may cover several nearby assets if the terrain suits it. In a mining or industrial facility, gateways may be placed around the site to cover tanks, sumps, pipelines, and transfer stations.
For solar-powered installations, design around energy use. The main loads are sensors, the controller, radio transmissions, and any backhaul equipment. Analogue sensors that stay powered all day may use far more energy than a LoRaWAN node that wakes up, samples, transmits, and sleeps.
Where this approach is used
Wireless pump monitoring is not limited to one industry. The same signal types appear across many assets.
Councils and utilities
Councils can monitor sewer pump stations, stormwater pumps, potable water booster stations, reservoirs, and recycled water systems. Live alarms reduce inspection runs and help crews respond before overflows, low-pressure complaints, or storage issues grow.
Irrigation
Irrigation operators can track bore pumps, channel pumps, dam transfers, filter stations, and fertigation systems. Flow totals support allocation records, while pressure and energy trends help find blocked filters, leaks, and pump wear.
Water treatment
Treatment plants often use pumps for raw water, backwash, dosing, transfer, and wastewater handling. Wireless nodes can extend visibility to package plants, remote tanks, and small assets not connected to the main SCADA network.
Mining
Mine sites use pumps for dewatering, process water, tailings, dust suppression, and washdown. Wireless monitoring helps teams see remote assets without running long cable routes through difficult ground.
Industrial facilities
Factories, food processors, quarries, and logistics sites often have sumps, cooling water pumps, fire water tanks, and trade waste systems. Monitoring the right signals can reduce downtime and protect equipment.
Practical design checks before installation
A reliable system starts before the equipment is mounted. The site survey should answer a few practical questions.
Which measurements are already available in the panel?
Which new sensors are needed?
Are signals analogue, pulse, Modbus, or digital?
Is there 24 V DC power available?
Is the site mains, battery, or solar powered?
Where can the antenna be mounted safely?
Is there LoRaWAN coverage, or is a new gateway required?
How often should each value report?
Which alarms need immediate messages?
Who responds to each alarm?
It also helps to label every signal clearly. A dashboard tag called `Pump 1 Fault` is useful. A tag called `DI_03` is not. Good names reduce mistakes during callouts.
Earthing and surge protection deserve attention too. Pump stations often have long cable runs, motors, lightning exposure, and wet environments. Use suitable enclosures, glands, isolation, and protection devices for the site conditions. Follow Australian electrical requirements and use licensed trades where required.
What success looks like
A good remote monitoring system does not bury operators in data. It gives enough information to make the next decision.
If the pump is running, operators can see pressure, flow, level, and power. If it stops, they can see whether it was a planned stop, a level control action, a power issue, or a fault. If performance changes over weeks, they can compare trends and plan maintenance before failure.
Dragino wireless controllers and gateways make this practical for scattered pump assets because they can connect to the industrial signals already used in the field: 4–20 mA, pulse, Modbus, and digital contacts. Pair them with the right sensors, sensible alarms, and clear dashboards, and remote pump stations become visible assets rather than unknown risks.
