Lesson 61 of 78 · PLC Architecture & Sequences
PLC Scan, I/O & Control Architecture
Open alongside this lesson
Project resources
IEC 61131-3:2025 - Programmable Controllers, Part 3: Programming Languages (opens in a new tab)
Use the overview to distinguish ladder, function blocks, structured text, and sequential function charts.
A programmable logic controller is a deterministic industrial computer designed around physical I/O, machine sequencing, communications, diagnostics, and robust lifecycle support. IEC 61131-3:2025 specifies structured text, ladder diagram, function block diagram, and sequential function chart elements 1.
Scan behavior matters
Conceptually the PLC reads inputs into an image, executes logic in order, writes output states, services communications and diagnostics, then repeats. Immediate I/O, tasks, interrupts, motion systems, and distributed devices complicate this model, but the scan remains a useful timing foundation.
If a photoeye pulse lasts 4 ms and the worst-case task plus I/O update path is 12 ms, the event may be missed. Use hardware capture, a faster task, pulse stretching, or a sensor protocol designed for the requirement. “The PLC is fast” is not a timing analysis.
I/O list as contract
For every point record tag, device, location, type, electrical range, normal and safe/fault state, update requirement, scaling, filter, alarm, terminal, drawing reference, and test method. Distinguish command from proof: Conveyor_RunCmd is not Conveyor_RunningFb.
Architecture layers
Field devices sense and act. PLC and motion controllers execute deterministic control. HMI/SCADA supervises and records. MES coordinates operations. ERP plans business resources. ISA-95 gives a technology-neutral vocabulary for these boundaries 2. Do not let a slow business-system outage directly destabilize essential local control.
OT constraints
NIST notes that operational technology interacts with the physical world and has distinct safety, reliability, and performance requirements 3. Manage accounts, change control, remote access, backups, network segmentation, time, and asset inventory without treating a PLC as an ordinary office endpoint.
Architecture artifact
Draw the control architecture for a two-station cell. Add update times, ownership, network boundaries, local behavior during link loss, data retention, and which functions must remain available offline.
Source trail
References
- 1IEC 61131-3:2025 - Programmable Controllers, Part 3: Programming Languages. International Electrotechnical Commission. 2025. verifiedCurrent syntax and semantics for structured text, ladder diagram, function block diagram, and sequential function chart organization. Cited at: language suite.
- 2ISA-95 - Enterprise-Control System Integration. International Society of Automation. verifiedTechnology-neutral models for equipment hierarchy, manufacturing operations, and the interfaces among plant control and business systems. Cited at: levels and interfaces.
- 3NIST SP 800-82 Rev. 3 - Guide to Operational Technology Security. National Institute of Standards and Technology. 2023. verifiedSecurity guidance for OT systems, including PLC, DCS, SCADA, physical-process interactions, reliability, performance, and safety constraints. Cited at: OT scope.
Check your understanding
- What is the usual conceptual PLC scan order?
- Read inputs execute logic update outputs and perform system tasks
- Update outputs once per month
- Read no sensors
- Execute every rung simultaneously in physical time
Controllers commonly form an input image, solve the program, update outputs, handle communications and diagnostics, then repeat.
- Why document signal fail state?
- A broken wire or lost network must lead to defined detectable behavior
- It changes wire color
- It eliminates validation
- Signals never fail
The architecture must distinguish healthy off from channel failure when consequences require it.