Troubleshooting WinCC Bar Graph Display Inactive with Yellow Warning Triangle in PCS 7

In WinCC Graphics Designer and PCS 7 Runtime, a bar graph that appears grayed out and displays a yellow warning triangle icon indicates an invalid tag interconnection, an unresolved tag structure, or a bad quality code from the automation controller. This issue commonly occurs when a tag was linked using an incomplete structure (such as omitting the CFC chart name) or when an analog value possesses bad signal status (ST = 16#00). To fix the bar graph: 1. Open the dynamic connection property and verify the tag syntax adheres to PlantHierarchy/CFC_Chart/Block.Parameter#Value; 2. Check the controller channel driver (Pcs7AnIn) in CFC to ensure hardware diagnostics or wire breaks are cleared; and 3. Confirm tag prefixes match if placed inside picture windows.

Executive Summary

When developing human-machine interface (HMI) screens in WinCC Graphics Designer for SIMATIC PCS 7, engineers frequently use the Dynamic Wizard or manual tag binding to link process variables to standard graphical bar graphs. In runtime, an engineer may observe that a specific bar graph remains grayed out and static, marked by a prominent yellow warning triangle, even while other bar graphs in the same picture function normally. Disabling simulation mode on the controller fails to clear the warning. This article details how WinCC evaluates runtime tag dynamics and quality codes, diagnoses the root causes of the yellow warning triangle, and provides step-by-step instructions to correct tag syntax, restore signal quality, and align picture window prefixes.

Architecture and Fundamental Mechanics

WinCC Runtime Dynamic Evaluation, Quality Code Badges, and Tag Naming Mechanics:

The Yellow Warning Triangle Meaning in WinCC:
In SIMATIC WinCC / PCS 7 OS, the yellow warning triangle on a graphical object indicates an Invalid Quality Code or an Unresolved Dynamic Tag Connection.
When WinCC detects that a dynamically bound tag does not exist in the Tag Management database, cannot be polled via the communication channel, or returns a Quality Code indicating Bad signal status (16#00 or 16#28), the runtime engine sets the object to its configured error display state (typically grayed-out fill with the yellow warning badge).
PCS 7 Structured Tag Naming Syntax:
Unlike standalone WinCC projects that utilize flat internal tags, PCS 7 generates structured process tags during AS-OS compilation.
The tag name syntax in WinCC Tag Management strictly mirrors the plant hierarchy: <Plant_Hierarchy>/<CFC_Chart>/<Block_Instance>.<Parameter>.
For an analog floating-point variable with signal status, the tag structure contains sub-elements: .PV_Out#Value (real process value) and .PV_Out#ST (quality status byte).
If an engineer manually configures a dynamic connection using only BlockName.Parameter or omits the CFC chart name, WinCC fails to resolve the tag, immediately rendering the yellow warning triangle.
Quality Code Influence (ST Byte):
In PCS 7 APL, if the upstream channel driver (Pcs7AnIn) reports Bad = 1 (caused by open circuit, sensor failure, or missing module QMODF = 1), the output status byte PV_Out.ST becomes 16#00 (Bad).
Even if the value appears as 0.0 in the controller, WinCC evaluates ST and marks the bar graph invalid because the data is legally untrustworthy.
Picture Window Tag Prefix Conflicts:
If the bar graph resides inside a picture displayed within a WinCC Picture Window (@PictureWindow), the window's TagPrefix property is automatically prepended to all relative tag names.
If an absolute tag path is configured inside a prefixed window, the resulting tag lookup becomes Prefix/Prefix/Chart/Block, which fails to resolve in runtime.

Step-by-Step Implementation Procedure

Inspect the Bar Graph Dynamic Configuration in Graphics Designer:
* In WinCC Explorer, open the graphic picture containing the failing bar graph.
* Right-click the Bar Graph object and select Properties.
* Navigate to Geometry or Process Value under the Dynamic column.
* Check whether the property is animated via a Direct Tag Connection, a Dynamic Dialog, or a C/VBS Script.
Validate Tag Syntax and Hierarchy Path:
* Open the dynamic binding dialog.
* Compare the configured tag string against a working bar graph.
* Ensure the tag string contains the full hierarchy path: Area/Unit/CFC_Chart/Block.PV_Out#Value.
* If the tag was typed manually, click the Tag Browser button (...), navigate to WinCC Tag Management, and re-select the exact tag to guarantee syntactic accuracy.
Inspect Quality Code in CFC Test Mode:
* Open SIMATIC Manager and open the CFC chart supplying the process value.
* Switch to Test Mode (Ctrl+F).
* Inspect the output parameter of the channel driver (Pcs7AnIn.PV_Out).
* Check the signal status byte ST: if ST = 16#00 or 16#28, the channel is faulted.
* Check if Bad = 1 or if hardware wire-break diagnostics are active on the analog input channel in HW Config.
* Correct the sensor wiring, supply valid simulation input, or resolve module driver faults.
Verify Picture Window Tag Prefix Compatibility:
* If the graphic is loaded inside a parent picture window, check if the parent window assigns a TagPrefix.
* If a prefix is present, format the bar graph dynamic property as a relative tag name (e.g. Block.PV_Out#Value without chart prefix), or ensure the prefix matches the exact parent hierarchy.
Save and Test in Runtime:
* Save the modified picture in Graphics Designer.
* Return to WinCC Runtime; trigger a screen change to reload the picture.
* Confirm that the bar graph displays the active bar level and that the yellow warning triangle clears.

Verification

In WinCC Runtime, navigate to the screen hosting the bar graph.
Verify that the yellow warning triangle is no longer visible.
Verify that the bar graph dynamically reflects process value changes (e.g. changing between 0% and 100%).
In CFC test mode, temporarily disconnect the sensor or force SimOn = 1 with a substitute value to confirm that the bar graph responds correctly to valid simulated data.

Limitations and Operational Precautions

Disabling simulation mode on a channel driver (SimOn = 0) will NOT clear the yellow warning triangle if the physical sensor is disconnected or experiencing a wire break; under open-circuit conditions, the driver immediately transitions from simulation to Bad quality (16#00), keeping the warning active. If using custom C-scripts to animate bar graphs, syntax errors or runtime exceptions in the script will also trigger the invalid object badge.

Engineer FAQ

What does the yellow triangle on a WinCC bar graph signify?

It indicates an invalid tag connection, an unresolvable tag name, or that the connected tag possesses a Bad Quality Code (ST = 16#00).

Why did turning off simulation not clear the yellow warning?

If the physical field sensor is disconnected or faulty, the channel driver reverts to Bad quality (ST = 16#00), preserving the warning triangle.

What is the correct tag syntax for PCS 7 analog values?

The full hierarchical path: <Hierarchy>/<CFC_Chart>/<Block_Instance>.<Parameter>#Value (e.g. Area/TIC101/MonAnL.PV_Out#Value).

Can a tag prefix in a picture window cause the warning triangle?

Yes, if an absolute tag name is configured inside a picture window that already has a TagPrefix, the resulting concatenated tag name fails to resolve.