System and observed failure
The installation uses a Pixel 1211 controller, a variable-frequency-drive fan with a 0-10 V speed command, a water heating coil, a refrigerant cooling coil with a condensing unit, and outdoor-air, duct-air, and return-water temperature sensors. It recirculates air with a small unforced outdoor-air intake and must cool in summer and heat in winter.
| Observed item | Value or behavior | Control consequence |
|---|---|---|
| Outdoor temperature | 24 degrees C | Used for summer/winter mode selection in the described project, not temperature regulation |
| Duct temperature | 26.5 degrees C | Above the 25 degrees C setpoint, so cooling was requested |
| Return-water temperature | 20 degrees C | Available to the heating function; no additional behavior is established |
| Fan output | Fell to its 20% lower limit | Reduced airflow while the condensing unit remained active |
| Reported condensing-unit activity | 10 cycles per minute | The evidence does not identify whether this was compressor switching, a controller cycle indication, or another signal; verify the actual output before diagnosing it |
This combination failed to lower the measured duct temperature and raised a reported risk of freezing at the cooling coil.
Root cause: the feedback sensor is upstream
The duct sensor had been moved ahead of the cooling and heating coils. In that position it measured air entering the coils rather than conditioned discharge air. The sequencer therefore saw slow progress far from setpoint and advanced from its reported cooling stage 8 to a fan-speed-reduction stage.
The sensor placement prevents the controller from promptly observing the cooling coil's effect. A minus 2 degrees C sensor correction reportedly altered when cooling started, but it does not correct the underlying measurement location.
Select the control objective before changing speed logic
Use separate measurements for separate objectives. Place the duct sensor after both the cooling and heating coils when it is the discharge-temperature feedback. Add a room sensor near the return-air pickup if the objective is occupied-space temperature. Without a room sensor, reaching the duct setpoint does not prove that the room has reached its target.
Do not assume the sequencer automatically reduces fan speed after temperature reaches setpoint; the available evidence explicitly says this behavior is not an inherent sequencer task. If room-temperature-dependent speed reduction is required, modify the project to bind fan speed to the relevant room-temperature condition.
Correct the summer fan-speed strategy
- Move the duct-temperature sensor downstream of the cooling and heating coils so the loop measures conditioned discharge air.
- Add a room sensor at the return-air pickup when room comfort, rather than discharge temperature alone, determines when capacity or airflow may decrease.
- Disable summer fan-speed reduction based on temperature if that option is causing airflow to fall during active cooling. The configuration identifies this fan option as operation by temperature; the evidence supports using it only for winter in this application.
- Expose a separate minimum fan-speed setting that applies while the condensing unit is enabled. Determine that minimum experimentally for the actual installation; the existing 20% limit is not demonstrated to provide adequate airflow.
- When cooling is off, permit the separately selected low ventilation speed if the operating requirement calls for it. Keep the active-cooling minimum independent from this ventilation setting.
An alternative is to command fixed fan speed whenever the condensing unit runs, but the evidence does not establish the required value. Do not select that value without airflow and equipment-protection verification.
Handle mode boundaries and verify the result
The outdoor sensor participates in summer/winter selection in the described configuration; it does not directly regulate the duct temperature. Confirm the mode transition separately from the discharge-temperature loop.
A custom macro was later configured with a 1 degree C hysteresis and summer/winter modes, but transition through zero at the boundaries remained unresolved. Treat this as an unverified project-logic issue: inspect the sign convention, heating/cooling exclusivity, and state retained inside the hysteresis band before commissioning. The evidence does not supply a proven Pixel 1211 implementation for that boundary.
Verify the corrected system by recording the downstream duct temperature, room temperature if installed, fan command, cooling request, and actual condensing-unit output together. During cooling, confirm that discharge temperature responds promptly, fan speed never falls below the commissioned active-cooling minimum, and the ambiguous 10-cycles-per-minute indication has been identified. Confirm heating and cooling cannot be requested simultaneously and check the condensing unit's required protection sequence against its manufacturer documentation; those requirements are not provided here.
FAQ
Where should the Pixel 1211 duct temperature sensor be installed?
Install the control sensor after the cooling and heating coils when it regulates discharge temperature.
Why does the fan fall to 20% while the condensing unit is cooling?
The sequencer saw slow temperature reduction from the upstream sensor and entered a fan-speed-reduction stage. Disable summer temperature-based speed reduction or enforce a separately commissioned minimum speed whenever cooling is active.
Can duct temperature prove that the room reached setpoint?
No. Add a room sensor near the return-air pickup if room temperature controls capacity or fan-speed reduction; the downstream duct sensor only establishes conditioned-air temperature.