Timing Relay vs PLC Timer: When to Use Each

20 Sep, 2026
Posted by: Muhammet KUL

What is the difference between a timing relay and a PLC timer? A timing relay is a self-contained hardwired device that switches its output a fixed, dial-set interval after a trigger, to IEC 61812; a PLC timer is a software instruction (TON, TOF, RTO) running inside the processor's scan cycle. The relay keeps timing even if the PLC loses power, faults, or is mid firmware-update, because it does not depend on the controller staying alive. This article compares timing accuracy, fail-safe behavior, panel space and wiring cost, diagnostics, and flexibility, and sets out which jobs call for a relay, which call for logic, and where panel builders run both together.

What Is a Timing Relay vs a PLC Timer?

A timing relay is a module: supply terminals, a trigger input, one or two change-over output contacts, and a dial or DIP switch for the delay. Nothing else is required. No processor, no program, no I/O card. Set the dial, wire the trigger, done. A PLC timer is different in kind, not just packaging: it is an instruction inside a ladder or structured-text program, consuming a memory address and a rung of logic, and its output only changes when the scan reaches that rung and evaluates it true. For background on the internal construction, see our how a timing relay works guide.

PLC (Programmable Logic Controller) is a digital control computer that executes a stored program, cyclically reading inputs, executing logic, and writing outputs, per IEC 61131.

Scan cycle is the time a PLC takes to complete one input-read, program-execute, output-write loop; typical scan times run from under 1 ms to tens of milliseconds depending on program size and I/O count.

Both devices produce the same visible result, a delayed contact change, but the mechanism underneath is not interchangeable when the application involves safety, standalone operation, or a controller that might not be running yet.

Timing Accuracy: Oscillator vs Scan Cycle

A timing relay's delay is generated by a dedicated electronic oscillator or counter circuit, independent of anything else in the panel. Repeat accuracy, how close the actual delay comes to the set value on every cycle, typically runs ±0.5% to ±1% of the set time on a good electronic timer.

Formula: Timing Relay Repeat Accuracy — Source: IEC 61812, timing performance clause

T_error = ± (A% × T_set)

Symbol	Description	Unit
T_error	Maximum deviation from the set delay on repeat operation	s
A	Repeat accuracy rating of the timer (typically ±0.5% to ±1%)	%
T_set	Delay value set on the dial or rotary switch	s

A PLC timer's resolution is bound to the scan cycle instead of a dedicated oscillator: the instruction can only update as often as the program scans, so a 10 ms scan puts roughly ±10 ms of jitter on top of whatever timebase the instruction uses internally. For a 30-second star-delta transition that jitter is irrelevant. For a 50 ms interlock gap, it is not.

Key takeaway: Sub-second, safety-relevant delays are better served by a dedicated timing relay; multi-second and multi-minute delays tolerate PLC scan jitter without practical consequence.

Fail-Safe Independence: Why Some Circuits Still Hardwire a Timer

A timing relay has no firmware to hang, no program to corrupt, and no communication bus to drop. Power it, trigger it, it times. A PLC timer inherits every failure mode of the controller it lives in: a watchdog fault, a battery-backed memory loss, an in-progress program download, a network interruption on a distributed I/O rack. If the safety or interlock function has to work even while the PLC is being reprogrammed or has faulted, it cannot live only in PLC logic.

What we see in the field: star-delta starters, off-delay motor cooling fans, and door-interlock delays are often still hardwired with a timing relay even in fully PLC-controlled panels, specifically so the motor protection and mechanical sequencing survive a PLC fault. See our star-delta timing relay motor starting guide for how that specific circuit is built.

Key takeaway: Keep the timing function hardwired wherever the delay protects equipment or people and must survive a PLC fault, firmware update, or program change.

Panel Space, Cost and Wiring

For one or two delay functions, a 17.5 mm or 22.5 mm DIN-rail timing relay costs less installed than adding I/O points, writing and testing a rung of logic, and documenting it in the program. No programming software, no download, no version control. The trade-off shows up at scale: a panel needing fifteen independent delays eats fifteen relays' worth of DIN rail and fifteen sets of terminals, against zero extra hardware for fifteen PLC timer instructions once the I/O already exists.

Multifunction, multi-range relays such as Schneider Zelio Time RE22 or ABB CT-MFD narrow that gap, since one part covers several functions and time ranges via rotary selection, cutting the number of distinct spare parts a panel builder has to stock. See our multifunction timing relays article for the selection detail, and browse stocked options in timing and control relays.

Key takeaway: A handful of independent delays favor discrete timing relays on cost and simplicity; a large count of delays inside an existing PLC favors software timers on marginal hardware cost.

