Programmable Logic Controllers (PLCs)

What Are Programmable Logic Controllers (PLCs)?

---

How Do PLCs Control Industrial Automation Systems?

PLCs control automation systems by running in a repeating cycle. In each cycle, the PLC reads input signals from sensors and devices, executes the programmed logic to determine which outputs are needed, and then sends signals to actuators and equipment. This input-read, logic-execute, and output-write cycle, called the scan cycle, occurs at predictable intervals, usually between 1 and 50 milliseconds.

Scan-Based Execution Architecture

PLCs work differently from event-driven computer programs. They run their control program in a continuous loop called the scan cycle. In each scan, the PLC reads all inputs, runs the entire program from start to finish, writes all outputs, handles tasks such as communication and diagnostics, and then starts the next scan right away. This predictable cycle makes sure the program runs at steady intervals, no matter what is happening in the process.

The time it takes a PLC to complete a scan depends on the program's length, the number of inputs and outputs, and the processor's speed. A simple machine program might finish in 2 to 5 milliseconds, while a complex production line could take 20 to 50 milliseconds. Having predictable scan times is important for stable control. Unlike regular computers, where timing can change due to the operating system, PLCs always complete scans within set time frames.

Instead of reading inputs or writing outputs directly during the program, PLCs use input and output image tables, which are virtual copies of the physical input and output states. At the start of each scan, the PLC reads all physical inputs into the input image table. The program then works with these tables. At the end of the scan, the output image table updates the physical outputs. This method keeps input values stable across scans and avoids inconsistent logic results.

Input and Output Processing

Within each scan cycle, the PLC processes different types of inputs and outputs.

PLCs interface with diverse industrial sensors and devices:

Inputs:

• Digital inputs: Discrete on/off signals from limit switches, proximity sensors, pushbuttons, and safety devices connect to digital input modules that convert field voltage levels to logic levels, providing electrical isolation
• Analog inputs: Continuous-variable signals from temperature sensors, pressure transducers, and flow meters are connected to analog input modules that convert current or voltage signals to digital values. The PLC program scales these to engineering units (degrees Celsius, PSI, GPM)
• Specialty inputs: High-speed counters process encoder signals at rates much faster than the normal scan cycle allows, enabling position or speed measurement. For example, thermocouple and RTD input modules include specialized signal conditioning for temperature measurement

PLCs command actuators and equipment through various output types:

Outputs:

• Digital outputs: Relay, transistor, or triac output modules switch field devices on/off based on program logic. Relay outputs handle higher currents and voltages but switch slowly. Solid-state outputs switch quickly but have lower current capacity.
• Analog outputs: Generate current or voltage control signals for variable-frequency drives, proportional valves, or process control loops
• Communication-based outputs: Modern automation often uses network communication (EtherNet/IP, PROFINET, Modbus TCP) rather than physical I/O for commanding distributed equipment like robot controllers or vision systems

---

What Programming Languages Do PLCs Use?

PLCs utilize five standardized programming languages defined by IEC 61131-3. These are Ladder Logic (LD), which resembles electrical relay schematics; Structured Text (ST), similar to Pascal or C; Function Block Diagram (FBD) for process control; Sequential Function Chart (SFC) for sequential control; and Instruction List (IL). Among these, Ladder Logic and Structured Text are the most commonly used in industrial automation.

Ladder Logic (LD)

Ladder Logic remains the most widely used PLC programming language. Programs consist of horizontal "rungs" between vertical "rails," with input contacts on the left and output coils or instructions on the right, visually resembling electrical relay ladder diagrams. The PLC evaluates ladder rungs sequentially from top to bottom, left to right, within each rung.

The language uses several basic elements:

• Normally open contacts: Close when the associated input is TRUE
• Normally closed contacts: Open when the input is TRUE
• Output coils: Energize when power flows through the rung
• Special function blocks: Timers, counters, and math operations

Strengths: Intuitive for electricians and technicians, excellent for discrete (on/off) control logic, easy troubleshooting by visually tracing power flow, and well-suited for safety-critical applications.

Limitations: Becomes difficult to read for complex mathematical operations, data manipulation, or algorithms involving loops and conditional branching.

Structured Text (ST)

