Resolving Siemens HMI Tag Update Cycle Limits Below 10 ms

Resolving Siemens HMI Tag Update Cycle Limits Below 10 ms

Siemens Comfort Panels and WinCC Runtime enforce a 100 ms minimum tag acquisition cycle by design. Achieving a true 10 ms poll on a standard HMI tag is not supported on the Comfort or Unified Comfort platforms, and the apparent "100 ms" published in TIA Portal is itself a theoretical value degraded by network jitter, panel CPU scheduling, and S7 communication stack latency. This reference documents the architectural limits, the closest available workarounds (trend and archive logging, script-driven polling, OPC UA Pub/Sub), and a commissioning procedure to measure and verify the actual update time you will see in the field.

1. Overview: The 10 ms HMI Tag Update Constraint

The original requirement was for a Siemens HMI in which "tag update time is less than or equal to 10 ms," and the applicant observed that the Comfort Panel default is 100 ms. The community consensus, confirmed by Siemens product documentation, is that the Comfort Panel and WinCC Runtime Advanced platforms do not support acquisition cycles below 100 ms. WinCC Runtime Professional on a PC platform enforces a 250 ms minimum cycle. The only Siemens-documented path to faster numeric update on a screen is to bypass the standard HMI tag polling and use trend archive logging with a faster sampling tick, accepting that the values rendered on a trend will refresh faster than values on numeric I/O fields bound to the same PLC address.

The 100 ms floor exists for three reasons: the panel's internal scheduler only services the S7 connection at a multiple of 100 ms; the S7 communication driver is non-preemptive and shares its thread with screen redraw; and on a Unified Comfort Panel the WinCC Unified runtime enforces a fixed 100 ms tick on the tag pipeline to guarantee deterministic behavior under Java VM garbage collection. A 10 ms acquisition cycle is below the scheduler quantum, below the HMI connection driver jitter floor, and below the screen redraw budget of any panel in the current Siemens catalog.

2. Siemens HMI Product Families and Acquisition Cycle Limits

The acquisition cycle floor depends on the runtime, not the panel hardware. The table below covers every currently shipping Siemens HMI runtime as of TIA Portal V18/V19. Cycle values not listed in the HMI configuration dialog are grayed out and cannot be selected.

Catalog part numbers are summarized from the Siemens Industry Mall and TIA Portal V19 HSP catalogs. Always cross-check the exact article number against the current Siemens product configurator before ordering, since revisions are frequent. The 6AV2 124 / 6AV2 128 / 6AV2 105 / 6AV2 106 prefixes are stable across the TIA Portal V16-V19 product lifecycle; minor suffix changes (e.g., -0AX0 vs -1AX0) indicate panel revision, not runtime change.

3. Configuring the Acquisition Cycle in TIA Portal

The acquisition cycle is set on the HMI tag properties sheet. The path is identical for Comfort Panels and WinCC Runtime Professional in TIA Portal V18 and V19.

1. Open the HMI project in the TIA Portal project tree.
2. Expand HMI_1 [TP1200 Comfort] → HMI tags → Default tag table (or your custom tag table).
3. Select a single tag or multi-select a group. Right-click and choose Edit → Properties.
4. Open the Properties tab in the inspector window and scroll to the Acquisition cycle field.
5. Click the cycle dropdown. The dropdown lists only the values allowed for the configured HMI device.
6. For a Comfort Panel, the choices are 100 ms, 200 ms, 500 ms, 1 s, 2 s, 5 s, 10 s, 30 s, 1 min, 5 min, 10 min, 1 h, and "Upon change" (event-driven).
7. For a Unified Comfort Panel, the dropdown additionally allows 150 ms, 300 ms, and 600 ms in TIA Portal V19 if the panel firmware is V19 or later.
8. For WinCC Runtime Professional, the dropdown starts at 250 ms and increments in 100 ms steps: 250, 300, 400, 500, ..., 1 s, 2 s, 5 s, etc.

Tags can also be assigned to a named acquisition cycle. This is the Siemens equivalent of a "tag group with scan rate" in other HMI platforms: a single acquisition cycle entry in HMI tags → Acquisition cycles can be referenced from many tag properties, allowing you to set a common 100 ms tick on a critical process variable without editing each tag individually. The acquisition cycle folder is a first-class object in the TIA Portal HMI tag tree as of V17.

