Using Counters in S7 GRAPH Actions in TIA Portal V17

S7-GRAPH is the Siemens programming language for sequential control on S7-300, S7-400, S7-1200, and S7-1500 CPUs. It separates the control flow (steps and transitions) from the actions executed in each step. Counting parts, tracking cycles, counting process events, and supervising time-quantity relationships are common requirements, and S7-GRAPH supports them natively through counter operations that are bound to events inside an action. This reference covers the supported counter operations, the COUNTER parameter type, IEC counter integration, common compile/runtime errors, and verified configuration paths in TIA Portal V17 (and V18/V19/V20, where the syntax is unchanged).

1. Prerequisites

• TIA Portal V17 Update 4 or later (V18, V19, and V20 share the same GRAPH counter syntax). Refer to the Siemens Industry Online Support entry for the SIMATIC S7-1500/ET 200 release notes.
• S7-GRAPH option package installed and licensed for the engineering station. Without this package the GRAPH FB type does not appear in the project tree.
• An S7-300, S7-400, S7-1200, or S7-1500 CPU whose firmware supports GRAPH actions with counter events. S7-1200 requires firmware V4.0 or higher; S7-1500 requires V1.5 or higher for full event syntax.
• For S7-1500: a CPU 1500 series with the optional GRAPHSYS block available in the program (it is supplied automatically by the GRAPH compiler).

2. Counter Types Available in an S7 System

Two distinct counter families exist in STEP 7 / TIA Portal, and they are not interchangeable in GRAPH:

Legacy COUNTER addresses are tied to the PLC's system counter area and are incremented/decremented by GRAPH counter operations. IEC counters are self-contained function blocks you can call from any language editor (LAD, FBD, SCL, GRAPH). Both can coexist in the same GRAPH FB; the choice depends on whether the rest of the project uses the legacy counter area or the IEC counter concept.

3. Counter Operations Supported in GRAPH Actions

According to the official Siemens TIA Portal V20 documentation — Counter operations (S7-300, S7-400, S7-1500), the following counter operations are valid inside an action:

All four operations require an event in the action qualifier. The event defines when the operation fires. Without an event, the action produces a compile error: "Event missing for counter operation".

3.1 Event qualifiers used with counter operations

4. Declaring the COUNTER Parameter in the GRAPH FB Interface

Before a counter operation can be edited in the action, the GRAPH FB must expose a parameter of type COUNTER. In TIA Portal:

1. Open the GRAPH FB in the project tree.
2. Right-click the FB block title → Properties → Interface.
3. Switch to the Input, Output, or InOut section as required by the sequence.
4. Add a new parameter; set the data type to COUNTER (not IEC_COUNTER, not CTU, not INT).
5. Confirm. The new parameter appears in the action editor's tag selector.

The COUNTER parameter type accepts:

• An absolute counter address in the form C1, C2, ... up to C255 on S7-300/400, and the equivalent IEC counter tags on S7-1500 that have been declared in the PLC tag table as Counter data type.
• A PLC tag defined in the PLC tag table with data type COUNTER or IEC_COUNTER (S7-1500 specific).

5. Configuration Walk-Through: Count-Up in a GRAPH Action

The following procedure reproduces the canonical pattern shown in the Siemens TIA Portal V20 documentation for counter operations and works identically in V17.

5.1 Prerequisites in the project

• A GRAPH FB named FB_Sequence with at least two sequential steps.
• A COUNTER parameter PartCounter declared in the FB interface (see Section 4).
• An input bit PartDetected in the FB interface used as the event trigger.

5.2 Step 1 — Declare the COUNTER parameter

1. Open FB_Sequence.
2. In the FB interface, add a parameter cnt_ProducedParts : COUNTER.
3. Save and compile the FB.

5.3 Step 2 — Add a counter operation in the action

