PLC Block Diagram: CPU, I/O, Memory & Scan Flow
Read a PLC block diagram from field inputs through modules, CPU, memory, communications and outputs. Includes scan flow, architecture variants and a planning worksheet.
A PLC block diagram shows how field inputs pass through input modules to the CPU, how the CPU executes a program stored in memory, and how calculated states pass through output modules to actuators. Power, communications, diagnostics and engineering software surround that core input–process–output path.
The diagram is conceptual. The exact backplane, terminal, power and memory arrangement depends on the controller family. Use it to understand ownership and data flow, then use the current manual for the selected hardware.
Download the PLC architecture planning worksheet (CSV)
PLC block diagram at a glance
| Block | Primary job | Design evidence | Common failure |
|---|---|---|---|
| Power supply | Provide controller/backplane power | power budget and supply specification | undervoltage, overload, wrong grounding |
| CPU | Execute tasks, communications and diagnostics | exact catalog/firmware and execution estimate | watchdog, major fault, overload |
| Memory | Store program, tags, configuration and retained data | memory estimate and retention plan | capacity exhaustion, stale retained state |
| Input modules | Isolate and convert field signals into controller data | I/O list and module wiring diagram | wrong common, channel mode or scaling |
| Output modules | Convert controller decisions into field switching/signals | load schedule and output rating | inrush, short circuit, leakage or wrong voltage |
| Communications | Exchange data with I/O, HMI, drives and other controllers | network architecture and message ownership | duplicate address, loss, stale data |
| Engineering interface | Configure, download, monitor and archive | approved software/version and backup | wrong project/revision or uncontrolled online edit |
1. Power-supply block
A PLC needs a compatible power source for the CPU and system bus. Some compact controllers contain an integrated supply; modular systems may use a dedicated chassis or bus supply. Field devices and output loads often need separate power even when their modules receive backplane power.
The block diagram should distinguish:
- incoming mains or 24 VDC;
- controller/backplane power;
- field input power;
- output/load power;
- isolated supplies and commons;
- protective earth and functional-earth connections;
- redundancy, UPS or hold-up requirements.
Do not infer terminal wiring from a block arrow. Verify conductor protection, isolation, inrush, permissible supply range and grounding in the exact product documentation.
2. CPU block
The CPU contains the processor and system functions that schedule logic, handle communications, update I/O, diagnose faults and manage memory. A “faster CPU” is not automatically a better design. Selection should start with the required I/O, tasks, motion, safety, network nodes, data handling, execution time and lifecycle.
CPU behavior is organized differently across platforms:
- a small PLC may expose one cyclic program;
- IEC 61131-3 systems may use tasks and program organization units;
- Siemens projects use organization blocks, function blocks, functions and data blocks;
- Logix controllers use tasks, programs and routines.
The block remains the same even when the software vocabulary changes: a scheduler decides what logic executes, when it executes and what happens if execution exceeds its limit.
3. Memory block
PLC memory is not one generic bucket. A design may include:
- nonvolatile project and firmware storage;
- working memory for logic and data;
- input and output process images;
- retained or retentive values;
- diagnostics and fault history;
- recipe, alarm, historian-buffer or communication data;
- removable media for backup or transfer.
Retention needs deliberate ownership. A production count may need to survive power loss; a momentary start request usually should not. After a restart, the program should establish a defined state rather than allowing every old Boolean value to resume unquestioned.
4. Input-module block
Input modules translate field conditions into data the CPU can use.
Digital inputs
A digital input detects an on/off electrical state. The module still needs the correct voltage family, sourcing/sinking arrangement, common, input delay and wiring protection. A physically normally closed contact does not guarantee the PLC Boolean is false in the healthy state; document the electrical and logical conventions separately.
Analog inputs
An analog input converts current, voltage, resistance or another measured signal into a numeric value. Configuration covers channel mode, range, filtering, raw counts, engineering scaling, open-circuit behavior and diagnostics.
Specialty and network inputs
High-speed counters, motion feedback, thermocouple, RTD and safety modules may process signals differently from ordinary cyclic I/O. Remote I/O adds network update behavior, connection status and stale-data handling.
5. CPU scan and process images
A simplified cyclic scan is:
- read physical inputs or update the input image;
- execute scheduled program logic;
- write the output image to physical outputs;
- perform communications, diagnostics and housekeeping;
- repeat.
That sequence is a learning model, not a universal timing promise. Some platforms update modules asynchronously, use immediate I/O instructions, schedule periodic/event tasks or exchange network data independently of the continuous task.
The design question is therefore not only “what is the scan time?” It is:
- when is each value produced;
- when is it consumed;
- how old may it be;
- what indicates valid/invalid data;
- which task owns the output;
- what happens on communication loss or task overrun?
6. Output-module block
Output modules convert controller state into electrical action.
| Output type | Typical role | Critical check |
|---|---|---|
| Relay | AC/DC switching with physical contact isolation | contact voltage, current, inrush and life |
| Transistor | Fast DC switching | sourcing/sinking type, leakage and inductive suppression |
| Triac | AC switching | leakage, minimum load and zero-cross behavior |
| Analog current | 4–20 mA command | loop power, burden, fail direction and scaling |
| Analog voltage | 0–10 V or similar | reference/common, impedance and noise |
| Network command | drive, valve island or remote output | connection status, ownership and timeout state |
An output command is not a safety function merely because logic turns it off. Safety-related risk reduction requires the approved architecture, components and validation process.
7. Communications block
Communications connect the controller to remote I/O, HMIs, drives, robots, vision systems, SCADA, historians and other controllers. The block diagram should show more than a protocol name.
Record:
- physical port and medium;
- device/connection owner;
- producer and consumer;
- cyclic rate or requested update;
- command/status handshake;
- data validity and heartbeat;
- timeout and fallback behavior;
- security zone and routed boundaries;
- diagnostic location.
A network arrow without ownership creates hidden coupling. A useful block labels who commands, who acknowledges and what both sides do when the connection disappears.
8. Compact, modular and distributed variants
Compact PLC
CPU, power and some I/O share one body. Expansion modules attach locally. This reduces footprint but does not remove the need for I/O, power and network planning.
Modular PLC
Power, CPU, communications and I/O occupy selected chassis or bus positions. The engineer sizes slots, bus power, spare space and module compatibility.
Distributed architecture
One or more controllers own remote I/O and intelligent devices over industrial networks. The physical signal path can be short while the logical command path crosses several blocks. Network loss and ownership become first-class design states.
Worked example: conveyor cell
Assume a conveyor has a photoelectric sensor, motor starter, run feedback, jam switch and HMI.
| Block | Conveyor implementation |
|---|---|
| Input | photoeye, jam switch, run feedback and stop-circuit status |
| CPU logic | mode manager, permissive evaluation, start/stop state and timers |
| Output | starter or drive run command |
| Communications | HMI commands/status and upstream/downstream handshake |
| Memory | accumulated runtime and alarm history retained; momentary commands non-retained |
| Diagnostics | input state, output command, feedback timeout and communication health |
The critical distinction is command versus proof. The CPU may set the output command, but run feedback proves whether the physical machine responded.
Architecture review checklist
- Every field signal maps to one approved I/O-list row.
- Power blocks distinguish system, field and load power.
- The CPU/firmware and engineering-software versions are explicit.
- Retained data is intentional and has restart behavior.
- Tasks and data producers have one owner.
- Remote values include validity and timeout behavior.
- Output ratings cover steady current and inrush.
- Safety functions reference the approved safety design.
- Downloads, online edits and backups follow revision control.
- FAT/SAT tests trace to each important block and interface.
Primary references
- Siemens Industry Support, S7-1200 system manuals and module wiring documentation.
- Rockwell Automation, programmable-controller technical literature library.
- IEC, IEC 61131-3 programmable controller programming languages.
