What Is a PLC? A Complete Guide to Programmable Logic Controllers

Key Takeaways

• What Is a PLC? PLC (programmable logic controller) is a ruggedized industrial computer that reads field sensors, executes control logic on a repeating cycle, and drives output devices such as valves, solenoids, and motor starters.

• Historical Origins – The first production PLC was the Modicon model 084, built in 1968-69 to a General Motors specification for a solid-state replacement for relay logic.

• Standardized Programming Languages – The current edition of the programming standard, IEC 61131-3:2025, specifies four languages: Structured Text, Ladder Diagram, Function Block Diagram, and Sequential Function Chart.

• Modern Processing Performance – Modern controllers are fast: a Siemens CPU 1516-3 PN/DP executes a typical bit operation in 10 ns and addresses up to 8,192 I/O modules.

• Virtualization and Safety Limits – Virtual PLCs running in containers are emerging, but no vPLC yet supports control tasks faster than 1 millisecond, and none hold the functional safety certifications that hardware PLCs carry.

Introduction

If you are asking what is a PLC, the short answer is that a programmable logic controller is the industrial computer that runs almost every automated machine and process line you have ever walked past. It sits in a control cabinet, reads inputs from sensors, decides what to do according to a program you write, and switches outputs that move the physical world.

The acronym is heavily overloaded, which is worth clearing up before going further. In education, PLC means professional learning community. In UK company law, it means public limited company. In orthopaedics, it means the posterolateral corner of the knee. This guide covers only the industrial controller.

This article explains what is a PLC, what’s inside it, how the scan cycle works, which programming languages the current IEC standard defines, and how to choose the right controller for your application.

What Is a PLC? The Core Definition

The programmable logic controller is a digital industrial computer built for the control and command of machines, automated manufacturing and industrial processes. That framing comes straight from the equipment standard, IEC 61131-2, which covers PLCs alongside programmable automation controllers, remote I/O, programming tools, industrial computers, displays and HMIs. ^[4]

In practice, a PLC does four things on a continuous loop:

1. Reads the state of every connected input device, such as proximity sensors, push buttons, thermocouples and flow meters.

2. Executes your program logic against those input values.

3. Writes the results to its output modules.

4. Handles diagnostics, communications and internal maintenance tasks.

That loop is called the scan cycle, and it is the single most important concept to understand about how a PLC controller behaves. Everything else in this guide builds on it.

PLC vs Relay Logic: Why the PLC Replaced the Control Panel

Before PLCs, machine sequencing used relay logic: physical electromechanical relays wired together along the wall of a control room. The wiring itself was the program, so changing the machine's behavior meant rewiring the cabinet.

PLC collapses that into software. Programmable controllers drastically reduce system downtime for repairs or modifications because changes run on a computer and transfer to the unit within seconds, eliminating the need to manually rewire a massive control panel.

The solid-state switching also draws far less power than energizing a relay coil, and transistors outlast mechanical contacts. ^[9]  Those three advantages, reprogrammability, power efficiency and service life, are why relay panels disappeared from new machine builds.

Recommended Reading: Difference between PLC and DCS: Decoding the Automation Divide  

The History of the PLC

The 1968 General Motors Specification

The PLC was not invented speculatively. It was specified by a customer who was tired of relay panels.

The Hydra-Matic division in General Motors wrote requirements for a "standard machine controller" that had to be a solid-state, computer-like system priced competitively with relay systems, easy to maintain and program using relay ladder logic, and capable of functioning in harsh industrial environments. PLCs needed to be modular so components could be exchanged and the system expanded. ^[10]

The primary role of a PLC is to control machinery and processes. PLC continuously monitors the state of input devices and makes decisions based on a custom program to control the state of output devices. PLCs are often used in factories and industrial plants to control motors, pumps, valves, actuators, and other machinery involved in the production process. 

Dick Morley, Bedford Associates and the Modicon 084

Dick Morley and his company, Bedford Associates, responded to the requirements stated by General Motors. Morley, widely called the father of the PLC, dated the concept precisely: "The programmable controller was detailed on New Year's Day, 1968." ^[10]

