A PLC can make a breakdown look sophisticated even when the root cause is simple. The program is best used as a map of machine expectations, not as the first place to make changes.
Five Principles to Use in the Field
- Check controller health first. CPU mode, fault state, module diagnostics, network status, and power supply condition establish whether the controller is actually functioning.
- Use logic as a dependency map. Find the output or sequence step involved and work backward through permissives. The missing condition is often easier to diagnose than the symptom.
- Respect online edits. A code change under pressure can hide the original fault and create a new one. Only change logic when the existing logic is proven wrong and change control permits it.
- Understand forces. A forced input or output can make the screen lie about the physical world. Review force tables and temporary test logic when behavior makes no sense.
- Compare field state to software state. If a sensor is physically ON but the PLC input is OFF, the problem is outside the sequence logic: power, wiring, channel configuration, or module state.
Pressure Mistakes to Avoid
- Downloading a program because the machine is not responding.
- Editing timers to “give it more time” without understanding why the step is late.
- Forcing an output around an interlock.
- Assuming an input indicator proves the sensor is mechanically positioned correctly.
A Practical Breakdown Method
- Confirm CPU, I/O, and network health.
- Locate the affected output, step, or permissive.
- Identify the first false condition preventing progress.
- Compare that software state with the actual field condition.
- Troubleshoot the mismatch in the appropriate layer.
- Only consider logic changes after field conditions and design intent are understood.
Scenario: A palletizer will not cycle. The PLC program shows the sequence waiting for “pallet centered.” The physical pallet is centered, but the input is OFF. The sensor LED is ON, yet the module input is OFF. A broken conductor between the sensor junction and I/O rack is found. No program change is needed.
Train This Before the Next Callout
Choose one critical machine you know and apply the ideas from this chapter while it is healthy. For plc faults without panic, write down the normal sequence, the key evidence you would want to preserve, and the first three checks you would make if the machine stopped. Then compare your plan with the electrical drawings, PLC diagnostics, maintenance history, and the experience of another technician. A ten-minute rehearsal in daylight can remove several minutes of confusion at night.
3 AM Rule: Use the PLC to locate the missing condition; do not use it as permission to rewrite the machine at 3 AM.
Chapter Checklist
- Can I describe the symptom without naming an unproven cause?
- Have I preserved the evidence that could disappear after a reset or restart?
- Do I know which system boundary I am testing next and why?
- Have I kept safety controls and temporary changes visible and controlled?
- Can I explain my current facts, hypothesis, and next action in under thirty seconds?