PLC Automation Troubleshooting

PLC troubleshooting is about separating three layers quickly: the field device, the I/O module and the program. Interviewers ask what you do when an output will not energise, when an input LED is on but the program does not see it, when a 4-20 mA signal reads wrong or when the CPU goes to fault. The 70 questions below cover inputs and outputs, analog signals, memory and faults, communication and safe forcing. We add how the rounds run, a revision list, three worked examples and the mistakes that candidates make when they go straight to the program.

Original EngineerX flowchart: PLC system: output not energising. Follow the numbered checks in order; a “No” sends you back to widen the search.

How PLC automation troubleshooting interviews usually run

Basics — scan cycle, I/O types, ladder logic and a typical control panel.
Fault scenario — a device does not respond and you give the order from field to program.
Analog and scaling — 4-20 mA signals, raw counts and engineering units.
Safe practice — forcing, bypass, backup of the program and change control.

Concepts and readings to revise first

Digital I/O: sourcing and sinking, module LEDs and field wiring.
Analog I/O: 4-20 mA, 0-10 V and wire break detection.
Scan cycle and logic: why the order of rungs and latching matter.
CPU faults: battery, memory, watchdog and diagnostics buffer.
Communication: Ethernet, Profibus or Modbus link problems.
Power supply: 24 V DC supply quality and grounding.
Forcing and simulation: when it is allowed and the risk of leaving it on.
Program backup: online and offline versions and documentation.

Showing the first 70 questions free. The complete question bank is available as a PDF below.

PLC Power, CPU & Startup

Q1The PLC is completely dead and the RUN LED is off.

AnswerVerify the incoming control voltage, power-supply output, fuses, terminals, and grounding. Check whether the CPU has entered a fault state. Restore the correct supply and replace a failed fuse or power module only after finding the reason for the failure.

Q2The PLC powers up but remains in STOP mode.

AnswerCheck the CPU diagnostic buffer for the fault code. Inspect the program, memory, configuration, and hardware diagnostics. Correct the reported fault and return the CPU to RUN only after confirming that the machine is safe.

Q3The PLC CPU keeps restarting during machine operation.

AnswerCheck the control supply for voltage dips, loose terminals, excessive electrical noise, and an overloaded power supply. Review CPU diagnostics for watchdog or memory faults. Correct the supply or hardware problem before restarting the machine.

Q4A PLC CPU shows a memory or program fault after power-up.

AnswerRead the diagnostic message and determine whether the problem is program corruption, memory-module failure, or configuration mismatch. Compare the current program with the approved backup and reload the correct program if required.

Q5The PLC goes into fault whenever a large motor starts.

AnswerCheck for control-voltage dips, electromagnetic interference, inadequate power-supply capacity, and poor separation between power and control wiring. Inspect grounding and suppression devices on contactors. Correct the disturbance and verify stable PLC operation.

Q6The PLC loses its program after a power failure.

AnswerCheck whether the program is stored in nonvolatile memory and whether the backup battery, memory card, or retention mechanism is healthy. Replace the failed retention component and reload the approved program if the memory was lost.

Q7The PLC power supply is overheating.

AnswerMeasure the supply output and load current. Check ventilation, cabinet temperature, loose connections, and whether the power supply is operating above its rated capacity. Reduce the load or replace the supply with the correct rated unit.

Q8The PLC CPU reports a watchdog timeout.

AnswerCheck the diagnostic information to identify the program section or task causing excessive scan time. Look for infinite loops, heavy calculations, communication delays, or excessive data processing. Correct the program and verify the scan time.

Q9The PLC starts correctly but stops when an expansion module is connected.

AnswerCheck the module type, rack or network address, configuration, power requirements, and physical connection. Inspect diagnostic LEDs and replace the module only after confirming that the module or wiring is actually faulty.

Q10The PLC intermittently loses its RUN status.

AnswerCheck the diagnostic buffer for recurring faults. Inspect power terminals, grounding, communication errors, watchdog events, and module faults. Record when the fault occurs so the root cause can be correlated with a machine event.

Digital Input & Sensor Faults

Q11A proximity sensor detects a target, but the PLC input LED does not turn on.

AnswerCheck the sensor supply voltage, output type, wiring, common connection, and input-channel voltage. Confirm that the sensor output is compatible with the PLC input. Repair the wiring or replace the sensor only after testing it.

