Upstream Problem, Downstream Symptom: A Decision Tree

Why this matters

Most systems are a chain: a source feeds a path that feeds a device that does the work. When the device at the end misbehaves, the natural reflex is to fix the device. But a healthy device fed a bad input behaves badly through no fault of its own. Replace it and the new one fails the same way, because the real problem sits upstream. The discipline that separates a parts-changer from a diagnostician is checking the input before condemning the output.

Start here: is the input good?

Before you touch the failing device, ask what it is receiving.

  • Is it getting the right supply, at the right level, in the right form? Correct voltage, adequate pressure, sufficient flow, clean signal, proper fuel. If the input is wrong, stop testing the device. The fault is upstream. For electrical checks, de-energize and verify dead before working on the supply side, and only re-energize for a live reading when you have set up to do it safely.
  • Is it getting anything at all? A device with no input is not broken; it is starved. No power, no water, no signal, no flow. Trace back to where the supply stops.
  • Is the input steady or intermittent? A supply that comes and goes makes a good device look unreliable. The flakiness is in the feed, not the load.

If the input checks out as correct and steady, then the device itself is fair game. If not, you have already found your direction.

Branch 1: the supply is wrong

When the input is present but out of spec, fix the supply before anything downstream.

  • Low or weak supply. Low voltage, low pressure, restricted flow, a weak signal. Everything downstream underperforms in proportion. The device is doing its best with a starved input. Find the restriction or the weak source.
  • Wrong supply. Reversed polarity, the wrong line on a port, the wrong reference, a crossed connection. The device receives a valid-looking input that is simply incorrect, and it responds wrong.
  • Contaminated or noisy supply. Dirty fuel, debris in a line, electrical noise, air in a hydraulic loop. The supply is nominally present but fouled, and the fouling rides downstream into the device.

Branch 2: the supply is absent

No input means the break is somewhere between the source and the device.

  • If there is nothing at the device, walk back toward the source and find where the supply reappears. The break sits between the last good point and the first dead one. Test at points along the path, not just at the ends, to bracket the break.
  • If a protective device opened, it opened for a reason. A tripped breaker, a blown fuse, a closed safety valve. Reset only after you understand why it tripped, because resetting into an unresolved fault repeats the event or worse.
  • If a switch or control upstream is off or faulty, the device downstream is correctly receiving "off." The fault is the control, not the obedient device.

Branch 3: the device really is the problem

Only after the input is proven good and steady do you turn to the device itself.

  • Good input, bad output. The device receives exactly what it should and still produces the wrong result. Now the fault is genuinely local. Test the device against its spec.
  • A measurable internal defect. A component out of spec, a worn part, an internal blockage, a failed winding. Confirm it with a reading rather than a guess, and you can replace with confidence.

The general rule: test in the direction of flow

Work the chain in order: source, then path, then device. Confirm each stage delivers the correct output before blaming the next stage downstream. The first stage that fails to pass good output forward is your fault location. This keeps you from replacing the last thing in the chain when the first thing in the chain is what broke. Document where the chain failed, because the next tech will be tempted to start at the same wrong end you almost did.

References

  • See related: The Power Supply vs the Load: A Decision Tree
  • See related: Symptom Here, Cause Elsewhere: A Decision Tree
  • Trade-standard troubleshooting practice (test in the direction of supply flow)
  • Manufacturer documentation for required supply specs and circuit or flow diagrams