How to find the right PLC programme version when a machine stops

A packaging line stops at night, the customer’s technician reads out a serial, and your engineer finds four files named final, final2 and final_new. None of them carries a date, an author or a note about the controller it was loaded into, so the names tell the engineer nothing.

Which file runs in the controller right now, after three site visits by two engineers and one edit by the customer’s own maintenance team? Nobody can say. So the engineer drives two hours to site just to upload from the PLC and compare it by hand against whichever copy looks newest.

That drive repeats whenever the file trail is unclear, whether the customer runs a bottling plant or a textile mill, because nobody can prove which revision is live. The fix is dull but works.

Count where files sit today, from the van laptop to the memory stick taped inside a control cabinet door, because each holds a copy either current or stale. You cannot tell which.

Engineers keep private copies on their own laptops because they do not trust the shared folder, and years of overwritten files and half-finished uploads usually explain why. Clean the folder first. The habit follows the trust.

List every location for one customer, because the real latest version often sits on the laptop of an engineer who has left the firm.

A file name alone is no record. Pair each backup with a small entry naming the project, the machine serial, the PLC model, the engineering software version used to open it and the date.

Add what changed and why in words a different engineer could follow without phoning the author, because the person who wrote the change is unreachable when the fault arrives. Added a conveyor interlock after a jam. Changed a timer on the sealing station. One line, written then, is enough.

Then log each site visit against the same machine and note which revision was left running, since that single line answers the midnight question. Writing it takes thirty seconds.

At site, upload the running programme first and compare it with the stored one, because a match proves you hold the right file. Otherwise someone changed the machine unannounced.

Save the uploaded copy as a new entry marked found on site, and never overwrite your stored revision, because both are evidence and the gap between them matters.

Make your change from the matched file, using the engineering software version that last saved it, since a newer release may refuse to download back to an older controller. Upload again after the fix. Log it before you drive off.

Rules fail when they take long. Keep the routine to four steps, namely upload on arrival, compare, change, then upload and log on departure, and print them on a laminated card for the service bag.

Keep the review light. Pick three machines at random and check that the stored file matches what is running, since any mismatch shows exactly where the habit is slipping.

Five machines are enough to begin. Choose the five you service most often, build their records first, and add the rest of the fleet as each visit puts you in front of the cabinet.