Glossary · Automation fundamentals, platforms and components
Scan cycle
Also known as: PLC scan, Program cycle, Cycle time, Scan time
German: Zykluszeit
In PLC technology, the scan cycle is the repeating sequence in which a controller reads its inputs into the process image, executes the user program, writes the outputs and performs system tasks. The cycle time (German: Zykluszeit) is the duration of one such cycle.
- Automation components
In one sentence
The scan cycle is the PLC's repeating loop of reading inputs, executing the program and writing outputs; cycle time is its duration.
Example
The main task has a cycle time of 8 ms; a new visualization routine raised it to 14 ms and delayed the response to a sensor.
How it applies
- Engineering: Response time from input to output is roughly up to two cycles plus input and output delays. Cyclic tasks run at a fixed interval, free-running cycles as fast as possible.
- Operation: A Watchdog monitors the maximum cycle time; if exceeded, the controller typically goes to STOP or runs an error routine.
- Documentation: State typical and maximum cycle times in the software documentation, and include them in response time calculations for safety functions. Note that the German list term "Zykluszeit" refers to the time, while "scan cycle" names the loop itself.
Scan cycle vs. machine cycle
The scan cycle is a controller's program loop, measured in milliseconds. A machine cycle or Stroke (machine cycle) is one production cycle of the machine, measured in seconds, and spans many scan cycles.
In risk assessment, PL analysis and security analysis
- Risk assessment (CE): The response time of a safety function realized in a PLC includes the input delay, up to two scan cycles (a change can arrive just after the inputs were read), the output delay and, for networked I/O, the watchdog time of the safety protocol. Use the maximum cycle time, not the typical one: it feeds the overall stopping time and thus the minimum distance of guards under ISO 13855.
- PL analysis: The Performance Level under ISO 13849-1 is determined by category, MTTFD, DCavg and CCF, not by the cycle time. The cycle time belongs in the safety requirements specification as the required response time and is checked in validation.
- Security analysis: Added load (extra communication, diagnostic requests, a flood of network traffic) can lengthen the cycle until the watchdog timer trips. Under IEC 62443 this falls under resource availability (FR 7); the design must make sure such a stop leads to the defined safe state, not to an undefined one.
Naming this term in a document never shows conformity; the risk assessment, the validation of the safety functions and the security risk assessment do. EN 50742 is a CENELEC draft as of the review date: it is neither law nor a source of presumption of conformity.