Flexibility, Diagnostics and Programming Changes

Changing a timing relay's delay means opening the panel and turning a dial, or in some ranges flipping a DIP switch and then a dial. Changing a PLC timer's preset means editing a program value, often remotely, sometimes from an HMI without opening the enclosure at all. That difference dominates in machines that need operator-adjustable delays across recipes or product changeovers.

Diagnostics differ just as much. A PLC timer's current value, done bit, and enable bit are all visible on the programming software or HMI while the machine runs; a timing relay usually shows only an LED for power and, on some models, one for output state, no live count-down value. This depends on the specific relay model. Higher-end electronic timers now expose the current stage on a small display, narrowing that gap.

Key takeaway: If the delay needs to change per recipe, per operator, or per shift without opening the panel, put it in the PLC; if it is set once at commissioning and rarely touched, a relay dial is fine.

Head-to-Head Comparison

Criteria	Timing Relay	PLC Timer
Depends on controller running	No	Yes
Typical accuracy	±0.5% to ±1% of set value	Bound to scan cycle (jitter)
Change the delay	Open panel, turn dial/DIP	Edit program or HMI value
Incremental hardware cost per delay	One relay + socket per function	Near zero once I/O exists
Diagnostics while running	LED only on most models	Live value on HMI/software
Survives PLC fault or firmware update	Yes	No

Neither column wins outright. The table is a starting point for the selection call, not a verdict, and it is exactly why we wrote a dedicated how to select a timing relay guide for the cases that do call for a relay.

Typical Applications for Each

Timing relays remain the default for star-delta motor starting transition timing, off-delay cooling-fan run-on after a compressor or oven shuts down, door or guard interlock delays on machinery, and any delay function required to work in a standalone panel with no PLC at all, such as a simple pump-alternation controller. Each of these either needs to survive a controller fault or does not have a controller to depend on.

PLC timers dominate where a delay is one of many interlocked steps in a sequence already running in the controller: conveyor start staggering across a line, batch-process dwell times, alarm delay-to-confirm before shutting down a process, and any function an operator needs to retune without a panel key. Some panel builders still spec a hardwired timer for the fan run-on even inside a fully PLC-driven machine, purely so HVAC cooling continues if the PLC is offline for a firmware push; that habit costs one relay and buys real independence.

Key takeaway: Default to a relay for standalone or safety-adjacent delays, and to the PLC for delays that are one step among many in an already-programmed sequence.

Frequently Asked Questions

Is a PLC timer as accurate as a timing relay?

For delays of several seconds or longer, the difference is not practical. For delays under roughly 100 ms, scan-cycle jitter on the PLC timer becomes significant relative to the delay itself, while a dedicated timing relay's oscillator-based accuracy stays consistent regardless of the delay length.

Can a timing relay replace every PLC timer in a panel?

Not economically. One relay per function adds DIN-rail space and wiring for every delay, so a panel with many independent timed steps is normally cheaper and easier to maintain with PLC timers once the controller and I/O are already there.

Why do panel builders still hardwire timing relays in PLC-controlled machines?

To keep specific functions, most commonly star-delta transitions and cooling-fan run-on, working even if the PLC faults, loses power to its CPU, or is mid firmware-update. The relay has no dependency on the controller staying alive.

Do timing relays need a program or configuration software?

No. Delay is set with a dial or DIP switch and rotary range selector on the device itself; no programming software, download, or version management is involved.

Which is better for a safety-related delay?

A hardwired timing relay, generally, because the delay function then does not depend on PLC program integrity, scan health, or communication to a remote I/O rack. Safety-rated timing relays and safety PLCs both exist; the choice depends on the full safety function, not the delay alone.

Can I mix both in the same panel?

Yes, and it is common. Safety-adjacent or standalone delays go on hardwired relays; recipe-driven or sequence-internal delays go into PLC logic. Most multi-function panels use both side by side.

Conclusion

A timing relay and a PLC timer solve the same visible problem, delaying a contact change by a set time, with different dependencies underneath. The relay's oscillator and dial make it independent, precise at short intervals, and unaffected by controller faults, at the cost of one device per function and a screwdriver to change the setting. The PLC timer's cost per additional delay is near zero once the I/O exists, and its value is remotely adjustable and visible on an HMI, at the cost of depending on the controller staying alive and scanning. Match the dependency profile to the job: standalone or safety-adjacent delays to the relay, sequence-internal and recipe-driven delays to the PLC. For the stocked models that cover the hardwired side, see our timing relay engineering guide.