Q12A PLC input remains ON even when the field sensor is disconnected.

AnswerCheck for a shorted input wire, incorrect common connection, damaged input channel, or external voltage entering the circuit. Isolate the field wiring and measure the input terminal to determine whether the fault is in the wiring or the input module.

Q13A push button works intermittently in the PLC program.

AnswerInspect the push-button contacts, terminal tightness, wiring continuity, and input status while operating the button. If the electrical signal is unstable, repair the contact or wiring. If the field signal is stable but the input is unstable, test the input module.

Q14A limit switch is mechanically operated, but the PLC does not see the signal.

AnswerCheck mechanical alignment, switch travel, contact condition, wiring, and input voltage. Confirm that the switch reaches its electrical switching point. Correct the alignment or replace the faulty switch or cable.

Q15A photoelectric sensor works in manual testing but misses products during automatic operation.

AnswerCheck sensor alignment, sensing distance, background reflection, response time, mounting vibration, and product position. Monitor the PLC input while products pass and adjust the sensor or program timing as required.

Q16A digital input flickers rapidly on the PLC screen.

AnswerInspect for electrical noise, loose terminals, bouncing contacts, unstable sensor output, and poor grounding. Check whether software filtering or debounce is required. Correct the physical cause before adding software filtering.

Q17Several PLC inputs fail at the same time.

AnswerCheck the shared sensor supply, common terminal, input-module supply, fuse, and connector. If all affected inputs share one common circuit, the common supply or wiring is a strong suspect.

Q18A sensor LED is ON, but its PLC input remains OFF.

AnswerMeasure the sensor output at the PLC input terminal, not only at the sensor. Check output polarity, PNP/NPN compatibility, common wiring, and cable continuity. Correct the interface wiring or use the compatible sensor type.

Q19A normally closed safety input is always showing a fault.

AnswerCheck the safety-device contacts, wiring continuity, dual-channel connections, and supply voltage. Look for an open circuit or incorrect reset condition. Do not bypass the safety circuit; repair the identified fault and verify the safety function.

Q20A sensor gives correct signals at slow speed but misses signals at high speed.

AnswerCheck the sensor response time, PLC input filter, scan time, pulse width, and machine speed. Use a faster input or high-speed counter when required. Verify that the sensor produces a pulse wide enough for the selected input hardware.

Digital Output & Actuator Faults

Q21The PLC output is commanded ON, but the contactor does not energize.

AnswerMeasure voltage at the PLC output and at the contactor coil. Check the output fuse, interposing relay, coil voltage rating, wiring, and common connection. Repair the open circuit or replace the failed relay or coil after testing.

Q22A PLC output LED is ON, but the connected solenoid valve does not operate.

AnswerCheck the output voltage at the terminal and at the solenoid coil. Inspect the valve coil, fuse, common wiring, connector, and suppression device. If voltage reaches the coil but it does not operate, test or replace the coil/valve.

Q23A motor starter output remains ON after the PLC command turns OFF.

AnswerCheck whether the output device is mechanically stuck, the contactor has welded contacts, or an interposing relay is stuck. Verify the PLC output status and then isolate the power circuit before inspecting the contactor.

Q24A solenoid output burns out repeatedly.

AnswerCheck the coil voltage, current, duty cycle, switching frequency, ambient temperature, and suppression method. Verify that the output module is rated for the load. Correct the coil or suppression problem rather than repeatedly replacing the output.

Q25A relay chatters when the PLC output is commanded ON.

AnswerMeasure the relay-coil voltage during operation. Low or unstable control voltage, loose wiring, a damaged relay coil, or insufficient suppression can cause chatter. Correct the supply and connections and replace the relay if required.

Q26A digital output module shows an overload fault.

AnswerCheck the connected load current, short circuit, wiring, and output type. Disconnect the load safely and determine whether the fault clears. Verify the load is within the module rating before reconnecting it.

Q27One PLC output channel never turns ON, while the program command is correct.

AnswerCheck the output LED, terminal voltage, fuse, wiring, and load. Compare the channel with a known-good channel where appropriate. If the command and field wiring are correct but the channel has no output, test the output module.

Q28A contactor drops out whenever a nearby valve is switched.

