A VSD can operate a pump feeding several branched lines, but it changes the head available to every branch at once. It cannot independently control two branch flows with one speed command. Use pump speed for a common variable such as header pressure or total flow, then use branch control valves or other independent restrictions wherever each destination requires its own flow.
Branch-flow symptoms
The number that matters is the differential head available between the common suction and each destination. When speed falls, every branch receives less available head. The branch with the greatest static head, destination pressure, or piping loss reaches zero flow first; the other branches may continue flowing.
| Quantity | Limit or diagnostic meaning | Where to read it |
|---|---|---|
| Pump differential pressure | Must exceed destination pressure plus static and friction losses for the branch to flow | Suction and discharge pressure instruments |
| Individual branch flow | Shows the actual split; total pump flow cannot reveal a starved branch | Branch flow transmitter or a temporary measurement |
| Total pump flow | Must remain inside the permitted pump operating region | Common-header flow transmitter and pump curve |
| Destination pressure or liquid level | Changes the branch system curve and therefore its share of flow | Receiving-vessel pressure and level instruments |
| VSD speed command | Changes the pump curve for all branches simultaneously | Drive status or control-system display |
| Control-valve position | A valve near fully open indicates insufficient available head; a valve near closed indicates excess head or poor pressure coordination | Valve-position feedback |
| Required minimum pump flow | Defines the low-flow operating boundary and any recycle requirement | Pump manufacturer curve and datasheet |
Common-head hydraulic mechanism
Each branch intersects the pump operating condition through its own system curve. Static elevation, receiving-vessel pressure, pipe friction, fittings, and valve position determine that curve. Branch flows settle where their combined demand matches the pump curve at the commanded speed.
Reducing speed lowers the pump head curve. A low-resistance branch may still accept substantial flow while a higher-pressure branch loses flow completely. This is a hydraulic limit, not a controller-selection problem: once available differential head is below a branch requirement, additional controller output cannot produce flow without raising pump speed or reducing resistance.
The branch split also changes when a receiving vessel pressure rises, a level changes the static head, or a valve moves. A disturbance in one branch therefore shifts the operating point of the others. Check valves may prevent reverse flow, but they do not create independent regulation.
Control-architecture selection
Select the manipulated variable by separating the common duty from the independent duties. One VSD provides one continuously manipulated speed. That speed can regulate one common process variable directly, while separate valves regulate branch-specific variables.
| Process requirement | Practical control arrangement | Main limitation |
|---|---|---|
| One critical branch; other branch accepts variable flow | Use speed to control the critical branch flow and monitor the secondary branch | Secondary flow changes with speed and destination conditions |
| Stable common-header pressure with independent branch flows | Use the VSD for header-pressure control and one control valve for each regulated branch | The pressure setpoint must give the most demanding valve adequate authority |
| Controlled total flow with a fixed hydraulic split | Use the VSD for total flow and balance branches with fixed restrictions or manual valves | The split changes when destination pressures or line resistances change |
| Two independently controlled branch flows | Provide two independent manipulated elements, normally branch valves, with speed maintaining shared head | One speed command alone cannot satisfy two independent flow setpoints |
For reflux service, treat the required column return flow as a protected process duty. A transfer branch must not consume enough capacity to deprive that duty. Establish the controlling case from the required flows, destination pressures, and pump curve rather than from valve positions alone.
Configuration and commissioning procedure
- Draw the hydraulic path from pump suction through the common header to every destination. Mark elevation changes, destination pressures, control valves, check valves, and flow measurements.
- Obtain the pump curves across the intended speed range. Mark the permitted operating region, required minimum flow, and any motor or drive restrictions from the manufacturer documentation.
- Calculate or measure each branch system curve. Include static head, vessel pressure, and friction loss at the required branch flow.
- Identify the worst hydraulic case: highest destination pressure, greatest static head, largest required combined flow, or the combination specified by the process design.
- Select a common control objective for the VSD. Header pressure is usually suitable when several branch valves must regulate independently; total flow or one critical branch flow may be suitable when the remaining branches can float.
- Set the common pressure target high enough for the most demanding branch at design flow, while avoiding unnecessary throttling across the easier branches. Read the required value from the hydraulic calculation and measured pressure profile.
- Configure each critical branch controller to operate its own valve. Coordinate controller response so fast valve corrections do not fight a similarly aggressive speed loop.
- Apply low-speed, low-flow, loss-of-flow, and destination-protection limits using the pump datasheet and process design values. Where minimum-flow recycle is required, make it independent of normal branch demand.
Operating-case verification
Test the control scheme at the boundaries, not only at one normal operating point. Record suction pressure, discharge pressure, speed, total flow, every critical branch flow, valve positions, and receiving-vessel conditions.
- Run each branch alone at its required flow and confirm that the pump supplies the needed head without leaving its permitted operating region.
- Run all intended branches together at the maximum credible demand. Confirm that the highest-resistance branch retains positive flow and usable valve authority.
- Move the secondary branch from minimum to maximum demand. The protected branch must recover to setpoint without sustained oscillation or unacceptable deviation.
- Raise the destination pressure through its permitted operating range, or reproduce the equivalent hydraulic case. Confirm that the affected valve does not remain fully open while its flow falls below requirement.
- Reduce demand and verify minimum-flow protection before the pump enters its prohibited low-flow region.
A sound result has stable branch flows, bounded speed movement, and control valves operating away from continuous saturation. If a branch valve remains fully open, compare measured pump differential pressure with the calculated branch requirement before changing tuning.
Recurring hydraulic and control pitfalls
Oversizing the header-pressure setpoint wastes energy across throttled valves and can aggravate leakage or valve noise. Undersizing it causes the hydraulically demanding valve to saturate and lose flow first. Select pressure from the worst required branch condition, then validate it under actual operating cases.
Using total flow as proof of branch performance hides redistribution. The common flow can remain on target while a low-resistance route takes more and the reflux route takes less. Measure every process-critical branch.
Two fast controllers acting on the same hydraulic disturbance can hunt: a branch valve opens as flow falls, the pressure loop raises speed, and the branch controller then closes sharply. Establish a clear hierarchy, tune the inner or faster response first, and trend both outputs during disturbances.
Low-speed operation can cross pump cooling, lubrication, minimum-flow, or motor-cooling limits. The applicable boundary comes from the pump, motor, and VSD documentation; speed percentage alone is not a hydraulic protection criterion.
Frequently asked questions
Why does one pump branch stop flowing when VSD speed drops?
The reduced speed lowers available pump head for every branch. The branch whose static head, destination pressure, and friction losses exceed that head reaches zero flow first.
Why does opening one branch change flow in another branch?
Opening a branch changes total system resistance and moves the common pump operating point. The resulting discharge pressure change redistributes flow through every connected branch.
Why do the branch valve and VSD pressure loop oscillate?
Both loops are correcting the same hydraulic disturbance with poorly separated response rates. Trend pressure, branch flow, speed, and valve position, then establish a slower common-head loop and faster local flow correction where the process permits.
When should I stop tuning and call official support?
Stop when measured pressure and flow place the pump outside its manufacturer-defined operating region, when minimum-flow protection cannot be maintained, or when the required branch duty needs more head than the documented pump curve provides. Escalate to the pump and VSD manufacturers through their official support channels with the pump curves, hydraulic calculation, drive status, instrument trends, and valve positions.