Main Types of Programmable Logic Controllers: A Complete PLC Guide

Main Types of Programmable Logic Controllers: A Complete PLC Guide

PLCs are industrial computers that deterministically control electromechanical processes via 24 VDC logic, with scan times of 1–50 ms. Choosing the wrong architecture causes I/O bottlenecks, scan overruns, and costly retrofits.

Why PLC Architecture Matters Before You Buy

In our experience, procurement teams often select a PLC based on price-per-I/O alone, then discover six months later that the controller cannot handle a new packaging line because its expansion bus is saturated. This is the most common mistake we see in greenfield projects. PLC architecture is not interchangeable — a compact controller designed for a conveyor sorter is a poor fit for a 12,000-tag wastewater SCADA system, regardless of how attractive the unit price looks.

The IEC 61131 family of standards classifies PLCs by hardware architecture, programming language conformance (61131-3), and communication profiles. When we audit an existing plant, the first question we ask is not "which brand?" but "which architecture class?". The answer determines everything downstream: panel size, cooling strategy, network topology, spare-parts inventory, and the engineer-hours needed to commission.

For a foundational refresher on what a PLC actually does inside a control loop, see What Is a Programmable Logic Controller? How PLCs Work Explained.

Programmable Logic Controller (PLC) is defined as a digitally operating electronic system designed for use in an industrial environment, which uses programmable memory for the internal storage of user-oriented instructions for implementing specific functions such as logic, sequencing, timing, counting, and arithmetic, to control through digital or analog inputs and outputs various types of machines or processes (per IEC 61131-1).

For authoritative requirements on PLC equipment characteristics and testing, refer to the IEC 61131-2 PLC Equipment Standard, which defines the environmental, electrical, and functional criteria every industrial PLC must meet.

The Five Main Types of Programmable Logic Controllers

Across thousands of installations, PLCs fall into five hardware architectures. Each emerged to solve a specific industrial pain point, and each carries trade-offs that no marketing brochure will spell out clearly.

1. Compact (Fixed) PLCs

A compact PLC integrates the CPU, power supply, digital I/O, and often analog channels into a single sealed enclosure. Typical I/O counts range from 10 to 60 points. The Siemens S7-1200 CPU 1214C – 6ES7214-1AG40-0XB0 is a representative example: 14 digital inputs, 10 digital outputs, 2 analog inputs, integrated PROFINET, and a scan-time of roughly 0.085 µs per bit instruction.

Compact units are the workhorses of OEM machine builds — bottling lines, small HVAC plants, conveyor segments, packaging cells. They are inexpensive, fast to wire, and easy to stock as full-unit spares. The downside? Limited expansion. Once you exceed roughly 60–80 I/O, you are forced into a modular architecture or you stack multiple compact PLCs and pay the integration cost in PROFINET or Modbus TCP traffic.

Key takeaway: Choose compact PLCs for fixed-scope OEM machinery where I/O count will not grow more than 20% over the equipment lifetime. Beyond that, modular wins on lifecycle cost.

2. Modular (Rack-Based) PLCs

Modular PLCs separate the CPU, power supply, and I/O into individual cards that mount on a backplane or rack. Siemens S7-1500, Allen-Bradley ControlLogix 5580, ABB AC500, and Schneider Modicon M580 are the dominant platforms. I/O counts scale from 128 to over 30,000 tags depending on CPU class.

What we typically see in the field: modular PLCs dominate process industries — petrochemical, pharmaceutical, water treatment, automotive paint shops. The reason is not just I/O count. It is hot-swap capability, redundant CPU pairs, and the ability to mix specialty modules (high-speed counters, weighing modules, motion controllers, IS barriers for Zone 1) on the same rack. For a deeper teardown of how these modules interact, our colleagues wrote PLC System Components: CPU, I/O Modules, Power Supply and Rack Explained.

3. Rack-Mount Industrial PCs (Soft PLCs)