AnswerCheck for voltage dips and electromagnetic interference caused by the valve coil. Inspect coil suppression, control wiring, grounding, and separation from high-power wiring. Add the correct suppression and improve wiring practices where required.

Q29A PLC output is turning ON and OFF repeatedly without the operator command.

AnswerMonitor the PLC logic and output status together. Check for a logic condition that is repeatedly becoming true/false, a feedback signal oscillation, or a timer/counter reset. Correct the logic or unstable feedback source.

Q30A pneumatic actuator does not move although the PLC output and solenoid LED are ON.

AnswerCheck whether the solenoid coil is receiving the correct voltage, then inspect air pressure, valve operation, tubing, flow controls, and actuator mechanical condition. If the electrical command is healthy, continue troubleshooting on the pneumatic side.

PLC-HMI & Network Communication

Q31The PLC cannot communicate with the HMI.

AnswerCheck the physical cable, connector, communication port, IP address or station address, protocol settings, and PLC/HMI communication status. Compare the configuration with the approved project and inspect diagnostic messages.

Q32The HMI shows a communication timeout with the PLC.

AnswerCheck network quality, addressing, cable condition, switch ports, PLC scan load, and communication parameters. Verify that the PLC is running and reachable on the network. Correct the network or configuration issue and retest.

Q33A remote I/O station suddenly disappears from the PLC network.

AnswerCheck the station power supply, network cable, connectors, address, termination where applicable, and diagnostic LEDs. Inspect the last healthy device and the first failed device to narrow down the network section.

Q34PLC communication works initially but fails after several hours.

AnswerLook for temperature-related failures, loose connectors, power-supply instability, network errors, memory growth, and excessive communication load. Review diagnostic logs and trend the fault against cabinet temperature and machine events.

Q35Two PLC devices report an IP address conflict.

AnswerIdentify both devices using the same address, isolate one device if necessary, and restore the approved network addressing plan. Update the device configuration and verify communication after the conflict is removed.

Q36The PLC can ping a device, but data exchange still fails.

AnswerCheck the communication protocol, port or service settings, data mapping, device mode, and application-level diagnostics. Network reachability alone does not prove that the required protocol is configured correctly.

Q37Ethernet communication becomes unstable when a VFD runs.

AnswerCheck for electromagnetic interference, cable shielding, grounding, routing, and separation between motor and communication cables. Inspect the VFD and communication grounding practices and correct the physical installation.

Q38A Modbus device is online but its values are incorrect.

AnswerVerify slave address, function code, register address, data type, byte/word order, scaling, and communication settings. Compare the PLC mapping with the device manual and test one known register before correcting the complete map.

Q39A PLC loses communication after replacing a network switch.

AnswerCheck switch configuration, port speed or duplex settings, VLAN configuration where used, device addresses, and cable connections. Compare the new switch configuration with the previous approved configuration.

Q40Only one HMI screen stops updating while the rest of the system communicates normally.

AnswerCheck the tags used by that screen, data-source configuration, screen scripts, PLC addresses, and any communication error associated with those tags. If other HMI data works, focus on the affected tag group rather than the whole network.

Analog Signal & I/O Faults

Q41A 4–20 mA pressure transmitter reads zero even though pressure is present.

AnswerMeasure loop current directly and check transmitter supply, loop wiring, polarity, fuse, terminals, and input-channel configuration. If loop current is correct but the PLC value is zero, verify the analog input scaling and channel configuration.

Q42An analog value is fluctuating rapidly on the HMI.

AnswerCheck sensor stability, cable shielding, grounding, power-supply noise, loose terminals, and analog input filtering. Compare the raw PLC value with the field measurement to determine whether the fluctuation is physical or electrical.

Q43A temperature transmitter reads much higher than the actual temperature.

AnswerCheck sensor type, transmitter range, wiring, polarity, scaling, and input configuration. Compare the raw analog signal with the expected value and verify the transmitter calibration.

Q44A PLC analog output is commanded to 50%, but the control valve remains fully closed.

AnswerMeasure the analog output signal at the PLC terminals and at the valve positioner. Check output range, wiring, polarity, positioner supply, scaling, and valve feedback. Repair the signal path or correct the configuration.

Q45An analog input shows a fixed value even when the process changes.

