Hubbry Logo
Programmable logic controllerProgrammable logic controllerMain
Open search
Programmable logic controller
Community hub
Programmable logic controller
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Programmable logic controller
Programmable logic controller
Programmable logic controller
View on Wikipedia
from Wikipedia

PLCs for a monitoring system in the pharmaceutical industry
Part of a series of articles on
Machine industry
Mill
Manufacturing methods
Industrial technologies
Information and communication
Process control

A programmable logic controller (PLC) or programmable controller is an industrial computer that has been ruggedized and adapted for the control of manufacturing processes, such as assembly lines, machines, robotic devices, or any activity that requires high reliability, ease of programming, and process fault diagnosis.

PLCs can range from small modular devices with tens of inputs and outputs (I/O), in a housing integral with the processor, to large rack-mounted modular devices with thousands of I/O, and which are often networked to other PLC and SCADA systems.[1] They can be designed for many arrangements of digital and analog I/O, extended temperature ranges, immunity to electrical noise, and resistance to vibration and impact.

PLCs were first developed in the automobile manufacturing industry to provide flexible, rugged and easily programmable controllers to replace hard-wired relay logic systems. Dick Morley, who invented the first PLC, the Modicon 084, for General Motors in 1968, is considered the father of PLC.

A PLC is an example of a hard real-time system since output results must be produced in response to input conditions within a limited time, otherwise unintended operation may result. Programs to control machine operation are typically stored in battery-backed-up or non-volatile memory.

Invention and early development

[edit]

The PLC originated in the late 1960s in the automotive industry in the US and was designed to replace relay logic systems.[2] Before, control logic for manufacturing was mainly composed of relays, cam timers, drum sequencers, and dedicated closed-loop controllers.[3]

The hard-wired nature of these components made it difficult for design engineers to alter the automation process. Changes would require rewiring and careful updating of the documentation. Troubleshooting was a tedious process.[4] When general-purpose computers became available, they were soon applied to control logic in industrial processes. These early computers were unreliable[5] and required specialist programmers and strict control of working conditions, such as temperature, cleanliness, and power quality.[6]

The PLC provided several advantages over earlier automation systems. It was designed to tolerate the industrial environment better than systems intended for office use, and was more reliable, compact, and required less maintenance than relay systems. It was easily expandable with additional I/O modules. While relay systems required tedious and sometimes complicated hardware changes in case of reconfiguration, a PLC can be reconfigured by loading new or modified code. This allowed for easier iteration over manufacturing process design. With a simple programming language focused on logic and switching operations, it was more user-friendly than computers using general-purpose programming languages. Early PLCs were programmed in ladder logic, which strongly resembled a schematic diagram of relay logic. It also permitted its operation to be monitored.[7][8]

Virtual PLCs

[edit]

In recent years, the introduction of virtual PLCs has expanded the scope of programmable logic controllers. Virtual PLCs are software-based controllers that simulate the functions of traditional PLCs but are executed on general-purpose hardware, offering a more cost-effective and flexible alternative. These controllers enable automation systems to be managed without the need for dedicated hardware, making them ideal for applications requiring simulation, remote control, or cloud-based systems.[9]

Modicon

[edit]

In 1968, GM Hydramatic, the automatic transmission division of General Motors, issued a request for proposals for an electronic replacement for hard-wired relay systems based on a white paper written by engineer Edward R. Clark. The winning proposal came from Bedford Associates from Bedford, Massachusetts. The result, built in 1969, was the first PLC and designated the 084, because it was Bedford Associates' eighty-fourth project.[10][11]

Bedford Associates started a company, Modicon, Inc.,[12] dedicated to developing, manufacturing, selling, and servicing this new product, which they named Modicon (standing for "modular digital controller"). One of the people who worked on that project was Dick Morley, who is considered to be the father of the PLC.[13] The Modicon brand was sold in 1977 to Gould Electronics and later to Schneider Electric, its current owner.[11] About this same time, Modicon created Modbus, a data communications protocol to be used with its PLCs. Modbus has since become a standard open protocol commonly used to connect many industrial electrical devices.[14]

One of the first Modicon 084 models built is now on display at Schneider Electric's facility in North Andover, Massachusetts. It was presented to Modicon by GM, when the unit was retired after nearly twenty years of uninterrupted service. Modicon used the 84 moniker at the end of its product range like Modicon Micro 84 and Modicon TSX CSY 84 until after the 984 made its appearance.[15]

Allen-Bradley

[edit]

In a parallel development, Odo Josef Struger is sometimes known as the "father of the programmable logic controller" as well.[13] He was involved in the invention of the Allen-Bradley programmable logic controller[16][17][18] and is credited with coining the PLC acronym.[13][16] Allen-Bradley (now a brand owned by Rockwell Automation) became a major PLC manufacturer in the United States during his tenure.[19] Struger played a leadership role in developing IEC 61131-3 PLC programming language standards.[13] Allen-Bradley's PLC-5 family, released in the 1980's, was the first modular design found in modern-day systems.[20]


Early methods of programming

[edit]

Many early PLC programming applications were not capable of graphical representation of the logic, and so it was instead represented as a series of logic expressions in some kind of Boolean format, similar to Boolean algebra. As programming terminals evolved, because ladder logic was a familiar format used for electro-mechanical control panels, it became more commonly used. Newer formats, such as state logic,[21] function block diagrams, and structured text exist. Ladder logic remains popular because PLCs solve the logic in a predictable and repeating sequence, and ladder logic allows the person writing the logic to see any issues with the timing of the logic sequence more easily than would be possible in other formats.[22]

Up to the mid-1990s, PLCs were programmed using proprietary programming panels or special-purpose programming terminals, which often had dedicated function keys representing the various logical elements of PLC programs.[10] Some proprietary programming terminals displayed the elements of PLC programs as graphic symbols, but plain ASCII character representations of contacts, coils, and wires were common. Programs were stored on cassette tape cartridges. Facilities for printing and documentation were minimal due to a lack of memory capacity. The oldest PLCs used magnetic-core memory.[23]

Architecture

[edit]

A PLC is an industrial microprocessor-based controller with programmable memory used to store program instructions and various functions.[24] It consists of:

  • A processor unit (CPU) which interprets inputs, executes the control program stored in memory and sends output signals,
  • A power supply unit which converts AC voltage to DC,
  • A memory unit storing data from inputs and program to be executed by the processor,
  • An input and output interface, where the controller receives and sends data from and to external devices,
  • A communications interface to receive and transmit data on communication networks from and to remote PLCs.[25]

PLCs require a programming device which is used to develop and later download the created program into the memory of the controller.[25]

Modern PLCs generally contain a real-time operating system, such as OS-9 or VxWorks.[26]

Mechanical design

[edit]
Compact PLC with 8 inputs and 4 outputs
Modular PLC with EtherNet/IP module, digital and analog I/O, with some slots being empty.
Modular PLC with EtherNet/IP module, discrete and analog I/O, with some slots being empty

There are two types of mechanical design for PLC systems. A single box (also called a brick) is a small programmable controller that fits all units and interfaces into one compact casing, although, typically, additional expansion modules for inputs and outputs are available. The second design type – a modular PLC – has a chassis (also called a rack) that provides space for modules with different functions, such as power supply, processor, selection of I/O modules and communication interfaces – which all can be customized for the particular application.[27] Several racks can be administered by a single processor and may have thousands of inputs and outputs. Either a special high-speed serial I/O link or comparable communication method is used so that racks can be distributed away from the processor, reducing the wiring costs for large plants.[citation needed]

Discrete and analog signals

[edit]

Discrete (digital) signals can only take on or off value (1 or 0, true or false). Examples of devices providing a discrete signal include limit switches and photoelectric sensors.[28]

Analog signals can use voltage or current that is analogous to the monitored variable and can take any value within their scale. Pressure, temperature, flow, and weight are often represented by analog signals. These are typically interpreted as integer values with various ranges of accuracy depending on the device and the number of bits available to store the data.[28] For example, an analog 0 to 10 V or 4-20 mA current loop input would be converted into an integer value of 0 to 32,767. The PLC will take this value and translate it into the desired units of the process so the operator or program can read it.

Redundancy

[edit]

Some special processes need to work permanently with minimum unwanted downtime. Therefore, it is necessary to design a system that is fault tolerant. In such cases, to increase the system availability in the event of hardware component failure, redundant CPU or I/O modules with the same functionality can be added to a hardware configuration to prevent a total or partial process shutdown due to hardware failure. Other redundancy scenarios could be related to safety-critical processes, for example, large hydraulic presses could require that two PLCs turn on output before the press can come down in case one PLC does not behave properly.

Programming

[edit]
Example of a ladder diagram logic

Programmable logic controllers are intended to be used by engineers without a programming background. For this reason, a graphical programming language called ladder logic was first developed. It resembles the schematic diagram of a system built with electromechanical relays and was adopted by many manufacturers and later standardized in the IEC 61131-3 control systems programming standard. As of 2015, it is still widely used, thanks to its simplicity.[29]

As of 2015, the majority of PLC systems adhere to the IEC 61131-3 standard that defines 2 textual programming languages: Structured Text (similar to Pascal) and Instruction List; as well as 3 graphical languages: ladder logic, function block diagram and sequential function chart.[29][30] Instruction List was deprecated in the third edition of the standard.[31]

Modern PLCs can be programmed in a variety of ways, from the relay-derived ladder logic to programming languages such as specially adapted dialects of BASIC and C.[32]

While the fundamental concepts of PLC programming are common to all manufacturers, differences in I/O addressing, memory organization, and instruction sets mean that PLC programs are never perfectly interchangeable between different makers. Even within the same product line of a single manufacturer, different models may not be directly compatible.[33]

Programming device

[edit]

Manufacturers develop programming software for their PLCs. In addition to being able to program PLCs in multiple languages, they provide common features like hardware diagnostics and maintenance, software debugging, and offline simulation.[34]

PLC programs are typically written in a programming device, which can take the form of a desktop console, special software on a personal computer, or a handheld device.[34] The program is then downloaded to the PLC through a cable connection or over a network. It is stored either in non-volatile flash memory or battery-backed-up RAM on the PLC. In some PLCs, the program is transferred from the programming device using a programming board that writes the program into a removable chip, such as EPROM that is then inserted into the PLC.

Simulation

[edit]

An incorrectly programmed PLC can result in lost productivity and dangerous conditions for programmed equipment. PLC simulation is a feature often found in PLC programming software. It allows for testing and debugging early in a project's development. Testing the project in simulation improves its quality, increases the level of safety associated with equipment and can save time during the installation and commissioning of automated control applications since many scenarios can be tried and tested before the system is activated.[34][35]

Functionality

[edit]
PLC system in a rack, left-to-right: power supply (PS), CPU, interface module (IM) and communication processor (CP)
Control panel with PLC (gray elements in the center). The unit consists of separate elements, from left to right: power supply, controller, relay units for input and output.

