Why a PCS 7 SFC Timer Does Not Count When Its Trigger Is Set True

An SFC timer needs both a configured duration and a valid input pulse. Siemens' SFC interface documents _TIME0 as the timer duration in seconds and _I0 as the input pulse; the timer's mode also determines how it behaves. Setting _I0 to TRUE by itself does not establish that the timer received the intended trigger or that its duration is correct. Check the timer's runtime values and the transition logic that drives its trigger.

What the SFC timer inputs mean

For the SFC timer characteristic, Siemens documents name_TIME0 as a REAL time in seconds, name_I0 as a BOOL input pulse, name_MODE as the operating mode, name_RESET as reset, name_Q0 as output pulse, name_PTIME as remaining time, and name_QERR as error. The documented modes are Pulse, ExtP, OnDel, RetOn-D and Off-D. The source discussion does not identify which mode the sequence uses.

Check the configured duration

Confirm the timer characteristic has an intended, nonzero _TIME0 value in seconds. The Siemens manual lists a default of 1.0 s in the cited edition, but the project may configure a different value and the source gives no requested duration. Do not assume a default is appropriate for the process.

Check whether the trigger actually pulses

_I0 is documented as an input pulse. Inspect the generated timer interface or SFC instance online while the sequence runs and verify that the signal driving _I0 changes as intended when the relevant step or event occurs. If it is held TRUE continuously, or the transition never produces the expected event, the source discussion does not establish that the timer received a valid start pulse. Correct the transition/action logic using the behavior documented for the project's exact PCS 7 version.

Check mode, reset and outputs

Confirm _MODE matches the required timer behavior and inspect _RESET, _Q0, _PTIME and _QERR during the test. A reset signal can affect timer state; the expected output is dependent on selected mode and duration. The older Siemens manual defines these interface signals but does not document the ticket's actual configured mode or program behavior.

A focused online diagnostic procedure

Identify the timer name and selected operating mode in the SFC type.
Confirm the instance's _TIME0 value and units (seconds).
Monitor the source signal and the timer's _I0 input during a controlled, approved test; confirm the intended pulse reaches the timer.
Observe _RESET, _PTIME, _Q0 and _QERR together rather than judging by the trigger assignment alone.
Compare the observations with the timer mode and the manual matching the installed PCS 7/SFC version. Preserve the trace or observations if the behavior remains unclear.

Expected observations and verification

For a functioning timed sequence, the trigger must reach the timer input and the timer's status/output must behave consistently with its selected mode and configured time. Use _PTIME and _Q0 as documented interface signals to determine whether the timer is counting and whether it has produced its output pulse. The available ticket does not report measured online values or identify what transition action should be used.

Version applicability

No PCS 7 or SFC version is stated in the source. The cited Siemens SFC for SIMATIC S7 manual is an older official edition. Its interface table supports the meanings of the timer fields but does not prove that every screen, generated interface detail or mode behavior is identical in an unspecified installed release. Consult the matching release manual before changing or downloading the sequence.

Verification

In an approved non-production test or otherwise under site procedure, observe the timer instance's _TIME0, _I0, _RESET, _MODE, _PTIME, _Q0 and _QERR during one intended trigger. The practical diagnosis is confirmed only when the runtime values show the trigger is reaching the timer and timing/output behavior matches the selected mode. An assignment showing TRUE in an editor alone does not verify runtime timing.

Limitations and Operational Precautions

The source contains a user question and two replies but no version, timer name/configuration, timing requirement, online trace or confirmed final outcome. Siemens documentation identifies the timer interface signals; it cannot determine whether this particular project is misconfigured. Changes to sequence logic can affect plant operation: use site change control, a suitable test opportunity and the project's normal review/download safeguards.

Engineer FAQ

What is _TIME0? Siemens defines it as the SFC timer duration in seconds; the default shown in the cited manual is 1.0 s.

What is _I0? It is the timer's Boolean input pulse in the documented SFC timer interface.

Does _I0 = TRUE prove that timing has started? No. Verify the runtime signal reaches the timer as the intended pulse and inspect _PTIME, _Q0, _RESET and _QERR.

Which timer mode should I use? The interface lists Pulse, ExtP, OnDel, RetOn-D and Off-D. Choose based on required behavior and confirm details in the installed release's manual; the ticket does not specify a requirement.

What should I do if the timer still does not count? Capture the timer mode and online values for _TIME0, _I0, _RESET, _PTIME, _Q0 and _QERR, then compare them with the version-matched Siemens documentation.

Technical References

Siemens, SFC for SIMATIC S7, §6.6.4.7, “Timers” characteristic, printed pp. 91–92, document A5E00807946-01. This older edition defines the timer characteristic I/Os and operating modes; verify details against the deployed PCS 7 version: https://cache.industry.siemens.com/dl/files/748/24451748/att_96723/v1/s7sfcs7b_e.pdf
Siemens, SFC for SIMATIC S7 (V9.0 SP1), §13.2.6.8, “Timers” characteristic, manual listing: https://support.industry.siemens.com/cs/attachments/109755020/s7sfcs7b_en-US.pdf (direct document access returned HTTP 403 during research; the opened older edition is the supporting readable reference).

Why a PCS 7 SFC Timer Does Not Count When Its Trigger Is Set True