The first unit was the Modicon 084, so named because it was prototype number 84. It was presented to GM, described as "very limited success", and the early prototype had only 125 words of memory and ran too slowly, which forced expansion first to 1K and then to 4K of memory.

The very first production PLC, the Modicon Model 084, was built in 1968-69. The original specification called for 16 inputs, 16 outputs and 1 kilobyte of memory space, all intended to be upgradable to some extent. ^[10]

The commercial breakthrough came later, with the Modicon 184 designed by Michael Greenberg and Lee Rousseau, revolutionizing the automation business.

How the PLC Got Its Name?

Two innovators share the title of father of the PLC. Morley, the founding member of the Modicon brand and the main driver of the invention, stands alongside Dr Odo Struger, who worked for Allen-Bradley during the same period and eventually became VP of Technology for Rockwell Automation. ^[9]

Allen-Bradley popularized the PLC name and acronym; until then, the device was simply called a programmable controller. Schneider Electric purchased the Modicon brand in 1977 and again in 1997, and the name survives on current products. Early PLCs met real resistance from electricians who doubted a small embedded processor could replace proven relay logic.

What Is Inside a PLC? Core Components

Central Processing Unit

The central processing unit runs your control logic and enforces the scan-cycle timing. Modern CPUs are considerably faster than the general-purpose reputation of industrial hardware suggests.

Siemens specifies the CPU 1516-3 PN/DP at typical processing times of 10 ns for bit operations, 12 ns for word operations, 16 ns for fixed-point arithmetic and 64 ns for floating-point arithmetic. Those four numbers are the honest way to compare CPUs, because a single headline figure hides how much slower floating-point math is than bit logic.

Memory

PLC memory is split by purpose, not treated as one pool. On the same Siemens CPU, integrated work memory is 1 MB for program and 5 MB for data, while load memory is a plug-in SIMATIC memory card of up to 32 GB.

Retentive memory is a third category, holding values that must survive a power cycle. The CPU 1516-3 PN/DP provides a total retentive data area of 512 KB covering bit memories, timers, counters, data blocks and technological data.

Rockwell takes a simpler approach on the ControlLogix 5580 family, quoting a single user memory figure: the 1756-L83E carries 10 MB of user memory. Once you compare controllers across vendors, check what each memory number includes before treating them as equivalent.

Input and Output Modules

I/O modules are where the controller meets the plant. Capacity here is usually what determines whether a controller fits an application.

The Siemens CPU 1516-3 PN/DP addresses up to 8192 I/O modules, with 32 KB of input and 32 KB of output address area, all of which sits in the process image. Its rack supports up to 32 modules: the CPU plus 31 others.

Power Supply

Industrial controllers commonly standardize on 24 V DC. The Siemens CPU accepts a supply range from 19.2 V to 28.8 V and buffers power or voltage failures for 5 ms, with a typical power loss of 7 W.

That failure buffer time matters more than it looks. It determines whether a brief supply dip causes a controlled ride-through or an unplanned stop.

The Programming Device

The programming device is the workstation running the engineering toolchain of a vendor. It is not part of the running control system, but toolchain version compatibility is a real constraint: the Siemens CPU above requires STEP 7 TIA Portal V14 or later.

Recommended Reading: Types of Industrial Control Systems: Examples and Applications  

How Does a PLC Work? The Scan Cycle

The scan cycle is the repeating loop that gives a PLC its deterministic behavior. It has four stages, detailed as follows:

1. Housekeeping: The CPU runs internal diagnostics, services communication requests, checks memory integrity and updates its own status.

2. Input Scan: The CPU reads every input channel at once and freezes those values into a memory area called the process image.

3. Program Execution: Your program logic runs against the frozen input values, from the first rung to the last, writing results into the output process image.

4. Output Scan: The CPU writes the output process image to the physical output modules, and the cycle repeats.

