Understanding the PLC Scan Cycle and Program Execution
The PLC scan cycle is a fundamental operating principle of a Programmable Logic Controller (PLC) in industrial automation. It determines how the PLC reads input signals, executes control instructions, and updates output devices during normal operation. Understanding this process is essential for designing reliable industrial automation systems and evaluating the performance of PLC-based applications.
During a conventional PLC scan cycle, the controller performs three principal operations: input reading, control program execution, and output updating. The time required to complete these operations is known as the PLC scan time. However, the actual PLC response time also depends on input sampling, hardware delays, and task scheduling. These factors influence the behavior and responsiveness of an industrial control system.
This article explains how a PLC executes a control program, how scan time affects execution performance, and why input-to-output response delays matter. It also presents a practical motor start/stop example and compares cyclic, periodic, and interrupt-driven PLC tasks used in modern industrial controllers.
 |
| PLC scan cycle showing input signals, control program execution, and output updates for industrial automation devices. |
1. What Is a PLC Scan Cycle?
A PLC scan cycle is the repetitive process through which a Programmable Logic Controller (PLC) monitors input signals, executes its control program, and updates output signals to control industrial equipment and processes. During normal cyclic operation, the PLC continuously repeats this sequence, allowing the control system to respond to changing input conditions and perform the programmed control functions.
In industrial applications, PLCs interact with field devices such as pushbuttons, limit switches, proximity sensors, pressure, temperature, level sensors, and other instruments. Their control programs use these signals to operate equipment such as contactors, solenoid valves, indicator lamps, and motor starters. For example, a PLC can start a motor when the required operating conditions are satisfied and stop it when a stop command or protective condition is detected.
Each complete scan requires a certain amount of time, known as the PLC scan time, which is typically measured in milliseconds (ms). The scan time depends on several factors, including the PLC processor, program size and complexity, communication activities, and system configuration. Although PLCs execute their programs repeatedly, the time required for a physical input change to affect an output is not necessarily equal to one scan cycle.
The PLC scan cycle is fundamental to industrial automation because it provides a systematic method for executing control instructions and responding to process conditions. Understanding this operating principle helps engineers and technicians develop reliable control programs, troubleshoot unexpected equipment behavior, and evaluate the response performance of PLC-based control systems.
2. How Does a PLC Execute a Scan Cycle?
In a conventional cyclic PLC system, the PLC Central Processing Unit (CPU) executes the control program through a repeated sequence of operations. The three principal stages are reading inputs, executing the control program, and updating outputs. Additional system activities, such as communication and diagnostics, may also be performed depending on the PLC architecture.
The following explanation describes the conventional cyclic scan, which provides the foundation for understanding PLC program execution. Other execution methods, including periodic and interrupt-driven tasks, are discussed later in this article.
1. Input Reading
At the beginning of a conventional scan cycle, the PLC reads the states of its connected input devices, such as pushbuttons, limit switches, and proximity sensors. These states are transferred into an internal memory area commonly called the input image table or process input image.
For example, when a normally open START pushbutton is pressed, its associated digital input may change from logic 0 (OFF) to logic 1 (ON). The PLC stores this state in the input image, making it available to the control program during execution.
In systems using a conventional input image, changes occurring at physical inputs after the input-reading stage are generally not reflected in that image until the next scheduled input update. However, some PLCs support immediate input instructions or asynchronous I/O updates.
2. Control Program Execution
After acquiring the input states, the PLC CPU executes the user control program according to its defined execution order. In a conventional cyclic ladder logic program, instructions are generally evaluated sequentially according to the program structure and the PLC manufacturer's execution rules.
During execution, the CPU evaluates logical conditions, performs calculations, processes timers and counters, and determines the required output states. It uses the available input values, internal memory bits, and other program variables to make control decisions.
For example, if a START pushbutton is active and the required permissive conditions are satisfied, the control logic may issue a command to energize a motor contactor. The resulting output state is normally stored in an internal output image table until the physical outputs are updated.
It is important to understand that internal variables and output commands can change during program execution, even when physical outputs have not yet been updated.
3. Output Updating
Once the control program has completed its execution, a conventional PLC transfers the calculated output states from the output image to the corresponding physical output modules.
These modules then control connected field devices, such as contactor coils, solenoid valves, and indicator lamps. For example, when the program commands a motor to start, the appropriate PLC output can energize a suitably rated contactor coil, allowing the contactor to switch the motor power circuit.
The physical response of the connected equipment may require additional time due to output-module switching delays, contactor operating time, and the characteristics of the controlled device. Therefore, updating a PLC output does not necessarily mean that the connected equipment responds instantaneously.
4. System Housekeeping and Diagnostics
In addition to the three principal stages, PLCs perform internal system activities that support reliable operation. Depending on the manufacturer and PLC architecture, these activities may include communication processing, diagnostic checks, memory management, and operating-system functions.
These operations are not necessarily performed as a separate stage at the end of every scan. Some PLC systems execute them between program cycles, while others distribute them across different tasks or operating-system processes.
 |