The main difference compared to most other computing devices is that PLCs are intended for and therefore tolerant of more severe environmental conditions (such as dust, moisture, heat, cold), while offering extensive input/output (I/O) to connect the PLC to sensors and actuators. PLC input can include simple digital elements such as limit switches, analog variables from process sensors (such as temperature and pressure), and more complex data such as that from positioning or machine vision systems.[36] PLC output can include elements such as indicator lamps, sirens, electric motors, pneumatic or hydraulic cylinders, magnetic relays, solenoids, or analog outputs. The input/output arrangements may be built into a simple PLC, or the PLC may have external I/O modules attached to a fieldbus or computer network that plugs into the PLC.

The functionality of the PLC has evolved over the years to include sequential relay control, motion control, process control, distributed control systems, and networking. The data handling, storage, processing power, and communication capabilities of some modern PLCs are approximately equivalent to desktop computers. PLC-like programming combined with remote I/O hardware allows a general-purpose desktop computer to serve as a PLC in certain applications.[citation needed] Desktop computer controllers have not been generally accepted in heavy industry because desktop computers run on less stable operating systems than PLCs, and because the desktop computer hardware is typically not designed to the same levels of tolerance to temperature, humidity, vibration, and longevity as PLCs.

Basic functions

[edit]

The most basic function of a programmable logic controller is to emulate the functions of electromechanical relays. Within the PLC programming environment, discrete inputs are given a unique address, and a PLC instruction can test if the input state is on or off. Just as a series of relay contacts perform a logical AND function, not allowing current to pass unless all the contacts are closed, so a series of examine if on instructions will energize its output storage bit if all the input bits are on. Similarly, a parallel set of instructions will perform a logical OR. In an electromechanical relay wiring diagram, a group of contacts controlling one coil is called a rung of a ladder diagram, and this concept is also used to describe PLC logic.[a] The output of each rung sets or clears a storage bit, which may be associated with a discrete output or which may be an internal coil with no physical connection. Such internal coils can be used, for example, as a common element in multiple separate rungs.

More advanced instructions of the PLC may be implemented as functional blocks, which carry out some operation, such as manipulating internal variable, when enabled by a logical input and which produce outputs to signal, for example, completion or errors.

Communication

[edit]

PLCs use built-in ports, such as USB, Ethernet, RS-232, RS-485, or RS-422 to communicate with external devices (sensors, actuators) and systems (programming tools, SCADA and other user interfaces). Communication is carried over various industrial network protocols, like Modbus, or EtherNet/IP. Many of these protocols are vendor specific. Formerly, some manufacturers offered dedicated communication modules as an add-on function where the processor had no network connection built-in.

PLCs used in larger I/O systems may have peer-to-peer (P2P) communication between processors. This allows separate parts of a complex process to have individual control while allowing the subsystems to coordinate over the communication link.

User interface

[edit]
Control panel with a PLC user interface for thermal oxidizer regulation
See also: User interface and List of human-computer interaction topics

PLCs may need to interact with people for the purpose of configuration, alarm reporting, or everyday control. A human-machine interface (HMI) is employed for this purpose. HMIs are also referred to as man-machine interfaces (MMIs) and graphical user interfaces (GUIs). A simple system may use buttons and lights to interact with the user. Text displays are available as well as graphical touch screens. More complex systems use programming and monitoring software installed on a computer, with the PLC connected via a communication interface.

Process of a scan cycle

[edit]

A PLC works in a program scan cycle, where it executes its program repeatedly. The simplest scan cycle consists of 3 steps:

  1. Read inputs.
  2. Execute the program.
  3. Write outputs.[37]

The program follows the sequence of instructions. It typically takes a time span of tens of milliseconds for the processor to evaluate all the instructions and update the status of all outputs.[38] If the system contains remote I/O—for example, an external rack with I/O modules—then that introduces additional uncertainty in the response time of the PLC system.[37]

As PLCs became more advanced, methods were developed to change the sequence of ladder execution, and subroutines were implemented.[39]

Special-purpose I/O modules may be used where the scan time of the PLC is too long to allow predictable performance. Precision timing modules, or counter modules for use with shaft encoders, are used where the scan time would be too long to reliably count pulses or detect the sense of rotation of an encoder. This allows even a relatively slow PLC to still interpret the counted values to control a machine, as the accumulation of pulses is done by a dedicated module that is unaffected by the speed of program execution.[40]

Security

[edit]

In his book from 1998, E. A. Parr pointed out that even though most programmable controllers require physical keys and passwords, the lack of strict access control and version control systems, as well as an easy-to-understand programming language make it likely that unauthorized changes to programs will happen and remain unnoticed.[41]

Prior to the discovery of the Stuxnet computer worm in June 2010, the security of PLCs received little attention. Modern programmable controllers generally contain real-time operating systems, which can be vulnerable to exploits in a similar way as desktop operating systems, like Microsoft Windows. PLCs can also be attacked by gaining control of a computer they communicate with.[26] Since 2011, these concerns have grown – networking is becoming more commonplace in the PLC environment, connecting the previously separated plant floor networks and office networks.[42]

In February 2021, Rockwell Automation publicly disclosed a critical vulnerability affecting its Logix controllers family. The secret cryptographic key used to verify communication between the PLC and workstation could be extracted from the programming software (Studio 5000 Logix Designer) and used to remotely change program code and configuration of a connected controller. The vulnerability was given a severity score of 10 out of 10 on the CVSS vulnerability scale. At the time of writing, the mitigation of the vulnerability was to limit network access to affected devices.[43][44]

Safety PLCs

[edit]

Safety PLCs can be either a standalone device or a safety-rated hardware and functionality added to existing controller architectures (Allen-Bradley GuardLogix, Siemens F-series, etc.). These differ from conventional PLC types by being suitable for safety-critical applications for which PLCs have traditionally been supplemented with hard-wired safety relays and areas of the memory dedicated to the safety instructions. The standard of safety level is the SIL.

A safety PLC might be used to control access to a robot cell with trapped-key access, or to manage the shutdown response to an emergency stop button on a conveyor production line. Such PLCs typically have a restricted regular instruction set augmented with safety-specific instructions designed to interface with emergency stop buttons, light screens, and other safety-related devices.

The flexibility that such systems offer has resulted in rapid growth of demand for these controllers.[citation needed]

PLC compared with other control systems

[edit]
PLC installed in a control panel
Control center with a PLC for a RTO

PLCs are well adapted to a range of automation tasks. These are typically industrial processes in manufacturing where the cost of developing and maintaining the automation system is high relative to the total cost of the automation, and where changes to the system would be expected during its operational life. PLCs contain input and output devices compatible with industrial pilot devices and controls; little electrical design is required, and the design problem centers on expressing the desired sequence of operations. PLC applications are typically highly customized systems, so the cost of a packaged PLC is low compared to the cost of a specific custom-built controller design. On the other hand, in the case of mass-produced goods, customized control systems are economical. This is due to the lower cost of the components, which can be optimally chosen instead of a "generic" solution, and where the non-recurring engineering charges are spread over thousands or millions of units.[citation needed]

Programmable controllers are widely used in motion, positioning, or torque control. Some manufacturers produce motion control units to be integrated with PLC so that G-code (involving a CNC machine) can be used to instruct machine movements.[citation needed]

PLC chip / embedded controller

[edit]

These are for small machines and systems with low or medium volume. They can execute PLC languages such as Ladder, Flow-Chart/Grafcet, etc. They are similar to traditional PLCs, but their small size allows developers to design them into custom printed circuit boards like a microcontroller, without computer programming knowledge, but with a language that is easy to use, modify and maintain. They sit between the classic PLC / micro-PLC and microcontrollers.[citation needed]

Microcontrollers

[edit]

A microcontroller-based design would be appropriate where hundreds or thousands of units will be produced and so the development cost (design of power supplies, input/output hardware, and necessary testing and certification) can be spread over many sales, and where the end-user would not need to alter the control. Automotive applications are an example; millions of units are built each year, and very few end-users alter the programming of these controllers. However, some specialty vehicles such as transit buses economically use PLCs instead of custom-designed controls, because the volumes are low and the development cost would be uneconomical.[45]

Single-board computers

[edit]

Very complex process control, such as those used in the chemical industry, may require algorithms and performance beyond the capability of even high-performance PLCs. Very high-speed or precision controls may also require customized solutions; for example, aircraft flight controls. Single-board computers using semi-customized or fully proprietary hardware may be chosen for very demanding control applications where the high development and maintenance cost can be supported. "Soft PLCs" running on desktop-type computers can interface with industrial I/O hardware while executing programs within a version of commercial operating systems adapted for process control needs.[45]

The rising popularity of single board computers has also had an influence on the development of PLCs. Traditional PLCs are generally closed platforms, but some newer PLCs (e.g. groov EPIC from Opto 22, ctrlX from Bosch Rexroth, PFC200 from Wago, PLCnext from Phoenix Contact, and Revolution Pi from Kunbus) provide the features of traditional PLCs on an open platform.

Programmable logic relays (PLR)

[edit]

In more recent years,[when?] small products called programmable logic relays (PLRs) or smart relays, have become more common and accepted. These are similar to PLCs and are used in light industries where only a few points of I/O are needed, and low cost is desired. These small devices are typically made in a common physical size and shape by several manufacturers and branded by the makers of larger PLCs to fill their low-end product range. Most of these have 8 to 12 discrete inputs, 4 to 8 discrete outputs, and up to 2 analog inputs. Most such devices include a tiny postage stamp-sized LCD screen for viewing simplified ladder logic (only a very small portion of the program being visible at a given time) and status of I/O points, and typically these screens are accompanied by a 4-way rocker push-button plus four more separate push-buttons, similar to the key buttons on a VCR remote control, and used to navigate and edit the logic. Most have an RS-232 or RS-485 port for connecting to a PC so that programmers can use user-friendly software for programming instead of the small LCD and push-button set for this purpose. Unlike regular PLCs that are usually modular and greatly expandable, the PLRs are usually not modular or expandable, but their cost can be significantly lower than that a PLC, and they still offer robust design and deterministic execution of the logic.

A variant of PLCs, used in remote locations is the remote terminal unit or RTU. An RTU is typically a low power, ruggedized PLC whose key function is to manage the communications links between the site and the central control system (typically SCADA) or in some modern systems, "The Cloud". Unlike factory automation using wired communication protocols such as Ethernet, communications links to remote sites are often radio-based and are less reliable. To account for the reduced reliability, RTU will buffer messages or switch to alternate communications paths. When buffering messages, the RTU will timestamp each message so that a full history of site events can be reconstructed. RTUs, being PLCs, have a wide range of I/O and are fully programmable, typically with languages from the IEC 61131-3 standard that is common to many PLCs, RTUs and DCSs. In remote locations, it is common to use an RTU as a gateway for a PLC, where the PLC is performing all site control and the RTU is managing communications, time-stamping events and monitoring ancillary equipment. On sites with only a handful of I/O, the RTU may also be the site PLC and will perform both communications and control functions.

See also

[edit]

Notes

[edit]

References

[edit]

Further reading

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Programmable logic controller