The process image is the detail most newcomers miss. Because inputs are sampled once per scan rather than read live mid-program, your program logic sees a consistent snapshot of the machine, which makes the behaviour repeatable.The practical consequence is that scan time sets your worst-case reaction time. If an input changes just after the input scan, the controller will not act on it until the next cycle. When you size a controller for a fast process, that latency, not the CPU's instruction speed, is usually the binding constraint.

Timers, Counters and Retentivity

Timers and counters are the workhorses of sequential control. Vendors differ in how they allocate them: the Siemens CPU 1516-3 PN/DP provides 2048 S7 timers and 2048 S7 counters, while IEC timers and IEC counters are unlimited and bounded only by available work memory.

Retentivity is adjustable on both, which matters whenever a process must resume where it stopped rather than restart from zero.

Inputs and Outputs: Discrete and Analog Signals

PLC inputs and outputs fall into two main categories: discrete and analog signals. 

Discrete, or digital, signals represent only two states, such as on or off, open or closed, and true or false. Typical discrete input devices include push buttons, limit switches, proximity sensors, and level switches. Discrete I/O is used extensively in machine-control applications.

Analog signals, by comparison, represent continuously changing values within a defined range. Thermocouples, pressure transmitters, flow meters, and load cells provide analog inputs, while variable-speed drives, modulating valves, and positioners receive analog outputs. Analog I/O is essential for closed-loop control of temperature, pressure, flow, speed, and position. 

On the output side, actuators convert the control decisions of a PLC into physical action. Valves and solenoids typically manage fluid systems, while motor starters and variable-speed drives control machinery used in conveying, processing, and assembly operations. 

PLC Programming Languages and the IEC 61131-3 Standard

PLC programming is standardized. PLCopen describes IEC 61131-3 as the worldwide recognised standard for programming and configuring industrial control devices, originally released in 1993 and widely accepted by the international user and vendor community since. ^[3]

The current edition is IEC 61131-3:2025, Edition 4.0, published on 22 May 2025. ^[1] It specifies the syntax and semantics of programming languages for programmable controllers, and its headline change from the previous edition is the inclusion of UTF-8 strings and their associated functions.

Ladder Logic

Ladder logic, also called a ladder diagram, is the language that made PLCs adoptable. The original 1968 GM specification explicitly required programming using relay ladder logic, because the maintenance electricians who would live with the machine already read relay schematics.

That design decision has outlasted the hardware it was made for. Ladder remains the default language for discrete machine control.

Function Block Diagram and Structured Text

The function block diagram represents logic as interconnected blocks with signals flowing between them, which suits continuous process control and reusable logic. On the other hand, structured text is a textual language closer to conventional programming, and it is the right choice when you need loops, arrays or arithmetic that ladder makes painful to express and harder to read.

Sequential Function Chart

Sequential function chart is a structuring tool rather than a general-purpose language. IEC describes the standard's suite as structured text plus the graphical ladder diagram and function block diagram languages, with sequential function chart elements included for program organization. ^[1] It fits batch processes and state machines where the program is naturally a sequence of steps and transitions.

Recommended Reading: PLC Programming: A Comprehensive Guide to Mastering the Art of Automation  

Types of PLCs

PLCs are available in compact, modular, distributed, and virtual configurations. Each type provides distinct advantages based on the application’s size, I/O requirements, processing demands, expansion needs, and installation environment.

Compact or Fixed PLCs

The compact PLC combines the CPU, power supply, communication interfaces, and a fixed number of input/output points within a single housing. It suits small standalone machines with stable, clearly defined control requirements. Although some compact PLCs support limited expansion modules, they are generally less flexible than modular systems.

Modular PLCs

The modular PLC uses separate CPU, power supply, communication, and I/O modules installed on a common rack or backplane. Modules can be replaced, expanded, or reconfigured as operational requirements change, making modular PLCs the mainstream choice for industrial machinery and larger automation systems. This architecture reflects the original requirement by General Motors for an expandable controller with interchangeable components. The Modicon name is also commonly interpreted as a contraction of “modular digital controller.”

Distributed I/O PLC Systems

