Resolving WinCC Trend Control Slow Update Response Time

WinCC Trend Control Latency: Problem Definition

Operators commissioning a Siemens WinCC Runtime project frequently observe that an Online Trend Control in a process picture updates noticeably slower than an adjacent I/O field bound to the same PLC tag. In a typical complaint, an analog process value is forced in STEP 7 / TIA Portal or via PLCSIM, the I/O field reflects the new value within one acquisition cycle, but the trend curve still shows the previous value for approximately three seconds before the new point is plotted.

This three-second latency is not a single tunable parameter. It is the cumulative sum of three independent update stages inside the WinCC Runtime:

1. The PLC tag acquisition cycle managed by the WinCC tag management channel.
2. The TagLogging acquisition and archive cycle that feeds the in-memory process value buffer.
3. The picture update cycle of the picture window containing the Trend Control, plus the internal redraw rate of the trend widget itself.

Engineers must tune all three stages to compress the end-to-end latency from a default of roughly 2–3 seconds down to a sub-second figure suitable for emulating a paper recorder or capturing fast transients.

WinCC Trend Architecture: From PLC Bit to Pixel

Before touching parameters, understand the data path. A WinCC Online Trend Control does not read the PLC directly. It reads from a WinCC tag that has already been acquired by the tag management, and that tag's value has been recorded by the TagLogging runtime. The control then samples that historical buffer at a fixed display cadence.

The PLC tag in stage 1 is the same tag that the I/O field is bound to. That is why the I/O field is "fast" – it only waits for stage 1. The trend waits for stages 1 + 2 + 3 + 4. The total observed delay is the sum of these stages.

Root Cause Matrix: Why Your Trend Is Three Seconds Late

The most common root causes, in order of frequency, are:

Configuring the Picture Update Cycle (Graphics Designer)

The picture update cycle is the most often missed parameter. It controls how often the entire picture window re-evaluates tags, animations, and control repaints. In classic WinCC (WinCC 7.x and TIA WinCC Professional), it is configured in the Graphics Designer:

1. Open the picture that contains the Online Trend Control.
2. Select the picture background (not the control).
3. Open View → Properties (or right-click → Properties).
4. Navigate to Miscellaneous → Update Cycle.
5. Enter the cycle number from the table below.

For a paper-recorder style trend, set the picture update cycle to 1 (250 ms) or 2 (500 ms). Save and rebuild the runtime.

Configuring TagLogging Acquisition and Archive Cycles

TagLogging is the database layer behind the Online Trend Control. Two parameters drive its latency:

• Acquisition cycle – how often TagLogging reads the WinCC tag.
• Archive cycle – how often the acquired value is written to the in-memory ring buffer and SQL archive.

To configure them in classic WinCC / TIA Portal WinCC Professional:

1. Open the Tag Logging editor.
2. Select the archive (e.g. SYSTEM_ARCHIVE_01) and the process tag inside it.
3. In the properties of the tag, set:
   • Acquisition cycle = 500 ms (or 250 ms if the underlying WinCC tag supports it)
   • Archive cycle = 1 × 500 ms (1× the acquisition cycle, evaluated every 500 ms)

The archive cycle's factor applies a multiple of the acquisition cycle. 1×500 ms means one archive entry per 500 ms acquisition tick. 10×1 s would store one point every 10 s, which is too slow for a paper-recorder emulation.

For a 3-second-latency complaint against a single process value, the typical diagnosis is an archive cycle of 1 × 2 s or 1 × 1 s combined with a picture update cycle of 2 s. Setting both to 500 ms typically drops the perceived latency to under 1 s.

Tuning the WinCC Online Trend Control Properties

Even with a 250 ms archive cycle, the Online Trend Control in classic WinCC has an internal sampling/display tick that historically runs at roughly 1 Hz. The control property knobs that influence responsiveness are:

• Time range of the X axis – a longer range spreads the same archive density over more pixels; perception of "delay" can be visual, not temporal. A 5-minute range with 250 ms archive points is 1200 points. A 30-minute range is 7200 points. Use the shortest range consistent with the operator's task.
• Number of visible points / time base – the time base of the curve (e.g. 500 ms per pixel) is derived from the time range and the screen width.
• Online configuration / source settings – confirm the control is bound to the TagLogging archive, not a static curve or formula.
• Trend type – Online trend (real-time only) is faster than History trend (database read) when starting from a cold cache.