View on Grokipedia
from Grokipedia
A programmable logic controller (PLC) is a ruggedized industrial digital computer designed for automating electromechanical processes, such as those in and assembly lines, by monitoring inputs, processing programmed logic, and controlling actuators or outputs to ensure precise, reliable operation in harsh environments. The PLC was invented in 1968 by engineer Richard (Dick) Morley of Bedford Associates to address the limitations of hard-wired systems, which were labor-intensive to modify for ' Hydra-matic Division automotive production lines. The first prototype, designated the 084, was delivered in 1969 and commercially developed as the Modicon 084 by Modicon, a company founded by members of Bedford Associates, marking the shift from electromechanical relays to solid-state programmable control for faster reconfiguration and reduced downtime. This innovation rapidly expanded in the 1970s, with companies like introducing their own models, such as the PLC-5 in 1986, standardizing PLC use across industries. At its core, a PLC comprises a (CPU) that executes user programs, (I/O) modules for with field devices like sensors and motors, a unit (typically 24V DC or 120V AC), and a chassis or rack for modular expansion, all housed in a robust to withstand vibrations, , and extremes. Programming occurs via specialized software using standardized languages outlined in , including (which emulates diagrams for discrete control), function block diagrams, , instruction lists, and sequential function charts, enabling real-time decision-making and fault diagnostics. Key advantages over traditional systems include smaller footprint, simpler modifications without rewiring, integrated troubleshooting tools, and scalability for complex tasks like PID (proportional-integral-derivative) control in continuous processes. PLCs are integral to modern industrial , applied in sectors such as automotive assembly, food and beverage processing, , , and building systems for tasks ranging from simple on/off sequencing to sophisticated and safety interlocks. Their evolution into programmable automation controllers (PACs) in the and beyond has incorporated advanced networking (e.g., ), higher processing power, and integration with supervisory control and data acquisition () systems, enhancing efficiency and remote monitoring in Industry 4.0 environments.

History and Development

Invention in the late 1960s

In the late 1960s, industrial in the automotive sector faced significant challenges due to reliance on hardwired -based control systems. At ' Hydra-Matic transmission plant in , production line changes for new vehicle models necessitated extensive rewiring of relay panels, often involving thousands of relays and miles of wiring, which resulted in substantial , high labor costs, and frequent maintenance issues from tangled "rats' nests" of cables. To address this, GM issued a request for proposals in for a "standard machine controller" that could be easily reprogrammed without physical modifications, aiming to reduce setup times from weeks to hours. The programmable logic controller (PLC) emerged as a direct response to these needs, with the concept first proposed by engineer Richard "Dick" Morley on January 1, 1968, while working at Bedford Associates in . Commissioned by , Morley's design envisioned a solid-state, digital device to replace entirely, using software for logic implementation rather than mechanical switches or wiring changes. This innovation shifted control from electromechanical hardware to electronic programming, emphasizing ruggedness for factory environments, direct memory mapping for inputs and outputs, and a scan-based execution cycle to mimic relay timing. Bedford Associates incorporated as Modicon (from "modular digital controller") later that year to commercialize the technology. The initial prototype, designated the Modicon 084, was developed and demonstrated in , marking the first functional PLC. Built by Morley's team—including , Jonas Landau, and Tom Boissevain—this unit focused exclusively on digital input/output handling for boolean logic operations, deliberately excluding analog processing to keep costs low and align with replacement needs. It featured a custom, hardened enclosure with no fans or external air intake to prevent contamination, and was tested on machinery like gear grinders before delivery to GM's Hydra-Matic plant in November 1969, where it successfully controlled a press line. Key milestones included the filing of U.S. Patent 3,761,893 by Morley on July 2, 1970, which described a digital adaptable for industrial control, emphasizing addressed for I/O and expandable systems without dedicated hardware registers. Granted on September 25, 1973, this patent underscored the core principle of reprogrammability through software, predating other similar filings and laying the foundation for PLC scalability. The invention's impact was immediate, with GM ordering units worth $1 million, validating the shift from hardware-centric to software-driven .

Key early manufacturers and models

The pioneering commercial introduction of the programmable logic controller (PLC) occurred with the Modicon 084 in 1971, developed by engineer Dick Morley's team at Modicon Inc. in response to ' call for a solid-state replacement for relay-based systems. This model featured a allowing for expandable (I/O) configurations, initially supporting up to 64 discrete I/O points, and utilized memory-based programming that emulated diagrams stored in core memory. Its rugged construction, including conductive cooling and no power switch to prevent accidental shutdowns, made it suitable for harsh industrial environments, marking the first widespread commercial PLC deployment at facilities like Bryant Chuck and Grinder. Concurrent with Modicon's efforts, released its first PLC, the Bulletin 1774, in 1974, engineered by Odo Struger and Ernst Dummermuth. This stand-alone controller emphasized reliability for factory floor applications through direct emulation of relay ladder logic, enabling easier transition from electromechanical systems without requiring extensive retraining for maintenance personnel. The Bulletin 1774's parallel processing architecture and integration with existing I/O chassis further solidified its role as a durable alternative to custom wiring panels. In Europe, contributed to early global adoption with the launch of the S3 in 1973, the first PLC to incorporate technology and integrated circuits for programmable logic control. This innovation allowed for more compact and flexible systems compared to earlier hard-wired controllers, accelerating PLC penetration beyond . Meanwhile, Modicon's evolution included its acquisition by in 1997, following Schneider's 1988 purchase of Telemecanique, which integrated complementary automation technologies and expanded the reach of early PLC designs. These early models catalyzed a fundamental shift in industrial automation, replacing cumbersome custom relay panels with standardized, reprogrammable controllers that substantially reduced wiring complexity and installation time—often by up to 50%—particularly in automotive assembly lines where frequent modifications were common. This transition not only lowered costs but also improved system reliability and scalability, laying the foundation for broader adoption across manufacturing sectors.

Evolution of programming methods and standards

In the 1970s, programmable logic controller (PLC) programming was characterized by proprietary mnemonic codes that mimicked relay ladder logic operations, such as AND, OR, and NOT functions, entered directly into the device using hand-held programmers or dedicated terminals. These early methods were vendor-specific, limiting portability and requiring physical access to the PLC for modifications, as the systems emulated hardwired relay panels to control . Hand-held programmers, often battery-powered units with keypads and small displays, allowed technicians to input sequences step-by-step, but they supported only basic logic without advanced or capabilities. The 1980s brought significant advancements with the integration of personal computers (PCs) for PLC programming, replacing cumbersome hand-held devices with more flexible software interfaces. PC-based tools enabled offline program development and downloading via serial connections, while graphical ladder logic editors emerged, allowing users to visually construct rung-based diagrams resembling electrical schematics on screen. Precursors to structured text programming also appeared, introducing text-based commands for more efficient handling of repetitive or arithmetic operations, though these remained largely proprietary across manufacturers like Allen-Bradley and Modicon. This shift improved productivity by facilitating easier editing, testing, and documentation of control logic. A major milestone occurred in 1993 with the publication of the standard by the (IEC), which established a unified framework for PLC programming languages to promote interoperability and reduce . This standard defined five languages—ladder diagram (LD) for graphical relay-style logic, (FBD) for modular interconnections, (ST) for high-level algorithmic coding, instruction list (IL) for low-level assembly-like instructions, and (SFC) for state-machine representations—allowing programs to be portable across compliant PLCs from different vendors. Updated in its third edition in 2013 and fourth edition in 2025, incorporated enhancements for better data typing, function blocks, and , further standardizing syntax and semantics to support complex systems. From the 2000s onward, PLC programming evolved toward greater interoperability through initiatives like PLCopen, an organization that developed XML-based data exchange formats in 2005 to enable seamless transfer of programs, configurations, and documentation between development tools and vendors. This , aligned with , facilitated version control, simulation integration, and multi-vendor collaboration without proprietary formats. Concurrently, the adoption of OPC UA (Unified Architecture), standardized by the in collaboration with PLCopen starting in 2008—including the release of companion specifications in 2014—allowed secure, platform-independent communication between PLCs and higher-level systems, embedding data models for real-time data access and control. Additionally, there has been a shift toward high-level languages like for implementing complex algorithms, such as PID control or data analytics, enabling PLCs to handle Industry 4.0 applications like while maintaining with legacy .

System Overview and Principles

Definition and core purpose

A programmable logic controller (PLC) is a ruggedized digital computer specifically designed for real-time control of processes, electromechanical , and industrial machinery. It operates by receiving inputs from sensors and devices, processing them according to a user-defined program, and outputting commands to actuators and machinery to execute control actions. This architecture enables precise in environments where reliability is paramount, such as assembly lines and process plants. The core purpose of a PLC is to automate sequential and control tasks through programmable logic, thereby replacing traditional hard-wired systems with flexible, software-based alternatives. By emulating in a digital format, PLCs allow for rapid reconfiguration of control sequences without the need for extensive physical rewiring, which was a significant limitation of electromechanical systems. This shift, originating in the late , addressed the growing complexity of industrial automation by enabling dynamic adaptations to production changes. Key characteristics of PLCs include deterministic execution via fixed scan times, ensuring predictable response intervals for time-critical operations. They are engineered for tolerance to harsh industrial conditions, such as extreme temperatures, , , and electrical , through robust enclosures and components. Additionally, PLCs offer , ranging from compact units handling a few I/O points to expansive distributed systems managing thousands of signals across large facilities.

Basic components and block diagram

A programmable logic controller (PLC) consists of several core components that enable it to monitor inputs, execute control logic, and manage outputs in industrial environments. The serves as the brain of the system, interpreting and executing the user-defined program to process input data and determine output states. Input modules interface with field devices such as sensors and switches, converting real-world signals (e.g., digital on/off states or analog values) into formats the CPU can . Output modules, conversely, translate CPU commands into signals that drive actuators, relays, , or other control elements. A dedicated provides stable DC voltage, typically 24 VDC, to all components, ensuring reliable operation in harsh conditions. Memory in a PLC is categorized by function to support program storage and data handling. (RAM) holds runtime data, including temporary variables and status during program execution, but it is volatile and requires battery backup to retain information during power loss. (ROM) or electrically erasable programmable read-only memory () stores the , operating system, and fixed program instructions, offering non-volatile . Retentive memory, often a of RAM or , preserves critical data like setpoints and counters across power cycles for continuous process monitoring. The of a typical PLC illustrates a sequential scan cycle: field inputs from sensors flow through input modules to the CPU, which processes the logic program stored in and updates output states accordingly before sending signals via output modules to actuators. Communication buses, such as a or serial links, interconnect these modules, enabling data exchange; the system supports I/O counts ranging from as few as 8 points in compact units to over 65,000 in expansive configurations. This architecture ensures deterministic execution, with the CPU scanning the program in milliseconds. PLC systems integrate components in rack-mounted or distributed configurations to suit varying scales. In rack-mounted setups, modules plug into a with a shared for high-speed communication and power distribution, ideal for centralized control in factories. Distributed systems, by contrast, deploy remote I/O modules connected via networks, reducing wiring in large facilities while maintaining modular expansion.

Hardware Architecture

Processor, , and power supply