In a distributed I/O architecture, a central PLC communicates with remote I/O stations through an industrial network. Instead of routing every sensor and actuator connection back to a single control cabinet, field signals connect to remote modules closer to the equipment. This approach reduces cabling requirements and is particularly valuable in large factories, processing facilities, and geographically dispersed industrial systems.

Virtual or Soft PLCs

The virtual PLC, also called a soft PLC, performs control functions through software running on an industrial PC, edge server, or virtualized computing environment. Major vendors have introduced commercial platforms, including SIMATIC S7-1500V in April 2023, CODESYS Virtual Control SL in June 2024, and Virtual PLCnext Control in November 2024.

However, virtual PLC technology remains in its early stages. IoT Analytics reports that virtual PLCs represent only a small single-digit percentage of the overall PLC market, although they could account for approximately one-quarter of new PLC sales by 2030.

Current virtual PLCs also have important engineering limitations. They do not support control tasks requiring execution times below one millisecond, generally lack the necessary functional safety certifications, offer limited code portability between runtimes, and often lack redundancy. Therefore, conventional hardware PLCs remain the preferred option for applications requiring sub-millisecond cycle times, certified safety functions, deterministic operation, or redundant control. 

PLC vs Microcontroller, Industrial PC and Other Controllers

PLCs, microcontrollers, industrial PCs, and programmable automation controllers can all execute control logic, but they differ significantly in hardware, software, reliability, and maintenance requirements. 

The right platform depends on the production volume, environmental conditions, processing needs, timing requirements, and expected service life of the application.

PLC

PLCs provide deterministic program execution, industrial-grade construction, standardised programming languages, modular I/O, and built-in diagnostics. It is designed for continuous operation in harsh environments and can usually be serviced by maintenance technicians using established troubleshooting tools. Its main trade-offs are a higher unit cost and less flexibility for general-purpose computing tasks.

Microcontroller

The microcontroller offers a compact footprint, low unit cost, and complete control over the embedded firmware. It is often the best choice for high-volume products with fixed functions. However, the development team must provide the surrounding infrastructure, including environmental protection, signal conditioning, diagnostics, communication interfaces, development tools, and maintenance procedures.

Industrial PC

Industrial PC combines industrial-grade hardware with general-purpose computing power, advanced data processing, storage capacity, and access to modern operating systems. It is well suited to machine vision, analytics, database operations, and complex user interfaces. However, it is not inherently deterministic, so real-time control depends on additional software, operating-system extensions, or a dedicated control runtime.

Programmable Automation Controller

The programmable automation controller (PAC) combines PLC-style deterministic control with more advanced computing, networking, data handling, and multi-axis control capabilities. PACs are commonly used in complex automation systems that require coordination across multiple processes. However, the distinction between a PAC and a high-end PLC has become increasingly unclear and is now often based more on vendor terminology than fundamental architecture.

PLC vs Microcontroller: The Practical Difference

Microcontroller can execute machine-control logic effectively, particularly in high-volume embedded products. However, choosing it over a PLC means giving up standardized programming languages, modular I/O, built-in diagnostics, industrial environmental qualification, and straightforward field servicing. 

PLC allows a maintenance technician to diagnose a machine failure using familiar tools without needing to interpret custom firmware. This makes it more practical for many industrial applications.

Recommended Reading: What Is a Programmable Automation Controller (PAC)?  

Communication Protocols

Modern automation systems are networked, and a PLC controller is usually one node among many.

Modbus

Modbus is considered the most widely adopted industrial communication protocol in the world. The current application layer specification is Modbus application protocol V1.1b3, alongside a serial line protocol and implementation guide at V1.02 and a Modbus messaging implementation guide version 1.0b for TCP/IP. ^[7]

The organization also publishes a Modbus Security protocol, and explicitly flags its original serial-line document from 1996 as obsolete and for legacy applications only. ^[7] If you are specifying Modbus on a new system, work from the current documents rather than whatever PDF is already on the plant server.

EtherNet/IP and CIP

EtherNet/IP utilizes the Common Industrial Protocol for its upper layers, and CIP networks follow the seven-layer OSI model. ^[8]