1. Select the step where the count must increment (e.g., Step_3_Running).
2. In the Actions table of the step, choose an empty row.
3. Click the Event cell and select an event — for a one-shot on step entry, select S1. To count on every rising edge of a process signal within the step, use L1 or a custom event expression.
4. Click the Action cell on the same row. The action editor opens.
5. Type the counter operation, e.g.:

   CU  C1

   or, when using the FB parameter:

   CU  cnt_ProducedParts

6. Press Apply. The action editor closes, and the step is marked with a counter symbol.

5.4 Step 3 — Optional: reset on step exit

Add a second action row in the same step or in the next step with event S0 and the CR operation:

CR  cnt_ProducedParts

This forces the counter to 0 the moment the step deactivates.

5.5 Step 4 — Compile and download

1. Right-click the GRAPH FB → Compile > Software (only).
2. Resolve any Data type Counter is not allowed here warnings — they are usually caused by an IEC counter tag being wired to a counter operation; switch the tag to COUNTER or to an absolute C address.
3. Download the program to the CPU. After a STOP → RUN transition, the GRAPH sequencer is ready.

6. Integrating an IEC Counter (CTU/CTD/CTUD) Inside GRAPH

Many modern code bases avoid the legacy COUNTER area and rely entirely on IEC counters. GRAPH supports them, but the integration model is different: IEC counters are called in the action body rather than triggered by a counter operation.

6.1 Single-instance IEC counter

1. Add a tag of type CTU, CTD, or CTUD in the FB interface (e.g., iec_ProducedParts : CTU).
2. Open the action cell, switch the language to SCL if you need full expression access (right-click action body → Change language).
3. Insert a call to the IEC counter:

   iec_ProducedParts(CU := PartDetected, R := ResetCounter, PV := 1000, Q => PartsReached, CV => CurrentCount);

4. Bind the event in the action qualifier (e.g., L1) — the event determines when the call is executed, not when the internal CU edge of the FB is generated.

6.2 Multi-instance IEC counter (recommended)

1. Inside the GRAPH FB, add a static variable Multi_Counter : CTU in the Static section of the FB interface.
2. In the action, call:

   #Multi_Counter(CU := SensorEdge, R := Reset, PV := 500, Q => #Done, CV => #Actual);

Multi-instance IEC counters keep the counter encapsulated inside the GRAPH FB's instance DB, eliminating name conflicts across FB copies.

7. Common Compile and Runtime Errors

8. Counter vs. IEC Counter — Selection Guide

9. Verifying Counter Behavior Online

1. Download the program and switch the CPU to RUN.
2. Open the GRAPH FB in Online > Monitor.
3. Force the supervising step to active by setting the transition condition.
4. Watch the COUNTER value in the Sequence view; for IEC counters, add a watch table on the GRAPH instance DB and observe the CV field.
5. Trigger the count event (a process signal or a forced input). Confirm that the value increments on each event edge.
6. To verify the reset path, deactivate the step (set the transition true) and check that CR brings the value to 0.

10. Migration Notes: S7-300/400 to S7-1500

If a legacy GRAPH FB is migrated from S7-300/400 to S7-1500 in TIA Portal V17, the migration tool will convert COUNTER declarations to IEC counter tags. The counter operations remain valid, but verify the following:

• The number of available system counters on the S7-1500 (default 2048 IEC counters).
• That no HMI tag references the old C address with an offset that no longer matches.
• That programs that assumed BCD behavior (values up to 999) are updated if a wider range is now in use.

11. Field-Proven Tips

• Prefer IEC counters for any new GRAPH FB. The COUNTER parameter type is kept for compatibility with migrated code.
• When using the legacy COUNTER area, allocate a dedicated address range per GRAPH FB to avoid overlap with other FBs.
• Use a comment column in the action table to record the meaning of the counter — GRAPH actions are not searchable by symbol name.
• If the action body needs complex math around the count, switch the action language to SCL and call a CTUD instance directly.
• For safety-related sequencers, route counter events through the interlock and use L1 / L0 events so that the counter reacts to process state changes, not step activation.

12. FAQ