The processor in a programmable logic controller (PLC) serves as the central computational unit, typically implemented as a microprocessor-based CPU using 32-bit or 64-bit architectures such as or processors to ensure reliable real-time operation in industrial environments. For instance, the S7-1500 CPU 1513-1 PN employs a high-performance processor capable of executing bit operations in as little as 40 nanoseconds and word operations in 48 nanoseconds, enabling efficient handling of complex control tasks. These CPUs manage the PLC's core scan cycle, which typically operates at intervals of 1 to 100 milliseconds, encompassing input reading, program execution, and output updating to maintain deterministic control. Integrated watchdog timers further enhance reliability by monitoring scan cycle duration; if the cycle exceeds a predefined threshold—such as 100 milliseconds for a nominal 20-millisecond scan—the timer triggers a fault detection response, halting operations to prevent unsafe conditions. PLC memory is organized in a to support both volatile and non-volatile storage needs, with program dedicated to user logic (up to several megabytes in modern units) and data for runtime variables, tags, and states. In the S7-1500 CPU 1513-1 PN, for example, work allocates 300 kilobytes for programs and 1.5 megabytes for data, while load uses flash-based SIMATIC Memory Cards expandable to 32 gigabytes for non-volatile program retention and backups. Similarly, Rockwell Automation's ControlLogix 5580 controllers provide integrated from 3 megabytes to 40 megabytes for combined program and data storage, facilitating for applications ranging from simple sequences to advanced . This structure aligns with the scan cycle : during each iteration, inputs are scanned into data , the program executes using both types, and outputs are updated based on results, ensuring consistent without in power interruptions when backed by flash. The power supply in PLCs is designed for robust, isolated operation to withstand industrial electrical , commonly providing 24 V DC output with between input and output circuits for safety and . Devices like the Phoenix Contact QUINT-PS/1AC/24DC/10 deliver 24 V DC at 10 A, incorporating selective fuse-breaking for surge protection against transients up to industrial standards. features, such as integration with uninterruptible power supplies (UPS), enable seamless in critical systems, while built-in surge suppression handles voltage spikes from switching or lightning, often complying with for . is optimized for compliance, with many units achieving over 90% efficiency and idle power consumption below 10 to minimize and operational costs in continuous-duty environments. High-end PLC processors support advanced performance metrics, including clock speeds reaching up to 1 GHz in select models for multitasking capabilities, often running real-time operating systems like or the runtime environment. , for example, powers embedded real-time PLC designs by providing deterministic scheduling for scan cycles and fault-tolerant execution. The runtime further enables compliant multitasking on diverse hardware, distributing tasks across cores for improved throughput in networked systems.

Input/output modules and signal handling

Input/output (I/O) modules serve as the interface between a programmable logic controller (PLC) and the physical processes it controls, converting field signals into digital data for processing and vice versa. These modules handle both discrete and analog signals, enabling PLCs to monitor sensors and actuate devices in industrial environments. As part of the modular hardware architecture, I/O modules are typically pluggable cards that expand the PLC's capability to connect with diverse field devices, supporting configurations from a few points in compact systems to hundreds in larger setups. Discrete I/O modules process binary signals, representing on/off states for digital control. Input modules accept signals from devices such as proximity sensors, limit switches, and pushbuttons, commonly using 24 V DC or 120 V AC voltages. These modules employ optocouplers for electrical isolation, with typical channel counts of 8 to 32 points per module. Output modules drive actuators like solenoids, indicator lights, and relays, also supporting 24 V DC (sinking or sourcing) or 120 V AC configurations to match field device requirements. Sinking outputs (NPN) provide a path to ground, drawing current into the module, while sourcing outputs (PNP) supply positive voltage, pushing current out—configurations must align with connected devices to ensure proper operation. Analog I/O modules manage continuous signals for variables like , , and flow, using standardized ranges such as 4-20 mA current loops or 0-10 V voltage signals to minimize noise and enable long-distance transmission. Input modules incorporate analog-to-digital (A/D) converters to digitize these signals, typically offering 12- to 16-bit resolution for precision equivalent to 0.1% accuracy across industrial ranges. Output modules use digital-to-analog (D/A) converters to generate signals for devices like variable-speed drives or proportional valves, with similar resolution and range support. Channel densities vary, but modules often handle 2 to 8 channels, scalable through in higher-density designs. Signal conditioning in I/O modules ensures reliable amid industrial noise and transients. For discrete signals, optocouplers provide basic isolation, while analog modules feature up to 1500 V to prevent ground loops and protect the PLC from high-voltage surges. Noise rejection is achieved through differential inputs, low-pass filters, and notch filters targeting 50/60 Hz interference, with configurable digital filtering times from 0 to 10 seconds per channel. High-density modules employ to share A/D or D/A resources across 16 to 64 channels, optimizing space without sacrificing performance. Expansion of I/O capacity is facilitated through remote modules connected via systems like , allowing distributed architectures that support thousands of I/O points across a facility. These remote setups reduce wiring complexity and enable , with individual modules maintaining the same discrete and analog handling capabilities as local ones.

Mechanical design and redundancy features

Programmable logic controllers (PLCs) are engineered with robust mechanical designs to withstand harsh industrial environments, including , , extremes, and mechanical stresses. Enclosures for PLC systems often achieve IP65 ratings, providing protection against ingress and low-pressure water jets from any direction, while DIN-rail mounting facilitates easy installation and modularity within control panels. Operating temperature ranges typically span from -20°C to 60°C for many standard PLC units, ensuring reliable performance in varied ambient conditions without additional cooling in moderate setups. IEC 61131-2 outlines environmental requirements, including sinusoidal tolerance of up to 1g over 10-150 Hz for main processing units and 2g for remote I/O stations during operation. Cooling and ventilation strategies in PLC designs prioritize reliability and minimal maintenance. Compact PLC models often employ fanless, to reduce points of failure and noise in space-constrained applications, relying on natural and heat sinks. In contrast, larger rack-mounted systems may incorporate cooling with fans to manage higher loads from multiple modules, though designs aim to minimize dust accumulation through filtered intakes. and shock resistance further enhances durability, with IEC 61131-2 specifying tolerance for operational shocks up to 15g in some configurations, allowing PLCs to operate in vibrating machinery environments. Redundancy features in PLCs ensure continuous operation in mission-critical settings by mitigating single points of . Hot-swappable modules allow I/O components to be replaced without system shutdown, maintaining process continuity during maintenance. Dual CPU configurations provide fault-tolerant processing, with bumpless transfer enabling switchover in typically 50 ms to several hundred milliseconds, depending on the system and configuration, to minimize disruptions in control logic execution. Mirrored power supplies decouple redundant inputs to prevent faults from propagating, often using diode-based isolation for seamless . These features are essential in high-stakes applications such as oil refineries, where can lead to significant and economic risks. PLCs are available in modular and compact form factors to suit diverse needs. Modular designs use scalable rack systems, often adhering to 19-inch standards for integration into industrial cabinets, allowing expansion with additional CPU, I/O, and communication modules as system requirements grow. Compact, all-in-one units integrate the CPU, , and limited I/O in a single enclosure, ideal for small machines or standalone controls where simplicity and low cost outweigh the need for extensive customization. This distinction enables engineers to select architectures that balance flexibility, ease, and initial based on application demands.

Programming PLCs

Standard programming languages

The (IEC) standard 61131-3 (edition 4.0, 2025) defines a suite of programming languages for programmable logic controllers (PLCs) to ensure portability, , and consistency in industrial . This standard specifies four languages: three graphical (Ladder Diagram, , and ) and one textual (). Instruction List (IL), a low-level textual language from previous editions, was removed in the 2025 edition but remains supported by many vendors for legacy applications. These languages support the creation of modular programs using function blocks, programs, and organizations, facilitating structured and reusable code. Ladder Diagram (LD) is a graphical language that mimics traditional relay ladder logic, using horizontal rungs to represent control circuits with vertical power rails. It employs symbols like normally open contacts (--| |--), normally closed contacts (--|/|--), and coils (--( )--) to denote inputs, outputs, and boolean operations, making it intuitive for electricians transitioning to PLC programming. For instance, an AND operation between inputs A and B to energize output C is depicted as:

--|A|--|B|--(C)

--|A|--|B|--(C)

LD excels in discrete control applications, such as machine sequencing, due to its visual similarity to electrical schematics. (FBD) is another graphical that represents logic as interconnected blocks, where each block processes inputs to produce outputs, emphasizing data flow. Standard blocks include logical operators like AND and OR, as well as more complex ones such as PID controllers, allowing for modular designs in process-oriented systems. It supports execution from left to right or top to bottom, promoting reusability through user-defined function blocks. FBD is particularly useful for continuous control tasks, like in lines. Structured Text (ST) is a high-level, textual language resembling Pascal or , enabling complex algorithmic expressions with statements like , CASE, FOR loops, and arithmetic operations. It supports data typing and function block calls, making it suitable for mathematical computations and conditional logic beyond simple operations. An example for turning off a heater if temperature exceeds 100 is:

IF temp > 100 THEN heater := FALSE; END_IF;

IF temp > 100 THEN heater := FALSE; END_IF;

ST is ideal for applications requiring intricate calculations, such as data analysis in control systems. Sequential Function Chart (SFC) is a graphical language for modeling sequential and state-based processes, structured as a series of steps connected by transitions, with actions associated to steps. Derived from Grafcet and Petri nets, it decomposes batch or machine operations into states (e.g., "FILL" or "EMPTY"), enabling parallel branches and hierarchical designs. Transitions are triggered by boolean conditions, facilitating clear visualization of process flows. SFC is widely applied in batch processing and automated assembly lines. While promotes standardization, vendors may implement limited proprietary extensions, such as additional function blocks or syntax enhancements (e.g., C++-like integrations), provided they do not conflict with the core standard to maintain basic across compliant systems. These extensions allow customization for specific hardware but can introduce if over-relied upon.

Development tools and devices

Development tools for programmable logic controllers (PLCs) encompass both hardware devices and software environments designed to facilitate the creation, editing, and deployment of control programs. Programming devices typically include handheld terminals for smaller PLC systems, which connect directly to the controller via serial ports or interfaces to enter basic or function block diagrams without requiring a full computer setup. These portable units are particularly suited for on-site modifications in compact applications, such as controls, due to their low cost and ease of use. For larger or more complex systems, personal computers or laptops serve as the primary programming devices, interfacing with the PLC through USB, Ethernet, or serial connections to enable comprehensive program development. A representative example is Rockwell Automation's Connected Components Workbench (CCW), a suite that supports programming of Micro800 controllers via Ethernet or USB, allowing users to configure hardware and develop applications in a unified environment. Similarly, handheld programmers have been used historically by vendors like for SLC 500 series PLCs, though modern preferences lean toward PC-based tools for enhanced functionality. Software environments for PLC programming are typically integrated development environments (IDEs) that provide graphical editors, tag management, and configuration tools to streamline the implementation of standard languages such as ladder diagram (LD) and (FBD). Siemens' Totally Integrated Automation (TIA) Portal, for instance, offers an intuitive interface for configuring, programming, and diagnosing controllers, featuring drag-and-drop editors and centralized tag databases to manage variables across projects. Schneider Electric's EcoStruxure Machine Expert provides a similar single-environment approach, enabling hardware configuration, programming in multiple languages, and commissioning of Modicon controllers through visual tools and reusable libraries. These IDEs support vendor-specific extensions while adhering to open standards, reducing development time by integrating device parameterization with code editing. The deployment process begins with compiling the user-written program—often in graphical or textual formats—into machine-readable optimized for the PLC's processor. This compilation step checks for syntax errors and generates executable blocks, as implemented in tools like TIA Portal where program data is transformed into loadable modules for the controller. The compiled program is then downloaded to the PLC via Ethernet or serial links, with modern systems supporting partial downloads to update specific sections without halting operations. Online monitoring features in these environments allow real-time observation of variables and execution during deployment, enabling immediate edits and verification directly from the connected PC. Vendor-specific tools vary in proprietary features but increasingly incorporate open standards for , such as PLCopen's for exporting and importing program elements across different platforms. This IEC 61131-10 compliant format facilitates program exchange between tools, including POU definitions and configurations, without loss of structure. , a widely adopted multi-vendor IDE, exemplifies this by supporting hardware from over 500 manufacturers and enabling XML-based exports for seamless migration or integration with third-party systems. Such standards promote flexibility in development workflows, allowing to work across ecosystems while maintaining compatibility with programming paradigms.

