A machine controlled by a PLC is not automatically suffering from a PLC program fault. The program often reports a problem created elsewhere: a missing sensor signal, open safety circuit, failed drive, communications loss or mechanical condition that prevents the sequence from advancing.
Fault finding asks what the control system can see
Structured diagnosis compares the expected machine state with live inputs, outputs, alarms, sequence steps and connected-device status. The objective is to locate the boundary between the command, field signal and physical process.
For example, a conveyor that will not start may be inhibited by an emergency-stop circuit, guard switch, downstream-ready signal, drive fault, overload, missing product condition or permissive held false by another part of the line. Changing logic before identifying the condition can hide the real failure.
A program change is a controlled modification
Editing PLC or HMI software changes how the machine behaves. It therefore needs an agreed objective, a verified current backup, consideration of safety and process consequences, documented change control, testing and an authorised route back into production.
A modification may be appropriate when the operating requirement has genuinely changed, an obsolete component is being replaced, a known software defect is confirmed or an improvement project has been designed. It should not be the default response to an unexplained stop.
Establish the backup position
Before any authorised change, identify the controller platform, exact hardware and firmware, programming-software version and communication method. Uploading from a controller is not always equivalent to possessing a complete, documented source project.
The backup should be named, dated, stored securely and compared with the expected site master. HMI, safety-controller, motion, drive and recipe files may need separate treatment. A rollback plan should state how the previous proven state will be restored if testing fails.
Test the complete sequence
Testing must cover more than the edited rung or function block. Confirm relevant manual and automatic modes, alarms, interlocks, restart behaviour, product flow, communications and failure recovery. Safety functions require appropriate competent assessment and validation.
Record what was changed, why it was changed, who authorised it, the software revision and the results of production testing. Updated drawings, comments and handover records make later fault finding safer and faster.
Information to provide for PLC support
Send the PLC, HMI and drive manufacturers; exact alarms; machine state; recent changes; current backup status; software versions; network symptoms and the production impact. State whether the request is diagnosis, recovery, modification, upgrade or commissioning.
This distinction allows the work to be planned with the correct access, software, controls capability and production authority.
Information to record
- PLC and HMI manufacturer and model
- Programming-software version
- Exact alarm and sequence state
- Verified current source backup
- Recent electrical or mechanical work
- Network and connected-device status
- Agreed change objective
- Safety and process impact review
- Test and rollback plan
- Authorised production handover