A soft PLC runs IEC 61131-3 runtime on a hardened industrial PC — Beckhoff TwinCAT, CODESYS Control, Siemens SIMATIC S7-1500 Software Controller. The advantage is computational headroom. We deployed a Beckhoff CX2042 in a steel rolling mill last year that handled motion control on 32 axes, MES communication via OPC UA, and vision processing on a single quad-core CPU. A traditional hardware PLC would have required three separate controllers.

The trade-off is determinism under Windows or Linux. Real-time kernels help, but a soft PLC requires careful tuning of CPU affinity, interrupt priorities, and thermal design. Not always the right choice for safety-critical loops.

4. Distributed Control Systems (DCS) with PLC Functionality

The line between DCS and PLC has blurred since 2015. Modern systems like ABB 800xA, Emerson DeltaV, and Siemens PCS 7 are essentially networked PLCs with engineering tooling optimized for continuous process control rather than discrete logic. They handle thousands of analog loops, advanced regulatory control, and batch sequencing per ISA-88.

5. Safety PLCs

Safety PLCs (Siemens S7-1500F, Allen-Bradley GuardLogix, Pilz PSS 4000) are certified to IEC 61508 SIL 3 and ISO 13849 PL e. They use redundant processing, diverse instruction sets, and certified function blocks for emergency stop, light curtain monitoring, and safe motion. A safety PLC is not optional in machinery covered by the EU Machinery Directive 2006/42/EC — it is a regulatory requirement when risk assessment demands SIL 2 or higher.

Comparing PLC Types: A Procurement View

Criteria Compact Modular Soft PLC Safety PLC
Typical I/O range 10–60 128–30,000+ Unlimited (license-bound) 16–4,000
Scan time (1k logic) 1–5 ms 0.5–2 ms 0.1–1 ms 5–20 ms
Hot-swap I/O No Yes Depends on hardware Yes
Certification IEC 61131-2 IEC 61131-2 IEC 61131-3 runtime IEC 61508 SIL 3
Typical cost (USD) $300–$1,500 $3,000–$50,000 $2,000–$15,000 $5,000–$30,000
Best fit OEM machines Process plants Motion + vision Machinery safety
Key takeaway: Cost-per-I/O is misleading. Calculate cost-per-tag-over-10-years including spare parts, engineering hours, and expansion headroom. Modular PLCs typically win that math above 200 I/O.

Sizing a PLC: Scan Time, Memory, and I/O Headroom

Engineers often overlook scan-time budgeting until commissioning, when the HMI starts lagging and PID loops oscillate. The fundamental constraint is simple: every input must be read, every rung executed, and every output written within one scan cycle.

Formula: PLC Scan Time Estimation — Source: IEC 61131-1, informative annex

Tscan = Ti/o + (Ninst × tinst) + Tcomm + Tos

Symbol Description Unit
Tscan Total scan cycle time ms
Ti/o I/O image update time ms
Ninst Number of executed instructions
tinst Average instruction execution time µs
Tcomm Communication processing overhead ms
Tos Operating system / housekeeping time ms

A practical rule we apply: design for scan time at 60% of the controller's specified maximum. If your application demands a 20 ms loop, do not size a CPU that achieves 19.8 ms in best-case benchmarks. Real-world overhead — communications, alarms, diagnostics, fault handling — consumes the rest.

Memory sizing follows a similar logic. Allocate 30% headroom on program memory, 50% on data memory if you expect future logging or recipe expansion. For a working primer on internal CPU operation, see What Is a Programmable Logic Controller and How Does It Work.

IEC 61131-3 Programming Languages: Choose Wisely

IEC 61131-3 defines five standardized PLC languages: Ladder Diagram (LD), Function Block Diagram (FBD), Structured Text (ST), Instruction List (IL — deprecated in the 2013 edition), and Sequential Function Chart (SFC). The choice is not religious. It is engineering-driven.

When to use each language

Ladder Diagram remains dominant in North American discrete manufacturing. Maintenance electricians read it natively, and troubleshooting is fast. Use it for interlocks, motor starters, and conveyor logic.

