The Control vs the Controlled: Which Is Wrong? A Decision Tree
Why this matters
Almost every system has a brain and a muscle: a control that decides, and a controlled device that acts. A thermostat and a furnace. A pressure switch and a pump. A float and a valve. A board and a motor. When the output is wrong, you have to know which side failed, because replacing the muscle when the brain is broken leaves you exactly where you started. The fastest way to lose an afternoon is to swap the controlled device on a control fault. This tree keeps you honest about which side to chase.
Start here: is the control calling for the right action?
Split the system at the command. Find out what the control is telling the device to do, then compare that to what the device should be doing.
- What is the control commanding right now? Read its output: the signal it is sending, the contact it is closing, the call it is making. For electrical, de-energize and verify dead to make connections, and only take a live command reading when you are set up to do it safely.
- Is that command correct for the conditions? If the space is cold and the control is correctly calling for heat, the control is doing its job. If the space is cold and the control is calling for nothing (or for cooling), the control is wrong.
- Does the device do what it is told? Once you know the command, watch whether the device obeys it. Obeying a wrong command points at the control. Ignoring a right command points at the device.
This single split, "is the command right, and is it being obeyed," sends you down the correct branch almost every time.
Branch 1: the control is wrong (the brain)
The control fails when it commands the wrong thing or commands nothing when it should command something.
- Wrong command for the conditions. It calls for the opposite action, calls at the wrong time, or never calls when it should. Often a bad sensor or input is feeding the control a false picture, so the control "correctly" acts on wrong information. Check the control's inputs, not just its output.
- A setting or calibration is off. The setpoint is wrong, the differential is misadjusted, a schedule or mode is incorrect, the sensor reads off-true. The control is healthy but configured to do the wrong thing.
- The control's output never reaches the device. The command is correct but lost in the wiring, a connector, or a relay between control and device. The brain spoke; the message did not arrive. If the command is correct at the control but absent at the device, the fault is in between, not in either end.
Branch 2: the controlled device is wrong (the muscle)
The device fails when it receives a correct command and still does the wrong thing.
- Correct command, no action. The device is told to run and does not. The contactor is closed, the signal is present, the supply is good, and the motor, valve, or element sits dead. That is a failed device.
- Correct command, wrong action. It runs weak, runs backward, sticks partway, or runs when it should stop. The command is right; the response is defective.
- A measurable internal fault. The device tests out of spec, an open winding, a stuck mechanism, a part below rating. Confirm with a reading before you replace it.
The deciding test: command versus response
| What the control commands | What the device does | Faulty side |
|---|---|---|
| Wrong command for conditions | Obeys faithfully | Control (or its sensor) |
| Correct command | Nothing, or wrong action | Controlled device |
| Correct command at control, absent at device | Cannot obey | Wiring between them |
| Correct command | Correct action, but system still wrong | Neither: look elsewhere (supply, load, mechanical) |
Read the command, then read the response, and the table tells you where to dig. Note the last row: when the command is right and the device obeys correctly but the system still misbehaves, the fault is in neither the control nor the device, and you belong in a different tree (supply, load, or a referred fault).
Working it cleanly
Force a known command and watch the response: command the device on and off and see if it tracks. Inject a correct input at the control and see if it commands correctly. Never replace the controlled device until you have proven the command reaching it is correct, and never replace the control until you have proven the device would obey a correct command. Document which side failed, because "I changed the thermostat and it still does it" is the report you are trying not to write.
References
- See related: The Power Supply vs the Load: A Decision Tree
- See related: Upstream Problem, Downstream Symptom: A Decision Tree
- Trade-standard controls troubleshooting practice (separate command from response)
- Manufacturer documentation for control wiring, sequence of operation, and device specs