WinCC Unified V20 Trend Control: Time Range and Refresh Behavior

WinCC Unified (TIA Portal V20 and later) re-implements the trend control as an HTML5 / JavaScript-based widget. The configuration dialog differs, but the underlying latency model is similar. To configure the displayed time range in WinCC Unified V20 RT:

1. Click "Select time range" in the toolbar of the trend control. The "Time selection" dialog opens.
2. Choose between the predefined ranges (Last 5 minutes, Last 30 minutes, etc.) or enter a custom start and end time.
3. Confirm with OK; the trend control reloads the data for the selected window.

Reference: Changing the time range of a trend (WinCC Unified V20, TIA Portal)

For real-time updates in WinCC Unified, configure the HMI tag's acquisition cycle in the project tree under HMI tags → [tag] → Properties → Acquisition cycle. The trend control subscribes to the tag through the Unified runtime data source; the lower the acquisition cycle, the more frequently the curve receives new points. Typical values for paper-recorder emulation on a Unified Panel or Unified PC Runtime are 250 ms to 500 ms.

Verification Procedure with PLCSIM and Real PLCs

Validate the tuning with a deterministic test before deploying to the operator screen.

1. Open the picture containing the trend and an I/O field on the same tag.
2. Connect PLCSIM or a real S7-1200/1500. For PLCSIM, start a watch table in STEP 7 / TIA Portal and set the value of the analog input (e.g. MW100) to 0.
3. Note the time on the runtime screen's clock.
4. Apply a step change in the watch table (e.g. 0 → 100) and record the exact second.
5. Observe both indicators:
   • The I/O field should update within one tag acquisition cycle (typically ≤ 1 s).
   • The trend should display the new point within the sum of (archive cycle + picture update cycle). For 500 ms + 500 ms = approximately 1 s; for 250 ms + 250 ms = approximately 0.5 s.
6. Repeat the test with the picture update cycle set to 1 (250 ms) and 4 (2 s). The delta in observed latency confirms whether the picture cycle is the dominant contributor.
7. Repeat with the archive cycle at 1×500 ms and 1×2 s. The delta confirms the archive cycle contribution.

A correctly tuned system with 250 ms archive and 250 ms picture cycle should display a step change in the trend within roughly 500 ms to 1 s. If the I/O field also shows a 1 s delay, the bottleneck is the PLC tag acquisition, not the trend.

Edge Cases, Alias Tags, and Field-Proven Caveats

After the obvious parameters are tuned, a few less common factors still produce a "slow trend" symptom:

• Alias tags pointing to an indirectly accessed DB: If the trend is bound to an HMI tag that uses a tag-prefixed path through an S7 connection and the underlying DB is optimized (S7-1500), the symbolic access may take 1 s per request. Switch the DB access to absolute or to a non-optimized DB to test.
• Multiple trend windows open simultaneously: Each active Online Trend Control instance holds its own buffer subscription. Opening ten trend windows on ten fast tags can starve TagLogging cycles. Open only the trend window the operator needs.
• Compressed archive on a slow disk: If the runtime stores the TagLogging archive on a network share or a spinning disk under heavy SQL Server load, archive writes block. Move the archive to a local SSD or reduce the number of tags in the archive.
• PLCSIM throttling: PLCSIM in some TIA Portal versions caps variable writes to one per second through a watch table in RUN. Use the PLCSIM virtual controller's web API or a script (e.g. SCL in a cyclic OB) to drive faster changes during commissioning.
• License of TagLogging Fast: The "fast" archive option in WinCC TagLogging allows sub-second cycle archives but requires a valid WinCC Logging license. If the license is missing, the runtime silently falls back to a 1 s minimum cycle. Verify in WinCC Explorer → Properties → Runtime settings → TagLogging.
• OPC UA connection throttling: If the WinCC tag is sourced through an OPC UA server (third-party or another SCADA), the published item sampling interval on the OPC server is the floor of the trend's responsiveness. A 1 s OPC sampling rate cannot be improved from the WinCC side.

Troubleshooting Matrix

Frequently Asked Questions