4. Why a True 10 ms Acquisition Cycle Is Not Achievable on a Panel

Even if you could enter "10 ms" in the cycle field, the value would not be honored. The reasons are stack-level.

4.1 S7 communication driver scheduling

Comfort Panels use a single-threaded S7 connection. The driver calls read_var() on the configured update interval, parses the response, and pushes results into the tag cache. A full round-trip read on a S7-1500 over PROFINET with one 4-byte tag takes 1-3 ms on the wire, but the panel-side driver also services other connections (alarm logging, recipe, screen change requests) on the same thread. The effective minimum cycle measured in the Siemens Industry Online Support contribution referenced in the source thread on a TP1200 Comfort with one S7-1500 and 50 active tags is 105-120 ms, even when the configured cycle is 100 ms. The full procedure is described in Siemens FAQ 21913875.

4.2 Unified Comfort Panel runtime constraints

Unified Comfort Panels run WinCC Unified on a Java VM. The tag pipeline is implemented in the SCADA server component and the runtime enforces a 100 ms tick to keep the GC pause under 30 ms. A 10 ms tick would generate roughly 100 tag-pipeline events per second per tag, swamping the SCADA server thread and starving the screen redraw. Siemens documents this in the WinCC Unified help under "Performance → Tag cycle behavior" in the TIA Portal information system.

4.3 Screen redraw budget

A Comfort Panel with an 800x480 pixel display running a typical process screen redraws the canvas in 60-80 ms. Even if the tag cache updated at 10 ms, the value visible on the I/O field would only change at the redraw rate. Optimizing the screen (fewer animations, no overlapping transparent objects) can push redraw down to 40-50 ms on a TP700, but not to 10 ms. A TP2200 with a full-graphic screen at 1920x1080 typically redraws in 180-220 ms.

4.4 Practical latency stack

End-to-end observed latency from PLC process value to pixels on a Comfort Panel screen:

Note that 10 ms is below the sum of any single layer in the worst case, let alone the stack. It is physically unachievable on this platform.

5. The Fastest Native Path: Trend and Archive Sampling

The closest Siemens-supported path to a faster numeric update is to use archive tags and let the trend logging system sample the value at a faster rate than the HMI tag poll. This is the approach specifically recommended in the Siemens Industry Online Support contribution cited at the top of this article, and is also the technique that allows a useful "fast" display of a slowly-changing analog value on a Comfort Panel.

5.1 Configuring a fast archive tag

1. Open the HMI project in TIA Portal.
2. Right-click HMI_1 → Historical data → Logs and create a new tag logging log, e.g. ProcessFastLog.
3. Open the new log and add a tag, e.g. PressureActual, configured as Process tag with acquisition type Cyclic or On change.
4. Set the Acquisition cycle to 100 ms (the floor for Comfort Panels). For Unified Comfort Panels with V19 firmware, 50 ms is supported.
5. Open the HMI screen and insert a Trend view or Function trend view control. Bind it to the new log.
6. The trend will refresh at the configured cycle, while a numeric I/O field bound to the same HMI tag will still update at 100 ms. The perceived "speed" of the trend comes from the smooth interpolation of consecutive samples, not from a higher sample rate.

5.2 Using "Upon change" with a tolerance band

If the goal is fast update of a value that does not change continuously, set the archive tag acquisition mode to Upon change with a tolerance (deadband) of 0.1% of engineering range. The tag is logged every time the value moves by more than the deadband. The HMI I/O field is still bound to the tag, but the value will appear to update instantly on every change because the "Upon change" event runs at the panel's event scheduling latency, typically 10-30 ms after the PLC wrote the value. This is the only Siemens-native way to push a sub-100 ms single-event update through a Comfort Panel I/O field, and it only works for values that change discretely (e.g., a valve command echo), not for continuously varying analogs.

6. Sub-100 ms Workarounds for Critical Analog Display

If the application absolutely requires sub-100 ms visual update of a single analog value, none of the options below are "comfort panel" solutions, but all are Siemens-supported and documented.

