PLC Working Principle: 5 Real-World Examples Updated for 2026

AI Summary

  • A 2026 PLC still runs the input → scan → program → output cycle, but IEC 61131-3:2024 (Edition 4) makes the cycle a publishable runtime model — per-task scan time, retain-tag health, and process deviations are exposed as named tags.
  • The five real-world working examples (conveyor, packaging line, robot cell, water-treatment skid, HVAC retrofit) all map to the same scan loop; only the I/O mix, safety class, and bus protocol differ.
  • Modern examples are 2026 networked: EtherNet/IP, PROFINET, CC-Link IE TSN, and OPC UA Pub/Sub have replaced most point-to-point wiring in greenfield cells.
  • Source the CPU, I/O, and bus module from a single multi-brand distributor — KOEED stocks active and EOL parts across nine brands, with same-day quotes from Moritta@KOEED.COM.

This 2026 Engineering Notes walks through five live PLC working-principle examples, the 2026 scan-cycle update, and the multi-brand BOM sourcing paths.

PLC Fundamentals · Engineering Notes · 2026-06-30

By KOEED Engineering Team · 2026-06-30 · 8 min read · Engineering Notes

The PLC working principle has not changed since the 2024 edition of this article — scan the inputs, run the program, update the outputs, repeat. What has changed is what that loop exposes. In 2026 the same scan cycle that once lit a status LED now publishes per-task execution time, retain-tag integrity, and process deviations over OPC UA Pub/Sub. This Engineering Notes walks through five live working-principle examples and the 2026 update to the scan cycle, I/O mix, and bus wiring.

What changed since 2024

The 2024 version of this article framed the PLC working principle as a four-step loop on a stand-alone controller. The 2026 picture keeps the same four steps but extends each:

  • Standardized scan-cycle semantics. IEC 61131-3:2024 (Edition 4) names the phases (input update, program execution, output update, housekeeping) and aligns them with the OPC UA companion specification methods.
  • Real-time bus is the default. Greenfield cells in 2026 use EtherNet/IP, PROFINET, CC-Link IE TSN, or EtherCAT — point-to-point discrete wiring is reserved for safety and a few legacy machines.
  • Per-task visibility. Modern CPUs (ControlLogix 1756-L8x, SIMATIC S7-1500, MELSEC iQ-R) expose the scan time of every periodic task as a named tag.
  • Safety and standard share the controller. Safety I/O is no longer a separate black box — the same CPU runs the safety task alongside the standard task, which changes the working-principle diagram for any cell with a guard.
  • Edge analytics on the bus. A condition-monitoring service can now score vibration, current, and thermal data inside the same scan window, using the AI Diagnostic Tool as a 24/7 assistant.

The 2026 scan cycle, in four phases

Every example below runs the same four-phase scan. The differences are timing, determinism, and how the bus is wired:

Phase What happens 2026 mechanism
1. Input scan Read sensor and field-bus state into the input image table Discrete and analog modules over EtherNet/IP, PROFINET, CC-Link IE TSN; safety inputs share the same scan
2. Program execution Run user logic, periodic and event tasks, motion and safety IEC 61131-3:2024 task model; published per-task execution time as named tags
3. Output scan Push output image table to physical and bus devices Same bus back to valves, drives, and remote I/O; safety outputs cross-checked against the standard task
4. Housekeeping Communication, diagnostics, retain-tag backup OPC UA Pub/Sub publish of fault buffer, battery health, scan statistics

Example 1 — Conveyor belt with VFD and photo-eye

The simplest example of the PLC working principle is a single conveyor with a photo-eye, a VFD, and a starter. The scan cycle is textbook: read the eye, run the start/stop and jam logic, drive the VFD reference, and repeat. In 2026 the same example adds an Allen-Bradley 1734 POINT I/O block at the belt, an EtherNet/IP tap into the VFD, and a tag that publishes belt speed to the SCADA historian. A typical bill of materials for a 2026 retrofit:

  • CPU: CompactLogix 1769-L30ER or SIMATIC S7-1200 CPU 1214C
  • Inputs: 1734-IB8 (8-point 24 VDC sink) or 6ES7 321-1BH02
  • Outputs: 1734-OB8 or 6ES7 322-1BH01
  • Network: 1734-AENTR or 6GK7 243-1BX30 on EtherNet/IP / PROFINET
  • Drive: PowerFlex 525 or SINAMICS V20 with bus control word

Example 2 — Packaging line with batching counter

A packaging machine uses the same scan cycle, but the program adds a counter and an interlock to a heat sealer. The 2024 example talked about a single counter on a digital input. The 2026 example counts in a high-speed counter module (for example 1734-IK or FX3U-4HSX-ADP) and the count is published as a named tag, so a SCADA dashboard can graph throughput without polling the CPU. The PLC working principle is the same — read, count, decide, output — but the data path is now networked from the high-speed module to the edge.

A typical 2026 packaging BOM uses a Mitsubishi FX3U-32MR base plus a high-speed counter adapter, or an Omron CP1E-N40DR-A for the smaller line. For higher throughput, a CompactLogix 1769-L30ER with 1734-IK and 1734-OB8 runs the same logic at a faster scan rate.