Simulation, testing, and debugging

for programmable logic controllers (PLCs) enables engineers to verify and refine programs in a , eliminating the need for physical hardware during initial development stages. These tools create digital twins of PLC systems, replicating key operational behaviors such as (I/O) interactions and execution cycles to facilitate offline testing. For instance, Siemens' S7-PLCSIM Advanced emulates the and behavior of SIMATIC S7 controllers, allowing comprehensive of control programs without hardware. This includes support for testing by simulating scan cycles, forcing I/O values to mimic real-world signals, and incorporating timing elements to evaluate program responses under various conditions. Testing strategies for PLC programs progress from isolated components to full system integration, ensuring reliability before deployment. Unit tests focus on individual functions or rungs within the program, verifying logic without external dependencies, often using built-in simulator features to isolate and execute code segments. Integration tests then combine these units with virtual I/O modules to check interactions, such as data flow between logic blocks and simulated sensors. Hardware-in-the-loop (HIL) testing advances this by connecting the PLC software to actual I/O modules or physical components within a controlled simulation loop, validating performance in near-real conditions while mitigating risks to live systems. This approach, as detailed in studies on PLC validation, enhances fault detection by simulating complex machine interactions. Debugging tools integrated into PLC development environments provide granular control over program execution to identify and resolve issues efficiently. Breakpoints allow programmers to pause execution at specific code lines or when variable conditions are met, enabling step-by-step inspection of logic flow. Watch windows monitor real-time values of variables, arrays, and I/O points during or online runs, while trace logs record execution paths, timestamps, and state changes for post-analysis. These features, exemplified in , also support error handling for syntax errors—detected during compilation—and runtime faults, such as invalid array accesses or overflow conditions, by halting execution and displaying diagnostic messages. Compliance with international standards ensures that simulation, testing, and processes meet requirements for critical applications. The standard outlines validation techniques for programmable electronics, including software and hardware verification through structured testing plans that cover all operational modes and failure scenarios. A key method is , where simulated errors—such as bit flips or signal losses—are introduced to assess system robustness and diagnostic coverage, particularly for achieving Safety Integrity Levels (SIL). This validation, often performed by independent assessors, confirms that PLC programs handle faults without compromising , as required for E/E/PE systems.

Operational Functionality

Core functions and logic operations

Programmable logic controllers (PLCs) implement core functions through standardized instructions that enable digital and analog control in industrial , as defined in the standard for programming languages. These functions form the foundation for executing logic operations, timing sequences, counting events, performing calculations, and handling specialized control tasks, allowing PLCs to manage complex processes reliably. Basic logic operations in PLCs replicate relay ladder logic using Boolean gates such as AND, OR, and NOT, which are essential for interlocking and conditional control. In ladder diagram form, AND is represented by series contacts that energize an output only when all inputs are true, while OR uses parallel contacts to activate the output if any input is true; NOT inverts the state of an input contact. For example, series contacts can interlock safety circuits to prevent machine startup unless multiple conditions like emergency stops and limit switches are satisfied. These operations execute at high speeds in modern PLCs, supporting real-time decision-making. Timers provide time-based control for sequencing operations, with standard types including on-delay (TON), off-delay (TOF), and retentive variants. The timer delays output activation until a preset time elapses after the input turns true, commonly used for startup delays in . TOF maintains the output true for a set duration after the input goes false, suitable for cooldown periods, while retentive timers like accumulate elapsed time across power cycles until reset, preserving state in volatile environments. memory usage varies by PLC model and data structure. Counters track discrete events or pulses for applications like and position monitoring. Up counters (CTU) increment a value each time the input pulses until reaching a preset limit, triggering an output for sequencing tasks such as conveyor counts. Down counters (CTD) decrement similarly for countdowns, and bidirectional counters (CTUD) allow both directions based on input signals, often used with encoders for bidirectional motion. High-speed counters handle rapid inputs for precise , with capabilities varying by model, such as up to 200 kHz and multiple instances supporting quadrature phase detection in some systems like the Siemens S7-1200. Counter storage varies by and PLC implementation. Mathematical operations facilitate data processing, such as scaling analog sensor values or calculating totals. Addition (ADD), subtraction (SUB), and multiplication (MUL) support integer and floating-point types, enabling tasks like converting voltage readings to engineering units. Comparison instructions like equal (EQ), greater than (GT), and less than (LT) evaluate conditions for branching logic, outputting a Boolean result to direct program flow based on thresholds. Special functions extend core capabilities for advanced control, including proportional-integral-derivative (PID) loops for regulating processes like or flow. PID instructions compute control outputs using proportional, , and terms to minimize , often with self-tuning for optimal performance in continuous systems; for example, the PID_Compact instruction in PLCs. Bit manipulation operations like shift left (BSL), shift right (BSR), and move (MOV) handle data transfer and pattern adjustment, with MOV copying values between registers while supporting . These functions are implemented across languages like ladder diagram and for versatile programming.

Communication protocols and networking

Programmable logic controllers (PLCs) rely on various communication protocols to exchange with other devices, sensors, actuators, and higher-level systems in industrial environments. These protocols enable real-time control, monitoring, and integration within networks, supporting topologies from point-to-point connections to large-scale distributed systems. Early protocols focused on for cost-effective, simple setups, while later developments introduced standards for deterministic performance and modern Ethernet-based solutions for high-speed, scalable networking. Serial protocols form the foundation of PLC communication, particularly for short-distance, low-to-medium speed applications. is a point-to-point standard used for direct connections between a PLC and a single device, supporting full-duplex communication over distances up to 15 meters at speeds up to 20 kbps in typical industrial settings. In contrast, enables multi-drop networks, allowing up to 32 devices (extendable with repeaters) in a half-duplex configuration over longer distances up to 1,200 meters, making it suitable for connecting multiple I/O modules to a PLC via twisted-pair cabling. A prominent example is RTU, which operates over in a master-slave model, supporting up to 247 slave devices on a single network with baud rates up to 115.2 kbps and employing (CRC-16) for error detection to ensure reliable data transmission. Fieldbus protocols extend serial communication to provide more robust, deterministic networking for factory automation. , defined in IEC 61158 Type 3, operates as a multi-master token-passing bus with data rates up to 12 Mbps over cabling, enabling precise timing for cyclic exchange in process control applications. , built on the Controller Area Network (CAN) physical layer, uses a trunkline-dropline with speeds up to 500 kbps and integrates DC power distribution, facilitating peer-to-peer messaging via the (CIP) for device-level connectivity in manufacturing. adapts CIP over standard Ethernet (), leveraging TCP/IP for client-server interactions at speeds exceeding 100 Mbps, which supports seamless integration of PLCs into enterprise networks while maintaining real-time capabilities through producer-consumer models. Contemporary protocols address the demands of Industry 4.0 by emphasizing , , and IoT connectivity. OPC UA provides a platform-independent, for secure data access and control, enabling PLCs to publish structured information to supervisory systems without vendor-specific dependencies. , a lightweight publish-subscribe protocol, facilitates efficient messaging over constrained networks in industrial IoT setups, allowing PLCs to transmit real-time status updates to services with minimal overhead. PLC networking configuration involves setting parameters such as device addressing, transmission speeds, and error-handling mechanisms to ensure compatibility and reliability. Addressing schemes, like unique slave IDs in or node addresses in , prevent conflicts in multi-device setups, while configurable rates (e.g., 9.6 kbps to 12 Mbps) balance speed and distance. Error checking, typically via CRC or parity bits, detects transmission faults, with protocols supporting models like master-slave for hierarchical control or peer-to-peer for direct device interactions. Physical links to these networks often interface through dedicated I/O modules.

Human-machine interfaces

Human-machine interfaces (HMIs) in programmable logic controllers (PLCs) enable operators to monitor, control, and interact with in real time, bridging the gap between human operators and automated systems. These interfaces facilitate visualization of system status, input of commands, and acknowledgment of events such as alarms, enhancing and safety in environments. Hardware-based HMIs typically consist of dedicated panels, commonly ranging from 7 to 15 inches in size, which connect to PLCs via Ethernet for seamless data exchange. These panels display graphical representations known as mimics that illustrate process flows, real-time alarms to alert operators of anomalies, and trend charts to visualize historical data variations. For instance, a 12.1-inch HMI can integrate up to 1000 I/O points while rendering dynamic process diagrams. Key features of these touchscreen HMIs include recipe management for storing and selecting production parameters, data logging to record process variables for analysis, and graphical animations that simulate equipment states for intuitive operation. Operator inputs on these panels are designed to achieve response times under 500 milliseconds, ensuring prompt feedback and minimizing delays in critical tasks. Software-based HMIs extend accessibility beyond physical panels by incorporating web servers directly into PLCs, allowing operators to access interfaces via standard web browsers on devices like tablets or computers. These solutions often integrate with supervisory control and (SCADA) systems for higher-level oversight, enabling remote monitoring and control across networked environments. To support in diverse setups, HMI protocols adhere to standards such as (OPC DA), which standardizes data exchange between multi-vendor devices and applications. Tools like Kepware implement these OPC standards as connectivity platforms, facilitating reliable communication between HMIs, PLCs, and other industrial components without proprietary limitations.

Scan Cycle and Execution

The PLC scan process