Structured Text provides high-level programming for complex control using Pascal/C-like syntax, with familiar constructs such as IF-THEN-ELSE statements, FOR and WHILE loops, CASE statements, and function calls.

ST excels for applications requiring sophisticated processing:

• Motion control calculations and trajectory planning
• Recipe management and data processing
• Statistical process control
• Communication protocol parsing

ST programs organize into reusable functions and function blocks (subroutines with encapsulated logic and data), promoting modular programming and code reuse.

Strengths: Compact representation for complex logic, natural expression of mathematical and algorithmic operations, easier to version control, and accessible to engineers from software backgrounds.

Limitations: Less intuitive for electricians and technicians trained on relay logic, and harder to visualize logic flow compared to ladder diagrams.

Function Block Diagram (FBD)

A Function Block Diagram (FBD) presents control as a series of interconnected blocks that represent functions such as PID controllers, mathematical operations, and logic gates. FBD is especially effective for process control loops, where sensor inputs undergo steps such as signal conditioning, scaling, PID control, and output limiting. This makes FBD popular in industries such as chemical, pharmaceutical, and water treatment sectors.

Sequential Function Chart (SFC)

A Sequential Function Chart (SFC) handles processes that progress through a series of steps. It breaks the process into steps, with conditions that control when to move from one step to the next. Each step has actions that run while it is active. SFC uses graphics to show the process flow, making it easier for operators and maintenance staff to understand. It can also handle multiple steps at once or let the process follow different paths based on conditions.

Strengths: Excellent for batch processes, machine cycles, and sequential operations with well-defined steps.

Limitations: Not well-suited for continuous control or logic without a clear sequential structure.

Multi-Language Programming

Modern PLC projects often combine languages:

• Ladder Logic: Safety interlocks and discrete control
• Structured Text: Complex calculations and data handling
• Function Block Diagrams: Analog control loops
• Sequential Function Charts: Batch sequences

Each language addresses specific control requirements where it provides the clearest, most maintainable solution.

---

How Do PLCs Compare to Industrial PCs for Automation Control?

PLCs offer predictable scan-based operation with guaranteed cycle times, tough hardware built for factory environments, simple programming focused on control logic, and strong support for industrial input and output. In contrast, industrial PCs offer greater computing power for complex tasks, are more flexible for vision processing and data analysis, and integrate more easily with enterprise systems, but they require more advanced programming and ongoing operating system maintenance.

PLC vs Industrial PC: Feature Comparison

Key Differences

Determinism and timing: PLCs run programs with consistent, predictable timing. For instance, if a scan cycle lasts 10 milliseconds, each cycle will be approximately 10 milliseconds, regardless of other processes. This consistency is crucial for accurate motion control, synchronization, and safety. Industrial PCs with general-purpose operating systems lack this predictability, as their timing can fluctuate due to the operating system, background tasks, or interruptions.

Programming complexity: PLC programming focuses solely on control logic, so users do not need to handle operating systems, device drivers, or networking details. In contrast, industrial PCs require an understanding of operating systems, drivers, multithreading, memory management, and error handling. This makes development more time-consuming and requires software engineering skills beyond just control logic.

I/O integration: PLCs connect easily to industrial I/O devices via standard modules. Wiring devices to PLC terminals is simple, and you can replace failed I/O modules without stopping the whole system. Industrial PCs need extra I/O cards or fieldbus communication, which adds cost and complexity.

Computational capability: PLCs have sufficient processing power for control logic, motion control, and data logging, but they are not suited for demanding tasks such as image processing, complex optimization, or machine learning. Industrial PCs, with their multi-core processors and GPUs, can handle vision processing, predictive analytics, and machine learning tasks that PLCs cannot.

Hybrid architectures: Many modern automation systems use PLCs for reliable machine control and safety, while industrial PCs handle tasks like vision inspection, data analysis, and complex optimization. The PLC ensures real-time control, and the PC provides extra computing power. These systems communicate over industrial Ethernet.

---

What Role Do PLCs Play in Coordinating Multi-Robot Systems?

