Fixing Symbolic IO Field Text List Updates in WinCC Unified V16

Problem Overview

A Symbolic IO field bound to a Text list in WinCC Unified (RT Unified) continues to display the original text value after the engineer modifies the underlying text list entry inside TIA Portal V16 Update 3. Editing the default entry, value list pair, or text content of an existing text list does not propagate to the Symbolic IO field at runtime even after a successful compile and download cycle. The defect is reproducible on PC Runtime and is independent of the PLC tag value itself - the tag updates correctly, only the rendered text from the text list remains stale.

The failure mode is specific to the symbolic IO field (the WinCC Unified variant that drives its display through a text list reference) and does not affect plain numeric or string IO fields that read tag values directly. The issue is documented in field reports against TIA Portal V16 Update 3 and the bundled WinCC Unified runtime. Engineers should treat any text list change on an active HMI project as a potential trigger for this defect and apply one of the documented remediation paths before resuming commissioning.

Affected Environment and Versions

Root Cause Analysis

The Symbolic IO field in WinCC Unified stores a resolved copy of the text list lookup table in the compiled screen artifact. During incremental compile, TIA Portal regenerates the screen container but, in V16 Update 3, does not always invalidate the cached text list snapshot consumed by the runtime. Three contributing factors have been observed in field reproductions:

1. Stale incremental compile output. The Compile > Rebuild All command is required to force regeneration of the text list dependency graph. A standard Compile > Software (rebuild only changes) leaves the prior text list binary intact in the IM folder of the runtime project.
2. Browser cache retention on PC Runtime web client. The Unified PC Runtime serves the screen HTML and JavaScript artifacts through a local web server. Edge/Chrome retains the prior text list JSON in the browser cache, and the runtime does not append a content-hash suffix to the text list payload in V16 Update 3.
3. Runtime-side text list index pointer. The runtime caches the text list ID-to-entry mapping at startup. A warm restart of the runtime service reloads the mapping, but a soft reload (browser refresh only) does not. Operators commonly click refresh on the web client and assume the change has taken effect when in fact the runtime service still serves the old mapping.

The combination of any two of these three factors is sufficient to reproduce the symptom. The reliable remediation is to invalidate all three at once.

Prerequisites

• TIA Portal V16 Update 3 installed with WinCC Unified ES and RT components.
• Administrative access to the engineering station and the runtime station.
• Read/write permission on the runtime project directory (default: C:\Program Files\Siemens\Automation\WinCCUnified\RT_V16\<ProjectName>).
• Ability to stop and restart the WinCC Unified Runtime service: WinCCUnifiedRT_V16.
• Current backup of the TIA project and runtime archive (created with Project > Archive and Runtime > Backup).

Step-by-Step Remediation

Apply the steps below in order. Stop at the first procedure that resolves the symptom; if the defect returns after additional text list edits, proceed to the next procedure.

Procedure A - Incremental Rebuild with Dependency Wipe

