Author: scott

  • Honeywell VAV Controller Offline – Common Causes and Fixes

    Why Does a Honeywell VAV Controller Go Offline?

    A Honeywell VAV controller appearing offline usually indicates a communication failure or power issue.


    Common Causes

    • BACnet communication loss
    • Loose wiring
    • Power supply failure
    • Duplicate MAC address
    • Controller firmware issue

    Troubleshooting Steps

    1. Verify controller power supply
    2. Check network polarity and termination
    3. Confirm unique device address
    4. Restart controller and monitor status

    Most offline issues are wiring-related rather than hardware failure.


    FAQ

    Should the controller be replaced immediately?
    No. Confirm communication and power before replacing hardware.

  • High Head Pressure on Rooftop Unit – Causes and Fixes

    What Causes High Head Pressure?

    High head pressure indicates elevated refrigerant pressure on the condenser side of the system.

    This condition can trigger safety lockouts.


    Common Causes

    • Dirty condenser coil
    • Failed condenser fan motor
    • Refrigerant overcharge
    • Non-condensable gases in system
    • Blocked condenser airflow

    Troubleshooting

    1. Inspect and clean condenser coil
    2. Verify condenser fan operation
    3. Measure refrigerant pressures
    4. Check ambient temperature conditions

    Persistent high head pressure can damage the compressor.


    FAQ

    Can high outdoor temperature cause this?
    Yes, but the system should still operate within design limits.

  • RTU Trips Breaker on Startup – Causes and Solutions

    Why Does an RTU Trip the Breaker When Starting?

    If a rooftop unit trips the breaker immediately upon startup, the most common cause is excessive inrush current from the compressor or fan motor.


    Common Causes

    • Shorted compressor windings
    • Failed start capacitor
    • Locked rotor condition
    • Undersized breaker
    • Ground fault
    • Loose electrical connections

    Troubleshooting Steps

    1. Measure compressor winding resistance
    2. Inspect start and run capacitors
    3. Check breaker rating versus unit specifications
    4. Inspect wiring for signs of burning or insulation damage

    Repeated breaker trips require immediate diagnosis.


    FAQ

    Is this dangerous?
    Yes. Repeated breaker trips indicate a serious electrical issue.

  • Carrier ComfortLink Alarm 12 – Low Suction Pressure Fault

    What Does Alarm 12 Indicate?

    Alarm 12 typically signals a low suction pressure condition in the refrigerant circuit.

    To protect the compressor, the controller may shut down cooling.


    Common Causes

    • Low refrigerant charge
    • Refrigerant leak
    • Dirty evaporator coil
    • Blocked airflow
    • Failed low-pressure switch

    Troubleshooting

    1. Inspect filters and evaporator coil
    2. Measure refrigerant pressures
    3. Check for visible oil residue (leak indicator)
    4. Test low-pressure switch continuity

    Correct the root cause before resetting the alarm.


    FAQ

    Will adding refrigerant fix it?
    Only if the system is properly diagnosed and leaks are repaired.

  • Trane RTU Error Code 91 – Communication Fault Explained

    What Does Trane RTU Error Code 91 Mean?

    Error Code 91 on many Trane rooftop units indicates a communication failure between the main controller and a connected module or sensor network.

    When active, the unit may:

    • Show module offline errors
    • Disable cooling or heating stages
    • Operate in limited fallback mode

    Common Causes

    • Loose or damaged communication wiring
    • Incorrect module addressing
    • Failed communication board
    • Electrical interference
    • Grounding issues

    Troubleshooting Steps

    1. Inspect communication wiring for polarity and continuity
    2. Verify unique module addresses
    3. Power cycle affected modules
    4. Check termination resistors if applicable

    Replace control modules only after verifying wiring and addressing.


    FAQ

    Does this mean the RTU has failed?
    No. Most cases involve wiring or configuration issues.

  • VAV Box Not Responding to Thermostat – Troubleshooting Steps

    Why Is the VAV Box Not Responding?

    If a VAV box does not respond to thermostat adjustments, the issue is typically:

    • Communication failure
    • Controller lockup
    • Sensor malfunction
    • Actuator failure

    Common Causes

    • BACnet or N2 communication loss
    • Broken thermostat wiring
    • Failed damper actuator
    • Incorrect controller configuration
    • Power supply failure

    Troubleshooting

    1. Verify Power to Controller

    Measure voltage at controller terminals.

    2. Check Communication Status

    Confirm device is online in supervisory system.

    3. Inspect Actuator Operation

    Manually command damper open/close.

    4. Test Thermostat Signal

    Verify signal continuity and calibration.


    FAQ

    Can the VAV operate without communication?
    Some controllers enter a fallback mode but functionality may be limited.

  • Modbus CRC Error – Meaning and Troubleshooting Guide

    What Is a Modbus CRC Error?

    A CRC (Cyclic Redundancy Check) error indicates that a Modbus message was corrupted during transmission.

    The receiving device rejects the message because the checksum does not match.


    Common Causes

    • Electrical noise
    • Improper RS-485 termination
    • Loose wiring
    • Incorrect baud rate
    • Grounding issues
    • Long cable runs without repeaters

    Troubleshooting Steps

    1. Verify Termination Resistors

    Ensure correct placement at both ends of the network.

    2. Inspect Shield Grounding

    Improper grounding increases noise susceptibility.

    3. Confirm Baud Rate and Parity

    All devices must match communication settings.

    4. Shorten Test Cable

    If possible, temporarily reduce cable length to isolate noise issues.


    FAQ

    Is a CRC error always wiring-related?
    Most commonly yes, though configuration mismatches can also cause errors.

  • BACnet Device Offline After Power Outage – How to Restore Communication

    Why Does a BACnet Device Go Offline After a Power Outage?

    After a power interruption, some BACnet devices may fail to rejoin the network properly.

    This typically results from:

    • Communication bus timing issues
    • Duplicate MAC address conflicts
    • Controller boot delays
    • MS/TP token disruptions

    Common Causes

    • Improper network restart sequence
    • Power supply instability
    • Faulty controller firmware
    • Lost BBMD registration (BACnet/IP systems)

    How to Fix It

    1. Power Cycle the Affected Device

    Shut down and restart the controller.

    2. Verify Network Voltage

    Confirm stable power supply levels.

    3. Check MAC Address Uniqueness

    Ensure no duplicate addresses exist.

    4. Restart MS/TP Trunk

    In some cases, restarting the entire segment resolves token issues.


    FAQ

    Does this indicate hardware failure?
    Usually not. It is often a communication reinitialization issue.

  • Compressor Short Cycling on Rooftop Unit – Causes and Solutions

    What Is Compressor Short Cycling?

    Short cycling occurs when the compressor starts and stops rapidly without completing a normal cooling cycle.

    This can reduce efficiency and damage equipment over time.


    Common Causes

    • Low refrigerant charge
    • Oversized unit
    • Dirty condenser coil
    • Faulty thermostat
    • Pressure switch fault
    • Improper airflow
    • Electrical supply issues

    Troubleshooting Steps

    1. Inspect Thermostat Settings

    Verify correct temperature differential.

    2. Check Refrigerant Levels

    Low charge often causes rapid cycling.

    3. Clean Condenser Coil

    Overheating can trigger high-pressure trips.

    4. Inspect Pressure Switch Operation

    Repeated trips indicate underlying system imbalance.


    Risks of Ignoring Short Cycling

    • Increased compressor wear
    • Higher energy usage
    • Premature system failure

    FAQ

    Can short cycling damage the compressor?
    Yes. Repeated starts increase mechanical stress.

  • RTU Not Cooling But Fan Running – Causes and Fixes

    Why Is My Rooftop Unit Fan Running but Not Cooling?

    If your rooftop unit (RTU) fan is running but the space is not cooling, the most common cause is that the compressor is not operating, even though the blower motor is functioning normally.

    This condition usually indicates a refrigerant circuit or safety lockout issue rather than a fan failure.


    Common Causes

    The most frequent causes include:

    • Tripped high-pressure or low-pressure switch
    • Compressor contactor failure
    • Blown fuse in compressor circuit
    • Failed run capacitor
    • Thermostat not calling for cooling
    • Low refrigerant charge
    • Control board lockout

    How to Troubleshoot

    1. Verify Thermostat Call

    Confirm the thermostat is calling for cooling and sending a signal to the RTU.

    2. Check Compressor Operation

    Listen for compressor startup. If silent:

    • Check contactor engagement
    • Measure voltage at compressor terminals

    3. Inspect Pressure Switches

    If a safety switch is open, the compressor will not run.

    Reset only after identifying root cause.

    4. Check Refrigerant Pressure

    Low suction pressure can trigger compressor lockout.


    When to Call for Service

    If:

    • Breakers trip repeatedly
    • Refrigerant pressures are abnormal
    • Compressor hums but does not start

    Professional service may be required.


    FAQ

    Why does the fan run but not the compressor?
    The blower is often on a separate control circuit and may continue running during faults.