The PLC scan process is a fundamental, repetitive cycle that ensures deterministic control in industrial automation systems. This cycle, also known as the scan cycle, consists of three primary phases executed sequentially by the PLC's (CPU): input scan, program execution, and output scan. These phases operate in a continuous loop, allowing the PLC to monitor field devices, process control logic, and update actuators without direct real-time interaction between inputs and outputs during logic evaluation, thereby preventing erratic behavior from momentary changes. In the input scan phase, the PLC reads the current states of all connected input devices, such as sensors and switches, and stores these values in an input image table within its . This snapshot isolates the input data from subsequent changes during the rest of the cycle, ensuring stable logic processing. For instance, binary signals (on/off) or analog values are captured and held in the image table until the next scan. During the program execution phase, the PLC evaluates the user-defined control program—typically in or other languages—using the data from the input image table. The CPU processes the logic sequentially, rung by rung or block by block, computing the desired states for outputs and storing them in an output image table. This phase relies on core functions like logical operations (AND, OR, NOT) and timers, but defers actual I/O updates to maintain scan integrity. The output scan phase then transfers the computed values from the output image table to the physical output modules, energizing or de-energizing devices like or valves accordingly. This ensures that outputs reflect the logic results only at of each cycle, providing a consistent control response. To handle high-speed or time-critical tasks that cannot wait for the main scan, many PLCs support asynchronous events through routines. These interrupts, such as event tasks in Rockwell Logix5000 controllers or hardware interrupts in Siemens S7-1500 systems, execute specialized code outside the primary cycle when triggered by events like input or motion signals. For example, high-speed counters for pulse tracking operate independently to avoid missing rapid changes. The scan cycle is initiated by the PLC's internal CPU clock following power-up and initialization, establishing synchronous operation where each loop begins with the input scan and repeats indefinitely during runtime. This clock-driven repetition guarantees predictable execution without external triggers for standard operations. A practical example illustrates the flow: in a system, the input scan detects a signal indicating a package arrival; the program execution then evaluates conditions (e.g., if the belt is clear, set motor output to on); and the output scan energizes the motor to start the conveyor. This sequence ensures reliable, step-by-step control.

Timing, synchronization, and performance considerations

The scan time in a programmable logic controller (PLC) represents the duration required to complete one full execution cycle, encompassing input scanning, program execution, and output updating, and typically ranges from 1 to 100 milliseconds depending on the system's configuration. This time is primarily influenced by program size, where larger programs with thousands of logic instructions extend the cycle; for instance, high-end PLC models can handle millions to billions of instructions per second, depending on the processor and instruction type. Additionally, communications overhead from network interactions or data exchanges adds latency, potentially increasing scan time by diverting CPU resources from core logic execution. In networked PLC environments, synchronization is essential to maintain coordinated operations across multiple devices, addressing clock drift through protocols like Precision Time Protocol (PTP) defined in IEEE 1588, which enables master-slave timing with sub-microsecond accuracy in many implementations, often achieving less than 1 µs synchronization error. Clock drift compensation in these systems involves periodic timestamp exchanges to adjust for variations in oscillator frequencies, ensuring deterministic behavior in distributed control applications. This precision is critical for real-time industrial processes, where PTP implementations in PLC networks can deliver synchronization accuracies below 100 nanoseconds under optimal conditions. Key performance metrics for PLCs include throughput, measured as I/O update rates often reaching thousands per second in high-speed configurations (e.g., over 2,000 pulses per second for encoder inputs), and latency, which is typically under 1 to support responsive event handling. Bottlenecks such as access delays can degrade these metrics, as slower RAM or cache misses prolong instruction fetch times during execution, particularly in systems with extensive logging or complex algorithms. These factors directly impact reliability in real-time applications, where consistent I/O throughput ensures timely sensor-actuator interactions without . To enhance performance, PLC optimizations include program partitioning into subroutines or tasks to isolate critical sections and reduce overall scan time, as well as disabling or removing unused code blocks to minimize unnecessary processing overhead. In safety-critical systems, (WCET) analysis is employed to statically predict maximum task durations, accounting for hardware effects like pipeline stalls and ensuring compliance with real-time deadlines through tools that model instruction paths and loop bounds. This approach, rooted in embedded systems research, verifies that WCET bounds remain within specified limits, preventing overruns in applications like automotive or controls integrated with PLCs.

Safety, Security, and Advanced Features

Safety-certified PLCs

Safety-certified programmable logic controllers (PLCs), also known as safety PLCs, are specialized variants engineered to ensure operation in environments where system failures could lead to hazards, such as industrial machinery or control. These devices incorporate redundant hardware architectures to detect and respond to faults, prioritizing the transition to a predefined safe state to mitigate risks to personnel and equipment. Unlike standard PLCs, safety-certified models undergo rigorous certification processes to meet international standards, enabling their use in safety instrumented systems (SIS). A core feature of safety PLCs is their hardware redundancy, typically including dual processors that execute the same control logic in parallel and continuously cross-compare results for consistency. If discrepancies arise, such as due to processor faults, the system activates diagnostic mechanisms like watchdog circuits to monitor memory integrity, including flash and RAM, ensuring high fault detection rates. Upon detecting any anomaly, the PLC forces outputs to a safe state, often de-energizing actuators to prevent unintended operation, thereby avoiding dangerous failures. Safety PLCs comply with key international standards for , including , which defines Safety Integrity Levels (SIL) up to SIL 4 for the highest risk reduction, and ISO 13849-1, which specifies Performance Levels (PL) up to PL e for machinery safety-related parts of control systems. These standards mandate diagnostic coverage exceeding 99% for critical faults, such as stuck outputs or channel cross-connections, achieved through built-in self-tests and . Additional features include dedicated safety I/O modules that support test pulses—periodic voltage signals sent to inputs to verify wiring integrity and detect faults like shorts—enhancing diagnostic coverage without interrupting operations. These modules also facilitate seamless integration with emergency stop (E-stop) devices, where activation triggers immediate safe state transitions across the system. Programming for safety PLCs utilizes safety-specific variants of standard languages, such as or function block diagrams (FBD), which enforce fault-tolerant structures and validation checks to maintain certification compliance. In applications, safety-certified PLCs are essential for , where they monitor safeguards like light curtains or interlocks to halt operations if breaches occur, and for process shutdowns in hazardous environments, such as chemical plants, to prevent escalations. Representative examples include the Pilz PSS 4000 series, which supports SIL 3 applications in automated assembly lines for guarding, and Rockwell Automation's GuardLogix controllers, certified to SIL 3 and PL e for integrated safety in systems like robotic cells.

Cybersecurity measures and vulnerabilities

Programmable logic controllers (PLCs) face significant cybersecurity vulnerabilities, particularly in connected industrial environments, where exploits can disrupt critical operations. A prominent example is the worm, discovered in 2010, which specifically targeted Step7 software and S7-300 PLCs by exploiting four zero-day vulnerabilities in Windows to inject malicious code that altered centrifuge speeds in Iran's nuclear facilities. This attack highlighted firmware manipulation risks, as reprogrammed PLC logic without detection, demonstrating how legacy systems with unpatched software remain susceptible even years later. Additionally, common vulnerabilities include weak or default passwords and exposed open ports, such as TCP port 102 in S7 PLCs, which allow unauthorized access via protocols like or without authentication. These issues enable attackers to gain , as seen in incidents where default credentials facilitated entry into (OT) networks. To mitigate these threats, several cybersecurity measures are implemented for PLCs. Encryption protocols like TLS 1.3 secure communications between PLCs and other devices, preventing interception of data in transit, while (RBAC) limits user privileges based on predefined roles to reduce insider risks. Firmware signing and secure boot processes verify the integrity of updates before execution, ensuring only authorized code runs on the device; for instance, PLCs use cryptographic signatures to detect tampering during boot. Air-gapping, isolating critical PLCs from external networks, provides a robust defense for high-security applications, though it limits remote monitoring. Intrusion detection systems (IDS) employing monitor PLC behavior for deviations, such as unusual command frequencies or process anomalies, alerting operators to potential intrusions. Standards guide these protections, with providing a framework for securing industrial automation and control systems (IACS), including requirements for secure product development and system zoning to isolate PLCs. Similarly, NIST SP 800-82 Revision 3 outlines OT security practices, emphasizing risk assessments, secure configurations, and continuous monitoring for ICS like PLCs. Post-2020 threats, including that can impact OT networks through IT compromises—such as the 2021 Colonial Pipeline attack, where an IT network breach led to precautionary OT shutdowns—underscore the need for zero-trust architectures, which verify every access request regardless of origin, and regular patching to address evolving . As of 2025, attacks against sectors like have surged by 34%, with over 50% of incidents targeting these areas, emphasizing the growing risks to PLC-integrated systems. These measures, when combined, enhance PLC resilience against sophisticated attacks.

Integration with modern industrial systems

Programmable logic controllers (PLCs) have evolved to seamlessly integrate with modern industrial systems, particularly within the framework of Industry 4.0, enabling enhanced connectivity, data-driven decision-making, and operational efficiency in smart factories. This integration positions PLCs as central nodes in interconnected ecosystems, bridging traditional (OT) with (IT) infrastructures to support real-time monitoring and advanced analytics. In the realm of Industrial Internet of Things (IIoT), PLCs serve as gateways that collect and preprocess data from sensors and machinery before transmitting it to cloud platforms such as AWS IoT. This architecture allows for applications, where AI analytics process real-time data from equipment sensors, including patterns, to forecast potential failures and minimize . For instance, AWS IoT integrates with to build models directly from PLC-sourced industrial data, enabling automated and maintenance scheduling. Such IIoT-enabled PLC systems enhance equipment reliability by fusing IoT connectivity with PLC control logic, optimizing across distributed industrial sites. Digital twins represent another key integration aspect, where virtual replicas of physical assets are synchronized with PLC-generated to facilitate , optimization, and what-if . These models leverage PLC inputs for dynamic updates, allowing manufacturers to predict system behaviors and refine processes without disrupting live operations. Standards like ISA-95 (IEC 62264) play a crucial role by defining hierarchical models for integrating manufacturing execution systems (MES) with () systems, ensuring standardized data exchange between PLC-controlled shop floors and higher-level business applications. This compliance streamlines , reduces integration errors, and supports holistic deployments in complex environments. Hybrid systems further advance PLC capabilities by incorporating embedded vision and AI modules directly into control architectures, fostering intelligent automation in smart factories. For example, Rockwell Automation's LogixAI module embeds coprocessors within ControlLogix PLCs, enabling on-device predictive modeling using native controller tags for tasks like in production lines. Similarly, FactoryTalk Analytics VisionAI integrates AI-driven vision with PLC systems, providing real-time assessments and yield optimization through embedded . These hybrid configurations allow PLCs to handle advanced perceptual tasks, such as defect detection via , without relying on external servers, thus improving responsiveness in dynamic industrial settings. Looking to trends in the 2020s, virtual PLCs (vPLCs) running on industrial PCs or environments are emerging for their flexibility and cost-effectiveness, decoupling control logic from dedicated hardware to enable scalable, software-defined in IT/OT-converged systems. This shift supports virtual PLC deployments that integrate seamlessly with and edge environments, reducing hardware dependencies while maintaining real-time performance. Additionally, networks are enabling low-latency of PLC systems, with ultra-reliable communication facilitating applications like in hazardous environments and synchronized multi-site operations. Sustainability efforts are also influencing PLC evolution, with a focus on energy-efficient programming techniques that optimize logic execution to lower power consumption in green manufacturing initiatives. These developments underscore PLCs' adaptability to resource-conscious industrial paradigms, promoting reduced environmental impact through intelligent .

Applications and Comparisons

Industrial and process control uses