PLCs serve as central controllers in multi-robot systems. They manage production line sequencing by commanding robots to perform operations in a coordinated order, ensuring smooth workflow. In addition, PLCs handle material flow coordination so that parts arrive at robots precisely when needed. They also implement safety logic, monitor safeguarding devices, and coordinate emergency stops across multiple robots, while orchestrating communication between robots, conveyors, vision systems, and other equipment via industrial networks, ensuring all components work together seamlessly.

Production Sequencing and Workflow Coordination

The PLC acts as the system supervisor, tracking production state across multiple robots and work cells. When a part enters the line, the PLC sequences the following operations: the conveyor brings the part to Robot 1, Robot 1 picks it up and places it into the fixture, Robot 2 performs assembly, and Robot 3 transfers it to the next station. The PLC issues commands to each robot at the appropriate time according to the overall production sequence.

The coordination process follows a clear pattern:

• PLCs send start commands and job parameters to robots through digital outputs or industrial network communication
• Robots report completion, errors, and status back to the PLC
• The PLC monitors these signals, ensuring each robot completes its operation before triggering the next sequence step
• The PLC measures and optimizes overall line cycle time by coordinating robot motions, conveyor speeds, and operation sequences

Material Flow and Part Tracking

PLCs manage material movement through multi-robot cells:

• Conveyor coordination: Control conveyors feeding robots and removing completed parts, coordinating speeds and timing with robot cycles. Sensors on conveyors signal part presence, and the PLC triggers robots when parts reach the correct positions
• Part tracking: Maintain part identities and histories as they progress through multi-robot processes. Reading barcodes or RFID tags, the PLC associates data with physical parts, passing information to each robot
• Buffer management: Manage buffer loading and unloading between stations, ensuring robots have parts available when ready and preventing buffer overflow
• Quality routing: Based on inspection results, route parts to appropriate robots or stations (good parts proceed, questionable parts route to rework, defective parts divert to scrap)

Integrated Safety Coordination

PLCs implement coordinated safety across multi-robot systems. Modern PLCs include safety-rated I/O and processing (up to SIL 3 or PLe) to implement safety-critical logic within the same controller that handles standard control. When an emergency stop is activated, the safety PLC immediately stops all robots in the affected zone and any material-handling equipment that could pose a hazard.

Large multi-robot cells are divided into safety zones with separate access control. The PLC monitors safety gate switches, presence detection, and enables devices for each zone, allowing work in one zone while another zone operates. This requires complex interlock logic to prevent zone interactions from creating hazards.

Industrial Network Communication

The PLC often serves as the master on industrial Ethernet networks (EtherNet/IP, PROFINET, EtherCAT), with robots, vision systems, and I/O as devices. The PLC cyclically exchanges data with all network devices, gathering status and sensor data while distributing commands and setpoints.

PLCs often serve as bridges between different communication protocols, translating and routing data between systems that couldn't communicate directly. The PLC collects production data from multiple robots and devices, aggregating counts, cycle times, quality metrics, and alarm histories. This consolidated data flows to MES or SCADA systems through industrial protocols (OPC UA, Modbus TCP), providing enterprise-level visibility.

---

Conclusion

Programmable Logic Controllers remain the primary control platform in industrial automation. They offer predictable timing with scan-based execution, are built to survive tough factory conditions, use standard IEC 61131-3 programming languages, and are proven to be reliable for over 1,000,000 hours between failures. PLCs are especially good at discrete and sequential control, safety-critical tasks, and real-time coordination of production equipment, including systems with multiple robots.

The IEC 61131-3 programming languages each suit different control needs. Ladder Logic is still the most common for discrete control, while Structured Text is used more for complex algorithms. Modern PLC projects often use a mix of languages, choosing the best one for each task. Compared to industrial PCs, PLCs offer better timing and simpler programming for basic control jobs. Industrial PCs, however, offer more computing power for tasks such as vision processing and analytics. Many systems now use both PLCs for real-time control and safety, and industrial PCs for demanding computing tasks.

In multi-robot systems, PLCs orchestrate production sequencing, coordinate material flow, implement integrated safety, and facilitate communication across robots, conveyors, vision systems, and other equipment, serving as the central coordinator ensuring synchronized, safe, and efficient automated operations.

---

Related Topics

Explore more AI insights and industry developments

  Back to Glossary