AnswerCheck whether the transmitter output changes at the field device. Inspect wiring, input channel health, broken conductors, frozen software values, and scaling. A fixed raw signal points toward the field loop or input hardware.

Q46A 0–10 V analog signal is correct at the sensor but incorrect at the PLC.

AnswerMeasure the voltage at both ends of the signal cable. Check common reference, cable resistance, grounding, analog input range, and terminal connections. Correct the reference or wiring issue and verify the reading again.

Q47An analog output becomes noisy when a motor starts.

AnswerCheck cable routing, shielding, grounding, analog common, and separation from motor power cables. Inspect the motor drive for interference and improve signal wiring and filtering if required.

Q48A flow transmitter reaches 20 mA before the expected maximum flow.

AnswerVerify transmitter range, calibration, process conditions, wiring, and PLC scaling. Check whether the transmitter is configured for a different upper range than the PLC program expects.

Q49A PLC analog output is correct in software but the actuator moves in the wrong direction.

AnswerCheck output polarity, actuator command convention, scaling, wiring, and the actuator's direction setting. Correct the interface so that the PLC command matches the required physical direction.

Q50Two analog channels influence each other when one signal changes.

AnswerInspect common wiring, shared references, incorrect terminal connections, grounding, and channel configuration. Check for a short or incorrect common between channels and verify each channel independently.

Program Logic & Sequence Faults

Q51A machine sequence stops at one step and never advances.

AnswerMonitor the step bit, transition conditions, required inputs, timers, counters, and interlocks. Identify which condition remains false. Correct the missing field signal or logic condition rather than forcing the next step.

Q52A cylinder extends but the sequence does not move to the next operation.

AnswerCheck the extend-complete sensor, PLC input status, timer completion, and sequence transition logic. Verify that the sensor changes state at the correct position and that the program uses the correct input address.

Q53A conveyor starts and stops repeatedly without a new start command.

AnswerMonitor the run command, stop conditions, overload feedback, sensor inputs, timers, and sequence bits. Find which condition is toggling and determine whether it is caused by field feedback or program logic.

Q54A timer never reaches its preset value.

AnswerCheck whether the timer enable condition remains continuously true and whether the timer is being reset every scan. Verify timer type, time base, preset value, and program logic around the reset condition.

Q55A counter stops counting after a certain machine speed.

AnswerCheck pulse frequency, input filter, scan time, counter mode, and whether a high-speed counter is required. Confirm that the input hardware can reliably detect the pulse frequency.

Q56The same output is commanded by two different program sections.

AnswerTrace all write commands to the output and identify which routine has control during each machine state. Use a single clear ownership strategy or interlock the commands to prevent conflicting writes.

Q57A motor runs correctly in manual mode but not in automatic sequence.

AnswerCompare the manual and automatic permissives. Check auto-mode interlocks, sequence steps, safety conditions, feedback requirements, and command bits. Identify the exact automatic condition preventing the start.

Q58A machine starts correctly but skips one sequence step.

AnswerReview the transition logic, input timing, step bits, one-shot logic, and scan behavior. Check whether the transition condition is already true before the step becomes active, causing the program to advance unexpectedly.

Q59An alarm clears immediately even though the fault is still present.

AnswerCheck whether the alarm is latched or directly tied to a transient condition. Verify the reset logic and the actual fault feedback. For critical faults, use a suitable latch and require the fault condition to be removed before reset.

Q60A start command is accepted even when a required interlock is not satisfied.

AnswerReview the start logic and all permissive conditions. Check for a bypassed, inverted, or incorrectly mapped interlock. Correct the logic and test the sequence under safe conditions before returning the machine to service.

HMI & SCADA Issues

Q61The HMI shows the wrong status for a motor.

AnswerCompare the HMI tag address with the PLC status bit and verify the motor feedback signal. Check tag scaling or inversion and confirm that the HMI is connected to the correct PLC variable.

Q62An HMI push button does not start the machine, but the physical button works.

AnswerCheck the HMI command tag, write permissions, PLC communication, command logic, and required interlocks. Monitor the PLC command bit while pressing the HMI button to locate where the signal is lost.

Q63The HMI alarm appears, but the alarm history does not record it.

