Static pressure reset with trim and respond

In a VAV system, the supply fan modulates to hold a duct static pressure setpoint, and each VAV box throttles its damper to deliver the airflow its zone needs. The traditional approach uses a fixed setpoint chosen to satisfy the worst-case zone at full load. At part load, which is most of the time, that fixed setpoint is far higher than necessary. Fans work harder than they need to, VAV dampers throttle almost closed, and noise increases.

Static pressure reset lowers the setpoint until at least one zone damper is nearly wide open. Trim and respond is the most widely used method for doing this, and it is the approach specified in ASHRAE Guideline 36.

Why reset saves so much energy

Fan power varies roughly with the cube of airflow in an ideal system, but in a VAV system controlled to fixed static pressure, the savings at part load are much smaller than the fan laws suggest because the fan must hold pressure even at low flow. Resetting static pressure lets the fan follow a lower system curve, capturing much more of the theoretical savings. See fan laws and how to apply them.

Savings depend on the system, but static pressure reset is widely regarded as one of the most cost-effective control upgrades for existing VAV systems. NECB and ASHRAE 90.1 require static pressure reset based on zone damper positions for many VAV systems with DDC zone controls; confirm the requirements of the edition that applies.

Other benefits include quieter operation, since dampers are less throttled and there is less duct-borne noise, and reduced duct leakage, because leakage rises with static pressure.

How trim and respond works

The logic operates on a regular time step:

1. Start. When the fan starts, the setpoint begins at an initial value and is held for a set delay while the system stabilizes.
2. Count requests. Each VAV zone generates pressure requests when its damper is nearly fully open and it still needs more airflow. The controller adds up requests from all zones, weighted by importance multipliers.
3. Ignore a few. A set number of requests is ignored, so one or two zones cannot drive the system.
4. Trim. If requests are at or below the ignore threshold, the setpoint is reduced by a small fixed amount.
5. Respond. If requests exceed the threshold, the setpoint is increased by an amount proportional to the excess requests, up to a maximum change per step.
6. Limit. The setpoint stays between a minimum and maximum.
7. Repeat every time step.

The setpoint drifts downward slowly when the system is comfortable and climbs quickly when zones start to starve.

Typical parameters

Guideline 36 provides default values that designers adjust for each project. The following are representative of those defaults:

The maximum setpoint should come from the balancing contractor's work: the pressure required at the sensor to deliver design airflow to all zones at full load. This is often lower than the design value on the drawings.

How zone requests are generated

The quality of the reset depends on the quality of the requests. A typical approach:

• A zone generates one request when its damper position exceeds about 95 percent and stops when it falls below about 85 percent, with hysteresis to avoid chattering.
• A zone generates additional requests when its measured airflow falls well short of its setpoint for a sustained period, for example below 50 percent or 70 percent of setpoint for several minutes, indicating severe starvation.
• Requests are suppressed for a period after a setpoint change, to avoid responding to transient conditions.

Requests require reliable damper position feedback or commanded position, and accurate airflow measurement at the box.

Rogue zones

A rogue zone is one that requests constantly regardless of the setpoint, typically because:

• The VAV box or its inlet duct is undersized
• The damper actuator has failed or slipped
• The airflow sensor is fouled or miscalibrated
• The zone's load exceeds its design
• The zone setpoint has been lowered unrealistically by an occupant

Rogue zones hold the setpoint at maximum and eliminate savings. The ignore count helps, and importance multipliers can reduce a zone's influence, but the real fix is to identify and repair the cause. Guideline 36 sequences accumulate request hours so operators can rank zones by how often they request.

Commissioning and verification

1. Confirm the static pressure sensor location and calibration, and that the transducer range suits the setpoint range. See duct static pressure and how to reduce it.
2. Verify each VAV box reports damper position and airflow correctly and generates requests under the defined conditions.
3. Set SPmax from balancing data.
4. Test start-up behaviour, trim during low load and respond when zones are forced to request.
5. Trend setpoint, measured static pressure, fan speed, number of requests and the requesting zones for at least a week.
6. Identify rogue zones from trends and correct them.
7. Confirm the fan static pressure loop is stable across the full setpoint range, since a loop tuned at high pressure may hunt at low pressure.

Common problems

• Reset logic installed but disabled, or SPmin set equal to SPmax
• Requests based on commanded rather than actual damper position, combined with failed actuators
• A single rogue zone holding the system at maximum
• Static pressure sensor in a turbulent location giving noisy readings
• No trends, so nobody notices the setpoint never moves

These are among the most common findings in retro-commissioning of VAV buildings, and correcting them is usually low-cost.

Key takeaways

• Fixed duct static pressure setpoints waste fan energy at part load; reset captures much of the potential savings.
• Trim and respond lowers the setpoint slowly when zones are satisfied and raises it quickly when they request.
• Representative Guideline 36 parameters are a good starting point, with SPmax taken from balancing.
• Reliable damper position and airflow data are essential for meaningful zone requests.
• Rogue zones must be found and fixed, and trends reviewed to confirm the setpoint actually moves.