Function Block Diagram excels in process control where signal flow mimics P&ID layout. PID loops, cascade control, and analog scaling read more clearly in FBD than LD.

Structured Text is mandatory for complex math, string handling, recipe management, and any algorithm that would require 200+ rungs in LD. We use ST for batch sequencing per ISA-88, motion profiles, and OPC UA payload construction.

Sequential Function Chart models state machines naturally. Batch reactors, washdown cycles, and startup sequences map cleanly to SFC steps and transitions.

IEC 61131-3 Conformance is defined as compliance with the syntax, data types, and execution semantics specified for the five PLC programming languages, verified by PLCopen certification testing (per IEC 61131-3:2013, Clause 4).

Integration with Field Devices: Contactors, Releases, and Mechanisms

A PLC is only as useful as its ability to drive real loads. In our field experience, the integration layer between PLC outputs and power devices causes more downtime than the PLC itself. Coil voltage mismatches, missing freewheel diodes, and undersized output relays are recurring failure modes.

Consider a typical motor control center retrofit. The PLC digital output (24 VDC, 0.5 A per point on most modules) cannot directly switch a 75 kW motor. Between the output and the motor, you need an interposing relay, a contactor, and often a motor mechanism module for remote racking. The Schneider Electric LC1E40M5 Easy TeSys 3-Pole 40A 440V AC Contactor handles motor loads up to 18.5 kW at 400 V with an AC-3 duty rating, driven by a 220 VAC coil that can be sourced from the PLC via an interposing relay or a 24 VDC coil variant.

For circuit breaker integration in switchgear, remote tripping and closing are coordinated through shunt releases. The ABB 1SDA073687R1 YC E1.2..E6.2-XT7M 220-240 VAC/DC Shunt Closing Release allows PLC-commanded closing of Tmax XT7 frame breakers, essential for automated tie-breaker operation and load shedding schemes per IEEE 1547.

For motor-operated breakers in NSX frames, the Schneider Electric LV429434 MT250 Motor Mechanism Module Compact NSX Series provides remote charge and close functions, controlled by the same PLC outputs that orchestrate the rest of the substation logic.

Key takeaway: Always specify interposing relays between PLC outputs and inductive loads above 0.3 A. Direct switching shortens output module life and can violate the manufacturer's published L/R time constant limits.

Common Field Failures and How to Avoid Them

Some engineers argue that PLCs "never fail" — and statistically, MTBF figures of 50–100 years for modern CPUs support that view. But the system around the PLC fails constantly. Here is what we typically see.

Power supply degradation

Switching power supplies feeding the PLC backplane lose capacitance over 7–10 years. Voltage ripple climbs from 50 mV to 200 mV, and the CPU starts logging intermittent faults. Replace 24 VDC supplies on a 7-year preventive cycle in continuous-duty plants. Not negotiable.

Ground loops on analog inputs

A 4–20 mA signal that reads correctly on a multimeter but jitters on the PLC almost always points to a ground loop. The fix is single-point grounding per IEEE 1100 (Emerald Book) and isolated analog input modules where field instruments share a different ground reference.

EMC-induced false trips

VFDs without proper shielded cable termination radiate noise that triggers false digital inputs. We have measured 8 V common-mode transients on 24 VDC input lines next to a 110 kW VFD with ungrounded shields. The remedy: 360° shield termination at both ends, ferrite cores on suspect lines, and twisted-pair cabling per IEC 61000-6-2.

Firmware version drift

A spare CPU pulled from stores after five years almost certainly runs a firmware version incompatible with the current project file. Maintain a firmware register for every controller and validate spares match production before they hit the panel.

Brand Selection: Siemens vs. Allen-Bradley vs. Schneider vs. ABB

Honest answer? Brand choice is 30% technical and 70% ecosystem. The technical differences between an S7-1500, a ControlLogix 5580, an M580, and an AC500 V3 are genuinely small for 90% of applications. What differs is the engineer base in your region, the integrator network, the spare-parts logistics, and the existing installed base in your plant.

