(The content of this post is intended for consideration by trained service personnel only)
We all start out in the service business thinking we have to learn how to troubleshoot and hoping we will some day. And if we stay in the business long enough, we eventually do. But the fact of the matter is, we didn’t really learn to troubleshoot because the truth of the matter is, you can’t learn to troubleshoot. What we end up learning is how stuff works…
If we were to try to define troubleshooting, the definition could be something like:
Troubleshooting is the process of collecting and analyzing information, then drawing conclusions from the information about how a system is operating.
What we’re doing when we troubleshoot is simply comparing the actual operation of a system to the expected or intended operation of the system. When we see the actual operation is different from the intended operation, we do whatever is necessary to determine the cause for the unexpected behavior. Which usually amounts to making some kind of electrical, pressure or temperature measurements. And the only way we can do that is by knowing what the expected or intended behavior is supposed to be, in the first place…knowing how stuff works.
If you can ever learn what heat pumps and furnaces are supposed to do, and what it takes to make them do it (learn how stuff works), troubleshooting becomes an instinctive, or maybe subconscious, response to an unexpected behavior. There’s nothing to learn about troubleshooting.
Let me illustrate what I’m saying…Say we go on a heat pump service call to investigate a “no cooling” complaint. In order for the system to initiate a “call for cool”, what’s supposed to happen?
We know a switch (or switches) inside the thermostat has to close and send 24 volts to the contactor coil, the reversing valve solenoid (with most equipment brands) and the blower motor control. Then the contactor coil is supposed to “pull-in”, completing the high voltage circuits to the compressor and condenser fan motors. The blower motor control also closes a switch, completing the high voltage circuit to the blower motor and the reversing valve solenoid causes the pilot valve to shift, which in turn results in the main valve shifting. If all that takes place as designed, the compressor motor, condenser fan motor and blower motor start, and the reversing valve directs the refrigerant flow in the right direction.
At that point, the intended/expected operation amounts to the correct or design volume of air being moved by the condenser fan and blower wheel, the compressor pumping the design volume of refrigerant, the reversing valve channeling the refrigerant flow in the right direction and the TXV maintaining the correct amount of liquid entering the evaporator coil. And of course, we confirm whether or not all that has happened simply through visual observations, system pressures and temperature measurements.
If our visual observations tell us the condenser didn’t start, we would logically begin troubleshooting for some electrical issue. The first thing we would do is check whether or not the contactor has pulled in. If not, the troubleshooting process begins with an analysis of the low voltage circuits. We would check for voltage on the “hot” side of the contactor coil. If the meter reads zero, we start “backing up” towards the low voltage source, which is the thermostat in this case, looking for the open circuit.
If the contactor has pulled in, then the high voltage circuits are suspect. We would begin by checking for high voltage at the contactor L1-L2 connections for power coming into the condenser unit. If there was no voltage there, you’d begin “backing up” towards the high voltage source, which is a breaker somewhere in the panel box.
In either case, it is our knowledge and understanding of what is supposed to take place, and our ability to reason through information, that tells us where to check for voltages.
If on the other hand, everything appears to be running, you initially begin the troubleshooting process with the assumption there is some problem with the refrigerant system. We confirm that by measuring system pressures, superheat and subcooling.
The expected behavior of an R-22 system would generate a suction pressure in the 70-80 psi range and a superheat in the 10-15 degree range. If you measured 50 psi and 30 degrees, you’d know something is wrong. If you understand what has to take place in order for the numbers to be 70-80 psi and 10-15 degrees, you would know there is not enough refrigerant entering the evaporator coil. And you would also know that has to be due to an undercharged system, a faulty TXV or liquid line restriction. At that point you have to evaluate the head pressure and subcooling to decide which of those possibilities is the problem. If the head pressure and subcooling are low, the problem is low charge. If the head pressure is in the normal range and the subcooling on the highish side, you know the problem is one of the other possibilities.
But to emphasize my point again, we didn’t learn to troubleshoot the problems…our knowledge of what the heat pump is supposed to do, instinctively led us to follow a logical procedure of observations and measurements, which resulted in a conclusion explaining the unexpected behavior of the heat pump.
And restating what I said earlier, once we learn what heat pumps and furnaces are supposed to do, and what it takes to make them do it (learn how stuff works), troubleshooting becomes an intuitive, subconscious response to an unexpected behavior. You just know what to do, without thinking about it. There’s nothing to learn about troubleshooting.
(The content of this post is intended for consideration by trained service personnel only)