CIP encompasses a comprehensive suite of messages and services covering control, safety, security, energy, synchronization and motion, information and network management, and ODVA describes it as a truly media-independent protocol supported by hundreds of vendors.

EtherNet/IP runs on standard, unmodified Ethernet, so facilities do not need special hardware or expertise. Devices that pass ODVA conformance testing work with any other conformance-tested device, regardless of supplier. ^[8]

EtherNet/IP also supports UDP, enabling real-time cyclic data transmission, and supports star, linear, and device-level ring topologies.

PLCs, HMIs and SCADA Systems

PLC rarely operates as a completely independent device. In most industrial automation systems, it forms part of a layered control architecture that also includes:

1. Human-Machine Interface (HMI) - HMI is the local operator-facing layer: a panel display where an operator starts a sequence, acknowledges an alarm or adjusts a setpoint. HMIs fall within the same equipment standard that covers PLCs, IEC 61131-2. ^[4]

2. Supervisory Control and Data Acquisition (SCADA) - SCADA is the plant-wide or site-wide layer that aggregates data from many controllers for monitoring, trending, alarm management and historical analysis. In a classic SCADA architecture, a remote terminal unit (RTU) performs field data acquisition at geographically distributed sites, a pattern common in water, wastewater, and pipeline systems.

The relationship is hierarchical. PLCs execute deterministic control at the machine, HMIs provide local operator interaction, and SCADA systems supervise across the site. Communication may use protocols such as Modbus TCP, PROFINET, EtherNet/IP, DNP3, or OPC UA, depending on the equipment and application.

Because these layers exchange operational commands and sensitive process data, their networks must also be protected through access controls, network segmentation, secure remote access, backups, and continuous monitoring. NIST groups PLCs, HMIs, SCADA systems, RTUs, and related equipment under operational technology (OT): programmable systems and devices that interact with and influence the physical environment. ^[5]

Recommended Reading: PLC and SCADA: Understanding the Differences in Industrial Automation Systems  

Where PLCs Are Used

PLCs are used wherever machines or industrial processes require reliable, repeatable, real-time control.

• Discrete Manufacturing and Assembly: PLCs sequence production stations, manage interlocks, track parts, coordinate robots, and reject defective products in automotive, electronics, and consumer-goods factories.

• Process Control: Chemical, pharmaceutical, food and beverage, and oil and gas plants use PLCs for closed-loop control of temperature, pressure, flow, level, and mixing operations.

• Motion Control and Robotics: PLCs synchronize servo motors in robotic cells, packaging machines, printing presses, and CNC equipment. Motion capacity is an important specification; the Rockwell ControlLogix 5580 family supports up to 256 integrated motion axes.

• Water and Wastewater: PLCs control pumps, valves, filtration, aeration, chemical dosing, and reservoir levels, typically under centralized SCADA supervision.

• Power and Utilities: Power plants, substations, microgrids, and renewable-energy installations use PLCs for equipment sequencing, generator control, load management, and auxiliary systems.

• Buildings and Infrastructure: Applications include HVAC plants, chillers, tunnel ventilation, airport baggage systems, railway equipment, and access control.

• Packaging and Logistics: PLCs coordinate filling, sealing, labelling, weighing, conveyors, sortation equipment, cranes, and automated storage systems.

• Mining and Heavy Industry: Rugged PLCs control crushers, furnaces, kilns, mills, casting lines, and bulk-material handling equipment.

• Safety Systems: Certified safety PLCs monitor emergency stops, machine guards, light curtains, and safe-motion functions.

Selecting a PLC depends on I/O capacity, scan time, network support, motion requirements, environmental ratings, safety certification, and future expansion.

Environmental and Equipment Requirements

PLC costs more than an equivalent-performance computer largely because of its qualification.

IEC 61131-2 specifies testing and verification methods, mechanical requirements and tests, functional requirements for power supplies and I/O, EMC requirements and tests, and operating conditions, temperature, and climatic testing. Its operating conditions and altitude temperature derating align with IEC 61010-2-201, and product safety requirements now sit in that standard rather than in IEC 61131-2 itself. ^[4]