6.1 WinCC Unified PC Runtime on a high-performance IPC

WinCC Unified PC Runtime on an industrial PC (e.g., SIMATIC IPC227G, IPC277G, IPC477E, IPC847E) supports a 50 ms acquisition cycle on the tag pipeline, and the SCADA server can be tuned to publish tag updates every 50 ms. A separate trend view can render at the same 50 ms tick. End-to-end observed latency is 70-90 ms. This is the lowest-latency native Siemens HMI path as of TIA Portal V19. The 50 ms cycle requires the panel firmware to be V18 Update 2 or later; older firmware silently clamps at 100 ms.

6.2 OPC UA Pub/Sub with a SIMATIC HMI

S7-1500 CPUs with firmware V2.9 or later can publish an OPC UA Pub/Sub stream directly to a Unified Comfort Panel that supports OPC UA subscription (all Unified Comfort Panels with V18 firmware). The publish interval is configurable down to 10 ms on the PLC side and the HMI subscription can be set to 50 ms. This is the only Siemens path that can be configured for a 10 ms transport interval, but the HMI tag cache still updates at 50-100 ms due to the panel-side constraints above. The transport-level 10 ms is useful for downstream analytics on a separate system, not for screen redraw.

6.3 Script-driven polling on a Unified Comfort Panel

WinCC Unified supports JavaScript in the screen logic. A custom script can call the tag API at a faster rate than the configured acquisition cycle, but the tag API itself is throttled to the configured cycle. This is not a workaround; it produces the same result as configuring a faster cycle, which is not allowed below 100 ms. The script overhead on a Unified Comfort Panel also reduces the redraw budget by 5-10%, making the situation worse.

6.4 External high-speed display hardware

For applications that need sub-10 ms display update (vibration monitoring, fast valve response, electrical protection), the standard Siemens answer is to use a SIMOTION or SINAMICS drive controller with a direct DVI/HDMI output to a panel-mount industrial monitor, bypassing WinCC entirely. A SIMOTION P320 with a custom HMI screen can display a 4 ms refreshed value, since there is no WinCC tag pipeline in the loop. This is outside the scope of an HMI tag configuration and should be sized as a separate subsystem, with its own network and grounding.

7. Tag Groups: Optimizing Mixed Cycle Requirements

On a typical process screen, only a handful of values actually need the 100 ms cycle (e.g., a critical pressure or speed). The rest of the tags can run on a 500 ms or 1 s cycle, freeing S7 connection bandwidth and panel CPU. TIA Portal supports this with named acquisition cycles.

1. Open HMI_1 → HMI tags → Acquisition cycles.
2. Create a new cycle, e.g. Cyclic_100ms, with the value 100 ms.
3. Create Cyclic_500ms with 500 ms, Cyclic_1s with 1 s, and so on.
4. Assign each HMI tag to the appropriate cycle on the Properties tab.

This is the Siemens equivalent of the "tag group with scan rate" approach used in other HMI platforms. It does not change the floor (still 100 ms), but it lets you concentrate the 100 ms load on the values that matter and protect the S7 connection from being saturated by a thousand 100 ms tags. The default 1000 ms cycle on a freshly added tag is the global default, not a per-tag setting; change it as soon as the tag is created if 1 s is too slow for the value being monitored.

7.1 S7 connection capacity

An S7-1500 with one Comfort Panel connection supports a maximum of 200 tags at the 100 ms cycle before the connection saturates and the cycle starts drifting upward. If you need more, move some tags to 500 ms or 1 s, or split the panel into two HMI connections (only available on Unified Panels with multi-connection firmware). The S7-1500 connection resource limit is documented in the S7-1500 System Manual under "Number of HMI connections" and is 32 in the standard CPU 1500, 64 in the CPU 1518.

8. Network and Communication Stack Considerations

The 100 ms cycle is degraded by network and stack factors. To get the closest to 100 ms in practice:

