Lesson 10 of 12 · Chapter 10
Diagnostics and Master Troubleshooting
Master troubleshooting is not a talent you either have or you don’t. It is a method: define the problem, verify intent, observe the sequence, measure the pathways, and change one variable at a time until the story makes sense again.
Step one
Read the material
Five ideas. Two on reading refrigerant: what gauges actually tell you, and the two numbers that bridge pressure and physics. One on digital tools. And two on the method itself: where to start, and in what order to test.
Idea one
Pressure is not the goal
A gauge does not diagnose a system. It reports a condition at a moment in time. Pressure is not the goal. Temperature is the goal. Convert suction pressure to the evaporator’s saturation temperature and head pressure to the condensing temperature, then ask whether the system is creating the temperature platforms it needs at both coils.
That is why low suction is never just low suction. It can be a coil pulled colder by low airflow, or a coil starved by a restriction, a failed metering device or low charge: very different stories with different fixes. So first check that the readings will mean something: a steady load, panels on, filter in, normal return paths, the right blower speed. And know your metering device: a fixed orifice leaves superheat reflecting charge and load, while a TXV controls superheat and can mask a charge problem.
Safety comes with the hoses. Eye protection is not optional, and you never loosen a hose under pressure because you are in a hurry.
Idea two
Superheat, subcooling and look-alikes
Superheat is the measured suction line temperature minus the saturation temperature at suction pressure. Low or zero superheat means floodback risk to the compressor; high superheat means a starved evaporator. Subcooling is how far the liquid has dropped below its saturation temperature: low suggests low charge or insufficient condensing; excessive suggests overcharge or a restriction stacking liquid in the condenser.
But do not turn these into single-number rules. Targets come from the system design and the manufacturer, and airflow changes everything: low airflow lowers the load and can raise superheat on its own. A restricted drier can create low suction and high superheat and masquerade as low charge; many systems have been topped off into worse conditions because nobody asked where the pressure was being lost. And high head pressure can come from a dirty condenser, non-condensables or poor outdoor airflow, not just overcharge.
Respect stabilization time. If you diagnose before the system settles, you are not reading the machine, you are reading your own impatience.
Idea three
Digital tools and trends
Digital tools either sharpen your habits or make your mistakes faster. They take simultaneous readings, which helps when a system is changing state, and they calculate superheat and subcooling automatically. That is only as good as the setup: the wrong refrigerant selected, a clamp on the wrong line, or poor contact on paint turns the answer confidently wrong.
Their best use is trending. Logging for 10 to 30 minutes shows the ramp, not just the peak, and keeps cause and effect straight: did head pressure rise first, or did the fan slow first? Board fault histories and sensor readings help too, but a logged high-pressure fault is a clue about a condition, not permission to change a switch, and an outdoor sensor reading 75°F on a 30°F day explains strange defrost behaviour without any guessing.
The tool’s confidence is not evidence. Consistency is evidence.
Idea four
Define it, then trace intent and sequence
Start with an operational definition, not a label. “Not cooling” can mean at least five different realities: no call, outdoor unit not running, no air moving, running but not removing heat, or removing heat but not moisture. Capture three facts before you touch anything: what the customer observes, what the thermostat indicates, and what the equipment is doing right now.
Then trace intent first: is there a call, are the right terminals energized, is O or B correct for that brand? Then watch the sequence; in cooling, the call, the blower, the contactor, the compressor and fan, pressures separating, coil temperatures stabilizing, condensate starting. The first step that does not happen is your pivot point.
Many “failed parts” are messengers. A float switch is telling you about drainage. Treat every safety as a consequence and ask what condition made the system refuse to continue.
Idea five
Power, control, load, machine
Divide the system into four layers and test them in order: power, control, load, and machine. Power is line and control voltage, including separate heat-strip breakers and missing legs. Control is intent signals, interlocks, boards and sensor plausibility. Load is the conditions and pathways that bring heat to the equipment: airflow, water flow, dirty coils, duct leaks, building pressure. Machine is the compressor, reversing valve, metering device, burner, heat exchanger and circulator.
You do not start with the machine, because that is where expensive guesses live. You reach it after the other three are proven, and then it is a conclusion, not a gamble.
And change one variable at a time. Fix the airflow, then re-read the cycle; fix heat rejection, then re-read head pressure. If a correction does not move the story toward consistency, you learned it was not the cause. Then prove repeatability and document what normal looks like now.
Step two
Work it with your hands on it
The Story Check. Enter the saturation temperatures you would read from your gauge scale, the line temperatures from your clamps, and the manufacturer’s targets. The bench computes superheat and subcooling the chapter’s way. It will not interpret anything until the system has stabilized and the airflow is proven, and it never tells you to add or remove refrigerant. One rule is the bench’s own, not the chapter’s: within 2°F of the target counts as near target.
Has the system run long enough to stabilize?
Has the airflow been verified?
Hands on it, off the screen. Before the next service visit to your home, write down three facts the way the chapter does: what you notice, what the thermostat shows, and what the equipment is doing at that moment. Include when it happens.
Then look at the thermostat or control board for a fault history or error code legend, and note what it says without clearing anything.
Step three
Prove you understood it
One question per idea, a new situation every time. Miss one and you are sent back to the idea it was testing.
All five solid.
You can turn pressures into temperatures, compute and read superheat and subcooling without single-number rules, use digital tools without trusting their confidence, define a problem before touching it, and test power, control, load and machine in order. Next: back to the class for lesson eleven.
The HVAC Apprentice’s Field Guide
Lesson ten of twelve, from chapter ten. Written by our founder, Dr. Gene A Constant, and donated to the Foundation. Published by Global Sovereign University Press.
Buy a copy — it funds a free seatGSU is a 501(c)(3) nonprofit and book sales are its only income. A purchase is not a tax-deductible donation. This lesson is free and always will be.