In Europe and Asia, Siemens dominates roughly 45% of new installations. In North America, Rockwell holds a similar share. Schneider is strong in water/wastewater and infrastructure. ABB leads in marine, mining, and heavy process. Pick the platform your maintenance team already knows, unless a specific technical requirement forces a change.

Ready to Source Programmable Logic Controller?

Frequently Asked Questions

What are the five main types of programmable logic controllers?

The five main PLC types are compact (fixed) PLCs, modular rack-based PLCs, soft PLCs running on industrial PCs, DCS-class controllers with PLC functionality, and safety PLCs certified to IEC 61508 SIL 3. Each addresses different I/O scale, determinism, and certification requirements. For deeper context, see What Is a Programmable Logic Controller? How PLCs Work Explained.

How do I choose between a compact and a modular PLC?

Use compact PLCs for fixed-scope machines under 60 I/O with no expansion plans. Choose modular PLCs when I/O exceeds 200 points, when hot-swap is required, or when specialty modules (motion, weighing, IS barriers) are needed on the same backplane. Lifecycle cost favors modular above 200 tags.

What is the difference between a PLC and a DCS?

Historically, PLCs handled discrete logic and DCS handled continuous process control. Today the boundary has dissolved — modern controllers like Siemens PCS 7 or ABB 800xA share PLC hardware but use process-oriented engineering tools, libraries, and operator interfaces optimized for hundreds of analog loops and ISA-88 batch control.

Are safety PLCs required by law?

In the EU, machinery covered by Directive 2006/42/EC must meet risk-assessed safety integrity. When the assessment yields PL d or PL e per ISO 13849-1, or SIL 2/SIL 3 per IEC 62061, a certified safety PLC or hardwired safety relay is required. Standard PLCs cannot be used for safety functions regardless of programming care.

What scan time should I target for motion control?

Coordinated motion typically requires 1–2 ms scan times for the motion task, with deterministic jitter under 100 µs. Logic tasks can run at 10–20 ms in parallel. Soft PLCs and dedicated motion controllers (Beckhoff, B&R, Siemens Technology CPUs) usually outperform general-purpose modular PLCs in this domain.

How long does a modern PLC last in continuous service?

The CPU itself often runs 15–20 years. Power supplies and electromechanical relay outputs degrade earlier — typically 7–10 years. Plan obsolescence around firmware support windows from the manufacturer; Siemens, Rockwell, and Schneider publish lifecycle phases (active, mature, end-of-sale, end-of-support) that should drive your migration roadmap.

Can I mix PLC brands on the same network?

Yes, through open protocols — PROFINET, EtherNet/IP, Modbus TCP, and OPC UA all support multi-vendor architectures. The practical challenge is engineering complexity: each platform requires its own programming software, separate spare-parts inventory, and engineers trained on multiple toolchains. We recommend single-vendor architectures for new builds and only mix brands when a specific technical or commercial constraint forces it.

Conclusion: Match the Architecture to the Mission

There is no universal "best" PLC. There is only the right architecture for the application, the team, and the lifecycle horizon. A compact PLC running a packaging line for ten years can deliver lower total cost than a modular system three times its capacity. A safety PLC is non-negotiable when human life is in the loop, regardless of budget pressure. A soft PLC unlocks computational density that no traditional controller matches — but only if your engineering team has the discipline to manage real-time tuning.

The procurement decision should follow the engineering analysis, not lead it. Start with the I/O list, the scan-time budget, the safety integrity requirements, and the expansion forecast. Then evaluate platforms. Then negotiate price. Engineers who reverse that order spend the next ten years working around decisions made in a spreadsheet.

For the full selection methodology, sizing worksheets, and maintenance protocols across the PLC lifecycle, see our complete Programmable Logic Controller Guide: Selection, Application, and Maintenance for Engineers. When you are ready to specify the field devices that connect your PLC to real plant equipment — contactors, shunt releases, motor mechanisms, and CPUs — Stoklink stocks genuine ABB, Schneider, and Siemens components with verified provenance and lead times suited to industrial project schedules.

Comments (0)

    Leave a comment