Those environmental conditions requirements trace directly back to the demand by General Motors in 1968 for a controller that could work amid dirt, moisture and vibration. ^[10] The requirement never went away; it just became a standard.

PLC Security

Networking PLCs to HMIs, SCADA platforms, engineering workstations, remote-access services, and enterprise systems improves visibility but expands the attack surface. The compromised PLC can expose data, stop production, alter product quality, damage equipment, disrupt essential services, or create unsafe physical conditions. 

Why PLCs Are Attractive Targets?

PLCs connect cyber systems with physical processes. The attacks could target control logic, firmware, industrial protocols, engineering software, removable media, and hardware interfaces. ^[6]

The common weaknesses include default credentials, unsupported firmware, exposed programming services, insecure remote access, poorly protected engineering workstations, and legacy protocols without encryption or authentication. Attackers may modify logic, manipulate setpoints, suppress alarms, or force equipment into an unsafe state.

Applying OT-Specific Security

The principal guidance is NIST SP 800-82 Revision 3, Guide to Operational Technology Security. ^[5] It addresses OT architectures, threats, vulnerabilities, and safeguards while accounting for the performance, reliability, and safety requirements of physical operations.

Conventional IT Practices cannot always be transferred unchanged to PLC environments. Automatic updates, aggressive scans, unplanned reboots, or untested endpoint software may interrupt production or affect deterministic control. Security changes must therefore be tested and coordinated with operations, maintenance, safety, and engineering teams.

Core PLC Security Controls

The practical PLC security programme should:

• Maintain an inventory of controllers, firmware versions, communication paths, connected equipment, and asset owners.

• Remove PLCs from direct internet exposure and separate IT and OT networks using firewalls, security zones, and an industrial demilitarized zone.

• Replace default passwords, apply role-based privileges, disable unnecessary services, and restrict programming access.

• Provide remote access only through approved, authenticated, encrypted, time-limited, and logged connections.

• Protect engineering workstations and control removable media, as both can introduce malicious code or unauthorized logic.

• Use passive network monitoring and change detection to identify abnormal communications or controller modifications without disrupting operations.

• Keep offline, version-controlled backups of PLC programs, configurations, recipes, HMI projects, and firmware, and test restoration procedures.

• Test patches and firmware updates before deployment and schedule them during approved maintenance windows.

PLC security requires defence in depth. Secure architecture, controlled access, system hardening, monitoring, tested backups, change management, and recovery planning must work together throughout the controller’s operating life.

Common Mistakes and Troubleshooting Tips

PLC faults often stem from configuration, timing, wiring, or commissioning decisions rather than failed hardware. 

The systematic troubleshooting process should begin with diagnostics, operating status, recent changes, and field-signal verification before modifying the program.

• Ignoring the Process Image: Expecting an input change to take effect mid-scan produces intermittent faults that are painful to reproduce. Reason about behavior one full cycle at a time.

• Sizing on Instruction Speed alone: The 10 ns bit operation is irrelevant if scan time and network update rate dominate your reaction time.

• Mixing Up Memory Categories: Program memory, data memory, load memory and retentive memory are separate budgets, and running out of one does not show up as a shortage of another.

• Overloading Output Modules: Per-channel current ratings and total module load are different limits. Meeting the first and violating the second is a common commissioning failure.

• Leaving Retentivity at Defaults: Decide deliberately which timers, counters and data blocks must survive a power cycle.

• Treating Vendor Protocol Documents as Interchangeable: Check the specification version you are working from, especially with Modbus, where an obsolete 1996 document is still in circulation. ^[7]

Recommended Reading: What is Programmable Automation

How to Choose a PLC?

Work through these in order, because each one eliminates options.

1. Establish Worst-Case Reaction Time: This drives scan time, network update rate, and, if the answer is under a millisecond, rules out virtual PLCs entirely.

2. Count and Classify I/O: Total channels, discrete versus analog split, and how much expansion headroom the system needs over its life.

3. Check Safety and Certification Requirements: A functional safety rating narrows the field immediately and currently excludes vPLCs.