Programmable logic controllers (PLCs) are extensively employed in to automate and coordinate complex sequences such as robotic welding in the automotive sector. In operations, PLCs manage the sequential control of machinery, ensuring precise timing for tasks like part feeding, positioning, and quality checks, which enhances production efficiency and reduces downtime. For instance, in automotive sequences, PLCs handle multiple (I/O) points to synchronize robotic arms, conveyor movements, and feedback for consistent application of coatings. In robotic welding applications, PLCs integrate with pneumatic systems and to control electrode positioning and rotation speeds, achieving uniform weld quality while doubling output compared to manual methods and minimizing labor costs. In process control industries, PLCs provide reliable for continuous operations like and oil and gas management. For water and , PLCs regulate pumps and valves through proportional-integral-derivative (PID) loops to maintain optimal flow rates, levels, and chemical dosing, enabling precise control that reduces reagent usage by up to 30% and pollutant removal efficiency of 89%. Electromagnetic valves and dosing pumps are directly actuated by the PLC based on real-time data, streamlining stages such as and to shorten cycle times by 31%. In the oil and gas sector, PLCs interface with supervisory control and (SCADA) systems to monitor pressures, flow rates, and , allowing remote oversight and rapid response to anomalies across extensive networks. PLCs also play a key role in , particularly for systems like (HVAC) and elevators, where they ensure energy-efficient and safe operations. In HVAC setups, PLCs sequence fan activation based on temperature thresholds from sensors, modulating speeds to optimize and maintain occupant comfort while integrating with broader for and . For elevators, PLCs manage floor selection, door operations, and emergency protocols, using inputs from position sensors and buttons to coordinate multi-floor movements reliably in high-traffic environments. The scalability of PLC systems accommodates a wide range of applications, from small setups with around 20 I/O points for simple conveyor sorting tasks—where basic sensors and actuators handle item detection and diversion—to large-scale installations exceeding 10,000 I/O points in mills, coordinating redundant controls for rolling processes, regulation, and to ensure uninterrupted production. These systems often incorporate redundancy for in critical operations.

Comparisons with microcontrollers and embedded systems

Microcontrollers, such as and PIC series, are general-purpose integrated circuits designed for a wide range of applications, including embedded systems, with costs typically ranging from $1 to $10 per unit. They are programmable in languages like or assembly, offering high flexibility for custom logic but lacking the rugged construction required for industrial environments, such as optical isolation for I/O to prevent noise interference and protection against extreme temperatures or vibrations. In contrast, programmable logic controllers (PLCs) provide built-in diagnostics for fault detection and self-monitoring, compliance with international standards like for programming and safety, and simplified maintenance through modular designs that facilitate easy troubleshooting and upgrades in operational settings. While s excel in low-power, compact applications with minimal overhead, PLCs incur higher costs—often starting at $500 for basic industrial units—due to their hardened enclosures, redundant power supplies, and extensive I/O capabilities tailored for harsh conditions. This makes PLCs less suitable for non-industrial tasks where cost and customization are paramount, as their standardized prioritizes reliability over optimization. However, PLCs offer superior scalability for expanding control systems without full redesigns, a feature absent in most microcontroller setups that require additional hardware for growth. Embedded systems that incorporate PLC functionality, such as "PLC on a chip" solutions from Divelbiss Corporation, integrate control logic directly into system-on-chips (SoCs) for compact devices like machinery controllers or IoT endpoints, reducing size and development time compared to discrete PLC hardware. These embedded PLC variants trade off the of traditional PLCs—which allow easy I/O expansion and vendor —for tighter integration and lower power use in space-constrained applications. In practice, microcontrollers suit prototyping, hobby projects, and small-scale custom builds where rapid iteration is key, whereas PLCs are essential for certified industrial reliability in and control, ensuring compliance and minimal downtime.

Comparisons with single-board computers and programmable relays

Single-board computers (SBCs), such as the , offer versatile, Linux-based computing platforms with high processing speeds typically ranging from 0.7 to 2.4 GHz and (GPIO) pins for interfacing with sensors and actuators. These devices support a wide array of programming languages like Python and C++, enabling complex tasks including and integration with applications. However, SBCs lack inherent real-time guarantees due to operating system overhead, which can introduce latency and in control loops, making them unsuitable for time-critical industrial automation without additional real-time kernels or hardware modifications. Furthermore, they are vulnerable to crashes from software faults or power fluctuations and are not ruggedized for harsh environments, such as extreme temperatures or electrical noise, often requiring protective enclosures for industrial deployment. Programmable logic relays (PLRs), exemplified by the LOGO! series, are compact devices designed for straightforward tasks, typically supporting 8 to 24 digital I/O points with basic analog capabilities in expanded configurations. They utilize or programming via user-friendly software, allowing replacement of traditional panels in small-scale applications like control or simple machinery sequencing. Priced between approximately $50 and $200 depending on the model and I/O expansion, PLRs are cost-effective for low-complexity logic but are limited to basic digital operations without support for high-speed counting, advanced analog processing, or extensive networking. Unlike full PLCs, they prioritize simplicity over scalability, making them ideal for cost-sensitive, non-demanding setups in residential or light industrial contexts. PLCs distinguish themselves through deterministic execution, ensuring predictable scan times in milliseconds for reliable real-time control, which is essential for safety-critical processes where timing precision prevents equipment damage or hazards. Their longevity is evidenced by high (MTBF) often exceeding 1 million hours, translating to operational lifespans of 15 years or more in industrial settings, supported by robust construction for temperatures from -20°C to 65°C and resistance to vibrations and . In contrast to SBCs' flexibility for non-deterministic tasks like AI integration, PLCs excel in harsh environments but at higher costs, while PLRs offer affordability for basic logic without the determinism or I/O versatility of PLCs. Vendor ecosystems, such as those from or , provide long-term support including software updates and spare parts, enhancing PLC reliability over the product lifecycle. Emerging hybrid approaches leverage SBCs to emulate PLC functionality through open-source software like OpenPLC, which runs on hardware to support programming and I/O handling via GPIO pins, enabling cost-effective prototyping or non-critical applications. This trend allows SBCs to mimic PLC scan cycles for simpler industrial uses, such as monitoring in , but retains limitations in real-time performance and environmental durability compared to dedicated hardware. Meanwhile, PLRs continue to serve cost-sensitive small machines, bridging the gap between hardwired relays and full PLCs without the need for advanced computing resources. Remote Terminal Units (RTUs) differ from PLCs in their primary focus on remote monitoring and data acquisition within Supervisory Control and Data Acquisition (SCADA) systems, often used in utilities, oil and gas, and water management, whereas PLCs emphasize complex local logic execution and deterministic real-time control for manufacturing and process automation. RTUs are engineered with superior environmental ruggedness, capable of operating in extreme remote conditions such as temperatures from -40°C to 85°C, high humidity, and dust, making them suitable for field deployments where PLCs might require additional protection. Configuration for RTUs is typically simpler, utilizing web-based interfaces or basic scripting for setup, in contrast to the more sophisticated programming languages like ladder logic required for PLCs, which demand greater engineering expertise. In terms of I/O and communication capabilities, RTUs often support a larger number of inputs/outputs, including analog and digital, with emphasis on long-distance telemetry protocols like Modbus or DNP3 for reliable data transmission over networks, while PLCs provide scalable, high-speed I/O modules optimized for local, precise control but with potentially less focus on extended remote communications.

