The fastest way to troubleshoot a PLC fault is to make the equipment safe, observe the symptom, read the controller's diagnostic buffer, and then prove each link in the chain (sensor, input module, logic, output module, actuator) with a measurement rather than a guess. HSE's GS38 guidance on electrical test equipment says that, wherever possible, work on electrical systems should be carried out with the system dead, and that dead tests are often as effective as live measurements. Good fault finding is mostly discipline: the engineers who find faults quickly are the ones who follow the same order every time.
What is the best method to troubleshoot a PLC?
Follow the same seven steps every time, because skipping steps is how a ten-minute fault becomes a three-hour one.
- Make it safe. Isolate and lock off before putting hands in a panel (see the safety section below).
- Gather information. What exactly was the machine doing? When did it start? What changed recently? Ask the operator for their exact words, because "conveyor stopped" and "conveyor running but no parts" are different faults.
- Read the alarms. Check active alarms and the alarm history on the HMI or SCADA before touching anything.
- Look at the PLC. Read the status LEDs (RUN, STOP, ERROR, bus fault) on the CPU and I/O modules.
- Read the diagnostic buffer. This is the controller's own log of what went wrong and when.
- Trace the signal chain. Field device, input module, CPU logic, output module, actuator. Confirm each stage independently and stop at the first link that fails.
- Repair, verify, document. Fix the cause, test before returning to production, and record symptom, cause and fix.
How do you read the diagnostic buffer?
Go online with the CPU and open its diagnostic buffer, which lists events such as module faults, communication loss, mode changes and why the CPU went to STOP. Read the most recent entries first. Siemens' S7-1500 system diagnostics application note describes system diagnostics being displayed in the CPU display, TIA Portal, HMI devices and the CPU's built-in web server, and says the diagnostic buffer can be read from the CPU web page without an engineering tool. That is handy when you are on site without a laptop licence.
On Siemens hardware the module LEDs also tell you a lot before you open software: a CPU in RUN or STOP, error indicators, and channel LEDs that show whether a signal is present at each input or output. Rockwell controllers have equivalent indicators and a fault log in the controller properties. The principle is the same on every brand: read what the controller already knows before you start measuring.
How do you check inputs and outputs with a multimeter?
Test the I/O in the same order the signal travels, and measure at each stage so you know exactly where it stops. For a 24 V DC digital input, check the sensor has power, actuate it, and measure the voltage at the input terminal against the common (0 V) terminal; the input LED should light when the voltage is present. For an output, check the LED, then measure at the output terminal and at the actuator.
| Stage | What to check | If it is wrong |
|---|---|---|
| Field device | Supply voltage present, sensor correctly positioned, switching when actuated | Replace or realign sensor, check cable |
| Input module | Channel LED lit, voltage at terminal matches the field state | Check wiring, common, module fault in diagnostics |
| CPU logic | Input tag follows the field; output tag follows the logic | Look for interlocks not satisfied, forced values, logic error |
| Output module | Output LED lit, voltage at terminal | Check fuse, relay or transistor output, external supply |
| Actuator | Voltage reaches the coil or drive, device moves | Check cable, overload, mechanical fault |
HSE's GS38 guidance covers the test equipment itself: probes, leads and the correct use of instruments on low-voltage systems. Use a meter rated for the environment, with good leads, and follow your site's prove-test-prove routine so you know the meter works. You can rehearse the technique safely in the free multimeter simulator and electrical wiring simulator, or take the free PLC electrical troubleshooting and maintenance course.
What are the most common PLC faults and their first checks?
Most faults fall into six categories, and the first check usually settles which one you have.
| Symptom | Likely causes | First check |
|---|---|---|
| CPU in STOP | Programme error, hardware fault, power supply failure, memory card problem | Diagnostic buffer entry for the STOP |
| Input not registering | Faulty sensor or wiring, wrong module configuration, module failure | Voltage at the input terminal and channel LED |
| Output not activating | Blown fuse, relay or transistor failure, interlock not satisfied | Output LED, then voltage at the terminal |
| Communication lost (remote I/O, HMI) | Damaged cable, IP address conflict, failed switch | Link lights, then IP and device names |
| Dead or restarting PLC | Failing 24 V DC supply, loose terminals, UPS fault | Measure the 24 V rail under load |
| Intermittent or odd behaviour | Logic bug, scan time creep, environmental causes | Reproduce it and watch tags online |
For network faults, our PROFINET guide explains the diagnostics you will use. For scan time problems, compare the current figure against a baseline you recorded when the machine was healthy.
Is it safe to force I/O?
Forcing overrides the programme, so only do it with authorisation, a risk assessment and a clear plan to remove the force afterwards. A forced output can move equipment that the logic would have held back, so never force anything that could injure someone, and never use forcing to defeat a safety function or interlock. Record every force you apply and remove it before handing the machine back. Watch tables and online monitoring give you most of what you need without forcing anything.
What safety rules apply when troubleshooting?
Isolate, lock off, prove dead, and work to a permit where one is required. HSE's guidance on making equipment safe says it is important to ensure there is no chance a source of energy can be deliberately or inadvertently reconnected, which can be achieved by applying a lock to each isolation device, with the person doing the maintenance holding the keys. Warning notices go at the points of isolation, and conductors should be proven dead using appropriate test equipment before work starts on or near exposed conductors.
HSE's maintenance guidance adds that machines should be locked off where there is a chance the power could be accidentally switched back on, and that formal systems of work such as a permit to work are required in some cases to manage high-risk maintenance. Under the Provision and Use of Work Equipment Regulations (PUWER), maintenance must be carried out safely. Americans call this lockout/tagout (LOTO); in UK workplaces you will usually hear lock-off or safe isolation, but the principle is the same. Our electrical safety guide covers the UK regulations in more detail.
How do you find intermittent faults?
Treat intermittent faults as a data problem: capture evidence until the pattern shows. Trend the relevant variables for 24 hours and look for patterns, such as a fault that always appears at the start of a shift. Add temporary diagnostic logic that records a timestamp and a snapshot of key states when the fault occurs. Check environmental causes (temperature, humidity, vibration, electrical noise) and scheduled events such as backups or maintenance jobs that coincide with the fault. Watch CPU load and scan time, because intermittent scan time extensions can point to communication or memory issues.
What should you keep in a fault log?
A personal fault log turns every breakdown into future speed. Record the date, plant, symptom, diagnostic evidence, root cause, fix and notes. Over time you will recognise patterns, such as the same network glitch at the same time of day, and solve them in minutes. Keep manufacturer diagnostic manuals and hardware catalogues with LED meanings to hand, and build your own checklists as you learn.
How EDWartens can help
The EDWartens UK Professional Module is a five-day live online class in Siemens TIA Portal. Days one and two cover the TIA Portal environment, S7 hardware, ladder logic and simulation and testing, so you practise going online and monitoring logic in PLCSIM rather than on a physical rig. The course is online and Siemens-focused, and it does not replace hands-on time with real equipment on site. For free practice, use the PLC simulator and the lab simulators above. Details are on the Professional Module page, and you can sign up to reserve a seat. If you are preparing for interviews, our PLC interview questions include troubleshooting scenarios.
