Remote Pump Monitoring
Plan pump run, fault, pressure, flow, current and level signals for remote alarms and multi-site water operations.
Related products
Representative product-family images. The exact model, interfaces and enclosure are confirmed in the written quotation.
Planning this application?
Send the site count, signals, network, power and reporting target. We will return a hardware configuration for quotation.
Why it matters
Pump stations are often far from the control room. A useful remote monitoring design starts with the operating decision: detect loss of flow, confirm a commanded start, identify abnormal current, prevent dry running, or escalate a high wet-well level. The hardware and I/O plan should follow those decisions instead of collecting every available signal.
How it works
- 1Map controller contacts, analog transmitters and Modbus registers into a clear point list.
- 2Connect the point list to remote I/O or a 4G RTU; use LoRaWAN where several low-data field points share one gateway.
- 3Send timestamped values and alarm states to the customer SCADA, dashboard or maintenance workflow.
Hardware used between field signals and the network
Representative product-family images. Exact model, interfaces and enclosure are confirmed in the written quote.
Where the hardware sits in the monitoring path
A planning view, not a fixed bundle. Signal type, protocol, power, network and the customer endpoint are confirmed before quotation.
Customer system
SCADA, BMS or customer-owned platform
Signals worth monitoring
Run / stop feedback
- Field input
- Auxiliary relay or controller dry contact
- Operational purpose
- Confirm the pump actually started or stopped after a command.
Common fault / trip
- Field input
- Dry contact or controller register
- Operational purpose
- Escalate a trip without waiting for the next site visit.
Discharge pressure
- Field input
- 4-20mA pressure transmitter, or a separately reviewed serial transmitter
- Operational purpose
- Detect loss of pressure, blocked discharge or abnormal operating conditions.
Flow
- Field input
- Pulse, 4-20mA or RS485 flow meter
- Operational purpose
- Compare delivered flow with pump state and expected demand.
Show the remaining monitored signals
Compare three deployment architectures
Water-site deployment context
Representative site context. Sensors, interfaces, enclosure, power and mounting are confirmed against the actual project before quotation.
I/O planning checklist
Digital inputs
Run, stop, fault, local/remote, high level, low level and door contacts.
Analog inputs
Signal type, range, loop power, isolation and scaling for pressure, flow or level.
RS485 ports
Device count, register maps, baud/parity groups, polling interval and timeout policy.
Pulse inputs
Pulse value, maximum frequency and whether totalization must survive power loss.
Show the remaining I/O checks
Alarm logic examples
Commanded run but no feedback
Project logic: Start command is active and run feedback remains absent after a project-defined delay.
Operator context: Check panel state, motor protection and communications before repeated restart attempts.
Running with low flow or pressure
Project logic: Run feedback is active while flow or pressure remains below the approved operating threshold.
Operator context: Investigate dry running, blocked suction, valve state, leakage or sensor condition.
High-high level
Project logic: Level crosses the project limit with delay and hysteresis to avoid chatter.
Operator context: Escalate immediately and show whether duty / standby pumps are running.
Show the remaining alarm examples
Related products
View all products →What to include in your quote request
- Pump count, duty / standby sequence and control-panel drawings
- Available contacts, analog signals and controller register maps
- Pressure, flow, level, current and vibration points required
- Country, site count, LTE operator or LoRaWAN coverage plan
- Power source, enclosure, antenna and surge-protection requirements
- Alarm recipients, SCADA / MQTT / API destination and reporting interval
- Pilot quantity, rollout quantity and target commissioning date
Remote integration context
Representative site context. Sensors, interfaces, enclosure, power and mounting are confirmed against the actual project before quotation.
Products used
- 4G/LTE Industrial RTU
- Modular Remote I/O
- Pressure / Flow / Current Sensors
Technologies
- Dry contact
- 4-20mA
- RS485
- Modbus
- LoRaWAN
- 4G LTE
- MQTT
Related solution
Water MonitoringRelated selection guides
Official technical references
FAQ
Can a pump station be monitored without replacing the existing controller?
Yes. A retrofit can read auxiliary contacts, analog transmitters or Modbus registers while the existing controller keeps its control role. The point list and electrical interfaces must be checked before selecting the RTU or remote I/O.
When should a pump project use a 4G RTU instead of LoRaWAN?
A 4G RTU is usually the direct path for one remote station with several I/O points, Modbus devices or local buffering. LoRaWAN is useful when many low-data sensor nodes share gateway coverage. Site topology, power, operator coverage and upstream architecture decide the final path.
Which signals are most useful for dry-run detection?
Run feedback combined with flow, discharge pressure, motor current or source level is more informative than one signal alone. The accepted thresholds and delays must be set from the pump and process operating envelope.
Can SunGene connect pump data to an existing SCADA or maintenance platform?
Yes. The hardware path can be prepared for Modbus TCP, MQTT or another agreed interface. Share the point list, naming convention, security requirements and destination-system responsibility before quotation.
What information is needed for a pump monitoring quote?
Provide the pump and panel count, available I/O, register maps, measured parameters, site power, country and network, enclosure needs, upstream system, alarm workflow, quantity and schedule.