| PLC scan cycle showing input reading, program execution, output updating, and diagnostics. |
After completing the required operations, the PLC continues with the next execution cycle. This repeated process allows the controller to monitor changing conditions and update control decisions continuously. The exact sequence and timing depend on the PLC model, I/O configuration, and task scheduling method.
3. PLC Scan Time and Execution Performance
The duration of a PLC scan affects how frequently the controller can process changing conditions. Understanding how scan time is calculated, what influences it, and how it is monitored helps engineers evaluate PLC execution performance.
1. PLC Scan Time Calculation
For a conventional cyclic PLC, scan time can be estimated using the following simplified equation:
Scan Time = Input Update + Program Execution + Output Update + System Overhead
For example, if input updating requires 1 ms, program execution 4 ms, output updating 1 ms, and system overhead 2 ms:
Scan Time = 1 + 4 + 1 + 2 = 8 ms
At a constant scan time of 8 ms, the PLC completes approximately 125 scans per second. The actual calculation depends on the PLC architecture, as some system activities occur asynchronously or in separate tasks.
2. Factors Affecting PLC Scan Time
Several factors influence PLC scan time:
- CPU performance: Processor speed and instruction execution capability.
- Program complexity: Number of instructions, calculations, loops, and function blocks.
- I/O configuration: Number of modules and their update methods.
- Communication: Network processing and data exchanges.
- Task scheduling: Higher-priority tasks and interrupts that delay cyclic execution.
3. PLC Scan Time Monitoring
Many PLC programming environments provide diagnostic values for current, minimum, and maximum scan times. These measurements help identify execution variations and excessive processing delays. For time-sensitive applications, the maximum observed scan time is often more important than the average because it indicates the longest measured execution cycle. Engineers should also allow for operating conditions not yet captured by monitoring.
4. PLC Watchdog Timer
A PLC watchdog timer supervises program execution to detect excessive execution time. If a monitored task exceeds its configured time limit, the controller may generate a fault, stop execution, or initiate a protective response. Watchdog monitoring helps identify execution problems, but its behavior depends on the PLC manufacturer and configuration.
 |
| PLC scan time example showing an 8 ms cycle, 125 scans per second, and key performance factors. |
4. PLC Response Time and Control Performance
A PLC may execute its control program in milliseconds, but this does not mean that connected equipment responds within the same time. Understanding PLC response time helps engineers evaluate whether a control system can react quickly enough to changing process conditions.
1. PLC Scan Time vs. Response Time
Although closely related, scan time and response time measure different aspects of PLC performance.
2. Input-to-Output Response Delay
In a conventional cyclic PLC, an input change detected before the input-reading stage may affect the output during the current scan. However, a change occurring immediately after input reading generally waits until the next scan before being processed.
Consequently, the delay depends on when the signal changes relative to the scan cycle. In a simplified system with one input and output update per scan, response time may approach two scan periods in an unfavorable case, before considering additional hardware delays.
Actual response time also depends on input filtering, output-module switching, communication delays, and the operating time of connected devices such as contactors.
3. Missed Input Signals
A short input pulse may begin and end between two input updates, preventing a conventional cyclic program from detecting it. This is particularly important in high-speed counting, position detection, and fast-moving production equipment.
Depending on the application and PLC capabilities, engineers can use high-speed counters, hardware input latching, or interrupt-driven processing to capture short-duration signals reliably.
4. Impact on Control Performance
PLC response time should be evaluated against the requirements of the controlled process. A delay of several milliseconds may be acceptable for ordinary motor start/stop commands but unsuitable for certain high-speed positioning or event-detection applications.
Engineers should consider the maximum expected response time, including I/O and communication delays, rather than relying only on the average PLC scan time. Safety-related functions must also meet the requirements of the applicable safety system and should not depend solely on ordinary PLC scan-time calculations.
 |
