A chemical injection pump physically pushes inhibitor into a pipeline or well, but something has to tell that pump how much to push and how often. That something is the chemical injection controller, and it is a distinct device from the pump itself. The controller turns a target dose - a barrel-per-day figure or a parts-per-million target - into the pump strokes or on-off timing that actually deliver it. On an unattended site it is also the piece that reports back whether the intended dose is being met, which is what lets an operator trust a number on a screen instead of driving out to read a tank.
Chemical Injection Controller in one line: A chemical injection controller is the device that meters a chemical injection pump to a target dose, commanding it by stroke rate, speed, or on-off duty cycle rather than moving fluid itself. It takes a setpoint from an operator or RTU, drives the pump to match it, and reports actual injection back so real dosing can be compared against the intended rate.
It helps to separate the two devices cleanly. The pump is the mechanical element: a diaphragm, plunger, or gear head that displaces a fixed volume of chemical per stroke or per revolution. The controller is the brain that decides how fast that head runs. On a solar-powered chemical pump the controller might switch the motor on for a few seconds every few minutes; on an electric metering pump it might set a continuous stroke frequency. Either way, the delivered rate is the volume per stroke multiplied by the strokes the controller commands.
There are a few common ways a controller meters a pump. Stroke-rate or frequency control varies how many strokes per minute the pump makes while each stroke moves a fixed volume. Duty-cycle or timer control runs a fixed-output pump for a portion of each cycle - on for thirty seconds, off for four and a half minutes - so the average rate scales with the on-time. Speed control varies motor RPM on a continuous pump. In every case the operator sets a target and the controller translates it into the pump's native language.
This division matters because the two devices fail in different ways and are tuned by different people. A pump can lose prime, vapor-lock, or wear a check valve; a controller can hold a wrong setpoint, miscount strokes, or lose its output signal. Diagnosing a low dose starts with asking whether the controller is commanding the right rate and whether the pump is actually delivering what it is being commanded to deliver.
On a monitored site the chemical injection controller usually sits under an RTU. The RTU may hold the dosing setpoint and hand it to the controller, or the controller may be a smart device the RTU simply reads and writes over a serial or digital link. The command path is straightforward: an operator or an automated routine sets a target dose, the RTU passes it down, and the controller drives the pump to match. Changing a dose remotely, rather than sending a technician with a screwdriver, is one of the main reasons to put a controller on a communications network at all.
Verification is the harder and more valuable half. A controller that only commands a rate is running open-loop: it assumes the pump delivered whatever it asked for. A controller that also measures delivery can close the loop. Feedback can come from a stroke counter that confirms the pump is actually cycling, from a level transmitter on the day tank whose drawdown reveals real consumption over time, or from a flow meter on the chemical line. Each of these lets the RTU compare actual injection against the setpoint and flag a gap.
That gap is where the operational payoff lives. A pump that is commanded to inject and is stroking normally but is drawing nothing from an empty tank, or is stroking against a stuck check valve, will look fine to a naive controller. Comparing commanded strokes against measured tank drawdown catches exactly that class of silent under-dose. The controller becomes not just an actuator but a reporting point that tells the operator whether the chemistry the process needs is genuinely reaching the pipe.
In a cloud SCADA deployment, the chemical injection controller becomes a set of tags: the commanded dose, the measured tank level, the stroke or pump-run count, and derived values like calculated versus target injection rate. Merobix collects those tags from the RTU and trends them so the whole dosing picture is visible remotely. An operator can see the setpoint, the tank draining at the expected slope, and a running comparison of intended against actual delivery, all without leaving the office.
The alarms this enables are the practical draw. A tank-level trend that flattens out means the pump has stopped drawing even though the controller is still commanding strokes, which points to a lost prime, a vapor lock, or an empty tank; catching that early prevents days of undosed production and the corrosion or hydrate risk that follows. A tank-level slope steeper than the setpoint would predict flags overdosing, which wastes expensive chemical. Both are far easier to see as a trend line than to catch on a monthly site visit.
Because the controller's data lands in the same historian as the process it protects, teams can also correlate dosing with outcomes. Trending corrosion-inhibitor delivery against downstream conditions, or methanol dose against measured temperatures, turns the controller from a black box into an auditable part of the chemical program. Remote setpoint changes plus verified delivery is the combination that lets a small team manage dosing across many wells with confidence.
The pump is the mechanical device that displaces a fixed volume of chemical per stroke or revolution. The controller is the logic that decides how fast the pump runs, translating a target dose into stroke rate, motor speed, or on-off timing. The controller can command a rate and, in better setups, verify that the pump actually delivered it.
It converts a target - either a volume per day or a parts-per-million concentration - into the pump's native control input. That might mean setting a stroke frequency, running a fixed-output pump for part of each timed cycle, or varying motor speed. The delivered rate is the pump's volume per stroke multiplied by the strokes the controller commands.
Commanding a pump is not the same as confirming delivery, so the RTU relies on feedback. A stroke counter confirms the pump is cycling, a day-tank level transmitter reveals real consumption through its drawdown, and a chemical-line flow meter measures actual throughput. Comparing any of these against the commanded setpoint lets the system catch a pump that is stroking but not moving fluid.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.