> Tip

When retrofitting a 1990s packaging line, keep the original high-speed counter module and add an OPC UA gateway — that preserves the proven input wiring while making the data publishable to the 2026 SCADA.

Example 3 — Robot cell with safety scanner

A robot cell is the cleanest illustration of the 2026 working principle: the standard task runs the pick-and-place, a separate safety task runs the laser-scanner muting, and both tasks share one CPU. The input scan reads the safety scanner over PROFIsafe or CIP Safety, the program executes both tasks, and the output scan drives the robot, the gripper, and the safety contactors. A typical BOM:

  • CPU: ControlLogix 1756-L73 with safety task, or SIMATIC S7-1500F
  • Safety I/O: 1734-IB8S modules on POINT Guard I/O, or 6ES7 136-6BA00 F-DI
  • Robot: Fanuc R-30iB or Yaskawa MP2300 controller on EtherNet/IP
  • Vision: KEYENCE CV-5000 series over PROFINET

Example 4 — Water treatment skid with redundant CPU

A water-treatment skid is a textbook 2026 example of redundancy in the working principle. Two CPUs run identical programs in parallel; the input and output buses are mirrored through a redundancy module; the scan cycles are bit-for-bit synchronized. When one CPU faults, the second takes over within one scan. The working principle is identical to the stand-alone case — input, program, output, repeat — only the synchronization layer changes. The redundancy module in a 2026 system is typically a 1756-RM2 (Allen-Bradley) or 6ES7 156 (Siemens), and the I/O is on remote EtherNet/IP / PROFINET taps.

Example 5 — HVAC / building automation with mixed-brand bus

A building-automation retrofit is the most common 2026 example of a multi-brand bus on one scan cycle. The PLC reads BACnet/IP from the chiller, Modbus TCP from the VFDs, and a few discrete inputs from the air-handler, and runs the program to balance the loop. A typical BOM is built around a Modicon M340 BMXP342020 CPU or a CompactLogix 1769-L30ER, with a BMXDDI1602 module for the discrete inputs.

Example CPU (2026 typical) Bus KOEED source
Conveyor 1769-L30ER / S7-1200 EtherNet/IP, PROFINET AB / Siemens
Packaging FX3U-32MR / CP1E CC-Link, Modbus Mitsubishi / Omron
Robot cell 1756-L73 / S7-1500F CIP Safety / PROFIsafe AB / Siemens
Water skid 1756-L73 redundant EtherNet/IP DLR ring AB
HVAC M340 / 1769-L30ER BACnet/IP, Modbus TCP Schneider

Reading a 2026 working-principle diagram

Modern working-principle drawings are no longer a single block with arrows in and out. They are typically three layers:

  1. The field layer — sensors, drives, valves, and remote I/O.
  2. The control layer — the CPU, the bus, and the I/O modules.
  3. The publish layer — OPC UA Pub/Sub, MQTT, and the historian.

When the diagram shows the publish layer explicitly, you can be sure the working principle is being documented in the 2026 sense. If the diagram only shows the field and control layers, the documentation is older and the scan statistics are probably terminal-only. For legacy serial payloads, the PLC Hex-to-Float Converter and the Modbus CRC Calculator help decode what the bus is actually saying.

Browse real-time restock records for live stock of Allen-Bradley, Siemens, Mitsubishi, Omron, Fanuc, Schneider, Yaskawa, Panasonic, and KEYENCE modules, or send a sales-record BOM to start a like-for-like quote.

Related on KOEED Blog

Frequently asked questions

Does IEC 61131-3:2024 change the four-step scan cycle?

No — the four steps are unchanged, but Edition 4 names them, aligns them with the OPC UA companion specification, and exposes per-task statistics as named tags.

Can one PLC run a 2026 working example across two brands?

Yes — most 2026 cells mix an AB or Siemens CPU with a Mitsubishi drive, a Schneider remote I/O drop, or a KEYENCE vision system over EtherNet/IP or PROFINET.

Is ladder logic still the right language for a 2026 example?

Ladder logic is still the dominant language for stand-alone cells, but structured text is now preferred for the periodic task that publishes OPC UA Pub/Sub data.

What is the most common 2026 starter BOM for a working example?

A CompactLogix 1769-L30ER with POINT I/O, or a SIMATIC S7-1200 with signal modules — both are in stock at KOEED for a same-week quote.

Where can I source the modules in these examples?

Send the BOM — including any obsolete items — to Moritta@KOEED.COM. KOEED stocks active and EOL SKUs for nine brands.

Building one of these 2026 examples or sourcing a working BOM?

Send your BOM — including any EOL modules — to Moritta@KOEED.COM. Active stock, EOL stock, and cross-references in one quote within 24 hours.

Send My BOM →

KOEED Engineering Desk

Industrial automation editors at KOEED. Writes about PLC working principles, scan-cycle design, and EOL sourcing across Allen-Bradley, Siemens, Mitsubishi, Omron, Fanuc, Schneider, Yaskawa, Panasonic, and KEYENCE. Reach the team at Moritta@KOEED.COM.

Related Articles

Zurück zum Blog