| PLC response time showing scan delays, missed input signals, and control performance. |
5. Practical Example: PLC Motor Start/Stop Control
A common application of the PLC scan cycle is controlling an electric motor using START and STOP pushbuttons. The PLC reads the pushbutton signals, executes the control logic, and energizes or de-energizes a contactor coil through its output module.
1. Motor Control Components
The example uses a normally open START pushbutton, a normally closed STOP pushbutton, a PLC, and a motor contactor. A motor overload protection device provides an additional protective input to the control logic.
2. Motor Start/Stop Sequence
- Input reading: The PLC reads the START, STOP, and overload protection signals.
- Program execution: When START is pressed, STOP is healthy, and no overload trip is present, the program activates a motor run command. A seal-in (latching) condition maintains the command after START is released.
- Output updating: The PLC energizes the contactor coil through a suitable output interface, closing the contactor's main contacts and supplying power to the motor.
- Stopping: Pressing STOP or detecting an overload trip removes the run command, de-energizing the contactor and stopping the motor.
3. PLC Scan Cycle in Motor Control
The PLC repeats this sequence during cyclic operation, monitoring the input conditions and updating the motor command. A change occurring just after input sampling may not be processed until the following scan, as explained in the previous section. The motor's actual starting and stopping times also depend on the contactor and mechanical system.
Important: Motor overload protection and emergency-stop functions must be implemented using appropriate protective and safety-rated equipment. Ordinary PLC program logic alone should not be relied upon as the sole means of personnel protection.
 |
| PLC motor control showing seal-in ladder logic and the scan cycle operating sequence. |
6. Cyclic Scans, Periodic Tasks, and Interrupts
Although conventional PLCs repeatedly execute their control programs through a scan cycle, modern PLCs may support different task execution methods. These methods determine when a program runs and how the controller responds to scheduled operations or specific events.
1. Cyclic Tasks
A cyclic task executes repeatedly as part of the controller's normal operation. Its execution interval may vary depending on program complexity, system loading, and higher-priority tasks. Cyclic execution is commonly used for general machine and process control.
2. Periodic Tasks
A periodic task is scheduled to execute at a configured time interval, such as every 10 ms. This provides more predictable execution timing for applications requiring regular updates, including certain control calculations and monitoring functions. However, the controller must have sufficient processing capacity to meet the scheduled interval.
3. Interrupt-Driven Tasks
An interrupt-driven task executes in response to a defined event, such as a hardware interrupt or supported input event. Depending on task priorities, it may interrupt lower-priority execution. This method can reduce event-handling delays, although the actual response depends on the PLC architecture and configuration.
The availability, scheduling rules, and priority levels of these execution methods vary between PLC manufacturers. Engineers should select the appropriate method according to the application's timing requirements and the controller's capabilities.
 |
| Comparison of cyclic, periodic, and interrupt-driven PLC execution methods. |
Related Articles
Summary
The PLC scan cycle is a fundamental operating principle of programmable logic controllers. During conventional cyclic operation, the PLC reads input signals, executes the control program, and updates output signals to control industrial equipment. Additional system activities, such as communication and diagnostics, may also influence execution.
Understanding PLC scan time and response time is essential for evaluating control performance. Scan time describes the duration of an execution cycle, while response time represents the delay between a physical input change and the corresponding output change. These delays depend on program execution, I/O processing, task scheduling, and hardware characteristics.
Modern PLCs may also support cyclic, periodic, and interrupt-driven tasks to meet different application requirements. Selecting the appropriate execution method and monitoring system performance help engineers develop reliable, efficient, and responsive industrial control systems.
Frequently Asked Questions (FAQs)
Q1: What is a PLC scan cycle?
A1: A PLC scan cycle is the repeated process in which a programmable logic controller reads input signals, executes its control program, and updates output signals. This sequence allows the PLC to monitor and control industrial equipment continuously.
Q2: What is the difference between PLC scan time and response time?
A2: PLC scan time is the duration of one execution cycle, while PLC response time is the delay between a physical input change and the corresponding physical output change. Response time also depends on input sampling, I/O hardware delays, and task execution.
Q3: Can a PLC miss an input signal during a scan cycle?
A3: Yes. In a conventional cyclic PLC, a short input pulse may occur entirely between input updates and remain undetected. High-speed counters, input latching, or suitable interrupt-driven functions can help capture such signals.
Q4: What is the difference between cyclic, periodic, and interrupt-driven PLC tasks?
A4: Cyclic tasks execute repeatedly during normal controller operation. Periodic tasks are scheduled at configured time intervals, while interrupt-driven tasks execute in response to specific events. Their availability and timing behavior depend on the PLC manufacturer and configuration.