Counter instructions: CTU, CTD, and CTUD

Counters look simpler than timers and cause more bugs because of one detail: the count input is edge-triggered, not level-triggered. A held input increments a counter exactly once and an engineer who tests with a forced bit instead of a real pulse will never see the bug until commissioning. The IEC 61131-3 standard defines CTU (count up), CTD (count down), and CTUD (up-down).

What this instruction does

The counters family is one of the building blocks every working PLC engineer uses on a weekly basis. This page is the one-page reference: what the instruction is for, how the IEC 61131-3 standard form reads, where each major vendor's IDE diverges from the standard, and the mistakes that typically cost a shift on commissioning. We program these on real hardware ourselves; the worked examples below are the patterns that actually ship, not toy snippets. Read the page front to back the first time, then bookmark it as a quick lookup once the patterns are in muscle memory. The simulator covers each example in the sandbox at the free tier, so you can copy a rung from this page and run it without installing anything.

IEC 61131-3 syntax

The standard form is the place to anchor; once the IEC syntax is clear the vendor variations are easier to read. The block below is the canonical counters declaration as the standard defines it.

CTU_Inst(CU := <bool>, R := <bool>, PV := 100);
CTU_Inst.Q   // BOOL, true when CV >= PV
CTU_Inst.CV  // INT current value
// CTUD also exposes QU, QD, CD, LD, and an INT CV.

A few notes on reading the syntax. The instance name on the left is what the runtime allocates state against — every call to a function block needs its own instance, never reused across rungs. The inputs after the colon-equals are how you bind real signals or constants to the block's parameters at call time. The dotted accessors after the call are how you read the output state on the next scan; the runtime only refreshes them at the call site, so referencing a dotted output from a rung that runs before the call gives you stale data.

Vendor implementations

Every major vendor implements the IEC standard form, but each adds its own conventions on top — IDE menu paths, datatype names, retentive variants. The mappings below are the ones that bite on a real commissioning visit. If your vendor is not listed here, the IEC form above is still the safe starting point; check the vendor docs for the brand-specific diff before you ship.

Siemens

TIA Portal: Instructions > Basic instructions > Counter operations. CTU, CTD, CTUD with their own instance DB. CV defaults to INT but can be set to DINT in the block properties.

TIA Portal generates a one-shot internally for the CU input on S7-1200 and S7-1500 CPUs. On older S7-300 firmware you must wire your own positive-edge instruction (P_TRIG) before CU.

Allen-Bradley

Studio 5000: CTU, CTD, and CTUD instructions. .PRE is preset, .ACC is the accumulator, .DN is the done bit, .OV and .UN are overflow and underflow.

Allen-Bradley counters do not have a built-in one-shot; you must precede the count input with a ONS (one-shot) instruction or the counter increments every scan the input is true.

Worked examples

The examples below are patterns we ship. Each one names the production context, the rung shape, and the parameter values that work in practice. Copy them into the simulator's sandbox to see the timing behaviour live before you put them on hardware.

Pack-out batch counter

Photoeye pulses once per bottle; CTU with PV=24 closes a contact when the case is full and a separate output triggers the case sealer.

// Pseudo-ladder
// BottleSensor ─[ONS]─[CTU PV=24]─
// Counter.Q ─] [─( CaseFull )

Bidirectional position counter

CTUD on a quadrature encoder's A-leading-B and B-leading-A pulses gives net position. Reset on home-switch or cycle-start to clear drift accumulated from missed pulses.

Common mistakes

The mistakes below cost real time on real projects. The first three appear on every commissioning visit; the rest are the second-tier traps that surface only under load or after a cold start. Run a paired-review pass against the list before you commit any rung that uses this instruction.

• Wiring a level-true bit to CU without a one-shot — counter increments every scan and the count is essentially scan-time divided by 1.
• Using a 16-bit INT for CV on a high-frequency counter that wraps at 32767 — set CV to DINT or reset more often.
• Resetting a counter with the same condition that increments it — the order of evaluation depends on the vendor and races silently.
• Forgetting that CTUD does not auto-reset CV when both CU and CD are true on the same scan — vendor behaviour varies.

A pattern across all of these: the instruction itself is rarely the bug — the bug is in how the surrounding rung reads or writes the instruction's state. Check the rung shape first. The simulator's live trace pane shows .Q and .ET (or the instruction's equivalent state fields) on every scan, which is the fastest way to see whether the instruction is doing what you think it is.

How to practise this in the simulator

The simulator has a sandbox that lets you write a one-rung program using this instruction in under sixty seconds. Free tier covers it — open the simulator, drop the instruction onto a rung, wire two test inputs, and watch the .Q and .ET fields update in the live trace pane. The patterns above are exactly the patterns the curriculum builds on; this page is the one-page reference, the curriculum is the deliberate-practice version. Working through the curriculum's matching module gives you ten to fifteen variations on the same instruction shape, with feedback on each, and a portfolio piece at the end. The free tier is enough to verify the instruction works as documented; the Basic tier (USD 12 per month) unlocks the curriculum modules.

Vendor reference

IEC 61131-3 standard is the canonical reference for the IEC 61131-3 standard form. For brand-specific quirks, Siemens Industry Online Support and Rockwell Automation Support are the canonical sources. When the standard and the vendor docs disagree, the vendor docs win for that vendor's hardware — the IEC form is the portable shape, the vendor form is what the firmware actually executes. For platform-pick decisions and longer brand context, see the Siemens and Allen-Bradley brand hubs.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The instruction reference on this page is a one-page summary of the IEC 61131-3 standard form plus vendor-specific quirks; vendor docs remain the canonical source for any production project.

Where this fits in a working week

A technician who has the counters family in muscle memory typically spends less than two minutes per rung writing one. The ones that take longer are the ones where the surrounding state machine has not been thought through; the instruction is fine, the design around it is what eats the day. The simulator's value is letting you exercise the design without paying for hardware time — write the rung, run it, watch the trace, fix the design, repeat. Twenty minutes in the sandbox saves a half-day of commissioning rework. The curriculum's matching module on the counters family takes about three to four hours of focused practice end to end and gives you the muscle memory plus the portfolio piece you can hand a hiring engineer. Petrochem, mining, FMCG, automotive, and water-utility sectors all use this family on a weekly basis; the patterns on this page are the same patterns the OEM engineering houses ship.

Load-shedding has changed the rung shapes that ship in SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — sit on top of the counters family; understanding the instruction in isolation is step one, understanding how it behaves on a cold start after a 2.5-hour cut is step two. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware. For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.