Cellular Gateway Retrofit: Connect Existing Pump-Off Controllers to SCADA
Key Takeaway
A cellular gateway retrofit polls existing pump-off controllers over Modbus and publishes tags to cloud or on-prem SCADA without replacing the pumping unit. Ideal for stripper fleets that already own Lufkin, Weatherford, or Unico POCs but lack telemetry.
Quick Answer
If the rod pump already has a pump-off controller, you usually do not need a new lift package to get SCADA — you need a cellular (or radio) gateway that speaks Modbus to the POC and MQTT/HTTPS/Modbus TCP to the host. That retrofit is often the cheapest path to POC SCADA integration and fewer truck rolls. Broader options: cellular vs radio vs satellite.
When a gateway retrofit fits
- POC is healthy; problem is visibility, not the pumping unit.
- Power exists (AC or adequately sized solar + battery).
- LTE (or scheduled radio) reaches the lease.
- Budget favors opex cellular over full pad redesign — see cost guide add-on ranges.
Skip the gateway-only approach when the POC is obsolete without a usable map, power cannot support a modem, or you need pad-wide facility control — then use a pad PLC/RTU architecture instead.
Retrofit steps
- Identify POC brand/firmware and obtain the Modbus register map.
- Confirm serial settings (RS-485, baud, parity) or Ethernet port.
- Install gateway in Div-appropriate enclosure ( classified panel guidance).
- Map load, SPM, fillage, status, faults; throttle dyno-card uploads.
- Point the gateway at Ignition, Geo SCADA, or hosted SCADA with certificates and firewall rules.
- Commission alarms and local/remote behavior; verify POC still controls pump-off if the WAN dies.
Common failure modes
- Wrong register map / byte order → nonsense fillage and loads.
- Polling dyno cards every second → blown cellular data caps.
- No surge/grounding on lease power → random gateway deaths.
- Alarm spam → pumpers disable notifications and drive routes again.
Site survey before you order hardware
Most failed retrofits were decided before any equipment arrived. Capture these facts per well first:
| Item to verify | Why it decides the design |
|---|---|
| Controller make, model, and firmware revision | Register maps differ between firmware generations of the same model |
| Available communication port (RS-485, RS-232, Ethernet) | Determines gateway model and wiring |
| Existing port already in use | A port serving a local display may not be shareable |
| Power source and spare capacity | A modem added to a marginal solar system browns out in winter |
| Area classification at the mounting location | Drives enclosure cost more than the gateway itself |
| Measured signal strength at the panel, not the road | Coverage at the gate does not prove coverage inside steel |
| Grounding and surge protection condition | Lease power quality kills unprotected electronics |
Gateway versus pad controller
A standalone gateway is the right answer for a scattered single well with one controller. It is the wrong answer once a site has several wells, facility equipment, or interlocks. Decide on scope, not on price alone:
- Gateway: one or two serial devices, no local control requirements, no facility I/O.
- Pad controller: multiple lift controllers, separator or tank I/O, interlocks, and a single shared backhaul — the architecture in well pad automation.
Retrofitting six gateways onto one pad usually costs more in modems, data plans, and support than one controller with a single backhaul.
Security basics people skip
A cellular gateway is an internet-facing device attached to production equipment. Minimum hygiene:
- Change default credentials on every device; do not reuse one password across the fleet.
- Disable unused services and remote administration interfaces.
- Prefer outbound-initiated connections over inbound port forwarding to field devices.
- Use a private APN or VPN where the carrier and budget allow.
- Keep an inventory of deployed firmware so a vulnerability announcement does not require a field survey to scope.
- Restrict write access to setpoints by role, and log every change.
These are the field-level expression of the practices covered in the OT cybersecurity for oil and gas material.
Proving the retrofit worked
Close the loop before calling the well complete. Compare a host value against the controller's own display for load, fillage, and strokes per minute. Pull the antenna and confirm the pump keeps running while the host flags stale data. Force a pump-off event and confirm both the event and any card upload arrive as configured. Check the first month of data usage against the plan so card polling is corrected before it becomes a recurring overage. Finally, walk the screen with the pumper — a retrofit that produces data nobody uses has not reduced a single truck roll.
How NFM Consulting helps
NFM Consulting supplies and commissions POC-to-SCADA cellular gateway retrofits for Texas rod-pump fleets, including register mapping and host screens. Request an assessment or call (210) 405-4248.
Need help with oil & gas field automation?
Texas-based licensed engineers — get a free, no-obligation assessment.
Frequently Asked Questions
Yes, if the POC has a documented Modbus (or similar) map and the site has power plus coverage. A cellular gateway polls the POC and publishes tags to your SCADA host without replacing the pumping unit.
Often in the roughly $8,000–25,000 per well range when the POC already exists, depending on enclosure classification, solar upgrades, and host integration. Full pad automation costs more when facilities and multiple wells are in scope.
It should. Leave pump-off and protection logic in the POC. The gateway and SCADA supervise and optionally write setpoints; they must not be the only pump-off brain.
Still have questions about your setup? Talk to an engineer or call (210) 405-4248.