PLC Simulator
Free tool

PLC Scan Time Calculator

Enter your program size, I/O count, and CPU class to get a rule-of-thumb scan cycle estimate — with an honest explanation of what actually drives scan time.

PLC Scan Time Estimator

Rule-of-thumb estimate only. Always verify with your controller’s benchmark utility. All calculations are client-side.

CPU class

rungs/instructions
points
points
points
points
ms (HMI, EtherNet/IP, remote I/O)

Estimated scan time range

3.2 ms – 6.0 ms

±30% spread accounts for overhead jitter, OS service tasks, and cache variability. Verify against the actual controller scan-time diagnostic.

How the scan works

The four phases of a PLC scan cycle

Every PLC executes the same repeating loop. Understanding which phase dominates your scan budget is the first step in reducing it.

ReadInputs1–5 µs/pt digital1–5 ms/card analogExecuteProgram0.05–0.5 µs/instrWriteOutputs≈ same as readComms&HousekeepingHMI, EtherNet/IPremote I/OOne complete scan loop — typically 1 ms to 50 ms
PLC architecture whose CPU class and I/O count drive the scan time estimateA modular PLC rack on a backplane: power supply, CPU processor, input module, output module and a communications module side by side.PLC RACKbackplane busPSUPowerCPUProcessorDIInputDOOutputNETComms
CPU class and I/O module count are the two biggest scan-time drivers.
Ladder logic rung whose instruction count the scan time calculator multiplies by per-instruction timeA basic ladder logic rung between two power rails: an examine-if-closed contact (XIC) in series driving an output coil (OTE).L1L2] [StartXIC I:0/0LampOTE O:0/0
Every rung adds instructions — the calculator multiplies by per-instruction execution time.
IEC 61131-3 languages whose instruction mix affects PLC scan timeThe five IEC 61131-3 PLC programming languages as chips: Ladder Diagram, Function Block Diagram, Structured Text, Instruction List and Sequential Function Chart.IEC 61131-3 — five languagesLDLadder DiagramFBDFunction BlockSTStructured TextILInstruction ListSFCSequential Func. Chart
Instruction mix matters — floating-point can run 10x slower than bit instructions.
Digital I/O points added to the scan time read-inputs and write-outputs phasesA digital input pushbutton wired to a PLC input card, and a PLC output card driving a lamp, with a sinking versus sourcing hint.I/O CARDINPUTOUTPUTPushbuttonI:0/0LampO:0/0sinking (NPN) vs sourcing (PNP)
Each digital I/O point adds time to the read-inputs and write-outputs phases.

Background

What is PLC scan time and why does it matter?

Every PLC executes a continuous loop — read all inputs into an image table, run every rung of your ladder program against that snapshot, write the output image table back to physical outputs, then service communications. The total elapsed time for one complete cycle is the scan time. Typical values range from under 1 ms for a small micro PLC to 50 ms or more for a heavily loaded mid-range controller.

Scan time matters for three reasons. First, the PLC cannot respond to an input change faster than one scan — a 20 ms scan misses any event shorter than 20 ms unless you use an interrupt task. Second, PID controllers placed in the main scan execute at a variable rate, which degrades loop performance; most PLC platforms provide periodic interrupt tasks specifically to give PID a consistent sample rate. Third, HMI responsiveness and remote I/O update rates both depend on the comms slice within the scan budget.

What the estimator models

The estimator multiplies your instruction count by a per-instruction execution time (0.05 µs for a high-end controller, 0.5 µs for a micro PLC — conservative rule-of-thumb values). It adds digital I/O time (approximately 1.5 µs per point), analogue I/O overhead (roughly 2.5 ms per 8-channel card, accounting for ADC conversion latency), and your estimated communications overhead. A ±30% spread is applied to reflect jitter from OS servicing, instruction-cache misses, and remote-I/O variability.

What the estimator does not model

CPU-specific pipeline stalls, instruction-mix effects (floating-point vs. bit instructions can differ by 10×), motion-control axis servicing, and any interrupt tasks you run outside the main scan. For accurate scan time on your specific controller, use the manufacturer’s scan-time diagnostic: Allen-Bradley uses the GSV instruction to read the Overhead Time Object; Siemens TIA Portal shows OB1 cycle time in the Watch Table; Omron reads D8012/D8013 system memory.

Where to see scan effects in practice

The free interactive PLC scan cycle visualizer lets you change a physical input between the read, solve, and write phases, while the scan cycle lesson explains how a slow scan affects output timing. The scenario auto-grades whether your outputs respond within the correct scan window. If your estimator result is marginal for your process, that scenario is the fastest way to observe the consequences.

See scan time effects in a live scenario

Numbers in a calculator are one thing. Watching outputs respond — or not — in a graded scenario makes the concept stick.

Open the scan-cycle visualizerRun your first PLC program — no signupBrowse scenarios →
Scan time FAQ

Common questions about PLC scan time.

A PLC scan cycle is the repeating loop the CPU executes: read all inputs, execute the user program, write all outputs, then service communications. The total time for one complete loop is the scan time. Typical values range from 1 ms to 50 ms for most industrial controllers running moderate programs.

Technical reference and worked-example guide

PLC scan-time calculator: field reference

Direct answer

The user can calculate a bounded estimate, state its assumptions and identify when measurement or a faster input, task or hardware function is required.

Written for pLC programmers estimating whether input update, logic execution, output update and task scheduling can observe and respond within a requirement.

System map / 02

NODE 01observable

Definition

Task period, scan components, instruction path, I/O update, communications, variation, event duration, response requirement and units.

NODE 02observable

Signal path

Input event through module update, task scheduling, logic execution, output update and physical response.

NODE 03observable

Worked example

Minimum, nominal and conservative values calculated with units and checked against a measured or specified bound.

NODE 04observable

Limits

Asynchronous I/O, missed pulses, periodic tasks, interrupts, communications, online monitoring, jitter and peak load.

NODE 05observable

Common mistake

An input-update, scheduling, execution, output-update, unit or assumption error.

NODE 06observable

Verification

The estimate compared with controller diagnostics, traces and an observed target acceptance test.

Answer surface / 07

How do you calculate PLC scan time?

Add or measure the relevant input update, scheduled wait, program execution, communication and output update terms for the task being evaluated, then include observed variation rather than relying on one nominal value.

Can a PLC detect a pulse shorter than one scan?

It may miss an ordinary sampled pulse. Use input latching, a high-speed counter, an event task or suitable hardware when the event contract requires it.

Continue the signal path / 08