1. In TIA Portal, close all open editors and the project navigator search pane.
2. Open the project tree, right-click the HMI device, and select Compile > Rebuild All. This regenerates the screen container, text list binaries, and the runtime deployment package.
3. Wait for the compile to finish and confirm no warnings are reported on the Info > Compile tab. Any warning about unresolved text list references aborts this procedure - fix the reference first.
4. Download the rebuilt HMI to the target device. Use Download to device > Software and configuration; do not use Download to file system only.
5. On the runtime station, open the WinCC Unified web client, append the parameter ?ts=<current_unix_timestamp> to the URL to force a bypass of the browser cache (example: https://localhost/?ts=1717000000).
6. Verify the Symbolic IO field reflects the updated text list entry.

Procedure B - Manual Browser Cache Invalidation

If Procedure A does not clear the stale display, the browser cache is the residual culprit. Apply a forced cache wipe on every client that connects to the Unified PC Runtime.

1. Close all browser windows targeting the Unified Runtime URL.
2. Open Edge or Chrome, press Ctrl + Shift + Delete.
3. Select Time range: All time.
4. Enable the checkboxes: Cookies and other site data, Cached images and files.
5. Click Clear now.
6. Reopen the Unified Runtime URL in an incognito/private window to confirm the fix.

Procedure C - Runtime Service Restart

A warm restart of the runtime reloads the text list mapping from the latest downloaded configuration. This is the most reliable single-step fix when both Procedures A and B have been attempted without success.

1. Open Services on the runtime station (Win + R, services.msc).
2. Locate WinCC Unified Runtime V16.
3. Right-click and select Stop. Wait until the service state reports Stopped.
4. Right-click and select Start. Wait for the service state to report Running.
5. Optionally verify the process is alive by opening Task Manager and confirming WinCCUnifiedRT.exe is consuming CPU cycles.
6. Reconnect the operator client and verify the Symbolic IO field.

Procedure D - Text List Deletion and Recreation

When the prior three procedures fail to invalidate the cached reference inside the screen container, the only remaining field-proven remediation is to delete the affected text list and recreate it under a new name. This forces the compiler to regenerate the lookup table and rebind the Symbolic IO field reference.

1. In TIA Portal, open the project tree, navigate to HMI > Text and graphics lists > Text lists.
2. Right-click the affected text list and select Delete. Confirm deletion.
3. Right-click the Text lists folder and select Add new text list. Use a distinct name (for example StatusList_v2) to avoid potential collision in the runtime cache.
4. Re-enter the entries, default value, and any range definitions that the original text list contained.
5. Open every screen that referenced the old text list and reassign the Symbolic IO field Text list property to the new name.
6. Compile the HMI device with Rebuild All.
7. Download the HMI to the device and restart the runtime service (Procedure C, steps 1-5).
8. Clear the browser cache on the operator client (Procedure B).
9. Verify the Symbolic IO field reflects the new text list entries.

Cache Management Deep Dive

WinCC Unified RT uses three distinct cache layers. Understanding each layer prevents recurring stale-text symptoms after every text list edit.

The reported defect manifests when any one of these layers continues to serve the prior text list payload while the others have been refreshed. The only fully deterministic procedure is the simultaneous invalidation of all four layers: rebuild, runtime download, service restart, and browser cache wipe.

Compilation Strategies

Engineers accustomed to incremental compile workflows on WinCC Comfort / Flexible will find that WinCC Unified demands stricter compile discipline for text list changes. The following practices reduce the probability of the defect recurring:

• Always use Compile > Rebuild All after editing a text list. The incremental compiler tracks screen-to-tag dependency but does not always detect text list dependency changes in V16 Update 3.
• Perform text list edits in dedicated engineering windows separated by at least one rebuild cycle. Avoid editing multiple text lists and downloading in a single session without an intermediate rebuild.
• When a text list edit must be deployed rapidly, prefer Procedure D (recreation under a new name) over editing the existing list in place. Recreation forces the compiler to allocate a fresh internal identifier, bypassing the cached mapping.
• Maintain a project-level change log entry for every text list modification, including the timestamp, the entry changed, the rebuild status, and the verification screenshot. This log accelerates root cause analysis when the symptom recurs.

Runtime Considerations for PC Runtime

The PC Runtime loads the HMI configuration at service start. Subsequent runtime configuration updates through TIA Portal download do not always reload the text list tables if the service was started with the configuration cache warm. The recommended startup sequence for PC Runtime after a text list edit is:

1. Download the HMI device from TIA Portal.
2. Open the WinCC Unified Configuration Manager on the runtime station.
3. Select the project and click Stop runtime.
4. Wait for the runtime status to read Stopped.
5. Click Start runtime. This performs a cold start of the runtime service.
6. Confirm the Symbolic IO field in the operator client.

Verification Checklist

After applying any remediation, verify the fix with the following checklist:

• The Symbolic IO field displays the new text list value within 2 seconds of a tag value change.
• The default text list entry is shown when the tag value falls outside the configured list range.
• Switching the operator client to an incognito window reproduces the correct text - confirms browser cache is not masking a residual defect.
• A second text list edit (after the fix) propagates on the next incremental compile without requiring the recreation procedure.
• The HMI Info > Compile log shows no warnings or errors related to text list references.

Escalation to Siemens Support

If all four procedures fail to resolve the defect, escalate through Siemens Technical Support with the following evidence package:

1. The TIA Portal project file (.ap16) archived with Project > Archive.
2. A minimal reproduction project containing one screen, one text list, and one Symbolic IO field that demonstrates the defect.
3. The HMI Info > Compile log exported as .txt.
4. The runtime diagnostic dump captured with the WinCC Unified Diagnostic Viewer.
5. The version output of Help > About > Installed software showing the exact TIA Portal and WinCC Unified build numbers.
6. Description of which procedures were attempted and their results.

Open the support request through the Siemens Industry Online Support portal at support.industry.siemens.com and reference the service request number in all follow-up communications.

Related Configuration Reference

The Symbolic IO field configuration in WinCC Unified is documented in the official Siemens TIA Portal Help. For projects migrating from WinCC Comfort or WinCC Advanced, review the Text list property under Properties > General > Text list on the Symbolic IO field and confirm the default entry is selected. The official reference is available at Symbolic IO field (RT Unified) - WinCC Unified.

Troubleshooting Matrix

FAQ