Troubleshooting guide · fundamentals
Check the Basics First: The Five Cheap Checks Before You Blame the Expensive Part
Most downtime isn't a mystery. It's an air valve somebody closed, a fuse, a button that got pulled, a lens covered in dust, or a code on a screen nobody read. Check the cheap things first — in a smart order.
Last updated: October 2026 · written and reviewed by a working maintenance professional
There's a pattern on every plant: a crew spends two hours inside the PLC, the drives and the network, and finds that the machine has been telling them the answer the whole time. The expensive explanations are more interesting, so they get checked first. The boring ones are right far more often.
That isn't a reason to skip thinking. It's a reason to run a short, disciplined set of basics first, because each one takes a minute or less and each one removes a whole branch of the tree.
1. Read the fault code and the screen
Before you open anything, read the HMI, the drive display and the PLC fault list. Write down the code before you reset it. Machines record a lot of what they know in those messages, and a reset can wipe it. See Is it the PLC or the field? for how to read what you find.
2. Check the E-stops and safety circuit
A pulled E-stop or an open guard door looks exactly like a dead machine from the PLC's point of view. Walk the machine. Check every E-stop, every pull cord, every guard switch, and reset what's been tripped. The safety relay will tell you if it's seeing a fault — see Safety Relay Won't Reset? Never bypass any of it; find the open device.
3. Check the air (on anything pneumatic)
A cylinder that won't move is blamed on the valve, then the solenoid, then the output — and the supply was closed, or the regulator was turned down, or the filter was clogged. Look at the supply gauge at the machine first. Then trace the chain; we map it in Pneumatic Cylinder Slow or Weak? Remember stored air: lock out and bleed it down before you work on anything.
Reading about it is one thing. Doing it is another.
faultline101 drops you into scenarios like this one where the readings respond to your choices — chase the wrong theory and you'll watch it cost you, exactly like a real callout. You practice the sequence until it's instinct, on equipment you can't actually break.
Module 1 is free, no card required — see how it works.
Works with no signal. Install it on your phone and the whole course — 35 modules, 210 faults — comes with you into the plant.
Try the trainer free4. Check the fuse — and ask why it blew
A control-power fuse is the cheapest protection on the machine and the most common reason a section of it goes dark. Check it de-energized with a meter for continuity, or live by measuring voltage on both sides of it — never judge a fuse by looking. A blown fuse is a symptom: replace it with the same rating, never a bigger one, and if it blows again, find the short or overload that caused it. We cover how a single open link stops everything in ‘Won't start’ is usually one open link.
5. Clean the sensor before you replace it
A photoeye, proximity switch or vision lens covered in dust, oil or film looks exactly like a failed device. Before you swap it, clean the lens and check the alignment. Then confirm the input actually changes state in the PLC. If you still need to prove the device bad, see Is It the Sensor or the Machine?
Two more that belong on the list
- Re-read what was just changed. A parameter entered with the decimal in the wrong place gives ten times the speed, time or setpoint, and everything else tests fine. Whenever a problem starts right after someone entered a value, compare it to the nameplate or the documented setting, one digit at a time.
- A power cycle, with care. Yes, turning it off and on works on latched faults and hung devices. Do it after you've recorded the fault code and only when it's safe to restart the process. If a power cycle fixes it, you still want to know why it latched.
Why the order matters
The order above is cheapest and fastest first: reading a screen, walking to a button, looking at a gauge, checking a fuse, wiping a lens. Together they take minutes. If none of them is the answer you've lost almost nothing, and you've ruled out the failures that account for an embarrassing share of callouts. Then go deeper — and when you do, go deeper with a method, like tracing the circuit by voltage.
Check the basics first. The big red button, the air valve and the two-dollar fuse have been humbling good technicians for decades.
Think you'd have found it faster? Try a real fault scenario free — Module 1, no card, works on your phone.
Try a free fault scenario