• Use PROFINET (not PROFIBUS or MPI) between the PLC and panel. PROFIBUS DP cycle on a 1.5 Mbaud segment adds 5-10 ms per poll.
• Set the PROFINET update time on the PLC port to 1 ms or 250 µs (only for the panel port; the rest of the IO can stay at the default 4 ms).
• Disable the OPC UA server on the panel if it is not used. The OPC UA server takes a slice of the same driver thread.
• Use a direct (cross-over) Ethernet cable if the panel is standalone. Adding a managed switch adds 0.5-2 ms of latency per hop.
• On Unified Comfort Panels, set the Performance mode to "Performance" in the panel control panel. This raises CPU clock and reduces the GC pause impact on the tag pipeline.
• Disable the Web Server and the Sm@rt Server on the panel if the operator does not need remote access. Each of these consumes a separate connection thread that competes with the tag pipeline for CPU.

9. Verification and Commissioning

To confirm the actual update time on the installed panel, use the Siemens WinCC Performance Insight tool or a manual trace.

9.1 WinCC Performance Insight

1. Install WinCC Performance Insight on a service laptop. The tool is a free add-on to TIA Portal V17 and later, available on the Siemens Industry Online Support portal.
2. Connect the laptop to the same subnet as the panel. The tool reads the panel's diagnostic counters over the same S7 connection.
3. Start a trace session. The tool records, per tag, the actual cycle, the maximum jitter, the number of missed cycles, and the screen redraw time.
4. Export the trace as a CSV. The "Actual cycle" column is the value you report back to the application team.

9.2 Manual trace method (no extra tool)

1. On the PLC, add a 100 ms toggle in a free marker (e.g., %MW1000 with CPU_Clock_1Hz XORed).
2. Bind a numeric I/O field on the HMI to the same tag with no formatting (raw integer).
3. Use a high-speed camera (240 fps) or a screen recorder at 60 fps and count the number of frames between the toggle transitions.
4. If the panel updates at exactly 100 ms, you should see one transition every 6 frames at 60 fps. Slower transitions indicate cycle drift.

9.3 Acceptance criteria

10. Decision Matrix: When 100 ms Is Enough and When It Is Not

11. Field-Proven Caveats and Common Errors

• Tag caching across screens: WinCC Runtime keeps tags in cache even when no screen is showing them. A tag at 100 ms cycle consumes bandwidth 24/7, not only when its screen is visible. Do not assign critical fast tags to a screen that is rarely opened; keep them on the home screen or in the alarm log.
• Pointer and array tags: Configuring a 100 ms cycle on a 1000-element array tag will saturate the S7 connection. The driver will throttle the cycle upward to whatever the connection can sustain, often 500 ms or 1 s, silently. Use structured DB access and bind only the individual array elements that need fast update.
• Recipe and data log interference: A recipe transfer in progress pauses the HMI tag poll for the duration of the transfer. Schedule recipe transfers at a time when the operator is not watching the critical screen.
• Firmware version dependency: The 50 ms acquisition cycle on WinCC Unified PC requires panel firmware V18 Update 2 or later. Earlier firmware silently clamps at 100 ms.
• PLC connection limit: A single S7-1500 can serve a maximum of 32 HMI connections (64 on CPU 1518). If you are running 4 panels and a WinCC Professional client, the 33rd connection will be rejected and the panel will fall back to 1 s default cycle. Check the PLC connection count in TIA Portal under Devices & networks → Connections.
• HMI connection drop recovery: When a Comfort Panel loses its S7 connection, it does not immediately fall back to the previous values; it shows the last cached value with a yellow connection-down indicator. The recovery time after a brief cable disconnect is 2-5 seconds, during which no new tag values arrive. Plan operator critical-loop screens with a fallback display that does not depend on real-time tag values.

12. Key Takeaways

• The Comfort Panel and Unified Comfort Panel acquisition cycle floor is 100 ms. The 100 ms value is a floor, not a target: configure carefully and verify with WinCC Performance Insight.
• WinCC Runtime Professional on a PC is the lowest-latency Siemens HMI runtime, with a 50 ms cycle on supported industrial PC hardware.
• For fast numeric display below 100 ms, the answer is not in the HMI tag configuration; it is in a different architecture (high-speed controller, external monitor, hard-wired relay).
• Use named acquisition cycles (Siemens tag groups) to concentrate 100 ms traffic on the tags that actually need it.
• Verify the actual cycle with a field trace. The configured value is the request, not the delivered value.

Frequently Asked Questions