Stable pressure follows when the VFD receives a correctly scaled feedback signal, compares it with the 45% setpoint, and drives the pump in the correct direction: feedback below setpoint raises speed, feedback above setpoint lowers speed. Configure the run-command path and analog feedback first, then apply the demonstrated PID values as commissioning starting points. Look at the trend first; tuning does not fix wiring, reversed action, or incorrect scaling.
How should you read the pressure-control symptoms?
Trace the loop from measurement to final element. The pressure sensor—or the AI1 potentiometer used to simulate one—produces the feedback. The VFD compares that value with its internal setpoint, calculates the PID correction, and changes motor speed. The pump then changes flow and pressure, which must return through the feedback channel.
| Signal or function | Source | Wrong-value symptom |
|---|---|---|
| Run command | K1 switch through DI1
|
The PID display may show an error, but the motor does not run. |
| PID setpoint | VFD panel, configured at 45%
|
The loop regulates to the wrong normalized pressure target. |
| PID feedback |
AI1; an external potentiometer simulates the process signal |
The drive accelerates, decelerates, or holds speed at the wrong time. |
| Controller output | PID calculation inside the VFD | Speed hunts, responds too slowly, or remains limited. |
| Process response | Motor, pump, and piping network | Motor speed changes correctly, but pressure does not follow as expected. |
If the motor never starts, investigate the command source, DI1 assignment, two-wire logic, permissives, and active drive faults before changing PID gains. If it starts but moves in the wrong direction after the feedback changes, check feedback polarity, PID action, and analog scaling. If the direction is correct but the pressure oscillates, inspect the trend and process mechanics before adjusting the controller.
What mechanism makes the VFD hold pressure?
The controller forms an error from the setpoint and feedback. In this application, feedback below the 45% setpoint commands more motor speed; feedback above setpoint commands less speed; equal values produce steady speed. That action matches a normal pump process in which increasing speed raises the measured pressure.
The proportional term reacts to present error. A higher proportional gain produces a larger immediate speed correction, but excessive gain can cause oscillation. The integral term accumulates error and removes persistent offset; an integral time that is too aggressive can drive repeated overshoot or windup when the output reaches a speed limit. The derivative term is disabled in the demonstrated configuration, avoiding amplification of noise on the analog feedback.
The 0.2 s sampling period determines how often the controller updates. The 5.0% deviation limit defines the configured allowable difference between feedback and setpoint. Confirm in the drive manual how that model applies the deviation limit—for example, as a control threshold, alarm threshold, or deadband—before using it as an acceptance tolerance.
What must be checked before entering PID values?
Measure before adjusting. With the motor stopped and the process in a safe condition, observe the raw or normalized AI1 value while moving the potentiometer through its usable range. The displayed feedback must change smoothly, without jumps, dropouts, saturation, or reversed scaling. For a real pressure transmitter, compare the drive indication with an independent pressure measurement at several operating points.
Confirm that the feedback represents pressure rather than a manually selected speed reference. Verify the analog input type, signal common, shield termination, input scaling, sensor supply, and engineering-unit conversion against the drive and transmitter documentation. A 45% setpoint is a normalized command; it represents the desired pressure only when the input scaling maps the transmitter range correctly.
Next, test the command chain independently. The configuration uses terminal control, assigns DI1 as forward run/stop, and selects two-wire operation. Operate K1 and verify that the drive status changes between stopped and forward run. Do not proceed to tuning if the run state is intermittent or governed by a different command source.
How do you configure the demonstrated control loop?
- Set
F00.11=1to select terminal start/stop commands. - Set
F15.00=2soDI1provides the forward run/stop function. - Set
F15.16=0for two-wire operation. - Set
F04.00=1to enable PID closed-loop control. - Set
F04.02=0to select the AI analog feedback input. - Set
F16.01=5to assign the AI input as PID feedback. - Set
F04.03=45for a45%setpoint. - Enter the demonstrated controller values:
F04.04=3for proportional gain andF04.05=2for an integral time of2 s. - Set
F04.7=0to disable derivative action. - Set
F04.09=0.2for a0.2 ssampling period. - Set
F04.10=5.0for a5%deviation limit. - Save the configuration using the drive's specified parameter-storage procedure, then cycle or reinitialize only if its manual requires that action.
These identifiers belong to the demonstrated drive and are not universal across manufacturers or product families. On another VFD, map each function—command source, digital-input assignment, two-wire mode, PID enable, feedback source, setpoint, gains, sampling period, and deviation limit—to that drive's parameter list rather than copying the numbers.
How do you verify the loop after configuration?
- Start the VFD with K1 and confirm that the drive reports a forward run command from
DI1. - Set simulated feedback below
45%. Confirm that the commanded frequency or speed rises. - Move feedback above
45%. Confirm that commanded frequency or speed falls. - Set feedback equal to
45%. Confirm that speed settles rather than continuing to ramp. - Move the potentiometer slowly through several values and trend setpoint, feedback, PID output, motor speed, and measured pressure where available.
- Replace the simulator with the real transmitter and repeat the checks using controlled demand changes.
Judge the signal chain separately. A correct error response proves the controller direction, but it does not prove the pressure calibration. Correct speed movement proves that the VFD output follows the controller, but it does not prove that the pump, valves, or piping can produce the required pressure. Verify each boundary before changing gain or integral time.
Which pitfalls recur on constant-pressure VFD systems?
Copying parameter numbers between drive families is the first failure mode. The same address can control a different function, accept a different unit, or be absent. Read back every configured function by description.
Incorrect feedback scaling is equally common. A stable loop can regulate precisely to the wrong pressure when the transmitter range and analog-input scaling disagree. Compare indicated feedback with an independent measurement rather than treating a quiet trend as proof of accuracy.
Reversed control action causes positive feedback: low pressure reduces speed or high pressure increases it. Stop the test if error grows after the first output movement. Correct signal polarity, scaling, or PID action before restarting.
Mechanical limits can resemble poor tuning. Closed valves, inadequate pump capacity, air, leakage, a blocked sensing line, or minimum and maximum speed limits can hold the controller at an output limit. Integral adjustment will not recover authority that the final element does not have.
Finally, tune with the actual process connected. The potentiometer proves signal direction and basic PID behavior, but it does not reproduce pump inertia, piping volume, demand disturbances, sensor lag, or hydraulic interaction.
FAQ
Can I copy these VFD PID parameters to another drive?
No. Use the functional sequence, but map it to the other drive's manual because addresses such as F04.03 and F15.00 are product-specific.
Does feedback above 45% always make the pump slow down?
It does in this configured loop: feedback above the 45% setpoint reduces speed, while feedback below it increases speed. If the installed system reacts oppositely, stop and correct the feedback polarity or PID action.
Can I fix pressure hunting by changing the PID gain?
Only after confirming a smooth feedback signal, correct scaling, correct action, usable speed limits, and sound hydraulics. Start from P=3, I=2 s, and D=0 only for the demonstrated drive and process, then adjust from trend data.
Can I keep troubleshooting if the feedback or output is unstable?
Stop commissioning when the analog value jumps, the control action runs away, the drive reaches a limit without pressure response, or a parameter function cannot be matched to the installed model. Record the parameter set, drive status, feedback trend, command state, and fault information, then escalate to the manufacturer's official support channel.