Plunger lift as a method uses a well's own gas pressure to sweep liquid to surface, but something has to decide when to open and close the well to make that happen reliably, cycle after cycle. That decision-maker is a dedicated field device: the plunger lift controller. This guide is about the controller itself - the box in the wellhead panel - rather than the lift method or the cycle it runs. It covers what inputs the controller reads, the states it sequences a well through, and how it is wired into the motor valve and arrival sensor at the wellhead.
Plunger Lift Controller in one line: A plunger lift controller is the dedicated field controller mounted at a gas well that automatically opens and closes the motor valve to run the well's plunger lift cycle. It reads inputs such as casing, tubing, and line pressure and a plunger arrival signal, and it sequences the well through open, afterflow, and shut-in states based on those inputs. It lives in the wellhead panel, wired to the motor valve it operates and the arrival sensor it listens to.
A plunger lift controller makes its decisions from a small set of measured inputs, each telling it something about the state of the well. Casing pressure is the central one, because it reflects the gas energy that has built up behind the accumulated liquid while the well was shut in - the pressure that will drive the plunger and its liquid slug to surface once the valve opens. Tubing pressure and flow-line pressure give the controller the picture on the production side, so it can judge the differential the well is working against and recognize when flow has fallen off. Reading these pressures lets the controller decide not just on a fixed schedule but in response to what the well is actually doing.
The other critical input is the plunger arrival signal. A sensor at the surface tells the controller the moment the plunger reaches the top of its travel, which is the event that marks a successful lift and lets the controller know the liquid slug has been delivered. Arrival is a discrete signal - it either happened within the expected window or it did not - and it is fundamental to the controller's logic, because whether and how quickly the plunger arrived is what tells the controller how the last cycle went. Some controllers also take additional inputs such as differential pressure across the line or line temperature, but casing pressure and arrival are the backbone.
From these inputs the controller continuously evaluates whether conditions warrant moving the well to its next state. It is not merely a timer running blind; it combines elapsed time with the measured pressures and the arrival signal to decide when the well has built enough energy to lift, when flow has dropped enough to warrant shutting in, and whether the last cycle succeeded. The quality of a plunger lift installation depends heavily on the controller sensing these inputs accurately and acting on them sensibly.
The controller drives the well through a repeating sequence of states, opening and closing the motor valve to move between them. In the shut-in state the valve is closed and the well is building - gas pressure accumulates in the casing while liquid falls back and collects, and the plunger sits at the bottom. The controller holds the well shut in until it judges that enough energy has built, based on casing pressure reaching a target, a shut-in time elapsing, or a combination of the two. This building phase is what gives the subsequent lift the pressure it needs to succeed.
When the controller opens the motor valve, the well enters the flow phase: the released pressure drives the plunger up the tubing ahead of the accumulated liquid, sweeping the slug to surface. The controller is watching for the plunger to arrive during this phase. Once arrival is detected, many controllers continue into an afterflow state, keeping the valve open to produce gas at a good rate while the well still has energy, since the point of deliquifying is to let the well flow freely once the liquid load is cleared. The controller decides how long to allow afterflow before flow decays enough that liquid begins loading up again.
As afterflow tails off, the controller closes the motor valve and returns the well to shut-in, and the sequence repeats. The controller's job is to time these transitions well: shut in too long and production is needlessly lost, shut in too little and the well may not build enough energy to lift the plunger, run afterflow too long and liquid reloads. Whether it uses fixed timers, pressure targets, or a more adaptive scheme to make these transitions is a matter of how the controller is configured, but sequencing the well through shut-in, flow, and afterflow is the fundamental behavior every plunger lift controller provides.
Physically, the plunger lift controller is a compact electronic device housed in the wellhead control panel, powered on many remote wells by a small solar-and-battery arrangement because grid power is not available. It is wired to the field: pressure transducers on the casing, tubing, and line feed it their signals; a discrete output drives the actuator or pilot that operates the motor valve on the wellhead; and a wire from the arrival sensor at the lubricator carries the plunger arrival signal in. The controller sits close to the equipment it operates, so it can keep running the well autonomously even when communications are down, which is essential on isolated locations.
That local autonomy is paired with remote visibility through SCADA. The controller typically supports a field protocol such as Modbus or DNP3, so a cloud SCADA can read its pressures, its arrival status, its cycle counts, and its state, and can adjust its setpoints without a technician driving to the pad. This is the difference between owning a well and merely having one: an operator can see how each plunger well is cycling, whether plungers are arriving, and how production is trending, from a screen covering the whole field.
For a producer running many plunger-lift gas wells across a wide area, connecting the controllers to a platform like Merobix turns a fleet of independent boxes into a monitorable, tunable system. The platform reads each controller over Modbus or DNP3, presents casing pressure and arrival behavior alongside production, flags wells that stop cycling or fail to arrive, and lets setpoints be pushed out remotely. The controller still runs the well locally, cycle by cycle, but the operator gains a fieldwide view and the ability to intervene from anywhere rather than one well at a time in person.
Plunger lift is the artificial-lift method that uses a well's own gas pressure to drive a plunger up the tubing and sweep liquid to surface. A plunger lift controller is the physical field device that actually runs that method on a well - reading pressures and the arrival signal and opening and closing the motor valve to sequence the cycle. The method is the concept; the controller is the box in the wellhead panel that executes it.
Chiefly casing pressure, which reflects the built-up gas energy that will drive the plunger, along with tubing and flow-line pressure on the production side, and the plunger arrival signal from a sensor at the surface. Some controllers also read differential pressure or line temperature. From these it decides when to open, when to shut in, and how the last cycle went.
It sits in the wellhead control panel at the well, often powered by solar and battery on remote locations. It is wired directly to the pressure transducers, to the actuator that operates the motor valve on the wellhead, and to the arrival sensor at the lubricator. Its proximity to the equipment lets it keep cycling the well autonomously even when communications to the outside are down.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.