4. Choose the Network: Existing plant infrastructure usually decides between EtherNet/IP, Modbus and the vendor's native protocol before you choose the controller.

5. Confirm Environmental Ratings: Temperature, vibration, humidity and altitude derating against IEC 61131-2 conditions. ^[4]

6. Weigh the Toolchain and Support Ecosystem: The programming device software, its version compatibility and the availability of technicians who know it will outlast your involvement in the project. 

Conclusion

PLC is a deterministic, ruggedized industrial computer that reads sensors, runs control logic on a repeating scan cycle, and drives output devices. The concept dates to a General Motors specification written in 1968 and a controller Dick Morley detailed on New Year's Day of that year, and the requirements in that original document still describe the category.

Modern controllers execute instructions at high speed, manage thousands of I/O points, coordinate complex motion, and communicate across industrial Ethernet networks. Their essential value, however, remains unchanged: predictable operation, dependable hardware, standardized programming, clear diagnostics, and straightforward field maintenance. 

Virtual PLCs may reshape future control architectures, but reliability, safety, determinism, and serviceability will continue to determine whether a controller suits an industrial application. 

Frequently Asked Questions

Q. What does PLC stand for?

A. PLC stands for programmable logic controller. Allen-Bradley popularized the acronym; before that, the device was simply called a programmable controller.

Q. What is a PLC used for?

A. PLCs control machines and processes: sequencing assembly lines, running closed-loop process control, coordinating motion axes, and managing distributed infrastructure such as water and wastewater sites.

Q. How does a PLC work?

A. It runs a repeating scan cycle with four stages: housekeeping, input scan, program execution and output scan. Inputs are frozen into a process image at the start of each cycle so program logic sees a consistent snapshot.

Q. What programming languages do PLCs use?

A. The current standard, IEC 61131-3:2025, specifies Structured Text, Ladder Diagram, Function Block Diagram and Sequential Function Chart. Ladder logic remains the most common choice for discrete machine control.

Q. What is the difference between a PLC and a microcontroller?

A. A microcontroller is a bare processing device you program at the firmware level. A PLC packages a processor with standardized programming languages, modular I/O, and equipment and environmental qualification under IEC 61131-2.

Q. What is the difference between a PLC and SCADA?

A. They operate at different levels. A PLC executes deterministic control at the machine. SCADA supervises across a site, aggregating data from many controllers for monitoring, alarms and historical analysis.

Q. Can a PLC run as software instead of hardware?

A. Yes, as a virtual PLC running on servers, edge devices or industrial PCs, with products from Siemens, CODESYS and Phoenix Contact. The category remains early: no vPLC currently supports control tasks faster than 1 millisecond, and none hold the required functional safety certifications.

Q. How much memory does a PLC have?

A. It varies widely by class and vendor accounting. The Siemens CPU 1516-3 PN/DP integrates 1 MB of work memory for program and 5 MB for data, with load memory on a card of up to 32 GB. The Rockwell 1756-L83E is quoted at 10 MB of user memory.

References

[1] IEC. IEC 61131-3:2025, Programmable Controllers, Part 3: Programming Languages [Cited 2026 September 08] Available at: Link

[2] PLCopen. IEC 61131-3 and PLCopen [Cited 2026 September 08] Available at: Link

[3] PLCopen. Status of IEC 61131-3 Standard [Cited 2026 September 08] Available at: Link

[4] PLCopen. IEC 61131-2, Equipment Requirements and Tests [Cited 2026 September 08] Available at: Link

[5] NIST. NIST SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security [Cited 2026 September 08] Available at: Link

[6] arXiv. SoK: Security of Programmable Logic Controllers [Cited 2026 September 08] Available at: Link

[7] Modbus. Modbus Specifications [Cited 2026 September 08] Available at: Link

[8] ODVA. EtherNet/IP Industrial Ethernet Network [Cited 2026 September 08] Available at: Link

[9] Control. The Origin Story of the PLC [Cited 2026 September 08] Available at: Link

[10] AutomationDirect. History of the PLC [Cited 2026 September 08] Available at: Link