AnswerCheck alarm trigger configuration, acknowledgement settings, historian/database connection, timestamps, and storage capacity. Verify the alarm using a controlled test condition and confirm that it is logged correctly.

Q64SCADA values freeze while the PLC continues running normally.

AnswerCheck the SCADA communication link, OPC or driver status, network connection, server resources, and tag quality. Compare live PLC values with SCADA values to determine whether the issue is communication or PLC logic.

Q65HMI values update slowly after the system has been running for a long time.

AnswerCheck communication load, polling rate, PLC scan time, HMI resources, network errors, and excessive logging. Reduce unnecessary polling or logging after identifying the actual performance bottleneck.

Q66An HMI screen displays communication errors only for one group of tags.

AnswerCheck the data source, tag addresses, device connection, and configuration of that tag group. If other tags work, focus on the affected addresses and their PLC data blocks or registers.

Q67The HMI recipe loads but the machine uses old values.

AnswerCheck whether the recipe values are actually written to the PLC and whether another routine overwrites them afterward. Monitor the PLC variables during recipe loading and trace all writes to the affected parameters.

Q68An HMI numeric value is ten times higher than the field value.

AnswerCheck engineering-unit scaling, decimal placement, raw value conversion, and data type. Compare the raw PLC value with the displayed value and correct the scaling formula.

Q69Acknowledge works on the HMI, but the alarm immediately returns.

AnswerDetermine whether the alarm condition is still active. Check the underlying field signal, PLC alarm logic, and reset/acknowledge separation. Acknowledge should not be treated as fault correction.

Q70A remote HMI cannot connect although the local HMI works.

AnswerCheck the remote HMI network connection, IP address, routing, firewall, server availability, and user permissions. Confirm that the remote device is allowed to access the required PLC or SCADA service.

Three worked fault examples

Example 1: “The program shows the output coil ON but the solenoid does not energise. What do you check?”

Look at the output LED on the module. If the LED is on, the PLC is doing its part and the fault is in the field.
Measure the voltage at the module terminal and at the solenoid. A voltage at the terminal but not at the device points to a broken wire or a blown fuse.
Check the output fuse, the relay or the common supply for that group.
If the voltage is present at the solenoid, the coil may be open or the valve stuck.
If the LED is off while the coil shows ON in the program, check for a module fault or a forced bit.

Example 2: “The input LED on the module is ON but the program does not see the input.”

Check the address in the program. A wrong address is a common cause after a modification.
Look for a forced value or a different instance of the same address in the program.
Check the module and rack configuration against the hardware, and see whether the module is reporting a fault.
Check that the program is in run mode and the scan is healthy.
Compare the online program with the backup to find a recent change.

Example 3: “A pressure transmitter gives 4-20 mA for 0-10 bar. The PLC reads 8 mA. What is the pressure? And what raw value would a 0-27648 analog input show?”

Pressure = (8 − 4) / 16 × 10 = 2.5 bar.
Raw count = (8 − 4) / 16 × 27,648 = 6,912 (the full range is 4 mA = 0 and 20 mA = 27,648).
A reading far below 4 mA, such as 0 mA, does not mean zero pressure. It indicates a broken wire or a dead transmitter.

Common mistakes that cost candidates the job

Going straight into the program before checking the field wiring and the module LEDs.
Leaving a force active after testing.
Not taking a backup before changing the program.
Confusing a broken wire (below 4 mA) with a true zero reading.
Overlooking a weak 24 V supply or a loose common.

Frequently asked questions

Which PLC brand should I prepare?

The brand named in the job advert. The troubleshooting method is the same for all.

Is ladder logic enough?

It is the base. Add basic knowledge of function block and structured text for newer plants.

What is the first step in PLC troubleshooting?

Find out what changed, then check the field device and the I/O LED before opening the program.

Keep preparing

→ Industrial Automation Troubleshooting Q&A → Sensor & Instrumentation Troubleshooting Q&A → VFD & Drives Troubleshooting Q&A → Industrial Robotics Troubleshooting Q&A → All branch-wise interview Q&A (hub)

📚 Buy Full Troubleshooting Q&A PDF — ₹99

You’ve read the first 70 questions here. Get the complete 150-question Troubleshooting Question Bank PDF with all questions and clear answers. One-time price: ₹99.

🛒 Buy PDF – ₹99