References

  1. https://digitalcommons.georgefox.edu/cgi/viewcontent.cgi?article=1022&context=mece_fac
  2. https://erieit.edu/introduction-to-programmable-logic-controllers/
  3. https://fi.edu/en/awards/laureates/richard-e-morley
  4. https://scholarsmine.mst.edu/cgi/viewcontent.cgi?article=1684&context=ele_comeng_facwork
  5. https://www.controleng.com/how-programmable-logic-controllers-emerged-from-industry-needs/
  6. https://www.realpars.com/blog/father-of-the-plc
  7. https://www.allaboutcircuits.com/news/historical-engineers-richard-morley-programmable-logic-controller-PLC/
  8. http://large.stanford.edu/courses/2016/ph240/parthasarathy2/docs/sans-aug14.pdf
  9. http://archive.control.lth.se/media/Education/DoctorateProgram/2012/HistoryOfControl/Vanessa_Albert-PLCDCS.pdf
  10. https://www.dosupply.com/tech/2020/03/31/infographic-history-of-plcs-1968-2000/
  11. https://www.siemens.com/global/en/company/about/history/specials/60-years-of-simatic.html
  12. https://www.se.com/ww/en/about-us/company-profile/history/schneider-electric-history/
  13. https://hybridplc.org/wp-content/uploads/chap1_S.pdf
  14. https://learntechnique.com/short-history-plc-programming-platforms/
  15. https://www.c3controls.com/white-paper/history-of-programmable-logic-controllers
  16. https://rlconsultinginc.com/the-history-of-plc-programming/
  17. https://control.com/technical-articles/an-overview-of-iec-61131-3-Industrial-Automation-Systems/
  18. https://webstore.iec.ch/en/publication/68533
  19. https://www.plcopen.org/download_file/view/02701805-7b7e-499a-bcf8-38f3e9ae8e32/
  20. https://opcfoundation.org/wp-content/uploads/2014/04/PLCopen-OPCF-Release-of-OPC-UA-FBs-EN_20140409.pdf
  21. https://www.plcopen.org/standards/xml-echange/
  22. https://opcfoundation.org/markets-collaboration/plcopen/
  23. https://www.controleng.com/are-you-making-the-most-of-plc-programming-standards-from-plcopen/
  24. https://inductiveautomation.com/resources/article/what-is-a-PLC
  25. https://www.allaboutcircuits.com/textbook/digital/chpt-6/programmable-logic-controllers-plc/
  26. https://www.hilscher.com/service-support/glossary/programmable-logic-controller-plc
  27. https://library.automationdirect.com/history-of-the-plc/
  28. https://www.weintekusa.com/plc-vs-scada-vs-hmi-whats-the-difference/
  29. https://www.empoweredautomation.com/automation-plc-key-features-and-benefits-explained
  30. https://www.empoweredautomation.com/what-is-the-difference-between-mes-and-plc
  31. https://cache.industry.siemens.com/dl/files/842/109752842/att_936139/v4/s71500_cpu1513_1_pn_dtc_manual_en-US_en-US.pdf
  32. https://forumautomation.com/t/what-is-scan-time-in-plc-and-what-are-the-types/9666
  33. https://literature.rockwellautomation.com/idc/groups/literature/documents/sg/1756-sg002_-en-p.pdf
  34. https://automationprimer.com/2016/08/28/plc-memory/
  35. https://www.omch.com/the-power-supply-in-a-small-plc-is-often/
  36. https://www.phoenixcontact.com/en-us/products/power-supply-quint-ps1ac24dc10-2866763
  37. https://www.phoenixcontact.com/en-pc/products/surge-protection/surge-protection-for-power-supplies
  38. https://en.eeworld.com.cn/news/qrs/eic210757.html
  39. https://us.codesys.com/products/runtime/
  40. https://control.com/textbook/programmable-logic-controllers/inputoutput-io-capabilities/
  41. https://www.doigcorp.com/core/media/media.nl?id=894497&c=3971987&h=8008cd1d8cc0e43bd6e2&_xt=.pdf
  42. https://cdn.automationdirect.com/static/specs/p316nd3.pdf
  43. https://www.analog.com/en/resources/analog-dialogue/articles/precision-plc-signal-processing-data-conversion.html
  44. https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1734-um011_-en-p.pdf
  45. https://www.ti.com/lit/wp/slla529/slla529.pdf?ts=1762592522541
  46. https://literature.rockwellautomation.com/idc/groups/literature/documents/sg/1734-sg001_-en-p.pdf
  47. https://www.farnell.com/datasheets/4152000.pdf
  48. https://kdmfab.com/everything-you-should-know-about-din-rail/
  49. https://assets.new.siemens.com/siemens/assets/api/uuid:7a7301d9-fde6-4ff6-9f92-60e8be643986/simatic-s7-1500-redundant-systems.pdf
  50. https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um523_-en-p.pdf
  51. https://new.abb.com/control-systems/service/customer-support/satt/controllers/satt-19-rack
  52. https://industrialautomationco.com/blogs/news/modular-vs-compact-plcs-which-architecture-saves-more-in-maintenance
  53. https://stefanhenneken.net/2025/06/11/iec-61131-3-comparison-of-edition-3-and-edition-4/
  54. https://library.e.abb.com/public/81478a314e1386d1c1257b1a005b0fc0/2101127.pdf
  55. https://www.holobloc.com/stds/iec/sc65bwg7tf3/html/faq.htm
  56. http://users.etown.edu/w/wunderjt/PLC_Fundamentals.pdf
  57. https://www.rockwellautomation.com/en-us/capabilities/industrial-automation-control/design-and-configuration-software.html
  58. https://ww2.jacksonms.gov/uploaded-files/jLILmz/270003/AllenBradleyPlcProgramming.pdf
  59. https://www.siemens.com/global/en/products/automation/industry-software/automation-software/tia-portal/software/step7-tia-portal.html
  60. https://www.se.com/us/en/product-range/2226-ecostruxure-machine-expert-software/
  61. https://support.industry.siemens.com/cs/mdm/109798671?c=133982951179&lc=en-eg
  62. https://docs.tia.siemens.cloud/r/en-us/v20/compiling-and-downloading-plc-programs/basics-for-compiling-and-downloading-plc-programs
  63. https://us.codesys.com/products/engineering/development-system/
  64. https://www.siemens.com/global/en/products/automation/systems/industrial/plc/s7-plcsim-advanced.html
  65. https://www.researchgate.net/publication/303874724_Hardware-In-the-Loop_Simulation_for_Validating_PLC_Programs
  66. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_using_breakpoints.html
  67. https://www.exida.com/articles/IEC-61508-Overview.pdf
  68. https://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm018_-en-p.pdf
  69. https://cache.industry.siemens.com/dl/files/465/36932465/att_106119/v1/s71200_system_manual_en-US_en-US.pdf
  70. https://www.seeedstudio.com/blog/2019/12/06/what-is-rs485-and-its-difference-between-rs232/
  71. https://www.infosecinstitute.com/resources/scada-ics-security/rs-232-and-rs-485/
  72. https://www.profibus.com/download/profibus-standard-dp-specification
  73. https://www.odva.org/wp-content/uploads/2021/05/PUB00026R5_Tech-Series-DeviceNet.pdf
  74. https://www.odva.org/technology-standards/key-technologies/ethernet-ip/
  75. https://ieeexplore.ieee.org/document/10866179
  76. https://www.prosoft-technology.com/content/download/5254/37617
  77. https://www.rteng.com/blog/plc-vs-hmi
  78. https://www.unitronicsplc.com/vision-series-vision1210/
  79. https://maplesystems.com/product/modelname/hmi5070bv3/
  80. https://www.unitronics-cannabis.com/plchmi/
  81. https://www.weintekusa.com/hmi-software-programming/
  82. https://ww2.jacksonms.gov/fulldisplay/4UhMhB/272014/high__performance__hmi_handbook.pdf
  83. https://maplesystems.com/web-hmi/
  84. https://inductiveautomation.com/solutions/hmi
  85. https://opcfoundation.org/wp-content/uploads/2017/08/OPC-Foundation-Process-Automation-Whitepaper-20170823.pdf
  86. https://community.ptc.com/sejnu66972/attachments/sejnu66972/kepware/1001/1/KEPServerEX%2520Manual%2520%282022%29.pdf
  87. https://library.automationdirect.com/plc-scan-fundamentals/
  88. https://theautomization.com/plc-working-principle-and-plc-scan-cycle/
  89. https://zeroinstrument.com/understanding-plc-scan-cycles-in-industrial-automation/
  90. https://www.plctalk.net/textbook/programmable-logic-controllers/the-plc-scan-cycle/
  91. https://literature.rockwellautomation.com/idc/groups/literature/documents/wp/logix-wp003_-en-p.pdf
  92. https://cache.industry.siemens.com/dl/files/558/59193558/att_112303/v1/s71500_cycle_and_reaction_times_function_manual_en-US_en-US.pdf
  93. https://www.plcacademy.com/scan-time-of-the-plc-program/
  94. https://library.automationdirect.com/plc-scan-time-control-system/
  95. https://www.ti.com/lit/pdf/spradg8
  96. https://control.com/forums/threads/fast-plc-need.6583/
  97. https://www.rtautomation.com/technologies/ieee-1588/
  98. https://www.teledynevisionsolutions.com/learn/learning-center/machine-vision/precision-system-synchronization-with-the-ieee-1588-precision-time-protocol-ptp/
  99. https://iebmedia.com/technology/industrial-ethernet/time-synchronization-to-improve-determinism-and-response-time/
  100. https://www.sciencedirect.com/science/article/pii/S2405844024135918
  101. https://www.mdpi.com/2079-9292/12/23/4730
  102. https://automationforum.co/how-to-optimize-plc-scan-time-for-better-automation/
  103. https://www.researchgate.net/publication/220643605_Worst-case_execution-time_analysis_for_embedded_real-time_systems
  104. https://www.absint.com/aiT_WCET.pdf
  105. https://industrialautomationco.com/blogs/news/what-s-the-difference-between-a-safety-plc-and-a-standard-plc
  106. https://www.infoplc.net/files/documentacion/seguridad_normativa/infoplc_net_plc_vs_safetyplc_fundamental_significant_differences.pdf
  107. https://www.intertek.com/electrical/standards/iec-61508/
  108. https://www.sciencedirect.com/topics/engineering/diagnostic-coverage
  109. https://www.blog.beckhoffus.com/post/test-pulses-vs-ossd
  110. https://www.automationreadypanels.com/plc-hmi/mastering-safety-plc-basics-of-safety-logic-systems/
  111. https://www.pilz.com/en-US/products/controllers/plc-controllers
  112. https://www.rockwellautomation.com/en-us/products/hardware/safety-products/safety-controllers.html
  113. https://industrialcyber.co/reports/half-of-2025-ransomware-attacks-hit-critical-sectors-as-manufacturing-healthcare-and-energy-top-global-targets/
  114. https://www.automation.com/article/technology-trends-empower-innovation
  115. https://www.iiconsortium.org/pdf/2021_March_JoI_Digital_Twin_and_IIoT_in_Optimizing_Manufacturing_Process_and_Quality_Management_SA.pdf
  116. https://aws.amazon.com/blogs/iot/industrial-iot-from-condition-based-monitoring-to-predictive-quality-to-digitize-your-factory-with-aws-iot-services/
  117. https://pages.awscloud.com/rs/112-TZM-766/images/Global_PTNR_AWS_IIOT_Ebook_1001201911.pdf
  118. https://aws.amazon.com/blogs/iot/using-aws-iot-for-predictive-maintenance/
  119. https://iaeme.com/MasterAdmin/Journal_uploads/IJPLCS/VOLUME_2_ISSUE_1/IJPLCS_02_01_001.pdf
  120. https://blog.isa.org/digital-twin-in-mes-transforming-manufacturing-execution-systems
  121. https://pmc.ncbi.nlm.nih.gov/articles/PMC8309547/
  122. https://www.symestic.com/en-us/blog/mes/integration/isa95?hs_amp=true
  123. https://mesautomation.com/en/isa-95/
  124. https://www.rockwellautomation.com/en-us/products/software/factorytalk/analytics-visionai.html
  125. https://www.rockwellautomation.com/en-us/support/documentation/overview/factorytalk-analytics-logixai--machine-learning-and-logix.html
  126. https://www.rockwellautomation.com/en-us/products/software/factorytalk/operationsuite/analytics-logixai.html
  127. https://emag.directindustry.com/2024/12/19/with-visionai-rockwell-automation-aims-to-revolutionize-quality-inspection/
  128. https://www.arcweb.com/blog/will-virtual-plcs-succeed-where-soft-plcs-failed
  129. https://iot-analytics.com/virtual-plcs/
  130. https://www.allpcb.com/allelectrohub/5gplc-system-architecture-and-applications
  131. https://www.mdpi.com/2071-1050/16/14/6230
  132. https://www.researchgate.net/publication/382482598_Industrial_Sustainable_Development_The_Development_Trend_of_Programmable_Logic_Controller_Technology
  133. https://ijaem.net/issue_dcp/Plc%20Integration%20for%20Robotic%20Welding.pdf
  134. https://www.mdpi.com/2076-3417/15/16/8990
  135. https://www.rockwellautomation.com/en-us/industries/oil-gas/pipeline-and-transportation-automation.html
  136. https://www.siemens.com/global/en/products/automation/systems/industrial/plc/logo/home-automation.html
  137. https://www.schindler.com/content/dam/website/us/docs/modernization/elevator-plc-brochure.pdf/_jcr_content/renditions/original./elevator-plc-brochure.pdf
  138. https://deepblue.lib.umich.edu/bitstream/handle/2027.42/45886/170_2003_Article_1996.pdf
  139. https://www.c3controls.com/white-paper/microcontrollers-versus-plcs-detailed-comparison
  140. https://processsolutions.com/microcontroller-vs-plc-whats-the-difference/
  141. https://basicplc.com/plc-vs-microcontroller/
  142. https://www.divelbiss.com/PLC.html
  143. https://www.controleng.com/plc-chip-for-embedded-applications-with-ethernet-communications/
  144. https://www.pdfsupply.com/blog/index.php/2021/12/06/raspberry-pi-vs-plc/
  145. https://kwoco-plc.com/raspberry-pi-plc-controller/
  146. https://automatismosmundo.com/en/logo-from-siemens-what-is-it-is-it-really-a-plc/
  147. https://www.automation24.com/siemens-logo-24-ce-6ed1052-1cc08-0ba2
  148. https://www.siemens.com/global/en/products/automation/systems/industrial/plc/logo.html
  149. https://www.eetimes.com/teardown-ruggedness-and-flexibility-keep-plcs-strong-in-industrial/
  150. https://support.industry.siemens.com/cs/document/16818490/mean-time-between-failures-%28mtbf%29-list-for-simatic-products?dti=0&lc=en-WW
  151. https://control.com/technical-articles/turn-a-raspberry-pi-into-a-plc-using-openplc/
  152. https://control.com/technical-articles/the-differences-between-plcs-and-rtus/
  153. https://www.plcdepartment.com/blogs/plcblog/remote-terminal-units-vs-programmable-logic-controllers-a-complete-comparison
  154. https://www.dpstele.com/rtu/plc/index.php
  155. https://teamuis.com/2023/03/29/rtu-vs-plc/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.