PLC Programming

PLC programs you can trust: a known master copy of every controller, written programming standards, IO lists, version control, simulation before site, safe online edits and clean go-lives.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for PLC Programming, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help you organise your own work. It does not replace your professional judgement, the rules of your regulator or professional body, your firm's policies, or advice from a qualified lawyer, accountant or other adviser. Where a law, code or standard applies, use the current official version for your country, and get qualified sign-off on regulated or safety-critical work.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

🔧 Engineering Practice

PLC Programming

Programming PLCs for machines and plants: ladder logic and structured text, input and output lists, sequence logic, simulation, version control and testing before going live.

  1. PLC and firmware inventory for the site
  2. Trusted master copy of every running program
  3. Written PLC programming standard
  4. Machine IO list as the single source
  5. Functional specification for a machine sequence
  6. Programming laptop and software environment
  7. Version control for PLC projects
  8. Simulation bench for testing logic offline
  9. Rules for online edits on running machines
  10. Monthly running program comparison
  11. PLC change log and weekly review
  12. Controller health and diagnostic check
  13. Forced IO register and Monday check
  14. Spare controllers and modules with matching firmware
  15. Peer code review before download
  16. Firmware and vulnerability advisory watch
  17. Programming toolchain upkeep
  18. Fault call-out log and monthly review
  19. Documenting legacy logic one routine a week
  20. Ladder logic fundamentals and the scan cycle
  21. Structured text for calculations and data
  22. Sequence logic with steps and state machines
  23. Timers, counters and edge cases that bite
  24. Analogue scaling and signal fault handling
  25. Remote IO and drives on industrial Ethernet
  26. Fault-finding through someone else's code online
  27. Reusable function blocks for motors and valves
  28. Choosing a PLC platform for a new machine
  29. Site device library for motors, valves and drives
  30. First-out fault capture in the PLC
  31. Task structure and scan time review
  32. Refactoring a legacy program into clear routines
  33. Parameter tables instead of hard-coded values
  34. Obsolete PLC migration and code conversion
  35. Simulation test run of a new machine program
  36. PLC IO check-out on a new machine
  37. Go-live of a new PLC program
  38. Planned online change during production
  39. PLC code and documentation handover package
  40. First 90 days as a plant PLC programmer
  41. From maintenance electrician to PLC programmer
  42. Integrator programmer on a customer's site
  43. Inheriting an undocumented program
  44. Sole PLC engineer on a small factory
  45. Remote PLC support with someone on site
  46. Safety PLC programming under the safety manual
  47. Batch phase logic to ISA-88
  48. PackML state model for a packaging machine
  49. Motion control with PLCopen blocks
  50. Automated unit tests for PLC function blocks

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

PLC and firmware inventory for the site

Before anyone can say which program is running where, someone has to list every controller on site with its make, model, firmware revision, programming software version and network address. Plants routinely discover a forgotten controller in a packaging line panel only when it fails, and the firmware revision decides which software version can even go online with it.

First tasks

  • Start a register with columns for panel, controller, firmware, software and machine
  • Walk every control panel on one area and record each controller you find
  • Read firmware revisions online from each controller and update the register
  • Flag controllers on platforms the vendor has retired
  • Refresh the PLC register against a panel walk-down @recurring(yearly)

Trusted master copy of every running program

On most older sites the file on the shared drive is not what is running in the controller, because someone made an online edit years ago and never saved it back. Uploading each running program, comparing it with the stored copy and declaring one master per controller ends the guesswork the first time a breakdown needs a quick fix.

First tasks

  • Agree with operations a time to upload programs from running controllers
  • Upload the program from the most critical controller and store it with the date
  • Run the software compare tool between the upload and the old offline file
  • Write down every difference and who might know why it exists
  • Declare the master copy for each controller in the register

Written PLC programming standard

Three programmers on one site will produce three styles of code unless a standard says otherwise, and the electrician fault-finding at night pays for every inconsistency. A short written standard covering tag names, program structure, comments, fault handling and the IEC 61131-3 languages allowed for which job gives every new routine the same shape.

First tasks

  • Collect any existing client, vendor or company PLC standards that apply
  • Write the tag and routine naming rules with five worked examples
  • Draw the standard program structure and routine call order
  • Send the draft to a maintenance electrician and another programmer for comment
  • Review the programming standard against lessons from the year @recurring(yearly)

Make it yours.

Install PLC Programming, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.